[
https://issues.apache.org/jira/browse/SQOOP-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14107439#comment-14107439
]
Abraham Elmahrek commented on SQOOP-1397:
-----------------------------------------
I think to get this working I had to add the above to
https://github.com/apache/sqoop/blob/branch-1.99.3/submission/mapreduce/src/main/java/org/apache/sqoop/submission/mapreduce/MapreduceSubmissionEngine.java#L202.
I believe if the above is added to the Configuration provided at Job
submission, the containers will be launched with the appropriate JVM arguments.
It's important to watch out for port conflicts. So Maybe the MapReduce
configuration can be handled in a different Jira.
> Sqoop2: Attach a debugger to miniclusters/ MR tasks at launch
> -------------------------------------------------------------
>
> Key: SQOOP-1397
> URL: https://issues.apache.org/jira/browse/SQOOP-1397
> Project: Sqoop
> Issue Type: Improvement
> Affects Versions: 2.0.0
> Reporter: Abraham Elmahrek
> Assignee: Veena Basavaraj
>
> It would be nice to have a way to attach a debugger to the miniclusters:
> http://cargo.codehaus.org/Starting+and+stopping+a+container and
> http://cargo.codehaus.org/Configuration+properties.
> For tomcat, I needed to add the following to TomcatSqoopMiniCluster:
> {code}
> configuration.setProperty(GeneralPropertySet.JVMARGS,
> "\"-agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=5005\"");
> {code}
> There should also be a way to attach a debugger to the Yarn container.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
