Mailing-List: contact dev-help@flume.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flume.apache.org
Date: Thu, 3 Nov 2016 12:49:58 +0000 (UTC)
From: "Yan Jian (JIRA)" <jira@apache.org>
To: dev@flume.apache.org
Message-ID: <JIRA.12862435.1441723241000.172005.1478177398398@Atlassian.JIRA>
In-Reply-To: <JIRA.12862435.1441723241000@Atlassian.JIRA>
References: <JIRA.12862435.1441723241000@Atlassian.JIRA> <JIRA.12862435.1441723241089@arcas>
Subject: [jira] [Updated] (FLUME-2786)  It will enter a deadlock state when
 modify the conf file before I stop flume-ng
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Thu, 03 Nov 2016 12:50:00 -0000


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

Yan Jian updated FLUME-2786:
----------------------------
    Attachment: flume-2786-v1.6.0.test.patch
                flume-2786-v1.6.0.patch.1

Hi [~denes], Thanks for your reply. I am so sorry about missing the unit te=
st.
[^flume-2786-v1.6.0.patch.1] contains both fixing and unit test code.
As well, I uploaded a patch [^flume-2786-v1.6.0.test.patch] that only conta=
ins unit test code. Test wont be passed when apply [^flume-2786-v1.6.0.test=
.patch] to release-1.6.0.

>  It will enter a deadlock state when modify the conf file before I stop f=
lume-ng
> -------------------------------------------------------------------------=
-------
>
>                 Key: FLUME-2786
>                 URL: https://issues.apache.org/jira/browse/FLUME-2786
>             Project: Flume
>          Issue Type: Bug
>          Components: Master
>    Affects Versions: v1.6.0
>            Reporter: godfrey he
>            Priority: Blocker
>         Attachments: flume-2786-v1.6.0.patch, flume-2786-v1.6.0.patch.1, =
flume-2786-v1.6.0.test.patch
>
>
> When modify the conf file=EF=BC=8Cand then I stop the flume-ng,  It will =
enter a deadlock state.=20
> jstack result:
> "agent-shutdown-hook" prio=3D10 tid=3D0x00007f2e26419800 nid=3D0x333ae wa=
iting on condition [0x0000000042c16000]
>    java.lang.Thread.State: TIMED_WAITING (parking)
>         at sun.misc.Unsafe.park(Native Method)
>         - parking to wait for  <0x00000000eaff3df8> (a java.util.concurre=
nt.locks.AbstractQueuedSynchronizer$ConditionObject)
>         at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.j=
ava:226)
>         at java.util.concurrent.locks.AbstractQueuedSynchronizer$Conditio=
nObject.awaitNanos(AbstractQueuedSynchronizer.java:2082)
>         at java.util.concurrent.ThreadPoolExecutor.awaitTermination(Threa=
dPoolExecutor.java:1468)
>         at java.util.concurrent.Executors$DelegatedExecutorService.awaitT=
ermination(Executors.java:635)
>         at org.apache.flume.node.PollingPropertiesFileConfigurationProvid=
er.stop(PollingPropertiesFileConfigurationProvider.java:87)
>         at org.apache.flume.lifecycle.LifecycleSupervisor.stop(LifecycleS=
upervisor.java:106)
>         - locked <0x00000000eaf2daa0> (a org.apache.flume.lifecycle.Lifec=
ycleSupervisor)
>         at org.apache.flume.node.Application.stop(Application.java:93)
>         - locked <0x00000000eaf3c580> (a org.apache.flume.node.Applicatio=
n)
>         at org.apache.flume.node.Application$1.run(Application.java:348)
> "conf-file-poller-0" prio=3D10 tid=3D0x00007f2e2e8cd000 nid=3D0x21819 wai=
ting for monitor entry [0x0000000041e3f000]
>    java.lang.Thread.State: BLOCKED (on object monitor)
>         at org.apache.flume.node.Application.handleConfigurationEvent(App=
lication.java:88)
>         - waiting to lock <0x00000000eaf3c580> (a org.apache.flume.node.A=
pplication)


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)