You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Patrick Hunt (JIRA)" <ji...@apache.org> on 2014/06/25 19:52:25 UTC
[jira] [Commented] (ZOOKEEPER-1784) Logic to process
INFORMANDACTIVATE packets in syncWithLeader seems bogus
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14043826#comment-14043826 ]
Patrick Hunt commented on ZOOKEEPER-1784:
-----------------------------------------
[~shralex] is this something we need to consider for 3.5? How big of an issue is it?
> Logic to process INFORMANDACTIVATE packets in syncWithLeader seems bogus
> ------------------------------------------------------------------------
>
> Key: ZOOKEEPER-1784
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1784
> Project: ZooKeeper
> Issue Type: Bug
> Affects Versions: 3.5.0
> Reporter: Raul Gutierrez Segales
> Assignee: Raul Gutierrez Segales
> Attachments: ZOOKEEPER-1784.patch
>
>
> If you look at Learner#syncWithLeader:
> {noformat}
> while (self.isRunning()) {
> readPacket(qp);
> switch(qp.getType()) {
> .......
> case Leader.INFORM:
> case Leader.INFORMANDACTIVATE:
> PacketInFlight packet = new PacketInFlight();
> packet.hdr = new TxnHeader();
> if (qp.getType() == Leader.COMMITANDACTIVATE) {
> {noformat}
> I guess "qp.getType() == Leader.COMMITANDACTIVATE" is a typo that should read "qp.getType() == Leader.INFORMANDACTIVATE".
> Assigning to Alexander for now since this is part of ZOOKEEPER-107.
--
This message was sent by Atlassian JIRA
(v6.2#6252)