Komal Desai
Komal Desai
Hello, Picking up this thread. Helix understands 2 kinds of messages which results in state-transitions: - recovery rebalance and regular load-balance Users can prioritize which task-transition takes precedent: eg: "listFields":...
good to hear from you @jiajunwang :-) thanks for the context. will update the thread once we have some design in-place
can the person with right set of access, please close this bug as we have fixed the issue and merged the change.
Hello @vaidhyanathan-ananthakrishnan-13 - can you elaborate on what is the size of the cluster, #resources etc this will help us simulate
not that i am aware of. i am relatively new and so not sure if others have seen this issue before.
Can we first create feature-branch? Then start working from their.
this test failure we haven't seen for over last 6 month. also this file was deleted as part of the other change and so this issue can be closed. thanks
Hello @bojanv55 - i am part of Helix core dev team here at @LinkedIn. I am trying to understand if this issue still exists? If possible, can you please close...
@mgao0 implemented the feature where user can specify customized threadpool for different ST messages: https://github.com/apache/helix/pull/2390 Hope the change addresses this requirement. @jackjlli - can you please mark this issue FIXed...
We have confirmed that by override the getExecutorService() method in StateModelFactory will resolve this issue. Please close this issue as FIXED once you are satisfied with the requet.