[ https://issues.apache.org/jira/browse/HADOOP-13189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15332537#comment-15332537 ]
Konstantin Shvachko commented on HADOOP-13189: ---------------------------------------------- _I think it is a bug fix._ Current meaning of call queue size for FairCallQueue contradicts documentation. The refreshCallQueue is a good example. You had a standard queue of size 1000. Then you switch to FairCallQueue using refreshCallQueue command, and suddenly increase the queue size to 4000. I don't think this is expected. It is definitely not documented. > FairCallQueue makes callQueue larger than the configured capacity. > ------------------------------------------------------------------ > > Key: HADOOP-13189 > URL: https://issues.apache.org/jira/browse/HADOOP-13189 > Project: Hadoop Common > Issue Type: Bug > Components: ipc > Affects Versions: 2.6.0 > Reporter: Konstantin Shvachko > Assignee: Vinitha Reddy Gankidi > Attachments: HADOOP-13189.001.patch, HADOOP-13189.002.patch, > HADOOP-13189.003.patch > > > {{FairCallQueue}} divides {{callQueue}} into multiple (4 by default) > sub-queues, with each sub-queue corresponding to a different level of > priority. The constructor for {{FairCallQueue}} takes the same parameter > {{capacity}} as the default CallQueue implementation, and allocates all its > sub-queues of size {{capacity}}. With 4 levels of priority (sub-queues) by > default it results in the total callQueue size 4 times larger than it should > be based on the configuration. > {{capacity}} should be divided by the number of sub-queues at some place. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org