Ignite log

[deleerhai]

hello!

Following the launch of the ignite has been following the log output, what
is the reason? Why is there a timeout?
 



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

Create cache configuration error

[deleerhai]

Hi,
Create cache configuration error.

 
 

七月 12, 2016 10:13:19 上午 org.apache.catalina.core.ApplicationContext log
严重: StandardWrapper.Throwable
javax.cache.CacheException: Index with name 'code_idx' already exists.
at
org.apache.ignite.configuration.CacheConfiguration$TypeDescriptor.addIndex(CacheConfiguration.java:2429)
at
org.apache.ignite.configuration.CacheConfiguration.processAnnotation(CacheConfiguration.java:2340)
at
org.apache.ignite.configuration.CacheConfiguration.processAnnotationsInClass(CacheConfiguration.java:2292)
at
org.apache.ignite.configuration.CacheConfiguration.processKeyAndValueClasses(CacheConfiguration.java:2233)
at
org.apache.ignite.configuration.CacheConfiguration.setIndexedTypes(CacheConfiguration.java:1913)
at
com.czt.kbp.coupon.repository.cachestore.CouponCacheConfig.config(CouponCacheConfig.java:14)
at
com.czt.kbp.coupon.repository.cachestore.CouponCacheIniter.init(CouponCacheIniter.java:58)
at
com.czt.kbp.coupon.repository.cachestore.CouponCacheIniter.initCache(CouponCacheIniter.java:41)
at
com.czt.kbp.coupon.server.servlet.CouponInitServlet.init(CouponInitServlet.java:19)
at
org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1238)
at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1151)
at 
org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1038)
at
org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4996)
at
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5285)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147)
at
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1408)
at
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1398)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)




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

Ignite create cache blocked.

[deleerhai]

Hi,

Today, a very strange question, Ignite started to complete, when the cache
is blocked, what is the reason? How to solve?
 
 



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

Re: IgniteCache remove cache data, repeated calls to the'deleteAll'CacheStore method many times, which is the reason?

[deleerhai]

Hi,

If you want to enable IgniteCache asynchronous function
(setWriteBehindEnabled (true)), and let IgniteCache in
call'put','putAll','remove','removeAll' trigger CacheStore corresponding
"add",'addAll','delete','deleteAll'. This scene to real now?
The proposed IgniteCache increases the'update'method, while'update' also
increases the CacheStore method.



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/IgniteCache-remove-cache-data-repeated-calls-to-the-deleteAll-CacheStore-method-many-times-which-is--tp6004p6031.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

IgniteCache remove cache data, repeated calls to the'deleteAll'CacheStore method many times, which is the reason?

[deleerhai]

When the'remove'/'removeAll'method is called, the IgniteCahce method is
called. alled multiple times, what is the reason?

config:
 

Execution process:
 
 
 



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/IgniteCache-remove-cache-data-repeated-calls-to-the-deleteAll-CacheStore-method-many-times-which-is--tp6004.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Put IgniteCache data call CacheStore persistent method of confusion

[deleerhai]

Hi,

When the put IgniteCache data call CacheStore persistence method appears the
phenomenon of confusion, what is the reason? How to solve?

As shown in figure:
 
 
When calling the put method of IgniteCache,addAll CacheStore method is
called,Theoretically should call the add method of CacheStore.
 
 
When calling the remove method of IgniteCache,deleteAll CacheStore method is
called,Theoretically should call the delete method of CacheStore.



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Put-IgniteCache-data-call-CacheStore-persistent-method-of-confusion-tp5984.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Ignite start-up connection timeout?

[deleerhai]

Hi,
Start ignite times wrong. How to solve? How to achieve more than 3 cache
query? Please help me. Thank you very much!


[29 09:40:49,277 DEBUG] [localhost-startStop-1]
multicast.TcpDiscoveryMulticastIpFinder - Address receive timeout.
[29 09:40:50,203 DEBUG] [tcp-disco-msg-worker-#2%null%] tcp.TcpDiscoverySpi
- Message has been added to queue: TcpDiscoveryStatusCheckMessage
[creatorNode=TcpDiscoveryNode [id=ca4d625c-71cb-4de9-b810-61469afe0b35,
addrs=[0:0:0:0:0:0:0:1, 127.0.0.1, 192.168.31.156],
sockAddrs=[PC-20160314ERQT/192.168.31.156:47500, /0:0:0:0:0:0:0:1:47500,
/127.0.0.1:47500, /192.168.31.156:47500], discPort=47500, order=0,
intOrder=0, lastExchangeTime=1467164448141, loc=true,
ver=1.5.0#20151229-sha1:f1f8cda2, isClient=false], failedNodeId=null,
status=0, super=TcpDiscoveryAbstractMessage [sndNodeId=null,
id=7f2d0d99551-ca4d625c-71cb-4de9-b810-61469afe0b35, verifierNodeId=null,
topVer=0, pendingIdx=0, failedNodes=null, isClient=false]]
[29 09:40:50,203 DEBUG] [tcp-disco-msg-worker-#2%null%] tcp.TcpDiscoverySpi
- Processing message [cls=TcpDiscoveryStatusCheckMessage,
id=7f2d0d99551-ca4d625c-71cb-4de9-b810-61469afe0b35]
[29 09:40:50,204 DEBUG] [tcp-disco-msg-worker-#2%null%] tcp.TcpDiscoverySpi
- Ignore message, local node order is not initialized
[msg=TcpDiscoveryStatusCheckMessage [creatorNode=TcpDiscoveryNode
[id=ca4d625c-71cb-4de9-b810-61469afe0b35, addrs=[0:0:0:0:0:0:0:1, 127.0.0.1,
192.168.31.156], sockAddrs=[PC-20160314ERQT/192.168.31.156:47500,
/0:0:0:0:0:0:0:1:47500, /127.0.0.1:47500, /192.168.31.156:47500],
discPort=47500, order=0, intOrder=0, lastExchangeTime=1467164448141,
loc=true, ver=1.5.0#20151229-sha1:f1f8cda2, isClient=false],
failedNodeId=null, status=0, super=TcpDiscoveryAbstractMessage
[sndNodeId=null, id=7f2d0d99551-ca4d625c-71cb-4de9-b810-61469afe0b35,
verifierNodeId=null, topVer=0, pendingIdx=0, failedNodes=null,
isClient=false]], locNode=TcpDiscoveryNode [id=ca4d625c-71cb-4de9-b81
0-61469afe0b35, addrs=[0:0:0:0:0:0:0:1, 127.0.0.1, 192.168.31.156],
sockAddrs=[PC-20160314ERQT/192.168.31.156:47500, /0:0:0:0:0:0:0:1:47500,
/127.0.0.1:47500, /192.168.31.156:47500], discPort=47500, order=0,
intOrder=0, lastExchangeTime=1467164448141, loc=true,
ver=1.5.0#20151229-sha1:f1f8cda2, isClient=false]]
[29 09:40:50,258 DEBUG] [localhost-startStop-1]
multicast.TcpDiscoveryMulticastIpFinder - Address receive timeout.
[29 09:40:50,260 DEBUG] [localhost-startStop-1]
multicast.TcpDiscoveryMulticastIpFinder - Received nodes addresses:
[PC-20160314ERQT/192.168.31.156:47500, /0:0:0:0:0:0:0:1:47500,
/127.0.0.1:47500]
[29 09:40:51,006 DEBUG] [grid-timeout-worker-#25%null%]
timeout.GridTimeoutProcessor - Timeout has occurred: CancelableTask
[id=5f2d0d99551-ea964ce2-f891-491e-8267-7f5240be0c80, endTime=1467164450992,
period=3000, cancel=false, task=MetricsUpdater [prevGcTime=-1,
prevCpuTime=-1,
super=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$MetricsUpdater@598ecc79]]
[29 09:40:51,278 ERROR] [localhost-startStop-1] tcp.TcpDiscoverySpi -
Exception on direct send: Connection refused: connect
java.net.ConnectException: Connection refused: connect
at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)
at
java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:85)
at
java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at
java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at
java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.openSocket(TcpDiscoverySpi.java:1266)
at
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.openSocket(TcpDiscoverySpi.java:1241)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl.sendMessageDirectly(ServerImpl.java:1086)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl.sendJoinRequestMessage(ServerImpl.java:939)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl.joinTopology(ServerImpl.java:804)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl.spiStart(ServerImpl.java:329)
at
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.spiStart(TcpDiscoverySpi.java:1835)
at
org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:255)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(GridDiscoveryManager.java:660)
at
org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1505)
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:917)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1688)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.

Re: Asynchronous cache batch write data can not be asynchronous execution

[deleerhai]

Hi,
Thank you very much!



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Asynchronous-cache-batch-write-data-can-not-be-asynchronous-execution-tp5638p5664.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Cache data loss

[deleerhai]

Hi,
The problem has been solved. Thank you very much.



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

Asynchronous cache batch write data can not be asynchronous execution

[deleerhai]

Hi,
Why asynchronous cache batch write data can not be asynchronous, please help
me.

1,Start a transaction, call the addAll method.
 

2,Gets an asynchronous cache and writes data to the cache.
 

3,Triggers the writeAll method of CacheStore, persistent storage.
 

4,Print execution process.The same thread execution, not asynchronous
execution.
 

I want asynchronous execution of persistent storage, can you do it?
Please help me.Thank you very much!



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Asynchronous-cache-batch-write-data-can-not-be-asynchronous-execution-tp5638.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Cache data loss

[deleerhai]

hi,
Data loss problem in batch operation!

 

 



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

Re: Ignite Start exception

[deleerhai]

hi,

Why not start the client node output log? 

The log output has a regular [id=0 ~ id=1023].

How to explain these logs?




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

Ignite Start exception

[deleerhai]

hi!
I have three nodes deployed, as shown below:

 

The server node starts normal, and is responsible for data thermal loading.
 

Client nodes start normal, can get data from the server node.
 

inner node start exception, always print the following log, what is the
reason?
 
 

Please help me!



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