[jira] [Created] (IGNITE-7903) Explain how to tune performance by using WAL modes

[Denis Magda (JIRA)]

Denis Magda created IGNITE-7903:
---

 Summary: Explain how to tune performance by using WAL modes
 Key: IGNITE-7903
 URL: https://issues.apache.org/jira/browse/IGNITE-7903
 Project: Ignite
  Issue Type: New Feature
  Components: documentation
Reporter: Denis Magda
 Fix For: 2.5


Explain how to improve performance by switching between the WAL modes:
https://apacheignite.readme.io/docs/durable-memory-tuning

Basically, LOG_ONLY and BACKGROUND mode can be considered as an alternative for 
FULL_SYNC.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [VOTE] Apache Ignite 2.4.0 RC1

[Anton Vinogradov]

+1, great work!

2018-03-07 19:34 GMT+03:00 Andrey Gura :

> +1
>
> Checked compilation under Java 8/9, examples, binaries checksums.
>
> On Wed, Mar 7, 2018 at 6:45 PM, Yury Babak  wrote:
> > +1
> >
> > Checked Ignite ML: sources and binaries.
> >
> > Regards,
> > Yury
> >
> >
> >
> > --
> > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>

[jira] [Created] (IGNITE-7902) Enable either swap space or persistence but not both

[Prachi Garg (JIRA)]

Prachi Garg created IGNITE-7902:
---

 Summary: Enable either swap space or persistence but not both 
 Key: IGNITE-7902
 URL: https://issues.apache.org/jira/browse/IGNITE-7902
 Project: Ignite
  Issue Type: Task
Reporter: Prachi Garg
Assignee: Ivan Rakov
 Fix For: 2.5


Enabling both swap and persistence at the same time for a data region does not 
make sense. An exception should be thrown in this case.

See discussion - 
http://apache-ignite-developers.2346864.n4.nabble.com/Enabling-swap-space-and-Ignite-Persistence-td27595.html



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: checksum file Release Distribution Policy

[Dmitriy Setrakyan]

On Tue, Mar 6, 2018 at 8:52 PM, Petr Ivanov  wrote:

> http://apache.org/dist/ignite/2.3.0/  >
>

Got it. Let's get rid of MD5 in this case.

D.

[GitHub] ignite pull request #3618: IGNITE-7791: add test case for delayed partition ...

[Mmuzaf]

GitHub user Mmuzaf opened a pull request:

https://github.com/apache/ignite/pull/3618

IGNITE-7791: add test case for delayed partition exchange

…nect

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/Mmuzaf/ignite ignite-7791

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/3618.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3618


commit 73c02562a485ad013d7a80cc358a56f47e7b1432
Author: Maxim Muzafarov 
Date:   2018-03-07T17:02:02Z

IGNITE-7791: add test case for delayed partition exchange after reconnect




---

[GitHub] ignite pull request #3598: IGNITE-7791: add additional logging

[Mmuzaf]

Github user Mmuzaf closed the pull request at:

https://github.com/apache/ignite/pull/3598


---

[GitHub] ignite pull request #3598: IGNITE-7791: add additional logging

[Mmuzaf]

Github user Mmuzaf closed the pull request at:

https://github.com/apache/ignite/pull/3598


---

[GitHub] ignite pull request #3598: IGNITE-7791: add additional logging

[Mmuzaf]

GitHub user Mmuzaf reopened a pull request:

https://github.com/apache/ignite/pull/3598

IGNITE-7791: add additional logging

Logging for reproducing bug

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/Mmuzaf/ignite ignite-7791

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/3598.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3598


commit 9e06b5f6c253af65373164d462efba4ef509a925
Author: Maxim Muzafarov 
Date:   2018-03-04T14:57:55Z

IGNITE-7791: add additional logging

commit c05110468124dbc21fe2ef148b4dc800be719dad
Author: Maxim Muzafarov 
Date:   2018-03-04T17:07:32Z

IGNITE-7791: add additional logging details for cache groups

commit 13e7d8a82e32e5c6a6437ad4816331ada30b4f95
Author: Maxim Muzafarov 
Date:   2018-03-05T16:51:55Z

IGNITE-7791: more logging

commit cc149ec8223dd501f7dbaf8011f2575864544971
Author: Maxim Muzafarov 
Date:   2018-03-06T10:56:48Z

IGNITE-7791: more logging 2

commit aed7ea90d029fd15f3d8b6474652e4250ca67de4
Author: Maxim Muzafarov 
Date:   2018-03-06T11:38:55Z

IGNITE-7791: more logging 3

commit 2b8a7ab433b9811a0a0df94b42300f19894c7332
Author: Maxim Muzafarov 
Date:   2018-03-06T15:16:14Z

IGNITE-7791: more logging 4

commit f75bcb954b22f81f1e341926b2fe86c20a08cf21
Author: Maxim Muzafarov 
Date:   2018-03-06T17:13:06Z

IGNITE-7791: more logging 5

commit 8691f5a67dd4c4b8d279661296241f1a77b28059
Author: Maxim Muzafarov 
Date:   2018-03-06T18:45:28Z

IGNITE-7791: more logging 6




---

Re: [VOTE] Apache Ignite 2.4.0 RC1

[Andrey Gura]

+1

Checked compilation under Java 8/9, examples, binaries checksums.

On Wed, Mar 7, 2018 at 6:45 PM, Yury Babak  wrote:
> +1
>
> Checked Ignite ML: sources and binaries.
>
> Regards,
> Yury
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Re: DiscoverySpi based on Apache ZooKeeper

[Sergey Chugunov]

Hello Ken,

Indeed tickets and documentation are confusing so let me clarify what they
are about.

Documentation at [1] and ticket IGNITE-1203 [2] are related to
*TcpDiscoverySpi* component (see javadoc for in at [3]).
More precisely they are about Zookeeper-based implementation of
subcomponent called IpFinder which helps TcpDiscoverySpi to locate nodes of
Ignite cluster.

Ticket IGNITE-7222 [4] is about new implementation of *DiscoverySpi*
interface (see [5]) based on Zookeeper. Most likely it will be released in
Ignite 2.5.

As per proposal page [6] it seems there is some mess with labels in JIRA
because tickets listed on the page look unrelated to it.
I'll try to fix the page so in won't confuse people.

[1] https://apacheignite.readme.io/docs/cluster-config#
zookeeper-based-discovery
[2] https://issues.apache.org/jira/browse/IGNITE-1203
[3]
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/spi/discovery/tcp/TcpDiscoverySpi.html
[4] https://issues.apache.org/jira/browse/IGNITE-7222
[5]
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/spi/discovery/DiscoverySpi.html
[6]
https://cwiki.apache.org/confluence/display/IGNITE/Discovery+SPI+by+ZooKeeper



On Wed, Mar 7, 2018 at 1:46 PM, kcheng.mvp  wrote:

> There is a section in the document
> https://apacheignite.readme.io/docs/cluster-config#
> zookeeper-based-discovery.
>
> but I found below two tickets.
>
> https://issues.apache.org/jira/browse/IGNITE-1203
>
> https://issues.apache.org/jira/browse/IGNITE-7222
>
> I am a bit confused about which version supports this feature.
>
> mean while I found there are 3 open issues in this wiki page.
>
>
> https://cwiki.apache.org/confluence/display/IGNITE/
> Discovery+SPI+by+ZooKeeper
>
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>

Re: [VOTE] Apache Ignite 2.4.0 RC1

[Yury Babak]

+1

Checked Ignite ML: sources and binaries.

Regards,
Yury



--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Re: Is ML a part of the Ignite.C# API? eom

[Guru Stron]

Hi, Dmitry

I'm also looking forward to try ML on Ignite.NET platform, is there any
idea when it is planned for release?

On 7 March 2018 at 12:15, Dmitry Pavlov  wrote:

> Hi Raymond,
>
> I guess it is not yet targetted to 2.5, because fix version is empty.
>
> Sincerely,
> Dmitriy Pavlov
>
> ср, 7 мар. 2018 г. в 11:54, Raymond Wilson :
>
> > Thanks Pavel.
> >
> > Will this target 2.5?
> >
> > -Original Message-
> > From: Pavel Tupitsyn [mailto:ptupit...@apache.org]
> > Sent: Wednesday, March 7, 2018 9:13 PM
> > To: dev 
> > Cc: u...@ignite.apache.org
> > Subject: Re: Is ML a part of the Ignite.C# API? eom
> >
> > Hi Raymond,
> >
> > This is planned, but not yet implemented:
> > https://issues.apache.org/jira/browse/IGNITE-6707
> >
> > Pavel
> >
> > On Wed, Mar 7, 2018 at 5:56 AM, Raymond Wilson <
> raymond_wil...@trimble.com
> > >
> > wrote:
> >
> > > … the reason I ask being that ML is included in the Ignite diagram in
> > > the Ignite.C# documentation page, but there is no documentation section
> > > for it.
> > >
> > >
> > >
> > > *From:* Raymond Wilson [mailto:raymond_wil...@trimble.com]
> > > *Sent:* Wednesday, March 7, 2018 3:55 PM
> > > *To:* u...@ignite.apache.org
> > > *Cc:* 'dev@ignite.apache.org' 
> > > *Subject:* Is ML a part of the Ignite.C# API? eom
> > >
> >
>

[GitHub] ignite pull request #3366: ignite-7396: fixed NullPointerException

[sk0x50]

Github user sk0x50 closed the pull request at:

https://github.com/apache/ignite/pull/3366


---

[GitHub] ignite pull request #3617: IGNITE-6860 Add logging and additional info while...

[ivandasch]

GitHub user ivandasch opened a pull request:

https://github.com/apache/ignite/pull/3617

IGNITE-6860 Add logging and additional info while BinaryMarshaller fa…

…ils to serialize object.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ivandasch/ignite ignite-6860

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/3617.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3617


commit 81071bec84d2cbb146acfb40d294e93cc44e7ffc
Author: Ivan Daschinskiy 
Date:   2018-03-07T13:43:59Z

IGNITE-6860 Add logging and additional info while BinaryMarshaller fails to 
serialize object.




---

[jira] [Created] (IGNITE-7901) Refactor Pages Write Throttling: introduce exponential throttle as separate class

[Ivan Rakov (JIRA)]

Ivan Rakov created IGNITE-7901:
--

 Summary: Refactor Pages Write Throttling: introduce exponential 
throttle as separate class
 Key: IGNITE-7901
 URL: https://issues.apache.org/jira/browse/IGNITE-7901
 Project: Ignite
  Issue Type: Improvement
Affects Versions: 2.5
Reporter: Ivan Rakov
Assignee: Dmitriy Pavlov


After IGNITE-7751 fix, we have three incarnations of Pages Write Throttle:

1) Only checkpoint buffer throttling - always on

2) Ratio based throttling - legacy

3) Speed based throttling - default when throttling is enabled

However, all three options use exponential throttling for preventing checkpoint 
buffer overflow (see PagesWriteSpeedBasedThrottle.ThrottleMode#EXPONENTIAL 
usages and isPageInCheckpoint branch of PagesWriteThrottle). 
For the sake of getting rid of copypaste, it would be better to refactor this 
and introduce exponential throttling to separate class. Two callbacks now will 
be called instead of one, but code will become nicer.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Thin client: transactions support

[Vladimir Ozerov]

We already have transactions support in JDBC driver in TX SQL branch
(ignite-4191). Currently it is implemented through separate thread, which
is not that efficient. Ideally we need to finish decoupling transactions
from threads. But alternatively we can change the logic on how we assign
thread ID to specific transaction and "impersonate" thin client worker
threads when serving requests from multiple users.



On Tue, Mar 6, 2018 at 10:01 PM, Denis Magda  wrote:

> Here is an original discussion with a reference to the JIRA ticket:
> http://apache-ignite-developers.2346864.n4.nabble.
> com/Re-Transaction-operations-using-the-Ignite-Thin-Client-
> Protocol-td25914.html
>
> --
> Denis
>
> On Tue, Mar 6, 2018 at 9:18 AM, Dmitriy Setrakyan 
> wrote:
>
> > Hi Dmitriy. I don't think we have a design proposal for transaction
> support
> > in thin clients. Do you mind taking this initiative and creating an IEP
> on
> > Wiki?
> >
> > D.
> >
> > On Tue, Mar 6, 2018 at 8:46 AM, Dmitriy Govorukhin <
> > dmitriy.govoruk...@gmail.com> wrote:
> >
> > > Hi, Igniters.
> > >
> > > I've seen a lot of discussions about thin client and binary protocol,
> > but I
> > > did not hear anything about transactions support. Do we have some draft
> > for
> > > this purpose?
> > >
> > > As I understand we have several problems:
> > >
> > >- thread and transaction have hard related (we use thread-local
> > variable
> > >and thread name)
> > >- we can process only one transaction at the same time in one thread
> > (it
> > >mean we need hold thread per client. If connect 100 thin clients to
> 1
> > >server node, then need to hold 100 thread on the server side)
> > >
> > > Let's discuss how we can implement transactions for the thin client.
> > >
> >
>

Re: QueryEntity design

[Vladimir Ozerov]

I do not think it is a big problem. We copy these values when starting node
anyway, so subsequent changes doesn't affect node's behavior. On the other
hand, this might be convenient to users in some cases.

On Wed, Mar 7, 2018 at 3:13 PM, Nikolay Izhikov  wrote:

> Vladimir.
>
> Thank you, it's clear now.
>
> I also wonder, why we provide access to internal HashMaps through getters?
> Should we wrap internal maps into `Collections.unmodifiableMap`?
>
>
> ```
> public Map getDefaultFieldValues() {
> return defaultFieldValues;
> }
> ```
>
> В Ср, 07/03/2018 в 14:36 +0300, Vladimir Ozerov пишет:
> > Hi Nikolay,
> >
> > The answer is simple - legacy. QueryEntity was introduced long before we
> > had rich SQL support. At this point we should consider both QueryEntity
> and
> > our SQL API obsolete. There is a ticket to design new SQL API [1] and new
> > "QueryEntity" should be it's integral part. If you have any ideas please
> > feel free to share.
> >
> > Vladimir.
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-4701
> >
> > On Wed, Mar 7, 2018 at 2:00 PM, Nikolay Izhikov 
> wrote:
> >
> > > Hello, Igniters.
> > >
> > > I'm working on IGNITE-7691 [1]
> > > The goal of ticket is provide scale and precision info about DECIMAL
> > > columns.
> > >
> > > I see that QueryEntity has a separate collection for each type of meta
> > > information:
> > >
> > > * not null fields - [2]
> > > * default values - [3]
> > >
> > > Why we have such class design?
> > > It seems like a wrong design to have a separate collection for every
> type
> > > of metainfo.
> > >
> > > Because, there are many pieces of column meta information:
> > >
> > > * not null
> > > * default value
> > > * maximum length/size for VARCHAR or ARRAY or BINARY
> > > * scale, precision
> > > * etc.
> > >
> > > Do we have plans to provide this information to user through
> QueryEntity?
> > >
> > > [1] https://issues.apache.org/jira/projects/IGNITE/issues/IGNITE-7691
> > > [2] https://github.com/apache/ignite/blob/master/modules/
> > > core/src/main/java/org/apache/ignite/cache/QueryEntity.java#L87
> > > [3] https://github.com/apache/ignite/blob/master/modules/
> > > core/src/main/java/org/apache/ignite/cache/QueryEntity.java#L90
>

[GitHub] ignite pull request #3616: ignite-2.5.1.b2 - zooKeeper discovery fixes

[sergey-chugunov-1985]

GitHub user sergey-chugunov-1985 opened a pull request:

https://github.com/apache/ignite/pull/3616

ignite-2.5.1.b2 - zooKeeper discovery fixes



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-2.5.1.b2

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/3616.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3616


commit 5671b68a71d7f8fad0ea34687295ad627de4952a
Author: sboikov 
Date:   2017-11-09T15:22:20Z

zk

commit d56163c0e5d87062687ec2325a8b11fb9e8682cc
Author: sboikov 
Date:   2017-11-10T08:34:00Z

zk

commit d1f730789ed718f11b0654fb3c4622cf9725b3db
Author: sboikov 
Date:   2017-11-10T09:04:54Z

zk

commit 48175cf3b5a18578173736ba1cbc4493e1327333
Author: sboikov 
Date:   2017-11-10T12:10:59Z

zk

commit 6c1fe28c70e677619842f57af09ce182daf3b06e
Author: sboikov 
Date:   2017-11-10T12:27:04Z

zk

commit 246478186aaef2f1e06deacb19d5198aeb1157fa
Author: sboikov 
Date:   2017-11-13T09:01:06Z

zk

commit 2b75ecfb9f1f490dbab907efd3aab8db9622b09c
Author: sboikov 
Date:   2017-11-13T09:01:23Z

Merge remote-tracking branch 'remotes/origin/master' into ignite-zk

commit 740c3b24f5d5d9fec166f9258d7bb0e31b1117fd
Author: sboikov 
Date:   2017-11-13T09:41:35Z

zk

commit 9970b95029f1c94ec027aaa38fdfda5719e79cfe
Author: sboikov 
Date:   2017-11-13T10:25:06Z

zk

commit 6ed2564a8d68e651cb776e13302d62f415938bea
Author: sboikov 
Date:   2017-11-13T11:24:54Z

zk

commit b361a78022a01ff854d469e26e2e3a773a64839a
Author: sboikov 
Date:   2017-11-13T11:41:11Z

zk

commit 804c84171cc75e53bed549d13d5af6858786d9a7
Author: sboikov 
Date:   2017-11-13T12:25:25Z

zk

commit 42813c8b0bca4e8cf1074ba6cbeff1a14247fbd3
Author: sboikov 
Date:   2017-11-13T15:08:46Z

zk

commit 32f7fa89899bd005791d941aed50c8f4f35dd46c
Author: sboikov 
Date:   2017-11-14T08:05:08Z

zk

commit 8ab3b56675ef9cd6a1515d2cb33f0b6fef0f0acd
Author: sboikov 
Date:   2017-11-14T10:52:51Z

zk

commit 3736abe27a080ac7962dd8ede9e7b7414c4a82ae
Author: sboikov 
Date:   2017-11-14T11:14:25Z

zk

commit 1842bb4c48ce245a5b69b669087590351de686fa
Author: sboikov 
Date:   2017-11-14T12:07:55Z

zk

commit 73f5af60cc6701a88712735f94f14f4fe0cdd92c
Author: sboikov 
Date:   2017-11-14T12:41:47Z

zk

commit f6218ddf57252c42e6f48df97d292473163dffdb
Author: sboikov 
Date:   2017-11-14T13:05:09Z

zk

commit 54211bfaee22bc77714f6c821b0765815f11e386
Author: sboikov 
Date:   2017-11-14T13:05:49Z

zk

commit d2f5a76cc725052d76a216603b2579f17ba92d60
Author: sboikov 
Date:   2017-11-14T13:34:42Z

zk

commit 775a60f79904686b2e443789ae8c62df74f4d6fa
Author: sboikov 
Date:   2017-11-14T14:36:24Z

zk

commit bedc4e99e14bd597616b134d99ea75cb4d22ea08
Author: sboikov 
Date:   2017-11-14T19:37:24Z

zk

commit 1ee551c856e988287ed6beeb054d53d89cb8800d
Author: sboikov 
Date:   2017-11-14T20:41:53Z

zk

commit ac07cbee75f3f230a12075ac91e4dad0f1a89b0b
Author: sboikov 
Date:   2017-11-15T07:10:24Z

Merge remote-tracking branch 'origin/ignite-zk' into ignite-zk

commit aa0ca90cbaec809715190c1036654a6aad0fb0a3
Author: sboikov 
Date:   2017-11-15T09:50:14Z

zk

commit 4ec75fa2900e3f4624d6516e0c50fc1877d7b5cc
Author: sboikov 
Date:   2017-11-15T10:12:26Z

zk

commit c55d5c2d039f58e3bd0d3ac089f2dfc09d6f90b9
Author: sboikov 
Date:   2017-11-15T11:20:08Z

zk

commit 11e2567fffa724e6b4af6021cda1bfbcf775370b
Author: sboikov 
Date:   2017-11-16T13:10:04Z

zk

commit 98a171c68a1f5610e5f5830144306ee73df866d6
Author: sboikov 
Date:   2017-11-16T14:42:05Z

zk




---

[jira] [Created] (IGNITE-7899) Write Zookeeper Discovery documentation in java docs

[Dmitry Sherstobitov (JIRA)]

Dmitry Sherstobitov created IGNITE-7899:
---

 Summary: Write Zookeeper Discovery documentation in java docs
 Key: IGNITE-7899
 URL: https://issues.apache.org/jira/browse/IGNITE-7899
 Project: Ignite
  Issue Type: Task
  Components: zookeeper
Affects Versions: 2.5
Reporter: Dmitry Sherstobitov
 Fix For: 2.5


Describe Zookeeper Discovery in java docs 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7900) Write Zookeeper Discovery documentation in readme.io

[Dmitry Sherstobitov (JIRA)]

Dmitry Sherstobitov created IGNITE-7900:
---

 Summary: Write Zookeeper Discovery documentation in readme.io
 Key: IGNITE-7900
 URL: https://issues.apache.org/jira/browse/IGNITE-7900
 Project: Ignite
  Issue Type: Task
  Components: zookeeper
Affects Versions: 2.5
Reporter: Dmitry Sherstobitov
 Fix For: 2.5


Describe Zookeeper Discovery in readme.io



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: MCTGA: .NET tests broken by IGNITE-6113

[Dmitry Pavlov]

Yes, it seems I need to do some update to
https://github.com/dspavlov/ignite-teamcity-helper to reset fail rate after
reasonable timeout/runs of tests.

I quess 3 weeks and/or 100 successfull runs may be sufficient to consider
test as fixed. WDYT?

ср, 7 мар. 2018 г. в 15:02, Pavel Tupitsyn :

> Yep, this test is not flaky at all, it had failed before for the same exact
> reason, forgetting to update .NET.
>
> On Wed, Mar 7, 2018 at 12:13 PM, Dmitry Pavlov 
> wrote:
>
> > Hi Pavel,
> >
> > Thank you for pointing to this issue. We have detected it under Teamcity
> > monitoring, but still any additional info on test failures is
> appreciated.
> >
> > I've checked PR run but did not noticed this failures, I have considered
> > this failures as flaky:
> >
> >Ignite Platform .NET Core Linux [ tests 1 ]
> >  dll: CacheMetricsParityTest.TestCacheMetrics (fail rate 2,9%)
> >
> >Ignite Platform .NET [ tests 1 ]
> >  exe: CacheMetricsParityTest.TestCacheMetrics (fail rate 1,9%)
> >
> > Please see https://issues.apache.org/jira/browse/IGNITE-7773
> >
> > Igniters, who can help with adding this metric to .NET?
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> >
> > ср, 7 мар. 2018 г. в 11:35, Pavel Tupitsyn :
> >
> > > Igniters, Alexey G, Pavel K,
> > >
> > > IGNITE-6113 changes [1] caused broken .NET test [2]
> > > Have you run TeamCity before merging?
> > >
> > > Please fix this.
> > >
> > > When new APIs are added to Java you should:
> > > a) add them to .NET as well
> > > - or -
> > > b) file a ticket and update .NET test (see how in CacheParityTest.cs we
> > > have a bunch of ignored APIs with JIRA tickets in comments)
> > >
> > > [1]
> > >
> > > https://github.com/apache/ignite/commit/6dc5804af6dda90ca210a39d622964
> > d78e3890f1
> > > [2] https://ci.ignite.apache.org/viewLog.html?buildId=1128191
> > >
> > > Thanks,
> > > Pavel
> > >
> >
>

[GitHub] ignite pull request #3614: IGNITE-7897 Add example for LSQR with data normal...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/3614


---

Re: QueryEntity design

[Nikolay Izhikov]

Vladimir.

Thank you, it's clear now.

I also wonder, why we provide access to internal HashMaps through getters?
Should we wrap internal maps into `Collections.unmodifiableMap`?


```
public Map getDefaultFieldValues() {
return defaultFieldValues;
}
```

В Ср, 07/03/2018 в 14:36 +0300, Vladimir Ozerov пишет:
> Hi Nikolay,
> 
> The answer is simple - legacy. QueryEntity was introduced long before we
> had rich SQL support. At this point we should consider both QueryEntity and
> our SQL API obsolete. There is a ticket to design new SQL API [1] and new
> "QueryEntity" should be it's integral part. If you have any ideas please
> feel free to share.
> 
> Vladimir.
> 
> [1] https://issues.apache.org/jira/browse/IGNITE-4701
> 
> On Wed, Mar 7, 2018 at 2:00 PM, Nikolay Izhikov  wrote:
> 
> > Hello, Igniters.
> > 
> > I'm working on IGNITE-7691 [1]
> > The goal of ticket is provide scale and precision info about DECIMAL
> > columns.
> > 
> > I see that QueryEntity has a separate collection for each type of meta
> > information:
> > 
> > * not null fields - [2]
> > * default values - [3]
> > 
> > Why we have such class design?
> > It seems like a wrong design to have a separate collection for every type
> > of metainfo.
> > 
> > Because, there are many pieces of column meta information:
> > 
> > * not null
> > * default value
> > * maximum length/size for VARCHAR or ARRAY or BINARY
> > * scale, precision
> > * etc.
> > 
> > Do we have plans to provide this information to user through QueryEntity?
> > 
> > [1] https://issues.apache.org/jira/projects/IGNITE/issues/IGNITE-7691
> > [2] https://github.com/apache/ignite/blob/master/modules/
> > core/src/main/java/org/apache/ignite/cache/QueryEntity.java#L87
> > [3] https://github.com/apache/ignite/blob/master/modules/
> > core/src/main/java/org/apache/ignite/cache/QueryEntity.java#L90

signature.asc
Description: This is a digitally signed message part

Re: MCTGA: .NET tests broken by IGNITE-6113

[Pavel Tupitsyn]

Yep, this test is not flaky at all, it had failed before for the same exact
reason, forgetting to update .NET.

On Wed, Mar 7, 2018 at 12:13 PM, Dmitry Pavlov 
wrote:

> Hi Pavel,
>
> Thank you for pointing to this issue. We have detected it under Teamcity
> monitoring, but still any additional info on test failures is appreciated.
>
> I've checked PR run but did not noticed this failures, I have considered
> this failures as flaky:
>
>Ignite Platform .NET Core Linux [ tests 1 ]
>  dll: CacheMetricsParityTest.TestCacheMetrics (fail rate 2,9%)
>
>Ignite Platform .NET [ tests 1 ]
>  exe: CacheMetricsParityTest.TestCacheMetrics (fail rate 1,9%)
>
> Please see https://issues.apache.org/jira/browse/IGNITE-7773
>
> Igniters, who can help with adding this metric to .NET?
>
> Sincerely,
> Dmitriy Pavlov
>
>
> ср, 7 мар. 2018 г. в 11:35, Pavel Tupitsyn :
>
> > Igniters, Alexey G, Pavel K,
> >
> > IGNITE-6113 changes [1] caused broken .NET test [2]
> > Have you run TeamCity before merging?
> >
> > Please fix this.
> >
> > When new APIs are added to Java you should:
> > a) add them to .NET as well
> > - or -
> > b) file a ticket and update .NET test (see how in CacheParityTest.cs we
> > have a bunch of ignored APIs with JIRA tickets in comments)
> >
> > [1]
> >
> > https://github.com/apache/ignite/commit/6dc5804af6dda90ca210a39d622964
> d78e3890f1
> > [2] https://ci.ignite.apache.org/viewLog.html?buildId=1128191
> >
> > Thanks,
> > Pavel
> >
>

[jira] [Created] (IGNITE-7898) IgniteCachePartitionLossPolicySelfTest is flaky on TC

[Pavel Kovalenko (JIRA)]

Pavel Kovalenko created IGNITE-7898:
---

 Summary: IgniteCachePartitionLossPolicySelfTest is flaky on TC
 Key: IGNITE-7898
 URL: https://issues.apache.org/jira/browse/IGNITE-7898
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 2.4
Reporter: Pavel Kovalenko
Assignee: Pavel Kovalenko


Affected tests:
testReadOnlyAll
testReadWriteSafe

Exception:
{code:java}
junit.framework.AssertionFailedError: Failed to find expected lost partition 
[exp=0, lost=[]]
at 
org.apache.ignite.internal.processors.cache.distributed.IgniteCachePartitionLossPolicySelfTest.verifyCacheOps(IgniteCachePartitionLossPolicySelfTest.java:219)
at 
org.apache.ignite.internal.processors.cache.distributed.IgniteCachePartitionLossPolicySelfTest.checkLostPartition(IgniteCachePartitionLossPolicySelfTest.java:166)
at 
org.apache.ignite.internal.processors.cache.distributed.IgniteCachePartitionLossPolicySelfTest.testReadWriteSafe(IgniteCachePartitionLossPolicySelfTest.java:114)
{code}

The problem of failure:
After we prepare topology and shutdown the node containing lost partition we 
start to check it immediately on all nodes (cache.lostPartitions() method). 
Sometimes we invoke this method on client node where last PME is not even 
started and getting empty list of lost partitions because we haven't received 
it yet on PME.

Possible solution:
Wait for PME finishing on all nodes (including client) before start to check 
for lost partitions.




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] ignite pull request #3615: Ignite 2.3.1.b3

[apopovgg]

GitHub user apopovgg opened a pull request:

https://github.com/apache/ignite/pull/3615

Ignite 2.3.1.b3



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-2.3.1.b3

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/3615.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3615


commit b433df44c99f0c21ca894e99e71317ba2466331f
Author: Alexey Goncharuk 
Date:   2017-10-30T15:31:59Z

IGNITE-6746 Persist system cache when persistent data regions are present

commit 7acc4d20b6bba249f659f2ec2f688cb35efa9975
Author: apopov 
Date:   2018-03-07T11:51:07Z

Ported IGNITE-7530 .NET: Fix memory usage and performance for GetAll and 
query cursors in binary mode




---

Re: QueryEntity design

[Vladimir Ozerov]

Hi Nikolay,

The answer is simple - legacy. QueryEntity was introduced long before we
had rich SQL support. At this point we should consider both QueryEntity and
our SQL API obsolete. There is a ticket to design new SQL API [1] and new
"QueryEntity" should be it's integral part. If you have any ideas please
feel free to share.

Vladimir.

[1] https://issues.apache.org/jira/browse/IGNITE-4701

On Wed, Mar 7, 2018 at 2:00 PM, Nikolay Izhikov  wrote:

> Hello, Igniters.
>
> I'm working on IGNITE-7691 [1]
> The goal of ticket is provide scale and precision info about DECIMAL
> columns.
>
> I see that QueryEntity has a separate collection for each type of meta
> information:
>
> * not null fields - [2]
> * default values - [3]
>
> Why we have such class design?
> It seems like a wrong design to have a separate collection for every type
> of metainfo.
>
> Because, there are many pieces of column meta information:
>
> * not null
> * default value
> * maximum length/size for VARCHAR or ARRAY or BINARY
> * scale, precision
> * etc.
>
> Do we have plans to provide this information to user through QueryEntity?
>
> [1] https://issues.apache.org/jira/projects/IGNITE/issues/IGNITE-7691
> [2] https://github.com/apache/ignite/blob/master/modules/
> core/src/main/java/org/apache/ignite/cache/QueryEntity.java#L87
> [3] https://github.com/apache/ignite/blob/master/modules/
> core/src/main/java/org/apache/ignite/cache/QueryEntity.java#L90

[GitHub] ignite pull request #3614: IGNITE-7897 Add example for LSQR with data normal...

[dmitrievanthony]

GitHub user dmitrievanthony opened a pull request:

https://github.com/apache/ignite/pull/3614

IGNITE-7897 Add example for LSQR with data normalization.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-7897

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/3614.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3614


commit 77890d9b1880cc94954b23973c2aee0bcb8847a5
Author: Anton Dmitriev 
Date:   2018-03-07T11:17:47Z

IGNITE-7897 Add example for LSQR with data normalization.




---

QueryEntity design

[Nikolay Izhikov]

Hello, Igniters.

I'm working on IGNITE-7691 [1]
The goal of ticket is provide scale and precision info about DECIMAL columns.

I see that QueryEntity has a separate collection for each type of meta 
information:

* not null fields - [2]
* default values - [3]

Why we have such class design?
It seems like a wrong design to have a separate collection for every type of 
metainfo.

Because, there are many pieces of column meta information:

* not null
* default value
* maximum length/size for VARCHAR or ARRAY or BINARY
* scale, precision
* etc.

Do we have plans to provide this information to user through QueryEntity?

[1] https://issues.apache.org/jira/projects/IGNITE/issues/IGNITE-7691
[2] 
https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/cache/QueryEntity.java#L87
[3] 
https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/cache/QueryEntity.java#L90

signature.asc
Description: This is a digitally signed message part

Re: DiscoverySpi based on Apache ZooKeeper

[kcheng.mvp]

There is a section in the document
https://apacheignite.readme.io/docs/cluster-config#zookeeper-based-discovery. 

but I found below two tickets.

https://issues.apache.org/jira/browse/IGNITE-1203

https://issues.apache.org/jira/browse/IGNITE-7222

I am a bit confused about which version supports this feature.

mean while I found there are 3 open issues in this wiki page.


https://cwiki.apache.org/confluence/display/IGNITE/Discovery+SPI+by+ZooKeeper




--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[GitHub] ignite pull request #3595: IGNITE-7851: .NET: linq query throws Hexadecimal ...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/3595


---

[jira] [Created] (IGNITE-7897) Add example of using LSQR with data normalization

[Anton Dmitriev (JIRA)]

Anton Dmitriev created IGNITE-7897:
--

 Summary: Add example of using LSQR with data normalization
 Key: IGNITE-7897
 URL: https://issues.apache.org/jira/browse/IGNITE-7897
 Project: Ignite
  Issue Type: Improvement
Reporter: Anton Dmitriev
Assignee: Anton Dmitriev


Currently we have an LSQR linear regression example (see 
[here|https://github.com/apache/ignite/blob/master/examples/src/main/java/org/apache/ignite/examples/ml/regression/linear/DistributedLinearRegressionWithLSQRTrainerExample.java])
 and a normalization procedure example (see 
[here|https://github.com/apache/ignite/blob/master/examples/src/main/java/org/apache/ignite/examples/ml/preprocessing/NormalizationExample.java]).

For better understanding we'd like to add an example that includes data 
normalization and LSQR linear regression in the same time.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] ignite pull request #3613: IGNITE-7773 Add 'rebalanceClearingPartitionsLeft'...

[Jokser]

GitHub user Jokser opened a pull request:

https://github.com/apache/ignite/pull/3613

IGNITE-7773 Add 'rebalanceClearingPartitionsLeft' metric to .NET



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-7773

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/3613.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3613


commit 0d839c8ecfbd521825ab13be799073207c4bbf71
Author: Pavel Kovalenko 
Date:   2018-03-07T09:17:13Z

IGNITE-7773 Add 'rebalanceClearingPartitionsLeft' metric to .NET




---

Re: Is ML a part of the Ignite.C# API? eom

[Dmitry Pavlov]

Hi Raymond,

I guess it is not yet targetted to 2.5, because fix version is empty.

Sincerely,
Dmitriy Pavlov

ср, 7 мар. 2018 г. в 11:54, Raymond Wilson :

> Thanks Pavel.
>
> Will this target 2.5?
>
> -Original Message-
> From: Pavel Tupitsyn [mailto:ptupit...@apache.org]
> Sent: Wednesday, March 7, 2018 9:13 PM
> To: dev 
> Cc: u...@ignite.apache.org
> Subject: Re: Is ML a part of the Ignite.C# API? eom
>
> Hi Raymond,
>
> This is planned, but not yet implemented:
> https://issues.apache.org/jira/browse/IGNITE-6707
>
> Pavel
>
> On Wed, Mar 7, 2018 at 5:56 AM, Raymond Wilson  >
> wrote:
>
> > … the reason I ask being that ML is included in the Ignite diagram in
> > the Ignite.C# documentation page, but there is no documentation section
> > for it.
> >
> >
> >
> > *From:* Raymond Wilson [mailto:raymond_wil...@trimble.com]
> > *Sent:* Wednesday, March 7, 2018 3:55 PM
> > *To:* u...@ignite.apache.org
> > *Cc:* 'dev@ignite.apache.org' 
> > *Subject:* Is ML a part of the Ignite.C# API? eom
> >
>

Re: MCTGA: .NET tests broken by IGNITE-6113

[Dmitry Pavlov]

Hi Pavel,

Thank you for pointing to this issue. We have detected it under Teamcity
monitoring, but still any additional info on test failures is appreciated.

I've checked PR run but did not noticed this failures, I have considered
this failures as flaky:

   Ignite Platform .NET Core Linux [ tests 1 ]
 dll: CacheMetricsParityTest.TestCacheMetrics (fail rate 2,9%)

   Ignite Platform .NET [ tests 1 ]
 exe: CacheMetricsParityTest.TestCacheMetrics (fail rate 1,9%)

Please see https://issues.apache.org/jira/browse/IGNITE-7773

Igniters, who can help with adding this metric to .NET?

Sincerely,
Dmitriy Pavlov


ср, 7 мар. 2018 г. в 11:35, Pavel Tupitsyn :

> Igniters, Alexey G, Pavel K,
>
> IGNITE-6113 changes [1] caused broken .NET test [2]
> Have you run TeamCity before merging?
>
> Please fix this.
>
> When new APIs are added to Java you should:
> a) add them to .NET as well
> - or -
> b) file a ticket and update .NET test (see how in CacheParityTest.cs we
> have a bunch of ignored APIs with JIRA tickets in comments)
>
> [1]
>
> https://github.com/apache/ignite/commit/6dc5804af6dda90ca210a39d622964d78e3890f1
> [2] https://ci.ignite.apache.org/viewLog.html?buildId=1128191
>
> Thanks,
> Pavel
>

RE: Is ML a part of the Ignite.C# API? eom

[Raymond Wilson]

Thanks Pavel.

Will this target 2.5?

-Original Message-
From: Pavel Tupitsyn [mailto:ptupit...@apache.org]
Sent: Wednesday, March 7, 2018 9:13 PM
To: dev 
Cc: u...@ignite.apache.org
Subject: Re: Is ML a part of the Ignite.C# API? eom

Hi Raymond,

This is planned, but not yet implemented:
https://issues.apache.org/jira/browse/IGNITE-6707

Pavel

On Wed, Mar 7, 2018 at 5:56 AM, Raymond Wilson 
wrote:

> … the reason I ask being that ML is included in the Ignite diagram in
> the Ignite.C# documentation page, but there is no documentation section
> for it.
>
>
>
> *From:* Raymond Wilson [mailto:raymond_wil...@trimble.com]
> *Sent:* Wednesday, March 7, 2018 3:55 PM
> *To:* u...@ignite.apache.org
> *Cc:* 'dev@ignite.apache.org' 
> *Subject:* Is ML a part of the Ignite.C# API? eom
>

[GitHub] ignite pull request #3599: IGNITE-5298 .NET: DML update via LINQ

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/3599


---

MCTGA: .NET tests broken by IGNITE-6113

[Pavel Tupitsyn]

Igniters, Alexey G, Pavel K,

IGNITE-6113 changes [1] caused broken .NET test [2]
Have you run TeamCity before merging?

Please fix this.

When new APIs are added to Java you should:
a) add them to .NET as well
- or -
b) file a ticket and update .NET test (see how in CacheParityTest.cs we
have a bunch of ignored APIs with JIRA tickets in comments)

[1]
https://github.com/apache/ignite/commit/6dc5804af6dda90ca210a39d622964d78e3890f1
[2] https://ci.ignite.apache.org/viewLog.html?buildId=1128191

Thanks,
Pavel

Re: Is ML a part of the Ignite.C# API? eom

[Pavel Tupitsyn]

Hi Raymond,

This is planned, but not yet implemented:
https://issues.apache.org/jira/browse/IGNITE-6707

Pavel

On Wed, Mar 7, 2018 at 5:56 AM, Raymond Wilson 
wrote:

> … the reason I ask being that ML is included in the Ignite diagram in the
> Ignite.C# documentation page, but there is no documentation section for it.
>
>
>
> *From:* Raymond Wilson [mailto:raymond_wil...@trimble.com]
> *Sent:* Wednesday, March 7, 2018 3:55 PM
> *To:* u...@ignite.apache.org
> *Cc:* 'dev@ignite.apache.org' 
> *Subject:* Is ML a part of the Ignite.C# API? eom
>