Re: How about adding kryo or protostuff as an optional marshaller?

Hi Lin, For a fair comparison, you have to use raw mode in Ignite, as discussed there: http://mail-archives.apache.org/mod_mbox/ignite-user/201606.mbox/%3ctencent_7adfd5073dba92c92769c...@qq.com%3E Pavel. On Wed, Jul 20, 2016 at 4:50 AM, Lin wrote: > Hi Andrey, > > Thanks for your response and

Re: https://apacheignite.readme.io/docs/rest-api#destroy-cache

Just to clarify: custom object types will be supported based on JSON format. Main ticket for this is this one: https://issues.apache.org/jira/browse/IGNITE-962 -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/https-apacheignite-readme-io-docs-rest-api-destro

Re: https://apacheignite.readme.io/docs/rest-api#destroy-cache

Hi, Please properly subscribe to the mailing list so that the community can receive email notifications for you messages. Here is the instruction: http://apache-ignite-users.70518.x6.nabble.com/mailing_list/MailingListOptions.jtp?forum=1 Marco wrote > REST API now provides Get/Put/GetAll/PutAll

Re: Socket Closure due to write timout

Hi, It sounds like that your network is not very stable, so increasing connection timeout helps to make the system more stable. This is fine, out default settings mostly tuned for fast stable network to provide better performance. What queue are you referencing to? -Val -- View this message i

Re: Cluster singleton and predicate method

Hi Vladik, You can use IgniteServices.cancel() method to undeploy the service, and then deploy it again. ServiceConfiguration contains 'nodeFilter' property that allows to define on which node(s) the service has to be deployed. Will this work for you? -Val -- View this message in context: ht

Re: 答复: ignite Spring application context resource is not injected problem

Kevin, This exception is thrown if Ignite node was started without knowing about the Spring app context. Generally it works if it is started using Ignition.start(..) method which gets a Spring configuration file, or if default Ignition.start() is used. The latter looks like your case, so I don't u

Re: Can not start another client when doing ContinuousAsyncQuery

I found it is related to "peerClassLoadingEnabled". If it is setted "true", client started failed. If it is setted "false", client started OK. The test sequence is: 1. Start a Ignite Server. 2. Start a Ignite client to do ContinuousAsyncQuery. 3. Start another Ignite client before step 2 has fini

答复: ignite Spring application context resource is not injected problem

Hi Val, Problem solved by using new class to extends from CacheJdbcPojoStoreFactory to solve this problem. But I think ignite should consider why the default CacheJdbcPojoStoreFactory not work, there might be a bug, because using default CacheJdbcPojoStoreFactory even with datasource bean defi

Re: How about adding kryo or protostuff as an optional marshaller?

Hi Andrey, Thanks for your response and advice. FYI, protostuff-runtime[1] does not need any *.proto files, and can generate the schema for you to cache and use at runtime via reflections[2]. I have post my benchmark codes in github[3], for customized class like [4] with two different cases

答复: ignite Spring application context resource is not injected problem

Hi Val, I tried both. And non of them work for me: 1. first I start from ignite.sh script, cache created okay. However, when I call from the client side (using Ignition.start()) to put data into cache, it gives me Spring application context resource is not injected error. 2. I restart the server

Re: Code execution on data node

Hi Ionut, This will always return the same node (the first one in the list). If you want to execute a closure on one of the nodes where CACHE exists, just do this: ignite.compute(ignite.cluster().forDataNodes("CACHE")).broadcast(...); Also note that clients do not execute compute logic unless yo

Re: ignite Spring application context resource is not injected problem

Hi Kevin, Can you please provide the whole configuration file and also show how you start the node? Is it a standalone node started with ignite.sh script or an embedded node started in code using Ignition.start()? -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabbl

Re: Removing or overwriting cache value, but still able to get it from the cache

Yes, I just realized that you don't have write-through, so delete operations are not propagated to the DB. In this case the behavior you're describing looks correct from Ignite standpoint. If you update something directly in the DB, but Ignite then loads old values from the DB, most likely the bug

Re: Can not start another client when doing ContinuousAsyncQuery

Hi, Do you have the test that reproduces the issue? I'm not sure I understand the sequence of events. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Can-not-start-another-client-when-doing-ContinuousAsyncQuery-tp6375p6395.html Sent from the Apache Ignite

Re: Pagination to fetch complete Cache data

Hi, Please properly subscribe to the mailing list so that the community can receive email notifications for you messages. Here is the instruction: http://apache-ignite-users.70518.x6.nabble.com/mailing_list/MailingListOptions.jtp?forum=1 begineer wrote > Sorry for mistake, correction in below li

Re: Socket Closure due to write timout

When increase the timeout (Very large) the issue goes away, however, we start getting queue size (Unack'd) messages. What I did was bump up the message queue size and decreased the socket timeout and it works perfectly. Is bumping up the queue size an anti-pattern? We do send a lot of tasks to be

Socket Closure due to write timout

Hello, I am trying to understand a socket write timeout filling our logs. While the jobs do finish eventually, they are a bit unsettling and would appreciate an explanation. The easy workaround is to seriously bump up the socket write timeout by maximum of affinity task time. However, why is the t

Re: Issue with concurrent users on Ignite 1.6.0 ODBC

Guys, Can someone who is more familiar with the H2 engine take a look? Sergi? Best Regards, Igor On Tue, Jul 19, 2016 at 2:18 PM, Agneeswaran < agneeswaran.ponnuraman...@nielsen.com> wrote: > Thanks Igor, > > Please find the attached Node log file. > > ignite-157c6cf1.zip > < > http://apache-ig

Re: How about adding kryo or protostuff as an optional marshaller?

Lin, I have no experience with protostuff, but if it relies on the user-defined proto files for generation of the serialization/deserialization stubs, then you'd have to provide the proto files for all serializable Ignite classes. You decide whether or not it's worth the effort. Of course,

Re: How about adding kryo or protostuff as an optional marshaller?

Hi Andrey, Than you for your advice, we will consider it seriously. BTW, it looks like all of the general serializers will work like Kyro, as we don't know any information about user's special readObject/writeObject routines , so protostuff may also meet these problems? Is it right? Thanks

Code execution on data node

Hi, What is the standard way of executing code on a data node (and not in the client)? Is there any issue with this usage in the client /ignite.compute(ignite.cluster().forDataNodes("CACHE").forNode(ignite.cluster().forDataNodes("CACHE").node())).broadcast(() -> {the logic});/ ? Thanks, Ionut

Re: How to troubleshoot a slow client node get()

Thanks Yakov and sorry for late reply. I tried to disable the shared memory communication and it seems working fine so far: public class App { public static void main(String[] args) { System.out.println("ver 0719-1933"); App app = new App();

Re: Issue with concurrent users on Ignite 1.6.0 ODBC

Thanks Igor, Please find the attached Node log file. ignite-157c6cf1.zip We could see SQL Exception caused while executing SQL statements, >From the Node log, at java.lang.Thread.run(Thread.java:745) Caused by:

Re: Adding a binary object to two caches fails with FULL_SYNC write mode configured for the replicated cache

Hi, It's also not working with PRIMARY_SYNC if you do gets. I've created an issue: https://issues.apache.org/jira/browse/IGNITE-3505 You may watch it to be notified on a progress. Thanks for participating in Apache Ignite's community. 2016-07-19 8:05 GMT+03:00 pragmaticbigdata : > Please see

Re: Issue with concurrent users on Ignite 1.6.0 ODBC

Agneeswaran, When you start your node there should be a path to the log: [18:27:41] ^-- Logging to file '...' By default, logs are stored in $IGNITE_HOME/work/log/ Best Regards, Igor On Tue, Jul 19, 2016 at 1:20 PM, Agneeswaran < agneeswaran.ponnuraman...@nielsen.com> wrote: > Hi Igor, > > S

Re: Issue with concurrent users on Ignite 1.6.0 ODBC

Hi Igor, Sorry, I am not sure where to check this Node log file. Could you please help me on this. Thanks, Agneeswaran -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Issue-with-concurrent-users-on-Ignite-1-6-0-ODBC-tp6217p6382.html Sent from the Apache Ignite

Re: Issue with concurrent users on Ignite 1.6.0 ODBC

Agneeswaran, Can you see any errors in the nodes log? Best Regards, Igor On Tue, Jul 19, 2016 at 1:10 PM, Igor Sapego wrote: > Hi Agneeswaran, > > Sorry, I seem to miss your previous mail. > I'm going to take a look and tell you about the results. > > Best Regards, > Igor > > On Tue, Jul 19, 2

Re: How to troubleshoot a slow client node get()

I see these possible reasons of the delay 1. GC pause on client or server. Please enable GC logging and rerun test. 2. your machine runs out of resources - CPU, memory, disk IO, etc. Can you please check that there are enough resources in the system? 3. Is any energy saving stuff enabled? I also d

Re: Issue with concurrent users on Ignite 1.6.0 ODBC

Hi Agneeswaran, Sorry, I seem to miss your previous mail. I'm going to take a look and tell you about the results. Best Regards, Igor On Tue, Jul 19, 2016 at 9:51 AM, Agneeswaran < agneeswaran.ponnuraman...@nielsen.com> wrote: > Hi Igor, > > Could you please suggest us, how to look forward with

Re: How to troubleshoot a slow client node get()

sorry for late reply, really busy last week can reproduce the read delay with a standalone program now, and use System.out.println() to time the cache read: public class App { public static void main(String[] args) { App app = new App(); app.run();

ignite Spring application context resource is not injected problem

Hi there, When I start Ignite client side code, I met the following error: [17:13:37,062][SEVERE][exchange-worker-#38%default%][GridCachePartitionExchangeManager] Failed to wait for completion of partition map exchange (preloading will not start): GridDhtPartitionsExchangeFuture [dummy=false, for

Re: How about adding kryo or protostuff as an optional marshaller?

Lin, TL;DR Do not use Kryo with Ignite. We tried using Kryo a while back (pre-Binary Objects times) and it didn't work. To add insult to injury, it didn't work in the worst possible way: it would appear to work just fine, no exceptions or anything like that. But then you'd discover that, fo

Can not start another client when doing ContinuousAsyncQuery

My test steps on Ignite version 1.6 are: 1. Start an Ignite with Server mode in remote side. 2. Start a ContinuousAsyncQuery with Client Mode in local side. 3. Start an Ignite with Client Mode in local side at the same time of step 2. I only use default configuration to start Ignite in all 3 steps.

Re: Any plans to enhance support for subselects on partitioned caches?

I hope we will release distributed joins in 1.7 soon, but community can decide to go other way, so I can't promise. Sergi On Tue, Jul 19, 2016 at 10:49 AM, Cristi C wrote: > Thanks, Sergi. I'll try that out. > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble

Re: Any plans to enhance support for subselects on partitioned caches?

Thanks, Sergi. I'll try that out. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Any-plans-to-enhance-support-for-subselects-on-partitioned-caches-tp6344p6373.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Removing or overwriting cache value, but still able to get it from the cache

Thank you. Coming with a reproducible example is a challenge, and will take, but I need this issue solved, so will try to come with something you can reproduce locally. Regards /"In you particular case, I would expect the removeAll() removes the provided keys from all caches and from the persiste

Re: Issue with concurrent users on Ignite 1.6.0 ODBC

Hi Igor, Could you please suggest us, how to look forward with this. Thanks, Agneeswaran Pasting earlier post. Hi Igor, We have debugged our code, as the core dump refers to SQLGetDiagRec() function. We are using this particular function to do the error validation,Yes previously TextLengthP

Cluster singleton and predicate method

Hi, I have a service that should have single instance running on cluster. So I use cluster singleton feature for this , which works fine. Now in my service I have some internal logic that decides that this particular machine is not good anymore and it needs to migrate. This logic doesn’t related