[jira] [Created] (IGNITE-6483) Entries count in caches' MX Beans not immediately available

Ilya Kasnacheev created IGNITE-6483: --- Summary: Entries count in caches' MX Beans not immediately available Key: IGNITE-6483 URL: https://issues.apache.org/jira/browse/IGNITE-6483 Project: Ignite

[GitHub] ignite pull request #2726: IGNITE-6480 fix serverTopologyNodes method

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

[jira] [Created] (IGNITE-6485) Binary marshaller fails on deserialization of object with writeReplace()

Andrey Gura created IGNITE-6485: --- Summary: Binary marshaller fails on deserialization of object with writeReplace() Key: IGNITE-6485 URL: https://issues.apache.org/jira/browse/IGNITE-6485 Project:

[GitHub] ignite pull request #2725: IGNITE-6397 .NET: Thin client: basic cache operat...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/2725 IGNITE-6397 .NET: Thin client: basic cache operations You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-6397

[GitHub] ignite pull request #2726: IGNITE-6480 fix serverTopologyNodes method

GitHub user DmitriyGovorukhin opened a pull request: https://github.com/apache/ignite/pull/2726 IGNITE-6480 fix serverTopologyNodes method You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-6480

[GitHub] ignite pull request #2710: IGNITE-6334 Throttle writing threads during ongoi...

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

[GitHub] ignite pull request #2695: Ignite 2.1.5-IGN-8173 remove locDepOwner

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

[GitHub] ignite pull request #2723: IGNITE-6213 remove locDepOwner flag, and mark as ...

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

[GitHub] ignite pull request #2721: IGNITE-6466:Ignite PDS1: Test testGetForInitialWr...

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

[jira] [Created] (IGNITE-6486) .NET: ActiveOnStart does not work

Pavel Tupitsyn created IGNITE-6486: -- Summary: .NET: ActiveOnStart does not work Key: IGNITE-6486 URL: https://issues.apache.org/jira/browse/IGNITE-6486 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-6480) Incorrect server node filter in GridDiscoveryManager

Dmitriy Govorukhin created IGNITE-6480: -- Summary: Incorrect server node filter in GridDiscoveryManager Key: IGNITE-6480 URL: https://issues.apache.org/jira/browse/IGNITE-6480 Project: Ignite

[jira] [Created] (IGNITE-6481) JDBC v2: must not use a cache to query Ignite

Taras Ledkov created IGNITE-6481: Summary: JDBC v2: must not use a cache to query Ignite Key: IGNITE-6481 URL: https://issues.apache.org/jira/browse/IGNITE-6481 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-6482) Add support for groups count

Pavel Konstantinov created IGNITE-6482: -- Summary: Add support for groups count Key: IGNITE-6482 URL: https://issues.apache.org/jira/browse/IGNITE-6482 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-6484) Fix IgnitePdsThreadInterruptionTest failure with larger number of threads.

Alexei Scherbakov created IGNITE-6484: - Summary: Fix IgnitePdsThreadInterruptionTest failure with larger number of threads. Key: IGNITE-6484 URL: https://issues.apache.org/jira/browse/IGNITE-6484

[jira] [Created] (IGNITE-6477) Add cache index metric to represent index size

Alexander Belyak created IGNITE-6477: Summary: Add cache index metric to represent index size Key: IGNITE-6477 URL: https://issues.apache.org/jira/browse/IGNITE-6477 Project: Ignite

Contributor permissions

Morning Community. Could you please provide me a contributor permissions? I'm going to help Yury Babak with ML component My Jira account: zaleslaw Alexey

[jira] [Created] (IGNITE-6479) IndexOutOfBoundsException jdbc2

Ilya Suntsov created IGNITE-6479: Summary: IndexOutOfBoundsException jdbc2 Key: IGNITE-6479 URL: https://issues.apache.org/jira/browse/IGNITE-6479 Project: Ignite Issue Type: Bug

Re: Ignite Enhancement Proposal process

Guys, I thought a bit more and looks like there is no conflict. Every IEP has a sponsor responsible for keeping it up to date. Let's agree that it is up to him how to organize tickets provided that they can be tracked from WIKI page easily. This way we will be able to use both approaches. Makes

Re: Contributor permissions

Hi Alex, Done. Glad to see you here! On Fri, Sep 22, 2017 at 11:17 AM, Alexey Zinoviev wrote: > Morning Community. > Could you please provide me a contributor permissions? > > I'm going to help Yury Babak with ML component > > My Jira account: zaleslaw > > Alexey >

[jira] [Created] (IGNITE-6478) IndexOutOfBoundsException jdbc2

Ilya Suntsov created IGNITE-6478: Summary: IndexOutOfBoundsException jdbc2 Key: IGNITE-6478 URL: https://issues.apache.org/jira/browse/IGNITE-6478 Project: Ignite Issue Type: Bug

Re: Persistence per memory policy configuration

I like it. Alexey G, can you please chime in? D. On Fri, Sep 22, 2017 at 11:33 AM, Vladimir Ozerov wrote: > Guys, > > Here is my proposal: > > 1) MemoryPolicyConfiguration is renamed to *DataRegionConfiguration*. > 2) PersistenceConfiguration is merged with

Re: Persistence per memory policy configuration

If we’re taking the consolidation path for Memory and Persistence configurations then it makes sense to merge MemoryMetrics [1] and PersistenceMetrics [2] plus their JMX beans. Agree? [1] https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/MemoryMetrics.html

[GitHub] ignite pull request #2727: IGNITE-6249 .NET: IgniteConfiguration.ConsistentI...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/2727 IGNITE-6249 .NET: IgniteConfiguration.ConsistentId You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-6249

[GitHub] ignite pull request #2728: race in innerUpdate fixed

GitHub user voipp opened a pull request: https://github.com/apache/ignite/pull/2728 race in innerUpdate fixed You can merge this pull request into a Git repository by running: $ git pull https://github.com/voipp/ignite ignite-5960-1 Alternatively you can review and apply

[GitHub] ignite pull request #2718: Ignite 6434

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

[GitHub] ignite pull request #2729: IGNITE-6486 .NET: Update IsActiveOnStart document...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/2729 IGNITE-6486 .NET: Update IsActiveOnStart documentation You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-6486

[GitHub] ignite pull request #2700: probable fix

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

[GitHub] ignite pull request #2720: Ignite 2.1.5 merge

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

[GitHub] ignite pull request #2497: IGNITE-6154 Incorrect check checkpoint pages coll...

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

[GitHub] ignite pull request #2730: Ignite-1.9.6-b6

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/2730 Ignite-1.9.6-b6 for tests You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-1.9.6-b6 Alternatively you can

[GitHub] ignite pull request #2731: Ignite-1.6.14

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/2731 Ignite-1.6.14 for test purposes You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-1.6.14 Alternatively you can

[jira] [Created] (IGNITE-6487) Affinity may return more backups that set during exchange

Dmitry Karachentsev created IGNITE-6487: --- Summary: Affinity may return more backups that set during exchange Key: IGNITE-6487 URL: https://issues.apache.org/jira/browse/IGNITE-6487 Project:

[GitHub] ignite pull request #2732: Ignite-gg-12751

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/2732 Ignite-gg-12751 check for service deployment hanging. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-12751

IGNITE-5798 - Logging Ignite configuration at startup

*Hello, Igniters!Now I’m working at ticket #5798[1] “Logging Ignite configuration at startup” and have the following questions: 1. Should I get fields and their values only from IgniteConfiguration or I should also get them from inherited classes? If second variant is correct , what level of

Re: Ignite Benchmarking Rules

Yes, we do. A team within AWS org wanted to contribute to the project and they are run a few machines for us. There's no money going back and forth, we are "just" using some of the resources. I guess the best way to get a few servers is to find people @Amazon, who'd be willing to make such

Re: IGNITE-5798 - Logging Ignite configuration at startup

Igniters, sorry for the wrong format of the previous letter. Below is the letter in the correct format. Now I’m working at ticket #5798[1] “Logging Ignite configuration at startup” and have the following questions: 1.Should I get fields and their values only from IgniteConfiguration or I should

Re: IGNITE-5798 - Logging Ignite configuration at startup

I would just create another category for logging configuration, e.g. ignite.config.log which by default should use our default file appender and output configuration to that category with info priority. Let's begin with IgniteConfiguration.toString(); --Yakov

[jira] [Created] (IGNITE-6488) Add info message for index rebuild

Alexey Goncharuk created IGNITE-6488: Summary: Add info message for index rebuild Key: IGNITE-6488 URL: https://issues.apache.org/jira/browse/IGNITE-6488 Project: Ignite Issue Type:

[GitHub] ignite pull request #2734: Ignite 2.1.3 p5

GitHub user glukos opened a pull request: https://github.com/apache/ignite/pull/2734 Ignite 2.1.3 p5 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.1.3-p5 Alternatively you can review and apply

[GitHub] ignite pull request #2736: ignite-5732-tc

GitHub user daradurvs opened a pull request: https://github.com/apache/ignite/pull/2736 ignite-5732-tc You can merge this pull request into a Git repository by running: $ git pull https://github.com/daradurvs/ignite ignite-5732-TC Alternatively you can review and apply these

[GitHub] ignite pull request #2733: IGNITE-6468: Added tests. Fixed some issues

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/2733 IGNITE-6468: Added tests. Fixed some issues You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-6468 Alternatively

Re: IGNITE-2894 - Binary object inside of Externalizable still serialized with OptimizedMarshaller

Nikita, I think it should be consistent with Binarylizable. -Val On Fri, Sep 22, 2017 at 7:12 AM Nikita Amelchev wrote: > Another problem is support BinaryObject methods, for example, when we need > to get a field(often case in queries with annotation QuerySqlField). In

[GitHub] ignite pull request #2735: Ignite 2.1.3 p4

GitHub user glukos opened a pull request: https://github.com/apache/ignite/pull/2735 Ignite 2.1.3 p4 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.1.3-p4 Alternatively you can review and apply

Warning if no table for BinaryObject

Hi all, I've seen several times that due wrong cache configuration people can't find data in cache and blame Ignite that it's buggy and doesn't work. And it's very difficult to find an error in the code, especially if you don't have reach experience with Ignite. One of the very common case is

[GitHub] ignite pull request #2410: IGNITE-5732 Provide API to test compatibility wit...

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

Review of IGNITE-6284/IGNITE-995

Hi All, I made a couple of pull requests and asked questions about several issues which I would like to work on. Can anyone please take a look into these? Pull requests: IGNITE-6284: Add IgniteCompute.withTaskNoResultCache() which should have similar effect as @ComputeTaskNoResultCache

[jira] [Created] (IGNITE-6489) Expiration Policies and Durable Memory Doc

Denis Magda created IGNITE-6489: --- Summary: Expiration Policies and Durable Memory Doc Key: IGNITE-6489 URL: https://issues.apache.org/jira/browse/IGNITE-6489 Project: Ignite Issue Type: Task

Expiration Policy and New Off-Heap Memory

Alex G., Some time ago I personally documented that the expiration policy is not support for the new off-heap space of the memory. A couple of days ago I got a feedback that it’s no longer true. The doc is fixed to avoid any confusions. Please check and confirm that it’s correct:

Re: Persistence per memory policy configuration

Guys, Here is my proposal: 1) MemoryPolicyConfiguration is renamed to *DataRegionConfiguration*. 2) PersistenceConfiguration is merged with MemoryConfiguration and renamed to ... *DataStorageConfiguration*! It has: common memory settings (e.g. default data region), persistence settings (e.g.

Re: Ignite Enhancement Proposal process

Sounds good to me. No more concerns. — Denis > On Sep 22, 2017, at 1:11 AM, Vladimir Ozerov wrote: > > Guys, > > I thought a bit more and looks like there is no conflict. Every IEP has a > sponsor responsible for keeping it up to date. Let's agree that it is up to > him