You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "Brahma Reddy Battula (JIRA)" <ji...@apache.org> on 2012/07/10 06:52:33 UTC
[jira] [Commented] (BOOKKEEPER-336) bookie readEntries is taking
more time if the ensemble has failed bookie(s)
[ https://issues.apache.org/jira/browse/BOOKKEEPER-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13410047#comment-13410047 ]
Brahma Reddy Battula commented on BOOKKEEPER-336:
-------------------------------------------------
For each entry retry it'll take 10seconds
{noformat}
2012-07-06 22:07:59,734 ERROR hidden.bkjournal.org.apache.bookkeeper.client.PendingReadOp: Bookie handle is not available while reading entry: 18 ledgerId: 3 from bookie: /HOST.24:3181
2012-07-06 22:08:10,234 ERROR hidden.bkjournal.org.apache.bookkeeper.proto.PerChannelBookieClient: Could not connect to bookie: /HOST.24:3181
2012-07-06 22:08:10,234 ERROR hidden.bkjournal.org.apache.bookkeeper.client.PendingReadOp: Bookie handle is not available while reading entry: 21 ledgerId: 3 from bookie: /HOST.24:3181
2012-07-06 22:08:21,234 ERROR hidden.bkjournal.org.apache.bookkeeper.proto.PerChannelBookieClient: Could not connect to bookie: /HOST.24:3181
2012-07-06 22:08:21,234 ERROR hidden.bkjournal.org.apache.bookkeeper.client.PendingReadOp: Bookie handle is not available while reading entry: 24 ledgerId: 3 from bookie: /HOST.24:3181
2012-07-06 22:08:31,734 ERROR hidden.bkjournal.org.apache.bookkeeper.proto.PerChannelBookieClient: Could not connect to bookie: /HOST.24:3181
2012-07-06 22:08:31,734 ERROR hidden.bkjournal.org.apache.bookkeeper.client.PendingReadOp: Bookie handle is not available while reading entry: 27 ledgerId: 3 from bookie: /HOST.24:3181
2012-07-06 22:08:42,734 ERROR hidden.bkjournal.org.apache.bookkeeper.proto.PerChannelBookieClient: Could not connect to bookie: /HOST.24:3181
2012-07-06 22:08:42,734 ERROR hidden.bkjournal.org.apache.bookkeeper.client.PendingReadOp: Bookie handle is not available while reading entry: 30 ledgerId: 3 from bookie: /HOST.24:3181
2012-07-06 22:08:53,234 ERROR hidden.bkjournal.org.apache.bookkeeper.proto.PerChannelBookieClient: Could not connect to bookie: /HOST.24:3181
{noformat}
> bookie readEntries is taking more time if the ensemble has failed bookie(s)
> ---------------------------------------------------------------------------
>
> Key: BOOKKEEPER-336
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-336
> Project: Bookkeeper
> Issue Type: Bug
> Affects Versions: 4.1.0
> Reporter: Brahma Reddy Battula
>
> Scenario:
> 1) Start three bookies. Create ledger with ensemblesize=3, quorumsize=3
> 2) Add 100 entries to this ledger
> 3) Make first bookie down and read the entries from 0-99
> Output: Each entry is going to fetch from the failed bookie and is waiting for the bookie connection timeout, only after failure going to next bookie.
> This is affecting the read entry performance.
> Impact: Namenode switching time will be affected by adding this failed bookie readTimeOut also.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira