[jira] [Created] (IGNITE-10852) [Documentation] - Add details on to public API behaviour

Alexander Gerus created IGNITE-10852: Summary: [Documentation] - Add details on to public API behaviour Key: IGNITE-10852 URL: https://issues.apache.org/jira/browse/IGNITE-10852 Project: Ignite

RE: REST GridCacheCommandHandler writes ERROR in log in caseofbaduser input

I think that this case is serious gap in Ignite maintainability 1. This is business as usual case and client application can create an incorrect API call. User error should be returned back to user via the same API 2. Exception in the Ignite log file should cause an alert for application

Re: Pre-touch for Ignite off-heap memory

Hi, Ivan Let me try to explain. I think that there are 2 goals that are mostly applicable for prod systems: 1. I can agree with Dave that swap is not a good case for performance and disk resource. It is possible that other applications can consume memory that is free after Ignite was started. In

Pre-touch for Ignite off-heap memory

Hi *Igniters*, Some time ago I've raised a suggestion for product improvement https://issues.apache.org/jira/browse/IGNITE-9112 . It's all about off-heap memory allocation. Current implementation can have some improvements for failure critical

[jira] [Created] (IGNITE-9495) Update version for org.apache.lucene lucene-queryparser : 5.5.2

Alexander Gerus created IGNITE-9495: --- Summary: Update version for org.apache.lucene lucene-queryparser : 5.5.2 Key: IGNITE-9495 URL: https://issues.apache.org/jira/browse/IGNITE-9495 Project

[jira] [Created] (IGNITE-9112) Pre-touch for Ignite off-heap memory

Alexander Gerus created IGNITE-9112: --- Summary: Pre-touch for Ignite off-heap memory Key: IGNITE-9112 URL: https://issues.apache.org/jira/browse/IGNITE-9112 Project: Ignite Issue Type: New