Exception on Ignite shutdown

classic Classic list List threaded Threaded
3 messages Options
colinc colinc
Reply | Threaded
Open this post in threaded view
|

Exception on Ignite shutdown

I'm running some tests on an Ignite cluster using an Ignite client. I'm receiving a stacktrace quite regularly in the client - especially when the cluster is freshly started. The exception occurs at the point that the client is closed down (i.e. the try block completes) - see below log trace.

The exception doesn't seem to be related to what the test is actually doing with Ignite.

        public void helloWorldCompute() {
                Ignition.setClientMode(true);              
                try (Ignite ignite = Ignition.start(CONFIG)) {
                        ignite.compute().broadcast(() -> System.out.println("Hello World"));
                }
        }

INFO  2016-06-09 11:30:49,385   [Log4J Redirect INFO-1] AladdinLog4JAppender$SystemOutProxy - [11:30:49] Topology snapshot [ver=2, servers=1, clients=1, CPUs=8, heap=4.5GB]

[11:30:49,666][SEVERE][tcp-client-disco-sock-writer-#2%null%][TcpDiscoverySpi] Failed to send message: TcpDiscoveryPingResponse [clientExists=false, super=TcpDiscoveryAbstractMessage [sndNodeId=null, id=1e3d6b43551-cdbda7fe-4fd6-4339-855f-25d02ebb03bf, verifierNodeId=null, topVer=0, pendingIdx=0, failedNodes=null, isClient=true]]
class org.apache.ignite.IgniteCheckedException: Failed to serialize object: TcpDiscoveryPingResponse [clientExists=false, super=TcpDiscoveryAbstractMessage [sndNodeId=null, id=1e3d6b43551-cdbda7fe-4fd6-4339-855f-25d02ebb03bf, verifierNodeId=null, topVer=0, pendingIdx=0, failedNodes=null, isClient=true]]
        at org.apache.ignite.marshaller.jdk.JdkMarshaller.marshal(JdkMarshaller.java:82)
        at org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.writeToSocket(TcpDiscoverySpi.java:1381)
        at org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.writeToSocket(TcpDiscoverySpi.java:1352)
        at org.apache.ignite.spi.discovery.tcp.ClientImpl$SocketWriter.body(ClientImpl.java:1071)
        at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
Caused by: java.net.SocketException: Socket closed
        at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:116)
        at java.net.SocketOutputStream.write(SocketOutputStream.java:153)
        at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
        at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
        at org.apache.ignite.marshaller.jdk.JdkMarshallerOutputStreamWrapper.flush(JdkMarshallerOutputStreamWrapper.java:58)
        at java.io.ObjectOutputStream$BlockDataOutputStream.flush(ObjectOutputStream.java:1823)
        at java.io.ObjectOutputStream.flush(ObjectOutputStream.java:719)
        at org.apache.ignite.marshaller.jdk.JdkMarshaller.marshal(JdkMarshaller.java:79)
        ... 4 more
INFO  2016-06-09 11:30:49,677   [Log4J Redirect INFO-1] AladdinLog4JAppender$SystemOutProxy - [11:30:49] Ignite node stopped OK [uptime=00:00:00:292]


Is this a cause for concern, or just something I should ignore? Is there any way to supress the error?

Thanks,
Colin.
colinc colinc
Reply | Threaded
Open this post in threaded view
|

Re: Exception on Ignite shutdown

By the way, I only get this error with Ignite 1.6. Switching back to 1.5 it goes away.
Denis Magda Denis Magda
Reply | Threaded
Open this post in threaded view
|

Re: Exception on Ignite shutdown

In reply to this post by colinc
Hi Colin,

Please properly subscribe to the user list (this way we will not have to manually approve your emails). All you need to do is send an email to ì user-subscribe@ignite.apache.orgî and follow simple instructions in the reply.

In fact there is no reason to worry about this kind of exceptions on a node shutdown. There can be many opened I/O connections that are used in parallel by Ignite internals and the chances that you will see an exception like this on the node shutdown are high. In order to suppress the error you need to set severity level to critical for org.apache.ignite.spi.discovery.tcp.ClientImpl class. But I wouldn't do this because it will turn off useful logging that may be helpful at the time when the client node is being used.

--
Denis

-----------------------

I'm running some tests on an Ignite cluster using an Ignite client. I'm receiving a stacktrace quite regularly in the client - especially when the cluster is freshly started. The exception occurs at the point that the client is closed down (i.e. the try block completes) - see below log trace.

The exception doesn't seem to be related to what the test is actually doing with Ignite.

        public void helloWorldCompute() {
                Ignition.setClientMode(true);              
                try (Ignite ignite = Ignition.start(CONFIG)) {
                        ignite.compute().broadcast(() -> System.out.println("Hello World"));
                }
        }

INFO  2016-06-09 11:30:49,385   [Log4J Redirect INFO-1] AladdinLog4JAppender$SystemOutProxy - [11:30:49] Topology snapshot [ver=2, servers=1, clients=1, CPUs=8, heap=4.5GB]

[11:30:49,666][SEVERE][tcp-client-disco-sock-writer-#2%null%][TcpDiscoverySpi] Failed to send message: TcpDiscoveryPingResponse [clientExists=false, super=TcpDiscoveryAbstractMessage [sndNodeId=null, id=1e3d6b43551-cdbda7fe-4fd6-4339-855f-25d02ebb03bf, verifierNodeId=null, topVer=0, pendingIdx=0, failedNodes=null, isClient=true]]
class org.apache.ignite.IgniteCheckedException: Failed to serialize object: TcpDiscoveryPingResponse [clientExists=false, super=TcpDiscoveryAbstractMessage [sndNodeId=null, id=1e3d6b43551-cdbda7fe-4fd6-4339-855f-25d02ebb03bf, verifierNodeId=null, topVer=0, pendingIdx=0, failedNodes=null, isClient=true]]
        at org.apache.ignite.marshaller.jdk.JdkMarshaller.marshal(JdkMarshaller.java:82)
        at org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.writeToSocket(TcpDiscoverySpi.java:1381)
        at org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.writeToSocket(TcpDiscoverySpi.java:1352)
        at org.apache.ignite.spi.discovery.tcp.ClientImpl$SocketWriter.body(ClientImpl.java:1071)
        at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
Caused by: java.net.SocketException: Socket closed
        at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:116)
        at java.net.SocketOutputStream.write(SocketOutputStream.java:153)
        at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
        at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
        at org.apache.ignite.marshaller.jdk.JdkMarshallerOutputStreamWrapper.flush(JdkMarshallerOutputStreamWrapper.java:58)
        at java.io.ObjectOutputStream$BlockDataOutputStream.flush(ObjectOutputStream.java:1823)
        at java.io.ObjectOutputStream.flush(ObjectOutputStream.java:719)
        at org.apache.ignite.marshaller.jdk.JdkMarshaller.marshal(JdkMarshaller.java:79)
        ... 4 more
INFO  2016-06-09 11:30:49,677   [Log4J Redirect INFO-1] AladdinLog4JAppender$SystemOutProxy - [11:30:49] Ignite node stopped OK [uptime=00:00:00:292]


Is this a cause for concern, or just something I should ignore? Is there any way to supress the error?

Thanks,
Colin.