You are viewing a plain text version of this content. The canonical link for it is here.
Posted to reviews@helix.apache.org by GitBox <gi...@apache.org> on 2020/09/16 00:28:14 UTC

[GitHub] [helix] vvavepacket opened a new issue #1364: [Question] Worker not executing submitted job by Administrator

vvavepacket opened a new issue #1364:
URL: https://github.com/apache/helix/issues/1364


   I tried submitting my query to the mailing list but I didn't get confirmation that it went through. In case it got submitted there I will close this issue and continue the conversation there.
   
   I'm new to Helix and trying to learn it. I was able to create a helix cluster and able to see my Participant joined the cluster by seeing it in zookeeper. Question, why is that when I'm trying to submit a job thru the Administrator, my Participant is not picking them up (not able to see the run method invoked in my user implemented Task class)?
   
   I mainly used this as guide for creating my task, job and workflow. However on the integration tests, I see a scenario where we need to register the task as a callback, but I never see their usage on the tutorial. My question are
   
   1. When is the time we need to explicitly register task callbacks? 
   2. What's the difference between StateModel and TaskStateModel and when should we use one over the other? In my implementation, I only used a StateModel with no callbacks as per the tutorial, but some integration tests are using TaskStateModel with callbacks


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@helix.apache.org
For additional commands, e-mail: reviews-help@helix.apache.org