pulsar-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] jerrypeng opened a new issue #2720: Improving stop and start function instances
Date Thu, 04 Oct 2018 21:35:02 GMT
jerrypeng opened a new issue #2720: Improving stop and start function instances
URL: https://github.com/apache/pulsar/issues/2720
 
 
   Currently, when a user submits a request to stop or start a function instance, the worker
that receives the request attempt to redirect the stop or start request to the actual worker
running the function instance.  I don't think this is a good mechanism for this and it is
prone to failures.  What is happening here is a state change, however the state change isn't
persisted, thus when failures happen this state change is lost.  For example, if the worker
running the function instance has stopped the instance but then the worker itself crashes.
Upon restarting, the worker will start the function instance in the incorrect state.
   
   The better mechanism for doing this add a field FunctionMetaData, to indicate the state
of the function instance.  And when the worker that is assigned/running the function instances
reads from the FunctionMetaData topic gets an update of the state, it can act accordingly.
 This will also persist across failures and functions instances will get restarted in the
correct state.
   
   @rdhabalia can you provide feedback?
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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


With regards,
Apache Git Services

Mime
View raw message