You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by 张鹏鹏 <zh...@gmail.com> on 2016/03/23 04:49:00 UTC

Ignite server stop unexpectedly

I am just learning Ignite,so maybe this is a dumb question.

I want to test the Partitioned Cache Mode,so I start three Ignite nodes on
three Server.This is the config:


<?xml version="1.0" encoding="UTF-8"?>

<!--
  Licensed to the Apache Software Foundation (ASF) under one or more
  contributor license agreements.  See the NOTICE file distributed with
  this work for additional information regarding copyright ownership.
  The ASF licenses this file to You under the Apache License, Version 2.0
  (the "License"); you may not use this file except in compliance with
  the License.  You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

  Unless required by applicable law or agreed to in writing, software
  distributed under the License is distributed on an "AS IS" BASIS,
  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  See the License for the specific language governing permissions and
  limitations under the License.
-->

<beans xmlns="http://www.springframework.org/schema/beans"
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xsi:schemaLocation="
       http://www.springframework.org/schema/beans
       http://www.springframework.org/schema/beans/spring-beans.xsd">
    <bean id="grid.cfg"
class="org.apache.ignite.configuration.IgniteConfiguration">
        <property name="peerClassLoadingEnabled" value="true"/>
        <property name="discoverySpi">
            <bean
class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi">
                <property name="ipFinder">
                    <bean
class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
                        <property name="addresses">
                            <list>
                                <value>10.20.30.91</value>
                                <value>10.20.30.92</value>
                                <value>10.20.30.93</value>
                            </list>
                        </property>
                    </bean>
                </property>
            </bean>
        </property>
        <property name="cacheConfiguration">
            <bean
class="org.apache.ignite.configuration.CacheConfiguration">
                <property name="name" value="testCache"/>
                <property name="cacheMode" value="PARTITIONED"/>
                <property name="backups" value="1"/>
            </bean>
        </property>
    </bean>
</beans>

I start the nodes use this command:

./ignite.sh ../../ignite-config.xml >> /opt/ignite.log &



I start a Client node to write some date to the Server nodes.Simple code
copy from the Doc.Then I kill one Server node and start the Client again.I
find that one Ignite server stop unexpectedly.

Sometimes I can find Exceptions like this:


   [10:35:40,259][SEVERE][tcp-disco-msg-worker-#2%null%][TcpDiscoverySpi]
TcpDiscoverSpi's message worker thread failed abnormally. Stopping the node
in order to prevent cluster wide instability.
java.lang.InterruptedException
        at
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.reportInterruptAfterWait(AbstractQueuedSynchronizer.java:2014)
        at
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2088)
        at
java.util.concurrent.LinkedBlockingDeque.pollFirst(LinkedBlockingDeque.java:522)
        at
java.util.concurrent.LinkedBlockingDeque.poll(LinkedBlockingDeque.java:684)
        at
org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.body(ServerImpl.java:5779)
        at
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.body(ServerImpl.java:2161)
        at
org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
[10:35:40] Topology snapshot [ver=9, servers=1, clients=0, CPUs=12,
heap=1.0GB]
[10:35:40] Ignite node stopped OK [uptime=00:07:53:07]

sometimes,I just find one line:
       Ignite node stopped OK

Re: Ignite server stop unexpectedly

Posted by 张鹏鹏 <zh...@gmail.com>.
Thank you for checking my problem.
I have found that's my mistake.I connected the server use ssh. when I lost
the connection,the shell auto closed the Ignite node.

I add 'nohup' before the command,then it's fixed.

2016-03-23 11:49 GMT+08:00 张鹏鹏 <zh...@gmail.com>:

> I am just learning Ignite,so maybe this is a dumb question.
>
> I want to test the Partitioned Cache Mode,so I start three Ignite nodes on
> three Server.This is the config:
>
>
> <?xml version="1.0" encoding="UTF-8"?>
>
> <!--
>   Licensed to the Apache Software Foundation (ASF) under one or more
>   contributor license agreements.  See the NOTICE file distributed with
>   this work for additional information regarding copyright ownership.
>   The ASF licenses this file to You under the Apache License, Version 2.0
>   (the "License"); you may not use this file except in compliance with
>   the License.  You may obtain a copy of the License at
>
>        http://www.apache.org/licenses/LICENSE-2.0
>
>   Unless required by applicable law or agreed to in writing, software
>   distributed under the License is distributed on an "AS IS" BASIS,
>   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
>   See the License for the specific language governing permissions and
>   limitations under the License.
> -->
>
> <beans xmlns="http://www.springframework.org/schema/beans"
>        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>        xsi:schemaLocation="
>        http://www.springframework.org/schema/beans
>        http://www.springframework.org/schema/beans/spring-beans.xsd">
>     <bean id="grid.cfg"
> class="org.apache.ignite.configuration.IgniteConfiguration">
>         <property name="peerClassLoadingEnabled" value="true"/>
>         <property name="discoverySpi">
>             <bean
> class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi">
>                 <property name="ipFinder">
>                     <bean
> class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
>                         <property name="addresses">
>                             <list>
>                                 <value>10.20.30.91</value>
>                                 <value>10.20.30.92</value>
>                                 <value>10.20.30.93</value>
>                             </list>
>                         </property>
>                     </bean>
>                 </property>
>             </bean>
>         </property>
>         <property name="cacheConfiguration">
>             <bean
> class="org.apache.ignite.configuration.CacheConfiguration">
>                 <property name="name" value="testCache"/>
>                 <property name="cacheMode" value="PARTITIONED"/>
>                 <property name="backups" value="1"/>
>             </bean>
>         </property>
>     </bean>
> </beans>
>
> I start the nodes use this command:
>
> ./ignite.sh ../../ignite-config.xml >> /opt/ignite.log &
>
>
>
> I start a Client node to write some date to the Server nodes.Simple code
> copy from the Doc.Then I kill one Server node and start the Client again.I
> find that one Ignite server stop unexpectedly.
>
> Sometimes I can find Exceptions like this:
>
>
>    [10:35:40,259][SEVERE][tcp-disco-msg-worker-#2%null%][TcpDiscoverySpi]
> TcpDiscoverSpi's message worker thread failed abnormally. Stopping the node
> in order to prevent cluster wide instability.
> java.lang.InterruptedException
>         at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.reportInterruptAfterWait(AbstractQueuedSynchronizer.java:2014)
>         at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2088)
>         at
> java.util.concurrent.LinkedBlockingDeque.pollFirst(LinkedBlockingDeque.java:522)
>         at
> java.util.concurrent.LinkedBlockingDeque.poll(LinkedBlockingDeque.java:684)
>         at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.body(ServerImpl.java:5779)
>         at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.body(ServerImpl.java:2161)
>         at
> org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> [10:35:40] Topology snapshot [ver=9, servers=1, clients=0, CPUs=12,
> heap=1.0GB]
> [10:35:40] Ignite node stopped OK [uptime=00:07:53:07]
>
> sometimes,I just find one line:
>        Ignite node stopped OK
>
>
>
>
>
>

Re: Ignite server stop unexpectedly

Posted by Vladimir Ozerov <vo...@gridgain.com>.
Hi,

Looks like you faced split brain situation. Say, you have 3 server nodes -
A, B and C. A-B see each other, B-C see each other, but A-C don't. If you
shut down node B, then nodes A and C will form two independent clusters
which we refer to as "split-brain".

Are you sure that all your sever nodes is able to reach each other?

On Wed, Mar 23, 2016 at 6:49 AM, 张鹏鹏 <zh...@gmail.com> wrote:

> I am just learning Ignite,so maybe this is a dumb question.
>
> I want to test the Partitioned Cache Mode,so I start three Ignite nodes on
> three Server.This is the config:
>
>
> <?xml version="1.0" encoding="UTF-8"?>
>
> <!--
>   Licensed to the Apache Software Foundation (ASF) under one or more
>   contributor license agreements.  See the NOTICE file distributed with
>   this work for additional information regarding copyright ownership.
>   The ASF licenses this file to You under the Apache License, Version 2.0
>   (the "License"); you may not use this file except in compliance with
>   the License.  You may obtain a copy of the License at
>
>        http://www.apache.org/licenses/LICENSE-2.0
>
>   Unless required by applicable law or agreed to in writing, software
>   distributed under the License is distributed on an "AS IS" BASIS,
>   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
>   See the License for the specific language governing permissions and
>   limitations under the License.
> -->
>
> <beans xmlns="http://www.springframework.org/schema/beans"
>        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>        xsi:schemaLocation="
>        http://www.springframework.org/schema/beans
>        http://www.springframework.org/schema/beans/spring-beans.xsd">
>     <bean id="grid.cfg"
> class="org.apache.ignite.configuration.IgniteConfiguration">
>         <property name="peerClassLoadingEnabled" value="true"/>
>         <property name="discoverySpi">
>             <bean
> class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi">
>                 <property name="ipFinder">
>                     <bean
> class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
>                         <property name="addresses">
>                             <list>
>                                 <value>10.20.30.91</value>
>                                 <value>10.20.30.92</value>
>                                 <value>10.20.30.93</value>
>                             </list>
>                         </property>
>                     </bean>
>                 </property>
>             </bean>
>         </property>
>         <property name="cacheConfiguration">
>             <bean
> class="org.apache.ignite.configuration.CacheConfiguration">
>                 <property name="name" value="testCache"/>
>                 <property name="cacheMode" value="PARTITIONED"/>
>                 <property name="backups" value="1"/>
>             </bean>
>         </property>
>     </bean>
> </beans>
>
> I start the nodes use this command:
>
> ./ignite.sh ../../ignite-config.xml >> /opt/ignite.log &
>
>
>
> I start a Client node to write some date to the Server nodes.Simple code
> copy from the Doc.Then I kill one Server node and start the Client again.I
> find that one Ignite server stop unexpectedly.
>
> Sometimes I can find Exceptions like this:
>
>
>    [10:35:40,259][SEVERE][tcp-disco-msg-worker-#2%null%][TcpDiscoverySpi]
> TcpDiscoverSpi's message worker thread failed abnormally. Stopping the node
> in order to prevent cluster wide instability.
> java.lang.InterruptedException
>         at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.reportInterruptAfterWait(AbstractQueuedSynchronizer.java:2014)
>         at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2088)
>         at
> java.util.concurrent.LinkedBlockingDeque.pollFirst(LinkedBlockingDeque.java:522)
>         at
> java.util.concurrent.LinkedBlockingDeque.poll(LinkedBlockingDeque.java:684)
>         at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.body(ServerImpl.java:5779)
>         at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.body(ServerImpl.java:2161)
>         at
> org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> [10:35:40] Topology snapshot [ver=9, servers=1, clients=0, CPUs=12,
> heap=1.0GB]
> [10:35:40] Ignite node stopped OK [uptime=00:07:53:07]
>
> sometimes,I just find one line:
>        Ignite node stopped OK
>
>
>
>
>
>