Re: CacheMode - REPLICATED related questions
Answers for all your questions (except of 4th) here depend on cache write synchronization mode. In case of FULL_SYNC mode the exception will be thrown on the client and you will be able to catch and process it. For PRIMARY_SYNC and FULL_ASYNC modes the client will get successful result and it's possible in this case that data will be inconsistent between primary and backup. So you should choose mode that provides required consistency guarantee for you. Your (1,1) entry will be available only if it was written to partition on node. You can use readFromBackup flag in order to control partition type that will be source for entry reading. So, for your use case every get operation will return (1,1) entry after put operation if readFromBackup == false independently of synchronization mode. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/CacheMode-REPLICATED-related-questions-tp16423p16452.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Is the following statement true in all cases for REPLICATED mode ?
Hi, When persistence store is enabled the data pages that can't be stored in the memory will be evicted to the persistence store. But capacity of your disks is still limit your data set size. So the statement is still correct. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Is-the-following-statement-true-in-all-cases-for-REPLICATED-mode-tp16432p16447.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: CacheMode - REPLICATED related questions
Hi, please see my answers (inlined) userx wrote > QUESTION 1: > Is there a way, we can identify which out of the three machines will be > the PRIMARY mode ? And does it change w.r.t different clients, say if C1 > is doing put, the primary is M1 and if C2 is doing put the primary is M2. > The reason I am asking this question is if replication fails for C1 and > say M1 goes down for some reason, then even if M2 and M3 are there, they > are not serving any purpose. You can identify primary node only for a particular partition. Partitions are evenly distributed among the nodes and for particular partition primary and backup nodes will be always different. So there is no primary node for all partitions. Affinity function is responsible for assigning primary or backup nodes for each partition and you can't change this behavior dynamically. userx wrote > QUESTION 2: > Can we configure or designate say M1 always to be primary ? You can't do it using backup filter that should be passed to RendezvousAffinityFunction. But I don't think that it's good idea because usually all request will be sent to the primary node and, in your case, only one node will be under load while other will not. userx wrote > QUESTION 3: > We have one of the CacheWriteSynchronizationMode as PRIMARY_SYNC which > means that put operation will wait for data to be written on PRIMARY NODE > (say M1)? Is there a way that we ensure data to be replicated atleast 2 > out of the 3 machines listed. I could see the options as FULL_SYNC or > PRIMARY_SYNC so its either all of them or just the primary one. There is no such possibility at present. userx wrote > QUESTION 4: > What happens if REPLICATION activity fails ? Is there any documentation > for the same as to what the cluster does in such cases or does client have > to take any actions on its part say log etc ? I'm afraid that I don't understand your question. Do you mean rebalancing due to a node outage or data propagation to backups? userx wrote > QUESTION5: > I am soon going to enter production with Xmx as 1G and "Persistent Store > Enabled" to take care of data to be cached whose size > 1G. Your > https://apacheignite.readme.io/docs/preparing-for-production document has > mentioned the JVM related settings for a server with Xmx of 10G. Since I > am going with 1G, is there a documentation which helps me w.r.t > recommended settings on Xmx of 1g ? It depends on your use cases and there are no any "silver bullet" like advice. It would be great to test your application ander load before production. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/CacheMode-REPLICATED-related-questions-tp16423p16446.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Affinity Key field is not identified if binary configuration is used on cache key object
Hi, this configuration shouldn't work because there is typo in property name in this code snippet (AffinityKeyFieldName should start with lower case, my fault from previous posts): I expect that exception should be throwed up on ignite instance start up because there is no such property "AffinityKeyFieldName". -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Affinity-Key-field-is-not-identified-if-binary-configuration-is-used-on-cache-key-object-tp15959p16079.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Inserting Data From Spark to Ignite
Hi, for data frames you can try to save records one by one but I'm not sure that Spark will not use batch store. The second option is transformation data frame to RDD and use savePairs method. Will this work for you? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Inserting-Data-From-Spark-to-Ignite-tp14937p15994.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Inserting Data From Spark to Ignite
Hi, Could you please share your cache configuration and full error stack trace? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Inserting-Data-From-Spark-to-Ignite-tp14937p15011.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: 回复：Weird index out bound Exception
Your client node could get cache by name. There is no any need to init cache configuration if cache already created on servers. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Weird-index-out-bound-Exception-tp14905p15004.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: 答复: how to set the interval time between tests while running yardstick-ignite
There are no any time interval between tests. It's test duration. You can change it in configuration file using `d` property. E.g. for 5 minutes you should use: # Duration. d=300 -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/how-to-set-the-interval-time-between-tests-while-running-yardstick-ignite-tp14539p15001.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Weird index out bound Exception
Hi, I can't reproduce your case. But the issue could occur if you had a REPLICATED cache and after some time changed it to PARTITIONED and for example call to getOrCreateCache keeping old cache name. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Weird-index-out-bound-Exception-tp14905p14920.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Pessimistic TXN did not release lock on a key, all subsequent txns failed
Hi, I think writeSynchronizationMode doesn't affect key locking. Actually this mode is just hint for transaction origination node ant it defines when tx should return control flow to user code: when all nodes responded or only primary nodes responded (without waiting for reply from backups). -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Pessimistic-TXN-did-not-release-lock-on-a-key-all-subsequent-txns-failed-tp10536p13516.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Creating cache on client node in xml not working
Hi, Any cache stores should be configured on all nodes of the cluster (including client nodes) and don't support zero deployment feature. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Creating-cache-on-client-node-in-xml-not-working-tp8918p12994.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: web monitor console without gridgrain or nodejs
Hi, Please properly subscribe to the mailing list so that the community can receive email notifications for your messages. To subscribe, send empty email to user-subscr...@ignite.apache.org and follow simple instructions in the reply. Web console is part of Apache Ignite project. But Node.JS is required for running of Web Console. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/web-monitor-console-without-gridgrain-or-nodejs-tp12545p12564.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: How to execute ignite jdbc query on specific node
Hi, Please properly subscribe to the mailing list so that the community can receive email notifications for your messages. To subscribe, send empty email to user-subscr...@ignite.apache.org and follow simple instructions in the reply. If I understand your question correctly you want to execute query using key that we used previously to insert data. Am I right? If yes then you should have configured indexing using query entities [1] for required fields and use regular SQL query to request value by this key. [1] https://apacheignite.readme.io/docs/indexes#queryentity-based-configuration -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/How-to-execute-ignite-jdbc-query-on-specific-node-tp12562p12563.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Ignite Failed
Hi, Please properly subscribe to the mailing list so that the community can receive email notifications for your messages. To subscribe, send empty email to user-subscr...@ignite.apache.org and follow simple instructions in the reply. It seems that you have libraries in calsspath with incorect versions (e.g. JCache). Could you please provide more details about your use case in order to reproduce this problem? Also please check that you have correct libraries in your classpath. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-Failed-tp11071p11092.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
