Re: Unable to identify root cause for node failure

2018-02-20 Thread Mikhail 
Hi, 

First, ignite will take all space that is configured in a data region. if
there's more data then data region can store it will write data to a disk.
However, it's about off-heap memory only, it doesn't use the heap for data
storing(at least by default).
How to configure data region size you can read here:
https://apacheignite.readme.io/docs/memory-configuration

So you need to sum jvm heap size, off-heap size and memory for OS and tools
and this sum must be < total memory your box has.

Thanks,
Mike.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Unable to identify root cause for node failure

2018-02-19 Thread Rahul Pandey 
Hi,
Yes, those logs are full.

Also found that root cause was O.S killing the process, the two nodes were
given 48gb each heap size, on reducing it to 32gb O.S did not kill the
process, but getting OutOfMemoryError while data loading.

Since Ignite Persistance is turned on doesn't data should be spill over to
disk when heap is full?

Thanks,
Rahul Pandey

On Mon, Feb 19, 2018 at 8:52 PM, Mikhail 
wrote:

> Hi Rahul,
>
> at 12:25:03 first node detected that second one is failed:
>
> [12:45:03,251][INFO][exchange-worker-#182][GridCachePartitionExchangeMana
> ger]
> Skipping rebalancing (nothing scheduled) [top=AffinityTopologyVersion
> [topVer=3, minorTopVer=0], evt=NODE_FAILED,
> node=bbdd7792-1309-4941-a7ad-05ed642f62b5]
>
> however, logs for ignite-bbdd7792 is ended at 12:44:14,167
>
> so, something interesting should be in logs after that time, are you sure
> that it's full log?
>
> Thanks,
> Mike.
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

-- 


--

The content of this e-mail is confidential and intended solely for the use 
of the addressee(s). The text of this email (including any attachments) may 
contain information, belonging to Pragmatix Services Private Limited, 
and/or its associates/ group companies/ subsidiaries (the Company), which 
is proprietary and/or confidential or legally privileged in nature or 
exempt from disclosure under applicable law. If you are not the addressee, 
or the person responsible for delivering it to the addressee, any 
disclosure, copying, distribution or any action taken or omitted to be 
taken in reliance on it is prohibited and may be unlawful. If you have 
received this e-mail in error, please notify the sender and remove this 
communication entirely from your system. The recipient acknowledges that no 
guarantee or any warranty is given as to completeness and accuracy of the 
content of the email. The recipient further acknowledges that the views 
contained in the email message are those of the sender and may not 
necessarily reflect those of the Company. Before opening and accessing the 
attachment please check and scan for virus. Thank you.

WARNING: Computer viruses can be transmitted via email. The recipient 
should check this email and any attachments for the presence of viruses. 
The sender or the Company accepts no liability for any damage caused by any 
virus transmitted by this email or errors or omissions.

Re: Unable to identify root cause for node failure

2018-02-19 Thread Mikhail 
Hi Rahul,

at 12:25:03 first node detected that second one is failed:

[12:45:03,251][INFO][exchange-worker-#182][GridCachePartitionExchangeManager]
Skipping rebalancing (nothing scheduled) [top=AffinityTopologyVersion
[topVer=3, minorTopVer=0], evt=NODE_FAILED,
node=bbdd7792-1309-4941-a7ad-05ed642f62b5]

however, logs for ignite-bbdd7792 is ended at 12:44:14,167

so, something interesting should be in logs after that time, are you sure
that it's full log?

Thanks,
Mike.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/