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

Update BK to 4.3.1.60-yahoo #302

Merged
merged 1 commit into from
Mar 23, 2017
Merged

Update BK to 4.3.1.60-yahoo #302

merged 1 commit into from
Mar 23, 2017

Conversation

merlimat
Copy link
Contributor

@merlimat merlimat commented Mar 21, 2017 •
edited
Loading

Changes includes:

  • Fixes for 64bit ledger ids
  • Fixed memory leak on read-only bookies
  • Fixed datasketches metric provider concurrency issue

Fixes #258

@merlimat
Update BK to 4.3.1.60-yahoo
3f201d4 
Changes includes:
  * Fixes for 64bit ledger ids
  * Fixed memory leak on read-only bookies
  * Fixed datasketches metric provider concurrency issue
@merlimat merlimat added the type/bug The PR fixed a bug or issue reported a bug label Mar 21, 2017
@merlimat merlimat added this to the 1.17 milestone Mar 21, 2017
@merlimat merlimat self-assigned this Mar 21, 2017
rdhabalia
rdhabalia approved these changes Mar 23, 2017
View reviewed changes
Copy link
Contributor

@rdhabalia rdhabalia left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@merlimat merlimat merged commit 8dd9ef4 into apache:master Mar 23, 2017
@sschepens
Copy link
Contributor

@merlimat @rdhabalia is it safe to deploy this in production? I worry about the ledger id generation, seems to have changed a lot

@merlimat
Copy link
Contributor Author

In theory the ledger id generation changes should be pretty safe and backward compatible (can rollback to previous release in case of issues).
In practice, to be safe you should wait until the official 1.17 release (should not too far away, the last big change is the load manager revamping). The release is guaranteed to go through a more rigorous regression test suite and system/stress test that runs continuously.

@xiaotongwang1 xiaotongwang1 mentioned this pull request Aug 4, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@rdhabalia rdhabalia rdhabalia approved these changes

Assignees

@merlimat merlimat

Labels
type/bug The PR fixed a bug or issue reported a bug
Projects
None yet
Milestone
1.17
Development

Successfully merging this pull request may close these issues.
3 participants
@merlimat @sschepens @rdhabalia