Re: Unreasonable segmentation in Kubernetes on one node reboot

[Roman Guseinov <ro...@gromtech.ru>]

Hi,

According to the last logs, this is a different issue.

2018-09-28T05:25:03.598Z [RxComputationThreadPool-1]/W: Get: batch { keys: 1 
} failed, retrying. 
java.util.concurrent.TimeoutException 
        at 
io.reactivex.internal.operators.flowable.FlowableTimeoutTimed$TimeoutSubscriber.onTimeout(FlowableTimeoutTimed.java:137) 
        at 
io.reactivex.internal.operators.flowable.FlowableTimeoutTimed$TimeoutTask.run(FlowableTimeoutTimed.java:169) 
        at 
io.reactivex.internal.schedulers.ScheduledRunnable.run(ScheduledRunnable.java:66) 
        at 
io.reactivex.internal.schedulers.ScheduledRunnable.call(ScheduledRunnable.java:57) 
        at java.util.concurrent.FutureTask.run(FutureTask.java:266) 
        at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) 
        at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) 
        at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 
        at java.lang.Thread.run(Thread.java:748)

"io.reactivex" is definitely not a part of Apache Ignite. Also, it is not
clear what happens in the process of "GET /health".

I am not sure the last provided deployment files would be enough to
reproduce current issue since they don't have any references to external
libs. Could you share a reproducer (actual YAML-files, client tools,
step-by-step instruction)? Do you use custom application inside with
embedded Ignite node in the Docker image? If yes, could you also upload a
simple maven project at GitHub?

Thanks.

Best Regards,
Roman



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