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

Posted to commits@helix.apache.org by "kishore gopalakrishna (JIRA)" <ji...@apache.org> on 2013/05/15 02:46:13 UTC

[jira] [Commented] (HELIX-8) Inconsistent ordering of thread interrupt and reset() method call on StateModel methods.

    [ https://issues.apache.org/jira/browse/HELIX-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13657757#comment-13657757 ] 

kishore gopalakrishna commented on HELIX-8:
-------------------------------------------

Terence, do you know how to fix this ?
                
> Inconsistent ordering of thread interrupt and reset() method call on StateModel methods.
> ----------------------------------------------------------------------------------------
>
>                 Key: HELIX-8
>                 URL: https://issues.apache.org/jira/browse/HELIX-8
>             Project: Apache Helix
>          Issue Type: Bug
>    Affects Versions: 0.6.0-incubating
>            Reporter: Terence Yim
>            Assignee: dafu
>             Fix For: 0.6.2-incubating
>
>
> The execution thread of the StateModel state transition method would get interrupted upon HelixManager.disconnect() is called, followed by reset() method. However, if zk connection expired, upon the reconnection, the reset() method is called before the state transition thread get interrupted.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira