[
https://issues.apache.org/jira/browse/HDDS-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16579752#comment-16579752
]
Elek, Marton commented on HDDS-342:
-----------------------------------
Thanks the feedback [~anu]. It was just an example script but I like your idea
to collect useful byteman scripts in the hadoop repository.
Using file from the repository could be more complex than using an url: it
requires not just adding one additional environment variable, but we need to
modify the mounts for all the containers (mount the folder with the scripts)
AND change the environment variables.
I would add the example script to the repository AND use an url to
https://github.com/apache/hadoop/trunk/... In that case url could be fixed
easily in case of change (script is part of the repo) but the usage still just
onliner... What do you think?
> Add example byteman script to print out hadoop rpc traffic
> ----------------------------------------------------------
>
> Key: HDDS-342
> URL: https://issues.apache.org/jira/browse/HDDS-342
> Project: Hadoop Distributed Data Store
> Issue Type: Improvement
> Reporter: Elek, Marton
> Assignee: Elek, Marton
> Priority: Minor
> Fix For: 0.2.1
>
> Attachments: HDDS-342.001.patch, byteman.png, byteman2.png
>
>
> HADOOP-15656 adds byteman support to the hadoop-runner base image. byteman is
> a simple tool to define java instrumentation. For example it's very easy to
> print out the incoming and outgoing hadoop rcp messages or fsimage edits.
> In this patch I add one more line to the standard docker-compose cluster to
> demonstrate this capability (print out rpc calls). By default it's turned off.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]