Re: Ignite 2.7 Errors

Philip, if you can bear with so huge JVM pauses, then there is no use to investigate stacktraces anymore. Just increase systemWorkerBlockedTimeout parameter of IgniteConfiguration appropriately, as described in https://apacheignite.readme.io/docs/critical-failures-handling#section-critical-workers-

Re: Ignite 2.7 Errors

hello, Andrey - for your 2nd question, in Ignite 2.5, we have 15 mins + JVM paused as well, but no IgniteException, was working fine. 2019-03-15 19:08:46,088 WARNING [ (jvm-pause-detector-worker)] Possible too long JVM pause: 1001113 milliseconds. 2019-03-15 19:08:46,280 INFO [IgniteKernal%XXX

Re: Ignite 2.7 Errors

Hello, Andrey - for your 1st question, I do have a straceTrace in other *FailureProcessor*.log Thread [name="tcp-disco-msg-worker-#2%XXXGrid%", id=445, state=RUNNABLE, blockCnt=0, waitCnt=320611] at sun.management.ThreadImpl.dumpThreads0(Native Method) at sun.management.ThreadImp

Re: Ignite 2.7 Errors

Sorry, my mistake. I meant the last message you provided, but it doesn't contain stacktrace, only brief thread information. Anyway, 15 minutes long JVM pauses are suspicious. Do you have the same message on 2.5 or 2.6? Best regards, Andrey Kuznetsov. чт, 21 марта 2019, 19:49 Philip Wu p...@enfusi

Re: Ignite 2.7 Errors

before that , there was: 2019-03-20 22:28:45,028 WARNING [G (tcp-disco-msg-worker-#2%XXXGrid%)] Thread [name="grid-nio-worker-tcp-comm-1-#73%XXXGrid%", id=415, state=RUNNABLE, blockCnt=0, waitCnt=0] -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite 2.7 Errors

Hello, Andrey - actually this is the sequence of events in time order: 2019-03-20 22:28:44,999 WARNING [IgniteKernal%XXXGrid (jvm-pause-detector-worker)] Possible too long JVM pause: 928937 milliseconds 2019-03-20 22:28:45,014 SEVERE [G (tcp-disco-msg-worker-#2%XXXGrid%)] Blocked system-critical

Re: Ignite 2.7 Errors

Hello, Andrey - I see this: 2019-03-20 22:28:45,052 WARNING [FailureProcessor (tcp-disco-msg-worker-#2%XXXGrid%)] No deadlocked threads detected. is that what you mean? --- Also, prior to crash, I see this: not sure if it is related. 2019-03-20 22:28:45,029 ERROR [stderr (ActiveMQ Inactivity

Re: Ignite 2.7 Errors

Hi, Philip! There should be a stacktrace of the blocked worker itself in the log, with warn level, before the message you cite, but after "Blocked system-critical thread has been detected." Could you please share that trace? It can help to understand failure cause. Best regards, Andrey Kuznetsov.

Re: Ignite 2.7 Errors

Hello! With NoOp handler this should be a purely cosmetic message. Regards, -- Ilya Kasnacheev чт, 21 мар. 2019 г. в 18:15, Philip Wu : > Thanks, llya! > > Actually it happened in PROD system again last night ... even with > NoOpFailureHandler. > > I am rolling back to Ignite 2.5 or 2.6 for n

Re: Ignite 2.7 Errors

Thanks, llya! Actually it happened in PROD system again last night ... even with NoOpFailureHandler. I am rolling back to Ignite 2.5 or 2.6 for now. Thanks! 2019-03-20 22:28:45,044 SEVERE [ (tcp-disco-msg-worker-#2%XXXGrid%)] Critical system error detected. Will be handled accordingly to configu

Re: Ignite 2.7 Errors

Hello! We are tweaking this mechanism so maybe you will wish to reenable it in 2.8. Regards, -- Ilya Kasnacheev ср, 20 мар. 2019 г. в 18:30, Philip Wu : > Thank you, IIya! > > We ended up using > > cfg.setFailureHandler(new NoOpFailureHandler()); > > it silenced the errors and no more stack d

Re: Ignite 2.7 Errors

Thank you, IIya! We ended up using cfg.setFailureHandler(new NoOpFailureHandler()); it silenced the errors and no more stack dumps, etc. and it seems to work like in 2.5 and 2.6, with no other changes. I am still curious if in the future I can take that line out if 2.7 is more stable or 2.8.

Re: Ignite 2.7 Errors

Hello! This is a new features and one which often misfires, see https://apacheignite.readme.io/docs/critical-failures-handling Other than what is described, increasing failureDetectionTimeout often helps. Regards, -- Ilya Kasnacheev вт, 19 мар. 2019 г. в 16:34, Philip Wu : > Hi, recently we

Re: Ignite 2.7 hadoop support

Hello! I don't see it either, I'm afraid you will have to build it yourself. It is also available in maven: https://mvnrepository.com/artifact/org.apache.ignite/ignite-hadoop Regards, -- Ilya Kasnacheev чт, 7 февр. 2019 г. в 17:33, Xia Qu : > I am trying to use Ignite for Map Reduce accelera

Re: Ignite 2.7 REST API returning escape characters

Hello! > What is the best practice way to do this in Ignite? Creating your own ConnectorMessageInterceptor implementation. Regards, -- Ilya Kasnacheev пн, 21 янв. 2019 г. в 21:05, EMCox : > Ilya, > > Thanks for helping me. > > I am trying to store the JSON as a string using the REST API Add

Re: Ignite 2.7 REST API returning escape characters

Eric, I might be misunderstand you, but the example you provided is: A full REST/HTTP response which has request and response payloads, and the response itself should have three constituent parts: - Start Line, - Headers, and - Body Now, I cannot see your actual output and it is client log

Re: Ignite 2.7 REST API returning escape characters

Glenn, I don't want to or need to interogate the JSON being stored. I just need it to be returned as valid JSON. If you try to parse a simple response as i show with the escape characters it will fail JSON validation and does. I just need the dynamic JSON to be valid in the response, stored in w

Re: Ignite 2.7 REST API returning escape characters

Eric, Just to be clear, the full REST response is legitimate and valid JSON, in fact the escape characters around the quotes in the response element (COMPARE REST Response to the Response element INSIDE the REST Response) are there precisely to keep it valid. Unfortunately, what you would like is

Re: Ignite 2.7 REST API returning escape characters

Glenn and Ilya, Can I take this string response and parse it as a JSON object using the Ignite REST API? Or am I forced into a programming language such as C# or Java to perform parse as JSON Object? I'm trying to use the Ignite REST API out of the box and have it return valid JSON. The string Ig

Re: Ignite 2.7 REST API returning escape characters

On the topic of the actual return, if you look at the documentation, I believe the Cache Get returns a single level JSON structure that includes a simple string "existing value" as below: Get and put Get and put command stores the

Re: Ignite 2.7 REST API returning escape characters

Ilya, Thanks for helping me. I am trying to store the JSON as a string using the REST API Add method. For instance, i want to store {"name":"Jamie"} in the cache and when I do a get return the same JSON data structure. Of course, in real life the JSON data structure could be much more complex

Re: Ignite 2.7 REST API returning escape characters

Hello again! You will also have to supply an interceptor to do this transformation. Ignite doesn't have native support for JSON so this step is necessary. Regards, -- Ilya Kasnach

Re: Ignite 2.7 REST API returning escape characters

Hello! I guess this means you store JSON as String in cache. Is this the case? If you want data to be output as JSON you will have to store it structured (such as with POJOs or Binary Objects). Regards, -- Ilya Kasnacheev пн, 21 янв. 2019 г. в 19:47, EMCox : > Add request: > Date →Mon, 21 Ja

Re: Ignite 2.7 REST API returning escape characters

Add request: Date →Mon, 21 Jan 2019 16:40:09 GMT Content-Type →application/json;charset=utf-8 Content-Length →124 Server →Jetty(9.4.11.v20180605) POST http://abcdef9d15:8080/ignite?cmd=add&key=107&val={"name":"Ceasar"}&cacheName=default&destId=8b13ac15-f503-4f4a-ab1f-a7fc3ce93596 {"successStatu

Re: Ignite 2.7 REST API returning escape characters

Hello! Can you show an example of such output? Note that Ignite will use JSON, which in turn will escape some characters in strings. Regards, -- Ilya Kasnacheev пн, 21 янв. 2019 г. в 17:04, eric...@outlook.com : > To all, > > I'm using Ignite 2.7 with the REST API enabled. When retrieving us

Re: Ignite 2.7 Client node security credentials configuration

I'm using IgniteConfiguration to provide the config while starting the node and not the XML file. I can't find a way to set the SecurityCredentials inside it. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite 2.7 Client node security credentials configuration

Hi, When you use the thick client, it uses pretty the same configuration file as server nodes, so, you can define it there. Best Regards, Evgenii вт, 15 янв. 2019 г. в 09:33, garima.j : > Hello, > > While going through the documents, I read that to enable basic > authentication, i can enable th

Re: Ignite 2.7 Persistence

Some java code that helps me on node startup: // Call for each partition in parallel private void preloadPartition(int partition) {     IgniteCache cache = ignite     .cache("test_cache")     .withKeepBinary();     ScanQuery query = new ScanQuery<>(partition, (k, v

RE: Ignite 2.7 Persistence

Is there a command that one can/needs to run to load the data into memory after restart of Ignite? The documentation suggests that at least for 2.7 that is not necessary, and I have not found a command that would start the loading into memory from persistence. It looks like one can write some Java

RE: Ignite 2.7 Persistence

for most users. Stan From: gweiske Sent: 11 января 2019 г. 2:03 To: user@ignite.apache.org Subject: RE: Ignite 2.7 Persistence Thanks for the replies. Yes, subsequent queries are faster, but the time to run the query the first time (i.e. load the data into memory) after a restart can be measured in

RE: Ignite 2.7 Persistence

Thanks for the replies. Yes, subsequent queries are faster, but the time to run the query the first time (i.e. load the data into memory) after a restart can be measured in hours and is significantly longer than loading the data from a csv file. That does not seem right. -- Sent from: http://a

RE: Ignite 2.7 Persistence

after the node start it may shorten the warmup period. Stan From: Glenn Wiebe Sent: 8 января 2019 г. 18:02 To: user@ignite.apache.org Subject: Re: Ignite 2.7 Persistence I am new to Ignite, but as I understand it, after cluster restart, data is re-hydrated into memory as the nodes receive requests

Re: Ignite 2.7 Persistence

I am new to Ignite, but as I understand it, after cluster restart, data is re-hydrated into memory as the nodes receive requests for their partitions' entries. So, a first query would be as slow as a distributed disk-based query. Subsequent queries should have some (depending on memory available) i

RE: Ignite 2.7

Thanks Andrey. От: Maxim.Pudov Отправлено: 26 ноября 2018 г. в 12:56 Кому: user@ignite.apache.org Тема: Re: Ignite 2.7 It is up to community to decide. You can track the progress here: http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-7-Last-Mile-td36359i40.html I think it

Re: Ignite 2.7

It is up to community to decide. You can track the progress here: http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-7-Last-Mile-td36359i40.html I think it will happen in a matter of weeks. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: ignite 2.7 connection pool support?

Hi, Ignite data source should be supported in 2.7 release. The use case you can see in next test: https://github.com/apache/ignite/blob/master/modules/clients/src/test/java/org/apache/ignite/jdbc/thin/JdbcThinDataSourceSelfTest.java However, you can try to ask Taras according to https://issues.a