Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Improve fencing logic #208

Closed
sijie opened this issue Jun 22, 2017 · 0 comments
Closed

Improve fencing logic #208

sijie opened this issue Jun 22, 2017 · 0 comments
Labels
area/client type/bug
Milestone
4.5.0

Comments

@sijie
Copy link
Member

sijie commented Jun 22, 2017

BUG REPORT

  1. Please describe the issue you observed:

  • What did you do?

  • What did you expect to see?

When bookie receive a fence request and couldn't find any writable dirs for the new index file, it will throw exception. This behavior can be improved, because as long as ledger fence request be persisted in Journal, we can say the fence request succeed. It should not depends on the success of flushing new index file.

  • What did you see instead?

Fence failed when bookies are in readonly.
@sijie sijie added this to the 4.5.0 milestone Jun 28, 2017
@sijie sijie closed this as completed in c49621b Jul 17, 2017
sijie added a commit to sijie/bookkeeper that referenced this issue Jan 26, 2018
@sijie
ISSUE apache#207: Support getFirstLogRecord
84ecaa8 
Descriptions of the changes in this PR:

- support getFirstLogRecord

Author: Sijie Guo <sijie@apache.org>

Reviewers: Jia Zhai <None>

This closes apache#208 from sijie/3_get_firstrecord_pr, closes apache#207
@sijie sijie mentioned this issue Apr 4, 2018
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/client type/bug
Projects
None yet
Milestone
4.5.0
Development

No branches or pull requests
1 participant
@sijie