[
https://issues.apache.org/jira/browse/BOOKKEEPER-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13401989#comment-13401989
]
Sijie Guo commented on BOOKKEEPER-314:
--
this cyclic reference issue is maven2
[
https://issues.apache.org/jira/browse/BOOKKEEPER-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13401993#comment-13401993
]
Ivan Kelly commented on BOOKKEEPER-303:
---
Because to generate during build, it
Hi Uma, We have had a related issue in BOOKKEEPER-112 and there is a doc there
describing how we deal with it. It might help to give it a look.
-Flavio
On Jun 27, 2012, at 7:06 AM, Uma Maheswara Rao G wrote:
Right. But Current Replication process considered for OPEN ledgers also. So,
Ledger
[
https://issues.apache.org/jira/browse/BOOKKEEPER-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402073#comment-13402073
]
Sijie Guo commented on BOOKKEEPER-303:
--
OK. thanks Ivan for explanation. it makes
[
https://issues.apache.org/jira/browse/BOOKKEEPER-311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402165#comment-13402165
]
Mridul Muralidharan commented on BOOKKEEPER-311:
bq. Also, it would
See https://builds.apache.org/job/bookkeeper-trunk/579/
--
[...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
AU
[
https://issues.apache.org/jira/browse/BOOKKEEPER-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402184#comment-13402184
]
Mridul Muralidharan commented on BOOKKEEPER-321:
Currently, the
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
[
https://issues.apache.org/jira/browse/BOOKKEEPER-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402240#comment-13402240
]
Hudson commented on BOOKKEEPER-303:
---
Integrated in bookkeeper-trunk #580 (See
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
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
[
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
---
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
[
https://issues.apache.org/jira/browse/BOOKKEEPER-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402773#comment-13402773
]
Sijie Guo commented on BOOKKEEPER-310:
--
{quote}
This was observed as part of a
14 matches
Mail list logo
