Re: Ignite communicating with non ignite servers

[ignite_user2016]

We have SSL enabled on all servers but some how it s trying to attempt
connection on SSL causing heap dumps. Is there a way to disable to external
server try connecting to ignite ? 

2020-09-10 22:52:47,029 WARN [grid-nio-worker-tcp-comm-3-#27%NAME_GRID%]
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi Client
disconnected abruptly due to network connection loss or because the
connection was left open on application shutdown. [cls=class
o.a.i.i.util.nio.GridNioException, msg=Failed to decode SSL data:
GridSelectorNioSessionImpl [worker=DirectNioClientWorker
[super=AbstractNioClientWorker [idx=3, bytesRcvd=13315002728, bytesSent=0,
bytesRcvd0=18, bytesSent0=0, select=true, super=GridWorker
[name=grid-nio-worker-tcp-comm-3, igniteInstanceName=WebGrid,
finished=false, heartbeatTs=1599796365124, hashCode=1230825885,
interrupted=false, runner=grid-nio-worker-tcp-comm-3-#27%WebGrid%]]],
writeBuf=java.nio.DirectByteBuffer[pos=0 lim=32768 cap=32768],
readBuf=java.nio.DirectByteBuffer[pos=18 lim=18 cap=32768], inRecovery=null,
outRecovery=null, closeSocket=true,
outboundMessagesQueueSizeMetric=o.a.i.i.processors.metric.impl.LongAdderMetric@69a257d1,
super=GridNioSessionImpl [locAddr=/*IG_SERVER1*:47101, rmtAddr=/*SEC_SCAN*
SERVER:52082, createTime=1599796365124, closeTime=0, bytesSent=0,
bytesRcvd=18, bytesSent0=0, bytesRcvd0=18, sndSchedTime=1599796365124,
lastSndTime=1599796365124, lastRcvTime=1599796367026, readsPaused=false,
filterChain=FilterChain[filters=[GridNioCodecFilter
[parser=o.a.i.i.util.nio.GridDirectParser@20ca1d6a, directMode=true],
GridConnectionBytesVerifyFilter, SSL filter], accepted=true,
markedForClose=false]]]



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

Re: Ignite communicating with non ignite servers

[ignite_user2016]

we use Nessus security tool, and the module is Tenable.sc which scans the
vulnerability on spring boot app which runs with ignite client.



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

Ignite communicating with non ignite servers

[ignite_user2016]

Recently, we migrated ignite to JDK11, all works well except when we run our
security scan, ignite node tries to connect on that servers and result in
out of memory and heap dump errors.

Is it possible where we can stop that scan server connecting to ignite ? 

Any configuration ? 

help is much appreciated.

And I have observed that ignite visor is also broken where it cant give us
the states for nodes, memory and CPU.

Thanks..
Rishi



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

Re: cache expiry issue

[ignite_user2016]

any reply please ? 

we have 2 node cluster and we are only seeing expiry issues with few cache
entries which never gets expired unless we restart the servers OR clear the
cache ? 

The clearing out cache works and removes the expiry cache values.

appreciate all help here ..



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

cache expiry issue

[ignite_user2016]

we use ignite with spring boot application and seeing issue in production
where few cache entries are not being expired. our configuration is based on
XML, sample configuration as follows - 











we apply this expiry policy on cache configuration as follows - 



#{{cacheName}}*"/>





So I have a questions as follows -
  - Does this configuration looks OK OR we are missing something here ? 
  - why we issues with few cache entries ? 
  - Is there any way we can have a hook to expiry ? OR we can evict the
cache using API ? 
 
   



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

Re: JDK 11 support

[ignite_user2016]

I am running Ignite 2.7 on JDK 11 but getting following error - 

c:\apache-ignite-2.7.0-bin\bin>ignite.bat
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by
org.apache.ignite.internal.util.GridUnsafe$2
(file:/C:/apache-ignite-2.7.0-bin/libs/ignite-core-2.7.0.jar) to field
java.nio.Buffer.address
WARNING: Please consider reporting this to the maintainers of
org.apache.ignite.internal.util.GridUnsafe$2
WARNING: Use --illegal-access=warn to enable warnings of further illegal
reflective access operations
WARNING: All illegal access operations will be denied in a future release
Exception in thread "main" java.lang.ExceptionInInitializerError
at
org.apache.ignite.internal.util.IgniteUtils.(IgniteUtils.java:795)
at
org.apache.ignite.lang.IgniteProductVersion.fromString(IgniteProductVersion.java:305)
at
org.apache.ignite.internal.IgniteVersionUtils.(IgniteVersionUtils.java:71)
at
org.apache.ignite.startup.cmdline.CommandLineStartup.(CommandLineStartup.java:99)
Caused by: java.lang.RuntimeException: jdk.internal.misc.JavaNioAccess class
is unavailable.
at
org.apache.ignite.internal.util.GridUnsafe.javaNioAccessObject(GridUnsafe.java:1453)
at
org.apache.ignite.internal.util.GridUnsafe.(GridUnsafe.java:112)
... 4 more
Caused by: java.lang.IllegalAccessException: class
org.apache.ignite.internal.util.GridUnsafe cannot access class
jdk.internal.misc.SharedSecrets (in module java.base) because module
java.base does not export jdk.internal.misc to unnamed module @689604d9
at
java.base/jdk.internal.reflect.Reflection.newIllegalAccessException(Reflection.java:361)
at
java.base/java.lang.reflect.AccessibleObject.checkAccess(AccessibleObject.java:591)
at java.base/java.lang.reflect.Method.invoke(Method.java:558)
at
org.apache.ignite.internal.util.GridUnsafe.javaNioAccessObject(GridUnsafe.java:1450)
... 5 more
Press any key to continue . . .

c:\apache-ignite-2.7.0-bin\bin>java -version
java version "11.0.1" 2018-10-16 LTS
Java(TM) SE Runtime Environment 18.9 (build 11.0.1+13-LTS)
Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.1+13-LTS, mixed mode)

c:\apache-ignite-2.7.0-bin\bin>control.bat





























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

Re: JDK 11 support

[ignite_user2016]

what version of Ignite run on JDK 11 ? Does any one tried running Ignite on
open JDK 11 ? 



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

Re: SB2 with Ignite 2.6 Sample Application

[ignite_user2016]

I meant I have it locally so if any of our community member needs it I can
provide a sample application.



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

SB2 with Ignite 2.6 Sample Application

[ignite_user2016]

I have a sample application that works on Springboo2 with Ignite 2.6 version,
do let me know if any one more details OR will like to have sample app ? can
post it here on request.

Thanks..



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

Re: Spring upgrade on Ignite

[ignite_user2016]

I fixed the issue with following inclusion in my build gradle - 

configurations.all {
exclude group: "commons-logging", module: "commons-logging"
}

Thanks..
Rishi



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

Spring upgrade on Ignite

[ignite_user2016]

Is there a plan to upgrade spring lib to 5.0 for upcoming release ? 

Currently, Ignite-spring uses Spring 4.3.4 version so if I am running Ignite
with spring boot better to upgrade all the spring libs to 5.1 version.

I run into some weird logging issue since ignite using older version of
spring where it missed out following logs since Ignite using older version
of spring lib.

2018-11-07 09:46:34,098 INFO [main]
org.springframework.boot.web.embedded.undertow.UndertowServletWebServer
Undertow started on port(s) 8080 (http) with context path ''
2018-11-07 09:46:34,099 DEBUG [main]
org.springframework.beans.factory.support.DefaultListableBeanFactory
Returning cached instance of singleton bean 'delegatingApplicationListener'
2018-11-07 09:46:34,099 DEBUG [main]
org.springframework.web.context.support.StandardServletEnvironment Adding
PropertySource 'server.ports' with highest search precedence
2018-11-07 09:46:34,108 INFO [main] demo.SB20CacheApplication Started
SB20CacheApplication in 18.618 seconds (JVM running for 20.738)

The details are as follows - 

On the logging front, Spring Framework 5.0 comes out of the box with Commons
Logging bridge module, named spring-jcl instead of the standard Commons
Logging. Also, this new version will auto detect Log4j 2.x, SLF4J, JUL (
java.util.logging) without any extra bridges.

Thanks..
Rishi



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

RE: Ignite on Spring Boot 2.0

[ignite_user2016]

yes agree it is trivial but my ignite configuration stays in XML files so I
would have to pull that XML configuration in code.. 

I am still wondering why this piece of code stopped working ? 

if (cfgPath != null && cfg != null) {
throw new IllegalArgumentException("Both 'configurationPath' and
'configuration' are " +
"provided. Set only one of these properties if you need
to start a Ignite node inside of " +
"SpringCacheManager. If you already have a node running,
omit both of them and set" +
"'gridName' property.");
}

if (cfgPath != null)
ignite = IgniteSpring.start(cfgPath, springCtx);
else if (cfg != null)
ignite = IgniteSpring.start(cfg, springCtx);
else
ignite = Ignition.ignite(gridName);

so it mean with newer version there is no way Ignition can connect to ignite
with grid name ..



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

RE: Ignite on Spring Boot 2.0

[ignite_user2016]

Do you have any sample here ? the bean define in ignite configuration would
not work with spring boot context. we need to instantiate spring cache
manager with in spring boot context.




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

Re: Ignite on Spring Boot 2.0

[ignite_user2016]

Attaching sample project on spring boot 1 in which Spring Cache Manager
initialize correctly. sb1-cache-app.7z
  



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

Re: Ignite on Spring Boot 2.0

[ignite_user2016]

Please find sample project running on SB 2.0.. when I try to instantiate it
gives following exception - 

2018-10-09 16:54:28.207  WARN 14068 --- [   main]
io.undertow.servlet  : UT015020: Path /* is secured for
some HTTP methods, however it is not secured for [HEAD, DELETE, POST, GET,
CONNECT, OPTIONS, PUT]
[2018-10-09 16:54:30,636][ERROR][main][SpringApplication] Application run
failed
class org.apache.ignite.IgniteIllegalStateException: Ignite instance with
provided name doesn't exist. Did you call Ignition.start(..) to start an
Ignite instance? [name=WebGrid]
at org.apache.ignite.internal.IgnitionEx.grid(IgnitionEx.java:1383)
at org.apache.ignite.Ignition.ignite(Ignition.java:535)
at
org.apache.ignite.cache.spring.SpringCacheManager.onApplicationEvent(SpringCacheManager.java:334)
at
org.apache.ignite.cache.spring.SpringCacheManager.onApplicationEvent(SpringCacheManager.java:146)
at
org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:172)
at
org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:165)
at
org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:139)
at
org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:400)
at
org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:354)
at
org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:888)
at
org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.finishRefresh(ServletWebServerApplicationContext.java:161)
at
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:553)
at
org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:140)
at
org.springframework.boot.SpringApplication.refresh(SpringApplication.java:759)
at
org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:395)
at
org.springframework.boot.SpringApplication.run(SpringApplication.java:327)
at demo.SB20CacheApplication.main(SB20CacheApplication.java:28)
sb20-cache-app.7z
  
cache_log.txt
  



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

RE: Ignite on Spring Boot 2.0

[ignite_user2016]

I will share a sample application soon.. stay tuned ...



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

Re: Ignite on Spring Boot 2.0

[ignite_user2016]

Small update - 

I also upgraded ignite to recent version but no use.

Current version is Ignite 2.0





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

Ignite on Spring Boot 2.0

[ignite_user2016]

Hello..

I am using Ignite with Spring boot version 1.5.8, all works well but when I
try to upgrade my spring boot app to 2.0.1 version some how
SpringCacheManager does not work.

Here is my piece of code - 

   /**
 * Provides SpringCacheManager to enable 2nd level caching on Ignite
 *
 * @return SpringCacheManager
 */
@Bean
public SpringCacheManager SpringCacheManager() {
SpringCacheManager springCacheManager = new SpringCacheManager();
springCacheManager.setGridName("WebGrid");
return springCacheManager;
}


During debug, I found out that following piece of code does not work - 

this.ignite = Ignition.ignite(this.igniteInstanceName);


So somehow, It cant join the existing instance on spring boot 2.0

Please note that ignite instance starts correctly but when it tries to join
it, it cant find the grid instance.

Did anyone experienced such issue ? 




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

Message Queue Size

[ignite_user2016]

hello igniters,

When I start up the console, I get this warning -

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.

I am wondering how can I set the message queue limit ? any example would be
helpful here.

Thanks..

Rishi



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

Re: client thread dumps

[ignite_user2016]

Thank you for all your help ...



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

Re: client thread dumps

[ignite_user2016]

Hello Evgenii,

We only used ignite for 2nd level cache, mostly we used get operation on
cache however we monitor with Ignite visor console, not sure if that would
make difference.

Do you know what could be the reason for leak which shows on heap dump ? 

One instance of
"org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager"
loaded by "sun.misc.Launcher$AppClassLoader @ 0x88003d40" occupies
375,647,072 (83.93%) bytes. The memory is accumulated in one instance of
"java.util.LinkedList" loaded by "".

Keywords
java.util.LinkedList
sun.misc.Launcher$AppClassLoader @ 0x88003d40
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager




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

Re: client thread dumps

[ignite_user2016]

I took a heap dump and it all points to following class - 

One instance of
"org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager"
loaded by "sun.misc.Launcher$AppClassLoader @ 0x88003d40" occupies
375,647,072 (83.93%) bytes. The memory is accumulated in one instance of
"java.util.LinkedList" loaded by "".

Keywords
java.util.LinkedList
sun.misc.Launcher$AppClassLoader @ 0x88003d40
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager

see the attached images.
 



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

Re: client thread dumps

[ignite_user2016]

I am also seeing frequent GC in GC monitor, wondering what it can relate to
that is with CPU spike ? 

 



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

client thread dumps

[ignite_user2016]

Hello Igniters,

curious about client thread dumps, I see so many ignite threads on client
side, wondering what are there and how can I reduce the size of threads ? 

we run ignite 2.0 in production on SB instances.

see the attached image for more information.

 

And our JVM setting as follows - 

-Xms2g -Xmx2g -server -XX:+AggressiveOpts -XX:MaxMetaspaceSize=256m
-XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=DIR_PATH -XX:+UseParNewGC
-XX:+UseConcMarkSweepGC -XX:+UseTLAB -XX:NewSize=128m -XX:MaxNewSize=128m

Since we use ignite for bare minimum do I need some tuning here ? 

Thank you for all your help ..




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

memory increases on heap

[ignite_user2016]

Hello Igniters,

We have 2 instances on ignite ( 2.0) in production, we mostly used ignite
for spring cache.

Seeing so many Ignite threads on client heap dumps, wondering what are these
and can we reduce the thread size on client side ? with that can we reduce
the memory foot print ? 

please see the attached image..

 







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

Re: Ignite 2.0 out of memory

[ignite_user2016]

Thanks for the quick response.

how many nodes you have on the one machine? we have single ignite node on
the machine.

How many visor clients on it machine? we mostly monitor ignite using
ignitevisor, and it might have happened the visor client did not shut down
correctly.

I think, it could be an issue with Nagios monitoring so will see if run into
same issue again however will try to get the logs from ops team.

Thanks ..



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

Ignite 2.0 out of memory

[ignite_user2016]

Hello igniters,

I see the following warning in the log - 

[17:23:29,070][WARN ][main][TcpCommunicationSpi] 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.

Is this warning relevant to following error ? 

And then our server went down with following error - 

java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start0(Native Method) ~[?:1.8.0_121]
at java.lang.Thread.start(Thread.java:714) ~[?:1.8.0_121]
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(GridDiscoveryManager.java:726)
~[ignite-core-2.0.0.jar:2.0.0]
at
org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1745)
~[ignite-core-2.0.0.jar:2.0.0]
at
org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:968)
[ignite-core-2.0.0.jar:2.0.0]
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1895)
[ignite-core-2.0.0.jar:2.0.0]
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1647)
[ignite-core-2.0.0.jar:2.0.0]
at
org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1075)
[ignite-core-2.0.0.jar:2.0.0]
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:595)
[ignite-core-2.0.0.jar:2.0.0]
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:519)
[ignite-core-2.0.0.jar:2.0.0]
at org.apache.ignite.Ignition.start(Ignition.java:322)
[ignite-core-2.0.0.jar:2.0.0]
at
org.apache.ignite.visor.commands.open.VisorOpenCommand.open(VisorOpenCommand.scala:251)
[ignite-visor-console-2.0.0.jar:2.0.0]
at
org.apache.ignite.visor.commands.open.VisorOpenCommand.open(VisorOpenCommand.scala:219)
[ignite-visor-console-2.0.0.jar:2.0.0]
at
org.apache.ignite.visor.commands.open.VisorOpenCommand$$anonfun$2.apply(VisorOpenCommand.scala:306)
[ignite-visor-console-2.0.0.jar:2.0.0]
at
org.apache.ignite.visor.commands.open.VisorOpenCommand$$anonfun$2.apply(VisorOpenCommand.scala:306)
[ignite-visor-console-2.0.0.jar:2.0.0]
at
org.apache.ignite.visor.commands.VisorConsole.mainLoop(VisorConsole.scala:217)
[ignite-visor-console-2.0.0.jar:2.0.0]
at
org.apache.ignite.visor.commands.VisorConsole$.delayedEndpoint$org$apache$ignite$visor$commands$VisorConsole$1(VisorConsole.scala:329)
[ignite-visor-console-2.0.0.jar:2.0.0]
at
org.apache.ignite.visor.commands.VisorConsole$delayedInit$body.apply(VisorConsole.scala:318)
[ignite-visor-console-2.0.0.jar:2.0.0]
at scala.Function0$class.apply$mcV$sp(Function0.scala:34)
[scala-library-2.11.7.jar:?]
at
scala.runtime.AbstractFunction0.apply$mcV$sp(AbstractFunction0.scala:12)
[scala-library-2.11.7.jar:?]
at scala.App$$anonfun$main$1.apply(App.scala:76)
[scala-library-2.11.7.jar:?]
at scala.App$$anonfun$main$1.apply(App.scala:76)
[scala-library-2.11.7.jar:?]
at scala.collection.immutable.List.foreach(List.scala:381)
[scala-library-2.11.7.jar:?]
at
scala.collection.generic.TraversableForwarder$class.foreach(TraversableForwarder.scala:35)
[scala-library-2.11.7.jar:?]
at scala.App$class.main(App.scala:76) [scala-library-2.11.7.jar:?]
at
org.apache.ignite.visor.commands.VisorConsole$.main(VisorConsole.scala:318)
[ignite-visor-console-2.0.0.jar:2.0.0]
at
org.apache.ignite.visor.commands.VisorConsole.main(VisorConsole.scala)
[ignite-visor-console-2.0.0.jar:2.0.0]
[22:25:28,566][ERROR][main][G] Failed to initialize striped pool.
java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start0(Native Method) ~[?:1.8.0_121]
at java.lang.Thread.start(Thread.java:714) ~[?:1.8.0_121]
at
org.apache.ignite.internal.util.StripedExecutor$Stripe.start(StripedExecutor.java:444)
~[ignite-core-2.0.0.jar:2.0.0]
at
org.apache.ignite.internal.util.StripedExecutor.(StripedExecutor.java:84)
[ignite-core-2.0.0.jar:2.0.0]
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1729)
[ignite-core-2.0.0.jar:2.0.0]
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1647)
[ignite-core-2.0.0.jar:2.0.0]
at
org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1075)
[ignite-core-2.0.0.jar:2.0.0]
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:595)
[ignite-core-2.0.0.jar:2.0.0]
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:519)
[ignite-core-2.0.0.jar:2.0.0]
at org.apache.ignite.Ignition.start(Ignition.java:322)
[ignite-core-2.0.0.jar:2.0.0]
at
org.apache.ignite.visor.commands.open.VisorOpenCommand.open(VisorOpenCommand.scala:251)
[ignite-visor-console-2.0.0.jar:2.0.0]
at

Re: Use SLF4J in Ignite

[ignite_user2016]

It looks like ignite version of slf4j is not in the classpath.

Did you copy the ignite slf4j jars into server lib directory ?

On Mon, Aug 14, 2017 at 1:55 PM, waterg [via Apache Ignite Users] <
ml+s70518n1617...@n6.nabble.com> wrote:

> Hello there,
>
> I'm having following error when starting Ignite server node
>
> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
> SLF4J: Defaulting to no-operation (NOP) logger implementation
> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further
> detail
> s.
>
> In maven pom file, I added
> 
> org.apache.ignite
> ignite-slf4j
> ${ignite.version}
> 
> In XML config, I added:
> 
> 
> 
> I've also moved 'optional/ignite-slf4j' folder to
> 'libs' folder before running 'ignite.{sh|bat}' script, according to README
> here https://github.com/apache/ignite/tree/master/modules/slf4j
>
> What should I do differently?
>
> Thank you.
> Jessie
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://apache-ignite-users.70518.x6.nabble.com/Use-SLF4J-
> in-Ignite-tp16179.html
> To start a new topic under Apache Ignite Users, email
> ml+s70518n1...@n6.nabble.com
> To unsubscribe from Apache Ignite Users, click here
> 
> .
> NAML
> 
>



-- 
Rishi Yagnik




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

Re: heap dump on ignite servers

[ignite_user2016]

any help here ? 



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/heap-dump-on-ignite-servers-tp15679p16089.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: heap dump on ignite servers

[ignite_user2016]

Thank you Andrew.. we are upgrading Ignite to 2.0 so hopefully we wont have
such issues.



On Wed, Jul 26, 2017 at 10:35 AM, Andrew Mashenkov [via Apache Ignite
Users] <ml+s70518n15695...@n6.nabble.com> wrote:

> Hi,
>
> Looks like we have a more optimal code in latest versions. See IGNITE-4154
> [1]
> Try to update to >= 1.8 version.
>
> As a workaround you can try to reduce discovery history size with JVM
> option IGNITE_AFFINITY_HISTORY_SIZE, which is 500 by default.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-4154
>
> On Wed, Jul 26, 2017 at 7:30 AM, ignite_user2016 <[hidden email]
> <http:///user/SendEmail.jtp?type=node=15695=0>> wrote:
>
>> Hello Igniters / Val,
>>
>> Since last few weeks, we are seeing out of memory issues on ignite
>> servers,
>> today I was able to capture the heapdumps and that is pointing to
>> following
>> classes -
>>
>> Our version of Ignite is 1.7.0.
>>
>> 15 instances of
>> "org.apache.ignite.internal.processors.affinity.GridAffinity
>> AssignmentCache",
>> loaded by "sun.misc.Launcher$AppClassLoader @ 0xc0029998" occupy
>> 453,929,512
>> (76.41%) bytes.
>>
>> Biggest instances:
>> •org.apache.ignite.internal.processors.affinity.GridAffinity
>> AssignmentCache
>> @ 0xc426b868 - 34,931,744 (5.88%) bytes.
>> •org.apache.ignite.internal.processors.affinity.GridAffinity
>> AssignmentCache
>> @ 0xc2f94e28 - 34,745,904 (5.85%) bytes.
>> •org.apache.ignite.internal.processors.affinity.GridAffinity
>> AssignmentCache
>> @ 0xc4a0ffc8 - 34,745,896 (5.85%) bytes.
>> •org.apache.ignite.internal.processors.affinity.GridAffinity
>> AssignmentCache
>> @ 0xc2e41e10 - 34,642,904 (5.83%) bytes.
>> •org.apache.ignite.internal.processors.affinity.GridAffinity
>> AssignmentCache
>> @ 0xc100a648 - 34,376,920 (5.79%) bytes.
>> •org.apache.ignite.internal.processors.affinity.GridAffinity
>> AssignmentCache
>> @ 0xc3da2ac0 - 34,376,288 (5.79%) bytes.
>> •org.apache.ignite.internal.processors.affinity.GridAffinity
>> AssignmentCache
>> @ 0xc32991b0 - 34,376,208 (5.79%) bytes.
>> •org.apache.ignite.internal.processors.affinity.GridAffinity
>> AssignmentCache
>> @ 0xc427d798 - 34,376,008 (5.79%) bytes.
>> •org.apache.ignite.internal.processors.affinity.GridAffinity
>> AssignmentCache
>> @ 0xc57cbd28 - 34,270,952 (5.77%) bytes.
>> •org.apache.ignite.internal.processors.affinity.GridAffinity
>> AssignmentCache
>> @ 0xc0a22ae8 - 34,191,040 (5.76%) bytes.
>> •org.apache.ignite.internal.processors.affinity.GridAffinity
>> AssignmentCache
>> @ 0xc0d8ade8 - 34,190,960 (5.76%) bytes.
>> •org.apache.ignite.internal.processors.affinity.GridAffinity
>> AssignmentCache
>> @ 0xc38a3618 - 34,190,920 (5.76%) bytes.
>> •org.apache.ignite.internal.processors.affinity.GridAffinity
>> AssignmentCache
>> @ 0xc50d0ca8 - 33,900,352 (5.71%) bytes.
>>
>>
>> Keywords
>> sun.misc.Launcher$AppClassLoader @ 0xc0029998
>> org.apache.ignite.internal.processors.affinity.GridAffinityA
>> ssignmentCache
>>
>> we are running ignite on 1G memory and dont use ignite for any computing.
>>
>> Our configuration is based on ip cluster that is as follows -
>>
>> 
>>
>>
>>
>>
>> http://www.springframework.org/schema/beans;
>>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>>xmlns:util="http://www.springframework.org/schema/util;
>>xsi:schemaLocation="
>> http://www.springframework.org/schema/beans
>> http://www.springframework.org/schema/beans/spring-beans.xsd
>> http://www.springframework.org/schema/util
>> http://www.springframework.org/schema/util/spring-util.xsd;>
>>
>>
>>
>>
>> > class="org.apache.ignite.configuration.IgniteConfiguration">
>>
>> 
>>
>>
>> 
>>
>> 
>>
>>
>> 
>> 
>> > value="config/log4j2.xml"/>
>> 
>> 
>>
>>
>> 
>> 
>> > static-field="org.apache.ignite.events.EventType.EVT_CLIENT_
>> NODE_RECONNECTED"/>
>> 
>> 
>>
>>
>> 
>> 
>>
>>
>>
>>
>>
>>
>>
>>
>> 
>> 
>>
>>
>>
>>

heap dump on ignite servers

[ignite_user2016]

Hello Igniters / Val,

Since last few weeks, we are seeing out of memory issues on ignite servers,
today I was able to capture the heapdumps and that is pointing to following
classes - 

Our version of Ignite is 1.7.0.

15 instances of
"org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache",
loaded by "sun.misc.Launcher$AppClassLoader @ 0xc0029998" occupy 453,929,512
(76.41%) bytes. 

Biggest instances:
•org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache
@ 0xc426b868 - 34,931,744 (5.88%) bytes. 
•org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache
@ 0xc2f94e28 - 34,745,904 (5.85%) bytes. 
•org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache
@ 0xc4a0ffc8 - 34,745,896 (5.85%) bytes. 
•org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache
@ 0xc2e41e10 - 34,642,904 (5.83%) bytes. 
•org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache
@ 0xc100a648 - 34,376,920 (5.79%) bytes. 
•org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache
@ 0xc3da2ac0 - 34,376,288 (5.79%) bytes. 
•org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache
@ 0xc32991b0 - 34,376,208 (5.79%) bytes. 
•org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache
@ 0xc427d798 - 34,376,008 (5.79%) bytes. 
•org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache
@ 0xc57cbd28 - 34,270,952 (5.77%) bytes. 
•org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache
@ 0xc0a22ae8 - 34,191,040 (5.76%) bytes. 
•org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache
@ 0xc0d8ade8 - 34,190,960 (5.76%) bytes. 
•org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache
@ 0xc38a3618 - 34,190,920 (5.76%) bytes. 
•org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache
@ 0xc50d0ca8 - 33,900,352 (5.71%) bytes. 


Keywords
sun.misc.Launcher$AppClassLoader @ 0xc0029998
org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache

we are running ignite on 1G memory and dont use ignite for any computing.

Our configuration is based on ip cluster that is as follows - 






http://www.springframework.org/schema/beans;
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
   xmlns:util="http://www.springframework.org/schema/util;
   xsi:schemaLocation="
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd
http://www.springframework.org/schema/util
http://www.springframework.org/schema/util/spring-util.xsd;>













 



























  











HOST_IP1:47500..47509
HOST_IP2:47500..47509











 
what am I missing here ? 

thanks for all your help..




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/heap-dump-on-ignite-servers-tp15679.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: benchmark

[ignite_user2016]

Few more words from my end -

Open source ignite gives you basic require features that is something not
there in open source version of ignite.
Switching open source version to paid version and vice versa would be easy
with Ignite.

On Fri, Jul 21, 2017 at 12:29 PM, Denis Magda-2 [via Apache Ignite Users] <
ml+s70518n1525...@n6.nabble.com> wrote:

> Hi Lugman!
>
> Please take a look at this post - https://dmagda.blogspot.ru/
> 2017/04/benchmarking-apache-ignite-still-keeps.html. You can find links
> to yardstick repositories in the post. Instructions on how to reproduce the
> results can be found in the repos. You may need to adopt the benchmarks or
> create your own to reflect your particular use case.
>
> —
> Denis
>
> On Jul 21, 2017, at 8:47 AM, luqmanahmad <[hidden email]
> > wrote:
>
> Hi,
>
> I am a user of ignite since 1.3 and know its much better than hazlecast.
> Now
> just need to convince it to the management, and they asked for the
> benchmarks. They are really keen on hazlecast  but I have convinced them on
> most of the features. Is there a good place where I can find some
> information about running the benchmarks for both.
>
> Thanks,
> Luqman
>
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/benchmark-tp15246.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
>
>
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://apache-ignite-users.70518.x6.nabble.com/benchmark-
> tp15246p15250.html
> To start a new topic under Apache Ignite Users, email
> ml+s70518n1...@n6.nabble.com
> To unsubscribe from Apache Ignite Users, click here
> 
> .
> NAML
> 
>



-- 
Rishi Yagnik




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

Re: SpringBoot integration with Ignite

[ignite_user2016]

let me know if you need help here, I can help you out further here for sure
..

On Wed, Jul 12, 2017 at 5:51 AM, afedotov [via Apache Ignite Users] <
ml+s70518n14717...@n6.nabble.com> wrote:

> Hi,
>
> Please check
> http://apache-ignite-users.70518.x6.nabble.com/SpringBoot-Integration-
> td11659.html
> and
> http://apache-ignite-users.70518.x6.nabble.com/Using-
> AbstractAnnotationConfigDispatcherServletInitializer-td14592.html#a14600
>
>
> Kind regards,
> Alex.
>
> On Wed, Jul 12, 2017 at 12:53 PM, vishal jain [via Apache Ignite Users] 
> <[hidden
> email] > wrote:
>
>> Hi,
>>
>>
>> How can we integrate apache ignite with SpringBoot application?
>> I want to use ignite as the distribute cache for our springBoot
>> application, any pointers/suggestions will help.
>>
>> Thanks,
>> VJ
>>
>>
>>
>> --
>> If you reply to this email, your message will be added to the discussion
>> below:
>> http://apache-ignite-users.70518.x6.nabble.com/SpringBoot-
>> integration-with-Ignite-tp14715.html
>> To start a new topic under Apache Ignite Users, email [hidden email]
>> 
>> To unsubscribe from Apache Ignite Users, click here.
>> NAML
>> 
>>
>
>
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://apache-ignite-users.70518.x6.nabble.com/
> SpringBoot-integration-with-Ignite-tp14715p14717.html
> To start a new topic under Apache Ignite Users, email
> ml+s70518n1...@n6.nabble.com
> To unsubscribe from Apache Ignite Users, click here
> 
> .
> NAML
> 
>



-- 
Rishi Yagnik




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

Re: frequet disconnection in ignite cluster

[ignite_user2016]

Hello Val,

I have asked for such changes would keep you informed.

PS - our world is very slow so any changes would take 1-2 week of time.

Thanks..

On Fri, Jul 7, 2017 at 2:06 PM, vkulichenko [via Apache Ignite Users] <
ml+s70518n1450...@n6.nabble.com> wrote:

> Rishi,
>
> Does the issue go away if you stop triggering monitoring every 5 minutes.
> Such frequency is very small, it should not cause any issues of course.
>
> -Val
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://apache-ignite-users.70518.x6.nabble.com/frequet-
> disconnection-in-ignite-cluster-tp14411p14505.html
> To start a new topic under Apache Ignite Users, email
> ml+s70518n1...@n6.nabble.com
> To unsubscribe from Apache Ignite Users, click here
> 
> .
> NAML
> 
>



-- 
Rishi Yagnik




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

Re: Ignite 1.6.0 suspected memory leak from DynamicCacheDescriptor

[ignite_user2016]

Hello Val..

Thanks, will try out and let you know ...

On Fri, Jul 7, 2017 at 12:25 PM, vkulichenko [via Apache Ignite Users] <
ml+s70518n1449...@n6.nabble.com> wrote:

> Hi Rishi,
>
> ignite.cluster().nodes() will give the list of nodes and full information
> about topology. Will this work for you?
>
> -Val
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://apache-ignite-users.70518.x6.nabble.com/Ignite-1-
> 6-0-suspected-memory-leak-from-DynamicCacheDescriptor-tp9443p14492.html
> To start a new topic under Apache Ignite Users, email
> ml+s70518n1...@n6.nabble.com
> To unsubscribe from Apache Ignite Users, click here
> 
> .
> NAML
> 
>



-- 
Rishi Yagnik




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Ignite-1-6-0-suspected-memory-leak-from-DynamicCacheDescriptor-tp9443p14495.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite 1.6.0 suspected memory leak from DynamicCacheDescriptor

[ignite_user2016]

Hello Val,

Do you have any example on it ? would like to see how can we leverage that
piece of code for monitoring ?

Thanks for all your help..


On Thu, Jul 6, 2017 at 5:46 PM, vkulichenko [via Apache Ignite Users] <
ml+s70518n14430...@n6.nabble.com> wrote:

> Tom,
>
> It sounds like these jobs are triggered pretty frequently. So why not
> create a small application that will create an embedded client once and
> also have an internal timer or cron based scheduler to execute jobs
> periodically. You can do the topology check within this application as
> well, instead of using Visor.
>
> -Val
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://apache-ignite-users.70518.x6.nabble.com/Ignite-1-
> 6-0-suspected-memory-leak-from-DynamicCacheDescriptor-tp9443p14430.html
> To start a new topic under Apache Ignite Users, email
> ml+s70518n1...@n6.nabble.com
> To unsubscribe from Apache Ignite Users, click here
> 
> .
> NAML
> 
>



-- 
Rishi Yagnik




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Ignite-1-6-0-suspected-memory-leak-from-DynamicCacheDescriptor-tp9443p14491.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: frequet disconnection in ignite cluster

[ignite_user2016]

Hello ..

Thanks for sharing the thread..

we have 4 core, 8 GB RAM mostly Ignite is used for 2nd level cache.

We have set our JVM to 1G RAM.

Then, wondering how would we monitor ignite without impacting the system ?

Thanks ...

On Thu, Jul 6, 2017 at 9:54 PM, tysli2016 [via Apache Ignite Users] <
ml+s70518n14442...@n6.nabble.com> wrote:

> Hi Rishi,
>
> seems it's not a good idea to connect ignite repeatedly, I observed a
> similar memory issue.
> would you mind to share your server configurations (cores, memory)?
>
> http://apache-ignite-users.70518.x6.nabble.com/Ignite-1-
> 6-0-suspected-memory-leak-from-DynamicCacheDescriptor-td9443i20.html
>
> http://apache-ignite-users.70518.x6.nabble.com/OOME-on-2-
> node-cluster-with-visor-running-repeatedly-Ignite-1-9-tt12409.html
>
> Tom
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://apache-ignite-users.70518.x6.nabble.com/frequet-
> disconnection-in-ignite-cluster-tp14411p14442.html
> To start a new topic under Apache Ignite Users, email
> ml+s70518n1...@n6.nabble.com
> To unsubscribe from Apache Ignite Users, click here
> 
> .
> NAML
> 
>



-- 
Rishi Yagnik




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

Re: frequet disconnection in ignite cluster

[ignite_user2016]

Thank you.. Val for all your help.

I will investigate further..

We are monitoring ignite every 5 mins with shell script could that cause memory 
to go high ?

Take Care,
Rishi

> On Jul 6, 2017, at 4:50 PM, vkulichenko [via Apache Ignite Users] 
>  wrote:
> 
> Rishi, 
> 
> This is usually caused by either network or memory issues. Check that you 
> don't have any network glitches and that there are no GC pauses, memory 
> leaks, etc. on the nodes. 
> 
> -Val 
> 
> If you reply to this email, your message will be added to the discussion 
> below:
> http://apache-ignite-users.70518.x6.nabble.com/frequet-disconnection-in-ignite-cluster-tp14411p14420.html
> To start a new topic under Apache Ignite Users, email 
> ml+s70518n1...@n6.nabble.com 
> To unsubscribe from Apache Ignite Users, click here.
> NAML




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

frequet disconnection in ignite cluster

[ignite_user2016]

hello Igniters,

we are seeing frequent disconnection between ignite instances, we have IP
based clusters which has following configuration - 

Ignite version - 1.7.0

 









HOST_IP1:47500..47509
HOST_IP2:47500..47509







See the error log - 

[09:53:46,139][WARN ][tcp-disco-msg-worker-#2%WebGrid%][TcpDiscoverySpi]
Local node has detected failed nodes and started cluster-wide procedure. To
speed up failure detection please see 'Failure Detection' section under
javadoc for 'TcpDiscoverySpi'

[09:54:56,060][WARN
][exchange-worker-#54%WebGrid%][GridCachePartitionExchangeManager] Failed to
wait for partition map exchange [topVer=AffinityTopologyVersion
[topVer=22132, minorTopVer=0], node=d3719fe1-84cf-4fe5-91dd-2d10abb1b3d2].
Dumping pending objects that might be the cause:
[09:54:56,060][WARN
][exchange-worker-#54%WebGrid%][GridCachePartitionExchangeManager] Ready
affinity version: AffinityTopologyVersion [topVer=22131, minorTopVer=0]
[09:54:56,062][WARN
][exchange-worker-#54%WebGrid%][GridCachePartitionExchangeManager] Last
exchange future: GridDhtPartitionsExchangeFuture [dummy=false,
forcePreload=false, reassign=false, discoEvt=DiscoveryEvent
[evtNode=TcpDiscoveryNode [id=d2ffb86c-5305-4cb3-96a0-874be73d610a,
addrs=[0:0:0:0:0:0:0:1%lo, 127.0.0.1, host_ip2],
sockAddrs=[host2/host_ip2:47501, 0:0:0:0:0:0:0:1%lo:47501,
/127.0.0.1:47501], discPort=47501, order=22131, intOrder=11068,
lastExchangeTime=1499352867440, loc=false, ver=1.7.0#20160801-sha1:383273e3,
isClient=false], topVer=22132, nodeId8=d3719fe1, msg=Node left:
TcpDiscoveryNode [id=d2ffb86c-5305-4cb3-96a0-874be73d610a,
addrs=[0:0:0:0:0:0:0:1%lo, 127.0.0.1, host_ip2],
sockAddrs=[host2/host_ip2:47501, 0:0:0:0:0:0:0:1%lo:47501,
/127.0.0.1:47501], discPort=47501, order=22131, intOrder=11068,
lastExchangeTime=1499352867440, loc=false, ver=1.7.0#20160801-sha1:383273e3,
isClient=false], type=NODE_LEFT, tstamp=1499352886042], crd=TcpDiscoveryNode
[id=64ce302c-9743-47bc-bf27-641015a37b81, addrs=[127.0.0.1, host_ip1],
sockAddrs=[/127.0.0.1:47500, host1/host_ip1:47500], discPort=47500, order=1,
intOrder=1, lastExchangeTime=1498849915139, loc=false,
ver=1.7.0#20160801-sha1:383273e3, isClient=false],
exchId=GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion
[topVer=22132, minorTopVer=0], nodeId=d2ffb86c, evt=NODE_LEFT], added=true,
initFut=GridFutureAdapter [resFlag=2, res=true, startTime=1499352886042,
endTime=1499352886052, ignoreInterrupts=false, state=DONE],init=true,
topSnapshot=null, lastVer=null, partReleaseFut=GridCompoundFuture [rdc=null,
initFlag=1, lsnrCalls=3, done=true, cancelled=false, err=null, futs=[true,
true, true]], affChangeMsg=null, skipPreload=false,
clientOnlyExchange=false, initTs=1499352886042, centralizedAff=true,
evtLatch=0, remaining=[64ce302c-9743-47bc-bf27-641015a37b81],
srvNodes=[TcpDiscoveryNode [id=64ce302c-9743-47b
c-bf27-641015a37b81, addrs=[127.0.0.1, host_ip1],
sockAddrs=[/127.0.0.1:47500, host1/host_ip1:47500], discPort=47500, order=1,
intOrder=1, lastExchangeTime=1498849915139, loc=false,
ver=1.7.0#20160801-sha1:383273e3, isClient=false], TcpDiscoveryNode
[id=d3719fe1-84cf-4fe5-91dd-2d10abb1b3d2, addrs=[127.0.0.1, host_ip2],
sockAddrs=[/127.0.0.1:47500, host2/host_ip2:47500], discPort=47500, order=4,
intOrder=3, lastExchangeTime=1499352895809, loc=true,
ver=1.7.0#20160801-sha1:383273e3, isClient=false]], super=GridFutureAdapter
[resFlag=0, res=nul
l, startTime=1499352886042, endTime=0, ignoreInterrupts=false, state=INIT]]

[10:08:37,232][WARN
][exchange-worker-#54%WebGrid%][GridCachePartitionExchangeManager] Failed to
wait for partition map exchange [topVer=AffinityTopologyVersion
[topVer=22134, minorTopVer=0], node=
d3719fe1-84cf-4fe5-91dd-2d10abb1b3d2]. Dumping pending objects that might be
the cause:
[10:08:47,287][WARN
][exchange-worker-#54%WebGrid%][GridCachePartitionExchangeManager] Failed to
wait for partition map exchange [topVer=AffinityTopologyVersion
[topVer=22134, minorTopVer=0], node=
d3719fe1-84cf-4fe5-91dd-2d10abb1b3d2]. Dumping pending objects that might be
the cause:

class org.apache.ignite.IgniteException: Failed to wait for affinity ready
future for topology version: AffinityTopologyVersion [topVer=22134,
minorTopVer=0]
at
org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.awaitTopologyVersion(GridAffinityAssignmentCache.java:526)
at
org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.cachedAffinity(GridAffinityAssignmentCache.java:434)
at

Re: Start and Stop Ignite as Systemd Process

[ignite_user2016]

we killed it with the script.

On Mon, May 22, 2017 at 11:39 AM, amithpatrick1 [via Apache Ignite Users] <
ml+s70518n13072...@n6.nabble.com> wrote:

> Hello Rishi,
>
> Can you  tell what are the steps you are taking into consideration while
> stopping the node ? Are just killing the process or are there other
> mechanisms to stop the node ?
> If you can share the code snippet/psuedo code for the same it would be
> really helpful.
>
> Thanks.
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://apache-ignite-users.70518.x6.nabble.com/Start-and-
> Stop-Ignite-as-Systemd-Process-tp13047p13072.html
> To start a new topic under Apache Ignite Users, email
> ml+s70518n1...@n6.nabble.com
> To unsubscribe from Apache Ignite Users, click here
> 
> .
> NAML
> 
>



-- 
Rishi Yagnik




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Start-and-Stop-Ignite-as-Systemd-Process-tp13047p13073.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Start and Stop Ignite as Systemd Process

[ignite_user2016]

Hello,

We also start ignite with systemd, we have a written a shell script to manage 
ignite start and stop.

Hope it helps ..

Take Care,
Rishi

> On May 20, 2017, at 12:00 PM, amithpatrick1 [via Apache Ignite Users] 
>  wrote:
> 
> Hello, 
> 
> Has anyone tired managing the Ignite server nodes as a Systemd process? What 
> are the steps to start and stop ignite nodes as systemd service? Also , what 
> is the graceful way to stop a ignite node ? 
> 
> If you reply to this email, your message will be added to the discussion 
> below:
> http://apache-ignite-users.70518.x6.nabble.com/Start-and-Stop-Ignite-as-Systemd-Process-tp13047.html
> To start a new topic under Apache Ignite Users, email 
> ml+s70518n1...@n6.nabble.com 
> To unsubscribe from Apache Ignite Users, click here.
> NAML




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Start-and-Stop-Ignite-as-Systemd-Process-tp13047p13048.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: How to monitor and alert for server counts

[ignite_user2016]

we did not made any tweak to memory configuration and our configuration is
a bare bone configuration.

Please note that our need with ignite is not big data.

On Wed, May 10, 2017 at 2:08 AM, tysli2016 [via Apache Ignite Users] <
ml+s70518n12582...@n6.nabble.com> wrote:

> we run the visor in 10 every mins, the Ignite servers would OOME in a
> couple weeks.
> Ignite server allocated 1g memory.
>
> would you mind to share you server's config.xml? any JVM parameters
> changes?
>
> thanks
> Tom
>
> ignite_user2016 wrote
> yes you are correct, we run visor in the batch mode.
>
> we have 2 host hosting 2 client and 2 server for ignite, our conf is bare
> minimal 4 cores 8 GB RAM.
>
> Now with OOME, how often you run the visor command ? we run it every 5
> mins.should you try that ?
>
> On Mon, May 8, 2017 at 9:01 PM, tysli2016 [via Apache Ignite Users] <
> [hidden email] <http:///user/SendEmail.jtp?type=node=12582=0>>
> wrote:
>
> > thanks Rishi, can you share more about that?
> > what's the version of Ignite? how many Ignite servers? how many
> > CPU/memory?
> > are you using the Visor in batch mode (https://apacheignite-tools.
> > readme.io/v1.9/docs/batch-mode)?
> > or Visor alert?
> >
> > I have tried Visor batch mode, but it lead to OOME eventually (
> > http://apache-ignite-users.70518.x6.nabble.com/OOME-on-2-
> > node-cluster-with-visor-running-repeatedly-Ignite-1-9-td12409.html).
> >
> > --
> > If you reply to this email, your message will be added to the discussion
> > below:
> > http://apache-ignite-users.70518.x6.nabble.com/How-to-
> > monitor-and-alert-for-server-counts-tp12533p12557.html
> > To start a new topic under Apache Ignite Users, email
> > [hidden email] <http:///user/SendEmail.jtp?type=node=12582=1>
> > To unsubscribe from Apache Ignite Users, click here
> > <http://apache-ignite-users.70518.x6.nabble.com/template/
> NamlServlet.jtp?macro=unsubscribe_by_code=1=
> cmlzaGl5YWduaWtAZ21haWwuY29tfDF8MTMwNTI4OTg1Mw==>
> > .
> > NAML
> > <http://apache-ignite-users.70518.x6.nabble.com/template/
> NamlServlet.jtp?macro=macro_viewer=instant_html%
> 21nabble%3Aemail.naml=nabble.naml.namespaces.
> BasicNamespace-nabble.view.web.template.NabbleNamespace-
> nabble.view.web.template.NodeNamespace=
> notify_subscribers%21nabble%3Aemail.naml-instant_emails%
> 21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
> <http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=macro_viewer=instant_html%21nabble%3Aemail.naml=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml%3E>
> >
>
>
>
> --
> Rishi Yagnik
>
>
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://apache-ignite-users.70518.x6.nabble.com/How-to-
> monitor-and-alert-for-server-counts-tp12533p12582.html
> To start a new topic under Apache Ignite Users, email
> ml+s70518n1...@n6.nabble.com
> To unsubscribe from Apache Ignite Users, click here
> <http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code=1=cmlzaGl5YWduaWtAZ21haWwuY29tfDF8MTMwNTI4OTg1Mw==>
> .
> NAML
> <http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=macro_viewer=instant_html%21nabble%3Aemail.naml=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>



-- 
Rishi Yagnik




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/How-to-monitor-and-alert-for-server-counts-tp12533p12610.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: How to monitor and alert for server counts

[ignite_user2016]

yes you are correct, we run visor in the batch mode.

we have 2 host hosting 2 client and 2 server for ignite, our conf is bare
minimal 4 cores 8 GB RAM.

Now with OOME, how often you run the visor command ? we run it every 5
mins.should you try that ?

On Mon, May 8, 2017 at 9:01 PM, tysli2016 [via Apache Ignite Users] <
ml+s70518n12557...@n6.nabble.com> wrote:

> thanks Rishi, can you share more about that?
> what's the version of Ignite? how many Ignite servers? how many
> CPU/memory?
> are you using the Visor in batch mode (https://apacheignite-tools.
> readme.io/v1.9/docs/batch-mode)?
> or Visor alert?
>
> I have tried Visor batch mode, but it lead to OOME eventually (
> http://apache-ignite-users.70518.x6.nabble.com/OOME-on-2-
> node-cluster-with-visor-running-repeatedly-Ignite-1-9-td12409.html).
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://apache-ignite-users.70518.x6.nabble.com/How-to-
> monitor-and-alert-for-server-counts-tp12533p12557.html
> To start a new topic under Apache Ignite Users, email
> ml+s70518n1...@n6.nabble.com
> To unsubscribe from Apache Ignite Users, click here
> 
> .
> NAML
> 
>



-- 
Rishi Yagnik




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/How-to-monitor-and-alert-for-server-counts-tp12533p12561.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: How to monitor and alert for server counts

[ignite_user2016]

I would try to help here -

we monitor our prod environment with ignite visor command so worth looking
into it.

Let me know if you need more details, I can surely help here.

On Mon, May 8, 2017 at 6:26 AM, Denis Magda [via Apache Ignite Users] <
ml+s70518n12540...@n6.nabble.com> wrote:

> Vidos UI telemetry capabilities can be considered: http://docs.
> gridgain.com/docs/visor-gui
>
> Denis
>
> On Monday, May 8, 2017, Andrey Mashenkov <[hidden email]
> > wrote:
>
>> Looks like you need a 3rd party monitoring software.
>> E.g. Nagios\Icinga or Zabbix.
>>
>> On Mon, May 8, 2017 at 1:19 PM, tysli2016 <> href="javascript:_e(%7B%7D,cvml,tom.ys...@cityline.com.hk);"
>> target="_blank">Tom.YS.Li@...> wrote:
>>
>>> we have a couple of Ignite servers serve as key-value store and want to
>>> get
>>> email notification when any server went down.
>>>
>>> anyone are having the same need? what is your solution?
>>>
>>>
>>>
>>> --
>>> View this message in context: http://apache-ignite-users.705
>>> 18.x6.nabble.com/How-to-monitor-and-alert-for-server-counts-tp12533.html
>>> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>>>
>>
>>
>>
>> --
>> Best regards,
>> Andrey V. Mashenkov
>>
>
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://apache-ignite-users.70518.x6.nabble.com/How-to-
> monitor-and-alert-for-server-counts-tp12533p12540.html
> To start a new topic under Apache Ignite Users, email
> ml+s70518n1...@n6.nabble.com
> To unsubscribe from Apache Ignite Users, click here
> 
> .
> NAML
> 
>



-- 
Rishi Yagnik




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/How-to-monitor-and-alert-for-server-counts-tp12533p12544.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite 2.0 visor issue

[ignite_user2016]

Found the issue dont worry about it..



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

Ignite 2.0 visor issue

[ignite_user2016]

Hello Igniters,

I downloaded Ignite 2.0 and run the client and server all works well however
when I try to get stats from visor, I cant get anything.

visor> top
Empty topology.

visor> cache -scan
(wrn) : No caches found.
(wrn) : Type 'help cache' to see how to use this command.

Not sure what has changed with visor, any help would be much appreciated
here.

My environment is JDK8, Windows 7 with Ignite 2.0

Thanks,
Rishi



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

Re: Ignite Web Sessions Caching Failover question

[ignite_user2016]

Hello Val,

I did looked at this possibility but this is something needs to be done on
Spring boot side so spring boot should provide us the capability to manage
user session in memory when the distributed cache cant get connected, kind
of a fall back mechanism.

I still believe this is something distributed cache cant do OR should not do
however it can have the failure handlers which would tell spring boot to
manage sessions in memory.

The usecase gets more complicated when a user session does fall back on
memory and now ignite comes up then the framework shall do the session
replication on ignite and vice versa..

Hope it helps..

Thanks,
Rishi





--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Ignite-Web-Sessions-Caching-Failover-question-tp12240p12295.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite errors in log

[ignite_user2016]

Thanks, Andrew.

I enabled the ipv4 stack option and see if that resolves our problem.

I will keep you posted, thank you for all your help.


On Tue, Apr 18, 2017 at 1:41 PM, Andrew Mashenkov [via Apache Ignite Users]
<ml-node+s70518n12044...@n6.nabble.com> wrote:

> Hi Rishi,
>
> Would you please check if both nodes has same either
> java.net.preferIPv4Stack=true or java.net.preferIPv6Stack=true option?
> "remote_host/remote_host:47102" looks weird. Would you also check if all
> dns names are correctly resolved on both nodes?
>
> On Tue, Apr 18, 2017 at 9:29 PM, Rishi Yagnik <[hidden email]
> <http:///user/SendEmail.jtp?type=node=12044=0>> wrote:
>
>> I checked the port and all ports are open between 2 ignite instances.
>>
>> There is something more going on, will provide the log soon.
>>
>> On Tue, Apr 18, 2017 at 12:00 PM, ignite_user2016 <[hidden email]
>> <http:///user/SendEmail.jtp?type=node=12044=1>> wrote:
>>
>>> we use Ignite 1.7, yes application is communicating between hosts and
>>> client application.
>>>
>>> I will provide the logs soon.
>>>
>>> Thanks,
>>>
>>> On Tue, Apr 18, 2017 at 11:09 AM, Evgenii Zhuravlev [via Apache Ignite
>>> Users] <[hidden email]
>>> <http:///user/SendEmail.jtp?type=node=12042=0>> wrote:
>>>
>>>> Which version of ignite do you use?
>>>>
>>>> It looks like nodes discovered each other via 47500+ ports, but they
>>>> can't communicate through 47100+ ports. Did you opened these ports? Are you
>>>> sure that all nodes was used in your application?
>>>>
>>>> Also, it would be helpful if you provided full logs, it's nearly
>>>> impossible to understand what really happens on the nodes without them.
>>>>
>>>> 2017-04-18 18:39 GMT+03:00 ignite_user2016 <[hidden email]
>>>> <http:///user/SendEmail.jtp?type=node=12038=0>>:
>>>>
>>>>> Yes, I see this logs in both the host.
>>>>>
>>>>> The log entries I have provided, here is my config file -
>>>>>
>>>>> http://www.springframework.org/schema/beans;
>>>>>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>>>>>xmlns:util="http://www.springframework.org/schema/util;
>>>>>xsi:schemaLocation="
>>>>> http://www.springframework.org/schema/beans
>>>>> http://www.springframework.org/schema/beans/spring-beans.xsd
>>>>> http://www.springframework.org/schema/util
>>>>> http://www.springframework.org/schema/util/spring-util.xsd;>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> 
>>>>>
>>>>> 
>>>>>
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>>
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> >>>> value="config/log4j.xml"/>
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>>
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>>
>>>>>
>>>>>
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>>
>>>>>
>>>>>
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 

Re: Ignite errors in log

[ignite_user2016]

we use Ignite 1.7, yes application is communicating between hosts and
client application.

I will provide the logs soon.

Thanks,

On Tue, Apr 18, 2017 at 11:09 AM, Evgenii Zhuravlev [via Apache Ignite
Users] <ml-node+s70518n12038...@n6.nabble.com> wrote:

> Which version of ignite do you use?
>
> It looks like nodes discovered each other via 47500+ ports, but they can't
> communicate through 47100+ ports. Did you opened these ports? Are you sure
> that all nodes was used in your application?
>
> Also, it would be helpful if you provided full logs, it's nearly
> impossible to understand what really happens on the nodes without them.
>
> 2017-04-18 18:39 GMT+03:00 ignite_user2016 <[hidden email]
> <http:///user/SendEmail.jtp?type=node=12038=0>>:
>
>> Yes, I see this logs in both the host.
>>
>> The log entries I have provided, here is my config file -
>>
>> http://www.springframework.org/schema/beans;
>>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>>xmlns:util="http://www.springframework.org/schema/util;
>>xsi:schemaLocation="
>> http://www.springframework.org/schema/beans
>> http://www.springframework.org/schema/beans/spring-beans.xsd
>> http://www.springframework.org/schema/util
>> http://www.springframework.org/schema/util/spring-util.xsd;>
>>
>>
>>
>>
>> 
>>
>> 
>>
>> 
>> 
>> 
>> 
>>
>> 
>> 
>> 
>> 
>> > value="config/log4j.xml"/>
>> 
>> 
>> 
>> 
>>
>> 
>> 
>> 
>> 
>> 
>> 
>>
>>
>>
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>
>>
>>
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> HOST_IP1:47500..47509
>> HOST_IP2:47500..47509
>> 
>> 
>> 
>> 
>> 
>> 
>>
>> 
>> 
>>
>> On Tue, Apr 18, 2017 at 5:46 AM, Evgenii Zhuravlev [via Apache Ignite
>> Users] <[hidden email]
>> <http:///user/SendEmail.jtp?type=node=12037=0>> wrote:
>>
>>> Hi,
>>>
>>> Could you check that destination node accessible from current node via
>>> one of this addresses(remote_host/remote_host:47102,
>>> /0:0:0:0:0:0:0:1%lo:47102, /127.0.0.1:47102?)
>>>
>>> Do you have problems only with one node, or you have same messages about
>>> another nodes and on another nodes?
>>>
>>> Please provide logs from another nodes and your config file.
>>>
>>> 2017-04-17 23:00 GMT+03:00 ignite_user2016 <[hidden email]
>>> <http:///user/SendEmail.jtp?type=node=12025=0>>:
>>>
>>>> I see the frequent disconnect errors in the logs -
>>>>
>>>> [10:34:03,028][WARN ][tcp-comm-worker-#1%WebGrid%][TcpCommunicationSpi]
>>>> Failed to connect to a remote node (make sure that destination node is
>>>> alive
>>>> and operating system firewall is disabled on local and remote hosts)
>>>> [addrs=[remote_host/remote_host:47102, /0:0:0:0:0:0:0:1%lo:47102,
>>>> /127.0.0.1:47102]]
>>>> [11:58:06,634][WARN ][grid-nio-worker-2-#42%WebGri
>>>> d%][TcpCommunicationSpi]
>>>> Communication SPI Session write timed out (consider increasing
>>>> 'socketWriteTimeout' configuration property)
>>>> [remoteAddr=/remote_host_ip:38104, writeTimeout=2000]
>>>> [12:04:04,124][WARN ][tcp-comm-worker-#1%WebGrid%][TcpCommunicationSpi]
>>>> Connect timed out (consider increasing 'failureDetectionTimeout'
>>>> configuration property) [addr=/0:0:0:0:0:0:0:1%lo:47102,
>>

Re: Ignite errors in log

[ignite_user2016]

Yes, I see this logs in both the host.

The log entries I have provided, here is my config file -

http://www.springframework.org/schema/beans;
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
   xmlns:util="http://www.springframework.org/schema/util;
   xsi:schemaLocation="
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd
http://www.springframework.org/schema/util
http://www.springframework.org/schema/util/spring-util.xsd;>


























































HOST_IP1:47500..47509
HOST_IP2:47500..47509










On Tue, Apr 18, 2017 at 5:46 AM, Evgenii Zhuravlev [via Apache Ignite
Users] <ml-node+s70518n12025...@n6.nabble.com> wrote:

> Hi,
>
> Could you check that destination node accessible from current node via one
> of this addresses(remote_host/remote_host:47102,
> /0:0:0:0:0:0:0:1%lo:47102, /127.0.0.1:47102?)
>
> Do you have problems only with one node, or you have same messages about
> another nodes and on another nodes?
>
> Please provide logs from another nodes and your config file.
>
> 2017-04-17 23:00 GMT+03:00 ignite_user2016 <[hidden email]
> <http:///user/SendEmail.jtp?type=node=12025=0>>:
>
>> I see the frequent disconnect errors in the logs -
>>
>> [10:34:03,028][WARN ][tcp-comm-worker-#1%WebGrid%][TcpCommunicationSpi]
>> Failed to connect to a remote node (make sure that destination node is
>> alive
>> and operating system firewall is disabled on local and remote hosts)
>> [addrs=[remote_host/remote_host:47102, /0:0:0:0:0:0:0:1%lo:47102,
>> /127.0.0.1:47102]]
>> [11:58:06,634][WARN ][grid-nio-worker-2-#42%WebGri
>> d%][TcpCommunicationSpi]
>> Communication SPI Session write timed out (consider increasing
>> 'socketWriteTimeout' configuration property)
>> [remoteAddr=/remote_host_ip:38104, writeTimeout=2000]
>> [12:04:04,124][WARN ][tcp-comm-worker-#1%WebGrid%][TcpCommunicationSpi]
>> Connect timed out (consider increasing 'failureDetectionTimeout'
>> configuration property) [addr=/0:0:0:0:0:0:0:1%lo:47102,
>> failureDetectionTimeout=1]
>> [12:04:04,124][WARN ][tcp-comm-worker-#1%WebGrid%][TcpCommunicationSpi]
>> Connect timed out (consider increasing 'failureDetectionTimeout'
>> configuration property) [addr=/127.0.0.1:47102,
>> failureDetectionTimeout=1]
>> [12:04:04,124][WARN ][tcp-comm-worker-#1%WebGrid%][TcpCommunicationSpi]
>> Failed to connect to a remote node (make sure that destination node is
>> alive
>> and operating system firewall is disabled on local and remote hosts)
>> [addrs=[remote_host/remote_host:47102, /0:0:0:0:0:0:0:1%lo:47102,
>> /127.0.0.1:47102]]
>>
>> With this errors in the logs, I see our system is operational and does not
>> have any failures so are these errors showing false alarms ?
>>
>>
>> I am wondering what would be the idle value for socketWriteTimeOut and
>> failureDetectionCount ? would it have any performance impact on it ?
>>
>>
>> Thanks,
>> Rishi
>>
>>
>>
>> --
>> View this message in context: http://apache-ignite-users.705
>> 18.x6.nabble.com/Ignite-errors-in-log-tp12007.html
>> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>>
>
>
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://apache-ignite-users.70518.x6.nabble.com/Ignite-
> errors-in-log-tp12007p12025.html
> To start a new topic under Apache Ignite Users, email
> ml-node+s70518n1...@n6.nabble.com
> To unsubscribe from Apache Ignite Users, click here
> <http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code=1=cmlzaGl5YWduaWtAZ21haWwuY29tfDF8MTMwNTI4OTg1Mw==>
> .
> NAML
> <http://apache-ignite

Ignite errors in log

[ignite_user2016]

I see the frequent disconnect errors in the logs - 

[10:34:03,028][WARN ][tcp-comm-worker-#1%WebGrid%][TcpCommunicationSpi]
Failed to connect to a remote node (make sure that destination node is alive
and operating system firewall is disabled on local and remote hosts)
[addrs=[remote_host/remote_host:47102, /0:0:0:0:0:0:0:1%lo:47102,
/127.0.0.1:47102]]
[11:58:06,634][WARN ][grid-nio-worker-2-#42%WebGrid%][TcpCommunicationSpi]
Communication SPI Session write timed out (consider increasing
'socketWriteTimeout' configuration property)
[remoteAddr=/remote_host_ip:38104, writeTimeout=2000]
[12:04:04,124][WARN ][tcp-comm-worker-#1%WebGrid%][TcpCommunicationSpi]
Connect timed out (consider increasing 'failureDetectionTimeout'
configuration property) [addr=/0:0:0:0:0:0:0:1%lo:47102,
failureDetectionTimeout=1]
[12:04:04,124][WARN ][tcp-comm-worker-#1%WebGrid%][TcpCommunicationSpi]
Connect timed out (consider increasing 'failureDetectionTimeout'
configuration property) [addr=/127.0.0.1:47102,
failureDetectionTimeout=1]
[12:04:04,124][WARN ][tcp-comm-worker-#1%WebGrid%][TcpCommunicationSpi]
Failed to connect to a remote node (make sure that destination node is alive
and operating system firewall is disabled on local and remote hosts)
[addrs=[remote_host/remote_host:47102, /0:0:0:0:0:0:0:1%lo:47102,
/127.0.0.1:47102]]

With this errors in the logs, I see our system is operational and does not
have any failures so are these errors showing false alarms ? 


I am wondering what would be the idle value for socketWriteTimeOut and
failureDetectionCount ? would it have any performance impact on it ? 


Thanks,
Rishi



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

Re: max size on cache

[ignite_user2016]

Thanks, Val.

On Tue, Mar 28, 2017 at 5:49 PM, vkulichenko [via Apache Ignite Users] <
ml-node+s70518n11524...@n6.nabble.com> wrote:

> Hi Rishi,
>
> Eviction policies allow to specify limits: https://apacheignite.readme.
> io/docs/evictions
>
> -Val
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://apache-ignite-users.70518.x6.nabble.com/max-size-
> on-cache-tp11523p11524.html
> To start a new topic under Apache Ignite Users, email
> ml-node+s70518n1...@n6.nabble.com
> To unsubscribe from Apache Ignite Users, click here
> 
> .
> NAML
> 
>



-- 
Rishi Yagnik




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

max size on cache

[ignite_user2016]

Hi Val,

How can I put a max size on cache ? could not find any property in Cache
Configuration OR I missed something.

Thanks,
Rishi



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

Re: Aggregation of log files

[ignite_user2016]

I found my answers I think it is working by design so user always has a
choice to override logger with jcl logger.

Thank you for all your help,
Rishi



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Aggregation-of-log-files-tp11102p11140.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: ignite log4j is not working

[ignite_user2016]

My bad fixed the issue dont worry about it.



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/ignite-log4j-is-not-working-tp11136p11138.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

ignite log4j is not working

[ignite_user2016]

Here is my configuration for logging - 

 
  
 
  



Copied following libs from optional lib folder to enable log4j logging - 

ignite-log4j-1.7.0.jar  log4j-1.2.17.jar


And the log as follows - 

log4j: Trying to find [log4j.xml] using context classloader
sun.misc.Launcher$AppClassLoader@764c12b6.
log4j: Trying to find [log4j.xml] using
sun.misc.Launcher$AppClassLoader@764c12b6 class loader.
log4j: Trying to find [log4j.xml] using ClassLoader.getSystemResource().
log4j: Trying to find [log4j.properties] using context classloader
sun.misc.Launcher$AppClassLoader@764c12b6.
log4j: Trying to find [log4j.properties] using
sun.misc.Launcher$AppClassLoader@764c12b6 class loader.
log4j: Trying to find [log4j.properties] using
ClassLoader.getSystemResource().
log4j: Could not find resource: [null].
log4j: System property is :null
log4j: Standard DocumentBuilderFactory search succeded.
log4j: DocumentBuilderFactory is:
com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
log4j: debug attribute= "false".
[13:25:32,239][WARN ][main][IgniteKernal%WebGrid] Peer class loading is
enabled (disable it in production for performance and deployment consistency
reasons)
[13:25:32,723][WARN ][main][NoopCheckpointSpi] Checkpoints are disabled (to
enable configure any GridCheckpointSpi implementation)
[13:25:32,754][WARN ][main][GridCollisionManager] Collision resolution is
disabled (all jobs will be activated upon arrival).
[13:25:32,758][WARN ][main][NoopSwapSpaceSpi] Swap space is disabled. To
enable use FileSwapSpaceSpi.
[13:25:43] New version is available at ignite.apache.org: 1.9.0

With this setting I see the log file gets generated it s not taking my log
file setting that is as follows - 

 










I am expecting logs to get generated on ignite.log so wondering what am I
missing here ? 

Thanks,
Rishi





--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/ignite-log4j-is-not-working-tp11136.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Aggregation of log files

[ignite_user2016]

I believe IgniteVisor would act as a client to ignite server, correct ? 

So wondering how to control log files here when ignite visor is used for
monitoring ? 



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Aggregation-of-log-files-tp11102p11131.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Aggregation of log files

[ignite_user2016]

Hi Val,

We generally see the message - 
Ignite node started OK (id=cc119e30) on the console 

so now log file will be generated as follows - 

ignite-cc119e30.0

now if I am monitoring ignite visor command every time it will connect to
ignite via new session with new id as a result for every monitor we set
would generate log file with that session id.

hope I clarify here.

Thanks,
Risih






--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Aggregation-of-log-files-tp11102p11128.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Aggregation of log files

[ignite_user2016]

So The default logger is JUL how can I change it to log4j-2 logging ? 





--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Aggregation-of-log-files-tp11102p11127.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Aggregation of log files

[ignite_user2016]

Here is the log4j config, I changed it to warn level still sees INFO 



























[09:20:42,208][INFO][main][IgniteKernal] Config URL:
file:/C:/projects/Ignite/apache-ignite-fabric-1.7.0-bin/config/default-config.xml
[09:20:42,208][INFO][main][IgniteKernal] Daemon mode: off
[09:20:42,208][INFO][main][IgniteKernal] OS: Windows 7 6.1 x86
[09:20:42,208][INFO][main][IgniteKernal] OS user: host
[09:20:42,208][INFO][main][IgniteKernal] Language runtime: Java Platform API
Specification ver. 1.8
[09:20:42,208][INFO][main][IgniteKernal] VM information: Java(TM) SE Runtime
Environment 1.8.0_20-b26 Oracle Corporation Java HotSpot(TM) Client VM
25.20-b23
[09:20:42,223][INFO][main][IgniteKernal] VM total memory: 0.24GB
[09:20:42,223][INFO][main][IgniteKernal] Remote Management [restart: on,
REST: on, JMX (remote: on, port: 49237, auth: off, ssl: off)]
[09:20:42,223][INFO][main][IgniteKernal]
IGNITE_HOME=C:\projects\Ignite\apache-ignite-fabric-1.7.0-bin
[09:20:42,223][INFO][main][IgniteKernal] VM arguments: [-DIGNITE_QUIET=true,
-DIGNITE_SUCCESS_FILE=C:\projects\Ignite\apache-ignite-fabric-1.7.0-bin\work\ignite_success_060af0bc-5e6b-4a1b-ab1e-175170bd5eae,
-Dcom.sun.management.jmxremote, -Dcom.sun.management.jmxremote.port=49237,
-Dcom.sun.management.jmxremote.authenticate=false,
-Dcom.sun.management.jmxremote.ssl=false,
-DIGNITE_HOME=C:\projects\Ignite\apache-ignite-fabric-1.7.0-bin,
-DIGNITE_PROG_NAME=ignite.bat]
[09:20:42,223][INFO][main][IgniteKernal] Configured caches
['ignite-marshaller-sys-cache', 'ignite-sys-cache',
'ignite-atomics-sys-cache']
[09:20:42,223][INFO][main][IgniteKernal] 3-rd party licenses can be found
at: C:\projects\Ignite\apache-ignite-fabric-1.7.0-bin\libs\licenses
[09:20:42,239][WARNING][pub-#3%null%][GridDiagnostic] Initial heap size is
16MB (should be no less than 512MB, use -Xms512m -Xmx512m).
[09:20:45,297][INFO][main][IgniteKernal] Non-loopback local IPs:
10.204.48.143, 192.168.1.3


and I am using log4j-2 configuration, copied log4j2 lib to lib folder ? what
am I missing here ? 

Thanks for all your help..



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Aggregation-of-log-files-tp11102p11125.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Aggregation of log files

[ignite_user2016]

Any reply would be helpful here.. 



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Aggregation-of-log-files-tp11102p6.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite client reconnect error

[ignite_user2016]

Thanks Val,

We will sent you the code changes with added documentation.

On Fri, Mar 10, 2017 at 3:20 AM, vkulichenko [via Apache Ignite Users] <
ml-node+s70518n11103...@n6.nabble.com> wrote:

> IGNITE-2766 is not fixed yet, and I think overriding and tweaking
> SpringCacheManager is currently the only way to work around the problem.
> Would be great if you configure your change to the project.
>
> -Val
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://apache-ignite-users.70518.x6.nabble.com/Ignite-
> client-reconnect-error-tp11091p11103.html
> To start a new topic under Apache Ignite Users, email
> ml-node+s70518n1...@n6.nabble.com
> To unsubscribe from Apache Ignite Users, click here
> 
> .
> NAML
> 
>



-- 
Rishi Yagnik




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

Aggregation of log files

[ignite_user2016]

Currently, we have a monitor in place to monitor ignite servers, however we
are seeing log files for every session that is connected to ignite.As a
result, we see almost 50-80K log files every day.

Is there a way where I can aggregate log files with some settings ? any
example would be helpful here.

Looking forward for your quick help here.

Thanks,
Rishi



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Aggregation-of-log-files-tp11102.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite client reconnect error

[ignite_user2016]

I could not find a most elegant solution and upgrading 1.8 did not work for
us.

I override the SpringCacheManager and implemented subscription of events on
client ignite.

This is just a hack but looking for correct fix in future to avoid client
reconnect errors.

Thanks,
Rishi



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

Ignite client reconnect error

[ignite_user2016]

We are on ignite version 1.8, when the server goes down we can connect the
client error but our caches are not being cleared.what is the expected
behavior here ? 

http://apache-ignite-developers.2346864.n4.nabble.com/Finished-IGNITE-901-td1690.html

A couple of additional questions:
1. I am assuming that near caches are dropped on reconnect as well, right?
2. Do we have documentation for this feature? If not, can we add this
documentation to the client section?
3. Did this feature in any way affect ability to start many (100+) clients
in the same JVM?

Same questions are being asked by dsetrakyan ? 

https://issues.apache.org/jira/browse/IGNITE-2766

This says it s fixed in 1.8.0 however we are seeing the same issue here.
It looks like a bug again how do we handle this scenario ? 



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

configuration of SSL Ciphers

[ignite_user2016]

Is there a way on ignite if I want to disable SSL Ciphers ? I would like to
disable weak ciphers, any configuration would help here ? 

For example, I would like to disable weak ciphers 3DES, how do I do that on
Ignite ? 

Thanks,
Rishi



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/configuration-of-SSL-Ciphers-tp10676.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Question on replication

[ignite_user2016]

I have a question on replication, when we are replicaing the cache, during an
update does it update the entire object ? OR any update the deltas ? 

For example,

I replicated entity-Cache on 2 node cluster, entity cache has following
entities A and B ? now when I update the cache for entity A for certain
attributes, would the Ignite update only deltas on entity A? OR will replace
the entire entity A.

Thank you for taking a time on replying my questions.

Rishi



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

Re: spring boot clustered session with ignite

[ignite_user2016]

Yes,I am interested in contribution.



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/spring-boot-clustered-session-with-ignite-tp10455p10510.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: spring boot clustered session with ignite

[ignite_user2016]

How do I vote for following feature ? 


https://issues.apache.org/jira/browse/IGNITE-2741

Thanks,
Rishi



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/spring-boot-clustered-session-with-ignite-tp10455p10505.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: spring boot clustered session with ignite

[ignite_user2016]

Any reply will help me here ? we are running into issues where spring  filter
s cant recognize Ignite as session data store result in weird errors.

I see an issue out there but no progress since it got created.

Better response would help me sticking to Ignite here.



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/spring-boot-clustered-session-with-ignite-tp10455p10465.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

spring boot clustered session with ignite

[ignite_user2016]

Has any body had any success on running spring boot session with ignite ? we
want to use ignite as our session cache so that we can clustered out SB app.

https://issues.apache.org/jira/browse/IGNITE-2741

Do we have to use spring session here ? wondering why not simple web session
? 

Thanks,
Rishi



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/spring-boot-clustered-session-with-ignite-tp10455.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: 2nd level cache with eclipselink

[ignite_user2016]

Any plan to add eclipse link JPA implementation. for 2nd level cache ?

Take Care,
Rishi

> On Feb 2, 2017, at 8:07 PM, vkulichenko [via Apache Ignite Users] 
>  wrote:
> 
> I don't think there is an implementation for Eclipselink. Ignite provides L2 
> cache for Hibernate and also there is an implementation for MyBatis. 
> 
> -Val 
> 
> If you reply to this email, your message will be added to the discussion 
> below:
> http://apache-ignite-users.70518.x6.nabble.com/2nd-level-cache-with-eclipselink-tp10385p10402.html
> To unsubscribe from 2nd level cache with eclipselink, click here.
> NAML




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/2nd-level-cache-with-eclipselink-tp10385p10408.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

2nd level cache with eclipselink

[ignite_user2016]

Can any one post an example on 2nd level cache with eclipselink ? is it being
supported with Ignite cache ? 

any help would be helpful here..

Thanks,
Rishi



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/2nd-level-cache-with-eclipselink-tp10385.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.