Mailing-List: contact user-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@ignite.apache.org
Date: Wed, 6 Apr 2016 12:39:25 -0700 (PDT)
From: vkulichenko <valentin.kulichenko@gmail.com>
To: user@ignite.apache.org
Message-ID: <1459971565364-3981.post@n6.nabble.com>
In-Reply-To: <000801d18fca$05feb780$11fc2680$@taqniatech.com>
References: <001501d18f06$8523b2a0$8f6b17e0$@taqniatech.com>
 <1459845256132-3930.post@n6.nabble.com>
 <000801d18fca$05feb780$11fc2680$@taqniatech.com>
Subject: RE: Heap memory getting increase while doing cache.get()
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi,

Can you please attach the whole log? Most likely the node was still
suffering from GC pauses or OOM and was segmented.

Answering your questions:

1. Yes, data in partitioned cache is evenly split across nodes. But note
that there is always Ignite overhead on top of the data itself. Refer to [1]
for some details and hints. Also keep in mind that memory is managed by JVM,
so part of the heap is usually consumed by garbage which will be eventually
collected. So the reported amount of consumed memory is not always accurate.
To check this you can use any tool like VisualVM to force garbage
collection. After it's done, you will get more informative picture.
2. Client node will connect to one of the addresses provided by the IP
finder. There is no single point where all clients connect to.

-Val


--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Heap-memory-getting-increase-while-doing-cache-get-tp3925p3981.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.