Best practise for setting Ignite.Active to true when using persistence layer in Ignite 2.1

Hi, I am experimenting with a POC looking into using the Ignite persistence layer. One aspect of this is setting the grid to be ‘Active’ after all cache grid nodes have instantiated. In practical terms, what is the best practice for ensuring the cluster is running and in a good state to

Accessing array elements within items cached in Ignite without deserialising the entire item

Hi, I’ve been looking at IBinarizable and IBinarySerializer with regards to controlling object serialization (using the Ignite.Net client). A couple of questions: 1. Some of the APIs in IBinarizable allow for a factory methods to control construction of collection and dictionary

Webinar: Building Consistent and Highly Available Distributed Systems with Apache Ignite

Igniters, This Wednesday (August 2nd at 11am PT), I will host a webinar where I will go through different Apache Ignite features and capabilities that allow to build consistent and highly available distributed systems. More information here:

Re: Data loss validation. TopologyValidator

/Scenario : If there are multiple node failures occurred at the same time and ignite loses primary and as well as backup copies of partitions and how to know if this happened and data is lost? Once you detect the data loss, how to restrict/reject clients and because the cache is partial and

Re: [ANNOUNCE] Apache Ignite 2.1.0 Released

I apologize if this is documented somewhere, but I am having trouble building the new 2.1 release from source. Suggestions on switches, environment, etc are appreciated. I see the following: [INFO] ignite-appserver-test .. SUCCESS [ 0.166 s] [INFO]

Re: About Apache Ignite in Japanese

Thanks, Nikita! I often use Google Translate — love it! Denis, yes, I could translate the blog from Japanese using Google Translate to speed things up — and my wife (who is Japanese … from Tokyo) can proof-read it for me and make it perfect. I speak Japanese much better than I can read/write.

Re: bugreport: logger

Thanks, i agree, but i still think it is undesired behaviour i.e. a undesired side effect. G. Simon On 31-07-17 15:36, Nikolai Tikhonov wrote: Hello! Thank you for your feedback. IgniteJdbcDriver tries to find a there /config/java.util.logging.properties/ by default or get path to

Re: Cache refresh because of hibernate versioning mechanism.

Hi, Thanks for your response. Hibernate dao return object with new version. Version is used for optimistic locking mechanism. So we have hibernate dao -s and hibernate data model ( *.hbm.xml files). We want to avoid (if possible) completely rewrite this code. Another issue will be in our data

Re: bugreport: logger

Hello! Thank you for your feedback. IgniteJdbcDriver tries to find a there *config/java.util.logging.properties* by default or get path to configuration file by *java.util.logging.config.file* system property. And only if both a tries are failed, Ignite Jdbc Driver will configure JUL. On Sun,

Re: Create and query a binary cache in ignite

Hi James, Could you share your code as simple maven project? It would be great and allows to us help you quickly. On Mon, Jul 31, 2017 at 9:43 AM, James Isaac wrote: > > Hi, > > I am trying to use BinaryObjects to create the cache at runtime. For > example, instead of

Re: Error : Commit produced a runtime exception

No I have not set any memory configuration -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Error-Commit-produced-a-runtime-exception-tp15768p15824.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: most of the dat in mbeans in empty

Sorry, I missed it. It's known behaviour. Count of operation (put/remove and etc) updated on data nodes (node which really stored data) but time of operation is counted on client node (node which perform this operation). We have plan to make this more clear and intuitive. You can track status of

Re: Error : Commit produced a runtime exception

Did you configure IgniteConfiguration#setMemoryConfiguration? On Mon, Jul 31, 2017 at 3:18 PM, iostream wrote: > I have already shared the cache configuration in my post above. Reposting > below- > > Cache configuration :- > cacheConfig.setAtomicityMode(TRANSACTIONAL); >

Re: [ANNOUNCE] Apache Ignite 2.1.0 Released

Blog post on new .NET features: https://ptupitsyn.github.io/Whats-New-In-Ignite-Net-2.1/ On Fri, Jul 28, 2017 at 12:58 AM, Denis Magda wrote: > The Apache Ignite Community is pleased to announce the release of Apache > Ignite 2.1.0 [1]. >