[SERVER-40308] ShardRegistry should not reload after shutdown Created: 22/Mar/19  Updated: 20/Jun/19  Resolved: 19/Jun/19

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Misha Tyulenev Assignee: Benjamin Caimano (Inactive)
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Sprint: Service Arch 2019-04-08, Service Arch 2019-05-06, Service Arch 2019-05-20, Service Arch 2019-06-03, Service Arch 2019-06-17, Service Arch 2019-07-01
Participants:

 Description   

In BF-11792 logs the reload call fails here due to ShutdownInProgress exception.
However, the following call to the executor to reschedule the reload does not return the ShutdownInProgress status and hence the reload attempts being retried indefinitely.



 Comments   
Comment by Benjamin Caimano (Inactive) [ 19/Jun/19 ]

So parts of the ShardRegistry can run after shutdown, but they'll catch interrupts pretty quick. Beyond some code smells and some poorly written log messages, there isn't a lot to fix here. I suspect that what lead this ticket to exist is summed up with BF-13577. In short, RSTargeter.findHost() can ignore its timeout.

Generated at Thu Feb 08 04:54:36 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.