[GitHub] ignite pull request #3000: ignite-6767: reset of the topVer on loading of th...

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

Should we enable write throttling by default?

Igniters, I finished documenting pages write throttling and checkpointing buffers adjustment sections under the performance notes: https://apacheignite.readme.io/docs/durable-memory-tuning#section-pages-writes-throttling

[jira] [Created] (IGNITE-6924) CacheStoreSessionListener#onSessionStart() is not called in case of 'WriteBehind' mode is enabled and 'writeCache' size exceeds critical size.

Vyacheslav Koptilin created IGNITE-6924: --- Summary: CacheStoreSessionListener#onSessionStart() is not called in case of 'WriteBehind' mode is enabled and 'writeCache' size exceeds critical size. Key: IGNITE-6924

Re: Should we enable write throttling by default?

Thanks Denis, looks very nice! Igniters, let's stop asking users to enable flags in order for the system to behave properly. All such flags should be enabled by default. D. On Wed, Nov 15, 2017 at 11:26 AM, Denis Magda wrote: > Igniters, > > I finished documenting pages

[GitHub] ignite pull request #3040: ignite-6924: Fixed missed CacheStoreSessionListen...

GitHub user sk0x50 opened a pull request: https://github.com/apache/ignite/pull/3040 ignite-6924: Fixed missed CacheStoreSessionListener#onSessionStart() call CacheStoreSessionListener#onSessionStart() is not called in case of 'WriteBehind' mode is enabled and 'writeCache' size

[jira] [Created] (IGNITE-6917) SQL: implement COP command for efficient data loading

Vladimir Ozerov created IGNITE-6917: --- Summary: SQL: implement COP command for efficient data loading Key: IGNITE-6917 URL: https://issues.apache.org/jira/browse/IGNITE-6917 Project: Ignite

[jira] [Created] (IGNITE-6918) SQL: support window functions

Vladimir Ozerov created IGNITE-6918: --- Summary: SQL: support window functions Key: IGNITE-6918 URL: https://issues.apache.org/jira/browse/IGNITE-6918 Project: Ignite Issue Type: New Feature

Re: Ignite Enhancement Proposal #6 (Metrics)

Dima, This appears to be a INFRA's bug. I filed a ticket [1]. [1] https://issues.apache.org/jira/browse/INFRA-15487 On Tue, Nov 14, 2017 at 9:25 PM, Dmitriy Setrakyan wrote: > On Tue, Nov 14, 2017 at 10:12 AM, Anton Vinogradov < > avinogra...@gridgain.com > > wrote: > >

[jira] [Created] (IGNITE-6916) A node joining with enabled persistence and empty disc space causes exchange to hang.

Stanilovsky Evgeny created IGNITE-6916: -- Summary: A node joining with enabled persistence and empty disc space causes exchange to hang. Key: IGNITE-6916 URL: https://issues.apache.org/jira/browse/IGNITE-6916

[GitHub] ignite pull request #3036: IGNITE-6916: node joining with enabled pds and em...

GitHub user zstan opened a pull request: https://github.com/apache/ignite/pull/3036 IGNITE-6916: node joining with enabled pds and empty disc space cause… …s exchange to hang You can merge this pull request into a Git repository by running: $ git pull

Re: Request for Contributers permission

Hello Turik, Done! Some extra info that might be useful for you. Get familiar with Ignite development process described here: https://cwiki.apache.org/confluence/display/IGNITE/Development+Process Instructions on how to contribute can be found here:

Re: Request for contributors permissions

Hi Michael, Ready! Done! Some extra info that might be useful for you. Get familiar with Ignite development process described here: https://cwiki.apache.org/confluence/display/IGNITE/Development+Process Instructions on how to contribute can be found here:

Re: request for contributors permissions

Hello Denis, Seems that someone has already given your the permission and forgot to reply here. — Denis > On Nov 15, 2017, at 4:08 AM, Denis Loginov wrote: > > Hello! > > I want to resolve bugs using my account: da.loginov > Please, provide me with necessary

[jira] [Created] (IGNITE-6925) Simplify cache metrics activation

Denis Magda created IGNITE-6925: --- Summary: Simplify cache metrics activation Key: IGNITE-6925 URL: https://issues.apache.org/jira/browse/IGNITE-6925 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-6927) Web Console: Create build with maven for Web Console direct-install.

Andrey Novikov created IGNITE-6927: -- Summary: Web Console: Create build with maven for Web Console direct-install. Key: IGNITE-6927 URL: https://issues.apache.org/jira/browse/IGNITE-6927 Project:

Re: Ignite Enhancement Proposal #6 (Metrics)

Ok, closed the previously existed as a duplicate and add another usability issue to fix in the scope of this IEP: https://issues.apache.org/jira/browse/IGNITE-6925 — Denis > On Nov 15, 2017, at 9:21 AM, Anton Vinogradov

[jira] [Created] (IGNITE-6926) Web console: SimpleWorkerPool select wrong worker in special case

Alexey Kuznetsov created IGNITE-6926: Summary: Web console: SimpleWorkerPool select wrong worker in special case Key: IGNITE-6926 URL: https://issues.apache.org/jira/browse/IGNITE-6926 Project:

Re: Why isn't Apache Ignite on stackshare.io

Interesting source. Will look into it in a couple of days. Thanks for sharing. — Denis > On Nov 15, 2017, at 8:23 AM, Dmitriy Setrakyan wrote: > > Hi Jason, great point! > > Denis, what do you think? Here is a link to how you can add Ignite to the > Stackshare: >

Re: Should we enable write throttling by default?

AFAIK throttling may decrease peak throughput. Alex, Ivan, Is it correct? On Thu, Nov 16, 2017 at 1:12 AM, Dmitriy Setrakyan wrote: > Thanks Denis, looks very nice! > > Igniters, let's stop asking users to enable flags in order for the system > to behave properly. All

Re: Should we enable write throttling by default?

Yes, it is correct. But still, right after implementation I was for enabling this mode by detault. - It is not simple to explain need to enable this feature to each user. - Moreover write freezing after peak load may be considered by some Ignite users as bug. Not all of them will write to user

[jira] [Created] (IGNITE-6920) Web console: Prepare Web Console package with simple deploy.

Andrey Novikov created IGNITE-6920: -- Summary: Web console: Prepare Web Console package with simple deploy. Key: IGNITE-6920 URL: https://issues.apache.org/jira/browse/IGNITE-6920 Project: Ignite

Re: Add emergency node closing handler to public Ignite API

AFAIK the idea was not only to shutdown the node, but also to give user (e.g. administrator) ability to observe the problem from the outside, e.g. through JMX. E.g. if we detect Java-level deadlock, it doesn't mean that the only possible solution is node shutdown. In addition it could be no-op,

[GitHub] ignite pull request #3015: IGNITE-6836: Implemented query timeout.

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

Request for contributors permissions

Hello! I want to resolve bugs. Please, grant me permission for assign tasks in jira. My jira account MikeZhur. Regards, Mike Zhuravlev

Why isn't Apache Ignite on stackshare.io

Just curious, why isn't Apache Ignite on Stackshare.io? Stackshare.io is really picking up in momentum as a developer community for sharing what stacks are used and where. Could be useful in promoting usage in the open-source community. I can see that Hazelcast is:

[jira] [Created] (IGNITE-6919) Web console: incorrect character in tab name under IE11

Pavel Konstantinov created IGNITE-6919: -- Summary: Web console: incorrect character in tab name under IE11 Key: IGNITE-6919 URL: https://issues.apache.org/jira/browse/IGNITE-6919 Project: Ignite

Re: Add emergency node closing handler to public Ignite API

Vladimir, Could you please refine, what are local metrics? Should I extend Ignite interface by adding something similar to dataRegionMetrics() or there is some universal mechanism to handle metrics? 2017-11-15 8:30 GMT+03:00 Vladimir Ozerov : > > This information should be

Re: Add emergency node closing handler to public Ignite API

Vova, Currently we have a lot IEPs to improve grid monitoring and behavior. Let's split tasks to: 1) Graceful shutdown. In this case we'd like to provide user ability to do something, LifecycleBean is what we looking for, thanks for tips! But, we have to keep shutdown reason somewhere. In case

Re: Add emergency node closing handler to public Ignite API

I am not quite I understand how tasks are split. How can we discuss graceful shutdown without discussing the reasons of this shutdown? What leads to it? On Wed, Nov 15, 2017 at 2:10 PM, Anton Vinogradov wrote: > Vova, > > Currently we have a lot IEPs to improve grid

Re: Add emergency node closing handler to public Ignite API

Vova, Could you point to metric you're talking about? On Wed, Nov 15, 2017 at 1:06 PM, Andrey Kuznetsov wrote: > Vladimir, > > Could you please refine, what are local metrics? Should I extend Ignite > interface by adding something similar to dataRegionMetrics() or there is >

[GitHub] ignite pull request #2745: Ignite 1.8.12

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

[jira] [Created] (IGNITE-6921) Optimise tx/queries tracking when mvcc is enabled and local caches are used

Igor Seliverstov created IGNITE-6921: Summary: Optimise tx/queries tracking when mvcc is enabled and local caches are used Key: IGNITE-6921 URL: https://issues.apache.org/jira/browse/IGNITE-6921

Re: Add emergency node closing handler to public Ignite API

According to [1] Reasons are: - IgniteOutOfMemoryException - Persistence errors - ExchangeWorker exits with error [1] https://cwiki.apache.org/confluence/display/IGNITE/IEP-7%3A+Ignite+internal+problems+detection On Wed, Nov 15, 2017 at 2:24 PM, Vladimir Ozerov wrote: >

[jira] [Created] (IGNITE-6923) Cache metrics are updated in timeout-worker potentially delaying critical code execution due to current implementation issues.

Alexei Scherbakov created IGNITE-6923: - Summary: Cache metrics are updated in timeout-worker potentially delaying critical code execution due to current implementation issues. Key: IGNITE-6923 URL:

[jira] [Created] (IGNITE-6922) Class can not undeploy from grid in some specific cases

Vladislav Pyatkov created IGNITE-6922: - Summary: Class can not undeploy from grid in some specific cases Key: IGNITE-6922 URL: https://issues.apache.org/jira/browse/IGNITE-6922 Project: Ignite

Re: Losing data during restarting cluster with persistence enabled

Hi Vyacheslav, Key to partition mapping shouldn't depends on topology, and shouldn't changed unstable topology. Looks like you've missed smth. Would you please share configuration? Does all nodes share same RockDB database or each node has its own copy? On Wed, Nov 15, 2017 at 12:22 AM,

Re: Add emergency node closing handler to public Ignite API

It would be nice to see the whole design first before going into low-level details. Without it we are jumping from topic to topic. Were the list events and reaction to these events discussed previously? At this point it is not clear why nodes should be forcefully stopped without any alternative.

Re: Add emergency node closing handler to public Ignite API

Vova, I'll refactor IEP-7 [1], most likely merge it with IEP-5 [2], and let you know that overall design ready and clear :) [1] https://cwiki.apache.org/confluence/display/IGNITE/IEP-7%3A+Ignite+internal+problems+detection#IEP-7:Igniteinternalproblemsdetection-SystemThreadRegestry . [2]

[GitHub] ignite pull request #3038: Ignite gg 13060

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

[GitHub] ignite pull request #3039: IGNITE-6911 .NET: Optionally disable Java console...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/3039 IGNITE-6911 .NET: Optionally disable Java console redirect You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #3031: IGNITE-6896 .NET: support Multidimensional Arrays...

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

[GitHub] ignite pull request #3037: [IGNITE-6702] Get rid of values deserialization i...

GitHub user gg-shq opened a pull request: https://github.com/apache/ignite/pull/3037 [IGNITE-6702] Get rid of values deserialization in H2TreeIndex.getRowCount Committing preliminary version to run tests on TC You can merge this pull request into a Git repository by running: $

request for contributors permissions

Hello! I want to resolve bugs using my account: da.loginov Please, provide me with necessary permissions. My GutHub account: Denis-Log Thanks in advance. Best regards, Denis

Re: Why isn't Apache Ignite on stackshare.io

Hi Jason, great point! Denis, what do you think? Here is a link to how you can add Ignite to the Stackshare: https://stackshare.io/stacks Jason, perhaps you can be our first customer testimonial there :) D. On Wed, Nov 15, 2017 at 1:50 AM, Jason Man, CLSA wrote: > Just

Re: collocated compute and off-heap cache

Dmitriy, There will be no performance overhead for reads, but there will be a significant performance overhead for writes because each update must be changed in offheap, and since the offheap will be very small, there will be a lot of pages reads and spills. 2017-11-15 6:53 GMT+03:00 Dmitriy

Re: collocated compute and off-heap cache

On Wed, Nov 15, 2017 at 8:38 AM, Alexey Goncharuk < alexey.goncha...@gmail.com> wrote: > Dmitriy, > > There will be no performance overhead for reads, but there will be a > significant performance overhead for writes because each update must be > changed in offheap, and since the offheap will be

Re: Ignite Enhancement Proposal #6 (Metrics)

Denis, It looks like [1] is a duplicate of [2] and [3] [1] https://issues.apache.org/jira/browse/IGNITE-5796 [2] https://issues.apache.org/jira/browse/IGNITE-6903 [3] https://issues.apache.org/jira/browse/IGNITE-6902 Please close issue as duplicate in case that's true. On Wed, Nov 15, 2017 at