[jira] [Commented] (BOOKKEEPER-604) Ledger storage can log an exception if GC happens concurrently.

[ https://issues.apache.org/jira/browse/BOOKKEEPER-604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718026#comment-13718026 ] Uma Maheswara Rao G commented on BOOKKEEPER-604: Nits: {code} try

[jira] [Updated] (BOOKKEEPER-604) Ledger storage can log an exception if GC happens concurrently.

[ https://issues.apache.org/jira/browse/BOOKKEEPER-604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated BOOKKEEPER-604: -- Attachment: 0001-BOOKKEEPER-604-Ledger-storage-can-log-an-exception-i.patch Fixed

[jira] [Commented] (BOOKKEEPER-648) BasicJMSTest failed

[ https://issues.apache.org/jira/browse/BOOKKEEPER-648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718267#comment-13718267 ] Mridul Muralidharan commented on BOOKKEEPER-648: I was not able to

[jira] [Commented] (BOOKKEEPER-625) On OutOfMemoryError in NIOServerFactory thread bookie should shutdown

[ https://issues.apache.org/jira/browse/BOOKKEEPER-625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718291#comment-13718291 ] Ivan Kelly commented on BOOKKEEPER-625: --- Great. Patch is good. +1. Committing.

[jira] [Updated] (BOOKKEEPER-654) Bookkeeper client operations are allowed even after its closure, bk#close()

[ https://issues.apache.org/jira/browse/BOOKKEEPER-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated BOOKKEEPER-654: -- Fix Version/s: 4.2.2 Bookkeeper client operations are allowed even after its closure,

[jira] [Updated] (BOOKKEEPER-649) Race condition in sync ZKUtils.createFullPathOptimistic()

[ https://issues.apache.org/jira/browse/BOOKKEEPER-649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated BOOKKEEPER-649: -- Fix Version/s: 4.2.2 Race condition in sync ZKUtils.createFullPathOptimistic()

[jira] [Commented] (BOOKKEEPER-648) BasicJMSTest failed

[ https://issues.apache.org/jira/browse/BOOKKEEPER-648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718353#comment-13718353 ] Flavio Junqueira commented on BOOKKEEPER-648: - have you tried running in a

[jira] [Commented] (BOOKKEEPER-648) BasicJMSTest failed

[ https://issues.apache.org/jira/browse/BOOKKEEPER-648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718365#comment-13718365 ] Mridul Muralidharan commented on BOOKKEEPER-648: I tried it 3 times -

[jira] [Commented] (BOOKKEEPER-648) BasicJMSTest failed

[ https://issues.apache.org/jira/browse/BOOKKEEPER-648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718369#comment-13718369 ] Mridul Muralidharan commented on BOOKKEEPER-648: I tried it 3 times -

[jira] [Updated] (BOOKKEEPER-632) AutoRecovery should consider read only bookies

[ https://issues.apache.org/jira/browse/BOOKKEEPER-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay updated BOOKKEEPER-632: - Attachment: BOOKKEEPER-632.patch Attaching the patch for trail space removal.

[jira] [Created] (BOOKKEEPER-660) Logs too noisy on NIOServerFactory when client drops a connection

Ivan Kelly created BOOKKEEPER-660: - Summary: Logs too noisy on NIOServerFactory when client drops a connection Key: BOOKKEEPER-660 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-660 Project:

[jira] [Commented] (BOOKKEEPER-632) AutoRecovery should consider read only bookies

[ https://issues.apache.org/jira/browse/BOOKKEEPER-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718381#comment-13718381 ] Ivan Kelly commented on BOOKKEEPER-632: --- This doesn't address the other issue

[jira] [Commented] (BOOKKEEPER-642) Bookie returns incorrect exitcode, ExitCode.ZK_REG_FAIL is getting overridden

[ https://issues.apache.org/jira/browse/BOOKKEEPER-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718403#comment-13718403 ] Ivan Kelly commented on BOOKKEEPER-642: --- Ah, as the bookie hasn't started at

[jira] [Updated] (BOOKKEEPER-642) Bookie returns incorrect exitcode, ExitCode.ZK_REG_FAIL is getting overridden

[ https://issues.apache.org/jira/browse/BOOKKEEPER-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated BOOKKEEPER-642: -- Fix Version/s: 4.2.2 Bookie returns incorrect exitcode, ExitCode.ZK_REG_FAIL is

[jira] [Commented] (BOOKKEEPER-632) AutoRecovery should consider read only bookies

[ https://issues.apache.org/jira/browse/BOOKKEEPER-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718424#comment-13718424 ] Vinay commented on BOOKKEEPER-632: -- {quote}he patch adds a new public api to read the

[jira] [Commented] (BOOKKEEPER-632) AutoRecovery should consider read only bookies

[ https://issues.apache.org/jira/browse/BOOKKEEPER-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718433#comment-13718433 ] Ivan Kelly commented on BOOKKEEPER-632: --- InetSocketAddress can easily be

[jira] [Commented] (BOOKKEEPER-632) AutoRecovery should consider read only bookies

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

[jira] [Commented] (BOOKKEEPER-632) AutoRecovery should consider read only bookies

[ https://issues.apache.org/jira/browse/BOOKKEEPER-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718485#comment-13718485 ] Vinay commented on BOOKKEEPER-632: -- One more doubt, In Auditor#checkAllLedgers(),

[jira] [Updated] (BOOKKEEPER-632) AutoRecovery should consider read only bookies

[ https://issues.apache.org/jira/browse/BOOKKEEPER-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay updated BOOKKEEPER-632: - Attachment: BOOKKEEPER-632.patch Attached the updated patch. Used the BookKeeperAdmin apis

[jira] [Commented] (BOOKKEEPER-632) AutoRecovery should consider read only bookies

[ https://issues.apache.org/jira/browse/BOOKKEEPER-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718541#comment-13718541 ] Ivan Kelly commented on BOOKKEEPER-632: --- Regarding, #checkAllLedgers(), I don't

[jira] [Updated] (BOOKKEEPER-660) Logs too noisy on NIOServerFactory when client drops a connection

[ https://issues.apache.org/jira/browse/BOOKKEEPER-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Merli updated BOOKKEEPER-660: Attachment: BOOKKEEPER-660.diff Logs too noisy on NIOServerFactory when client

[jira] [Commented] (BOOKKEEPER-660) Logs too noisy on NIOServerFactory when client drops a connection

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

[jira] [Commented] (BOOKKEEPER-654) Bookkeeper client operations are allowed even after its closure, bk#close()

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

[jira] [Commented] (BOOKKEEPER-658) ledger cache refactor

[ https://issues.apache.org/jira/browse/BOOKKEEPER-658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13719225#comment-13719225 ] Sijie Guo commented on BOOKKEEPER-658: -- this patch is just simply moving code

[jira] [Commented] (BOOKKEEPER-654) Bookkeeper client operations are allowed even after its closure, bk#close()

[ https://issues.apache.org/jira/browse/BOOKKEEPER-654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13719262#comment-13719262 ] Sijie Guo commented on BOOKKEEPER-654: -- thanks for updating. 1. in

[jira] [Updated] (BOOKKEEPER-604) Ledger storage can log an exception if GC happens concurrently.

[ https://issues.apache.org/jira/browse/BOOKKEEPER-604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sijie Guo updated BOOKKEEPER-604: - Attachment: BOOKKEEPER-604.diff attach a patch - obtain fileinfo before flushing - pass