[jira] [Updated] (ZOOKEEPER-1489) Data loss after truncate on transaction log

[ https://issues.apache.org/jira/browse/ZOOKEEPER-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-1489: Attachment: ZOOKEEPER-1489_br34.patch ZOOKEEPER-1489_br33.patch

[jira] [Commented] (ZOOKEEPER-1489) Data loss after truncate on transaction log

[ https://issues.apache.org/jira/browse/ZOOKEEPER-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13412548#comment-13412548 ] Patrick Hunt commented on ZOOKEEPER-1489: - Christian no worries at all. I

[jira] [Updated] (ZOOKEEPER-1489) Data loss after truncate on transaction log

[ https://issues.apache.org/jira/browse/ZOOKEEPER-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-1489: Attachment: ZOOKEEPER-1489.patch This update adds more logging, I also believe it

[jira] [Commented] (ZOOKEEPER-1489) Data loss after truncate on transaction log

[ https://issues.apache.org/jira/browse/ZOOKEEPER-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13412554#comment-13412554 ] Patrick Hunt commented on ZOOKEEPER-1489: - I also verified that the latest

[jira] [Commented] (ZOOKEEPER-1453) corrupted logs may not be correctly identified by FileTxnIterator

[ https://issues.apache.org/jira/browse/ZOOKEEPER-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13412560#comment-13412560 ] Patrick Hunt commented on ZOOKEEPER-1453: - Hi Bill. bq. I am guessing that

[jira] [Commented] (ZOOKEEPER-1489) Data loss after truncate on transaction log

[ https://issues.apache.org/jira/browse/ZOOKEEPER-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13412566#comment-13412566 ] Hadoop QA commented on ZOOKEEPER-1489: -- +1 overall. Here are the results of

Success: ZOOKEEPER-1489 PreCommit Build #1136

Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-1489 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1136/ ### ## LAST 60 LINES OF THE CONSOLE ###

[jira] [Updated] (ZOOKEEPER-1497) Allow server-side SASL login with JAAS configuration to be programmatically set (rather than only by reading JAAS configuration file)

[ https://issues.apache.org/jira/browse/ZOOKEEPER-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-1497: Affects Version/s: (was: 3.3.5) 3.5.0 Allow

Success: ZOOKEEPER-1489 PreCommit Build #1137

Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-1489 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1137/ ### ## LAST 60 LINES OF THE CONSOLE ###

[jira] [Commented] (ZOOKEEPER-1489) Data loss after truncate on transaction log

[ https://issues.apache.org/jira/browse/ZOOKEEPER-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13412581#comment-13412581 ] Hadoop QA commented on ZOOKEEPER-1489: -- +1 overall. Here are the results of

[jira] [Updated] (ZOOKEEPER-1496) Ephemeral node not getting cleared even after client has exited

[ https://issues.apache.org/jira/browse/ZOOKEEPER-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh R updated ZOOKEEPER-1496: Attachment: ZOOKEEPER-1496.2.patch Ephemeral node not getting cleared even after client

Success: ZOOKEEPER-1496 PreCommit Build #1138

Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-1496 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1138/ ### ## LAST 60 LINES OF THE CONSOLE ###

[jira] [Commented] (ZOOKEEPER-1496) Ephemeral node not getting cleared even after client has exited

[ https://issues.apache.org/jira/browse/ZOOKEEPER-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13412655#comment-13412655 ] Hadoop QA commented on ZOOKEEPER-1496: -- +1 overall. Here are the results of

[jira] [Commented] (ZOOKEEPER-1496) Ephemeral node not getting cleared even after client has exited

[ https://issues.apache.org/jira/browse/ZOOKEEPER-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13412663#comment-13412663 ] Rakesh R commented on ZOOKEEPER-1496: - Attached the patch with test case. Please

[jira] [Updated] (ZOOKEEPER-1496) Ephemeral node not getting cleared even after client has exited

[ https://issues.apache.org/jira/browse/ZOOKEEPER-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh R updated ZOOKEEPER-1496: Affects Version/s: 3.4.3 Ephemeral node not getting cleared even after client has exited

[jira] [Updated] (ZOOKEEPER-1219) LeaderElectionSupport recipe is unnecessarily dispatching the READY_START event even if the ELECTED node stopped/expired simultaneously.

[ https://issues.apache.org/jira/browse/ZOOKEEPER-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh R updated ZOOKEEPER-1219: Assignee: (was: Rakesh R) LeaderElectionSupport recipe is unnecessarily dispatching

[jira] [Updated] (ZOOKEEPER-1209) LeaderElection recipe doesn't handle the split-brain issue, n/w disconnection can bring both the client nodes to be in ELECTED

[ https://issues.apache.org/jira/browse/ZOOKEEPER-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh R updated ZOOKEEPER-1209: Assignee: (was: Rakesh R) LeaderElection recipe doesn't handle the split-brain issue,

[jira] [Updated] (ZOOKEEPER-1225) Successive invocation of LeaderElectionSupport.start() will bring the ELECTED node to READY and cause no one in ELECTED state.

[ https://issues.apache.org/jira/browse/ZOOKEEPER-1225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh R updated ZOOKEEPER-1225: Assignee: (was: Rakesh R) Successive invocation of LeaderElectionSupport.start() will

Re: 3.3.6 and 3.4.4 releases

We've made good progress. 1489 tests are now passing consistently and the patch is about to be committed, which means that 3.3.6 is unblocked. I'd like to get Michi's patch in, it's the only other PA remaining on 3.3.6, can someone review this asap?

[jira] [Updated] (ZOOKEEPER-1478) Small bug in QuorumTest.testFollowersStartAfterLeader( )

[ https://issues.apache.org/jira/browse/ZOOKEEPER-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-1478: Fix Version/s: 3.5.0 3.4.4 Small bug in

[jira] [Commented] (ZOOKEEPER-1489) Data loss after truncate on transaction log

[ https://issues.apache.org/jira/browse/ZOOKEEPER-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13413045#comment-13413045 ] Camille Fournier commented on ZOOKEEPER-1489: - +1 looks good

[jira] [Commented] (ZOOKEEPER-1508) Reliable standalone mode through redundant databases

[ https://issues.apache.org/jira/browse/ZOOKEEPER-1508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13413270#comment-13413270 ] Flavio Junqueira commented on ZOOKEEPER-1508: - bq. When you say it

[jira] [Commented] (ZOOKEEPER-1477) Test failures with Java 7 on Mac OS X

[ https://issues.apache.org/jira/browse/ZOOKEEPER-1477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13413501#comment-13413501 ] Diego Oliveira commented on ZOOKEEPER-1477: --- I did some logging to look up

[jira] [Updated] (BOOKKEEPER-337) Add entry fails with MetadataVersionException when last ensemble has morethan one bookie failures

[ https://issues.apache.org/jira/browse/BOOKKEEPER-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sijie Guo updated BOOKKEEPER-337: - Attachment: BOOKKEEPER-337-try.patch yup, ur right. the confliction occurred due to there

[jira] [Created] (BOOKKEEPER-338) Create Version.NEW and Version.ANY static instances of Version so that were not passing around nulls

Ivan Kelly created BOOKKEEPER-338: - Summary: Create Version.NEW and Version.ANY static instances of Version so that were not passing around nulls Key: BOOKKEEPER-338 URL:

[jira] [Commented] (BOOKKEEPER-259) Create a topic manager using versioned write for leader election

[ https://issues.apache.org/jira/browse/BOOKKEEPER-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13412681#comment-13412681 ] Ivan Kelly commented on BOOKKEEPER-259: --- Looks good. I have a couple of

[jira] [Commented] (BOOKKEEPER-220) Managed Ledger proposal

[ https://issues.apache.org/jira/browse/BOOKKEEPER-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13412835#comment-13412835 ] Ivan Kelly commented on BOOKKEEPER-220: --- re: protobuf It would be much easier to

[jira] [Commented] (BOOKKEEPER-326) DeadLock during ledger recovery

[ https://issues.apache.org/jira/browse/BOOKKEEPER-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13412897#comment-13412897 ] Ivan Kelly commented on BOOKKEEPER-326: --- I don't think the problem here is that

[jira] [Commented] (BOOKKEEPER-220) Managed Ledger proposal

[ https://issues.apache.org/jira/browse/BOOKKEEPER-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13412902#comment-13412902 ] Matteo Merli commented on BOOKKEEPER-220: - Ok, I thought it was meant to be

[jira] [Commented] (BOOKKEEPER-220) Managed Ledger proposal

[ https://issues.apache.org/jira/browse/BOOKKEEPER-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13412907#comment-13412907 ] Matteo Merli commented on BOOKKEEPER-220: - On a slightly related topic, we've

[jira] [Commented] (BOOKKEEPER-220) Managed Ledger proposal

[ https://issues.apache.org/jira/browse/BOOKKEEPER-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13412961#comment-13412961 ] Ivan Kelly commented on BOOKKEEPER-220: --- Can a client see the same entry from

[jira] [Commented] (BOOKKEEPER-220) Managed Ledger proposal

[ https://issues.apache.org/jira/browse/BOOKKEEPER-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13412993#comment-13412993 ] Matteo Merli commented on BOOKKEEPER-220: - Yes, there will be always the

[jira] [Updated] (BOOKKEEPER-312) Implementation of JMS provider

[ https://issues.apache.org/jira/browse/BOOKKEEPER-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Muralidharan updated BOOKKEEPER-312: --- Attachment: hedwig-client-jms.patch.3 Use custom header definition based

[jira] [Updated] (BOOKKEEPER-311) Changes in hedwig client api to support JMS spec

[ https://issues.apache.org/jira/browse/BOOKKEEPER-311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Muralidharan updated BOOKKEEPER-311: --- Attachment: hedwig-client.patch.3 Removed all optional changes for base

[jira] [Updated] (BOOKKEEPER-310) Changes in hedwig server to support JMS spec

[ https://issues.apache.org/jira/browse/BOOKKEEPER-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Muralidharan updated BOOKKEEPER-310: --- Attachment: hedwig-server.patch.3 Removed all spurious and non essential

[jira] [Updated] (BOOKKEEPER-309) Protocol changes in hedwig to support JMS spec

[ https://issues.apache.org/jira/browse/BOOKKEEPER-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Muralidharan updated BOOKKEEPER-309: --- Attachment: hedwig-protocol.patch.3 Changes to protocol to return seq-id

[jira] [Commented] (BOOKKEEPER-308) Add support for JMS implementation for hedwig

[ https://issues.apache.org/jira/browse/BOOKKEEPER-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13413134#comment-13413134 ] Mridul Muralidharan commented on BOOKKEEPER-308: I have removed all

[jira] [Commented] (BOOKKEEPER-331) Let hedwig support returning message seq id for publish requests.

[ https://issues.apache.org/jira/browse/BOOKKEEPER-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13413171#comment-13413171 ] Mridul Muralidharan commented on BOOKKEEPER-331: As of now, post

[jira] [Commented] (BOOKKEEPER-310) Changes in hedwig server to support JMS spec

[ https://issues.apache.org/jira/browse/BOOKKEEPER-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13413181#comment-13413181 ] Mridul Muralidharan commented on BOOKKEEPER-310: Please note that the

[jira] [Updated] (BOOKKEEPER-311) Changes in hedwig client api to support JMS spec

[ https://issues.apache.org/jira/browse/BOOKKEEPER-311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Muralidharan updated BOOKKEEPER-311: --- Attachment: (was: hedwig-client.patch.3) Changes in hedwig

[jira] [Updated] (BOOKKEEPER-311) Changes in hedwig client api to support JMS spec

[ https://issues.apache.org/jira/browse/BOOKKEEPER-311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Muralidharan updated BOOKKEEPER-311: --- Attachment: hedwig-client.patch.3 Changes in hedwig client api to

[jira] [Commented] (BOOKKEEPER-326) DeadLock during ledger recovery

[ https://issues.apache.org/jira/browse/BOOKKEEPER-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13413492#comment-13413492 ] Rakesh R commented on BOOKKEEPER-326: - @Ivan bq.I don't think the problem here is