[Red Hat JIRA] (ISPN-12614) Initial state transfer timed out for cache
by Om Giri (Jira)
[ https://issues.redhat.com/browse/ISPN-12614?page=com.atlassian.jira.plugi... ]
Om Giri commented on ISPN-12614:
--------------------------------
Hi [~dan.berindei],
Thanks for the reply. Kindly guide how administrator changes the cache availability status to {{AVAILABLE. Is there any coding or command way to do that. We are using Infinispan with Spring application. Thanks in advance.}}
Regards
Om
> Initial state transfer timed out for cache
> ------------------------------------------
>
> Key: ISPN-12614
> URL: https://issues.redhat.com/browse/ISPN-12614
> Project: Infinispan
> Issue Type: Bug
> Components: State Transfer
> Affects Versions: 9.2.5.Final
> Reporter: Om Giri
> Priority: Critical
> Labels: state_transfer, timeout
> Attachments: error.log, fw-jgroups.xml, infinispan-fw-cache.xml
>
>
> In 2 node cluster environment, 1st time both node up properly with replicated cache. After down 1 node and again up the same node, getting "org.infinispan.commons.CacheException: Initial state transfer timed out for cache". Log/cache-configuration/jgroup file attached.
>
> I have tried this with Weblogic/IBM-WAS/Jetty server and issue replicated on every server and every time.
>
> org.infinispan.commons.CacheException: Initial state transfer timed out for cache GENERIC_PARAMETER_TYPE_ENTITIES$EMPTY on NII0910LEDF0031-12663
> at org.infinispan.statetransfer.StateTransferManagerImpl.waitForInitialStateTransferToComplete(StateTransferManagerImpl.java:233)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.infinispan.commons.util.SecurityActions.lambda$invokeAccessibly$0(SecurityActions.java:79)
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 3 months
[Red Hat JIRA] (ISPN-12614) Initial state transfer timed out for cache
by Dan Berindei (Jira)
[ https://issues.redhat.com/browse/ISPN-12614?page=com.atlassian.jira.plugi... ]
Dan Berindei resolved ISPN-12614.
---------------------------------
Resolution: Duplicate Issue
A cache with partition handling enabled will enter degraded mode when one node of a 2-node cluster is killed (it needs a majority of nodes to stay alive for the cache to remain available).
When a cache is degraded, reads and writes fail with {{AvailabilitException}}, and new nodes cannot join. Unless the administrator changes the cache availability status back to {{AVAILABLE}}, new nodes (including restarted nodes) will fail with a state transfer timeout exception.
ISPN-12179 changes this: instead of timing out, joining nodes skip state transfer for degraded caches. Reads and writes will still fail with {{AvailabilityException}}, and state transfer will happen later if the administrator changes the cache availability status to {{AVAILABLE}}.
> Initial state transfer timed out for cache
> ------------------------------------------
>
> Key: ISPN-12614
> URL: https://issues.redhat.com/browse/ISPN-12614
> Project: Infinispan
> Issue Type: Bug
> Components: State Transfer
> Affects Versions: 9.2.5.Final
> Reporter: Om Giri
> Priority: Critical
> Labels: state_transfer, timeout
> Attachments: error.log, fw-jgroups.xml, infinispan-fw-cache.xml
>
>
> In 2 node cluster environment, 1st time both node up properly with replicated cache. After down 1 node and again up the same node, getting "org.infinispan.commons.CacheException: Initial state transfer timed out for cache". Log/cache-configuration/jgroup file attached.
>
> I have tried this with Weblogic/IBM-WAS/Jetty server and issue replicated on every server and every time.
>
> org.infinispan.commons.CacheException: Initial state transfer timed out for cache GENERIC_PARAMETER_TYPE_ENTITIES$EMPTY on NII0910LEDF0031-12663
> at org.infinispan.statetransfer.StateTransferManagerImpl.waitForInitialStateTransferToComplete(StateTransferManagerImpl.java:233)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.infinispan.commons.util.SecurityActions.lambda$invokeAccessibly$0(SecurityActions.java:79)
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 3 months
[Red Hat JIRA] (ISPN-12607) Metrics degrade cluster performance
by Will Burns (Jira)
[ https://issues.redhat.com/browse/ISPN-12607?page=com.atlassian.jira.plugi... ]
Will Burns updated ISPN-12607:
------------------------------
Fix Version/s: 12.0.0.Final
11.0.9.Final
Resolution: Done
Status: Resolved (was: Pull Request Sent)
> Metrics degrade cluster performance
> -----------------------------------
>
> Key: ISPN-12607
> URL: https://issues.redhat.com/browse/ISPN-12607
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 12.0.0.CR1, 11.0.8.Final
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 12.0.0.Final, 11.0.9.Final
>
>
> The `/metrics` endpoint exposes Infinispan stats so that they can be periodically scraped by monitoring tools such as Prometheus. However, these stats include calls to `size` which does not perform well as the number of entries in a cache increase. Consequently, if deploying DG in a k8 environment with Prometheus monitoring the DG cluster performance rapidly declines as the number of entries in a cache increases due to time /resources spent iterating the cache container.
> This problem is only exasperated when muiltiple caches exist with many entries exist.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 3 months