[jira] [Created] (IGNITE-2841) IGFS: Lock trash during file overwrite only if there is clear evidence of a conflict.

Vladimir Ozerov created IGNITE-2841: --- Summary: IGFS: Lock trash during file overwrite only if there is clear evidence of a conflict. Key: IGNITE-2841 URL: https://issues.apache.org/jira/browse/IGNITE-2841

[jira] [Created] (IGNITE-2840) Refactoring of creation of elements on cluster page to using of mixins

Vasiliy Sisko created IGNITE-2840: - Summary: Refactoring of creation of elements on cluster page to using of mixins Key: IGNITE-2840 URL: https://issues.apache.org/jira/browse/IGNITE-2840 Project: Ign

[jira] [Created] (IGNITE-2839) Working paths are hard-coded in bin/ scripts and log4j xml

knivit created IGNITE-2839: -- Summary: Working paths are hard-coded in bin/ scripts and log4j xml Key: IGNITE-2839 URL: https://issues.apache.org/jira/browse/IGNITE-2839 Project: Ignite Issue Type: B

[jira] [Created] (IGNITE-2838) IGFS: Optimize IgfsListingEntry format.

Vladimir Ozerov created IGNITE-2838: --- Summary: IGFS: Optimize IgfsListingEntry format. Key: IGNITE-2838 URL: https://issues.apache.org/jira/browse/IGNITE-2838 Project: Ignite Issue Type: Ta

[jira] [Created] (IGNITE-2837) Docker daemon doesn't start on the AWS instances

Vasilisa Sidorova created IGNITE-2837: -- Summary: Docker daemon doesn't start on the AWS instances Key: IGNITE-2837 URL: https://issues.apache.org/jira/browse/IGNITE-2837 Project: Ignite

[GitHub] ignite pull request: IGNITE-2703 .NET: Dynamic class registration ...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/555 IGNITE-2703 .NET: Dynamic class registration for non-serializable types You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignit

[GitHub] ignite pull request: IGNITE-2823: Split libcommon in two libs.

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/554 IGNITE-2823: Split libcommon in two libs. You can merge this pull request into a Git repository by running: $ git pull https://github.com/isapego/ignite ignite-2823 Alternatively you can revi

[GitHub] ignite pull request: Ignite gg 10885

GitHub user sboikov opened a pull request: https://github.com/apache/ignite/pull/553 Ignite gg 10885 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-10885 Alternatively you can review and apply t

[jira] [Created] (IGNITE-2836) IGFS: Investigate why BinaryMarshaller is slower than OptimizedMarshaller in meta operations.

Vladimir Ozerov created IGNITE-2836: --- Summary: IGFS: Investigate why BinaryMarshaller is slower than OptimizedMarshaller in meta operations. Key: IGNITE-2836 URL: https://issues.apache.org/jira/browse/IGNITE-283

BinaryObjectOffHeapImpl leaked to app code level

Igniters, To my knowledge BinaryObjectOffHeapImpl is considered to be used under some internal lock only to prevent possible offheap pointer movement. However seems that we made it available to public code. If to start a partitioned cache in OFFHEAP_TIRED mode, get BinaryObject from the cache

[jira] [Created] (IGNITE-2835) BinaryObjectOffHeapImpl leaked to public code

Denis Magda created IGNITE-2835: --- Summary: BinaryObjectOffHeapImpl leaked to public code Key: IGNITE-2835 URL: https://issues.apache.org/jira/browse/IGNITE-2835 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-2834) IGFS: Introduce optional co-location of metadata.

Vladimir Ozerov created IGNITE-2834: --- Summary: IGFS: Introduce optional co-location of metadata. Key: IGNITE-2834 URL: https://issues.apache.org/jira/browse/IGNITE-2834 Project: Ignite Issu

[jira] [Created] (IGNITE-2833) Huge memory utilization when OFFHEAP_TIERED mode and expiry policy are enabled.

Vladimir Ozerov created IGNITE-2833: --- Summary: Huge memory utilization when OFFHEAP_TIERED mode and expiry policy are enabled. Key: IGNITE-2833 URL: https://issues.apache.org/jira/browse/IGNITE-2833