You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "binlijin (JIRA)" <ji...@apache.org> on 2012/07/12 17:06:35 UTC
[jira] [Created] (HIVE-3254) Reuse RunningJob in
ExecDriver.progress
binlijin created HIVE-3254:
------------------------------
Summary: Reuse RunningJob in ExecDriver.progress
Key: HIVE-3254
URL: https://issues.apache.org/jira/browse/HIVE-3254
Project: Hive
Issue Type: Bug
Reporter: binlijin
while (!rj.isComplete()) {
RunningJob newRj = jc.getJob(rj.getJobID());
}
Should we reuse the RunningJob? If not, why?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3254) Reuse RunningJob
Posted by "binlijin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
binlijin updated HIVE-3254:
---------------------------
Description:
private MapRedStats progress(ExecDriverTaskHandle th) throws IOException {
while (!rj.isComplete()) {
try {
Thread.sleep(pullInterval);
} catch (InterruptedException e) {
}
RunningJob newRj = jc.getJob(rj.getJobID());
}
}
Should we reuse the RunningJob? If not, why?
was:
while (!rj.isComplete()) {
RunningJob newRj = jc.getJob(rj.getJobID());
}
Should we reuse the RunningJob? If not, why?
Summary: Reuse RunningJob (was: Reuse RunningJob in ExecDriver.progress)
> Reuse RunningJob
> -----------------
>
> Key: HIVE-3254
> URL: https://issues.apache.org/jira/browse/HIVE-3254
> Project: Hive
> Issue Type: Bug
> Reporter: binlijin
>
> private MapRedStats progress(ExecDriverTaskHandle th) throws IOException {
> while (!rj.isComplete()) {
> try {
> Thread.sleep(pullInterval);
> } catch (InterruptedException e) {
> }
> RunningJob newRj = jc.getJob(rj.getJobID());
> }
> }
> Should we reuse the RunningJob? If not, why?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3254) Reuse RunningJob
Posted by "Lianhui Wang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13424569#comment-13424569 ]
Lianhui Wang commented on HIVE-3254:
------------------------------------
yes, i think that can do.
but maybe the newRj is null.so you must check the null.
because the jobtracker always cache the fixed-size completed job's infos.
if the job that you get have completed,maybe the JT removed the job's information.
> Reuse RunningJob
> -----------------
>
> Key: HIVE-3254
> URL: https://issues.apache.org/jira/browse/HIVE-3254
> Project: Hive
> Issue Type: Bug
> Reporter: binlijin
>
> private MapRedStats progress(ExecDriverTaskHandle th) throws IOException {
> while (!rj.isComplete()) {
> try {
> Thread.sleep(pullInterval);
> } catch (InterruptedException e) {
> }
> RunningJob newRj = jc.getJob(rj.getJobID());
> }
> }
> Should we reuse the RunningJob? If not, why?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira