Re: Unassigned issue IGNITE-12174
Thank you for the reply. Quoting Alexei Scherbakov : Lucene and spatial indexes do not support persistence. This is known limitation which would probably be addressed in the future releases. I think this limitation should at least be mentioned in the documentation then: https://apacheignite-sql.readme.io/docs/geospatial-support It would be even better to handle this unsupported use case in the code as well instead of throwing a NullPointerException. I can add this check as improvement to the Ignite code if this is wanted and agreed. But I need a hint on what would be the right place to add this check in the code base. Thanks, Jan
Unassigned issue IGNITE-12174
Hi, I have opened a bug issue some time ago about a NullPointerException thrown if geospatial indexing is used together with durable memory: https://issues.apache.org/jira/browse/IGNITE-12174 Even though I provided a minimal reproducing code example the issue was not assigned or reviewed to confirm whether we have a bug here or whether I did something wrong putting together my Ignite config. I tried to find the root cause by myself but got lost in the Ignite code base that is still mostly unknown to me. ;-) Can you please tell me what I can do to get the bug reviewed/confirmed/fixed? The bug could also be relevant for the upcoming 2.8 release. Thank you very much, Jan
[jira] [Created] (IGNITE-11823) Client Heap Memory in Cluser
Venkatesh D J created IGNITE-11823: -- Summary: Client Heap Memory in Cluser Key: IGNITE-11823 URL: https://issues.apache.org/jira/browse/IGNITE-11823 Project: Ignite Issue Type: Test Reporter: Venkatesh D J Hello, I've created a cluster with four server nodes(12GB memory each)of 48GB memory with 1GB heap. It contains only one Cache(Partitioned) with a single back and created a client node with 14GB heap size. When i tried to fill the cache fully, i noticed that the server nodes started to crash due to out of memory when it reaches around 33-35GB. Server nodes are crashed even when it has 13-15GB free space was left. Is the crashed occurred due to the heap size of the client node? Can you please clarify it? Please let me know in case of any additional details. Thanks in Advance Regards, Venkatesh D J -- This message was sent by Atlassian JIRA (v7.6.3#76005)
