[infinispan-issues] [JBoss JIRA] (HRJS-59) Under heavy load of servers and javascript client ERROR messages about timeouts can starve resources in limited environments (kubernetes/openshift)
Rafa Eska created HRJS-59:
-----------------------------
Summary: Under heavy load of servers and javascript client ERROR messages
about timeouts can starve resources in limited environments (kubernetes/openshift)
Key: HRJS-59
URL: https://issues.jboss.org/browse/HRJS-59
Project: Infinispan Javascript client
Issue Type: Enhancement
Affects Versions: 0.4.0
Environment: Node 8.6.0 in a container inside Openshift with limits of 1000
millicores and 1000MB of memory
Infinispan 'Chakra' 8.4.0.Final-redhat-3 running in 2 pods running image
registry.access.redhat.com/jboss-datagrid-7/datagrid71-openshift/images/1... with limits
of 1000 millicores and 1000MB of memory
Reporter: Rafa Eska
During charge tests Infinispan undersizes server end denegating service, and Javascript
Hotrod client consume all Node.js pod resources emitting this:{{
{code:java}
[31m[2018-05-10 12:38:24.956] [ERROR] decoder - [39mError decoding body of
request(msgId=366322): org.infinispan.util.concurrent.TimeoutException: Timed out waiting
for responses
[31m[2018-05-10 12:38:24.957] [ERROR] decoder - [39mError decoding body of
request(msgId=366322): org.infinispan.util.concurrent.TimeoutException: Timed out waiting
for responses
[31m[2018-05-10 12:38:24.957] [ERROR] decoder -[39mError decoding body of
request(msgId=366322): org.infinispan.util.concurrent.TimeoutException: Timed out waiting
for responses
jdg error org.infinispan.util.concurrent.TimeoutException: Timed out waiting for
responses
[31m[2018-05-10 12:38:24.958] [ERROR] decoder -[39mError decoding body of
request(msgId=366322): org.infinispan.util.concurrent.TimeoutException: Timed out waiting
for responses
[31m[2018-05-10 12:38:24.958] [ERROR] io_1_conn_5 - [39mError received but rpc not found
for (msgId=366322)
[31m[2018-05-10 12:38:24.958] [ERROR] decoder - [39mError decoding body of
request(msgId=366322): org.infinispan.util.concurrent.TimeoutException: Timed out waiting
for responses
[31m[2018-05-10 12:38:24.958] [ERROR] io_1_conn_5 - [39mError received but rpc not found
for (msgId=366322)
[31m[2018-05-10 12:38:24.958] [ERROR] decoder - [39mError decoding body of
request(msgId=366322): org.infinispan.util.concurrent.TimeoutException: Timed out waiting
for responses
[31m[2018-05-10 12:38:24.958] [ERROR] io_1_conn_5 - [39mError received but rpc not found
for (msgId=366322)
{code}
}}
Shouldn't it be WARNINGS? Or control in any way number of emitted messages?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)