[jira] [Updated] (HBASE-29912) Codel lifoThreshold should be applied on soft queue limit instead of hard limit
[ https://issues.apache.org/jira/browse/HBASE-29912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Umesh Kumar Kumawat updated HBASE-29912: Status: Patch Available (was: In Progress) > Codel lifoThreshold should be applied on soft queue limit instead of hard > limit > --- > > Key: HBASE-29912 > URL: https://issues.apache.org/jira/browse/HBASE-29912 > Project: HBase > Issue Type: Bug > Components: rpc >Affects Versions: 2.5.13, 2.6.4, 3.0.0-beta-1 >Reporter: Umesh Kumar Kumawat >Assignee: Umesh Kumar Kumawat >Priority: Major > Labels: pull-request-available > > Codel switch from fifo to lifo and it does this when queue size reached an > threshold. > For now codel lifoThreshold is applied on hard limit. By default soft limit > of the queue remains 100 (10 handler per queue > (CALL_QUEUE_HANDLER_FACTOR_CONF_KEY) and we use > DEFAULT_MAX_CALLQUEUE_LENGTH_PER_HANDLER is 10). And 250 is hard limit. > This way we are never achiving out desired behaviour. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-29912) Codel lifoThreshold should be applied on soft queue limit instead of hard limit
[ https://issues.apache.org/jira/browse/HBASE-29912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Umesh Kumar Kumawat updated HBASE-29912: Description: Codel switch from fifo to lifo and it does this when queue size reached an threshold. For now codel lifoThreshold is applied on hard limit. By default soft limit of the queue remains 100 (10 handler per queue (CALL_QUEUE_HANDLER_FACTOR_CONF_KEY) and we use DEFAULT_MAX_CALLQUEUE_LENGTH_PER_HANDLER is 10). And 250 is hard limit. This way we are never achiving out desired behaviour. was: Code switch from fifo to lifo and it does this when queue size reached an threshold. For now codel lifoThreshold is applied on hard limit. By default soft limit of the queue remains 100 (10 handler per queue (CALL_QUEUE_HANDLER_FACTOR_CONF_KEY) and we use DEFAULT_MAX_CALLQUEUE_LENGTH_PER_HANDLER is 10). And 250 is hard limit. This way we are never achiving out desired behaviour. > Codel lifoThreshold should be applied on soft queue limit instead of hard > limit > --- > > Key: HBASE-29912 > URL: https://issues.apache.org/jira/browse/HBASE-29912 > Project: HBase > Issue Type: Bug > Components: rpc >Affects Versions: 3.0.0-beta-1, 2.6.4, 2.5.13 >Reporter: Umesh Kumar Kumawat >Assignee: Umesh Kumar Kumawat >Priority: Major > Labels: pull-request-available > > Codel switch from fifo to lifo and it does this when queue size reached an > threshold. > For now codel lifoThreshold is applied on hard limit. By default soft limit > of the queue remains 100 (10 handler per queue > (CALL_QUEUE_HANDLER_FACTOR_CONF_KEY) and we use > DEFAULT_MAX_CALLQUEUE_LENGTH_PER_HANDLER is 10). And 250 is hard limit. > This way we are never achiving out desired behaviour. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-29912) Codel lifoThreshold should be applied on soft queue limit instead of hard limit
[ https://issues.apache.org/jira/browse/HBASE-29912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Umesh Kumar Kumawat updated HBASE-29912: Description: Code switch from fifo to lifo and it does this when queue size reached an threshold. For now codel lifoThreshold is applied on hard limit. By default soft limit of the queue remains 100 (10 handler per queue (CALL_QUEUE_HANDLER_FACTOR_CONF_KEY) and we use DEFAULT_MAX_CALLQUEUE_LENGTH_PER_HANDLER is 10). And 250 is hard limit. This way we are never achiving out desired behaviour. was: For now codel lifoThreshold is applied on hard limit. By default soft limit of the queue remains 100 (10 handler per queue (CALL_QUEUE_HANDLER_FACTOR_CONF_KEY) and we use DEFAULT_MAX_CALLQUEUE_LENGTH_PER_HANDLER is 10). And 250 is hard limit. This way we are never achiving out desired behaviour. > Codel lifoThreshold should be applied on soft queue limit instead of hard > limit > --- > > Key: HBASE-29912 > URL: https://issues.apache.org/jira/browse/HBASE-29912 > Project: HBase > Issue Type: Bug > Components: rpc >Affects Versions: 3.0.0-beta-1, 2.6.4, 2.5.13 >Reporter: Umesh Kumar Kumawat >Assignee: Umesh Kumar Kumawat >Priority: Major > Labels: pull-request-available > > Code switch from fifo to lifo and it does this when queue size reached an > threshold. > For now codel lifoThreshold is applied on hard limit. By default soft limit > of the queue remains 100 (10 handler per queue > (CALL_QUEUE_HANDLER_FACTOR_CONF_KEY) and we use > DEFAULT_MAX_CALLQUEUE_LENGTH_PER_HANDLER is 10). And 250 is hard limit. > This way we are never achiving out desired behaviour. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-29912) Codel lifoThreshold should be applied on soft queue limit instead of hard limit
[ https://issues.apache.org/jira/browse/HBASE-29912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated HBASE-29912: --- Labels: pull-request-available (was: ) > Codel lifoThreshold should be applied on soft queue limit instead of hard > limit > --- > > Key: HBASE-29912 > URL: https://issues.apache.org/jira/browse/HBASE-29912 > Project: HBase > Issue Type: Bug > Components: rpc >Affects Versions: 3.0.0-beta-1, 2.6.4, 2.5.13 >Reporter: Umesh Kumar Kumawat >Assignee: Umesh Kumar Kumawat >Priority: Major > Labels: pull-request-available > > For now codel lifoThreshold is applied on hard limit. By default soft limit > of the queue remains 100 (10 handler per queue > (CALL_QUEUE_HANDLER_FACTOR_CONF_KEY) and we use > DEFAULT_MAX_CALLQUEUE_LENGTH_PER_HANDLER is 10). And 250 is hard limit. > This way we are never achiving out desired behaviour. -- This message was sent by Atlassian Jira (v8.20.10#820010)
