You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Ashish Paliwal (JIRA)" <ji...@apache.org> on 2014/11/05 10:35:34 UTC
[jira] [Resolved] (FLUME-517) FlumeMaster deadlock during
configuration of logical nodes
[ https://issues.apache.org/jira/browse/FLUME-517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ashish Paliwal resolved FLUME-517.
----------------------------------
Resolution: Won't Fix
Won't fix. 0.X branch not maintained anymore
> FlumeMaster deadlock during configuration of logical nodes
> ----------------------------------------------------------
>
> Key: FLUME-517
> URL: https://issues.apache.org/jira/browse/FLUME-517
> Project: Flume
> Issue Type: Bug
> Affects Versions: v0.9.4
> Reporter: Disabled imported user
> Fix For: v0.9.5
>
> Attachments: ASF.LICENSE.NOT.GRANTED--flume_dump.txt
>
>
> Occasionally I notice the FlumeMaster deadlocking when I run commands against the shell.
> I have attached the Thread Dump during one of the deadlocks.
> The following are the commands I run which 80% of the time execute without any problem.
> 0 SUCCEEDED decommission [collector0_rpc]
> 1 SUCCEEDED decommission [collector0_log_dir]
> 2 SUCCEEDED noop [10000]
> 3 SUCCEEDED config [collector0_rpc, rpcFlow, autoCollectorSource, collectorSink("hdfs://hadoop-name-node1.dc1.blah.net:9000/rpc/%Y-%m-%d/%H00/%{host}", "data-", 60000)]
> 4 SUCCEEDED config [collector0_log_dir, logDirFlow, autoCollectorSource, collectorSink("hdfs://hadoop-name-node1.dc1.blah.net:9000/logs/%Y-%m-%d/%H00/%{host}", "log-", 60000)]
> 5 SUCCEEDED spawn [hadoop-data-node5.dc1.blah.net, collector0_rpc]
> 6 SUCCEEDED spawn [hadoop-data-node5.dc1.blah.net, collector0_log_dir]
> 7 SUCCEEDED decommission [hadoop_agent0_log_dir_0]
> 8 SUCCEEDED decommission [hadoop_agent1_log_dir_0]
> 9 SUCCEEDED decommission [hadoop_agent2_rpc]
> 10 SUCCEEDED decommission [hadoop_agent0_rpc]
> 11 SUCCEEDED decommission [hadoop_agent1_rpc]
> 12 SUCCEEDED decommission [hadoop_agent2_log_dir_0]
> 13 SUCCEEDED noop [10000]
> 14 SUCCEEDED noop [10000]
> 15 SUCCEEDED noop [10000]
> 16 SUCCEEDED config [hadoop_agent0_log_dir_0, logDirFlow, tailDir("/opt/flume/logs"), autoE2EChain ]
> 17 SUCCEEDED config [hadoop_agent0_rpc, rpcFlow, rpcSource(36893), autoE2EChain ]
> 18 SUCCEEDED config [hadoop_agent1_log_dir_0, logDirFlow, tailDir("/opt/flume/logs"), autoE2EChain ]
> 19 SUCCEEDED config [hadoop_agent1_rpc, rpcFlow, rpcSource(36893), autoE2EChain ]
> 20 SUCCEEDED config [hadoop_agent2_rpc, rpcFlow, rpcSource(36893), autoE2EChain ]
> 21 SUCCEEDED config [hadoop_agent2_log_dir_0, logDirFlow, tailDir("/opt/flume/logs"), autoE2EChain ]
> 22 SUCCEEDED spawn [hadoop-data-node1.dc1.blah.net, hadoop_agent0_log_dir_0]
> 23 SUCCEEDED spawn [hadoop-data-node2.dc1.blah.net, hadoop_agent1_log_dir_0]
> 24 SUCCEEDED spawn [hadoop-data-node3.dc1.blah.net, hadoop_agent2_rpc]
> 25 SUCCEEDED spawn [hadoop-data-node1.dc1.blah.net, hadoop_agent0_rpc]
> 26 SUCCEEDED spawn [hadoop-data-node2.dc1.blah.net, hadoop_agent1_rpc]
> 27 SUCCEEDED spawn [hadoop-data-node3.dc1.blah.net, hadoop_agent2_log_dir_0]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)