April 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-8852) StackOverflowError when requesting data in case cache is in degraded mode

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-8852?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-8852: ------------------------------------ [~stehlik.michal] from the stack trace it appears that the cache uses pessimistic locking and the application is doing a {{cache.getAdvancedCache().withFlags(Flag.FORCE_WRITE_LOCK).get(key)}}, is that correct? [~ryanemerson] I believe in this scenario the read should fail with an {{AvailabilityException}}, because the cache is in DEGRADED mode and lock acquisition needs to contact all the owners. > StackOverflowError when requesting data in case cache is in degraded mode > ------------------------------------------------------------------------- > > Key: ISPN-8852 > URL: https://issues.jboss.org/browse/ISPN-8852 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.1.4.Final > Reporter: Michal Stehlik > Assignee: Ryan Emerson > Fix For: 9.3.0.Beta1 > > Attachments: stackowerflow.log > > > Found StackOverflowError in logs when network was disconnected, caches are in degraded mode and system attempt to operate with cache Read & Update. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8852) StackOverflowError when requesting data in case cache is in degraded mode

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-8852?page=com.atlassian.jira.plugin.... ] Dan Berindei reassigned ISPN-8852: ---------------------------------- Assignee: Ryan Emerson > StackOverflowError when requesting data in case cache is in degraded mode > ------------------------------------------------------------------------- > > Key: ISPN-8852 > URL: https://issues.jboss.org/browse/ISPN-8852 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.1.4.Final > Reporter: Michal Stehlik > Assignee: Ryan Emerson > Fix For: 9.3.0.Beta1 > > Attachments: stackowerflow.log > > > Found StackOverflowError in logs when network was disconnected, caches are in degraded mode and system attempt to operate with cache Read & Update. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8852) StackOverflowError when requesting data in case cache is in degraded mode

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-8852?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-8852: ------------------------------- Status: Open (was: New) > StackOverflowError when requesting data in case cache is in degraded mode > ------------------------------------------------------------------------- > > Key: ISPN-8852 > URL: https://issues.jboss.org/browse/ISPN-8852 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.1.4.Final > Reporter: Michal Stehlik > Assignee: Ryan Emerson > Fix For: 9.3.0.Beta1 > > Attachments: stackowerflow.log > > > Found StackOverflowError in logs when network was disconnected, caches are in degraded mode and system attempt to operate with cache Read & Update. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8852) StackOverflowError when requesting data in case cache is in degraded mode

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-8852?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-8852: ------------------------------- Fix Version/s: 9.3.0.Beta1 > StackOverflowError when requesting data in case cache is in degraded mode > ------------------------------------------------------------------------- > > Key: ISPN-8852 > URL: https://issues.jboss.org/browse/ISPN-8852 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.1.4.Final > Reporter: Michal Stehlik > Assignee: Ryan Emerson > Fix For: 9.3.0.Beta1 > > Attachments: stackowerflow.log > > > Found StackOverflowError in logs when network was disconnected, caches are in degraded mode and system attempt to operate with cache Read & Update. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9103) Default merge-policy should be NONE instead of PREFERRED_ALWAYS

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-9103?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-9103: ------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/5902, https://github.com/infinispan/infinispan/pull/5942 (was: https://github.com/infinispan/infinispan/pull/5902) > Default merge-policy should be NONE instead of PREFERRED_ALWAYS > --------------------------------------------------------------- > > Key: ISPN-9103 > URL: https://issues.jboss.org/browse/ISPN-9103 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 9.3.0.Alpha1 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.3.0.Beta1 > > > Due to the changes introduced in ISPN-8962 there is no longer a real difference between the PREFERRED_ALWAYS policy and utilising no conflict resolution. In fact, the latter provides the same behaviour but without the added performance cost of CR on partition merges, therefore we should set the default merge-policy to NONE. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9106) Readiness probe fails

by Sebastian Łaskawiec (JIRA)

Sebastian Łaskawiec created ISPN-9106: ----------------------------------------- Summary: Readiness probe fails Key: ISPN-9106 URL: https://issues.jboss.org/browse/ISPN-9106 Project: Infinispan Issue Type: Bug Affects Versions: 9.3.0.Alpha1 Reporter: Sebastian Łaskawiec Assignee: Ryan Emerson The readiness check returns an error on current master build: {code} opt/jboss/infinispan-server/bin/ispn-cli.sh -c --controller=172.16.26.143:9990 '/subsystem=datagrid-infinispan/cache-container=clustered/health=HEALTH:read-attribute(name=cluster-health)' Failed to link org/jboss/as/patching/cli/PatchCommand (Module "org.jboss.as.patching" version 4.0.0.Final from local module loader @555590 (finder: local module finder @6d1e7682 (roots: /opt/jboss/infinispan-server/modules,/opt/jboss/infinispan-server/modules/system/layers/base))): org/aesh/command/Command {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6921) Partition does not become available after merge

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-6921?page=com.atlassian.jira.plugin.... ] Radim Vansa commented on ISPN-6921: ----------------------------------- OK, I've changed the title of the JIRA. Nevertheless the situation described is clearly undesirable: when majority of nodes reunite, the partition should become available. > Partition does not become available after merge > ----------------------------------------------- > > Key: ISPN-6921 > URL: https://issues.jboss.org/browse/ISPN-6921 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.0.0.Alpha3 > Reporter: Radim Vansa > Assignee: Dan Berindei > > During a split (A, B, C, D) -> (A), (B, C, D) -> (A), (B), (C, D) -> (A, C, D), (B) > There was topology update with BCD in CH, but stable topology is still ABCD. > When a merge happens, the merged topology has only CD as newMembers when computing the new availability mode. Therefore, the ACD does not become available though it has enough data from the stable topology. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6921) Partition does not become available after merge

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-6921?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-6921: ------------------------------ Summary: Partition does not become available after merge (was: Use intersection of expected members and stable topology during merge) > Partition does not become available after merge > ----------------------------------------------- > > Key: ISPN-6921 > URL: https://issues.jboss.org/browse/ISPN-6921 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.0.0.Alpha3 > Reporter: Radim Vansa > Assignee: Dan Berindei > > During a split (A, B, C, D) -> (A), (B, C, D) -> (A), (B), (C, D) -> (A, C, D), (B) > There was topology update with BCD in CH, but stable topology is still ABCD. > When a merge happens, the merged topology has only CD as newMembers when computing the new availability mode. Therefore, the ACD does not become available though it has enough data from the stable topology. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6921) Use intersection of expected members and stable topology during merge

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-6921?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-6921: ------------------------------------ [~rvansa] unfortunately being an owner in the stable topology doesn't guarantee that node still has the data. Because the stable topology update is sent asynchronously after the rebalance ends, B could finish the rebalance for (B, C, D) and send the NO_REBALANCE topology update to C and D, but fail to send the stable topology update before it gets isolated. The rebalance process doesn't guarantee that when a node is removed only that node's segments move, so you could have segment 0 owned by CD in the stable topology and by DB in the rebalanced topology, meaning C has deleted its copy of the segment by the time we're trying to use the stable topology for the (A, C, D) partition. We could probably move the stable topology from being a completely separate thing to being just a flag or topology phase. I'm not yet sure if that would be enough or if we also have to change the way we update the topology after a node leaves to keep it in the CH until the rebalance ends. > Use intersection of expected members and stable topology during merge > --------------------------------------------------------------------- > > Key: ISPN-6921 > URL: https://issues.jboss.org/browse/ISPN-6921 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.0.0.Alpha3 > Reporter: Radim Vansa > Assignee: Dan Berindei > > During a split (A, B, C, D) -> (A), (B, C, D) -> (A), (B), (C, D) -> (A, C, D), (B) > There was topology update with BCD in CH, but stable topology is still ABCD. > When a merge happens, the merged topology has only CD as newMembers when computing the new availability mode. Therefore, the ACD does not become available though it has enough data from the stable topology. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6921) Use intersection of expected members and stable topology during merge

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-6921?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-6921: ------------------------------- Status: Open (was: New) > Use intersection of expected members and stable topology during merge > --------------------------------------------------------------------- > > Key: ISPN-6921 > URL: https://issues.jboss.org/browse/ISPN-6921 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.0.0.Alpha3 > Reporter: Radim Vansa > Assignee: Dan Berindei > > During a split (A, B, C, D) -> (A), (B, C, D) -> (A), (B), (C, D) -> (A, C, D), (B) > There was topology update with BCD in CH, but stable topology is still ABCD. > When a merge happens, the merged topology has only CD as newMembers when computing the new availability mode. Therefore, the ACD does not become available though it has enough data from the stable topology. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues April 2018