Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@karaf.apache.org
Date: Wed, 10 May 2017 14:40:04 +0000 (UTC)
From: =?utf-8?Q?Jean-Baptiste_Onofr=C3=A9_=28JIRA=29?= <jira@apache.org>
To: issues@karaf.apache.org
Message-ID: <JIRA.13025504.1480915244000.177204.1494427204981@Atlassian.JIRA>
In-Reply-To: <JIRA.13025504.1480915244000@Atlassian.JIRA>
References: <JIRA.13025504.1480915244000@Atlassian.JIRA> <JIRA.13025504.1480915244214@jira-lw-us.apache.org>
Subject: [jira] [Updated] (KARAF-4878) Cellar Hazelcast unresponsive when
 ETH Down
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Wed, 10 May 2017 14:40:11 -0000


     [ https://issues.apache.org/jira/browse/KARAF-4878?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Baptiste Onofr=C3=A9 updated KARAF-4878:
----------------------------------------
    Fix Version/s: cellar-4.1.0
                   cellar-4.0.4

> Cellar Hazelcast unresponsive when ETH Down
> -------------------------------------------
>
>                 Key: KARAF-4878
>                 URL: https://issues.apache.org/jira/browse/KARAF-4878
>             Project: Karaf
>          Issue Type: Bug
>          Components: cellar-hazelcast
>    Affects Versions: 4.0.5
>         Environment: Redhat Linux 7.2, CentOS 7.2
>            Reporter: Suresh Perumal
>            Assignee: Jean-Baptiste Onofr=C3=A9
>            Priority: Blocker
>             Fix For: cellar-4.0.4, cellar-4.1.0
>
>
> Cluster is configured with 2 Nodes. They are up and running.
> As part of fail-over scenario simulation. We are trying to test "ETHERNET=
 down scenario" by running "/etc/sysconfig/network-scripts/ifdown eth0" com=
mand on the first node.
> During this scenario we are shutting down the first node where the ETH is=
  down by using monitoring scripts(in-house scripts). The second node(Among=
 those two nodes) is kept alive.
> Second Node's Hazelcast is not accessible for more than 15 minutes. We ar=
e getting bellow exception and no operation related to Hazelcast is working=
. Applications whichever uses hazelcast kept frozen.
> Invocation                       | 52 - com.hazelcast - 3.5.2 | [10.249.5=
0.80]:5701 [cellar] [3.5.2] While asking 'is-executing': Invocation{ servic=
eName=3D'hz:impl:mapService', op=3DPutOperation{unacknowledged-alarm}, part=
itionId=3D165, replicaIndex=3D0, tryCount=3D250, tryPauseMillis=3D500, invo=
keCount=3D1, callTimeout=3D60000, target=3DAddress[10.249.50.79]:5701, back=
upsExpected=3D0, backupsCompleted=3D0}
> java.util.concurrent.TimeoutException: Call Invocation{ serviceName=3D'hz=
:impl:mapService', op=3Dcom.hazelcast.spi.impl.operationservice.impl.operat=
ions.IsStillExecutingOperation{serviceName=3D'hz:impl:mapService', partitio=
nId=3D-1, callId=3D2114, invocationTime=3D1480511190143, waitTimeout=3D-1, =
callTimeout=3D5000}, partitionId=3D-1, replicaIndex=3D0, tryCount=3D0, tryP=
auseMillis=3D0, invokeCount=3D1, callTimeout=3D5000, target=3DAddress[10.24=
9.50.79]:5701, backupsExpected=3D0, backupsCompleted=3D0} encountered a tim=
eout
>         at com.hazelcast.spi.impl.operationservice.impl.InvocationFuture.=
resolveApplicationResponse(InvocationFuture.java:366)[52:com.hazelcast:3.5.=
2]
>         at com.hazelcast.spi.impl.operationservice.impl.InvocationFuture.=
resolveApplicationResponseOrThrowException(InvocationFuture.java:334)[52:co=
m.hazelcast:3.5.2]
>         at com.hazelcast.spi.impl.operationservice.impl.InvocationFuture.=
get(InvocationFuture.java:225)[52:com.hazelcast:3.5.2]
>         at com.hazelcast.spi.impl.operationservice.impl.IsStillRunningSer=
vice.isOperationExecuting(IsStillRunningService.java:85)[52:com.hazelcast:3=
.5.2]
>         at com.hazelcast.spi.impl.operationservice.impl.InvocationFuture.=
waitForResponse(InvocationFuture.java:275)[52:com.hazelcast:3.5.2]
>         at com.hazelcast.spi.impl.operationservice.impl.InvocationFuture.=
get(InvocationFuture.java:224)[52:com.hazelcast:3.5.2]
>         at com.hazelcast.spi.impl.operationservice.impl.InvocationFuture.=
get(InvocationFuture.java:204)[52:com.hazelcast:3.5.2]
>         at com.hazelcast.map.impl.proxy.MapProxySupport.invokeOperation(M=
apProxySupport.java:456)[52:com.hazelcast:3.5.2]
>         at com.hazelcast.map.impl.proxy.MapProxySupport.putInternal(MapPr=
oxySupport.java:417)[52:com.hazelcast:3.5.2]
>         at com.hazelcast.map.impl.proxy.MapProxyImpl.put(MapProxyImpl.jav=
a:97)[52:com.hazelcast:3.5.2]
>         at com.hazelcast.map.impl.proxy.MapProxyImpl.put(MapProxyImpl.jav=
a:87)[52:com.hazelcast:3.5.2]
>         at com.fujitsu.fnc.emf.fpmplatform.cachemanager.HazelcastCacheMan=
agerMapServiceImpl.addToMap(HazelcastCacheManagerMapServiceImpl.java:87)[20=
9:FPMHazelcastCache:4.1.0.SNAPSHOT]
>         at Proxy1897a82c_c032_4a5c_9839_e71cb2af452a.addToMap(Unknown Sou=
rce)[:]
>         at com.fujitsu.fnc.ngemf.fm.server.impl.FpmConsumerTask.prepareJS=
ON(FpmConsumerTask.java:151)[235:com.fujitsu.fnc.ngemf.fm.server.impl:4.1.0=
.SNAPSHOT]
>         at com.fujitsu.fnc.ngemf.fm.server.impl.FpmConsumerTask.run(FpmCo=
nsumerTask.java:244)[235:com.fujitsu.fnc.ngemf.fm.server.impl:4.1.0.SNAPSHO=
T]
>         at java.util.concurrent.Executors$RunnableAdapter.call(Executors.=
java:511)[:1.8.0_66]
>         at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.=
0_66]
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolEx=
ecutor.java:1142)[:1.8.0_66]
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolE=
xecutor.java:617)[:1.8.0_66]
>         at java.lang.Thread.run(Thread.java:745)[:1.8.0_66]


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)