[SENTRY-1940] Sentry should time out threads waiting for notifications

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0
• Fix Version/s: 2.0.0
• Component/s: Sentry
• Labels: bite-sized newbie
• Assignee: Alex Kolbasov
• Reporter: Alex Kolbasov
• Created: 11/Sep/17 00:37
• Updated: 11/Sep/17 23:25
• Resolved: 11/Sep/17 23:25

Description

HMS synchronizes with Sentry by sending special sync requests waiting for notifications to be processed. When notification processing is delayed, a lot of Sentry service threads can be tied up waiting. HMS eventually times out these requests but Sentry doesn't, so if notifications are delayed, all service threads may become busy for a long time.

We must introduce a timeout on the Sentry side as well to avoid this scenario.

Issue Links

• relates to: SENTRY-1942 Bump BoneCP version from 0.7.1 to 0.8.0
• links to: Code review