[
https://issues.apache.org/jira/browse/TAJO-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13915515#comment-13915515
]
Hudson commented on TAJO-602:
-----------------------------
SUCCESS: Integrated in Tajo-master-build #94 (See
[https://builds.apache.org/job/Tajo-master-build/94/])
TAJO-602: WorkerResourceManager should be broke down into 3 parts. (missed
files) (hyunsik:
https://git-wip-us.apache.org/repos/asf/?p=incubator-tajo.git&a=commit&h=f5945424ed67fe18c67b15218c4176f592b145af)
*
tajo-core/tajo-core-backend/src/main/java/org/apache/tajo/master/rm/WorkerState.java
*
tajo-core/tajo-core-backend/src/main/java/org/apache/tajo/worker/WorkerHeartbeatService.java
*
tajo-core/tajo-core-backend/src/main/java/org/apache/tajo/master/rm/WorkerEvent.java
* tajo-core/tajo-core-backend/src/main/proto/ResourceTrackerProtocol.proto
*
tajo-core/tajo-core-backend/src/main/java/org/apache/tajo/master/rm/WorkerLivelinessMonitor.java
*
tajo-core/tajo-core-backend/src/main/java/org/apache/tajo/master/rm/WorkerEventType.java
*
tajo-core/tajo-core-backend/src/main/java/org/apache/tajo/master/rm/TajoRMContext.java
*
tajo-core/tajo-core-backend/src/main/java/org/apache/tajo/master/rm/WorkerStatusEvent.java
*
tajo-core/tajo-core-backend/src/main/java/org/apache/tajo/master/rm/TajoResourceTracker.java
*
tajo-core/tajo-core-backend/src/main/java/org/apache/tajo/master/rm/Worker.java
*
tajo-core/tajo-core-backend/src/test/java/org/apache/tajo/master/rm/TestTajoResourceManager.java
* tajo-common/src/main/java/org/apache/tajo/util/ProtoBufUtil.java
*
tajo-core/tajo-core-backend/src/main/java/org/apache/tajo/master/rm/WorkerReconnectEvent.java
> WorkerResourceManager should be broke down into 3 parts
> --------------------------------------------------------
>
> Key: TAJO-602
> URL: https://issues.apache.org/jira/browse/TAJO-602
> Project: Tajo
> Issue Type: Sub-task
> Affects Versions: 1.0-incubating
> Reporter: Min Zhou
> Assignee: Hyunsik Choi
> Fix For: 1.0-incubating
>
> Attachments: TAJO-602.patch
>
>
> Before implementing a scheduler, I think we should do some refactoring at
> first. There are 2 interfaces and 4 classes related to resource management,
> they are WorkerResourceManager , YarnTajoResourceManager,
> TajoWorkerResourceManager reside in TajoMaster, and ResourceAllocator,
> YarnResourceAllocator, TajoResourceAllocator reside in QueryMasters.
> WorkerResourceManager actually plays 3 roles
> 1. Choose or start a QueryMaster for a query, and management it
> 2. allocate resource for query tasks / task runners (only for standalone mode)
> 3. Handle worker's heartbeat (only for standalone mode)
> If the scheduler is a decentralized one, like sparrow, we can allocate
> resource for a QueryMaster as the same way for a TaskRunner. So 1. and 2.
> can use the same interface, but called by 2 different caller. 3. is
> different from the others, we can create another service, let's say
> HeartbeatService to deal with worker's heartbeats.
> Any suggestion?
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
