Re: Ignite 2.3.0 hangs in startup

[ezhuravlev]

Looks like you witnessed this issue:
https://issues.apache.org/jira/browse/IGNITE-6555
Which is already fixed and will be available in 2.4 release

Evgenii



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

Re: Ignite 2.3.0 hangs in startup

[Sumanta Ghosh]

Hi,
Got the reason now. Ignite 2.3.0 hangs because of a regression bug wherein
the cachestores use @SpringResource annotation and ignite starts up with
SpringCacheManager class.
Thanks for the help extended. 



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

Re: Ignite 2.3.0 hangs in startup

[Sumanta Ghosh]

Hi,
After enabling debug mode on ignite logging, the log shows ignite
continuously getting timeout in the following: -

2017-11-13 21:33:00.770 DEBUG 11232 --- [r-#23%bfs-grid%]
o.a.i.i.p.timeout.GridTimeoutProcessor   : Timeout has occurred
[obj=CancelableTask [id=2ea6e16bf51-d6f29d66-da45-4fe6-afda-81d6f43452a1,
endTime=1510588980769, period=5000, cancel=false,
task=org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryManager$BackupCleaner@650053ad],
process=true]
2017-11-13 21:33:02.067 DEBUG 11232 --- [r-#23%bfs-grid%]
o.a.i.i.p.timeout.GridTimeoutProcessor   : Timeout has occurred
[obj=CancelableTask [id=bda6e16bf51-d6f29d66-da45-4fe6-afda-81d6f43452a1,
endTime=1510588982062, period=3000, cancel=false,
task=org.apache.ignite.internal.processors.query.GridQueryProcessor$2@ff3c744],
process=true]
2017-11-13 21:33:02.493 DEBUG 11232 --- [r-#23%bfs-grid%]
o.a.i.i.p.timeout.GridTimeoutProcessor   : Timeout has occurred
[obj=CancelableTask [id=dda6e16bf51-d6f29d66-da45-4fe6-afda-81d6f43452a1,
endTime=1510588982486, period=3000, cancel=false, task=MetricsUpdater
[prevGcTime=67, prevCpuTime=5183,
super=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$MetricsUpdater@62b4cff]],
process=true]
2017-11-13 21:33:03.581 DEBUG 11232 --- [r-#24%bfs-grid%]
o.a.i.s.c.tcp.TcpCommunicationSpi: Balancing data [min0=0, minIdx=0,
max0=-1, maxIdx=-1]
2017-11-13 21:33:04.115 DEBUG 11232 --- [r-#29%bfs-grid%]
o.a.i.i.p.odbc.ClientListenerProcessor   : Balancing data [min0=0, minIdx=0,
max0=-1, maxIdx=-1]
2017-11-13 21:33:04.193 DEBUG 11232 --- [r-#35%bfs-grid%]
o.a.i.i.p.r.p.tcp.GridTcpRestProtocol: Balancing data [min0=0, minIdx=0,
max0=-1, maxIdx=-1]   

The above is getting printed continuously in the log. Can anyone please help
me understand what I am missing here?



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

Re: Ignite 2.3.0 hangs in startup

[Sumanta Ghosh]

Hi Evgenii,
I checked further, I am using logback with Slf4j (default setting in spring
boot). Can this be an issue? 



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

Re: Ignite 2.3.0 hangs in startup

[Sumanta Ghosh]

Hi Evgenii,
I have now the following set-up
IgniteConfiguration igniteConfig = new IgniteConfiguration();
igniteConfig.setGridLogger(new Slf4jLogger(log));
where log is my Slf4j logger. However, the server still hangs at startup
giving the same message. 



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

Re: Ignite 2.3.0 hangs in startup

[ezhuravlev]

For using slf4j, you need to have a configure file, as it showed in the
message, default it's config/java.util.logging.properties, so, you can add
this file to this path or try to configure slf4j:
https://www.slf4j.org/docs.html

Ignite slf4 logger constructor also have another constructor - new
Slf4jLogger(Logger logger).

Evgenii



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

Re: Ignite 2.3.0 hangs in startup

[Sumanta Ghosh]

Hi All, Evgenii,
Can you please help me here? We are kind of clue-less on this one and as a
result not able to upgrade to 2.3.0. Can you please let me know how to
enable verbose logging in embedded mode (i.e. running from within Spring
Boot application)?




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

Re: Ignite 2.3.0 hangs in startup

[Sumanta Ghosh]

Hi Evgenii,
 I have ignite-slf4j module included in my pom. Also has the following
settings done in java 
IgniteConfiguration igniteConfig = new
IgniteConfiguration();
igniteConfig.setGridLogger(new Slf4jLogger());
Do I have to do anything else? From documentation, these seems to be the
only steps to do to configure slf4j.

Thanks
Sumanta
 



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

Re: Ignite 2.3.0 hangs in startup

[ezhuravlev]

Hi,

As I see in this error message:

 Failed to resolve default logging config file:
config/java.util.logging.properties Console logging handler is not
configured. 

You don't have java.util.logging.properties config file for SLF4j. I've
checked 2.3.0 binaries and this file exists in folder config. You need to
add it to your project.

Also, please check the documentation for configuring SLF4j logger, maybe you
missed something: 

https://apacheignite.readme.io/docs/logging#section-slf4j

Evgenii



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

Ignite 2.3.0 hangs in startup

[Sumanta Ghosh]

Hi,
I have the following settings which works fine in ignite 2.0.0; however,
when I upgraded to 2.3.0, the ignite hangs during start. I am using a single
node setup in a laptop, no cluster.

IgniteConfiguration igniteConfig = new
IgniteConfiguration();
igniteConfig.setGridLogger(new Slf4jLogger(log));
// igniteConfig.setGridName(GRID_NAME);
igniteConfig.setIgniteInstanceName(GRID_NAME);
igniteConfig.setPeerClassLoadingEnabled(false);
// For a stand-alone single node cluster
igniteConfig.setDiscoverySpi(new 
TcpDiscoverySpi().setIpFinder(new
TcpDiscoveryVmIpFinder(true)));

List> cacheConfigs = new
ArrayList>();
addCacheConfigForCommon(cacheConfigs);
addCacheConfigForAuth(cacheConfigs);
addCacheConfigForUpstreamParty(cacheConfigs);
addCacheConfigForBFSParty(cacheConfigs);
addCacheConfigForBFSLoan(cacheConfigs);
igniteConfig.setCacheConfiguration(cacheConfigs.toArray(new
CacheConfiguration[cacheConfigs.size()]));

In the log (console log in eclipse) following is printed

**Ignite starting
2017-11-05 10:39:02.035  INFO 3392 --- [   main]
trationDelegate$BeanPostProcessorChecker : Bean 'igniteConfig' of type
[org.apache.ignite.configuration.IgniteConfiguration] is not eligible for
getting processed by all BeanPostProcessors (for example: not eligible for
auto-proxying)
[10:39:02]__   
[10:39:02]   /  _/ ___/ |/ /  _/_  __/ __/ 
[10:39:02]  _/ // (7 7// /  / / / _/   
[10:39:02] /___/\___/_/|_/___/ /_/ /___/  
[10:39:02] 
[10:39:02] ver. 2.3.0#20171028-sha1:8add7fd5
[10:39:02] 2017 Copyright(C) Apache Software Foundation
[10:39:02] 
[10:39:02] Ignite documentation: http://ignite.apache.org
[10:39:02] 
[10:39:02] Quiet mode.
[10:39:02]   ^-- To see **FULL** console log here add -DIGNITE_QUIET=false
or "-v" to ignite.{sh|bat}
[10:39:02] 
[10:39:02] OS: Windows 8.1 6.3 amd64
[10:39:02] VM information: Java(TM) SE Runtime Environment 1.8.0_92-b14
Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 25.92-b14
[10:39:02] Configured plugins:
[10:39:02]   ^-- None
[10:39:02] 
[10:39:06] 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.
[10:39:06] Security status [authentication=off, tls/ssl=off]
2017-11-05 10:39:07.213 ERROR 3392 --- [   main]
 
: Failed to resolve default logging config file:
config/java.util.logging.properties
Console logging handler is not configured.

Thanks
Sumanta




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