[
https://issues.apache.org/jira/browse/BOOKKEEPER-580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13593672#comment-13593672
]
Rakesh R commented on BOOKKEEPER-580:
-------------------------------------
bq.bookkeeper client still write ledger metadata to metadata storage even the
metadata is already closed or undergoing closing. which would cause lots of bad
version metadata update encountering unrecoverable errors in ledger handle.
e.g. NotEnoughtBookiesException
[~hustlmsp] If you could attach the log details, it would be helpful. I'm
interested to know how NotEnoughtBookiesException occuring due to
close/closing. Our existing #close() call is idempotent in nature, isn't it.
Am I missing anything?
> improve close logic
> -------------------
>
> Key: BOOKKEEPER-580
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-580
> Project: Bookkeeper
> Issue Type: Bug
> Components: bookkeeper-client
> Reporter: Sijie Guo
> Assignee: Sijie Guo
> Fix For: 4.3.0
>
> Attachments: BOOKKEEPER-580.diff
>
>
> currently, bookkeeper client still write ledger metadata to metadata storage
> even the metadata is already closed or undergoing closing. which would cause
> lots of bad version metadata update encountering unrecoverable errors in
> ledger handle. e.g. NotEnoughtBookiesException.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
