[JBoss JIRA] (ISPN-3160) RemoteCacheManager javadocs list wrong default pool size
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-3160?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-3160:
-----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> RemoteCacheManager javadocs list wrong default pool size
> --------------------------------------------------------
>
> Key: ISPN-3160
> URL: https://issues.jboss.org/browse/ISPN-3160
> Project: Infinispan
> Issue Type: Bug
> Components: Remote Protocols
> Affects Versions: 5.1.8.Final
> Reporter: Dennis Reed
> Assignee: Tristan Tarrant
> Priority: Minor
> Fix For: 7.0.0.Final
>
>
> RemoteCacheManager javadocs list the default pool size as 10:
> "infinispan.client.hotrod.default_executor_factory.pool_size, default = 10."
> However, the default is actually 99:
> org/infinispan/client/hotrodimpl/ConfigurationProperties.java: return props.getIntProperty(DEFAULT_EXECUTOR_FACTORY_POOL_SIZE, 99);
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month
[JBoss JIRA] (ISPN-4076) RHQ server plugin: bytesRead and bytesWritten stats are broken
by Tomas Sykora (JIRA)
[ https://issues.jboss.org/browse/ISPN-4076?page=com.atlassian.jira.plugin.... ]
Tomas Sykora commented on ISPN-4076:
------------------------------------
Ah, thanks for bringing this to our attention again!
I will need to look into it during next 2 weeks and re-try with latest bits.
> RHQ server plugin: bytesRead and bytesWritten stats are broken
> --------------------------------------------------------------
>
> Key: ISPN-4076
> URL: https://issues.jboss.org/browse/ISPN-4076
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Affects Versions: 7.0.0.Alpha1
> Reporter: Tomas Sykora
> Assignee: Tomas Sykora
> Labels: 630
>
> resource path: subsystem=endpoint
> and underlined connectors provides statistics: bytesRead, bytesWritten.
> However plugin asks for bytes-read and bytes-written which is wrong. Small change in map in MetricsRemappingComponent is needed.
> + We will remove monitoring of those statistics for REST endpoint, as this endpoint does not provide those statistics at all.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month
[JBoss JIRA] (ISPN-4922) Remove carriage returns from test files
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-4922?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-4922:
-------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Remove carriage returns from test files
> ---------------------------------------
>
> Key: ISPN-4922
> URL: https://issues.jboss.org/browse/ISPN-4922
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Core
> Affects Versions: 7.0.0.CR2
> Reporter: William Burns
> Assignee: William Burns
> Fix For: 7.0.0.Final
>
>
> DistributedEntryRetrieverTest still has some carriage returns in it erroneously. they should be removed as well as any other tests although running {code}find -name *.java -exec grep -r $'\r' '{}' \; -print
> {code} only seems to return DistributedEntryRetrieverTest.java
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month
[JBoss JIRA] (ISPN-4828) Increasing default internal thread pool size
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-4828?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-4828:
-----------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 7.0.0.Final
Resolution: Done
> Increasing default internal thread pool size
> --------------------------------------------
>
> Key: ISPN-4828
> URL: https://issues.jboss.org/browse/ISPN-4828
> Project: Infinispan
> Issue Type: Enhancement
> Components: Configuration, Core
> Affects Versions: 7.0.0.CR1
> Reporter: Matej Čimbora
> Assignee: Dan Berindei
> Priority: Critical
> Fix For: 7.0.0.Final
>
>
> Using synchronous replication with high number of concurrent clients doing put() operations over a shared set of keys, lock-acquisition timeouts occur when various thread pools (internal, jgroups oob) do not have appropriate size.
> org.infinispan.util.concurrent.TimeoutException: Unable to acquire lock after [3 seconds] on key [key_00000000000003B4] for requestor [Thread[OOB-66,default,node03-12795,5,main]]! Lock held by [Thread[OOB-314,default,node03-12795,5,main]]
> [org.infinispan.interceptors.InvocationContextInterceptor] (Stressor-1) ISPN000136: Execution error
> org.infinispan.util.concurrent.TimeoutException: org.infinispan.util.concurrent.TimeoutException: Node node04-24454 timed out
> This applies to both transactional and non-transactional configuration. The problem can be mitigated by increasing Infinispan's internal thread pool size (defined for remoteCommandsExecutor, blockingBoundedQueueThreadPool). In order to improve user experience either:
> a) When needed, the size of the thread pool should be increased as the load increases
> b) The default values should be high enough to handle even significant load (in terms of number of concurrent clients per node)
> c) The documentation should describe how the end user should size the thread pools based on expected load on the system
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month