Re: Re: Nodes can not join the cluster after reboot

Aaron, This Service instance after creating will be serialized and deserialized on the target nodes. So, the field of Logger will be serialized too and I don't think that it will be properly serialized with the possibility of deserialization since it holds context internally. It's not recommended

Re: Re: Nodes can not join the cluster after reboot

Hi Evgenii, I trying to remove this part and use the @LoggerResource; will have a try! thanks for your time. Regards Aaron Aaron.Kuai From: Evgenii Zhuravlev Date: 2018-01-19 16:28 To: user Subject: Re: Re: Nodes can not join the cluster after reboot Aaron, This Service instance after

Re: Re: Nodes can not join the cluster after reboot

Please let us know if this helped you Evgenii 2018-01-19 11:35 GMT+03:00 aa...@tophold.com : > Hi Evgenii, > > I trying to remove this part and use the @LoggerResource; will have a > try! thanks for your time. > > > Regards > Aaron > -- > Aaron.Kuai > > > *From:* Ev

Re: NPE from the native persistence enable node

Mikhail, I believe this NPE is already fixed as part of [1] and will be released in 2.4 version soon. I'm going to close IGNITE-7458 as duplicate with corresponding JIRA link. [1] https://issues.apache.org/jira/browse/IGNITE-6668 On Thu, Jan 18, 2018 at 3:03 AM, Mikhail wrote: > Hi Aaron, > >

index for like criteria

Hi All, My query is on substring index working for Ignite. I am using - data grid , default file system persistence enabled. Let us say, I have Organization POJO and index defined on its field as defined below: public class Organization { /** */ private static final AtomicLong ID_GEN = n

Re: Questions about SQL interface

Hello Wolfram, > 1. Duplication of table entries in sqlline (!tables) This is a known issue https://issues.apache.org/jira/browse/IGNITE-7277 This bug has been resolved in master branch and will be available in Apache Ignite 2.4. 3. Updating / Inserting via SQL fails Could you please provide SQL

Re: Node fails to recover

Hellp Ralph. I can see the frustration here, but the thing is, Ignite instance represents a database server node, and you can see how having such things in context would complicate the life cycle. You would probably want to make some wrapper that can handle such cases. I'm not sure if there are s

Re: Long activation times with Ignite persistence enabled

Hello! As far as my understanding goes, there's no distinction in Ignite between "data pages" and "index pages" All pages in durable memory are parts of "B+ tree" and are holding both data and references to downward branches in other pages. I'm not sure it had to load all the pages. Maybe only on

Re: index for like criteria

Hi Rajesh, > If I execute the following query , will the index would be applied on the > name field? Well, the answer is depended on the position of the wildcard character. For example, if filter pattern does not use the wildcard character (%) at the very beginning of the filter ("organization%")

Re: Questions about SQL interface

Hello Slava, On 19/01/2018 19:48, slava.koptilin wrote: Hello Wolfram, 1. Duplication of table entries in sqlline (!tables) This is a known issue https://issues.apache.org/jira/browse/IGNITE-7277 This bug has been resolved in master branch and will be available in Apache Ignite 2.4. I see,

Re: Data lost when primary nodes down.

Hi Denis, Thanks for your reply. > You didn't configure any backups for your cache, so, there is only one > node for every key in the cluster. In order to configure backups for cache, use CacheConfiguration.setBackups(int) method. If i have 3 nodes server, do i have to set up which is the primar

CacheWriterException: Failed to write entry to database

Hi, Some one please help me. It takes my time to figured this out. I got this error. It is happen when insert/update/delete operation. ignite-4c6985f2.log Here is my cluster configuration: IgniteConfiguration c

Re: Long activation times with Ignite persistence enabled

Hey Ilya! In fact I was talking about pre-loading the index *partitions* not pages. But in any case, it's besides the point, just a potential enhancement. What concerns me the most is how much time the activation takes and its apparent linear growth with the size of the on-disk data. In my case

Re: Cursor in TextQuery - first hasNex() is slow

Hi Val, Thank you for your response. I have created https://issues.apache.org/jira/browse/IGNITE-7482. Unfortunately, the solution does not seem to be resolvable with simple local patch - hence could not propose solution. But will try to take a closer look next week. For time being I went into di

Re: CacheWriterException: Failed to write entry to database

You should check the trace for the root cause, it will likely give your more pointers. Generally, this error just means that the cache store was not able to update your underlying database. Obviously, there are a lot of possible reasons for that. -Val -- Sent from: http://apache-ignite-users.70

Re: how to create Index for binary or byte type value

Rajesh, Whether you work with POJOs or with BinaryObject API, data is stored in the same binary format which allows to get field values without deserialization. Therefore indexing on binary data is possible. Please go through the documentation page I provided earlier, it gives more detailed descri

Re: Semaphore Stuck when no acquirers to assign permit

Igniters, Who can check out Tim’s fix for the semaphore? pull request: https://github.com/apache/ignite/pull/3138 jira: https://issues.apache.org/jira/browse/IGNITE-7090 — Denis > On Jan 15, 2018,

Re: Purpose of cache in cache.query(Create Table ...) statement

Hi Shravya, The best practice is to have a cache (and SQL table) per a business entity of your applications. So, my suggestion is not to mix different business entities in a single cache. Create your data schema as you would do for a relational database. The CREATE TABLE creates a new Ignite c

Re: usage of Apache ignite as Key value DB

> On Jan 17, 2018, at 4:30 AM, Rajesh Kishore wrote: > > Hello Mikael, > > Thanks a ton for your response. I got descent understanding that for any > operation I need to define cache and the cache item can be persisted. > - Does it mean all CRUD operations would be performed via cache operati