cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Francesco Messere <f.mess...@list-group.com>
Subject Cluster configuration issue
Date Fri, 09 Nov 2018 10:24:58 GMT
<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p><tt>Hi to all, <br>
      </tt></p>
    <tt>I have a problem with distribuited cluster configuration.</tt><br>
    <tt>This is a test environment  <br>
      Cassandra version is 3.11.3<br>
    </tt><tt>2 site Milan and Florence</tt><br>
    <tt>2 servers on each site <br>
    </tt><br>
    <tt>1 common "cluster-name" and </tt><tt>2 DC <br>
    </tt><br>
    <tt>First installation and startup goes ok all the nodes are present
      in the cluster. <br>
    </tt><br>
    <tt>The issue startup after a server reboot in FLORENCE DC <br>
    </tt><br>
    <tt>Cassandra node did not startup and in system.log last line
      written is <br>
    </tt><br>
    <u><i><tt>INFO  [ScheduledTasks:1] 2018-11-09 10:36:54,306
          TokenMetadata.java:498 - Updating topology for all endpoints
          that have changed<br>
          <br>
          <br>
        </tt></i></u><tt><br>
      The only way to correct the thing I found is to cleanup the node,
      remove from cluster and re-join it.<br>
    </tt>
    <p><tt>How can I solve it?</tt></p>
    <p><tt><br>
      </tt></p>
    <p><tt>here are configuration files <br>
      </tt></p>
    <p><tt>less cassandra-topology.properties <br>
        # Unless required by applicable law or agreed to in writing,
        software<br>
        # distributed under the License is distributed on an "AS IS"
        BASIS,<br>
        # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express
        or implied.<br>
        # See the License for the specific language governing
        permissions and<br>
        # limitations under the License.<br>
        <br>
        # Cassandra Node IP=Data Center:Rack<br>
        192.168.204.175=DC-FIRENZE:RACK1<br>
        192.168.204.176=DC-FIRENZE:RACK1<br>
        192.168.71.210=DC-MILANO:RACK1<br>
        192.168.71.211=DC-MILANO:RACK1<br>
        <br>
        # default for unknown nodes<br>
        default=DC-FIRENZE:r1<br>
        <br>
        # Native IPv6 is supported, however you must escape the colon in
        the IPv6 Address<br>
        # Also be sure to comment out JVM_OPTS="$JVM_OPTS
        -Djava.net.preferIPv4Stack=true"<br>
        # in cassandra-env.sh<br>
        #fe80\:0\:0\:0\:202\:b3ff\:fe1e\:8329=DC1:RAC3</tt></p>
    <p><tt><br>
      </tt></p>
    <p><tt>cassandra-rackdc.properties<br>
      </tt></p>
    <p><tt># Unless required by applicable law or agreed to in writing,
        software<br>
        # distributed under the License is distributed on an "AS IS"
        BASIS,<br>
        # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express
        or implied.<br>
        # See the License for the specific language governing
        permissions and<br>
        # limitations under the License.<br>
        <br>
        # These properties are used with GossipingPropertyFileSnitch and
        will<br>
        # indicate the rack and dc for this node<br>
        dc=DC-FIRENZE<br>
        rack=RACK1<br>
        <br>
        # Add a suffix to a datacenter name. Used by the Ec2Snitch and
        Ec2MultiRegionSnitch<br>
        # to append a string to the EC2 region name.<br>
        #dc_suffix=<br>
        <br>
        # Uncomment the following line to make this snitch prefer the
        internal ip when possible, as the Ec2MultiRegionSnitch does.<br>
        # prefer_local=true<br>
      </tt></p>
    <p><tt><br>
      </tt></p>
    <p><tt>In attach the system.log file <br>
      </tt></p>
    <p><tt>Regards <br>
      </tt></p>
    <p><tt>Francesco Messere</tt></p>
    <p><tt><br>
      </tt></p>
  </body>
</html>

Mime
View raw message