Thanks. I understand relying on user to determine if data is upto date
when Ignite is used as a cache. With native persistence, Ignite is the
source of the data. If some partitions become unavailable, there's no way
for data to become outdated. Feels like there should be a configuration
Hi,
It is totally ok if some WAL segment causes such exception in case of the
end of a file was reached.
Messages may disappear because some newer version has special records
showing the end of a segment, so WAL reader almost always knows that the
end of file reached.
Sincerely,
Dmitriy Pavlov
Hi all,
I'd like to understand how to determine that a continuous query (CQ) needs
to be re-created, in case of multiple server restarts.
My understanding for the following case is:
if an ignite client joins a cluster (composed by server-A only) and deploys
a CQ to the cluster, server-A will
version 2.6
i have a tool that creates ignite tables and it is passing in a class with
the type as decimal but it is coming out as double in when i query the
metadata using rest in ignite? The documentation explicitly states c#
decimal converts to java.math.bigdecimal which is not a floating
I'm not an architect of this feature, but the explanation could be quite
simple: data stored in lost partitions could have become outdated while
nodes containing data were out of the cluster, so it's up to user to decide
whether the restored data is OK, or not.
--
Sent from:
Little correction:
The actual value we have in production for the eviction policy is as
follows(500MB)
evpl.setMaxMemorySize(524288000);
-Original Message-
From: HEWA WIDANA GAMAGE, SUBASH [mailto:subash.hewawidanagam...@fmr.com]
Sent: Wednesday, October 03, 2018 10:47 PM
To:
Hi.
It might be the case of improperly activated cluster. You can check which
nodes are in the base topology by using a command
./control.sh --baseline
Here https://apacheignite.readme.io/docs/baseline-topology you can read more
about it.
Hope it will help.
--
Sent from:
Hi, it looks strange to me. Do you have a reproducer?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi Raymond,
No archiver mode means there is no cyclic enumeration of files in the work
directory, enumeration of segments is plain and absolute instead.
And all walHistSize rules applied to default mode applies to no-archiver
mode, as well. So there is not possible to lose any data, and no
Hi,
We are using Ignite as persistent store in Partitioned Mode having 6 cluster
node running, each node is running on different machine.
We started with Ignite-2.1 then upgrade to Ignite-2.3 in Feb-18. Recently we
have upgraded from Ignite 2.3 to Ignite 2.5, but we are seeing one issue
related
Hello,
I would like to enable partition aware data loading. I do have a composite
business key in the database (Oracle and SQL Server) that happen to be the
key of the object in the key. The most important part of that key is a
string
I can very easily compute a good affinity from that key, the
Hi,
Is there a way in ignite to know if the original value in DB has been
updated so as to refresh it in cache that has persistence enabled?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Andrey,
Other types will have lazy initialization, it's a default behavior.
Evgenii
вт, 2 окт. 2018 г. в 18:02, Andrey Davydov :
> Will binary serialization work for all other classes not listed in
> typeConfiguration?
>
>
>
> Andrey.
>
>
>
> *От: *Evgenii Zhuravlev
> *Отправлено: *2 октября
Hi,
According to the last logs, this is a different issue.
2018-09-28T05:25:03.598Z [RxComputationThreadPool-1]/W: Get: batch { keys: 1
} failed, retrying.
java.util.concurrent.TimeoutException
at
14 matches
Mail list logo