Yong Zhang
But there are still metadata operations before deferring it. If you don't give them a backoff, then the metadata service will suffer huge requests in a short time. And deferLedgerLockRelease...
Close this since it is open for a long time without any updates. Feel free to reopen it if you want to continue
You might need to clean up the `pvc` and `pv`. Use `k delete pvc --all -n pulsar` to clean up and then start the cluster.
The reason that `Invalid cookie` looks like you clean up the data directory but not reinitialize the cluster
Yes. It should fix the issue.
``` Error: Errors: Error: org.apache.bookkeeper.server.http.TestHttpService.testBookieReadOnlyState Error: Run 1: TestHttpService.testBookieReadOnlyState:983 » NullPointer Error: Run 2: TestHttpService.testBookieReadOnlyState:983 » NullPointer Error: Run 3: TestHttpService.testBookieReadOnlyState:983 » NullPointer ``` Seems related to this change
Yeah. Please go ahead.
Overall looks good to me. Could you please add a test which the request threshold is different from the configured threshold
We added more limitations on creating a ledger. May introduce some break changes? Remove the minor release tag.
@balticore According to the error, do you have the `scope` in the client credential file?