Hi,
We have been searching for a cause of memory leak in ignite server nodes for
many weeks now.
The memory leak exists and below is the scenario.
Scenario
* Scenario
* Our ignite servers have about 50GB of data. Two servers were baselined
* There are about 10 client nodes con
Who are you trying to share in the body? Attaching smth? Try to stick to
the plain text.
-
Denis
On Tue, Feb 25, 2020 at 9:35 AM Prasad Bhalerao <
prasadbhalerao1...@gmail.com> wrote:
> my mails with body contents are not showing up in ignite user list. Sent
> the same mail multiple times but n
Ignite Dev team,
This sounds like an issue in our replicated cache implementation rather
than an expected behavior. Especially, if partitioned caches don't have
such a specificity.
Who can explain why write-through needs to be enabled for replicated caches
to reload an entry from an underlying da
Hi,
> Ignite Version: 2.6
> No of nodes: 4
>
> I am getting following exception while committing transaction.
>
> Although I just reading the value from this cache inside transaction and I
> am sure that the cache and "cache entry" read is not being modified out
> this transaction on any other no
Hi,
1) What is nodeOrder in grid cache version?
2) When does it change?
3) How does it affect transaction?
I think my transaction is failing due to this change in nodeorder.
GridCacheVersion [topVer=194120123, order=4, nodeOrder=2]
Thanks,
Prasad
my mails with body contents are not showing up in ignite user list. Sent
the same mail multiple times but no luck.
Anyone knows the issue?
On Tue, Feb 25, 2020 at 10:45 PM Rick Alexander
wrote:
> Test MAIL reply
>
> On Tue, Feb 25, 2020, 12:00 PM Prasad Bhalerao <
> prasadbhalerao1...@gmail.com>
Test MAIL reply
On Tue, Feb 25, 2020, 12:00 PM Prasad Bhalerao
wrote:
>
>
Hello!
I recommend tweaking your dependency importing to make sure you exclude all
H2 versions but the one needed by Apache Ignite.
With Maven, mvn dependency:tree to the rescue.
H2 is currently the heart of Ignite's SQL and, as such, it is not
negotiable.
Regards,
--
Ilya Kasnacheev
вт, 25
Hi,
The most useful information here is the plan that the RDBMS uses.
Is it possible to share it?
I suppose that using of either the IDX_ORG_MEDP_DRUG index or the
IDX_DRUG_ID index is not absolutely correct.
My bet is an index on (DRUG_ID, ORG_ID) could help here but it's to be
checked.
And it'
Yes I'm using spring boot. Can Ignite be updated to work with the latest
h2?
On Fri, Feb 21, 2020, 6:25 AM Ilya Kasnacheev
wrote:
> Hello!
>
> I've heard about issues with e.g. Spring Boot overriding h2 database
> version and breaking our runtime. I'm not sure who else does that.
>
> Regards,
>
Hello!
I think this is by design. You may suggest edits on readme.io.
Regards,
--
Ilya Kasnacheev
пн, 24 февр. 2020 г. в 17:28, Prasad Bhalerao :
> Hi,
>
> Is this a bug or the cache is designed to work this way?
>
> If it is as-designed, can this behavior be updated in ignite documentation?
Can you pls suggest some alternate way of generating the same in the application which Is good for Primary Key like UUID where the issue is that it is 128bit . Regards, Abhay Gupta From: Igor SapegoSent: 25 February 2020 17:37To: userSubject: Re: Sequence with ODBC There is no such option currently
There is no such option currently, AFAIK
Best Regards,
Igor
On Tue, Feb 25, 2020 at 3:02 PM Abhay Gupta wrote:
> Hi ,
>
>
>
> Do we have a way to have Autoincrement field in Database for use in Thin
> Client / UNIX ODBC . The Atomic sequence help is available with Java when
> JAVA ignite is us
Hi , Do we have a way to have Autoincrement field in Database for use in Thin Client / UNIX ODBC . The Atomic sequence help is available with Java when JAVA ignite is used but it does not tell if the same is available through thin client protocol or not . Regards, Abhay Gupta
Ignite supports persistence to disk. It’s configured using data regions. So you
could have one data region that’s entirely in memory and another that’s on
disk. We don’t call them “tiers” but that’s effectively what they allow.
> On 25 Feb 2020, at 05:57, Preet wrote:
>
> I am new to ignit
As was mentioned above IGFS was deprecated and not recommended for use.
Just use native HDFS API for working with files:
https://hadoop.apache.org/docs/stable/api/org/apache/hadoop/fs/FileSystem.html
In case if you have some SQL over HDFS (Hive, Impala) then you can set up
the Ignite cache stor
Hi,
Even I am getting the same exception with cachemode.replicated.
But my requirement is that my ignite node shouldn't wait for other nodes in
the cluster.
In our case , even when one node is down , the other should be working.So
that's why we didn't define the baseline topology.
Can you give an
18 matches
Mail list logo