tajo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jihoon Son (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (TAJO-296) Late registration of Tajo workers
Date Fri, 01 Nov 2013 05:05:25 GMT

    [ https://issues.apache.org/jira/browse/TAJO-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13811046#comment-13811046
] 

Jihoon Son edited comment on TAJO-296 at 11/1/13 5:04 AM:
----------------------------------------------------------

We upgraded the java to 1.7 sometime ago. Here is the jvm version.
{code}
$ java -version
java version "1.7.0_17"
OpenJDK Runtime Environment (IcedTea7 2.3.8) (Gentoo build 1.7.0_17-b02)
OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode)
{code}


was (Author: jihoonson):
We upgraded the java to 1.7 sometime ago. Here is the jvm version
{code}
$ java -version
java version "1.7.0_17"
OpenJDK Runtime Environment (IcedTea7 2.3.8) (Gentoo build 1.7.0_17-b02)
OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode)
{code}

> Late registration of Tajo workers
> ---------------------------------
>
>                 Key: TAJO-296
>                 URL: https://issues.apache.org/jira/browse/TAJO-296
>             Project: Tajo
>          Issue Type: Bug
>          Components: resource manager
>            Reporter: Jihoon Son
>             Fix For: 0.8-incubating
>
>
> The worker registration takes too much time.
> When I tested on an in-house cluster which consists of one master and 32 workers, 31
workers are registered in about 2 minutes and one worker is failed to register.
> My guess from the log is that the failed worker does not receive any start messages.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message