Re: Node fauliure

Hi Anil, Unfortunatelly, I have no luck to reproduce it. On Mon, Feb 27, 2017 at 3:21 PM, Anil wrote: > Hi Andrey, > > thanks for looking into it. could you please share more details around the > bug ? this helps us. > > Thanks. > > On 27 February 2017 at 17:27, Andrey

Re: Node fauliure

Hi Andrey, thanks for looking into it. could you please share more details around the bug ? this helps us. Thanks. On 27 February 2017 at 17:27, Andrey Mashenkov wrote: > Thanks, It was very helpful. > > Seems, Offheap with swap enabled funcionality has a bug. > > On

Re: Node fauliure

Thanks, It was very helpful. Seems, Offheap with swap enabled funcionality has a bug. On Mon, Feb 27, 2017 at 2:46 PM, Anil wrote: > Hi Andrey, > > I set both off heap cache and swap enabled = true. > > Thanks > > On 27 February 2017 at 16:48, Andrey Mashenkov

Re: Node fauliure

Hi Andrey, I set both off heap cache and swap enabled = true. Thanks On 27 February 2017 at 16:48, Andrey Mashenkov wrote: > Hi Anil, > > One more question. Did you use Offheap cache or may be SwapEnabled=true is > set? > > > On Sat, Feb 25, 2017 at 5:14 AM, Anil

Re: Node fauliure

Hi Anil, One more question. Did you use Offheap cache or may be SwapEnabled=true is set? On Sat, Feb 25, 2017 at 5:14 AM, Anil wrote: > Thank you Andrey. > -- Best regards, Andrey V. Mashenkov

Re: Node fauliure

Thank you Andrey.

Re: Node fauliure

Hi Anil, I've created a Jira ticket [1] for SIGSEGV JVM crash. So, you can track it. [1] https://issues.apache.org/jira/browse/IGNITE-4751 On Fri, Feb 24, 2017 at 4:41 PM, Andrey Mashenkov < andrey.mashen...@gmail.com> wrote: > Hi Anil, > > Partition processing time can be high due to

Re: Node fauliure

Hi Anil, Partition processing time can be high due to non-uniform data distribution when data collocation or bad affinity function used. It is ok for collocate data, and it is shouldn't be an issue if partition size variation is low enough and you iterate over partitions in parallel manner.

Re: Node fauliure

Hi Andrey, if you notice in the log, time taken to process the partition is high ( > 15 sec). Not sure what is causing that high query time. In my case, both caches are collocated, and eqId column is indexed and setLocal is true for the query. I wonder if my approach is correct. please correct

Re: Node fauliure

Hi Andrey, I have attached the log. thanks. Thanks. On 24 February 2017 at 18:16, Andrey Mashenkov wrote: > Hi Anil, > > Would you please provide ignite logs as well? > > > On Fri, Feb 24, 2017 at 3:33 PM, Andrey Gura wrote: > >> Hi, Anil >>

Re: Node fauliure

Hi Anil, Would you please provide ignite logs as well? On Fri, Feb 24, 2017 at 3:33 PM, Andrey Gura wrote: > Hi, Anil > > Could you please provide crash dump? In your case it is > /opt/ignite-manager/api/hs_err_pid18543.log file. > > On Fri, Feb 24, 2017 at 9:05 AM, Anil

Re: Node fauliure

Hi, Anil Could you please provide crash dump? In your case it is /opt/ignite-manager/api/hs_err_pid18543.log file. On Fri, Feb 24, 2017 at 9:05 AM, Anil wrote: > Hi , > > I see the node is down with following error while running compute task > > > # A fatal error has been

Node fauliure

Hi , I see the node is down with following error while running compute task # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7facd5cae561, pid=18543, tid=0x7fab8a9ea700 # # JRE version: OpenJDK Runtime Environment (8.0_111-b14) (build