Github user jiajunwang commented on the issue:
https://github.com/apache/helix/pull/300
I don't think we can simply make this thread daemon. Actually, it only
makes sense when all the handlers are finalized. If one or more handlers are
still active, the re-subscribe function is
+1
On Tue, 5 Feb 2019 at 08:23, Xue Junkai wrote:
> Hi,
>
>
> This is to call for a vote on releasing the following candidate as Apache
> Helix 0.8.3. This is the 15th release of Helix as an Apache project, as
> well as the 11th release as a top-level Apache project.
>
>
> Apache Helix is a
GitHub user mebe opened a pull request:
https://github.com/apache/helix/pull/300
Daemonize SubscribeChangeEventProcessor thread in CallbackProcessor
`CallbackProcessor.SubscribeChangeEventProcessor` is a `DedupEventProcessor
extends Thread`. It is started in a static initializer in
GitHub user mebe opened a pull request:
https://github.com/apache/helix/pull/299
Remove unused _forceRebalanceTimer from GenericHelixController
`GenericHelixController. _forceRebalanceTimer` is a non-daemon `Timer`
thread. It is started in the initializer of
