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

Hudson commented on ZOOKEEPER-1124:
-----------------------------------

Integrated in ZooKeeper-trunk #1244 (See 
[https://builds.apache.org/job/ZooKeeper-trunk/1244/])
    ZOOKEEPER-1124. Multiop submitted to non-leader always fails due to timeout

breed : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1146961
Files : 
* 
/zookeeper/trunk/src/java/main/org/apache/zookeeper/server/quorum/FollowerRequestProcessor.java
* /zookeeper/trunk/src/java/test/org/apache/zookeeper/test/QuorumTest.java
* /zookeeper/trunk/CHANGES.txt
* 
/zookeeper/trunk/src/java/main/org/apache/zookeeper/server/quorum/ObserverRequestProcessor.java


> Multiop submitted to non-leader always fails due to timeout
> -----------------------------------------------------------
>
>                 Key: ZOOKEEPER-1124
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1124
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 3.4.0
>         Environment: all
>            Reporter: Marshall McMullen
>            Priority: Critical
>             Fix For: 3.4.0
>
>         Attachments: ZOOKEEPER-1124.patch
>
>
> The new Multiop support added under zookeeper-965 fails every single time if 
> the multiop is submitted to a non-leader in quorum mode. In standalone mode 
> it always works properly and this bug only presents itself in quorum mode 
> (with 2 or more nodes). After 12 hours of debugging (*sigh*) it turns out to 
> be a really simple fix. There are a couple of missing case statements inside 
> FollowerRequestProcessor.java and ObserverRequestProcessor.java to ensure 
> that multiop is forwarded to the leader for commit. I've attached a patch 
> that fixes this problem.
> It's probably worth nothing that zookeeper-965 has already been committed to 
> trunk. But this is a fatal flaw that will prevent multiop support from 
> working properly and as such needs to get committed to 3.4.0 as well. Is 
> there a way to tie these two cases together in some way?

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to