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

Hudson commented on TAJO-1040:
------------------------------

SUCCESS: Integrated in Tajo-master-build #360 (See 
[https://builds.apache.org/job/Tajo-master-build/360/])
TAJO-1040: Misuse netty HashedWheelTimer. (jinho) (jhkim: rev 
1a8a67ceb4224f3f0f3adab7d3e8956d3d12137c)
* tajo-core/src/main/java/org/apache/tajo/worker/Fetcher.java
* tajo-core/src/main/java/org/apache/tajo/worker/Task.java
* tajo-core/src/main/java/org/apache/tajo/worker/ExecutionBlockContext.java
* tajo-core/src/test/java/org/apache/tajo/worker/TestFetcher.java
* CHANGES
* tajo-core/src/main/java/org/apache/tajo/worker/TaskRunnerManager.java


> Misuse netty HashedWheelTimer
> -----------------------------
>
>                 Key: TAJO-1040
>                 URL: https://issues.apache.org/jira/browse/TAJO-1040
>             Project: Tajo
>          Issue Type: Improvement
>          Components: rpc
>    Affects Versions: 0.9.0
>            Reporter: Jinho Kim
>            Assignee: Jinho Kim
>             Fix For: 0.9.0
>
>
> HashedWheelTimer creates a new thread whenever it is instantiated and 
> started. Therefore, We should to share the instance
> refer to http://netty.io/3.6/api/org/jboss/netty/util/HashedWheelTimer.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to