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.

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

BenchReadThroughputLatency support config the way of gen ledger path. #4219

Conversation

horizonzy
Copy link
Member

Motivation

In BenchReadThroughputLatency, it generates the ledger zk node path using
String.format("/ledgers/L%010d", ledger.get());

But if the user uses HierarchicalLedgerManager, LegacyHierarchicalLedgerManager, or LongHierarchicalLedgerManager, the ledger zk node path is not the same as the way in the BenchReadThroughputLatency.

So we need support config the genLedgerWay to match the custom LedgerManager.

@@ -153,6 +154,9 @@ public static void main(String[] args) throws Exception {
Options options = new Options();
options.addOption("ledger", true, "Ledger to read. If empty, read all ledgers which come available. "
+ " Cannot be used with -listen");
//How to generate ledger id
options.addOption("genLedgerWay", true, "The way of generating ledgerId. "
Copy link
Contributor

Choose a reason for hiding this comment

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

Use ledgerManagerType?

# @Deprecated - `ledgerManagerType` is deprecated in favor of using `ledgerManagerFactoryClass`.
# ledgerManagerType=hierarchical

Copy link
Member Author

Choose a reason for hiding this comment

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

ledgerManagerType

Make sense.

@hangc0276 hangc0276 merged commit 7576f22 into apache:master Mar 1, 2024
20 checks passed
Ghatage pushed a commit to sijie/bookkeeper that referenced this pull request Jul 12, 2024
…apache#4219)

### Motivation
In BenchReadThroughputLatency, it generates the ledger zk node path using 
`String.format("/ledgers/L%010d", ledger.get());`

But if the user uses `HierarchicalLedgerManager`, `LegacyHierarchicalLedgerManager`, or `LongHierarchicalLedgerManager`, the ledger zk node path is not the same as the way in the BenchReadThroughputLatency.

So we need support config the `genLedgerWay` to match the custom LedgerManager.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants