Hi,
I am sure there are memory leaks. See below.
Class Name
| Objects
| Shallow Heap | Retained Heap
Hey, thanks. That was exactly the problem. The communication port was
obscured.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Ignite-in-Docker-tp10120p10185.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Hi Sam,
You can pass path as query param to get the log details. Please see this
jira ticket below for reference.
https://issues.apache.org/jira/browse/IGNITE-944
Regards
Saikat
On Thu, Jan 19, 2017 at 2:21 PM, javastuff@gmail.com <
javastuff@gmail.com> wrote:
> Hi,
>
> I find LOG comm
Hello Sam,
Due to security reason the log file need to be chrooted to IGNITE_HOME/log.
Please review this PR for the fix.
https://github.com/apache/ignite/pull/420
Regards,
Saikat
On Sun, Jan 22, 2017 at 12:03 PM, Saikat Maitra
wrote:
> Hi Sam,
>
> You can pass path as query param to get th
I was getting the errors while starting the cluster and there is no data in
the cache.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Timed-out-waiting-for-message-delivery-receipt-tp10171p10188.html
Sent from the Apache Ignite Users mailing list archive at Nabb
One more thing which I have noticed - First I have started 4 servers and they
were able to form a cluster of 4 nodes. But when I have started 1 client
then only 2 servers were able to communicate with the client. And other were
not able to communicate with client
Below were the messages on the ser
Hi,
My application run overnight and crash again after I set max heap as 2G. For I
saw there were many Future Objects,
I guess it may be caused by Async API. Now I am using Sync API. It seems that
the memory issue disappeared.
My application memory kept at 60M.
cache = cache.withAsync
Hi Denis,
I think I've found the issue.
Ignite skips references to Ignite-Caches.
Moving away from the Ignite-Cache, but using the Ignite-Marshaller caused
the issue.
So it isn't an issue Ignite can prevent. Removing those references did it.
Thanks for listening,
Peter
2017-01-22 6:15 GMT+01:0
