[JBoss JIRA] (ISPN-3223) HotRod 2.0 Client recieves stale toplogy view on instance leave
by Alan Field (JIRA)
[ https://issues.jboss.org/browse/ISPN-3223?page=com.atlassian.jira.plugin.... ]
Alan Field commented on ISPN-3223:
----------------------------------
Hey Galder,
This is what I see with a 7.2.0-SNAPSHOT build of today's code (Feb 27 2015):
(Start one server, then start the client)
15:59:33,778 INFO [org.infinispan.client.hotrod.impl.protocol.Codec20] (main) ISPN004006: localhost/127.0.0.1:11222 sent new topology view (id=0) containing 1 addresses: [/127.0.0.1:11222]
15:59:33,801 INFO [org.infinispan.client.hotrod.RemoteCacheManager] (main) ISPN004021: Infinispan version: 7.2.0-SNAPSHOT
15:59:33,809 INFO [org.infinispan.client.hotrod.impl.protocol.Codec20] (main) ISPN004006: localhost/127.0.0.1:11222 sent new topology view (id=0) containing 1 addresses: [/127.0.0.1:11222]
15:59:33,810 INFO [org.infinispan.test.CSPut] (main) Got cache: org.infinispan.client.hotrod.impl.RemoteCacheImpl@735b478
15:59:34,338 INFO [org.infinispan.test.CSPut] (main) Loop 1000 finished.
15:59:34,593 INFO [org.infinispan.test.CSPut] (main) Loop 2000 finished.
15:59:34,793 INFO [org.infinispan.test.CSPut] (main) Loop 3000 finished.
(Start second server)
15:59:47,319 INFO [org.infinispan.client.hotrod.impl.protocol.Codec20] (main) ISPN004006: localhost/127.0.0.1:11222 sent new topology view (id=1) containing 1 addresses: [/127.0.0.1:11222]
15:59:48,903 INFO [org.infinispan.test.CSPut] (main) Loop 134000 finished.
15:59:49,008 INFO [org.infinispan.client.hotrod.impl.protocol.Codec20] (main) ISPN004006: localhost/127.0.0.1:11222 sent new topology view (id=2) containing 2 addresses: [/127.0.0.1:11232, /127.0.0.1:11222]
15:59:49,008 INFO [org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory] (main) ISPN004014: New server added(/127.0.0.1:11232), adding to the pool.
15:59:50,130 INFO [org.infinispan.test.CSPut] (main) Loop 135000 finished.
15:59:50,779 INFO [org.infinispan.test.CSPut] (main) Loop 136000 finished.
15:59:51,584 INFO [org.infinispan.test.CSPut] (main) Loop 137000 finished.
(Stop a server)
15:59:59,513 INFO [org.infinispan.client.hotrod.impl.protocol.Codec20] (main) ISPN004006: /127.0.0.1:11232 sent new topology view (id=3) containing 1 addresses: [/127.0.0.1:11232]
15:59:59,514 INFO [org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory] (main) ISPN004016: Server not in cluster anymore(/127.0.0.1:11222), removing from the pool.
15:59:59,723 INFO [org.infinispan.client.hotrod.impl.protocol.Codec20] (main) ISPN004006: /127.0.0.1:11232 sent new topology view (id=4) containing 1 addresses: [/127.0.0.1:11232]
15:59:59,834 INFO [org.infinispan.test.CSPut] (main) Loop 158000 finished.
15:59:59,916 INFO [org.infinispan.test.CSPut] (main) Loop 159000 finished.
15:59:59,986 INFO [org.infinispan.test.CSPut] (main) Loop 160000 finished.
It looks like the issue is not longer there.
Thanks,
Alan
> 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
> 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.11#6341)
10 years, 9 months
[JBoss JIRA] (ISPN-5234) Implement single cluster view page (P1)
by Tomas Sykora (JIRA)
[ https://issues.jboss.org/browse/ISPN-5234?page=com.atlassian.jira.plugin.... ]
Tomas Sykora commented on ISPN-5234:
------------------------------------
The problem is that the path you would ask for cluster availability is: /profile=clustered/subsystem=infinispan/cache-container=clustered
And this path does not provide those information.
We need to ask the runtime path /host=master/server=server-one/subsystem=infinispan/cache-container=clustered which provides:
cluster-availability=AVAILABLE attribute ;)
Working on it.
> Implement single cluster view page (P1)
> ---------------------------------------
>
> Key: ISPN-5234
> URL: https://issues.jboss.org/browse/ISPN-5234
> Project: Infinispan
> Issue Type: Task
> Components: JMX, reporting and management
> Reporter: Vladimir Blagojevic
> Assignee: Vladimir Blagojevic
> Fix For: 8.0.0.Final
>
>
> In our admin console current single cluster view page does not contain the following functionality that should be implemented:
> * -Zoom in/out-
> * Node availability/detail
> * Filter by metrics (node view)
> * Filter by metrics (cache view)
> * Search node (search as you type)
> * Search cache (search as you type)
> * -Cluster switcher-
> * Cluster status view
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 9 months
[JBoss JIRA] (ISPN-5234) Implement single cluster view page (P1)
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-5234?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic commented on ISPN-5234:
-------------------------------------------
Isn't this already implemented in cluster-model.services.js, function getAvailability - we need to implement it though? It needs to actually check availability rather than simply returning true.
> Implement single cluster view page (P1)
> ---------------------------------------
>
> Key: ISPN-5234
> URL: https://issues.jboss.org/browse/ISPN-5234
> Project: Infinispan
> Issue Type: Task
> Components: JMX, reporting and management
> Reporter: Vladimir Blagojevic
> Assignee: Vladimir Blagojevic
> Fix For: 8.0.0.Final
>
>
> In our admin console current single cluster view page does not contain the following functionality that should be implemented:
> * -Zoom in/out-
> * Node availability/detail
> * Filter by metrics (node view)
> * Filter by metrics (cache view)
> * Search node (search as you type)
> * Search cache (search as you type)
> * -Cluster switcher-
> * Cluster status view
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 9 months
[JBoss JIRA] (ISPN-4751) Hibernate search, infinispan and Amazon S3 - IllegalArgumentException: bucketId: A96137216.bz2 (expected: integer)
by Vojtech Juranek (JIRA)
[ https://issues.jboss.org/browse/ISPN-4751?page=com.atlassian.jira.plugin.... ]
Vojtech Juranek commented on ISPN-4751:
---------------------------------------
I'm going to test updated cloud cache store (besides other) with S3 and if everything looks good, the PR will merged and available for use. Once done (general testing with S3), I'll to reproduce specifically this issue and verify that it's fixed by ISPN-3549 (and eventually propose the fix if the issue still remains).
> Hibernate search, infinispan and Amazon S3 - IllegalArgumentException: bucketId: A96137216.bz2 (expected: integer)
> ------------------------------------------------------------------------------------------------------------------
>
> Key: ISPN-4751
> URL: https://issues.jboss.org/browse/ISPN-4751
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Reporter: Lance Ess
> Assignee: Vojtech Juranek
>
> I'm trying to use hibernate-search to host a Lucene index on Amazon S3 but I'm getting the following exception:
> {code}
> Exception in thread "LuceneIndexesData-CloudCacheStore-0" java.lang.IllegalArgumentException: bucketId: A96137216.bz2 (expected: integer)
> at org.infinispan.loaders.bucket.Bucket.setBucketId(Bucket.java:84)
> at org.infinispan.loaders.cloud.CloudCacheStore.readFromBlob(CloudCacheStore.java:450)
> at org.infinispan.loaders.cloud.CloudCacheStore.scanBlobForExpiredEntries(CloudCacheStore.java:292)
> at org.infinispan.loaders.cloud.CloudCacheStore.purge(CloudCacheStore.java:284)
> at org.infinispan.loaders.cloud.CloudCacheStore.purgeInternal(CloudCacheStore.java:336)
> at org.infinispan.loaders.AbstractCacheStore$2.run(AbstractCacheStore.java:111)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at java.lang.Thread.run(Unknown Source)
> {code}
> The documentation for persisting Lucene indexes on Amazon-S3 is a little sparse but I think I'm on the right track. I'm trying to start infinispan embedded within my application so I've specified a path to the infinispan XML as follows in my hibernate.cfg.xml
> {code:xml}
> <property name="hibernate.search.default.directory_provider">infinispan</property>
> <property name="hibernate.search.infinispan.configuration_resourcename">infinispan-amazons3.xml</property>
> <property name="hibernate.search.infinispan.chunk_size">300000000</property>
> {code}
> And my infinispan-amazons3.xml is:
> {code:xml}
> <infinispan>
> <default>
> <loaders>
> <cloudStore xmlns="urn:infinispan:config:cloud:5.3"
> cloudService="aws-s3"
> identity="user"
> password="password"
> bucketPrefix="bucket">
> </cloudStore>
> </loaders>
> </default>
> </infinispan>
> {code}
> I'm using the following versions (maven pom.xml)
> {code}
> <dependency>
> <groupId>org.hibernate</groupId>
> <artifactId>hibernate-search</artifactId>
> <version>4.4.4.Final</version>
> </dependency>
> <dependency>
> <groupId>org.hibernate</groupId>
> <artifactId>hibernate-search-infinispan</artifactId>
> <version>4.4.4.Final</version>
> </dependency>
> <dependency>
> <groupId>org.infinispan</groupId>
> <artifactId>infinispan-cachestore-cloud</artifactId>
> <version>5.3.0.Final</version>
> </dependency>
> <dependency>
> <groupId>org.jclouds.provider</groupId>
> <artifactId>aws-s3</artifactId>
> <version>1.4.1</version>
> </dependency>
> {code}
> I initially thought this was related to ISPN-1909 but my version is after the fix for that issue (5.1.3.CR1, 5.1.3.FINAL)
> FYI here's my maven dependency tree (grepped for infinispan)
> {code}
> $ mvn dependency:tree | grep infinispan
> [INFO] +- org.hibernate:hibernate-search-infinispan:jar:4.4.4.Final:compile
> [INFO] | \- org.infinispan:infinispan-lucene-directory:jar:5.3.0.Final:compile
> [INFO] +- org.infinispan:infinispan-cachestore-cloud:jar:5.3.0.Final:compile
> [INFO] | \- org.infinispan:infinispan-core:jar:5.3.0.Final:compile
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 9 months