er@ignite.apache.org
Subject: Re: Timeout while running checkpoint
How often the "Skipping checkpoint" message occurred in logs?
2018-02-12 10:47 GMT+03:00 Josephine Barboza
mailto:josephine.barb...@nviz.com>>:
No I haven’t overridden checkpointFreq value.
From: Vinokurov Pave
er@ignite.apache.org
Subject: Re: Timeout while running checkpoint
How often the "Skipping checkpoint" message occurred in logs?
2018-02-12 10:47 GMT+03:00 Josephine Barboza
mailto:josephine.barb...@nviz.com>>:
No I haven’t overridden checkpointFreq value.
From: Vinokurov Pave
#checkpointFreq parameter.
Have you overrided checkpointFreq config parameter?
2018-02-12 10:05 GMT+03:00 Josephine Barboza
mailto:josephine.barb...@nviz.com>>:
Hi,
I’m constantly seeing a lot of information logs after setting up a cluster in
ignite of two nodes
Skipping checkpoint (no page
Hi,
I'm constantly seeing a lot of information logs after setting up a cluster in
ignite of two nodes
Skipping checkpoint (no pages were modified) [checkpointLockWait=0ms,
checkpointLockHoldTime=1ms, reason='timeout']
Why could the process be timing out? I am using persistent store configuratio
Thanks Alexey. Additionally, I think that "Started Page memory" log statement
is a better indicator of whether the new memory size has been applied or not.
-Original Message-
From: Alexey Popov [mailto:tank2.a...@gmail.com]
Sent: Friday, January 12, 2018 8:23 PM
To: user@ignite.apache.or
Hi Alexey,
Is there any way I can check the total memory being used by the off heap cache?
I wanted to confirm if the warning is valid.
Sorry that I forgot to mention the version I am currently using. It is 2.1.
-Original Message-
From: Alexey Popov [mailto:tank2.a...@gmail.com]
Sent:
Hi,
In spite of setting a defaultMemoryPocliySize I am getting the below warning on
starting the node. Is there any other configuration required?
WARNING: No user-defined default MemoryPolicy found; system default of 1GB size
will be used.
features.
I'm not sure 2.3 can support old storage out of box, but you can try.
Also, please, note the default pagesize was changed in between 2.2 and 2.3
releases from 2048 to 4096. So, you may need to specify it explicitly in your
config.
On Thu, Jan 11, 2018 at 11:23 AM, Josephine Ba
Hi,
I am currently using version 2.1 of ignite and want to upgrade to latest
version 2.3. My application uses Ignite
Persistence(org.apache.ignite.configuration. PersistentStoreConfiguration) to
persist data. As part of upgrading to version 2.3 do I need to change this to
DataStoreConfiguratio
10:04 PM
To: user@ignite.apache.org
Subject: Re: Node unable to join cluster
Sorry, I still don't understand, why you need an AddressResolver.
Can't you specify all external IPs in configuration and don't use internal ones?
Denis
пн, 27 нояб. 2017 г. в 15:55, Jo
ou have nodes in your cluster, that are able to see each other locally? If
not, then you don't need an address resolver actually.
Denis
чт, 23 нояб. 2017 г. в 13:10, Josephine Barboza
mailto:josephine.barb...@nviz.com>>:
Hi,
Still getting this error.
2017-11-23 08:59:27 [tcp-d
tSocketAddress addr)
throws IgniteCheckedException {
return maps.get(addr);
}
}
From: Josephine Barboza
Sent: Wednesday, November 22, 2017 5:13 PM
To: user@ignite.apache.org
Subject: RE: Node unable to join cluster
Hi Denis,
After adding the localAddress in TcpDiscoverySpi, the node is s
ignite.readme.io/docs/cluster-config
Denis
вт, 21 нояб. 2017 г. в 15:11, Josephine Barboza
mailto:josephine.barb...@nviz.com>>:
Hi,
I have setup ignite instances on two different VMs and I’m trying to create a
cluster using Static IP discovery using TcpDiscoveryVmIpFinder.
I have a couple o
Hi,
I have setup ignite instances on two different VMs and I'm trying to create a
cluster using Static IP discovery using TcpDiscoveryVmIpFinder.
I have a couple of questions:
1. Do I need to give loopback address or public IP for the node to start
before trying to connect to the other node
14 matches
Mail list logo
