[JBoss JIRA] (ISPN-3160) RemoteCacheManager javadocs list wrong default pool size
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-3160?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-3160:
------------------------------------
Fix Version/s: 7.0.0.Final
(was: 7.0.0.CR2)
> 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)
11 years, 5 months
[JBoss JIRA] (ISPN-3223) HotRod 2.0 Client recieves stale toplogy view on instance leave
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-3223?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-3223:
------------------------------------
Fix Version/s: (was: 7.0.0.CR2)
> HotRod 2.0 Client recieves stale toplogy view on instance leave
> ---------------------------------------------------------------
>
> Key: ISPN-3223
> URL: https://issues.jboss.org/browse/ISPN-3223
> Project: Infinispan
> Issue Type: Bug
> Components: Remote Protocols
> Affects Versions: 5.2.4.Final, 5.3.0.CR1, 7.0.0.Beta1
> Reporter: Takayoshi Kimura
> Assignee: Galder Zamarreño
> Fix For: 7.0.0.Final
>
> Attachments: hr-protocol-13.log, hr-protocol-20.log
>
>
> When killed a HotRod server node, HotRod Clinet sometimes recieves a stale toplogy view which includes the dead node and uses it as a latest view. In this case the client keeps trying to connect that node and keeps failing.
> Looks like the AbstractEncoder1x.generateTopologyResponse() takes care of node join but doesn't handle node leave:
> {noformat}
> if (!serverEndpointsMap.keySet.containsAll(cacheMembers)) {
> {noformat}
> For example, serverEndpointsMap.keySet is [A, B, C] and the actual cacheMembers is [A, B].
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months