Thanks Denis.
Sent from my iPhone
> On 9 Apr 2018, at 18:22, Denis Mekhanikov wrote:
>
> There are the following lines in the TcpDiscoverySpi implementation:
>
> if (log.isDebugEnabled())
> log.error("Exception on direct send: " + e.getMessage(), e);
>
> So, these exceptions are shown onl
There are the following lines in the TcpDiscoverySpi implementation:
if (log.isDebugEnabled())
log.error("Exception on direct send: " + e.getMessage(), e);
So, these exceptions are shown only when debug logging is enabled, and they
are logged as errors.
Neeraj, you probably just didn't enabl
Hi Denis,
But this issue does not occur on node2 even if it is started before node1. I
feel even otherwise this message related to Discovery of level SEVERE is a bit
misleading. Wouldn’t it be visible when log level is anything higher than DEBUG
as well ? I agree this is not a functional issue
Hi Denis,
I had a similar logs before and I can confirm I got them when enabled
"debug" level but the log level "severe" was really confusing.
On Fri, Apr 6, 2018, 8:52 AM Denis Mekhanikov wrote:
> Neeraj,
>
> You probably enabled debug logging on the following package:
> *org.apache.ignite.spi
Neeraj,
You probably enabled debug logging on the following package:
*org.apache.ignite.spi.discovery.tcp*
There is nothing wrong in these exceptions actually.
The first connection refused exception happens because there are two hosts
in the IP finder configuration, but when you start the first n
Hi,
I have 2 virtualbox guest OS'es (CentOS7 64-bit) , each having firewalld
stopped and disabled.
The nodes are axlrate-node-1 and axlrate-node-2. I have updated
default-config.xml in both servers
My default-config.xml looks like below :
-d
