Split read and write orderExecutor

[315157973]

BUG REPORT

Describe the bug

Now the read and write of BookkeeperClient share the same orderExecutor. When cold data is read, it will take a long time. At this time, the read request will be blocked, resulting in the write timeout.

Expected behavior
Thread pools for reading and writing should be separated

[dlg99]

This is done on purpose for writable ledgers.
Read-only ledgers (cold data) don't use OSE. Please take a look at #1792 / #1791

[315157973]

This is done on purpose for writable ledgers. Read-only ledgers (cold data) don't use OSE. Please take a look at #1792 / #1791

Thank you very much for your reply.
When the Ledger is in the Writable state, can we guarantee that the data is not read from disk?
As long as data is read from the disk, when there are many read requests, the read affects the write, resulting in a write timeout