You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Crash in commit_compaction_data causes severe issues. However it is quite hard to figure out what shard it was crashed on. We need to add logging to log shard name in case of a crash in the critical function.
Expected Behavior
When commit_compaction_data crashes for any reason we should see a message in the log which contains the shard name.
Current Behavior
There is a crash dump which doesn't contain any useful information to identify problematic shard.
Crash in
commit_compaction_data
causes severe issues. However it is quite hard to figure out what shard it was crashed on. We need to add logging to log shard name in case of a crash in the critical function.Expected Behavior
When
commit_compaction_data
crashes for any reason we should see a message in the log which contains the shard name.Current Behavior
There is a crash dump which doesn't contain any useful information to identify problematic shard.
Possible Solution
Add
try/catch
and log from thecatch
Steps to Reproduce (for bugs)
See https://github.com/apache/couchdb/pull/1255/files#diff-b6c880ef1513b1db939914f94786a1a5
Context
Your Environment
The text was updated successfully, but these errors were encountered: