Streaming test

[waterg]

Hello all,

I'm testing streaming input data and call a service deployed. Two things
happened quite confusing and could someone in the community help?

1. I print a '.' in StreamVisitor.from method to show it's running, and call
service via proxy. It actually ran for over 17K but then stopped/stuck. The
file I used to stream data in has over 1M records in it.

2. I also print a '.' in the service method to show it's being called. It
only printed couple dots and seemed to stuck as well.

First I thought, the message queue was too small, but increasing it to 10240
didn't change the behavior.  

What shall I do next to see where it might have got stuck?

Btw, the memory policy looks like this







and cache has a expiry policy looks like this.














--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Streaming-test-tp14039.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite 2.0 visor issue

[Vasiliy Sisko]

Hello @Amit Pundir

Visor show “Empty topology” message for “top” command when it can not find
nodes. Please check your discovery configuration. It should contain valid IP
addresses and ports. F.e. address format:
  127.0.0.1:47500..47510
That addresses should be available from system where visor cli is started.

Visor cli start internal node. So you should add address of visor cli into
discovery configuration:
  IP Address 1
  IP Address 2
  IP Address 3
  IP Address 4
  Visor IP Address



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Ignite-2-0-visor-issue-tp12460p14038.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Small value for IGNITE_ATOMIC_CACHE_DELETE_HISTORY_SIZE

[charly]

Hey everyone, 

We use Ignite 1.8 and see a difference in heap used when lowering the value
for IGNITE_ATOMIC_CACHE_DELETE_HISTORY_SIZE. I'm not sure to understand what
it's going to happen if we decrease that value on production. Could someone
clear that up for me please? From what I understand, deleted entries go in
that queue for cleaning, where one thread per cache is in charge of cleaning
the queue. But what if the queue is full? I might have missed that
information in the documentation, my bad if I did.

Maybe on the same subject, is it going to slow down the free up of the heap
after cache.destroy()? We have a use-case where we delete 4 caches at the
same time containing ~500k entries heavily indexed. When doing so, it takes
few minutes for the heap to decrease as you can see here
http://imgur.com/a/kPsSc . We would not want to extend the time to free up
memory even more.

More information about our setup:
 - on heap (we'll eventually move to off heap but back then we could not
make Ignite 1.8 to free up memory at all with our version of glibc. It would
work with jmalloc but that was not permitted on production at that time).
 - no backup
 - atomicity mode: atomic
 - cache mode: partitioned
 - cluster of 4 nodes
 - jvm options: -J-DIGNITE_LONG_OPERATIONS_DUMP_TIMEOUT=30 -J-Xms12g
-J-Xmx12g -J-server -J-XX:+UseParNewGC -J-XX:+UseConcMarkSweepGC
-J-XX:+UseTLAB -J-XX:NewSize=128m -J-XX:MaxNewSize=128m
-J-XX:MaxTenuringThreshold=0 -J-XX:SurvivorRatio=1024
-J-XX:+UseCMSInitiatingOccupancyOnly -J-XX:CMSInitiatingOccupancyFraction=10
-J-XX:MaxGCPauseMillis=1000 -J-XX:InitiatingHeapOccupancyPercent=10
-J-XX:+UseCompressedOops -J-XX:ParallelGCThreads=8 -J-XX:ConcGCThreads=8
-J-XX:+PrintGCDetails -J-XX:+PrintGCTimeStamps -J-XX:+PrintGCDateStamps
-J-XX:+UseGCLogFileRotation -J-XX:NumberOfGCLogFiles=10
-J-XX:GCLogFileSize=100M -J-Xloggc:/tmp/ignite-gc.log
-J-Dcom.sun.management.jmxremote.port=49130

Thanks for your help,
Charly





--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Small-value-for-IGNITE-ATOMIC-CACHE-DELETE-HISTORY-SIZE-tp14037.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: How does Ignite Lucene based text indexing & querying work if a field has comma separated values

[Muthu]

Okay...thanks for the input..just to understand better the comma is needed
with space to make sure it tokenizes the entire words in between as tokens?

Regards,
Muthu

On Wed, Jun 21, 2017 at 8:58 AM, Andrey Mashenkov <
andrey.mashen...@gmail.com> wrote:

> Not quite, comma separated String will be tokenized by Lucene
> StandartTokenizer,
> according to Unicode standard [1].
>
> I'd recommend to use ", " (comma with a space character) as separator.
>
> [1] http://unicode.org/reports/tr29/
>
> On Tue, Jun 20, 2017 at 11:55 PM, Muthu  wrote:
>
>> The objects in my ignite cache have a List as member...so i have
>> to change it to a comma separated String if i have to able to perform text
>> searches..correct?
>>
>> Regards,
>> Muthu
>>
>> On Tue, Jun 20, 2017 at 1:49 PM, Muthu  wrote:
>>
>>> Okay..alrite..thanks Andrey.
>>>
>>> Regards,
>>> Muthu
>>>
>>> On Tue, Jun 20, 2017 at 1:30 PM, Andrey Mashenkov <
>>> andrey.mashen...@gmail.com> wrote:
>>>
 Hi,
 I mean object fields which are type of String.

 20 июня 2017 г. 23:04 пользователь "Muthu" 
 написал:

 Okay...btw what is an object String?
>
> Regards,
> Muthu
>
> On Sat, Jun 17, 2017 at 1:53 AM, Andrey Mashenkov <
> andrey.mashen...@gmail.com> wrote:
>
>> No, only Strings and object String fields are supported.
>>
>> 16 июня 2017 г. 21:27 пользователь "Muthu" 
>> написал:
>>
>> Great!...thanks for the info...how about a list of strings
>> (List)...will it also be handled (an array value in the key-value
>> pair)?
>>
>> Regards,
>> Muthu
>>
>> On Fri, Jun 16, 2017 at 2:03 AM, Andrey Mashenkov <
>> andrey.mashen...@gmail.com> wrote:
>>
>>> Hi Muthu,
>>>
>>> Yes, field value will be tokenized with Lucene StandartAnalyzer [1].
>>>
>>> [1] http://lucene.apache.org/core/3_5_0/api/core/org/apache/
>>> lucene/analysis/standard/StandardAnalyzer.html
>>>
>>> On Fri, Jun 16, 2017 at 2:45 AM, Muthu 
>>> wrote:
>>>
 Folks,

 If a field annotated with @QueryTextField contains comma separated
 values would this be tokenized before being indexed by Lucene? How 
 does it
 work?

 Regards,
 Muthu

>>>
>>>
>>>
>>> --
>>> Best regards,
>>> Andrey V. Mashenkov
>>>
>>
>>
>>
>
>>>
>>
>
>
> --
> Best regards,
> Andrey V. Mashenkov
>

Re: PCF tile for Ignite

[vdpyatkov]

Hi,

I have not seen Ignite containerized within PCF, but I have no see any
limitation of that yet.
May be anyone from Community know about Ignite for PFC?



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/PCF-tile-for-Ignite-tp12466p14034.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: How does Ignite Lucene based text indexing & querying work if a field has comma separated values

[Andrey Mashenkov]

Not quite, comma separated String will be tokenized by Lucene
StandartTokenizer,
according to Unicode standard [1].

I'd recommend to use ", " (comma with a space character) as separator.

[1] http://unicode.org/reports/tr29/

On Tue, Jun 20, 2017 at 11:55 PM, Muthu  wrote:

> The objects in my ignite cache have a List as member...so i have
> to change it to a comma separated String if i have to able to perform text
> searches..correct?
>
> Regards,
> Muthu
>
> On Tue, Jun 20, 2017 at 1:49 PM, Muthu  wrote:
>
>> Okay..alrite..thanks Andrey.
>>
>> Regards,
>> Muthu
>>
>> On Tue, Jun 20, 2017 at 1:30 PM, Andrey Mashenkov <
>> andrey.mashen...@gmail.com> wrote:
>>
>>> Hi,
>>> I mean object fields which are type of String.
>>>
>>> 20 июня 2017 г. 23:04 пользователь "Muthu" 
>>> написал:
>>>
>>> Okay...btw what is an object String?

 Regards,
 Muthu

 On Sat, Jun 17, 2017 at 1:53 AM, Andrey Mashenkov <
 andrey.mashen...@gmail.com> wrote:

> No, only Strings and object String fields are supported.
>
> 16 июня 2017 г. 21:27 пользователь "Muthu" 
> написал:
>
> Great!...thanks for the info...how about a list of strings
> (List)...will it also be handled (an array value in the key-value
> pair)?
>
> Regards,
> Muthu
>
> On Fri, Jun 16, 2017 at 2:03 AM, Andrey Mashenkov <
> andrey.mashen...@gmail.com> wrote:
>
>> Hi Muthu,
>>
>> Yes, field value will be tokenized with Lucene StandartAnalyzer [1].
>>
>> [1] http://lucene.apache.org/core/3_5_0/api/core/org/apache/
>> lucene/analysis/standard/StandardAnalyzer.html
>>
>> On Fri, Jun 16, 2017 at 2:45 AM, Muthu 
>> wrote:
>>
>>> Folks,
>>>
>>> If a field annotated with @QueryTextField contains comma separated
>>> values would this be tokenized before being indexed by Lucene? How does 
>>> it
>>> work?
>>>
>>> Regards,
>>> Muthu
>>>
>>
>>
>>
>> --
>> Best regards,
>> Andrey V. Mashenkov
>>
>
>
>

>>
>


-- 
Best regards,
Andrey V. Mashenkov

Re: Ignite Custom Java Code calling

[ezhuravlev]

Hi,

It's not clear what you want to do. Why don't you just use simple sql
queries? Why do you think that you need @QuerySQLFunction?

Evgenii



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Ignite-Custom-Java-Code-calling-tp13819p14032.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Hadoop + IGFS + Hive+Tez

[Mimmo Celano]

Hi, thanks for reply.

Ignite configuration is a default configuration in
config/hadoop/default-configuration.xml i don't change anything. Hadoop
configuration is a cluster o 3 node, it work properly withouth ignite. The
problem is in a connection between the client and the 2 server. I don't
change anything in ignite file configuration, the only things i do is the
code who i posted.
I agree with you that is a configuration problem but i don't know how to
configure it. The 2 server node are slave in hadoop configuration, but i
don't think it's a problem. I don't find another ignite logs other that
posted... I don't use tez. You think that i use another configuration for
ignite instead the default for hadoop? I want just save all word of
wordcount processing in a grid cache between 2 node server. There's no log
of the task because the application crash before task..

The node are connected via lan. Thanks

2017-06-21 16:59 GMT+02:00 Taras Ledkov :

> Hi,
>
> Please provide:
> - ignite configuration;
> - ignite logs;
> - hadoop configurations;
> - logs of the task.
>
> I don't have tez experience but the cause of the problem looks like Ignite
> is not configured properly.
>
> On 21.06.2017 8:39, ishan-jain wrote:
>
> Hi all, I have configured hive to run over IGFS for hadoop file system. I am
> trying to install tez on it but am not able to configure tez-site.xml and
> bashrc file properly.
> I have downloaded a binary tez bin to my system (0.8.4)
> I Put the tez tar ball in hdfs dire /user/tez
> I pointed my tez.lib.uri to this path
> I have configured mapred-site.xml to use yarn-tez
> I have hive already configured to run over igfs.
> But when i execute the mapred task it says
> Failed to connect to shared memory endpoint .
> I am using TCP as ipc endpoint configuration and have enabled ipc endpoint
> property.
>
>
>
> --
> View this message in context: 
> http://apache-ignite-users.70518.x6.nabble.com/Hadoop-IGFS-Hive-Tez-tp14012.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
>
> --
> Taras Ledkov
> Mail-To: tled...@gridgain.com
>
>

Re: Hadoop + IGFS + Hive+Tez

[Taras Ledkov]

Hi,

Please provide:
- ignite configuration;
- ignite logs;
- hadoop configurations;
- logs of the task.

I don't have tez experience but the cause of the problem looks like 
Ignite is not configured properly.



On 21.06.2017 8:39, ishan-jain wrote:

Hi all, I have configured hive to run over IGFS for hadoop file system. I am
trying to install tez on it but am not able to configure tez-site.xml and
bashrc file properly.
I have downloaded a binary tez bin to my system (0.8.4)
I Put the tez tar ball in hdfs dire /user/tez
I pointed my tez.lib.uri to this path
I have configured mapred-site.xml to use yarn-tez
I have hive already configured to run over igfs.
But when i execute the mapred task it says
Failed to connect to shared memory endpoint .
I am using TCP as ipc endpoint configuration and have enabled ipc endpoint
property.



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Hadoop-IGFS-Hive-Tez-tp14012.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.


--
Taras Ledkov
Mail-To: tled...@gridgain.com

Re: Ignite Cassandra Exception

[nash1k]

hi!
Did you resolve this problem? We have the same issue and can't do anything
with it. Yep cassandra is under high load but how we can fix it? More
cassandra nodes or more ignite nodes?



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Ignite-Cassandra-Exception-tp13529p14029.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Hadoop and Ignite, Problem grid cache

[mimmo_c]

Hi, I'm trying to configure Ignite for hadoop. I would like to store the data
of a wordcount inside a grid cache between two server node. I'm on a Cluster
of 33 nodes but i want try with 3 node. 
When I start two node in server mode they connect itselfef with ignite.sh
. From the master node I run hadoop with
the jar of wordcount in wich just start ignite in client mode and try to
start a cache . For configuration i use default-configuration.xml in
config/hadoop. 

When i start hadoop from master it gives this error 


>>>__    
>>>   /  _/ ___/ |/ /  _/_  __/ __/  
>>>  _/ // (7 7// /  / / / _/
>>> /___/\___/_/|_/___/ /_/ /___/   
>>> 
>>> ver. 2.0.0#20170430-sha1:d4eef3c6
>>> 2017 Copyright(C) Apache Software Foundation
>>> 
>>> Ignite documentation: http://ignite.apache.org

2017-06-21 13:53:47,737 INFO  [main] internal.IgniteKernal
(Log4JLogger.java:info(475)) - Config URL:
file:/home/hduser/apache-ignite-2.0.0-src/config/hadoop/default-config.xml
2017-06-21 13:53:47,737 INFO  [main] internal.IgniteKernal
(Log4JLogger.java:info(475)) - Daemon mode: off
2017-06-21 13:53:47,737 INFO  [main] internal.IgniteKernal
(Log4JLogger.java:info(475)) - OS: Linux 4.4.0-79-generic amd64
2017-06-21 13:53:47,737 INFO  [main] internal.IgniteKernal
(Log4JLogger.java:info(475)) - OS user: hduser
2017-06-21 13:53:47,739 INFO  [main] internal.IgniteKernal
(Log4JLogger.java:info(475)) - PID: 22611
2017-06-21 13:53:47,739 INFO  [main] internal.IgniteKernal
(Log4JLogger.java:info(475)) - Language runtime: Java Platform API
Specification ver. 1.8
2017-06-21 13:53:47,739 INFO  [main] internal.IgniteKernal
(Log4JLogger.java:info(475)) - VM information: Java(TM) SE Runtime
Environment 1.8.0_131-b11 Oracle Corporation Java HotSpot(TM) 64-Bit Server
VM 25.131-b11
2017-06-21 13:53:47,740 INFO  [main] internal.IgniteKernal
(Log4JLogger.java:info(475)) - VM total memory: 0.87GB
2017-06-21 13:53:47,740 INFO  [main] internal.IgniteKernal
(Log4JLogger.java:info(475)) - Remote Management [restart: off, REST: off,
JMX (remote: off)]
2017-06-21 13:53:47,740 INFO  [main] internal.IgniteKernal
(Log4JLogger.java:info(475)) -
IGNITE_HOME=/home/hduser/apache-ignite-2.0.0-src
2017-06-21 13:53:47,741 INFO  [main] internal.IgniteKernal
(Log4JLogger.java:info(475)) - VM arguments: [-Xmx1000m,
-Dhadoop.log.dir=/usr/local/hadoop/logs, -Dhadoop.log.file=hadoop.log,
-Dhadoop.home.dir=/usr/local/hadoop, -Dhadoop.id.str=,
-Dhadoop.root.logger=INFO,console,
-Djava.library.path=/usr/local/hadoop/lib/native,
-Dhadoop.policy.file=hadoop-policy.xml, -Djava.net.preferIPv4Stack=true,
-Dhadoop.security.logger=INFO,NullAppender]
2017-06-21 13:53:47,741 INFO  [main] internal.IgniteKernal
(Log4JLogger.java:info(475)) - Configured caches [in 'default' memoryPolicy:
['ignite-sys-cache', 'ignite-hadoop-mr-sys-cache',
'ignite-atomics-sys-cache', 'igfs-internal-igfs-meta',
'igfs-internal-igfs-data']]
2017-06-21 13:53:47,744 INFO  [main] internal.IgniteKernal
(Log4JLogger.java:info(475)) - 3-rd party licenses can be found at:
/home/hduser/apache-ignite-2.0.0-src/libs/licenses
2017-06-21 13:53:47,746 WARN  [pub-#14%null%] internal.GridDiagnostic
(Log4JLogger.java:warning(480)) - Initial heap size is 504MB (should be no
less than 512MB, use -Xms512m -Xmx512m).
2017-06-21 13:53:47,794 INFO  [main] plugin.IgnitePluginProcessor
(Log4JLogger.java:info(475)) - Configured plugins:
2017-06-21 13:53:47,794 INFO  [main] plugin.IgnitePluginProcessor
(Log4JLogger.java:info(475)) -   ^-- None
2017-06-21 13:53:47,794 INFO  [main] plugin.IgnitePluginProcessor
(Log4JLogger.java:info(475)) - 
2017-06-21 13:53:47,842 INFO  [main] tcp.TcpCommunicationSpi
(Log4JLogger.java:info(475)) - Successfully bound communication NIO server
to TCP port [port=47100, locHost=0.0.0.0/0.0.0.0, selectorsCnt=4,
selectorSpins=0, pairedConn=false]
2017-06-21 13:53:47,846 WARN  [main] tcp.TcpCommunicationSpi
(Log4JLogger.java:warning(480)) - Message queue limit is set to 0 which may
lead to potential OOMEs when running cache operations in FULL_ASYNC or
PRIMARY_SYNC modes due to message queues growth on sender and receiver
sides.
2017-06-21 13:53:47,864 WARN  [main] noop.NoopCheckpointSpi
(Log4JLogger.java:warning(480)) - Checkpoints are disabled (to enable
configure any GridCheckpointSpi implementation)
2017-06-21 13:53:47,889 WARN  [main] collision.GridCollisionManager
(Log4JLogger.java:warning(480)) - Collision resolution is disabled (all jobs
will be activated upon arrival).
2017-06-21 13:53:47,890 INFO  [main] internal.IgniteKernal
(Log4JLogger.java:info(475)) - Security status [authentication=off,
tls/ssl=off]
2017-06-21 13:53:48,181 INFO  [main] rest.GridRestProcessor
(Log4JLogger.java:info(475)) - REST protocols do not start on client node.
To start the protocols on client node set
'-DIGNITE_REST_START_ON_CLIENT=true' system property.
2017-06-21 13:53:48,230 INFO  [main] loopback.IpcServerTcpEndpoint
(Log4JLogger.java:info(475)) - IPC server loopback endpoint started
[po

Hive +Tez over Ignite

[ishan-jain]

Hi
Can someone help me configure tez engine on ignite. 



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Hive-Tez-over-Ignite-tp14027.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Common query in Ignite

[dkarachentsev]

Hi,

1. You may run query from client node [1] or with REST API [2]. Client mode
requires that it should be accessible from cluster, at least 47500 and 47100
ports should be opened on machine with client node. REST allows calling
queries and other Ignite API without opening that ports.

2. Java client node doesn't keeps any cache data, you don't need to
configure that.

3. No, this doesn't supported.

4. You can use custom functions in query with @QuerySqlFunction annotation
[3]. Unfortunately I'm not familiar with Infinispan, but Ignite fully
supports regular ANSI SQL.

5. Answered in 1.

[1] https://apacheignite.readme.io/docs/clients-vs-servers
[2] https://apacheignite.readme.io/docs/rest-api
[3]
https://ignite.apache.org/releases/mobile/org/apache/ignite/cache/query/annotations/QuerySqlFunction.html

Thanks!
-Dmitry.



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Common-query-in-Ignite-tp13985p14026.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite-cassandra module issue

[dkarachentsev]

Hi,

Is it possible to provide a simple reproducer?
Answering your second question, yes, you can use BinaryObject as persistence
class name.

Thanks!
-Dmitry.




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Ignite-cassandra-module-issue-tp13808p14025.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Facing problem in examples.

[Igor Sapego]

Denis, great idea!

Best Regards,
Igor

On Wed, Jun 21, 2017 at 6:43 AM, Denis Magda  wrote:

> Thanks for confirming that the issue has been solved.
>
> I’ve added a special documentation section [1] to avoid issues like that
> in the future and placed "Platforms Interoperability Getting Started”
> callout block to C++ Getting Started Guide [2] to draw attention to these
> extra settings.
>
> [1] https://apacheignite-cpp.readme.io/docs/cross-platform-
> interoperability#binary-marshaller-configuration <
> https://apacheignite-cpp.readme.io/docs/cross-platform-
> interoperability#binary-marshaller-configuration>
> [2] https://apacheignite-cpp.readme.io/v2.0/docs/getting-
> started-1#section-start-from-command-line  readme.io/v2.0/docs/getting-started-1#section-start-from-command-line>
>
> —
> Denis
>
> > On Jun 20, 2017, at 8:05 AM, Rahul.S  wrote:
> >
> > BINGO!
> > that helped alot, it is working now thank you very much people for such a
> > positive and good support...
> >
> >
> >
> > --
> > View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Facing-problem-in-examples-tp13894p13981.html
> > Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
>

Re: encounter issue on ignite 2.0

[dkarachentsev]

Hi,

Could you please share your configurations?

Thanks!
-Dmitry.



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/encounter-issue-on-ignite-2-0-tp13812p14023.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Monitor remote cache in Ignite

[dkarachentsev]

Hi,

You may use Ignite Web Console for that purpose [1].

[1] https://ignite.apache.org/features/datavisualization.html

Thanks!
-Dmitry.



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Monitor-remote-cache-in-Ignite-tp13982p14022.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Apache Ignite client gets disconnected on Amazon EC2 Scale In

[robbie]

1.9.1



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

Re: Apache Ignite client gets disconnected on Amazon EC2 Scale In

[Nikolai Tikhonov]

Which version ignite do you use?

On Wed, Jun 21, 2017 at 6:08 AM, robbie  wrote:

> Hi. Below are the logs for server and client nodes
>
> server:
> https://pastebin.com/ashC5EN8
>
> client:
> https://pastebin.com/xTa0sQ9t
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Apache-Ignite-client-gets-disconnected-on-Amazon-EC2-
> Scale-In-tp13874p14000.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>