storm-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ? ?? <>
Subject Executor Change
Date Fri, 04 Aug 2017 05:45:01 GMT

    It is observed that the executor of a task changes to a different worker on  a different
supervisor. And the computation, which is similar to wordcount,  stops and starts over. After
several tests, I find that this is caused by the lost of the task state during executor change.
So I wonder:

  1.  Why does the change happen?
  2.  When the change happen, does the executor use a new component(bolt) instance? How does
the instance come into being? By constructor or deserialization?
  3.  In this case, how to persist the task state?


View raw message