[jira] [Commented] (HADOOP-12447) Clean up some htrace integration issues
[ https://issues.apache.org/jira/browse/HADOOP-12447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14943801#comment-14943801 ] Colin Patrick McCabe commented on HADOOP-12447: --- Thanks, [~iwasakims]. > Clean up some htrace integration issues > --- > > Key: HADOOP-12447 > URL: https://issues.apache.org/jira/browse/HADOOP-12447 > Project: Hadoop Common > Issue Type: Bug > Components: tracing >Affects Versions: 2.8.0 >Reporter: Colin Patrick McCabe >Assignee: Colin Patrick McCabe > Fix For: 2.8.0 > > Attachments: HADOOP-12447.002.patch > > > Clean up some htrace integration issues -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HADOOP-12364) Deleting pid file after stop is causing the daemons to keep restarting
[ https://issues.apache.org/jira/browse/HADOOP-12364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee updated HADOOP-12364: - Status: Patch Available (was: Open) > Deleting pid file after stop is causing the daemons to keep restarting > --- > > Key: HADOOP-12364 > URL: https://issues.apache.org/jira/browse/HADOOP-12364 > Project: Hadoop Common > Issue Type: Bug >Affects Versions: 2.6.0 >Reporter: Siqi Li >Assignee: Siqi Li >Priority: Minor > Attachments: HADOOP-12364.v1.patch > > > pid files are deleting in 5 seconds after we stop the daemons. If a start > command were executed within the 5 seconds, the pid file will be overwrite > with a new pid. However, this pid file is going to be deleted by the former > stop command. This is causing the monitoring service to lose track of the > daemons, hence keep rebooting them -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HADOOP-12452) Fix tracing documention reflecting the update to htrace-4
[ https://issues.apache.org/jira/browse/HADOOP-12452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin Patrick McCabe updated HADOOP-12452: -- Affects Version/s: 2.8.0 Target Version/s: 2.8.0 > Fix tracing documention reflecting the update to htrace-4 > - > > Key: HADOOP-12452 > URL: https://issues.apache.org/jira/browse/HADOOP-12452 > Project: Hadoop Common > Issue Type: Bug > Components: documentation >Affects Versions: 2.8.0 >Reporter: Masatake Iwasaki >Assignee: Masatake Iwasaki > Attachments: HADOOP-12452.001.patch > > > The sample code in Tracing.md have some problems. > * compilation error by not importing Tracer. > * generic options are not reflected because Tracer is initialized before > ToolRunner#run. > * it may be confusing to use FsShell in example because it has embedded > Tracer now. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HADOOP-12364) Deleting pid file after stop is causing the daemons to keep restarting
[ https://issues.apache.org/jira/browse/HADOOP-12364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee updated HADOOP-12364: - Assignee: Siqi Li > Deleting pid file after stop is causing the daemons to keep restarting > --- > > Key: HADOOP-12364 > URL: https://issues.apache.org/jira/browse/HADOOP-12364 > Project: Hadoop Common > Issue Type: Bug >Affects Versions: 2.6.0 >Reporter: Siqi Li >Assignee: Siqi Li >Priority: Minor > Attachments: HADOOP-12364.v1.patch > > > pid files are deleting in 5 seconds after we stop the daemons. If a start > command were executed within the 5 seconds, the pid file will be overwrite > with a new pid. However, this pid file is going to be deleted by the former > stop command. This is causing the monitoring service to lose track of the > daemons, hence keep rebooting them -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-12452) Fix tracing documention reflecting the update to htrace-4
[ https://issues.apache.org/jira/browse/HADOOP-12452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14943871#comment-14943871 ] Hudson commented on HADOOP-12452: - FAILURE: Integrated in Hadoop-Mapreduce-trunk #2425 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2425/]) HADOOP-12452. Fix tracing documention reflecting the update to htrace-4 (cmccabe: rev 3e1752f9fb762a8b3268247f0690374419b2c3a1) * hadoop-common-project/hadoop-common/CHANGES.txt * hadoop-common-project/hadoop-common/src/site/markdown/Tracing.md > Fix tracing documention reflecting the update to htrace-4 > - > > Key: HADOOP-12452 > URL: https://issues.apache.org/jira/browse/HADOOP-12452 > Project: Hadoop Common > Issue Type: Bug > Components: documentation >Affects Versions: 2.8.0 >Reporter: Masatake Iwasaki >Assignee: Masatake Iwasaki > Fix For: 2.8.0 > > Attachments: HADOOP-12452.001.patch > > > The sample code in Tracing.md have some problems. > * compilation error by not importing Tracer. > * generic options are not reflected because Tracer is initialized before > ToolRunner#run. > * it may be confusing to use FsShell in example because it has embedded > Tracer now. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-12441) Fix kill command behavior under some Linux distributions.
[
https://issues.apache.org/jira/browse/HADOOP-12441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14943739#comment-14943739
]
Vinod Kumar Vavilapalli commented on HADOOP-12441:
--
Both the RAT warning and the test failures are unrelated, will see if there are
tickets already.
Checking this in now.
> Fix kill command behavior under some Linux distributions.
> -
>
> Key: HADOOP-12441
> URL: https://issues.apache.org/jira/browse/HADOOP-12441
> Project: Hadoop Common
> Issue Type: Bug
>Reporter: Wangda Tan
>Assignee: Wangda Tan
>Priority: Critical
> Attachments: HADOOP-12441.1.patch, HADOOP-12441.2.patch,
> HADOOP-12441.4.patch
>
>
> After HADOOP-12317, kill command's execution will be failure under Ubuntu12.
> After NM restarts, it cannot get if a process is alive or not via pid of
> containers, and it cannot kill process correctly when RM/AM tells NM to kill
> a container.
> Logs from NM (customized logs):
> {code}
> 2015-09-25 21:58:59,348 INFO nodemanager.DefaultContainerExecutor
> (DefaultContainerExecutor.java:containerIsAlive(431)) - ==
> check alive cmd:[[Ljava.lang.String;@496e442d]
> 2015-09-25 21:58:59,349 INFO nodemanager.NMAuditLogger
> (NMAuditLogger.java:logSuccess(89)) - USER=hrt_qa IP=10.0.1.14
> OPERATION=Stop Container RequestTARGET=ContainerManageImpl
> RESULT=SUCCESS APPID=application_1443218269460_0001
> CONTAINERID=container_1443218269460_0001_01_01
> 2015-09-25 21:58:59,363 INFO nodemanager.DefaultContainerExecutor
> (DefaultContainerExecutor.java:containerIsAlive(438)) -
> ===
> ExitCodeException exitCode=1: ERROR: garbage process ID "--".
> Usage:
> kill pid ... Send SIGTERM to every process listed.
> kill signal pid ... Send a signal to every process listed.
> kill -s signal pid ...Send a signal to every process listed.
> kill -l List all signal names.
> kill -L List all signal names in a nice table.
> kill -l signalConvert between signal numbers and names.
> at org.apache.hadoop.util.Shell.runCommand(Shell.java:550)
> at org.apache.hadoop.util.Shell.run(Shell.java:461)
> at
> org.apache.hadoop.util.Shell$ShellCommandExecutor.execute(Shell.java:727)
> at
> org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor.containerIsAlive(DefaultContainerExecutor.java:432)
> at
> org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor.signalContainer(DefaultContainerExecutor.java:401)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainerLaunch.cleanupContainer(ContainerLaunch.java:419)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainersLauncher.handle(ContainersLauncher.java:139)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainersLauncher.handle(ContainersLauncher.java:55)
> at
> org.apache.hadoop.yarn.event.AsyncDispatcher.dispatch(AsyncDispatcher.java:175)
> at
> org.apache.hadoop.yarn.event.AsyncDispatcher$1.run(AsyncDispatcher.java:108)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HADOOP-12441) Fix kill command behavior under some Linux distributions.
[
https://issues.apache.org/jira/browse/HADOOP-12441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli updated HADOOP-12441:
-
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: 2.8.0
Status: Resolved (was: Patch Available)
Committed this to trunk and branch-2. Thanks Wangda!
> Fix kill command behavior under some Linux distributions.
> -
>
> Key: HADOOP-12441
> URL: https://issues.apache.org/jira/browse/HADOOP-12441
> Project: Hadoop Common
> Issue Type: Bug
>Reporter: Wangda Tan
>Assignee: Wangda Tan
>Priority: Critical
> Fix For: 2.8.0
>
> Attachments: HADOOP-12441.1.patch, HADOOP-12441.2.patch,
> HADOOP-12441.4.patch
>
>
> After HADOOP-12317, kill command's execution will be failure under Ubuntu12.
> After NM restarts, it cannot get if a process is alive or not via pid of
> containers, and it cannot kill process correctly when RM/AM tells NM to kill
> a container.
> Logs from NM (customized logs):
> {code}
> 2015-09-25 21:58:59,348 INFO nodemanager.DefaultContainerExecutor
> (DefaultContainerExecutor.java:containerIsAlive(431)) - ==
> check alive cmd:[[Ljava.lang.String;@496e442d]
> 2015-09-25 21:58:59,349 INFO nodemanager.NMAuditLogger
> (NMAuditLogger.java:logSuccess(89)) - USER=hrt_qa IP=10.0.1.14
> OPERATION=Stop Container RequestTARGET=ContainerManageImpl
> RESULT=SUCCESS APPID=application_1443218269460_0001
> CONTAINERID=container_1443218269460_0001_01_01
> 2015-09-25 21:58:59,363 INFO nodemanager.DefaultContainerExecutor
> (DefaultContainerExecutor.java:containerIsAlive(438)) -
> ===
> ExitCodeException exitCode=1: ERROR: garbage process ID "--".
> Usage:
> kill pid ... Send SIGTERM to every process listed.
> kill signal pid ... Send a signal to every process listed.
> kill -s signal pid ...Send a signal to every process listed.
> kill -l List all signal names.
> kill -L List all signal names in a nice table.
> kill -l signalConvert between signal numbers and names.
> at org.apache.hadoop.util.Shell.runCommand(Shell.java:550)
> at org.apache.hadoop.util.Shell.run(Shell.java:461)
> at
> org.apache.hadoop.util.Shell$ShellCommandExecutor.execute(Shell.java:727)
> at
> org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor.containerIsAlive(DefaultContainerExecutor.java:432)
> at
> org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor.signalContainer(DefaultContainerExecutor.java:401)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainerLaunch.cleanupContainer(ContainerLaunch.java:419)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainersLauncher.handle(ContainersLauncher.java:139)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainersLauncher.handle(ContainersLauncher.java:55)
> at
> org.apache.hadoop.yarn.event.AsyncDispatcher.dispatch(AsyncDispatcher.java:175)
> at
> org.apache.hadoop.yarn.event.AsyncDispatcher$1.run(AsyncDispatcher.java:108)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-12441) Fix kill command behavior under some Linux distributions.
[
https://issues.apache.org/jira/browse/HADOOP-12441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14943870#comment-14943870
]
Hudson commented on HADOOP-12441:
-
FAILURE: Integrated in Hadoop-Mapreduce-trunk #2425 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2425/])
HADOOP-12441. Fixed shell-kill command behaviour to work correctly on (vinodkv:
rev f1c19b9365cbac88e45a9eed516fbfc6c9aa9947)
*
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/NodeManager.java
*
hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/util/TestShell.java
* hadoop-common-project/hadoop-common/CHANGES.txt
*
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/util/Shell.java
> Fix kill command behavior under some Linux distributions.
> -
>
> Key: HADOOP-12441
> URL: https://issues.apache.org/jira/browse/HADOOP-12441
> Project: Hadoop Common
> Issue Type: Bug
>Reporter: Wangda Tan
>Assignee: Wangda Tan
>Priority: Critical
> Fix For: 2.8.0
>
> Attachments: HADOOP-12441.1.patch, HADOOP-12441.2.patch,
> HADOOP-12441.4.patch
>
>
> After HADOOP-12317, kill command's execution will be failure under Ubuntu12.
> After NM restarts, it cannot get if a process is alive or not via pid of
> containers, and it cannot kill process correctly when RM/AM tells NM to kill
> a container.
> Logs from NM (customized logs):
> {code}
> 2015-09-25 21:58:59,348 INFO nodemanager.DefaultContainerExecutor
> (DefaultContainerExecutor.java:containerIsAlive(431)) - ==
> check alive cmd:[[Ljava.lang.String;@496e442d]
> 2015-09-25 21:58:59,349 INFO nodemanager.NMAuditLogger
> (NMAuditLogger.java:logSuccess(89)) - USER=hrt_qa IP=10.0.1.14
> OPERATION=Stop Container RequestTARGET=ContainerManageImpl
> RESULT=SUCCESS APPID=application_1443218269460_0001
> CONTAINERID=container_1443218269460_0001_01_01
> 2015-09-25 21:58:59,363 INFO nodemanager.DefaultContainerExecutor
> (DefaultContainerExecutor.java:containerIsAlive(438)) -
> ===
> ExitCodeException exitCode=1: ERROR: garbage process ID "--".
> Usage:
> kill pid ... Send SIGTERM to every process listed.
> kill signal pid ... Send a signal to every process listed.
> kill -s signal pid ...Send a signal to every process listed.
> kill -l List all signal names.
> kill -L List all signal names in a nice table.
> kill -l signalConvert between signal numbers and names.
> at org.apache.hadoop.util.Shell.runCommand(Shell.java:550)
> at org.apache.hadoop.util.Shell.run(Shell.java:461)
> at
> org.apache.hadoop.util.Shell$ShellCommandExecutor.execute(Shell.java:727)
> at
> org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor.containerIsAlive(DefaultContainerExecutor.java:432)
> at
> org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor.signalContainer(DefaultContainerExecutor.java:401)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainerLaunch.cleanupContainer(ContainerLaunch.java:419)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainersLauncher.handle(ContainersLauncher.java:139)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainersLauncher.handle(ContainersLauncher.java:55)
> at
> org.apache.hadoop.yarn.event.AsyncDispatcher.dispatch(AsyncDispatcher.java:175)
> at
> org.apache.hadoop.yarn.event.AsyncDispatcher$1.run(AsyncDispatcher.java:108)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HADOOP-12452) Fix tracing documention reflecting the update to htrace-4
[ https://issues.apache.org/jira/browse/HADOOP-12452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin Patrick McCabe updated HADOOP-12452: -- Resolution: Fixed Fix Version/s: 2.8.0 Status: Resolved (was: Patch Available) > Fix tracing documention reflecting the update to htrace-4 > - > > Key: HADOOP-12452 > URL: https://issues.apache.org/jira/browse/HADOOP-12452 > Project: Hadoop Common > Issue Type: Bug > Components: documentation >Affects Versions: 2.8.0 >Reporter: Masatake Iwasaki >Assignee: Masatake Iwasaki > Fix For: 2.8.0 > > Attachments: HADOOP-12452.001.patch > > > The sample code in Tracing.md have some problems. > * compilation error by not importing Tracer. > * generic options are not reflected because Tracer is initialized before > ToolRunner#run. > * it may be confusing to use FsShell in example because it has embedded > Tracer now. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-12441) Fix kill command behavior under some Linux distributions.
[
https://issues.apache.org/jira/browse/HADOOP-12441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14943758#comment-14943758
]
Hudson commented on HADOOP-12441:
-
FAILURE: Integrated in Hadoop-trunk-Commit #8569 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/8569/])
HADOOP-12441. Fixed shell-kill command behaviour to work correctly on (vinodkv:
rev f1c19b9365cbac88e45a9eed516fbfc6c9aa9947)
* hadoop-common-project/hadoop-common/CHANGES.txt
*
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/util/Shell.java
*
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/NodeManager.java
*
hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/util/TestShell.java
> Fix kill command behavior under some Linux distributions.
> -
>
> Key: HADOOP-12441
> URL: https://issues.apache.org/jira/browse/HADOOP-12441
> Project: Hadoop Common
> Issue Type: Bug
>Reporter: Wangda Tan
>Assignee: Wangda Tan
>Priority: Critical
> Fix For: 2.8.0
>
> Attachments: HADOOP-12441.1.patch, HADOOP-12441.2.patch,
> HADOOP-12441.4.patch
>
>
> After HADOOP-12317, kill command's execution will be failure under Ubuntu12.
> After NM restarts, it cannot get if a process is alive or not via pid of
> containers, and it cannot kill process correctly when RM/AM tells NM to kill
> a container.
> Logs from NM (customized logs):
> {code}
> 2015-09-25 21:58:59,348 INFO nodemanager.DefaultContainerExecutor
> (DefaultContainerExecutor.java:containerIsAlive(431)) - ==
> check alive cmd:[[Ljava.lang.String;@496e442d]
> 2015-09-25 21:58:59,349 INFO nodemanager.NMAuditLogger
> (NMAuditLogger.java:logSuccess(89)) - USER=hrt_qa IP=10.0.1.14
> OPERATION=Stop Container RequestTARGET=ContainerManageImpl
> RESULT=SUCCESS APPID=application_1443218269460_0001
> CONTAINERID=container_1443218269460_0001_01_01
> 2015-09-25 21:58:59,363 INFO nodemanager.DefaultContainerExecutor
> (DefaultContainerExecutor.java:containerIsAlive(438)) -
> ===
> ExitCodeException exitCode=1: ERROR: garbage process ID "--".
> Usage:
> kill pid ... Send SIGTERM to every process listed.
> kill signal pid ... Send a signal to every process listed.
> kill -s signal pid ...Send a signal to every process listed.
> kill -l List all signal names.
> kill -L List all signal names in a nice table.
> kill -l signalConvert between signal numbers and names.
> at org.apache.hadoop.util.Shell.runCommand(Shell.java:550)
> at org.apache.hadoop.util.Shell.run(Shell.java:461)
> at
> org.apache.hadoop.util.Shell$ShellCommandExecutor.execute(Shell.java:727)
> at
> org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor.containerIsAlive(DefaultContainerExecutor.java:432)
> at
> org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor.signalContainer(DefaultContainerExecutor.java:401)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainerLaunch.cleanupContainer(ContainerLaunch.java:419)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainersLauncher.handle(ContainersLauncher.java:139)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainersLauncher.handle(ContainersLauncher.java:55)
> at
> org.apache.hadoop.yarn.event.AsyncDispatcher.dispatch(AsyncDispatcher.java:175)
> at
> org.apache.hadoop.yarn.event.AsyncDispatcher$1.run(AsyncDispatcher.java:108)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-12452) Fix tracing documention reflecting the update to htrace-4
[ https://issues.apache.org/jira/browse/HADOOP-12452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14943794#comment-14943794 ] Colin Patrick McCabe commented on HADOOP-12452: --- +1. Thanks, [~iwasakims]. > Fix tracing documention reflecting the update to htrace-4 > - > > Key: HADOOP-12452 > URL: https://issues.apache.org/jira/browse/HADOOP-12452 > Project: Hadoop Common > Issue Type: Bug > Components: documentation >Affects Versions: 2.8.0 >Reporter: Masatake Iwasaki >Assignee: Masatake Iwasaki > Attachments: HADOOP-12452.001.patch > > > The sample code in Tracing.md have some problems. > * compilation error by not importing Tracer. > * generic options are not reflected because Tracer is initialized before > ToolRunner#run. > * it may be confusing to use FsShell in example because it has embedded > Tracer now. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-12452) Fix tracing documention reflecting the update to htrace-4
[ https://issues.apache.org/jira/browse/HADOOP-12452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14943843#comment-14943843 ] Hudson commented on HADOOP-12452: - FAILURE: Integrated in Hadoop-trunk-Commit #8570 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/8570/]) HADOOP-12452. Fix tracing documention reflecting the update to htrace-4 (cmccabe: rev 3e1752f9fb762a8b3268247f0690374419b2c3a1) * hadoop-common-project/hadoop-common/CHANGES.txt * hadoop-common-project/hadoop-common/src/site/markdown/Tracing.md > Fix tracing documention reflecting the update to htrace-4 > - > > Key: HADOOP-12452 > URL: https://issues.apache.org/jira/browse/HADOOP-12452 > Project: Hadoop Common > Issue Type: Bug > Components: documentation >Affects Versions: 2.8.0 >Reporter: Masatake Iwasaki >Assignee: Masatake Iwasaki > Fix For: 2.8.0 > > Attachments: HADOOP-12452.001.patch > > > The sample code in Tracing.md have some problems. > * compilation error by not importing Tracer. > * generic options are not reflected because Tracer is initialized before > ToolRunner#run. > * it may be confusing to use FsShell in example because it has embedded > Tracer now. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-12350) WASB Logging: Improve WASB Logging around deletes, reads and writes
[ https://issues.apache.org/jira/browse/HADOOP-12350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14944523#comment-14944523 ] Hudson commented on HADOOP-12350: - FAILURE: Integrated in Hadoop-trunk-Commit #8574 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/8574/]) HADOOP-12350. WASB Logging: Improve WASB Logging around deletes, reads (cnauroth: rev 5f6edb30c2bb648d5564c951edc25645e17e6636) * hadoop-tools/hadoop-azure/src/main/java/org/apache/hadoop/fs/azure/NativeAzureFileSystem.java * hadoop-tools/hadoop-azure/src/main/java/org/apache/hadoop/fs/azure/AzureNativeFileSystemStore.java * hadoop-common-project/hadoop-common/CHANGES.txt > WASB Logging: Improve WASB Logging around deletes, reads and writes > --- > > Key: HADOOP-12350 > URL: https://issues.apache.org/jira/browse/HADOOP-12350 > Project: Hadoop Common > Issue Type: Improvement > Components: tools >Reporter: Dushyanth >Assignee: Dushyanth > Fix For: 2.8.0 > > Attachments: 0001-HADOOP-12350-Added-WASB-Logging-Statement.patch, > 0001-HADOOP-12350-Improve-WASB-Logging-Itr3.patch, > 0001-HADOOP-12350-Moving-from-commons.logging-to-slf4j-lo.patch, > HADOOP-12350.004.patch, HADOOP-12350.005.patch, HADOOP-12350.006.patch, > HADOOP-12350.007.patch > > > Logging around the WASB component is very limited and it is disabled by > default. This improvement is created to add logging around Reads, Writes and > Deletes when Azure Storage Exception to capture the blobs that hit the > exception. This information is useful while communicating with the Azure > storage team for debugging purposes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-12350) WASB Logging: Improve WASB Logging around deletes, reads and writes
[ https://issues.apache.org/jira/browse/HADOOP-12350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14944538#comment-14944538 ] Hudson commented on HADOOP-12350: - FAILURE: Integrated in Hadoop-Yarn-trunk #1223 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/1223/]) HADOOP-12350. WASB Logging: Improve WASB Logging around deletes, reads (cnauroth: rev 5f6edb30c2bb648d5564c951edc25645e17e6636) * hadoop-tools/hadoop-azure/src/main/java/org/apache/hadoop/fs/azure/NativeAzureFileSystem.java * hadoop-tools/hadoop-azure/src/main/java/org/apache/hadoop/fs/azure/AzureNativeFileSystemStore.java * hadoop-common-project/hadoop-common/CHANGES.txt > WASB Logging: Improve WASB Logging around deletes, reads and writes > --- > > Key: HADOOP-12350 > URL: https://issues.apache.org/jira/browse/HADOOP-12350 > Project: Hadoop Common > Issue Type: Improvement > Components: tools >Reporter: Dushyanth >Assignee: Dushyanth > Fix For: 2.8.0 > > Attachments: 0001-HADOOP-12350-Added-WASB-Logging-Statement.patch, > 0001-HADOOP-12350-Improve-WASB-Logging-Itr3.patch, > 0001-HADOOP-12350-Moving-from-commons.logging-to-slf4j-lo.patch, > HADOOP-12350.004.patch, HADOOP-12350.005.patch, HADOOP-12350.006.patch, > HADOOP-12350.007.patch > > > Logging around the WASB component is very limited and it is disabled by > default. This improvement is created to add logging around Reads, Writes and > Deletes when Azure Storage Exception to capture the blobs that hit the > exception. This information is useful while communicating with the Azure > storage team for debugging purposes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HADOOP-12350) WASB Logging: Improve WASB Logging around deletes, reads and writes
[ https://issues.apache.org/jira/browse/HADOOP-12350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HADOOP-12350: --- Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) +1 for patch v007. I confirmed once again that the test failure was unrelated and already tracked in existing JIRAs. I have committed this to trunk and branch-2. [~dchickabasapa], thank you for the contribution. > WASB Logging: Improve WASB Logging around deletes, reads and writes > --- > > Key: HADOOP-12350 > URL: https://issues.apache.org/jira/browse/HADOOP-12350 > Project: Hadoop Common > Issue Type: Improvement > Components: tools >Reporter: Dushyanth >Assignee: Dushyanth > Fix For: 2.8.0 > > Attachments: 0001-HADOOP-12350-Added-WASB-Logging-Statement.patch, > 0001-HADOOP-12350-Improve-WASB-Logging-Itr3.patch, > 0001-HADOOP-12350-Moving-from-commons.logging-to-slf4j-lo.patch, > HADOOP-12350.004.patch, HADOOP-12350.005.patch, HADOOP-12350.006.patch, > HADOOP-12350.007.patch > > > Logging around the WASB component is very limited and it is disabled by > default. This improvement is created to add logging around Reads, Writes and > Deletes when Azure Storage Exception to capture the blobs that hit the > exception. This information is useful while communicating with the Azure > storage team for debugging purposes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-12364) Deleting pid file after stop is causing the daemons to keep restarting
[
https://issues.apache.org/jira/browse/HADOOP-12364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14943911#comment-14943911
]
Hadoop QA commented on HADOOP-12364:
\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:red}-1{color} | patch | 0m 0s | The patch command could not apply
the patch during dryrun. |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL |
http://issues.apache.org/jira/secure/attachment/12753048/HADOOP-12364.v1.patch |
| Optional Tests | shellcheck |
| git revision | trunk / 3e1752f |
| Console output |
https://builds.apache.org/job/PreCommit-HADOOP-Build/7768/console |
This message was automatically generated.
> Deleting pid file after stop is causing the daemons to keep restarting
> ---
>
> Key: HADOOP-12364
> URL: https://issues.apache.org/jira/browse/HADOOP-12364
> Project: Hadoop Common
> Issue Type: Bug
>Affects Versions: 2.6.0
>Reporter: Siqi Li
>Assignee: Siqi Li
>Priority: Minor
> Attachments: HADOOP-12364.v1.patch
>
>
> pid files are deleting in 5 seconds after we stop the daemons. If a start
> command were executed within the 5 seconds, the pid file will be overwrite
> with a new pid. However, this pid file is going to be deleted by the former
> stop command. This is causing the monitoring service to lose track of the
> daemons, hence keep rebooting them
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-12441) Fix kill command behavior under some Linux distributions.
[
https://issues.apache.org/jira/browse/HADOOP-12441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14943958#comment-14943958
]
Wangda Tan commented on HADOOP-12441:
-
Thanks for Vinod's review and commit!
> Fix kill command behavior under some Linux distributions.
> -
>
> Key: HADOOP-12441
> URL: https://issues.apache.org/jira/browse/HADOOP-12441
> Project: Hadoop Common
> Issue Type: Bug
>Reporter: Wangda Tan
>Assignee: Wangda Tan
>Priority: Critical
> Fix For: 2.8.0
>
> Attachments: HADOOP-12441.1.patch, HADOOP-12441.2.patch,
> HADOOP-12441.4.patch
>
>
> After HADOOP-12317, kill command's execution will be failure under Ubuntu12.
> After NM restarts, it cannot get if a process is alive or not via pid of
> containers, and it cannot kill process correctly when RM/AM tells NM to kill
> a container.
> Logs from NM (customized logs):
> {code}
> 2015-09-25 21:58:59,348 INFO nodemanager.DefaultContainerExecutor
> (DefaultContainerExecutor.java:containerIsAlive(431)) - ==
> check alive cmd:[[Ljava.lang.String;@496e442d]
> 2015-09-25 21:58:59,349 INFO nodemanager.NMAuditLogger
> (NMAuditLogger.java:logSuccess(89)) - USER=hrt_qa IP=10.0.1.14
> OPERATION=Stop Container RequestTARGET=ContainerManageImpl
> RESULT=SUCCESS APPID=application_1443218269460_0001
> CONTAINERID=container_1443218269460_0001_01_01
> 2015-09-25 21:58:59,363 INFO nodemanager.DefaultContainerExecutor
> (DefaultContainerExecutor.java:containerIsAlive(438)) -
> ===
> ExitCodeException exitCode=1: ERROR: garbage process ID "--".
> Usage:
> kill pid ... Send SIGTERM to every process listed.
> kill signal pid ... Send a signal to every process listed.
> kill -s signal pid ...Send a signal to every process listed.
> kill -l List all signal names.
> kill -L List all signal names in a nice table.
> kill -l signalConvert between signal numbers and names.
> at org.apache.hadoop.util.Shell.runCommand(Shell.java:550)
> at org.apache.hadoop.util.Shell.run(Shell.java:461)
> at
> org.apache.hadoop.util.Shell$ShellCommandExecutor.execute(Shell.java:727)
> at
> org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor.containerIsAlive(DefaultContainerExecutor.java:432)
> at
> org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor.signalContainer(DefaultContainerExecutor.java:401)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainerLaunch.cleanupContainer(ContainerLaunch.java:419)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainersLauncher.handle(ContainersLauncher.java:139)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainersLauncher.handle(ContainersLauncher.java:55)
> at
> org.apache.hadoop.yarn.event.AsyncDispatcher.dispatch(AsyncDispatcher.java:175)
> at
> org.apache.hadoop.yarn.event.AsyncDispatcher$1.run(AsyncDispatcher.java:108)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HADOOP-12350) WASB Logging: Improve WASB Logging around deletes, reads and writes
[ https://issues.apache.org/jira/browse/HADOOP-12350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dushyanth updated HADOOP-12350: --- Attachment: HADOOP-12350.007.patch Attaching with the tab character style check warning fix. > WASB Logging: Improve WASB Logging around deletes, reads and writes > --- > > Key: HADOOP-12350 > URL: https://issues.apache.org/jira/browse/HADOOP-12350 > Project: Hadoop Common > Issue Type: Improvement > Components: tools >Reporter: Dushyanth >Assignee: Dushyanth > Fix For: 2.8.0 > > Attachments: 0001-HADOOP-12350-Added-WASB-Logging-Statement.patch, > 0001-HADOOP-12350-Improve-WASB-Logging-Itr3.patch, > 0001-HADOOP-12350-Moving-from-commons.logging-to-slf4j-lo.patch, > HADOOP-12350.004.patch, HADOOP-12350.005.patch, HADOOP-12350.006.patch, > HADOOP-12350.007.patch > > > Logging around the WASB component is very limited and it is disabled by > default. This improvement is created to add logging around Reads, Writes and > Deletes when Azure Storage Exception to capture the blobs that hit the > exception. This information is useful while communicating with the Azure > storage team for debugging purposes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-12436) GlobPattern regex library has performance issues with wildcard characters
[
https://issues.apache.org/jira/browse/HADOOP-12436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14943888#comment-14943888
]
Colin Patrick McCabe commented on HADOOP-12436:
---
Thanks for this, [~mattpaduano].
I don't think there are any API issues since {{GlobPattern}} has
{{InterfaceAnnotation private}}.
I do think adding a new dependency could be messy and we should consider
shading it, since it seems like a small utility library.
> GlobPattern regex library has performance issues with wildcard characters
> -
>
> Key: HADOOP-12436
> URL: https://issues.apache.org/jira/browse/HADOOP-12436
> Project: Hadoop Common
> Issue Type: Improvement
> Components: fs
>Affects Versions: 2.2.0, 2.7.1
>Reporter: Matthew Paduano
>Assignee: Matthew Paduano
> Attachments: HADOOP-12436.01.patch
>
>
> java.util.regex classes have performance problems with certain wildcard
> patterns. Namely, consecutive * characters in a file name (not properly
> escaped as literals) will cause commands such as "hadoop fs -ls
> file**name" to consume 100% CPU and probably never return in a reasonable
> time (time scales with number of *'s).
> Here is an example:
> {noformat}
> hadoop fs -touchz
> /user/mattp/job_1429571161900_4222-1430338332599-tda%2D%2D\\\+\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\*\\\+\\\+\\\+...%270%27%28Stage-1430338580443-39-2000-SUCCEEDED-production%2Dhigh-1430338340360.jhist
> hadoop fs -ls
> /user/mattp/job_1429571161900_4222-1430338332599-tda%2D%2D+**+++...%270%27%28Stage-1430338580443-39-2000-SUCCEEDED-production%2Dhigh-1430338340360.jhist
> {noformat}
> causes:
> {noformat}
> PIDCOMMAND %CPU TIME
> 14526 java 100.0 01:18.85
> {noformat}
> Not every string of *'s causes this, but the above filename reproduces this
> reliably.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-12441) Fix kill command behavior under some Linux distributions.
[
https://issues.apache.org/jira/browse/HADOOP-12441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14943982#comment-14943982
]
Hudson commented on HADOOP-12441:
-
FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #481 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/481/])
HADOOP-12441. Fixed shell-kill command behaviour to work correctly on (vinodkv:
rev f1c19b9365cbac88e45a9eed516fbfc6c9aa9947)
*
hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/util/TestShell.java
*
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/util/Shell.java
* hadoop-common-project/hadoop-common/CHANGES.txt
*
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/NodeManager.java
> Fix kill command behavior under some Linux distributions.
> -
>
> Key: HADOOP-12441
> URL: https://issues.apache.org/jira/browse/HADOOP-12441
> Project: Hadoop Common
> Issue Type: Bug
>Reporter: Wangda Tan
>Assignee: Wangda Tan
>Priority: Critical
> Fix For: 2.8.0
>
> Attachments: HADOOP-12441.1.patch, HADOOP-12441.2.patch,
> HADOOP-12441.4.patch
>
>
> After HADOOP-12317, kill command's execution will be failure under Ubuntu12.
> After NM restarts, it cannot get if a process is alive or not via pid of
> containers, and it cannot kill process correctly when RM/AM tells NM to kill
> a container.
> Logs from NM (customized logs):
> {code}
> 2015-09-25 21:58:59,348 INFO nodemanager.DefaultContainerExecutor
> (DefaultContainerExecutor.java:containerIsAlive(431)) - ==
> check alive cmd:[[Ljava.lang.String;@496e442d]
> 2015-09-25 21:58:59,349 INFO nodemanager.NMAuditLogger
> (NMAuditLogger.java:logSuccess(89)) - USER=hrt_qa IP=10.0.1.14
> OPERATION=Stop Container RequestTARGET=ContainerManageImpl
> RESULT=SUCCESS APPID=application_1443218269460_0001
> CONTAINERID=container_1443218269460_0001_01_01
> 2015-09-25 21:58:59,363 INFO nodemanager.DefaultContainerExecutor
> (DefaultContainerExecutor.java:containerIsAlive(438)) -
> ===
> ExitCodeException exitCode=1: ERROR: garbage process ID "--".
> Usage:
> kill pid ... Send SIGTERM to every process listed.
> kill signal pid ... Send a signal to every process listed.
> kill -s signal pid ...Send a signal to every process listed.
> kill -l List all signal names.
> kill -L List all signal names in a nice table.
> kill -l signalConvert between signal numbers and names.
> at org.apache.hadoop.util.Shell.runCommand(Shell.java:550)
> at org.apache.hadoop.util.Shell.run(Shell.java:461)
> at
> org.apache.hadoop.util.Shell$ShellCommandExecutor.execute(Shell.java:727)
> at
> org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor.containerIsAlive(DefaultContainerExecutor.java:432)
> at
> org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor.signalContainer(DefaultContainerExecutor.java:401)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainerLaunch.cleanupContainer(ContainerLaunch.java:419)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainersLauncher.handle(ContainersLauncher.java:139)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainersLauncher.handle(ContainersLauncher.java:55)
> at
> org.apache.hadoop.yarn.event.AsyncDispatcher.dispatch(AsyncDispatcher.java:175)
> at
> org.apache.hadoop.yarn.event.AsyncDispatcher$1.run(AsyncDispatcher.java:108)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HADOOP-10949) metrics2 sink plugin for Apache Kafka
[ https://issues.apache.org/jira/browse/HADOOP-10949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated HADOOP-10949: -- Summary: metrics2 sink plugin for Apache Kafka (was: Write metrics2 sink plugin for Apache Kafka -- KafkaSink) > metrics2 sink plugin for Apache Kafka > - > > Key: HADOOP-10949 > URL: https://issues.apache.org/jira/browse/HADOOP-10949 > Project: Hadoop Common > Issue Type: New Feature > Components: metrics >Reporter: Babak Behzad >Assignee: Babak Behzad > Attachments: HADOOP-10949-1.patch, HADOOP-10949-2.patch, > HADOOP-10949-4.patch, HADOOP-10949-5.patch, HADOOP-10949-6.patch, > HADOOP-10949.patch, HADOOP-10949.patch, HADOOP-10949.patch, > HADOOP-10949.patch, HADOOP-10949.patch, HADOOP-10949.patch, > HADOOP-10949.patch, HADOOP-10949.patch, HADOOP-10949.patch, > HADOOP-10949.patch, HADOOP-10949.patch > > > Write a metrics2 sink plugin for Hadoop to send metrics directly to Apache > Kafka in addition to the current, Graphite > ([Hadoop-9704|https://issues.apache.org/jira/browse/HADOOP-9704]), Ganglia > and File sinks. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HADOOP-10709) Reuse Filters across web apps
[ https://issues.apache.org/jira/browse/HADOOP-10709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoy Antony updated HADOOP-10709: -- Status: Patch Available (was: Open) > Reuse Filters across web apps > - > > Key: HADOOP-10709 > URL: https://issues.apache.org/jira/browse/HADOOP-10709 > Project: Hadoop Common > Issue Type: Improvement > Components: security >Reporter: Benoy Antony >Assignee: Benoy Antony > Attachments: HADOOP-10709-002.patch, HADOOP-10709-003.patch, > HADOOP-10709.patch, configForFilterReuse.xml > > > Currently, we need to define separate authentication filters for webhdfs and > general webui. This also involves defining parameters for those filters. > It will be better if one could reuse filters for web apps if desired. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HADOOP-10709) Reuse Filters across web apps
[ https://issues.apache.org/jira/browse/HADOOP-10709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoy Antony updated HADOOP-10709: -- Status: Open (was: Patch Available) > Reuse Filters across web apps > - > > Key: HADOOP-10709 > URL: https://issues.apache.org/jira/browse/HADOOP-10709 > Project: Hadoop Common > Issue Type: Improvement > Components: security >Reporter: Benoy Antony >Assignee: Benoy Antony > Attachments: HADOOP-10709-002.patch, HADOOP-10709-003.patch, > HADOOP-10709.patch, configForFilterReuse.xml > > > Currently, we need to define separate authentication filters for webhdfs and > general webui. This also involves defining parameters for those filters. > It will be better if one could reuse filters for web apps if desired. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-12441) Fix kill command behavior under some Linux distributions.
[
https://issues.apache.org/jira/browse/HADOOP-12441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14943962#comment-14943962
]
Hudson commented on HADOOP-12441:
-
SUCCESS: Integrated in Hadoop-Yarn-trunk-Java8 #489 (See
[https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/489/])
HADOOP-12441. Fixed shell-kill command behaviour to work correctly on (vinodkv:
rev f1c19b9365cbac88e45a9eed516fbfc6c9aa9947)
*
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/NodeManager.java
* hadoop-common-project/hadoop-common/CHANGES.txt
*
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/util/Shell.java
*
hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/util/TestShell.java
> Fix kill command behavior under some Linux distributions.
> -
>
> Key: HADOOP-12441
> URL: https://issues.apache.org/jira/browse/HADOOP-12441
> Project: Hadoop Common
> Issue Type: Bug
>Reporter: Wangda Tan
>Assignee: Wangda Tan
>Priority: Critical
> Fix For: 2.8.0
>
> Attachments: HADOOP-12441.1.patch, HADOOP-12441.2.patch,
> HADOOP-12441.4.patch
>
>
> After HADOOP-12317, kill command's execution will be failure under Ubuntu12.
> After NM restarts, it cannot get if a process is alive or not via pid of
> containers, and it cannot kill process correctly when RM/AM tells NM to kill
> a container.
> Logs from NM (customized logs):
> {code}
> 2015-09-25 21:58:59,348 INFO nodemanager.DefaultContainerExecutor
> (DefaultContainerExecutor.java:containerIsAlive(431)) - ==
> check alive cmd:[[Ljava.lang.String;@496e442d]
> 2015-09-25 21:58:59,349 INFO nodemanager.NMAuditLogger
> (NMAuditLogger.java:logSuccess(89)) - USER=hrt_qa IP=10.0.1.14
> OPERATION=Stop Container RequestTARGET=ContainerManageImpl
> RESULT=SUCCESS APPID=application_1443218269460_0001
> CONTAINERID=container_1443218269460_0001_01_01
> 2015-09-25 21:58:59,363 INFO nodemanager.DefaultContainerExecutor
> (DefaultContainerExecutor.java:containerIsAlive(438)) -
> ===
> ExitCodeException exitCode=1: ERROR: garbage process ID "--".
> Usage:
> kill pid ... Send SIGTERM to every process listed.
> kill signal pid ... Send a signal to every process listed.
> kill -s signal pid ...Send a signal to every process listed.
> kill -l List all signal names.
> kill -L List all signal names in a nice table.
> kill -l signalConvert between signal numbers and names.
> at org.apache.hadoop.util.Shell.runCommand(Shell.java:550)
> at org.apache.hadoop.util.Shell.run(Shell.java:461)
> at
> org.apache.hadoop.util.Shell$ShellCommandExecutor.execute(Shell.java:727)
> at
> org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor.containerIsAlive(DefaultContainerExecutor.java:432)
> at
> org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor.signalContainer(DefaultContainerExecutor.java:401)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainerLaunch.cleanupContainer(ContainerLaunch.java:419)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainersLauncher.handle(ContainersLauncher.java:139)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainersLauncher.handle(ContainersLauncher.java:55)
> at
> org.apache.hadoop.yarn.event.AsyncDispatcher.dispatch(AsyncDispatcher.java:175)
> at
> org.apache.hadoop.yarn.event.AsyncDispatcher$1.run(AsyncDispatcher.java:108)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-12452) Fix tracing documention reflecting the update to htrace-4
[ https://issues.apache.org/jira/browse/HADOOP-12452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14943963#comment-14943963 ] Hudson commented on HADOOP-12452: - SUCCESS: Integrated in Hadoop-Yarn-trunk-Java8 #489 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/489/]) HADOOP-12452. Fix tracing documention reflecting the update to htrace-4 (cmccabe: rev 3e1752f9fb762a8b3268247f0690374419b2c3a1) * hadoop-common-project/hadoop-common/src/site/markdown/Tracing.md * hadoop-common-project/hadoop-common/CHANGES.txt > Fix tracing documention reflecting the update to htrace-4 > - > > Key: HADOOP-12452 > URL: https://issues.apache.org/jira/browse/HADOOP-12452 > Project: Hadoop Common > Issue Type: Bug > Components: documentation >Affects Versions: 2.8.0 >Reporter: Masatake Iwasaki >Assignee: Masatake Iwasaki > Fix For: 2.8.0 > > Attachments: HADOOP-12452.001.patch > > > The sample code in Tracing.md have some problems. > * compilation error by not importing Tracer. > * generic options are not reflected because Tracer is initialized before > ToolRunner#run. > * it may be confusing to use FsShell in example because it has embedded > Tracer now. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-12452) Fix tracing documention reflecting the update to htrace-4
[ https://issues.apache.org/jira/browse/HADOOP-12452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14943969#comment-14943969 ] Hudson commented on HADOOP-12452: - FAILURE: Integrated in Hadoop-Yarn-trunk #1220 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/1220/]) HADOOP-12452. Fix tracing documention reflecting the update to htrace-4 (cmccabe: rev 3e1752f9fb762a8b3268247f0690374419b2c3a1) * hadoop-common-project/hadoop-common/src/site/markdown/Tracing.md * hadoop-common-project/hadoop-common/CHANGES.txt > Fix tracing documention reflecting the update to htrace-4 > - > > Key: HADOOP-12452 > URL: https://issues.apache.org/jira/browse/HADOOP-12452 > Project: Hadoop Common > Issue Type: Bug > Components: documentation >Affects Versions: 2.8.0 >Reporter: Masatake Iwasaki >Assignee: Masatake Iwasaki > Fix For: 2.8.0 > > Attachments: HADOOP-12452.001.patch > > > The sample code in Tracing.md have some problems. > * compilation error by not importing Tracer. > * generic options are not reflected because Tracer is initialized before > ToolRunner#run. > * it may be confusing to use FsShell in example because it has embedded > Tracer now. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HADOOP-10949) metrics2 sink plugin for Apache Kafka
[ https://issues.apache.org/jira/browse/HADOOP-10949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated HADOOP-10949: -- Resolution: Fixed Fix Version/s: 3.0.0 Status: Resolved (was: Patch Available) +1 committed to trunk. Thanks! > metrics2 sink plugin for Apache Kafka > - > > Key: HADOOP-10949 > URL: https://issues.apache.org/jira/browse/HADOOP-10949 > Project: Hadoop Common > Issue Type: New Feature > Components: metrics >Reporter: Babak Behzad >Assignee: Babak Behzad > Fix For: 3.0.0 > > Attachments: HADOOP-10949-1.patch, HADOOP-10949-2.patch, > HADOOP-10949-4.patch, HADOOP-10949-5.patch, HADOOP-10949-6.patch, > HADOOP-10949.patch, HADOOP-10949.patch, HADOOP-10949.patch, > HADOOP-10949.patch, HADOOP-10949.patch, HADOOP-10949.patch, > HADOOP-10949.patch, HADOOP-10949.patch, HADOOP-10949.patch, > HADOOP-10949.patch, HADOOP-10949.patch > > > Write a metrics2 sink plugin for Hadoop to send metrics directly to Apache > Kafka in addition to the current, Graphite > ([Hadoop-9704|https://issues.apache.org/jira/browse/HADOOP-9704]), Ganglia > and File sinks. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-12441) Fix kill command behavior under some Linux distributions.
[
https://issues.apache.org/jira/browse/HADOOP-12441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14943968#comment-14943968
]
Hudson commented on HADOOP-12441:
-
FAILURE: Integrated in Hadoop-Yarn-trunk #1220 (See
[https://builds.apache.org/job/Hadoop-Yarn-trunk/1220/])
HADOOP-12441. Fixed shell-kill command behaviour to work correctly on (vinodkv:
rev f1c19b9365cbac88e45a9eed516fbfc6c9aa9947)
* hadoop-common-project/hadoop-common/CHANGES.txt
*
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/util/Shell.java
*
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/NodeManager.java
*
hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/util/TestShell.java
> Fix kill command behavior under some Linux distributions.
> -
>
> Key: HADOOP-12441
> URL: https://issues.apache.org/jira/browse/HADOOP-12441
> Project: Hadoop Common
> Issue Type: Bug
>Reporter: Wangda Tan
>Assignee: Wangda Tan
>Priority: Critical
> Fix For: 2.8.0
>
> Attachments: HADOOP-12441.1.patch, HADOOP-12441.2.patch,
> HADOOP-12441.4.patch
>
>
> After HADOOP-12317, kill command's execution will be failure under Ubuntu12.
> After NM restarts, it cannot get if a process is alive or not via pid of
> containers, and it cannot kill process correctly when RM/AM tells NM to kill
> a container.
> Logs from NM (customized logs):
> {code}
> 2015-09-25 21:58:59,348 INFO nodemanager.DefaultContainerExecutor
> (DefaultContainerExecutor.java:containerIsAlive(431)) - ==
> check alive cmd:[[Ljava.lang.String;@496e442d]
> 2015-09-25 21:58:59,349 INFO nodemanager.NMAuditLogger
> (NMAuditLogger.java:logSuccess(89)) - USER=hrt_qa IP=10.0.1.14
> OPERATION=Stop Container RequestTARGET=ContainerManageImpl
> RESULT=SUCCESS APPID=application_1443218269460_0001
> CONTAINERID=container_1443218269460_0001_01_01
> 2015-09-25 21:58:59,363 INFO nodemanager.DefaultContainerExecutor
> (DefaultContainerExecutor.java:containerIsAlive(438)) -
> ===
> ExitCodeException exitCode=1: ERROR: garbage process ID "--".
> Usage:
> kill pid ... Send SIGTERM to every process listed.
> kill signal pid ... Send a signal to every process listed.
> kill -s signal pid ...Send a signal to every process listed.
> kill -l List all signal names.
> kill -L List all signal names in a nice table.
> kill -l signalConvert between signal numbers and names.
> at org.apache.hadoop.util.Shell.runCommand(Shell.java:550)
> at org.apache.hadoop.util.Shell.run(Shell.java:461)
> at
> org.apache.hadoop.util.Shell$ShellCommandExecutor.execute(Shell.java:727)
> at
> org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor.containerIsAlive(DefaultContainerExecutor.java:432)
> at
> org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor.signalContainer(DefaultContainerExecutor.java:401)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainerLaunch.cleanupContainer(ContainerLaunch.java:419)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainersLauncher.handle(ContainersLauncher.java:139)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainersLauncher.handle(ContainersLauncher.java:55)
> at
> org.apache.hadoop.yarn.event.AsyncDispatcher.dispatch(AsyncDispatcher.java:175)
> at
> org.apache.hadoop.yarn.event.AsyncDispatcher$1.run(AsyncDispatcher.java:108)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-10949) metrics2 sink plugin for Apache Kafka
[ https://issues.apache.org/jira/browse/HADOOP-10949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14944382#comment-14944382 ] Hudson commented on HADOOP-10949: - FAILURE: Integrated in Hadoop-Mapreduce-trunk #2427 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2427/]) HADOOP-10949. metrics2 sink plugin for Apache Kafka (Babak Behzad via (aw: rev b59e434116a54464efa91c6e81dcd2eb94fdf1f8) * hadoop-tools/hadoop-kafka/src/test/java/org/apache/hadoop/metrics2/impl/TestKafkaMetrics.java * hadoop-common-project/hadoop-common/CHANGES.txt * hadoop-tools/hadoop-kafka/pom.xml * hadoop-tools/pom.xml * hadoop-tools/hadoop-kafka/src/main/java/org/apache/hadoop/metrics2/sink/KafkaSink.java * hadoop-project/pom.xml > metrics2 sink plugin for Apache Kafka > - > > Key: HADOOP-10949 > URL: https://issues.apache.org/jira/browse/HADOOP-10949 > Project: Hadoop Common > Issue Type: New Feature > Components: metrics >Reporter: Babak Behzad >Assignee: Babak Behzad > Fix For: 3.0.0 > > Attachments: HADOOP-10949-1.patch, HADOOP-10949-2.patch, > HADOOP-10949-4.patch, HADOOP-10949-5.patch, HADOOP-10949-6.patch, > HADOOP-10949.patch, HADOOP-10949.patch, HADOOP-10949.patch, > HADOOP-10949.patch, HADOOP-10949.patch, HADOOP-10949.patch, > HADOOP-10949.patch, HADOOP-10949.patch, HADOOP-10949.patch, > HADOOP-10949.patch, HADOOP-10949.patch > > > Write a metrics2 sink plugin for Hadoop to send metrics directly to Apache > Kafka in addition to the current, Graphite > ([Hadoop-9704|https://issues.apache.org/jira/browse/HADOOP-9704]), Ganglia > and File sinks. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-12350) WASB Logging: Improve WASB Logging around deletes, reads and writes
[
https://issues.apache.org/jira/browse/HADOOP-12350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14944057#comment-14944057
]
Hadoop QA commented on HADOOP-12350:
\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | pre-patch | 16m 39s | Pre-patch trunk compilation is
healthy. |
| {color:green}+1{color} | @author | 0m 0s | The patch does not contain any
@author tags. |
| {color:red}-1{color} | tests included | 0m 0s | The patch doesn't appear
to include any new or modified tests. Please justify why no new tests are
needed for this patch. Also please list what manual steps were performed to
verify this patch. |
| {color:green}+1{color} | javac | 8m 5s | There were no new javac warning
messages. |
| {color:green}+1{color} | javadoc | 10m 20s | There were no new javadoc
warning messages. |
| {color:red}-1{color} | release audit | 0m 16s | The applied patch generated
1 release audit warnings. |
| {color:green}+1{color} | checkstyle | 0m 21s | There were no new checkstyle
issues. |
| {color:green}+1{color} | whitespace | 0m 1s | The patch has no lines that
end in whitespace. |
| {color:green}+1{color} | install | 1m 30s | mvn install still works. |
| {color:green}+1{color} | eclipse:eclipse | 0m 38s | The patch built with
eclipse:eclipse. |
| {color:green}+1{color} | findbugs | 0m 47s | The patch does not introduce
any new Findbugs (version 3.0.0) warnings. |
| {color:red}-1{color} | tools/hadoop tests | 1m 10s | Tests failed in
hadoop-azure. |
| | | 39m 51s | |
\\
\\
|| Reason || Tests ||
| Failed unit tests | hadoop.fs.azure.TestNativeAzureFileSystemOperationsMocked
|
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL |
http://issues.apache.org/jira/secure/attachment/12765056/HADOOP-12350.007.patch
|
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / 2fc2b50 |
| Release Audit |
https://builds.apache.org/job/PreCommit-HADOOP-Build/7769/artifact/patchprocess/patchReleaseAuditProblems.txt
|
| hadoop-azure test log |
https://builds.apache.org/job/PreCommit-HADOOP-Build/7769/artifact/patchprocess/testrun_hadoop-azure.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-HADOOP-Build/7769/testReport/ |
| Java | 1.7.0_55 |
| uname | Linux asf901.gq1.ygridcore.net 3.13.0-36-lowlatency #63-Ubuntu SMP
PREEMPT Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Console output |
https://builds.apache.org/job/PreCommit-HADOOP-Build/7769/console |
This message was automatically generated.
> WASB Logging: Improve WASB Logging around deletes, reads and writes
> ---
>
> Key: HADOOP-12350
> URL: https://issues.apache.org/jira/browse/HADOOP-12350
> Project: Hadoop Common
> Issue Type: Improvement
> Components: tools
>Reporter: Dushyanth
>Assignee: Dushyanth
> Fix For: 2.8.0
>
> Attachments: 0001-HADOOP-12350-Added-WASB-Logging-Statement.patch,
> 0001-HADOOP-12350-Improve-WASB-Logging-Itr3.patch,
> 0001-HADOOP-12350-Moving-from-commons.logging-to-slf4j-lo.patch,
> HADOOP-12350.004.patch, HADOOP-12350.005.patch, HADOOP-12350.006.patch,
> HADOOP-12350.007.patch
>
>
> Logging around the WASB component is very limited and it is disabled by
> default. This improvement is created to add logging around Reads, Writes and
> Deletes when Azure Storage Exception to capture the blobs that hit the
> exception. This information is useful while communicating with the Azure
> storage team for debugging purposes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HADOOP-12364) Deleting pid file after stop is causing the daemons to keep restarting
[ https://issues.apache.org/jira/browse/HADOOP-12364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HADOOP-12364: - Attachment: HADOOP-12364.v2.patch > Deleting pid file after stop is causing the daemons to keep restarting > --- > > Key: HADOOP-12364 > URL: https://issues.apache.org/jira/browse/HADOOP-12364 > Project: Hadoop Common > Issue Type: Bug >Affects Versions: 2.6.0 >Reporter: Siqi Li >Assignee: Siqi Li >Priority: Minor > Attachments: HADOOP-12364.v1.patch, HADOOP-12364.v2.patch > > > pid files are deleting in 5 seconds after we stop the daemons. If a start > command were executed within the 5 seconds, the pid file will be overwrite > with a new pid. However, this pid file is going to be deleted by the former > stop command. This is causing the monitoring service to lose track of the > daemons, hence keep rebooting them -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-10949) metrics2 sink plugin for Apache Kafka
[ https://issues.apache.org/jira/browse/HADOOP-10949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14944060#comment-14944060 ] Hudson commented on HADOOP-10949: - FAILURE: Integrated in Hadoop-trunk-Commit #8572 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/8572/]) HADOOP-10949. metrics2 sink plugin for Apache Kafka (Babak Behzad via (aw: rev b59e434116a54464efa91c6e81dcd2eb94fdf1f8) * hadoop-common-project/hadoop-common/CHANGES.txt * hadoop-tools/pom.xml * hadoop-tools/hadoop-kafka/pom.xml * hadoop-tools/hadoop-kafka/src/test/java/org/apache/hadoop/metrics2/impl/TestKafkaMetrics.java * hadoop-tools/hadoop-kafka/src/main/java/org/apache/hadoop/metrics2/sink/KafkaSink.java * hadoop-project/pom.xml > metrics2 sink plugin for Apache Kafka > - > > Key: HADOOP-10949 > URL: https://issues.apache.org/jira/browse/HADOOP-10949 > Project: Hadoop Common > Issue Type: New Feature > Components: metrics >Reporter: Babak Behzad >Assignee: Babak Behzad > Fix For: 3.0.0 > > Attachments: HADOOP-10949-1.patch, HADOOP-10949-2.patch, > HADOOP-10949-4.patch, HADOOP-10949-5.patch, HADOOP-10949-6.patch, > HADOOP-10949.patch, HADOOP-10949.patch, HADOOP-10949.patch, > HADOOP-10949.patch, HADOOP-10949.patch, HADOOP-10949.patch, > HADOOP-10949.patch, HADOOP-10949.patch, HADOOP-10949.patch, > HADOOP-10949.patch, HADOOP-10949.patch > > > Write a metrics2 sink plugin for Hadoop to send metrics directly to Apache > Kafka in addition to the current, Graphite > ([Hadoop-9704|https://issues.apache.org/jira/browse/HADOOP-9704]), Ganglia > and File sinks. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-12364) Deleting pid file after stop is causing the daemons to keep restarting
[
https://issues.apache.org/jira/browse/HADOOP-12364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14944139#comment-14944139
]
Hadoop QA commented on HADOOP-12364:
\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | pre-patch | 0m 0s | Pre-patch trunk compilation is
healthy. |
| {color:green}+1{color} | @author | 0m 0s | The patch does not contain any
@author tags. |
| {color:red}-1{color} | release audit | 0m 11s | The applied patch generated
1 release audit warnings. |
| {color:green}+1{color} | shellcheck | 0m 5s | There were no new shellcheck
(v0.3.3) issues. |
| {color:green}+1{color} | whitespace | 0m 0s | The patch has no lines that
end in whitespace. |
| | | 0m 19s | |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL |
http://issues.apache.org/jira/secure/attachment/12765075/HADOOP-12364.v2.patch |
| Optional Tests | shellcheck |
| git revision | trunk / b59e434 |
| Release Audit |
https://builds.apache.org/job/PreCommit-HADOOP-Build/7770/artifact/patchprocess/patchReleaseAuditProblems.txt
|
| Java | 1.7.0_55 |
| uname | Linux asf906.gq1.ygridcore.net 3.13.0-36-lowlatency #63-Ubuntu SMP
PREEMPT Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Console output |
https://builds.apache.org/job/PreCommit-HADOOP-Build/7770/console |
This message was automatically generated.
> Deleting pid file after stop is causing the daemons to keep restarting
> ---
>
> Key: HADOOP-12364
> URL: https://issues.apache.org/jira/browse/HADOOP-12364
> Project: Hadoop Common
> Issue Type: Bug
>Affects Versions: 2.6.0
>Reporter: Siqi Li
>Assignee: Siqi Li
>Priority: Minor
> Attachments: HADOOP-12364.v1.patch, HADOOP-12364.v2.patch
>
>
> pid files are deleting in 5 seconds after we stop the daemons. If a start
> command were executed within the 5 seconds, the pid file will be overwrite
> with a new pid. However, this pid file is going to be deleted by the former
> stop command. This is causing the monitoring service to lose track of the
> daemons, hence keep rebooting them
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-12364) Deleting pid file after stop is causing the daemons to keep restarting
[ https://issues.apache.org/jira/browse/HADOOP-12364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14943907#comment-14943907 ] Allen Wittenauer commented on HADOOP-12364: --- a) This patch needs to get updated for trunk. b) using single brackets in bash is bad c) using single quote shellouts is deprecated > Deleting pid file after stop is causing the daemons to keep restarting > --- > > Key: HADOOP-12364 > URL: https://issues.apache.org/jira/browse/HADOOP-12364 > Project: Hadoop Common > Issue Type: Bug >Affects Versions: 2.6.0 >Reporter: Siqi Li >Assignee: Siqi Li >Priority: Minor > Attachments: HADOOP-12364.v1.patch > > > pid files are deleting in 5 seconds after we stop the daemons. If a start > command were executed within the 5 seconds, the pid file will be overwrite > with a new pid. However, this pid file is going to be deleted by the former > stop command. This is causing the monitoring service to lose track of the > daemons, hence keep rebooting them -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-10949) metrics2 sink plugin for Apache Kafka
[ https://issues.apache.org/jira/browse/HADOOP-10949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14944146#comment-14944146 ] Hudson commented on HADOOP-10949: - FAILURE: Integrated in Hadoop-Yarn-trunk #1221 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/1221/]) HADOOP-10949. metrics2 sink plugin for Apache Kafka (Babak Behzad via (aw: rev b59e434116a54464efa91c6e81dcd2eb94fdf1f8) * hadoop-tools/hadoop-kafka/pom.xml * hadoop-project/pom.xml * hadoop-tools/pom.xml * hadoop-common-project/hadoop-common/CHANGES.txt * hadoop-tools/hadoop-kafka/src/test/java/org/apache/hadoop/metrics2/impl/TestKafkaMetrics.java * hadoop-tools/hadoop-kafka/src/main/java/org/apache/hadoop/metrics2/sink/KafkaSink.java > metrics2 sink plugin for Apache Kafka > - > > Key: HADOOP-10949 > URL: https://issues.apache.org/jira/browse/HADOOP-10949 > Project: Hadoop Common > Issue Type: New Feature > Components: metrics >Reporter: Babak Behzad >Assignee: Babak Behzad > Fix For: 3.0.0 > > Attachments: HADOOP-10949-1.patch, HADOOP-10949-2.patch, > HADOOP-10949-4.patch, HADOOP-10949-5.patch, HADOOP-10949-6.patch, > HADOOP-10949.patch, HADOOP-10949.patch, HADOOP-10949.patch, > HADOOP-10949.patch, HADOOP-10949.patch, HADOOP-10949.patch, > HADOOP-10949.patch, HADOOP-10949.patch, HADOOP-10949.patch, > HADOOP-10949.patch, HADOOP-10949.patch > > > Write a metrics2 sink plugin for Hadoop to send metrics directly to Apache > Kafka in addition to the current, Graphite > ([Hadoop-9704|https://issues.apache.org/jira/browse/HADOOP-9704]), Ganglia > and File sinks. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-12441) Fix kill command behavior under some Linux distributions.
[
https://issues.apache.org/jira/browse/HADOOP-12441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14944163#comment-14944163
]
Hudson commented on HADOOP-12441:
-
FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #456 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/456/])
HADOOP-12441. Fixed shell-kill command behaviour to work correctly on (vinodkv:
rev f1c19b9365cbac88e45a9eed516fbfc6c9aa9947)
*
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/util/Shell.java
* hadoop-common-project/hadoop-common/CHANGES.txt
*
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/NodeManager.java
*
hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/util/TestShell.java
> Fix kill command behavior under some Linux distributions.
> -
>
> Key: HADOOP-12441
> URL: https://issues.apache.org/jira/browse/HADOOP-12441
> Project: Hadoop Common
> Issue Type: Bug
>Reporter: Wangda Tan
>Assignee: Wangda Tan
>Priority: Critical
> Fix For: 2.8.0
>
> Attachments: HADOOP-12441.1.patch, HADOOP-12441.2.patch,
> HADOOP-12441.4.patch
>
>
> After HADOOP-12317, kill command's execution will be failure under Ubuntu12.
> After NM restarts, it cannot get if a process is alive or not via pid of
> containers, and it cannot kill process correctly when RM/AM tells NM to kill
> a container.
> Logs from NM (customized logs):
> {code}
> 2015-09-25 21:58:59,348 INFO nodemanager.DefaultContainerExecutor
> (DefaultContainerExecutor.java:containerIsAlive(431)) - ==
> check alive cmd:[[Ljava.lang.String;@496e442d]
> 2015-09-25 21:58:59,349 INFO nodemanager.NMAuditLogger
> (NMAuditLogger.java:logSuccess(89)) - USER=hrt_qa IP=10.0.1.14
> OPERATION=Stop Container RequestTARGET=ContainerManageImpl
> RESULT=SUCCESS APPID=application_1443218269460_0001
> CONTAINERID=container_1443218269460_0001_01_01
> 2015-09-25 21:58:59,363 INFO nodemanager.DefaultContainerExecutor
> (DefaultContainerExecutor.java:containerIsAlive(438)) -
> ===
> ExitCodeException exitCode=1: ERROR: garbage process ID "--".
> Usage:
> kill pid ... Send SIGTERM to every process listed.
> kill signal pid ... Send a signal to every process listed.
> kill -s signal pid ...Send a signal to every process listed.
> kill -l List all signal names.
> kill -L List all signal names in a nice table.
> kill -l signalConvert between signal numbers and names.
> at org.apache.hadoop.util.Shell.runCommand(Shell.java:550)
> at org.apache.hadoop.util.Shell.run(Shell.java:461)
> at
> org.apache.hadoop.util.Shell$ShellCommandExecutor.execute(Shell.java:727)
> at
> org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor.containerIsAlive(DefaultContainerExecutor.java:432)
> at
> org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor.signalContainer(DefaultContainerExecutor.java:401)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainerLaunch.cleanupContainer(ContainerLaunch.java:419)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainersLauncher.handle(ContainersLauncher.java:139)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainersLauncher.handle(ContainersLauncher.java:55)
> at
> org.apache.hadoop.yarn.event.AsyncDispatcher.dispatch(AsyncDispatcher.java:175)
> at
> org.apache.hadoop.yarn.event.AsyncDispatcher$1.run(AsyncDispatcher.java:108)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-12452) Fix tracing documention reflecting the update to htrace-4
[ https://issues.apache.org/jira/browse/HADOOP-12452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14944164#comment-14944164 ] Hudson commented on HADOOP-12452: - FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #456 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/456/]) HADOOP-12452. Fix tracing documention reflecting the update to htrace-4 (cmccabe: rev 3e1752f9fb762a8b3268247f0690374419b2c3a1) * hadoop-common-project/hadoop-common/src/site/markdown/Tracing.md * hadoop-common-project/hadoop-common/CHANGES.txt > Fix tracing documention reflecting the update to htrace-4 > - > > Key: HADOOP-12452 > URL: https://issues.apache.org/jira/browse/HADOOP-12452 > Project: Hadoop Common > Issue Type: Bug > Components: documentation >Affects Versions: 2.8.0 >Reporter: Masatake Iwasaki >Assignee: Masatake Iwasaki > Fix For: 2.8.0 > > Attachments: HADOOP-12452.001.patch > > > The sample code in Tracing.md have some problems. > * compilation error by not importing Tracer. > * generic options are not reflected because Tracer is initialized before > ToolRunner#run. > * it may be confusing to use FsShell in example because it has embedded > Tracer now. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-12452) Fix tracing documention reflecting the update to htrace-4
[ https://issues.apache.org/jira/browse/HADOOP-12452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14944206#comment-14944206 ] Hudson commented on HADOOP-12452: - FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #482 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/482/]) HADOOP-12452. Fix tracing documention reflecting the update to htrace-4 (cmccabe: rev 3e1752f9fb762a8b3268247f0690374419b2c3a1) * hadoop-common-project/hadoop-common/src/site/markdown/Tracing.md * hadoop-common-project/hadoop-common/CHANGES.txt > Fix tracing documention reflecting the update to htrace-4 > - > > Key: HADOOP-12452 > URL: https://issues.apache.org/jira/browse/HADOOP-12452 > Project: Hadoop Common > Issue Type: Bug > Components: documentation >Affects Versions: 2.8.0 >Reporter: Masatake Iwasaki >Assignee: Masatake Iwasaki > Fix For: 2.8.0 > > Attachments: HADOOP-12452.001.patch > > > The sample code in Tracing.md have some problems. > * compilation error by not importing Tracer. > * generic options are not reflected because Tracer is initialized before > ToolRunner#run. > * it may be confusing to use FsShell in example because it has embedded > Tracer now. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-12441) Fix kill command behavior under some Linux distributions.
[
https://issues.apache.org/jira/browse/HADOOP-12441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14944249#comment-14944249
]
Hudson commented on HADOOP-12441:
-
FAILURE: Integrated in Hadoop-Hdfs-trunk #2396 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/2396/])
HADOOP-12441. Fixed shell-kill command behaviour to work correctly on (vinodkv:
rev f1c19b9365cbac88e45a9eed516fbfc6c9aa9947)
*
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/util/Shell.java
* hadoop-common-project/hadoop-common/CHANGES.txt
*
hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/util/TestShell.java
*
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/NodeManager.java
> Fix kill command behavior under some Linux distributions.
> -
>
> Key: HADOOP-12441
> URL: https://issues.apache.org/jira/browse/HADOOP-12441
> Project: Hadoop Common
> Issue Type: Bug
>Reporter: Wangda Tan
>Assignee: Wangda Tan
>Priority: Critical
> Fix For: 2.8.0
>
> Attachments: HADOOP-12441.1.patch, HADOOP-12441.2.patch,
> HADOOP-12441.4.patch
>
>
> After HADOOP-12317, kill command's execution will be failure under Ubuntu12.
> After NM restarts, it cannot get if a process is alive or not via pid of
> containers, and it cannot kill process correctly when RM/AM tells NM to kill
> a container.
> Logs from NM (customized logs):
> {code}
> 2015-09-25 21:58:59,348 INFO nodemanager.DefaultContainerExecutor
> (DefaultContainerExecutor.java:containerIsAlive(431)) - ==
> check alive cmd:[[Ljava.lang.String;@496e442d]
> 2015-09-25 21:58:59,349 INFO nodemanager.NMAuditLogger
> (NMAuditLogger.java:logSuccess(89)) - USER=hrt_qa IP=10.0.1.14
> OPERATION=Stop Container RequestTARGET=ContainerManageImpl
> RESULT=SUCCESS APPID=application_1443218269460_0001
> CONTAINERID=container_1443218269460_0001_01_01
> 2015-09-25 21:58:59,363 INFO nodemanager.DefaultContainerExecutor
> (DefaultContainerExecutor.java:containerIsAlive(438)) -
> ===
> ExitCodeException exitCode=1: ERROR: garbage process ID "--".
> Usage:
> kill pid ... Send SIGTERM to every process listed.
> kill signal pid ... Send a signal to every process listed.
> kill -s signal pid ...Send a signal to every process listed.
> kill -l List all signal names.
> kill -L List all signal names in a nice table.
> kill -l signalConvert between signal numbers and names.
> at org.apache.hadoop.util.Shell.runCommand(Shell.java:550)
> at org.apache.hadoop.util.Shell.run(Shell.java:461)
> at
> org.apache.hadoop.util.Shell$ShellCommandExecutor.execute(Shell.java:727)
> at
> org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor.containerIsAlive(DefaultContainerExecutor.java:432)
> at
> org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor.signalContainer(DefaultContainerExecutor.java:401)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainerLaunch.cleanupContainer(ContainerLaunch.java:419)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainersLauncher.handle(ContainersLauncher.java:139)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainersLauncher.handle(ContainersLauncher.java:55)
> at
> org.apache.hadoop.yarn.event.AsyncDispatcher.dispatch(AsyncDispatcher.java:175)
> at
> org.apache.hadoop.yarn.event.AsyncDispatcher$1.run(AsyncDispatcher.java:108)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HADOOP-12452) Fix tracing documention reflecting the update to htrace-4
[ https://issues.apache.org/jira/browse/HADOOP-12452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14944250#comment-14944250 ] Hudson commented on HADOOP-12452: - FAILURE: Integrated in Hadoop-Hdfs-trunk #2396 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/2396/]) HADOOP-12452. Fix tracing documention reflecting the update to htrace-4 (cmccabe: rev 3e1752f9fb762a8b3268247f0690374419b2c3a1) * hadoop-common-project/hadoop-common/src/site/markdown/Tracing.md * hadoop-common-project/hadoop-common/CHANGES.txt > Fix tracing documention reflecting the update to htrace-4 > - > > Key: HADOOP-12452 > URL: https://issues.apache.org/jira/browse/HADOOP-12452 > Project: Hadoop Common > Issue Type: Bug > Components: documentation >Affects Versions: 2.8.0 >Reporter: Masatake Iwasaki >Assignee: Masatake Iwasaki > Fix For: 2.8.0 > > Attachments: HADOOP-12452.001.patch > > > The sample code in Tracing.md have some problems. > * compilation error by not importing Tracer. > * generic options are not reflected because Tracer is initialized before > ToolRunner#run. > * it may be confusing to use FsShell in example because it has embedded > Tracer now. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-10949) metrics2 sink plugin for Apache Kafka
[ https://issues.apache.org/jira/browse/HADOOP-10949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14944187#comment-14944187 ] Hudson commented on HADOOP-10949: - FAILURE: Integrated in Hadoop-Yarn-trunk-Java8 #491 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/491/]) HADOOP-10949. metrics2 sink plugin for Apache Kafka (Babak Behzad via (aw: rev b59e434116a54464efa91c6e81dcd2eb94fdf1f8) * hadoop-common-project/hadoop-common/CHANGES.txt * hadoop-tools/pom.xml * hadoop-tools/hadoop-kafka/src/main/java/org/apache/hadoop/metrics2/sink/KafkaSink.java * hadoop-tools/hadoop-kafka/src/test/java/org/apache/hadoop/metrics2/impl/TestKafkaMetrics.java * hadoop-project/pom.xml * hadoop-tools/hadoop-kafka/pom.xml > metrics2 sink plugin for Apache Kafka > - > > Key: HADOOP-10949 > URL: https://issues.apache.org/jira/browse/HADOOP-10949 > Project: Hadoop Common > Issue Type: New Feature > Components: metrics >Reporter: Babak Behzad >Assignee: Babak Behzad > Fix For: 3.0.0 > > Attachments: HADOOP-10949-1.patch, HADOOP-10949-2.patch, > HADOOP-10949-4.patch, HADOOP-10949-5.patch, HADOOP-10949-6.patch, > HADOOP-10949.patch, HADOOP-10949.patch, HADOOP-10949.patch, > HADOOP-10949.patch, HADOOP-10949.patch, HADOOP-10949.patch, > HADOOP-10949.patch, HADOOP-10949.patch, HADOOP-10949.patch, > HADOOP-10949.patch, HADOOP-10949.patch > > > Write a metrics2 sink plugin for Hadoop to send metrics directly to Apache > Kafka in addition to the current, Graphite > ([Hadoop-9704|https://issues.apache.org/jira/browse/HADOOP-9704]), Ganglia > and File sinks. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-10949) metrics2 sink plugin for Apache Kafka
[ https://issues.apache.org/jira/browse/HADOOP-10949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14944237#comment-14944237 ] Hudson commented on HADOOP-10949: - FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #483 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/483/]) HADOOP-10949. metrics2 sink plugin for Apache Kafka (Babak Behzad via (aw: rev b59e434116a54464efa91c6e81dcd2eb94fdf1f8) * hadoop-tools/pom.xml * hadoop-tools/hadoop-kafka/src/test/java/org/apache/hadoop/metrics2/impl/TestKafkaMetrics.java * hadoop-tools/hadoop-kafka/pom.xml * hadoop-project/pom.xml * hadoop-common-project/hadoop-common/CHANGES.txt * hadoop-tools/hadoop-kafka/src/main/java/org/apache/hadoop/metrics2/sink/KafkaSink.java > metrics2 sink plugin for Apache Kafka > - > > Key: HADOOP-10949 > URL: https://issues.apache.org/jira/browse/HADOOP-10949 > Project: Hadoop Common > Issue Type: New Feature > Components: metrics >Reporter: Babak Behzad >Assignee: Babak Behzad > Fix For: 3.0.0 > > Attachments: HADOOP-10949-1.patch, HADOOP-10949-2.patch, > HADOOP-10949-4.patch, HADOOP-10949-5.patch, HADOOP-10949-6.patch, > HADOOP-10949.patch, HADOOP-10949.patch, HADOOP-10949.patch, > HADOOP-10949.patch, HADOOP-10949.patch, HADOOP-10949.patch, > HADOOP-10949.patch, HADOOP-10949.patch, HADOOP-10949.patch, > HADOOP-10949.patch, HADOOP-10949.patch > > > Write a metrics2 sink plugin for Hadoop to send metrics directly to Apache > Kafka in addition to the current, Graphite > ([Hadoop-9704|https://issues.apache.org/jira/browse/HADOOP-9704]), Ganglia > and File sinks. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-10949) metrics2 sink plugin for Apache Kafka
[ https://issues.apache.org/jira/browse/HADOOP-10949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14944413#comment-14944413 ] Hudson commented on HADOOP-10949: - FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #457 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/457/]) HADOOP-10949. metrics2 sink plugin for Apache Kafka (Babak Behzad via (aw: rev b59e434116a54464efa91c6e81dcd2eb94fdf1f8) * hadoop-tools/hadoop-kafka/src/main/java/org/apache/hadoop/metrics2/sink/KafkaSink.java * hadoop-project/pom.xml * hadoop-tools/pom.xml * hadoop-tools/hadoop-kafka/src/test/java/org/apache/hadoop/metrics2/impl/TestKafkaMetrics.java * hadoop-tools/hadoop-kafka/pom.xml * hadoop-common-project/hadoop-common/CHANGES.txt > metrics2 sink plugin for Apache Kafka > - > > Key: HADOOP-10949 > URL: https://issues.apache.org/jira/browse/HADOOP-10949 > Project: Hadoop Common > Issue Type: New Feature > Components: metrics >Reporter: Babak Behzad >Assignee: Babak Behzad > Fix For: 3.0.0 > > Attachments: HADOOP-10949-1.patch, HADOOP-10949-2.patch, > HADOOP-10949-4.patch, HADOOP-10949-5.patch, HADOOP-10949-6.patch, > HADOOP-10949.patch, HADOOP-10949.patch, HADOOP-10949.patch, > HADOOP-10949.patch, HADOOP-10949.patch, HADOOP-10949.patch, > HADOOP-10949.patch, HADOOP-10949.patch, HADOOP-10949.patch, > HADOOP-10949.patch, HADOOP-10949.patch > > > Write a metrics2 sink plugin for Hadoop to send metrics directly to Apache > Kafka in addition to the current, Graphite > ([Hadoop-9704|https://issues.apache.org/jira/browse/HADOOP-9704]), Ganglia > and File sinks. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-10949) metrics2 sink plugin for Apache Kafka
[ https://issues.apache.org/jira/browse/HADOOP-10949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1491#comment-1491 ] Hudson commented on HADOOP-10949: - FAILURE: Integrated in Hadoop-Hdfs-trunk #2397 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/2397/]) HADOOP-10949. metrics2 sink plugin for Apache Kafka (Babak Behzad via (aw: rev b59e434116a54464efa91c6e81dcd2eb94fdf1f8) * hadoop-tools/hadoop-kafka/pom.xml * hadoop-project/pom.xml * hadoop-tools/hadoop-kafka/src/main/java/org/apache/hadoop/metrics2/sink/KafkaSink.java * hadoop-tools/pom.xml * hadoop-common-project/hadoop-common/CHANGES.txt * hadoop-tools/hadoop-kafka/src/test/java/org/apache/hadoop/metrics2/impl/TestKafkaMetrics.java > metrics2 sink plugin for Apache Kafka > - > > Key: HADOOP-10949 > URL: https://issues.apache.org/jira/browse/HADOOP-10949 > Project: Hadoop Common > Issue Type: New Feature > Components: metrics >Reporter: Babak Behzad >Assignee: Babak Behzad > Fix For: 3.0.0 > > Attachments: HADOOP-10949-1.patch, HADOOP-10949-2.patch, > HADOOP-10949-4.patch, HADOOP-10949-5.patch, HADOOP-10949-6.patch, > HADOOP-10949.patch, HADOOP-10949.patch, HADOOP-10949.patch, > HADOOP-10949.patch, HADOOP-10949.patch, HADOOP-10949.patch, > HADOOP-10949.patch, HADOOP-10949.patch, HADOOP-10949.patch, > HADOOP-10949.patch, HADOOP-10949.patch > > > Write a metrics2 sink plugin for Hadoop to send metrics directly to Apache > Kafka in addition to the current, Graphite > ([Hadoop-9704|https://issues.apache.org/jira/browse/HADOOP-9704]), Ganglia > and File sinks. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
