Server: The server fails to flush the in-memory table if the data file is locked by another process

[ohsayan]

Description of bug
When the server starts, it only reads from the data.bin file to restore the previously stored data. In the current implementation, if another process locks the file (for some reason, not something predictable) while the server is running, the server quits without flushing the data - with an error message.

There are two solutions to this:

1. Lock the file (record-level) OR
2. Wait for the other process to release the lock

For (1): This is fairly easy to implement and is better than (2) since we already have a lock on the file. Also, in the event that a quick shutdown is needed, this would be the most reliable option.
For (2): This is the easiest thing to implement - but there are doubts about how reliable this can be. The lock on the file may never be released and we may never be able to write to it. Also, if a quick shutdown is required, this solution is not favorable at all.

Steps to reproduce
NA

Expected behavior
NA

Meta

• Release tag: None
• Branch: None
• Commit ID: None
• Operating system: None

Additional context
None

[ohsayan]

Marking this as Windows only since on Windows locking is mandatory by default. This wouldn't be a problem on *nix systems.

[ohsayan]

As of now, we keep on looping until we get to write the file to disk, waiting for the user to retry.

Edit: Downgrading to low priority

[ohsayan]

This is a very rare scenario, and isn't something reproducible. I will reopen this when the problem reappears.