February 2019 - infinispan-issues

[JBoss JIRA] (ISPN-9908) Cache startup failure with insufficient segments

by Hiroki Daicho (Jira)

[ https://issues.jboss.org/browse/ISPN-9908?page=com.atlassian.jira.plugin.... ] Hiroki Daicho updated ISPN-9908: -------------------------------- Description: When setting small segment to a cache and using server hinting, node can't start with the following error[1]. It can be reproduced with RHDG 7.2.3 and 7.3 ER2. [1] {code} ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.datagrid-infinispan.clustered.test: org.jboss.msc.service.StartException in service jboss.datagrid-infinispan.clustered.test: Failed to start service ... Caused by: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.statetransfer.StateTransferManagerImpl.start() throws java.lang.Exception on object of type StateTransferManagerImpl ... Caused by: org.infinispan.util.concurrent.TimeoutException: Replication timeout for svr01 (flags=0), site-id=site1, rack-id=rack1, machine-id=machine1) at org.infinispan.remoting.transport.jgroups.JGroupsTransport.checkRsp(JGroupsTransport.java:916) ... {code} For example, 3rd node will fail to start with the following setting in 3 nodes cluster. When set the segments to 20 (6.6.2 default), 6th node will fail to start with the above timeout. Nodes seems to not be able to finish the initial state transfer and start up fails if the segments are set insufficiently against the number of nodes, {code} <distributed-cache name="default" segments="1" /> ... <stack name="udp"> <transport type="UDP" socket-binding="jgroups-udp" machine="${jboss.jgroups.transport.machine:machine1}" rack="${jboss.jgroups.transport.rack:rack1}" site="${jboss.jgroups.transport.site:site1}" /> </stack> {code} was: When setting small segment to a cache and using server hinting, node can't start with the following error[1]. It can be reproduced with RHDG 7.2.3 and 7.3 ER2. [1] {code} ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.datagrid-infinispan.clustered.test: org.jboss.msc.service.StartException in service jboss.datagrid-infinispan.clustered.test: Failed to start service ... Caused by: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.statetransfer.StateTransferManagerImpl.start() throws java.lang.Exception on object of type StateTransferManagerImpl ... Caused by: org.infinispan.util.concurrent.TimeoutException: Replication timeout for svr01 (flags=0), site-id=site1, rack-id=rack1, machine-id=machine1) at org.infinispan.remoting.transport.jgroups.JGroupsTransport.checkRsp(JGroupsTransport.java:916) ... {code} For example, 3rd node will fail to start with the following setting in 3 nodes cluster. When set the segments to 20 (6.6.2 default), 6nd node will fail to start with the above timeout. Nodes seems to not be able to finish the initial state transfer and start up fails if the segments are set insufficiently against the number of nodes, {code} <distributed-cache name="default" segments="1" /> ... <stack name="udp"> <transport type="UDP" socket-binding="jgroups-udp" machine="${jboss.jgroups.transport.machine:machine1}" rack="${jboss.jgroups.transport.rack:rack1}" site="${jboss.jgroups.transport.site:site1}" /> </stack> {code} > Cache startup failure with insufficient segments > ------------------------------------------------ > > Key: ISPN-9908 > URL: https://issues.jboss.org/browse/ISPN-9908 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.4.6.Final > Reporter: Hiroki Daicho > Assignee: Dan Berindei > Priority: Major > Attachments: logs.zip > > > When setting small segment to a cache and using server hinting, node can't start with the following error[1]. > It can be reproduced with RHDG 7.2.3 and 7.3 ER2. > [1] > {code} > ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.datagrid-infinispan.clustered.test: org.jboss.msc.service.StartException in service jboss.datagrid-infinispan.clustered.test: Failed to start service > ... > Caused by: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.statetransfer.StateTransferManagerImpl.start() throws java.lang.Exception on object of type StateTransferManagerImpl > ... > Caused by: org.infinispan.util.concurrent.TimeoutException: Replication timeout for svr01 (flags=0), site-id=site1, rack-id=rack1, machine-id=machine1) > at org.infinispan.remoting.transport.jgroups.JGroupsTransport.checkRsp(JGroupsTransport.java:916) > ... > {code} > For example, 3rd node will fail to start with the following setting in 3 nodes cluster. > When set the segments to 20 (6.6.2 default), 6th node will fail to start with the above timeout. > Nodes seems to not be able to finish the initial state transfer and start up fails if the segments are set insufficiently against the number of nodes, > {code} > <distributed-cache name="default" segments="1" /> > ... > <stack name="udp"> > <transport type="UDP" socket-binding="jgroups-udp" machine="${jboss.jgroups.transport.machine:machine1}" rack="${jboss.jgroups.transport.rack:rack1}" site="${jboss.jgroups.transport.site:site1}" /> > </stack> > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-84) ProtoSchemaBuilder does not detect duplicated enum constant names

by Adrian Nistor (Jira)

[ https://issues.jboss.org/browse/IPROTO-84?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated IPROTO-84: -------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/protostream/pull/58 > ProtoSchemaBuilder does not detect duplicated enum constant names > ----------------------------------------------------------------- > > Key: IPROTO-84 > URL: https://issues.jboss.org/browse/IPROTO-84 > Project: Infinispan ProtoStream > Issue Type: Bug > Affects Versions: 4.2.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Priority: Major > Fix For: 4.3.0.Alpha1, 4.2.3.Final > > > The duplication is eventually detected later by the proto schema parser, but at this moment the broken schema is already registered and its status is ERROR. Would be better to detect this early during the analysis of the annotations. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-85) ClassCastException with enum imported from external schema when using ProtoSchemaBuilder

by Adrian Nistor (Jira)

[ https://issues.jboss.org/browse/IPROTO-85?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated IPROTO-85: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/protostream/pull/58 > ClassCastException with enum imported from external schema when using ProtoSchemaBuilder > ---------------------------------------------------------------------------------------- > > Key: IPROTO-85 > URL: https://issues.jboss.org/browse/IPROTO-85 > Project: Infinispan ProtoStream > Issue Type: Bug > Affects Versions: 4.2.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Priority: Major > Fix For: 4.3.0.Alpha1, 4.2.3.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-85) ClassCastException with enum imported from external schema when using ProtoSchemaBuilder

by Adrian Nistor (Jira)

[ https://issues.jboss.org/browse/IPROTO-85?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated IPROTO-85: -------------------------------- Fix Version/s: 4.3.0.Alpha1 4.2.3.Final > ClassCastException with enum imported from external schema when using ProtoSchemaBuilder > ---------------------------------------------------------------------------------------- > > Key: IPROTO-85 > URL: https://issues.jboss.org/browse/IPROTO-85 > Project: Infinispan ProtoStream > Issue Type: Bug > Affects Versions: 4.2.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Priority: Major > Fix For: 4.3.0.Alpha1, 4.2.3.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-85) ClassCastException with enum imported from external schema when using ProtoSchemaBuilder

by Adrian Nistor (Jira)

[ https://issues.jboss.org/browse/IPROTO-85?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated IPROTO-85: -------------------------------- Status: Open (was: New) > ClassCastException with enum imported from external schema when using ProtoSchemaBuilder > ---------------------------------------------------------------------------------------- > > Key: IPROTO-85 > URL: https://issues.jboss.org/browse/IPROTO-85 > Project: Infinispan ProtoStream > Issue Type: Bug > Affects Versions: 4.2.0.Final > Reporter: Adrian Nistor > Priority: Major > Fix For: 4.3.0.Alpha1, 4.2.3.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-85) ClassCastException with enum imported from external schema when using ProtoSchemaBuilder

by Adrian Nistor (Jira)

[ https://issues.jboss.org/browse/IPROTO-85?page=com.atlassian.jira.plugin.... ] Adrian Nistor reassigned IPROTO-85: ----------------------------------- Assignee: Adrian Nistor > ClassCastException with enum imported from external schema when using ProtoSchemaBuilder > ---------------------------------------------------------------------------------------- > > Key: IPROTO-85 > URL: https://issues.jboss.org/browse/IPROTO-85 > Project: Infinispan ProtoStream > Issue Type: Bug > Affects Versions: 4.2.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Priority: Major > Fix For: 4.3.0.Alpha1, 4.2.3.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-84) ProtoSchemaBuilder does not detect duplicated enum constant names

by Adrian Nistor (Jira)

[ https://issues.jboss.org/browse/IPROTO-84?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated IPROTO-84: -------------------------------- Affects Version/s: 4.2.0.Final > ProtoSchemaBuilder does not detect duplicated enum constant names > ----------------------------------------------------------------- > > Key: IPROTO-84 > URL: https://issues.jboss.org/browse/IPROTO-84 > Project: Infinispan ProtoStream > Issue Type: Bug > Affects Versions: 4.2.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Priority: Major > Fix For: 4.3.0.Alpha1, 4.2.3.Final > > > The duplication is eventually detected later by the proto schema parser, but at this moment the broken schema is already registered and its status is ERROR. Would be better to detect this early during the analysis of the annotations. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-85) ClassCastException with enum imported from external schema when using ProtoSchemaBuilder

by Adrian Nistor (Jira)

Adrian Nistor created IPROTO-85: ----------------------------------- Summary: ClassCastException with enum imported from external schema when using ProtoSchemaBuilder Key: IPROTO-85 URL: https://issues.jboss.org/browse/IPROTO-85 Project: Infinispan ProtoStream Issue Type: Bug Affects Versions: 4.2.0.Final Reporter: Adrian Nistor -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-84) ProtoSchemaBuilder does not detect duplicated enum constant names

by Adrian Nistor (Jira)

[ https://issues.jboss.org/browse/IPROTO-84?page=com.atlassian.jira.plugin.... ] Work on IPROTO-84 started by Adrian Nistor. ------------------------------------------- > ProtoSchemaBuilder does not detect duplicated enum constant names > ----------------------------------------------------------------- > > Key: IPROTO-84 > URL: https://issues.jboss.org/browse/IPROTO-84 > Project: Infinispan ProtoStream > Issue Type: Bug > Affects Versions: 4.2.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Priority: Major > Fix For: 4.3.0.Alpha1, 4.2.3.Final > > > The duplication is eventually detected later by the proto schema parser, but at this moment the broken schema is already registered and its status is ERROR. Would be better to detect this early during the analysis of the annotations. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-84) ProtoSchemaBuilder does not detect duplicated enum constant names

by Adrian Nistor (Jira)

[ https://issues.jboss.org/browse/IPROTO-84?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated IPROTO-84: -------------------------------- Fix Version/s: 4.3.0.Alpha1 4.2.3.Final > ProtoSchemaBuilder does not detect duplicated enum constant names > ----------------------------------------------------------------- > > Key: IPROTO-84 > URL: https://issues.jboss.org/browse/IPROTO-84 > Project: Infinispan ProtoStream > Issue Type: Bug > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Priority: Major > Fix For: 4.3.0.Alpha1, 4.2.3.Final > > > The duplication is eventually detected later by the proto schema parser, but at this moment the broken schema is already registered and its status is ERROR. Would be better to detect this early during the analysis of the annotations. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2019