[
https://issues.apache.org/jira/browse/BOOKKEEPER-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiannan Wang updated BOOKKEEPER-438:
Attachment: BOOKKEEPER-438.patch
Add ledger id generation interface
[
https://issues.apache.org/jira/browse/BOOKKEEPER-438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13555979#comment-13555979
]
Hadoop QA commented on BOOKKEEPER-438:
--
Testing JIRA BOOKKEEPER-438
Patch
[
https://issues.apache.org/jira/browse/BOOKKEEPER-438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13555988#comment-13555988
]
Jiannan Wang commented on BOOKKEEPER-438:
-
Cancel patch, since Sijie has two
[
https://issues.apache.org/jira/browse/BOOKKEEPER-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiannan Wang updated BOOKKEEPER-438:
Attachment: BOOKKEEPER-438.patch
Attach new patch by sijie's comment
[
https://issues.apache.org/jira/browse/BOOKKEEPER-438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13556029#comment-13556029
]
Hadoop QA commented on BOOKKEEPER-438:
--
Testing JIRA BOOKKEEPER-438
Patch
[
https://issues.apache.org/jira/browse/BOOKKEEPER-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiannan Wang updated BOOKKEEPER-438:
Attachment: BOOKKEEPER-438.patch
Minor change: rename LedgerExistException should also
[
https://issues.apache.org/jira/browse/BOOKKEEPER-438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13556078#comment-13556078
]
Hadoop QA commented on BOOKKEEPER-438:
--
Testing JIRA BOOKKEEPER-438
Patch
WC got a normal I/O, entering ensemble change logic. But it could not do
ensemble change, since ledger state is already changed from OPEN to
IN_RECOVERY. so it would fail. If it doesn't stop and fail, it is a bug for
fencing, right? Please keep in mind, fencing is guarantee by bother
metadata
Hello all,
Currently, the ledger id generation is implemented with zookeeper
(persist-/ephemeral-) sequential node to make a global unique id. In code
detail,
- FlatLedgerManager requires a write on zookeeper
- HierarchicalLedgerManager and MSLedgerManagerFactory use same approach
Good job, Ivan. We all expect for this release and you did a great jobs on
it.
The code runs very well on my dev box, I'll merge all of changes into our
branch these two days.
Regards,
Jiannan
On 1/15/13 1:35 AM, Ivan Kelly iv...@apache.org wrote:
This is the first release candidate for Apache
As I pointed, the style 'create a ledger and record the ledger id in some
other places' is bad, especially changing ledger would cause 2 metadata
writes and it is in the publish path, which caused latency spike (the
latency spike depends on the two metadata writes latency). The reason why I
11 matches
Mail list logo