[GOBBLIN-774] Send nack when a control message handler fails in Fork

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.15.0
• Assignee: Hung Tran
• Reporter: Hung Tran
• Created: 20/May/19 22:18
• Updated: 21/May/19 03:56
• Resolved: 21/May/19 03:55

Description

Fork will raise an error without ack/nacking if the control message handler raises an error. This can result in another thread waiting indefinitely for a control message ack. Fork.

consumeRecordStream() should handle control message exceptions by calling nack() with the exception before reraising the error.

Issue Links

• links to: GitHub Pull Request #2639