[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 Issue Type: Improvement Components: documentation Affects Versions: 2.7, 2.6, 2.5, 2.4 Reporter: Alexander Gerus Current public API documentation has some specification gaps. In case if method was not successfully executed, it is not clear what should be done by user code. Good practice is to describe all API exceptions that can be processed by user code and recommended actions -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[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: Ignite Issue Type: Improvement Affects Versions: 2.6, 2.5, 2.4 Reporter: Alexander Gerus Update version for org.apache.lucene Current version: lucene-queryparser : 5.5.2 New version version: later than 7.1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[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 Feature
Affects Versions: 2.6, 2.5, 2.4
Reporter: Alexander Gerus
At the moment Ignite off-heap memory is allocated in virtual memory of
operating system, not physical memory: it is recorded in an internal data
structure to avoid it being used by any other process. Not even a single page
will be allocated in physical memory until it's actually accessed. When the
Ignite needs memory, the operating system will allocate pages as needed.
The proposal is to add an option to Ignite that will touch every single byte of
the max off heap with a '0', resulting in the memory being allocated in the
physical memory in addition to being reserved in the internal data structure
(virtual memory). Similar option is available in JVM {{-XX:+AlwaysPreTouch}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
