[JBoss JIRA] (ISPN-3223) HotRod 2.0 Client recieves stale toplogy view on instance leave
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-3223?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño commented on ISPN-3223:
----------------------------------------
Alan, FYI: ISPN-4707
> 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.Beta2, 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, 7 months
[JBoss JIRA] (ISPN-4707) On leave, Hot Rod client ends up with old cluster formation
by Galder Zamarreño (JIRA)
Galder Zamarreño created ISPN-4707:
--------------------------------------
Summary: On leave, Hot Rod client ends up with old cluster formation
Key: ISPN-4707
URL: https://issues.jboss.org/browse/ISPN-4707
Project: Infinispan
Issue Type: Bug
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 7.0.0.Beta2
In spite of that, at least with version 2.0 of the protocol, the consistent hash works fine and sends requests to remaining nodes only, without failure.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (ISPN-3223) HotRod 2.0 Client recieves stale toplogy view on instance leave
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-3223?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño commented on ISPN-3223:
----------------------------------------
Alan, although I see the same log messages, the logic works fine because even though there's two members in the cluster membership, the consistent hash points everything towards the only running node, even though the keys vary, so it's not the same case as Takayoshi has. Creating a new JIRA to track your particular issue.
> 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.Beta2, 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, 7 months
[JBoss JIRA] (ISPN-3223) HotRod 2.0 Client recieves stale toplogy view on instance leave
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-3223?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño commented on ISPN-3223:
----------------------------------------
[~tkimura], sorry we missed this JIRA :(
This issue can't be specific to HR 2.0 cos it was entered a year ago :|.
> 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.Beta2, 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, 7 months
[JBoss JIRA] (ISPN-3223) HotRod 2.0 Client recieves stale toplogy view on instance leave
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-3223?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-3223:
-----------------------------------
Fix Version/s: 7.0.0.Beta2
7.0.0.Final
> 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.Beta2, 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, 7 months
[JBoss JIRA] (ISPN-4604) Race condition in the QueryInterceptor involving SearchFactory
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-4604?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-4604:
-----------------------------------------------
Vojtech Juranek <vjuranek(a)redhat.com> changed the Status of [bug 1135553|https://bugzilla.redhat.com/show_bug.cgi?id=1135553] from ON_QA to VERIFIED
> Race condition in the QueryInterceptor involving SearchFactory
> --------------------------------------------------------------
>
> Key: ISPN-4604
> URL: https://issues.jboss.org/browse/ISPN-4604
> Project: Infinispan
> Issue Type: Bug
> Components: Embedded Querying, Test Suite - Query
> Affects Versions: 7.0.0.Alpha5
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Fix For: 7.0.0.Beta1
>
>
> During perform work task in the QueryInterceptor, the underlying SearchFactory could be swapped (for example by some other thread calling SearchFactory.addClass) and temporarily return null when looking for indexBindings, and throws intermittent Exceptions like:
> {code}
> Caused by: org.hibernate.search.exception.SearchException: Unable to perform work. Entity Class is not @Indexed nor hosts @ContainedIn: class org.infinispan.query.test.VeryLongIndexNamedClass
> at org.hibernate.search.backend.impl.TransactionalWorker.performWork(TransactionalWorker.java:58)
> at org.infinispan.query.backend.QueryInterceptor.performSearchWorks(QueryInterceptor.java:233)
> at org.infinispan.query.backend.QueryInterceptor.performSearchWork(QueryInterceptor.java:227)
> at org.infinispan.query.backend.QueryInterceptor.updateIndexes(QueryInterceptor.java:221)
> at org.infinispan.query.backend.QueryInterceptor.processPutKeyValueCommand(QueryInterceptor.java:531)
> at org.infinispan.query.backend.QueryInterceptor.visitPutKeyValueCommand(QueryInterceptor.java:162)
> at org.infinispan.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:71)
> at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:98)
> at org.infinispan.interceptors.locking.AbstractLockingInterceptor.visitPutKeyValueCommand(AbstractLockingInterceptor.java:46)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months