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

Tune BK auto-recovery settings with respect to the configuration best suited for Pravega specific use-cases #38

Open
pbelgundi opened this issue May 6, 2020 · 0 comments
Open

Tune BK auto-recovery settings with respect to the configuration best suited for Pravega specific use-cases #38

pbelgundi opened this issue May 6, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@pbelgundi
Copy link
Contributor

pbelgundi commented May 6, 2020 •
edited by SrishT
Loading

Description

Ensure the settings related to bookkeeper auto-recovery are fine-tuned to work best with Pravega cluster's use-cases.

Importance

must-have

Location

Moved from pravega-operator: pravega/pravega-operator#235

Suggestions for an improvement

The following are the auto-recovery settings in Bookkeeper which need to be considered:

Auto Recovery Settings

  • autoRecoveryDaemonEnabled
  • digestType
  • passwd
  • enableDigestTypeAutodetection

Placement settings

  • ensemblePlacementPolicy
  • reppDnsResolverClass
  • networkTopologyScriptFileName
  • networkTopologyScriptNumberArgs
  • minNumRacksPerWriteQuorum
  • enforceMinNumRacksPerWriteQuorum

Auditor settings

  • auditorPeriodicBookieCheckInterval
  • auditorPeriodicCheckInterval
  • auditorLedgerVerificationPercentage
  • lostBookieRecoveryDelay
  • storeSystemTimeAsLedgerUnderreplicatedMarkTime

Replication Worker settings

  • rereplicationEntryBatchSize
  • openLedgerRereplicationGracePeriod
  • rwRereplicateBackoffMs
@pbelgundi pbelgundi mentioned this issue May 6, 2020
Closed
@pbelgundi pbelgundi added the enhancement New feature or request label May 6, 2020
@pbelgundi pbelgundi mentioned this issue May 6, 2020
Closed
@SrishT SrishT changed the title Manage BK auto-recovery after Bookkeeper cluster upgrade Tune BK auto-recovery settings with respect to the configuration best suited for Pravega specific use-cases Nov 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@pbelgundi