[jira] [Resolved] (BOOKKEEPER-519) Ensure all threads in BookKeeper/Hedwig have meaningful names

[ https://issues.apache.org/jira/browse/BOOKKEEPER-519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sijie Guo resolved BOOKKEEPER-519. -- Resolution: Won't Fix grep the code base now, it seems that all the threads are already

[jira] [Updated] (BOOKKEEPER-661) Turn readonly back to writable if spaces are reclaimed.

[ https://issues.apache.org/jira/browse/BOOKKEEPER-661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sijie Guo updated BOOKKEEPER-661: - Attachment: BOOKKEEPER-661_662.diff attach a patch with BOOKKEEPER-662 changes for precommit

[jira] [Commented] (BOOKKEEPER-662) Major GC should kick in immediately if remaining space reaches a warning threshold

[ https://issues.apache.org/jira/browse/BOOKKEEPER-662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13871807#comment-13871807 ] Hadoop QA commented on BOOKKEEPER-662: -- Testing JIRA BOOKKEEPER-662 Patch

[jira] [Commented] (BOOKKEEPER-510) LedgerRecoveryOp updates metadata before it needs to

[ https://issues.apache.org/jira/browse/BOOKKEEPER-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13871815#comment-13871815 ] Sijie Guo commented on BOOKKEEPER-510: -- [~ikelly] I still don't understand. This

[jira] [Comment Edited] (BOOKKEEPER-510) LedgerRecoveryOp updates metadata before it needs to

[ https://issues.apache.org/jira/browse/BOOKKEEPER-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13871815#comment-13871815 ] Sijie Guo edited comment on BOOKKEEPER-510 at 1/15/14 8:48 AM:

[jira] [Commented] (BOOKKEEPER-710) OpenLedgerNoRecovery should watch ensemble change.

[ https://issues.apache.org/jira/browse/BOOKKEEPER-710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13871950#comment-13871950 ] Ivan Kelly commented on BOOKKEEPER-710: --- How do you communicate the change in

[jira] [Updated] (BOOKKEEPER-708) Shade protobuf library to avoid incompatible versions

[ https://issues.apache.org/jira/browse/BOOKKEEPER-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated BOOKKEEPER-708: -- Attachment: 0001-BOOKKEEPER-708-Shade-protobuf-library-to-avoid-incom.patch Shade

[jira] [Commented] (BOOKKEEPER-708) Shade protobuf library to avoid incompatible versions

[ https://issues.apache.org/jira/browse/BOOKKEEPER-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13872082#comment-13872082 ] Ivan Kelly commented on BOOKKEEPER-708: --- I've set createDependencyReducedPom to

[jira] [Commented] (BOOKKEEPER-708) Shade protobuf library to avoid incompatible versions

[ https://issues.apache.org/jira/browse/BOOKKEEPER-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13872123#comment-13872123 ] Hadoop QA commented on BOOKKEEPER-708: -- Testing JIRA BOOKKEEPER-708 Patch

Build failed in Jenkins: bookkeeper-trunk #509

See https://builds.apache.org/job/bookkeeper-trunk/509/changes Changes: [ivank] BOOKKEEPER-662: Major GC should kick in immediately if remaining space reaches a warning threshold (sijie via ivank) -- [...truncated 449 lines...] [INFO] Compiling 6 source

[jira] [Commented] (BOOKKEEPER-662) Major GC should kick in immediately if remaining space reaches a warning threshold

[ https://issues.apache.org/jira/browse/BOOKKEEPER-662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13872166#comment-13872166 ] Hudson commented on BOOKKEEPER-662: --- FAILURE: Integrated in bookkeeper-trunk #509

[jira] [Commented] (BOOKKEEPER-662) Major GC should kick in immediately if remaining space reaches a warning threshold

[ https://issues.apache.org/jira/browse/BOOKKEEPER-662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13872171#comment-13872171 ] Flavio Junqueira commented on BOOKKEEPER-662: - It is possibly not related

Re: hedwig-client-jms build failing

This is the test case failing for me: Failed tests: testSimpleChat(org.apache.hedwig.jms.BasicJMSTest) If you want I can create a jira and post logs. -Flavio Flavio: What's the error? Compilation error? or Test error? Could you send more info? - Sijie On Tue, Jan 14, 2014 at

[jira] [Commented] (BOOKKEEPER-662) Major GC should kick in immediately if remaining space reaches a warning threshold

[ https://issues.apache.org/jira/browse/BOOKKEEPER-662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13872177#comment-13872177 ] Ivan Kelly commented on BOOKKEEPER-662: --- Probably unrelated. That test has a

[jira] [Created] (BOOKKEEPER-718) AuditorLedgerCheckerTest is flakey

Ivan Kelly created BOOKKEEPER-718: - Summary: AuditorLedgerCheckerTest is flakey Key: BOOKKEEPER-718 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-718 Project: Bookkeeper Issue Type:

[jira] [Updated] (BOOKKEEPER-718) AuditorLedgerCheckerTest is flakey

[ https://issues.apache.org/jira/browse/BOOKKEEPER-718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated BOOKKEEPER-718: -- Attachment: error509.txt error505.txt AuditorLedgerCheckerTest is flakey

[jira] [Reopened] (BOOKKEEPER-661) Turn readonly back to writable if spaces are reclaimed.

[ https://issues.apache.org/jira/browse/BOOKKEEPER-661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sijie Guo reopened BOOKKEEPER-661: -- not sure why this was resolved. :( Turn readonly back to writable if spaces are reclaimed.