You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tajo.apache.org by "Jaehwa Jung (JIRA)" <ji...@apache.org> on 2015/08/04 05:07:05 UTC
[jira] [Updated] (TAJO-1506) WorkerConnectionInfo::id field may be
not unique, but its uniqueness is assumed throughout codes.
[ https://issues.apache.org/jira/browse/TAJO-1506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jaehwa Jung updated TAJO-1506:
------------------------------
Fix Version/s: (was: 0.11.0)
> WorkerConnectionInfo::id field may be not unique, but its uniqueness is assumed throughout codes.
> -------------------------------------------------------------------------------------------------
>
> Key: TAJO-1506
> URL: https://issues.apache.org/jira/browse/TAJO-1506
> Project: Tajo
> Issue Type: Improvement
> Components: QueryMaster, Worker
> Reporter: Hyunsik Choi
> Assignee: Jihun Kang
> Attachments: TAJO-1506.patch, TAJO-1506_1.patch, TAJO-1506_2.patch, TAJO-1506_3.patch, TAJO-1506_4.patch
>
>
> WorkerConnectionInfo::id is a integer value. It is generated in Worker by a hashCode as follows:
> {code}
> public WorkerConnectionInfo(String host, int peerRpcPort, int pullServerPort, int clientPort,
> int queryMasterPort, int httpInfoPort) {
> ...
> this.queryMasterPort = queryMasterPort;
> this.httpInfoPort = httpInfoPort;
> this.id = hashCode();
> {code}
> Fundamentally, it uses hashCode method, so there are possibility to cause duplicate integer value. But, all codes assume its uniqueness. It is a potential problem.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)