You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@bookkeeper.apache.org by GitBox <gi...@apache.org> on 2022/01/20 03:58:36 UTC

[GitHub] [bookkeeper] 315157973 opened a new issue #3003: Split read and write orderExecutor

315157973 opened a new issue #3003:
URL: https://github.com/apache/bookkeeper/issues/3003


   **BUG REPORT**
   
   ***Describe the bug***
   
   Now the read and write of BookkeeperClient share an 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
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@bookkeeper.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [bookkeeper] dlg99 commented on issue #3003: Split read and write orderExecutor

Posted by GitBox <gi...@apache.org>.
dlg99 commented on issue #3003:
URL: https://github.com/apache/bookkeeper/issues/3003#issuecomment-1039384636


   This is done on purpose for writable ledgers.
   Read-only ledgers (cold data) don't use OSE. Please take a look at https://github.com/apache/bookkeeper/pull/1792 / https://github.com/apache/bookkeeper/issues/1791


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@bookkeeper.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [bookkeeper] 315157973 commented on issue #3003: Split read and write orderExecutor

Posted by GitBox <gi...@apache.org>.
315157973 commented on issue #3003:
URL: https://github.com/apache/bookkeeper/issues/3003#issuecomment-1039898225


   > 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 hard disk, when there are many read requests,  the read affects the write, resulting in a write timeout


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@bookkeeper.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [bookkeeper] dlg99 commented on issue #3003: Split read and write orderExecutor

Posted by GitBox <gi...@apache.org>.
dlg99 commented on issue #3003:
URL: https://github.com/apache/bookkeeper/issues/3003#issuecomment-1039384636


   This is done on purpose for writable ledgers.
   Read-only ledgers (cold data) don't use OSE. Please take a look at https://github.com/apache/bookkeeper/pull/1792 / https://github.com/apache/bookkeeper/issues/1791


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@bookkeeper.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [bookkeeper] 315157973 edited a comment on issue #3003: Split read and write orderExecutor

Posted by GitBox <gi...@apache.org>.
315157973 edited a comment on issue #3003:
URL: https://github.com/apache/bookkeeper/issues/3003#issuecomment-1039898225


   > 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


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@bookkeeper.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [bookkeeper] 315157973 commented on issue #3003: Split read and write orderExecutor

Posted by GitBox <gi...@apache.org>.
315157973 commented on issue #3003:
URL: https://github.com/apache/bookkeeper/issues/3003#issuecomment-1039898225


   > 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 hard disk, when there are many read requests,  the read affects the write, resulting in a write timeout


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@bookkeeper.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org