addressing deadlocks in wal

Author: ayushsatyam146

internal/wal/wal_forge.go

@@ -192,12 +192,8 @@ func (wl *walForge) rotateLogIfNeeded(entrySize uint32) error {
 
 // rotateLog rotates the log by closing the current segment file,
 // incrementing the current segment index, and opening a new segment file.
-// This method is thread safe.
 func (wl *walForge) rotateLog() error {
 	fmt.Println("rotating log")
-	wl.mu.Lock()
-	defer wl.mu.Unlock()
-
 	// TODO: Ideally this function should not return any error
 	// Check for the conditions where it can return an error
 	// and handle them gracefully.
@@ -237,11 +233,7 @@ func (wl *walForge) rotateLog() error {
 
 // Writes out any data in the WAL's in-memory buffer to the segment file.
 // and syncs the segment file to disk.
-// This method is thread safe.
 func (wl *walForge) sync() error {
-	wl.mu.Lock()
-	defer wl.mu.Unlock()
-
 	// Flush the buffer to the segment file
 	if err := wl.csWriter.Flush(); err != nil {
 		return err
@@ -262,6 +254,8 @@ func (wl *walForge) sync() error {
 }
 
 func (wl *walForge) periodicSyncBuffer() {
+	wl.mu.Lock()
+	defer wl.mu.Unlock()
 	for {
 		select {
 		case <-wl.bufferSyncTicker.C:
@@ -277,6 +271,8 @@ func (wl *walForge) periodicSyncBuffer() {
 
 func (wl *walForge) periodicRotateSegment() {
 	fmt.Println("rotating segment")
+	wl.mu.Lock()
+	defer wl.mu.Unlock()
 	for {
 		select {
 		case <-wl.segmentRotationTicker.C: