missing website info

I have been going through the Ignite website today, and I have noticed that nowhere on the website we mention various modes on how Ignite native persistence can be used: - no disk, data is in memory-only (potentially over a 3rd-party database) - disk is a copy of the memory (only for recovery

memory-only mode for Ignite indexes

Igniters, One of the main complaints I hear from users is that whenever the persistence is turned on, index creation can really slow down the performance, because of massive amounts of writes to disk. The reason Ignite is writing indexes to disk is to support fast restarts - nothing needs to be

Re: IEP-19: Optimize SQL indexes

I think any ticket that results in less work being done is important, even if it's small, because the accumulation of these savings can have significant impact. I can't comment on how a lot of these may impact users like myself, but I'd like to echo that this is indeed a severe pain point that I

Re: IEP-4, Phase 2. Using BL(A)T for in-memory caches.

I do not like the name "current" on the methods. I think we should just remove it, e.g. currentAffinityTopology() -> affinityTopology() D. On Fri, May 4, 2018 at 6:17 AM, Eduard Shangareev < eduard.shangar...@gmail.com> wrote: > Igniters, > > With Vladimir's help, we analyzed another solution's

[GitHub] ignite pull request #3932: IGNITE-8413: Fixed CacheGroupMetricsMBeanTest.tes...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3932 ---

[jira] [Created] (IGNITE-8441) Java 9 (Stage II)

Peter Ivanov created IGNITE-8441: Summary: Java 9 (Stage II) Key: IGNITE-8441 URL: https://issues.apache.org/jira/browse/IGNITE-8441 Project: Ignite Issue Type: Improvement

[jira] [Created] (IGNITE-8440) Transaction may hangs on node in PREPARED state

Vladislav Pyatkov created IGNITE-8440: - Summary: Transaction may hangs on node in PREPARED state Key: IGNITE-8440 URL: https://issues.apache.org/jira/browse/IGNITE-8440 Project: Ignite

[GitHub] ignite pull request #3659: IGNITE-7986: GridPartitionStateMap.entrySet() opt...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3659 ---

Re: Apache Ignite 2.5 release

I did not understand process. Is it required to receive someone reply that issue is agreed to be included into release? Or because there is no response I can cherry-pick anything to 2.5 hoping it is lazy consensus; no one objected. пт, 4 мая 2018 г. в 17:44, Denis Magda : >

Re: Apache Ignite 2.5 release

Igniters, I got lost. Were all the bugs reported in this thread fixed and merged into 2.5 branch? Is there any bug which fix is still in progress? Just want to know when the QA and bugs fixing stage is over. -- Denis On Thu, May 3, 2018 at 9:14 AM, Dmitry Pavlov wrote:

[jira] [Created] (IGNITE-8439) IGNITE_JETTY_HOST doesn't work (never has probably)

Paul Anderson created IGNITE-8439: - Summary: IGNITE_JETTY_HOST doesn't work (never has probably) Key: IGNITE-8439 URL: https://issues.apache.org/jira/browse/IGNITE-8439 Project: Ignite Issue

Re: Ticket review checklist

Hi Dmitry, Yes, I'll do that in the nearest days. On Wed, Apr 25, 2018 at 8:24 PM, Dmitry Pavlov wrote: > Igniters, the idea was related to small refactorings co-located with main > change. > > Main change itself indicates that existing code did not meet the criteria >

Re: IEP-4, Phase 2. Using BL(A)T for in-memory caches.

Igniters, With Vladimir's help, we analyzed another solution's approaches. And decided to simplify our affinity topology auto-adjusting. It should be enough to be able to turn on/off auto-adjusting (flag) and set 2 timeouts if it is working: -soft timeout which would be used if there was no

Re: stopAllGrids() used by default and further steps

Dmitry, Task of migration to JUnit 4/5 sounds very interesting for me, but I'm not sure that I will have time for it in the next few weeks. Anyway let's create new task to it e.g. "providing design and analisys for migration to JUnit 4/5". I'll try to help with it! Test cases

Re: Replace Cron4J with Quartz for ignite-schedule module.

Folks, How can it be at PATCH AVAILABLE since *none* of my latest comments (made Feb 8) are resolved at Upsource? Changed state to IP. пн, 23 апр. 2018 г. в 20:00, Dmitry Pavlov : > Hi Andrey, > > Could you please pick up review? > > Sincerely, > Dmitriy Pavlov > > пн, 23

[GitHub] ignite pull request #3939: New implementation of getChildren method is added...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3939 ---

[GitHub] ignite pull request #3851: IGNITE-5994: IgniteInternalCache.invokeAsync().ge...

Github user SharplEr closed the pull request at: https://github.com/apache/ignite/pull/3851 ---

[GitHub] ignite pull request #3130: IGNITE-6565: Use long type for size and keySize i...

Github user SharplEr closed the pull request at: https://github.com/apache/ignite/pull/3130 ---

[jira] [Created] (IGNITE-8438) Change boxed types to primitives in Transactions.TransactionMXBeanImpl.getActiveTransactions operation

Dmitry Sherstobitov created IGNITE-8438: --- Summary: Change boxed types to primitives in Transactions.TransactionMXBeanImpl.getActiveTransactions operation Key: IGNITE-8438 URL:

Re: stopAllGrids() used by default and further steps

Hi Maxim, I think next step can be creation of Junit4/5 IgniteAbstractTest and/or IgniteTestRunner. Would you like to contribute this prototype? Regarding TC run there is a number of suspicious tests (e.g. IgnitePdsNativeIoTestSuite2:

Re: Looks like a bug in ServerImpl.joinTopology()

Alex, I checked reproducer you presented, please fix it according to the following rules 1) Never use System.out.println() as a part of reproducer, use assetrions if necessary. 2) Reproducer should be small. As small as possible. 3) Try to make reproducer clear. As crear as possible. In case

[GitHub] ignite pull request #2180: IGNITE-5567

Github user SharplEr closed the pull request at: https://github.com/apache/ignite/pull/2180 ---

[GitHub] ignite pull request #1676: IGNITE-4501: Improvement of connection in a clust...

Github user SharplEr closed the pull request at: https://github.com/apache/ignite/pull/1676 ---

[GitHub] ignite pull request #1527: IGNITE-817 Remove GridCacheOffHeapTest

Github user SharplEr closed the pull request at: https://github.com/apache/ignite/pull/1527 ---

[GitHub] ignite pull request #1466: IGNITE-4612

Github user SharplEr closed the pull request at: https://github.com/apache/ignite/pull/1466 ---

[GitHub] ignite pull request #1537: IGNITE-1948

Github user SharplEr closed the pull request at: https://github.com/apache/ignite/pull/1537 ---

[GitHub] ignite pull request #1539: IGNITE-1624 [not ready, just for testing]

Github user SharplEr closed the pull request at: https://github.com/apache/ignite/pull/1539 ---

[GitHub] ignite pull request #3834: IGNITE-7640 done

Github user SharplEr closed the pull request at: https://github.com/apache/ignite/pull/3834 ---

[jira] [Created] (IGNITE-8437) Control utility fails to connect to cluster if zookeeper discovery used

Dmitry Sherstobitov created IGNITE-8437: --- Summary: Control utility fails to connect to cluster if zookeeper discovery used Key: IGNITE-8437 URL: https://issues.apache.org/jira/browse/IGNITE-8437

[jira] [Created] (IGNITE-8436) Executor service for services does not shutdown properly

Maxim Muzafarov created IGNITE-8436: --- Summary: Executor service for services does not shutdown properly Key: IGNITE-8436 URL: https://issues.apache.org/jira/browse/IGNITE-8436 Project: Ignite

stopAllGrids() used by default and further steps

Igniters, Recenly, we've pached Ingite testing framework to stop all started instances after all test-cases completion by default. Details of impelemtaion can be viewed here [1]. This change leads us to a lot of boilerplate code. 1) I've created issue [2] and prepared PR [3] which removes all

[GitHub] ignite pull request #3944: IGNITE-8435 StorageException is handled like Node...

GitHub user akalash opened a pull request: https://github.com/apache/ignite/pull/3944 IGNITE-8435 StorageException is handled like NodeStoppingException du… …ring failing transaction commit You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-8435) Inconsistent data after StopNodeFailureHandler handles process termination

Anton Kalashnikov created IGNITE-8435: - Summary: Inconsistent data after StopNodeFailureHandler handles process termination Key: IGNITE-8435 URL: https://issues.apache.org/jira/browse/IGNITE-8435

[jira] [Created] (IGNITE-8434) .NET: Service proxies do not work on .NET Core

Pavel Tupitsyn created IGNITE-8434: -- Summary: .NET: Service proxies do not work on .NET Core Key: IGNITE-8434 URL: https://issues.apache.org/jira/browse/IGNITE-8434 Project: Ignite Issue