ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From robbie <rob.anonu...@gmail.com>
Subject Apache Ignite client gets disconnected on Amazon EC2 Scale In
Date Fri, 16 Jun 2017 12:45:39 GMT
Hi,

So I'm at a loss here on why my Ignite client gets disconnected during scale
ins. Here is my exact scenario:

1) Initial topology is 1- client, 1-server 
2) Client performs multiple compute tasks
3) CPU on server exceeds EC2 Alert value. 
4) Servers increase to 5
5) Compute tasks complete
6) Average CPU usage is lower than defined threshold 
7) Servers get scaled down to 1

In this scenario, my client gets disconnected entirely from the grid. I then
get an exception on the GridDhtPartitionTopologyImpl: 

 Failed to execute compound future reducer: GridCompoundFuture [rdc=null,
initFlag=1, lsnrCalls=0, done=false, cancelled=false, err=null,
futs=[true]]class org.apache.ignite.IgniteCheckedException: Index: 512,
Size: 512
2017-06-16 22:19:12,396 ERROR [stderr] (exchange-worker-#105%grid-name%)  
at org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7239)
2017-06-16 22:19:12,397 ERROR [stderr] (exchange-worker-#105%grid-name%)  
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:170)


Then client is shutdown. Has anybody encountered this error before?









--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Apache-Ignite-client-gets-disconnected-on-Amazon-EC2-Scale-In-tp13874.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Mime
View raw message