drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jacques Nadeau (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DRILL-489) hazelcast cluster membership
Date Thu, 29 May 2014 15:46:06 GMT

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

Jacques Nadeau commented on DRILL-489:
--------------------------------------

resolved with clusterid fixed.

> hazelcast cluster membership
> ----------------------------
>
>                 Key: DRILL-489
>                 URL: https://issues.apache.org/jira/browse/DRILL-489
>             Project: Apache Drill
>          Issue Type: Bug
>    Affects Versions: 1.0.0-rc1
>            Reporter: Chun Chang
>
> I have a four node cluster, with drill bit cluster name set to:
> drill.exec: {
>   cluster-id: "drillbitschun"
> on all nodes. After I started drill bit from all four nodes, I noticed in the drill bit.out
file that hazel cast cluster membership includes other nodes within the same subnet:
> Apr 04, 2014 3:41:19 PM com.hazelcast.cluster.ClusterService
> INFO: [10.10.100.120]:5701 [dev]
> Members [8] {
>         Member [10.10.100.127]:5701
>         Member [10.10.100.128]:5701
>         Member [10.10.100.129]:5701
>         Member [10.10.100.56]:5701
>         Member [10.10.100.117]:5701
>         Member [10.10.100.118]:5701
>         Member [10.10.100.119]:5701
>         Member [10.10.100.120]:5701 this
> }
> Notice it has more than four nodes in members. I don't know what ill behavior this might
cause but this definitely does not look correct.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message