Default page size in Ignite 2.1 was 2048 (2K), in 2.3 it was increased to
4096 (4K). Since your storage was created on 2.1 with page size of 2K, you
need to restore with the same size. To achieve this you should explicitly
set DataStorageConfiguration#pageSize property to 2048 when starting Ignite
Can you try to reproduce the issue in a smaller project that you would be
able to share? Honestly, issue is absolutely not clear to me.
-Val
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi Slava,
Thank you for solution.
Can you please help me with following question.
I am loading the cache from oracle table using loadCache method. If the
persistence is enabled and if the data is already persisted, I want to make
sure that the cache is loaded from persisted data instead of
Hi,
First, ignite will take all space that is configured in a data region. if
there's more data then data region can store it will write data to a disk.
However, it's about off-heap memory only, it doesn't use the heap for data
storing(at least by default).
How to configure data region size you
Hi. I use UriDeploymentSpi to deploy users code and ComputeTasks.
Simple ComputeTasks work well, but in ComputeTask with IgniteStreamer I
have ClassNotFoundException.
There is users transformations code in application which should be applied
to data on each node.
So I put transform execution
Hi,
I am starting ignite node in server mode in intellij. I am starting only
one instance of it. I am using IgniteSpringBean to set configuration and
start the node as shown below. But when I enable persistence, I get
following exception.
Caused by: java.lang.IllegalStateException: Ignite is in
Hi Dmitry,
It looks like the issue you described is similar to the following
https://issues.apache.org/jira/browse/IGNITE-3935
The fix will be available in ApacheIgnite 2.4.
In meanwhile, could you please check your case with the latest code from the
master branch?
Thanks!
--
Sent from:
Hi,
We are facing an issue which causes data losing. Details are in the jira issue
which is indicated below. So how can we proceed in order to solve that
persistency problem?
Thanks,
https://issues.apache.org/jira/projects/IGNITE/issues/IGNITE-7688
Muratcan TUKSAL
Dear Apache Enthusiast,
(You’re receiving this message because you’re subscribed to a user@ or
dev@ list of one or more Apache Software Foundation projects.)
We’re pleased to announce the upcoming ApacheCon [1] in Montréal,
September 24-27. This event is all about you — the Apache project
Hi, Slava. Thanks for your answer.
Yes, it looks similar.
But I think there are some difference.
Because I use UriDeploymentSpi i assume that I will have proper classloader
in each node for my executed ComputeTask.
In future I will remove peerClassloading because I load classes in each node
by
Hi,
we use Ignite as DataGrid and want to store data in cache forever as
we, for sure, have enough RAM to fit in. These data are just
dictionaries, less than 1M recordrs each.
Our deployment for now is 3 server nodes with several caches, each
configured in "replicated:" mode, There are one
Sergey,
Pages can't be evicted unless you configure data page eviction mode (see
DataPageEvictionMode). If page eviction is disabled and you still miss
your data, the problem is caused by something else.
Regarding message in log about page eviction start: there's a ticket
about it, but
Should I decrease these? One other thing to note is im monitoring GC and the
GC times do not correlate with these issues (GC times are pretty low
anyway). I honestly think that persisting to disk somehow causes things to
freeze up. Could it be an AWS related issue? Im using EBS IO1 with 20,000
I've done some additional testing. By shutting down another (the last)
client node that was running independent code, I was able to purge the bad
version of my code from the servers, while leaving the userVersion at "0".
Apparently in this case, the client nodes are "master" nodes. (The
Hi Prasad,
The root cause of IllegalStateException you observed is that the Ignite
instance is created within IgniteSpringBean#afterSingletonsInstantiated()
method which is triggered by the Spring Framework.
So, you should not call ignite.active(true) method here:
@Bean
public IgniteSpringBean
I've started reproducing this issue with more statistics, but have not
reached the worst performance point yet, but somethings are starting to
become clearer:
The DataStreamer hashes the affinity key to partition, and then maps the
partition to a node, and fills a single buffer at a time for the
I've started reproducing this issue with more statistics, but have not
reached the worst performance point yet, but somethings are starting to
become clearer:
The DataStreamer hashes the affinity key to partition, and then maps the
partition to a node, and fills a single buffer at a time for the
Hi folks,
I was wondering what's the status of Ignite 2.4. Is there any planned
release date?
The need to support java 9 is becoming a priority.
Cheers,
Paolo
Hi Paolo,
I think that Apache Ignite will be released soon.
You can track the status and find details on the dev-list:
http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-4-release-tc26031.html
Thanks!
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
19 matches
Mail list logo
