[
https://issues.apache.org/jira/browse/ZOOKEEPER-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13637957#comment-13637957
]
Flavio Junqueira edited comment on ZOOKEEPER-1694 at 4/22/13 12:17 PM:
-----------------------------------------------------------------------
The point is that we shouldn't treat the same issue in two separate jiras. We
already have a patch in ZOOKEEPER-1324 that has been committed to branch 3.4. I
had committed it to trunk, but we reverted because of a conflict with a much
larger patch, which was about to get in (ZOOKEEPER-107). My suggestion is that
you have a look at what has been done in ZOOKEEPER-1324 and confirm that it is
the same issue. If it is, we should close this jira as duplicate. Also, please
feel free to comment to ZOOKEEPER-1324, feedback is always appreciated.
was (Author: fpj):
The point is that we shouldn't treat the same issue in two separate jiras.
We already have a patch in ZOOKEEPER-1324 that has been committed to branch
3.4. I had committed it to trunk, but we reverted because of conflict with a
much larger patch, which was about to get in (ZOOKEEPER-107). My suggestion is
that you have a look at what has been done in ZOOKEEPER-1324 and confirm that
it is the same issue. If it is, we should close this jira as duplicate. Also,
please feel free to comment to ZOOKEEPER-1324, feedback is always appreciated.
> ZooKeeper Leader sends a repeated NEWLEADER quorum packet to followers
> ----------------------------------------------------------------------
>
> Key: ZOOKEEPER-1694
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1694
> Project: ZooKeeper
> Issue Type: Bug
> Components: quorum
> Affects Versions: 3.5.0, 3.4.5
> Environment: Windows, Linux, MacOSX
> Reporter: Germán Blanco
> Priority: Minor
> Labels: patch
> Fix For: 3.5.0
>
> Attachments: ZOOKEEPER-1694.patch
>
>
> This is at least what it seems in the logs. This also seems to cause a second
> snapshot in the follower.
--
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
