[KUDU-320] Running out of space should be handled more gracefully

• Type: Bug
• Status: Open
• Priority: Trivial
• Resolution: Unresolved
• Affects Version/s: M4
• Component/s: tablet
• Labels: roadmap-candidate
• Target Version/s: Backlog
• Assignee: Unassigned
• Reporter: Alex Feinberg
• Created: 31/May/14 18:17
• Updated: 28/May/20 15:37

Description

We could be more graceful when handling situations when we run out of space: it can be deadlock (when happens during unit test) or a bus error.

This is low priority and we shouldn't do much (it is the operator's responsibility to monitor disk space), but shutting down with "out of disk space" would be more graceful.

clien-test logs when my desktop ran out of space (for an unrelated reason):

W0531 15:49:12.632431 13187 rpc_server.cc:102] Unable to unregister service kudu.tserver.TabletServerService: Service unavailable: Service is not registered
...
W0531 15:49:46.814546 13187 thread.cc:360] Waited for 18000ms trying to join with rpc worker

Issue Links

• relates to: KUDU-1768 Tablet server cannot recover after run out of disk space