[
https://issues.apache.org/jira/browse/TAJO-991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14118169#comment-14118169
]
ASF GitHub Bot commented on TAJO-991:
-------------------------------------
Github user babokim commented on a diff in the pull request:
https://github.com/apache/tajo/pull/107#discussion_r16985288
--- Diff:
tajo-core/src/main/java/org/apache/tajo/master/querymaster/QueryMaster.java ---
@@ -183,7 +181,13 @@ public void stop() {
}
protected void
cleanupExecutionBlock(List<TajoIdProtos.ExecutionBlockIdProto>
executionBlockIds) {
- LOG.info("cleanup executionBlocks: " + executionBlockIds);
+ String cleanupMessage = "";
+ String prefix = "";
+ for (TajoIdProtos.ExecutionBlockIdProto eachEbId: executionBlockIds) {
+ cleanupMessage += prefix + (new
ExecutionBlockId(eachEbId)).toString();
--- End diff --
Yes
> Running PullServer on a dedicated JVM process which separates from worker.
> --------------------------------------------------------------------------
>
> Key: TAJO-991
> URL: https://issues.apache.org/jira/browse/TAJO-991
> Project: Tajo
> Issue Type: Sub-task
> Components: data shuffle
> Reporter: Hyoungjun Kim
> Assignee: Hyoungjun Kim
>
> Currently PullServer runs on TajoWorker. If a TajoWorker starts Garbage
> Collector, all fetching tasks which run on other worker are paused during
> Garbage Collection. Running PullServer on a dedicated JVM process which
> separates from worker is helpful avoiding stop the all cluster by GC.
> PullServer uses small memory and doesn't share any information and status
> with TajoWorker.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
