You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@shardingsphere.apache.org by GitBox <gi...@apache.org> on 2020/11/19 03:29:13 UTC

[GitHub] [shardingsphere-elasticjob] kaihekaihe opened a new issue #1725: how is “failover” properly setted to the executionSource，the property of the JobExecutionEvent.

kaihekaihe opened a new issue #1725:
URL: https://github.com/apache/shardingsphere-elasticjob/issues/1725


   ## Feature Request
   
   **For English only**, other languages will not accept.
   
   Please pay attention on issues you submitted, because we maybe need more details. 
   If no response anymore and we cannot make decision by current information, we will **close it**.
   
   Please answer these questions before submitting your issue. Thanks!
   
   ### Is your feature request related to a problem?
   
   ### Describe the feature you would like.
   
   
   
   
   In JobExecutionEvent,Enum ExecuitonSource has three members:NORMAL_TRIGGER, MISFIRE, FAILOVER,but FAILOVER is only used by a test class。
   
   As is shown in ElasticJobExecutor，the failovered shard may be triggered by NORMAL_TRIGGER or MISFIRE。
   
   If “failover” can be setted to the property of JobExecutionEvent，it will be more clear to view the process of the execution for users


----------------------------------------------------------------
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

[GitHub] [shardingsphere-elasticjob] TeslaCN commented on issue #1725: how is “failover” properly setted to the executionSource，the property of the JobExecutionEvent.

Posted by GitBox <gi...@apache.org>.

TeslaCN commented on issue #1725:
URL: https://github.com/apache/shardingsphere-elasticjob/issues/1725#issuecomment-732765260


   Thanks for your feedback. The current way to trigger failover shard does lead to this issue. We can further discuss it if you are interested in.


----------------------------------------------------------------
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