Re: get api takes more time when adding more nodes to cluster

application will start another node in client mode on the same JVM? That does not to look right. We don’t want to separate out these functionalities into different applications/JVM. I can make read heavy caches to be replicated. That will improve get operations on those caches. Ill try that out. -Biren

Re: get api takes more time when adding more nodes to cluster

initialize distributed caches and load data from persistent store. Then the application reads from and writes to caches. -Biren On 11/29/17, 3:52 PM, "vkulichenko" wrote: Biren, That's a wrong expectation because local in-memory read is drastically faster than a netwo

Re: get api takes more time when adding more nodes to cluster

data points every minute. But when I add 2 more nodes to the cluster the throughput reduces to 400K data point. Expectation is that with total 4 nodes we should be able to process more data point. -Biren On 11/29/17, 2:52 PM, "vkulichenko" wrote: Hi Biren, Are you doing

get api takes more time when adding more nodes to cluster

cores. Thanks, Biren Shah

Re: Cache size changes unexpectedly

that the average time is always going up. Either the each get/put call is getting slower by time or the metric is not collected correctly. -Biren From: Denis Mekhanikov Reply-To: "user@ignite.apache.org" Date: Tuesday, November 28, 2017 at 5:12 AM To: "user@ignite.apache.org"

Re: Cache size changes unexpectedly

Hi Denis, Thank you for confirming the issue. Is there any other way to calculate cache size? Also, how accurate are the other cache metrics like getAverageGetTime/getAveragePutTime? Do they provide average get time for entire cluster or just local node? -Biren From: Denis Mekhanikov Reply

Re: Cache size changes unexpectedly

Hi Denis, We are using CacheMetrics.getKeySize api to get size of a cache. Does this api give cache size of entire cache or just the size of the partitions local to the node? -Biren From: Denis Mekhanikov Reply-To: "user@ignite.apache.org" Date: Wednesday, November 22, 2017 at

Cache size changes unexpectedly

(false); cacheConfig.setWriteSynchronizationMode(CacheWriteSynchronizationMode.FULL_SYNC); cacheConfig.setStatisticsEnabled(true); -Biren

Adding user attribute after node has started

Hi, 1) Can we add/update user attribute after the node has started? 2) If we want to run jobs using compute or start a cache on specific nodes in the cluster then how can we do that? -Biren -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: getAverageGetTime/getAveragePutTime APIs of CacheMetrics always return 0

Thank you Pavel!!. I have not enabled statistics. Do you know what would be performance impact on enabling it? -Biren -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

getAverageGetTime/getAveragePutTime APIs of CacheMetrics always return 0

. Is this a bug or are we looking at wrong metric? -Biren -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite node not stopping after segmentation

or things we should watch out when using ignite? Thanks, Biren From: Mikhail Cherkasov Reply-To: "user@ignite.apache.org" Date: Sunday, September 10, 2017 at 10:27 AM To: "user@ignite.apache.org" Subject: Re: Ignite node not stopping after segmentation Biren, could you

Re: Ignite node not stopping after segmentation

We are on 2.0. Thanks, Biren On 9/8/17, 9:51 AM, "Mikhail" wrote: Hi all, I created a ticket for further investigations: https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_IGNITE-2D6323&

Re: Cluster segmentation

Hi Val, Did you get a chance to look at the code snippet I shared? If I understand correctly then when I do get() on cache, it creates a copy of the value and return that copy. Do you think turning off that behavior will help? Thanks, Biren On 8/24/17, 2:16 PM, "vkulichenko&qu

Re: Cluster segmentation

ly I was creating a key with some properties of RawPoint. Now I have added the affinity key to RawPoint. Reducing the number of objects I was creating. Thanks, Biren On 8/24/17, 2:16 PM, "vkulichenko" wrote: Biren, Can you show the code of the recei

Re: Cluster segmentation

that and running the test now. Also If I understand correctly then when I do get() on cache, it creates a copy of the object and return that copy. Do you think turning off that behavior will help? Thanks, Biren On 8/23/17, 5:51 PM, "vkulichenko" wrote: Biren, I see th

Re: Cluster segmentation

I faced was that once one of the node gets segmented, the other node dies. The reason it dies is because heap usage jumped on the other node instantly. It jumped from 4GM to 11 GB. Very strange. Any idea what could cause this? Thanks, Biren On 8/21/17, 6:53 PM, "vkulichenko" wrot

Cluster segmentation

stop another component 08/19/17 10:40:28 : dependent component stops 08/19/17 10:40:28 : received node failed event. The event was caused by application 1. 08/19/17 10:40:10 : Topology snapshot [ver=3, servers=1, clients=0, CPUs=32, heap=14.0GB] Thanks, Biren -- View this message in context

Re: Server node fails to start with exception IllegalThreadStateException

Well when i look at active threads after i stop the node, i don't see any active thread which was started by ignite. But i do see threads started by Ignite in finished threads list on yourkit. I think that is fine. When i try to start again, i get the IllegalThreadStateException exception. Here

Server node fails to start with exception IllegalThreadStateException

Hi, I am trying to embed Ignite server node into my application. I want to integration ignite such that i can start/stop ignite node at anytime while application is running. For that i have application level APIs to start or stop the ignite node. For most part the ignite node start and stops witho