[JBoss JIRA] (ISPN-7489) org.jgroups.protocols.TCP emits errors when node leaves the cluster
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-7489?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-7489:
------------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 9.0.0.CR3
Resolution: Done
> org.jgroups.protocols.TCP emits errors when node leaves the cluster
> -------------------------------------------------------------------
>
> Key: ISPN-7489
> URL: https://issues.jboss.org/browse/ISPN-7489
> Project: Infinispan
> Issue Type: Bug
> Components: Cloud Integrations, Core
> Affects Versions: 9.0.0.CR1
> Environment: * OpenShift {{v1.5.0-alpha.2+e4b43ee}}
> * Custom Infinispan Server build (based on [these instructions|https://github.com/slaskawi/infinispan-1/tree/custom_image]). SHA1 {{2b0731b21649a88a75ed71d21b9cc06ba365e947}}
> Reporter: Sebastian Łaskawiec
> Assignee: Sebastian Łaskawiec
> Priority: Critical
> Fix For: 9.0.0.CR3
>
>
> When I was performing [Spring Session and Kubernetes Rolling Update demo|https://bluejeans.com/s/pYKUg/] I encountered a couple of problems.
> One of the is this:
> {noformat}
> [transactions-repository-1-04x09] 18:09:12,193 ERROR [org.jgroups.protocols.TCP] (jgroups-30,transactions-repository-1-04x09) JGRP000029: transactions-repository-1-04x09: failed sending message to transactions-repository-1-4z05w (71 bytes): java.net.SocketTimeoutException: connect timed out, headers: GMS: GmsHeader[VIEW_ACK], UNICAST3: DATA, seqno=5262, TP: [cluster_name=cluster]
> [transactions-repository-1-1f8dx] 18:09:12,310 ERROR [org.jgroups.protocols.TCP] (jgroups-16,transactions-repository-1-1f8dx) JGRP000029: transactions-repository-1-1f8dx: failed sending message to transactions-repository-1-4z05w (71 bytes): java.net.SocketTimeoutException: connect timed out, headers: GMS: GmsHeader[VIEW_ACK], UNICAST3: DATA, seqno=6259, TP: [cluster_name=cluster]
> [transactions-repository-1-04x09] 18:09:12,997 ERROR [org.jgroups.protocols.TCP] (jgroups-22,transactions-repository-1-04x09) JGRP000029: transactions-repository-1-04x09: failed sending message to transactions-repository-1-4z05w (71 bytes): java.net.SocketTimeoutException: connect timed out, headers: GMS: GmsHeader[VIEW_ACK], UNICAST3: DATA, seqno=5262, TP: [cluster_name=cluster]
> [transactions-repository-1-1f8dx] 18:09:13,113 ERROR [org.jgroups.protocols.TCP] (jgroups-16,transactions-repository-1-1f8dx) JGRP000029: transactions-repository-1-1f8dx: failed sending message to transactions-repository-1-4z05w (71 bytes): java.net.SocketTimeoutException: connect timed out, headers: GMS: GmsHeader[VIEW_ACK], UNICAST3: DATA, seqno=6259, TP: [cluster_name=cluster]
> {noformat}
> Full logs from Rolling Update process might be found here: https://gist.github.com/slaskawi/530241bb695f1f490bcb25eabaf9d676
> Steps to reproduce:
> * Start local OpenShift Cluster
> * invoke `./init_infrastructure.sh` from https://github.com/slaskawi/presentations/tree/ISPN-7487-reproducer
> * invoke `cd transaction-creator && mvn fabric8:run`
> * Do the rolling update: `oc deploy transactions-repository --latest -n myproject`
> * Observe logs `kubetail -l environment=infrastructure`
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (ISPN-7505) Non-functional read in transaction with modifications returns old value
by Pedro Ruivo (JIRA)
[ https://issues.jboss.org/browse/ISPN-7505?page=com.atlassian.jira.plugin.... ]
Pedro Ruivo updated ISPN-7505:
------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 9.0.0.CR3
Resolution: Done
> Non-functional read in transaction with modifications returns old value
> -----------------------------------------------------------------------
>
> Key: ISPN-7505
> URL: https://issues.jboss.org/browse/ISPN-7505
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 9.0.0.CR1
> Reporter: Radim Vansa
> Assignee: Radim Vansa
> Fix For: 9.0.0.CR3
>
>
> See this modified FunctionalTxInMemoryTest:
> {code:java}
> @Test(dataProvider = "owningModeAndReadWrites")
> public void testReadWriteAfterMods(boolean isOwner, WriteMethod method) throws Exception {
> Object KEY = getKey(isOwner);
> cache(0, DIST).put(KEY, "a");
> tm.begin();
> assertEquals("a", rw.eval(KEY, append("b")).join());
> assertEquals("ab", rw.evalMany(Collections.singleton(KEY), append("c")).findAny().get());
> assertEquals("abc", cache(0, DIST).get(KEY)); // <-- THIS FAILS
> assertEquals(null, rw.eval("otherKey", append("d")).join());
> assertEquals("abc", method.action.eval(KEY, wo, rw,
> MarshallableFunctions.returnReadOnlyFindOrNull(),
> (BiConsumer<EntryView.WriteEntryView<String>, String> & Serializable) (e, prev) -> {}, getClass()));
> tm.commit();
> }
> {code}
> When the entry was modified in given transaction, we have to do the read using functional identity read which passes all modifications along. We need to do this for all {{remoteGet}} s, including those invoked for {{putIfAbsent}} etc.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (ISPN-7550) Remove TriangleAckInterceptor
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-7550?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-7550:
------------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Remove TriangleAckInterceptor
> -----------------------------
>
> Key: ISPN-7550
> URL: https://issues.jboss.org/browse/ISPN-7550
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Reporter: Pedro Ruivo
> Assignee: Pedro Ruivo
> Fix For: 9.0.0.CR3
>
>
> {{TriangleAckInterceptor}} has 2 main goals
> 1. sends the from backup/primary to originator
> 2. in originator, waits for the acks
> ... and has 2 issues:
> 1. if an exception occurs before it, the ack will not be sent!
> 2. waiting for the acks here will add more complexity to the following interceptor if they need the operation outcome.
> So, by removing the interceptor will have:
> 1. acks are sent in inbound handler (where the replies are sent too)
> 2. waiting for ack will happen on {{TriangleDistributionInterceptor}}.
> Other changes:
> * before sending the ack, notify the {{TriangleOrderManager}} that the next command can proceed.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (ISPN-7550) Remove TriangleAckInterceptor
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-7550?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-7550:
------------------------------------
Fix Version/s: 9.0.0.CR3
(was: 9.0.0.Final)
> Remove TriangleAckInterceptor
> -----------------------------
>
> Key: ISPN-7550
> URL: https://issues.jboss.org/browse/ISPN-7550
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Reporter: Pedro Ruivo
> Assignee: Pedro Ruivo
> Fix For: 9.0.0.CR3
>
>
> {{TriangleAckInterceptor}} has 2 main goals
> 1. sends the from backup/primary to originator
> 2. in originator, waits for the acks
> ... and has 2 issues:
> 1. if an exception occurs before it, the ack will not be sent!
> 2. waiting for the acks here will add more complexity to the following interceptor if they need the operation outcome.
> So, by removing the interceptor will have:
> 1. acks are sent in inbound handler (where the replies are sent too)
> 2. waiting for ack will happen on {{TriangleDistributionInterceptor}}.
> Other changes:
> * before sending the ack, notify the {{TriangleOrderManager}} that the next command can proceed.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (ISPN-7541) Health DMR fails with NPE in domain mode
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-7541?page=com.atlassian.jira.plugin.... ]
Ryan Emerson resolved ISPN-7541.
--------------------------------
Fix Version/s: 9.0.0.CR3
Resolution: Done
> Health DMR fails with NPE in domain mode
> ----------------------------------------
>
> Key: ISPN-7541
> URL: https://issues.jboss.org/browse/ISPN-7541
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management, Server
> Reporter: Ryan Emerson
> Assignee: Sebastian Łaskawiec
> Fix For: 9.0.0.CR3
>
>
> Server error when trying to access the HEALTH in domain mode:
> {code:java}
> [Host Controller] 10:21:09,122 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 25) WFLYCTL0013: Operation ("read-attribute") failed - address: ([
> [Host Controller] ("profile" => "clustered"),
> [Host Controller] ("subsystem" => "datagrid-infinispan"),
> [Host Controller] ("cache-container" => "clustered"),
> [Host Controller] ("health" => "HEALTH")
> [Host Controller] ]): java.lang.NullPointerException
> [Host Controller] at org.jboss.as.clustering.infinispan.subsystem.HealthMetricsHandler.executeRuntimeStep(HealthMetricsHandler.java:106)
> [Host Controller] at org.jboss.as.controller.AbstractRuntimeOnlyHandler$1.execute(AbstractRuntimeOnlyHandler.java:53)
> [Host Controller] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:890)
> [Host Controller] at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:659)
> [Host Controller] at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:370)
> [Host Controller] at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1329)
> [Host Controller] at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:400)
> [Host Controller] at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:222)
> [Host Controller] at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:208)
> [Host Controller] at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:130)
> [Host Controller] at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:152)
> [Host Controller] at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:148)
> [Host Controller] at java.security.AccessController.doPrivileged(Native Method)
> [Host Controller] at javax.security.auth.Subject.doAs(Subject.java:422)
> [Host Controller] at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:149)
> [Host Controller] at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:148)
> [Host Controller] at org.jboss.as.protocol.mgmt.AbstractMessageHandler$ManagementRequestContextImpl$1.doExecute(AbstractMessageHandler.java:363)
> [Host Controller] at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:472)
> [Host Controller] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [Host Controller] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [Host Controller] at java.lang.Thread.run(Thread.java:745)
> [Host Controller] at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month