tajo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "hyoungjunkim (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAJO-296) Late registration of Tajo workers
Date Sat, 23 Nov 2013 04:26:35 GMT

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

hyoungjunkim commented on TAJO-296:
-----------------------------------

When running in debug mode, takes a long time in the following section
{code}
2013-11-23 13:20:38,759 DEBUG mortbay.log (?:invoke(?)) - Container Server@5975d6ab + org.mortbay.jetty.servlet.HashSessionIdManager@7c65216
as sessionIdManager
2013-11-23 13:20:38,759 DEBUG mortbay.log (?:invoke(?)) - Init SecureRandom.
2013-11-23 13:22:45,941 DEBUG mortbay.log (?:invoke(?)) - started org.mortbay.jetty.servlet.HashSessionIdManager@7c65216
{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