ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vladislav Pyatkov <vldpyat...@gmail.com>
Subject Re: Ignite Cluster node stopped
Date Thu, 11 Aug 2016 13:01:33 GMT
Hello,

1) It is my mistake. I mean what a log level set as DEBUG for the package
org.apache.ignite.spi.discovery.

2) It the cluster group (172.21.0.181 and 172.21.0.183) was segmented again
at the time?
I think problem of network will do not stable.

3) Unfortunately, in my opinion, this problem bounds with system settings,
but do not with Ignite version.
However upgrade version will be good idea.

*About segmentation:*

*1. Log file from each nodes (including GC log)*

*2. System monitoring from each nodes and during all time (using dstat -t
--top-mem -m -s -g -d --fs --top-io-adv). We are need make sure, which we
have not delay by reason of memory swapping or IO activity.*

*3. Network monitoring for all time . You can to do it through ping, as you
do it before.*

Please, attach all the logs as soon the issue is repeated.

On Thu, Aug 11, 2016 at 1:58 PM, suhuadong <suhuadong888@163.com> wrote:

> hi,
> 1:How to add additional logger to the Discovery classes:
> org.apache.ignite.spi.discovery?
>
> 2:
>  NetWork is ok.
>  Before all server nodes stoped,I deploy shell script that  ping
> 172.21.0.181 from 172.21.0.183 and 172.21.0.183.
> log:
> 64 bytes from 172.21.0.181: icmp_seq=51251 ttl=64 time=0.141 ms 14:14:15
> 64 bytes from 172.21.0.181: icmp_seq=51296 ttl=64 time=0.196 ms 14:15:00
> 64 bytes from 172.21.0.181: icmp_seq=51297 ttl=64 time=0.160 ms 14:15:01
> 64 bytes from 172.21.0.181: icmp_seq=51298 ttl=64 time=0.199 ms 14:15:02
> 64 bytes from 172.21.0.181: icmp_seq=51299 ttl=64 time=0.205 ms 14:15:03
> 64 bytes from 172.21.0.181: icmp_seq=51300 ttl=64 time=0.191 ms 14:15:04
> 64 bytes from 172.21.0.181: icmp_seq=51301 ttl=64 time=0.200 ms 14:15:05
> 64 bytes from 172.21.0.181: icmp_seq=51302 ttl=64 time=0.190 ms 14:15:06
> 64 bytes from 172.21.0.181: icmp_seq=51303 ttl=64 time=0.195 ms 14:15:07
> 64 bytes from 172.21.0.181: icmp_seq=51304 ttl=64 time=0.209 ms 14:15:08
> 64 bytes from 172.21.0.181: icmp_seq=51305 ttl=64 time=0.204 ms 14:15:09
> 64 bytes from 172.21.0.181: icmp_seq=51306 ttl=64 time=0.208 ms 14:15:10
> 64 bytes from 172.21.0.181: icmp_seq=51307 ttl=64 time=0.206 ms 14:15:11
> 64 bytes from 172.21.0.181: icmp_seq=51308 ttl=64 time=0.231 ms 14:15:12
> 64 bytes from 172.21.0.181: icmp_seq=51309 ttl=64 time=0.251 ms 14:15:13
> 64 bytes from 172.21.0.181: icmp_seq=51310 ttl=64 time=0.213 ms 14:15:14
> 64 bytes from 172.21.0.181: icmp_seq=51311 ttl=64 time=0.240 ms 14:15:15
> 64 bytes from 172.21.0.181: icmp_seq=51312 ttl=64 time=0.250 ms 14:15:16
> 64 bytes from 172.21.0.181: icmp_seq=51313 ttl=64 time=0.227 ms 14:15:17
> 64 bytes from 172.21.0.181: icmp_seq=51314 ttl=64 time=0.236 ms 14:15:18
> 64 bytes from 172.21.0.181: icmp_seq=51315 ttl=64 time=0.253 ms 14:15:19
> 64 bytes from 172.21.0.181: icmp_seq=51316 ttl=64 time=0.138 ms 14:15:20
> 64 bytes from 172.21.0.181: icmp_seq=51317 ttl=64 time=0.139 ms 14:15:21
> 64 bytes from 172.21.0.181: icmp_seq=51318 ttl=64 time=0.180 ms 14:15:22
> 64 bytes from 172.21.0.181: icmp_seq=51319 ttl=64 time=0.131 ms 14:15:23
> 64 bytes from 172.21.0.181: icmp_seq=51320 ttl=64 time=0.187 ms 14:15:24
> 64 bytes from 172.21.0.181: icmp_seq=51321 ttl=64 time=0.134 ms 14:15:25
> 64 bytes from 172.21.0.181: icmp_seq=51322 ttl=64 time=0.132 ms 14:15:26
> 64 bytes from 172.21.0.181: icmp_seq=51323 ttl=64 time=0.133 ms 14:15:27
> 64 bytes from 172.21.0.181: icmp_seq=51324 ttl=64 time=0.153 ms 14:15:28
> 64 bytes from 172.21.0.181: icmp_seq=51325 ttl=64 time=0.172 ms 14:15:29
> 64 bytes from 172.21.0.181: icmp_seq=51326 ttl=64 time=0.170 ms 14:15:30
> 64 bytes from 172.21.0.181: icmp_seq=51327 ttl=64 time=0.172 ms 14:15:31
> 64 bytes from 172.21.0.181: icmp_seq=51328 ttl=64 time=0.170 ms 14:15:32
> 64 bytes from 172.21.0.181: icmp_seq=51329 ttl=64 time=0.175 ms 14:15:33
> 64 bytes from 172.21.0.181: icmp_seq=51330 ttl=64 time=0.169 ms 14:15:34
> 64 bytes from 172.21.0.181: icmp_seq=51331 ttl=64 time=0.191 ms 14:15:35
> 64 bytes from 172.21.0.181: icmp_seq=51332 ttl=64 time=0.171 ms 14:15:36
> 64 bytes from 172.21.0.181: icmp_seq=51333 ttl=64 time=0.192 ms 14:15:37
> 64 bytes from 172.21.0.181: icmp_seq=51334 ttl=64 time=0.190 ms 14:15:38
> 64 bytes from 172.21.0.181: icmp_seq=51335 ttl=64 time=0.188 ms 14:15:39
> 64 bytes from 172.21.0.181: icmp_seq=51336 ttl=64 time=0.189 ms 14:15:40
> 64 bytes from 172.21.0.181: icmp_seq=51337 ttl=64 time=0.179 ms 14:15:41
> 64 bytes from 172.21.0.181: icmp_seq=51338 ttl=64 time=0.175 ms 14:15:42
> 64 bytes from 172.21.0.181: icmp_seq=51339 ttl=64 time=0.171 ms 14:15:43
> 64 bytes from 172.21.0.181: icmp_seq=51340 ttl=64 time=0.146 ms 14:15:44
> 64 bytes from 172.21.0.181: icmp_seq=51341 ttl=64 time=0.136 ms 14:15:45
> 64 bytes from 172.21.0.181: icmp_seq=51342 ttl=64 time=0.124 ms 14:15:46
> 64 bytes from 172.21.0.181: icmp_seq=51343 ttl=64 time=0.130 ms 14:15:47
> 64 bytes from 172.21.0.181: icmp_seq=51344 ttl=64 time=0.136 ms 14:15:48
> 64 bytes from 172.21.0.181: icmp_seq=51345 ttl=64 time=0.129 ms 14:15:49
> 64 bytes from 172.21.0.181: icmp_seq=51346 ttl=64 time=0.175 ms 14:15:50
> 64 bytes from 172.21.0.181: icmp_seq=51347 ttl=64 time=0.168 ms 14:15:51
> 64 bytes from 172.21.0.181: icmp_seq=51348 ttl=64 time=0.138 ms 14:15:52
> 64 bytes from 172.21.0.181: icmp_seq=51349 ttl=64 time=0.144 ms 14:15:53
> 64 bytes from 172.21.0.181: icmp_seq=51350 ttl=64 time=0.152 ms 14:15:54
> 64 bytes from 172.21.0.181: icmp_seq=51351 ttl=64 time=0.135 ms 14:15:55
> 64 bytes from 172.21.0.181: icmp_seq=51352 ttl=64 time=0.134 ms 14:15:56
> 64 bytes from 172.21.0.181: icmp_seq=51353 ttl=64 time=0.133 ms 14:15:57
> 64 bytes from 172.21.0.181: icmp_seq=51354 ttl=64 time=0.177 ms 14:15:58
> 64 bytes from 172.21.0.181: icmp_seq=51355 ttl=64 time=0.127 ms 14:15:59
>
> 3:Faced with the problem,I plan to upgrade ignite from 1.6 to 1.7。
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Ignite-Cluster-node-stopped-tp6608p6962.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>



-- 
Vladislav Pyatkov

Mime
View raw message