[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-tabpanel&focusedCommentId=13402773#comment-13402773 ] Sijie Guo commented on BOOKKEEPER-310: -- {quote} This was observed as part of a te

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13402708#comment-13402708 ] Sijie Guo commented on BOOKKEEPER-309: -- {quote} But JMS assumes some basic functi

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13402706#comment-13402706 ] Sijie Guo commented on BOOKKEEPER-309: -- {quote} But JMS assumes some basic functi

Re: Race condition between LedgerChecker and Ensemble reformation from client

This discussion made me wonder about the relation between the bookie recovery tool and the auto-recovery feature. Does the latter replace the former? Also, if they share code, we want to avoid duplication, yes? -Flavio On Jun 27, 2012, at 4:17 PM, Uma Maheswara Rao G wrote: > Thanks Ivan and F

Re: Review Request: BOOKKEEPER-250: Need a ledger manager like interface to manage metadata operations in Hedwig

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/5101/#review8653 --- I don't think it will happen that a user will want a metadata manager

[jira] [Updated] (BOOKKEEPER-322) New protobufs generates findbugs errors

[ https://issues.apache.org/jira/browse/BOOKKEEPER-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated BOOKKEEPER-322: -- Attachment: BOOKKEEPER-322.diff > New protobufs generates findbugs errors > ---

RE: Race condition between LedgerChecker and Ensemble reformation from client

Thanks Ivan and Flavio. I got the point. And Yes, I have seen this with below mentioned steps. Infact, I used only very lower part of the code from BKAdmin.(Only fragment replication part) That will not have this prventing steps because that is only responsible for fragment. Need to build

[jira] [Created] (BOOKKEEPER-322) New protobufs generates findbugs errors

Ivan Kelly created BOOKKEEPER-322: - Summary: New protobufs generates findbugs errors Key: BOOKKEEPER-322 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-322 Project: Bookkeeper Issue Ty

[jira] [Commented] (BOOKKEEPER-303) LedgerMetadata should serialized using protobufs

[ https://issues.apache.org/jira/browse/BOOKKEEPER-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13402240#comment-13402240 ] Hudson commented on BOOKKEEPER-303: --- Integrated in bookkeeper-trunk #580 (See [http

Build failed in Jenkins: bookkeeper-trunk #580

See Changes: [ivank] BOOKKEEPER-303: LedgerMetadata should serialized using protobufs (ivank) -- [...truncated 351 lines...] A bookkeeper-server/src/main/resources/LICENSE.bin.txt A

Re: Race condition between LedgerChecker and Ensemble reformation from client

Hi Uma, Check the whole paragraph: Consequently, we restrict the recovery tool to only perform changes to the metadata when the ledger is closed or when the ledger writer has detected the bookie crash, has replaced it, and reflected the change in the metadata. It is not only for closed ledgers.

Re: Race condition between LedgerChecker and Ensemble reformation from client

Hi Uma, Are you actually seeing this happen? In BookKeeperAdmin we takes steps to explicitly stop this from happening. If we try to recover a ledger which is open, one of two things happen. 1. If the failed bookie is not in the last ensemble of the ledger, recover as normal. 2. If the failed bo

[jira] [Commented] (BOOKKEEPER-321) Message Filter Support

[ https://issues.apache.org/jira/browse/BOOKKEEPER-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13402184#comment-13402184 ] Mridul Muralidharan commented on BOOKKEEPER-321: Currently, the messag

Build failed in Jenkins: bookkeeper-trunk #579

See -- [...truncated 347 lines...] A bookkeeper-server/src/main/resources/NOTICE.bin.txt A bookkeeper-server/src/main/resources/LICENSE.bin.txt A bookkeeper-server/bin AUbo

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13402165#comment-13402165 ] Mridul Muralidharan commented on BOOKKEEPER-311: bq. Also, it would b

[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-tabpanel&focusedCommentId=13402161#comment-13402161 ] Mridul Muralidharan commented on BOOKKEEPER-310: bq. could you provide

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13402158#comment-13402158 ] Mridul Muralidharan commented on BOOKKEEPER-309: >From what I understa

RE: Race condition between LedgerChecker and Ensemble reformation from client

Thanks a lot, Flavio for reference. Here we are making use of RecoveryTool code. Also I have seen in the doc saying: Consequently, we restrict the recovery tool to only perform changes to the metadata when the ledger is closed In BOOKKEEPER-112 , Client is trying to handle this metad

[jira] [Created] (BOOKKEEPER-321) Message Filter Support

Sijie Guo created BOOKKEEPER-321: Summary: Message Filter Support Key: BOOKKEEPER-321 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-321 Project: Bookkeeper Issue Type: Improvement

[jira] [Commented] (BOOKKEEPER-303) LedgerMetadata should serialized using protobufs

[ https://issues.apache.org/jira/browse/BOOKKEEPER-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13402073#comment-13402073 ] Sijie Guo commented on BOOKKEEPER-303: -- OK. thanks Ivan for explanation. it makes

[jira] [Commented] (BOOKKEEPER-303) LedgerMetadata should serialized using protobufs

[ https://issues.apache.org/jira/browse/BOOKKEEPER-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13402052#comment-13402052 ] Ivan Kelly commented on BOOKKEEPER-303: --- For the C++ client, you need the protob

[jira] [Commented] (BOOKKEEPER-303) LedgerMetadata should serialized using protobufs

[ https://issues.apache.org/jira/browse/BOOKKEEPER-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13402042#comment-13402042 ] Sijie Guo commented on BOOKKEEPER-303: -- OK. I got the idea. but the generated fil