hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Surówka (Commented) (JIRA) <>
Subject [jira] [Commented] (HIVE-2500) Allow Hive to be debugged remotely
Date Fri, 14 Oct 2011 21:54:12 GMT


Robert Surówka commented on HIVE-2500:

Apparently this diff is still wrong (I will have to do small fix to, when
debug off, it will add just one if check for a key being in a map per execute() call of that
task, and only if new JVM is about to be started).

As I am working on it I plan to add following features:

-user could specify port on which Hive JVM will wait (8000 will be default).
-user could specify whether child JVMs should be also started in debug mode (default: not).
If started in debug mode, child JVMs will wait on a different ports than parent (and I will
try to make it in such a way, so probability of ports collision would be very small (to make
it impossible one would need to use some between process communication, since children can
start their own children, and I don't want to do that yet (especially that HIVE may be deployed
on various os-es). User will know on which port new JVMs are waiting, since upon start they
print that information. New JVMs will be started on ports higher than port of the initial
JVM - so if someone needs, he can set initial port to be higher than any other already used
TCP port). 

ETA: by mid of next week (hopefully)
> Allow Hive to be debugged remotely
> ----------------------------------
>                 Key: HIVE-2500
>                 URL:
>             Project: Hive
>          Issue Type: New Feature
>            Reporter: Robert Surówka
>            Assignee: Robert Surówka
>            Priority: Minor
>         Attachments: HIVE-2500.1.patch, HIVE-2500.2.patch

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message