Re: Not the best name for WAL on/off command in SQL

[Dmitriy Setrakyan]

Denis, I am not sure I like the underscore. I believe Vladimir took the
command name from other RDBMS systems, but I will let him comment.

D.

On Thu, Feb 22, 2018 at 4:27 PM, Denis Magda  wrote:

> Vladimir, Anton,
>
> I've been reviewing the docs of WAL on/off capabilities [1] added to 2.4
> and personally think that LOGGING/NOLOGGING is not the best name to turn
> WAL on/off with ALTER TABLE [2].
>
> May I suggest to name it in a more human-friendly fashion such as:
> ALTER TABLE table *[WAL_ON|WAL_OFF]*
>
> Hope you can do the renaming while 2.4 is still being tested and
> benchmarked. Sorry for late notice, but I missed the general review of the
> API.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-7415?filter=12342590
> [2] https://apacheignite-sql.readme.io/v2.3/docs/alter-table_24_hidden
>
> --
> Denis
>

Not the best name for WAL on/off command in SQL

[Denis Magda]

Vladimir, Anton,

I've been reviewing the docs of WAL on/off capabilities [1] added to 2.4
and personally think that LOGGING/NOLOGGING is not the best name to turn
WAL on/off with ALTER TABLE [2].

May I suggest to name it in a more human-friendly fashion such as:
ALTER TABLE table *[WAL_ON|WAL_OFF]*

Hope you can do the renaming while 2.4 is still being tested and
benchmarked. Sorry for late notice, but I missed the general review of the
API.

[1] https://issues.apache.org/jira/browse/IGNITE-7415?filter=12342590
[2] https://apacheignite-sql.readme.io/v2.3/docs/alter-table_24_hidden

--
Denis

[jira] [Created] (IGNITE-7798) Give user an ability to check driver metrics in Cassandra store

[Valentin Kulichenko (JIRA)]

Valentin Kulichenko created IGNITE-7798:
---

 Summary: Give user an ability to check driver metrics in Cassandra 
store
 Key: IGNITE-7798
 URL: https://issues.apache.org/jira/browse/IGNITE-7798
 Project: Ignite
  Issue Type: Improvement
  Components: cassandra
Affects Versions: 2.3
Reporter: Valentin Kulichenko
 Fix For: 2.5


Cassandra store uses generic client driver to connect to the cluster. The 
driver provides {{Metrics}} object which can be useful for monitoring, however 
there is no way for user to acquire it. Need to find a way to expose this 
information to public API.



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

Re: Next Steps: GA Grid: Request to contribute GA library to Apache Ignite

[Denis Magda]

Turik, All,

The IP clearance form is ready [1], and the final vote on general@incubator
is on the go [2].

Once the vote passes (72 hours), I'll finalize the process letting you know
when the code can be merged.

[1] http://incubator.apache.org/ip-clearance/ga-grid-ignite.html
[2]
http://apache-incubator-general.996316.n3.nabble.com/IP-CLEARANCE-Apache-Ignite-Genetic-Algorithms-Grid-td57791.html

--
Denis


On Thu, Feb 15, 2018 at 6:44 PM, techbysample  wrote:

> Denis,
>
> Thank you for providing status update.  I look forward to hearing from you.
>
> Best,
> Turik Campbell
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>

Re: Change TC trigger from Run All to per-project basis

[Dmitry Pavlov]

Hi Pavel,

regarding point 1, I've created draft here
https://cwiki.apache.org/confluence/display/IGNITE/Continuous+Integration

I'll create new topic once it will be ready.

SIncerely,
Dmitriy Pavlov

ср, 21 февр. 2018 г. в 10:26, Pavel Tupitsyn :

> Dmitry, thanks for the explanation, this makes sense.
>
> 1) Certainly can be helpful.
> 2) I would include "Platform .NET Core Linux": does not require win agent,
> runs 15 min, covers most functionality.
>
> Pavel
>
> On Wed, Feb 21, 2018 at 12:12 AM, Dmitry Pavlov 
> wrote:
>
> > Hi Pavel,
> >
> > WDYT,
> > 1) is it needed to prepare wiki article describing tests and chains we
> > have, e.g. describe
> >
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_
> > RunBasicTests
> > and
> > its difference with RunAll; which chain to use in each case?
> >
> > 2) Which .Net test suite may be applicable to be included into 'run basic
> > tests' (requires <30 min to run, no failed test, no flaky test with fail
> > rate >1%) ?
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > пн, 19 февр. 2018 г. в 0:39, Pavel Tupitsyn :
> >
> > > Igniters,
> > >
> > > Currently we have a TeamCity trigger only on Run All aggregating
> project:
> > >
> > > https://ci.ignite.apache.org/admin/editTriggers.html?id=
> > buildType:IgniteTests24Java8_RunAll
> > >
> > > Each change triggers it's own full run. If new changes are added while
> > some
> > > builds are queued,
> > > these changes are not picked up, and a separate run is scheduled.
> > >
> > > At this very moment I see over 600 queued builds, all on master branch
> > from
> > > some trigger.
> > > Previously we had a trigger per-project, which seems to be more
> > efficient.
> > >
> > > Thoughts?
> > >
> > > Pavel
> > >
> >
>

Re: Welcome email: Kalashnikov

[Denis Magda]

Hi Ruchir,

You're in. Now you can any ticket you'd like.

--
Denis

On Thu, Feb 22, 2018 at 10:43 AM, Ruchir Choudhry <
ruchirchoudhr...@gmail.com> wrote:

> Thank you Dmitry,
>
>
> here are the details,
>
> Username:ruchircFull name:ruchir choudhryEmail:ruchirchoudhry23 at gmail
> dot com
> Regards,
> Ruchir
>
>
>
>
> On Wed, Feb 21, 2018 at 11:31 PM, Dmitry Pavlov 
> wrote:
>
> > Hi Ruchir,
> >
> > You can sign up to apache JIRA by yourself.
> >
> > Could you share your JIRA username afterwards?
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > чт, 22 февр. 2018 г. в 10:19, Ruchir Choudhry <
> ruchirchoudhr...@gmail.com
> > >:
> >
> > > Hello Ignite team,
> > >
> > >
> > > I am not able to assign this ticket to my self,
> > >
> > > https://issues.apache.org/jira/browse/IGNITE-7759
> > >
> > >
> > >
> > > Can anyone help here,
> > >
> > > Thanks,
> > > Ruchir
> > >
> > > On Wed, Feb 21, 2018 at 2:31 AM, Dmitry Pavlov 
> > > wrote:
> > >
> > > > Hi Anton,
> > > >
> > > > Welcome to the Ignite Community!
> > > >
> > > > Could you please share your JIRA ID?
> > > >
> > > > Sincerely,
> > > > Dmitriy Pavlov
> > > >
> > > > P.S.
> > > > Please subscribe to both dev and user lists:
> > > > https://ignite.apache.org/community/resources.html#mail-lists
> > > >
> > > > 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:
> > > > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
> > > >
> > > > Project setup in Intellij IDEA:
> > > > https://cwiki.apache.org/confluence/display/IGNITE/Project+Setup
> > > >
> > > > ср, 21 февр. 2018 г. в 13:25, Антон Калашников :
> > > >
> > > > > Hello Ignite Community!
> > > > >
> > > > > I want to contribute to Apache Ignite and want to start with this
> > > issue -
> > > > > IGNITE-6552. Any help on this will be appreciated.
> > > > >
> > > > > Best regards,
> > > > > Anton Kalashnikov.
> > > > >
> > > > >
> > > >
> > >
> >
>

Re: [Apache Ignite Survey] Closed, results are attached

[Denis Magda]

Oops, anyway, it's not a big deal. Let's sum them up :)

On Thu, Feb 22, 2018 at 8:10 AM, Dmitry Pavlov 
wrote:

> Hi Denis,
>
> Interesting results, thank you.
>
> Unfortunately Ignite Persistence came twice in used features.
>
> And it becomes a a little bit unclear which measurement should be
> considered correct: max, min, or average.
>
> Sincerely,
> Dmitriy Pavlov
>
>
> чт, 22 февр. 2018 г. в 4:17, Dmitriy Setrakyan :
>
> > Very useful.
> >
> > BTW, here is the ticket for MultiMap implementation. It has a very nice
> > design proposal and looks fairly simple to implement.
> > https://issues.apache.org/jira/browse/IGNITE-640
> >
> > Hope someone in the community can pick it up.
> >
> > D.
> >
> > On Wed, Feb 21, 2018 at 3:56 PM, Denis Magda  wrote:
> >
> > > Igniters,
> > >
> > > The survey is off and here is a snapshot of the results:
> > > https://www.surveymonkey.com/results/SM-2T8S87DH8/
> > >
> > > Noteworthy observations:
> > >
> > >- 87% of respondents are software architects and engineers. These
> are
> > >the folks who help us to drive the project!
> > >
> > >
> > >- Most of Ignite use cases are in Banks and HighTech - this is what
> > the
> > >consistency and in-memory speed are valued for!
> > >
> > >
> > >- Majority of the deployments store up to 100 GB of data in up to 20
> > >nodes clusters while 10% of deployments maintain hundreds and
> > thousands
> > >nodes clusters - getting ready, community!
> > >
> > >
> > >- Ignite persistence is getting as valuable as the compute grid.
> > >
> > > Pay attention to the last question that contains a written individual
> > > feedback. It should guide our plans. For instance, I like this
> proposal:
> > >
> > > MultiMap support like in Guava is badly needed. Hazelcast has this and
> is
> > > highly used collection type, so much so this forces us to have to use
> > > Hazelcast over Ignite sadly in many apps
> > >
> > > --
> > > Denis
> > >
> >
>

[GitHub] ignite pull request #3566: Ignite 7686-2: Licenses fix

[dspavlov]

GitHub user dspavlov opened a pull request:

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

Ignite 7686-2: Licenses fix



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

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

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

https://github.com/apache/ignite/pull/3566.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 #3566


commit dd8a7ac47df1dc401e5a98dc21f9a0988fb50b0f
Author: dpavlov 
Date:   2017-12-01T16:47:45Z

GG-13117: PDS compatibility test flaky failure: debug code added

commit 2f869dfab5a2c56c26971c5cc88d3eed1314ad9b
Author: dspavlov 
Date:   2018-01-21T08:34:49Z

Merge remote-tracking branch 'apache/master'

commit 468afdd806ff0e15f732c6fe9a467c698fd6ee7a
Author: dspavlov 
Date:   2018-02-22T19:34:28Z

Merge remote-tracking branch 'apache/master'

commit d98b6420b8132c6871e9948917629bc847fd91b6
Author: dspavlov 
Date:   2018-02-22T19:36:53Z

IGNITE-7686: Licenses fix




---

Re: Welcome email: Kalashnikov

[Ruchir Choudhry]

Thank you Dmitry,


here are the details,

Username:ruchircFull name:ruchir choudhryEmail:ruchirchoudhry23 at gmail
dot com
Regards,
Ruchir




On Wed, Feb 21, 2018 at 11:31 PM, Dmitry Pavlov 
wrote:

> Hi Ruchir,
>
> You can sign up to apache JIRA by yourself.
>
> Could you share your JIRA username afterwards?
>
> Sincerely,
> Dmitriy Pavlov
>
> чт, 22 февр. 2018 г. в 10:19, Ruchir Choudhry  >:
>
> > Hello Ignite team,
> >
> >
> > I am not able to assign this ticket to my self,
> >
> > https://issues.apache.org/jira/browse/IGNITE-7759
> >
> >
> >
> > Can anyone help here,
> >
> > Thanks,
> > Ruchir
> >
> > On Wed, Feb 21, 2018 at 2:31 AM, Dmitry Pavlov 
> > wrote:
> >
> > > Hi Anton,
> > >
> > > Welcome to the Ignite Community!
> > >
> > > Could you please share your JIRA ID?
> > >
> > > Sincerely,
> > > Dmitriy Pavlov
> > >
> > > P.S.
> > > Please subscribe to both dev and user lists:
> > > https://ignite.apache.org/community/resources.html#mail-lists
> > >
> > > 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:
> > > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
> > >
> > > Project setup in Intellij IDEA:
> > > https://cwiki.apache.org/confluence/display/IGNITE/Project+Setup
> > >
> > > ср, 21 февр. 2018 г. в 13:25, Антон Калашников :
> > >
> > > > Hello Ignite Community!
> > > >
> > > > I want to contribute to Apache Ignite and want to start with this
> > issue -
> > > > IGNITE-6552. Any help on this will be appreciated.
> > > >
> > > > Best regards,
> > > > Anton Kalashnikov.
> > > >
> > > >
> > >
> >
>

Re: IgniteDataStreamer silently fails on a server node

[Nikolay Izhikov]

> I set 
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl#DFLT_MAX_REMAP_CNT
>  to zero and see test fails now.

Anton, thank you very much!

I've prepared PR [1] to fix issue [2]. TC looks OK.

Looks like it was introduced by commit 53802d8b46f8ee09d51ba84267f65dc6f7e73a2f 
[3]

Can, anyone do review of my fix?
It literally consists of 1 LOC.

[1] https://github.com/apache/ignite/pull/3550
[2] https://issues.apache.org/jira/browse/IGNITE-7756
[3] 
https://github.com/SomeFire/ignite/commit/53802d8b46f8ee09d51ba84267f65dc6f7e73a2f

В Ср, 21/02/2018 в 15:49 +0300, Anton Vinogradov пишет:
> Nikolay,
> 
> I checked your reproducer and it looks like retry helps data streamer to
> solve this.
> I
> set 
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl#DFLT_MAX_REMAP_CNT
> to zero and see test fails now.
> 
> Looks like second attempt is successful for such case.
> 
> On Wed, Feb 21, 2018 at 1:36 PM, Dmitriy Setrakyan 
> wrote:
> 
> > On Wed, Feb 21, 2018 at 12:10 AM, Nikolay Izhikov 
> > wrote:
> > 
> > > Hello, Igniters.
> > > 
> > > > Does this exception happen because IgniteUuid class is not correctly
> > > > handled?
> > > 
> > > Yes. I've fixed it.
> > > But story doesn't end :)
> > > 
> > > > As far as propagating exceptions, addData(...) is asynchronous
> > 
> > operation
> > > > and returns IgniteFuture.
> > > 
> > > Thank you, my bad.
> > > 
> > > But, I can't understand when returned future should complete?
> > > 
> > > Javadocs or documentation doesn't explain it.
> > > Also, I can't find any tests that checks future returned from addData.
> > > 
> > > Can someone explan it to me?
> > > 
> > 
> > The returned future should complete either when the data is successfully
> > stored in cache, or whenever the failure occurs.
> > 

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

[GitHub] ignite pull request #3560: IGNITE-7698: Fixed test hangup, avoid to double l...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] ignite pull request #3555: IGNITE-7780 Fixed test ClientConnectorConfigurati...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] ignite pull request #3532: IGNITE-7686: Fix of PDS Direct IO failure: Ignite...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] ignite pull request #3565: IGNITE-7702: Adopt kNN classifcation to the new d...

[zaleslaw]

GitHub user zaleslaw opened a pull request:

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

IGNITE-7702: Adopt kNN classifcation to the new datasets



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

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

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

https://github.com/apache/ignite/pull/3565.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 #3565


commit ae9741f36d360c2deada2804baa2cec1fb0254ea
Author: zaleslaw 
Date:   2018-02-14T14:42:16Z

Added draft sample

commit 531b336d569456fdee11a424878bd119b3b63c28
Author: Zinoviev Alexey 
Date:   2018-02-22T11:42:05Z

IGNITE-7702: Added tests

commit ad71203ca565f9ef688bea1924bc77052818e236
Author: Zinoviev Alexey 
Date:   2018-02-22T17:06:51Z

IGNITE-7702: Fixed bug

commit fd8f976f3d42066139b0359709fb8ea6eded2f0f
Author: Zinoviev Alexey 
Date:   2018-02-22T17:09:32Z

IGNITE-7702: remove incorrect examples

commit 4622dc6df0bf48c800dc413a24278d227e96f6aa
Author: Zinoviev Alexey 
Date:   2018-02-22T17:10:17Z

IGNITE-7702: Rewrite KNN classifications

commit 3a661d9e0627b8696c580d4f3587f51b30800166
Author: Zinoviev Alexey 
Date:   2018-02-22T17:11:28Z

IGNITE-7702: Delete incorrect benchmarks




---

[jira] [Created] (IGNITE-7797) Adopt yardstick tests for the new version of kNN classification algorithm

[Aleksey Zinoviev (JIRA)]

Aleksey Zinoviev created IGNITE-7797:


 Summary: Adopt yardstick tests for the new version of kNN 
classification algorithm
 Key: IGNITE-7797
 URL: https://issues.apache.org/jira/browse/IGNITE-7797
 Project: Ignite
  Issue Type: Sub-task
Reporter: Aleksey Zinoviev
Assignee: Aleksey Zinoviev






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

[jira] [Created] (IGNITE-7796) Adopt kNN classification example to the new datasets

[Aleksey Zinoviev (JIRA)]

Aleksey Zinoviev created IGNITE-7796:


 Summary: Adopt kNN classification example to the new datasets
 Key: IGNITE-7796
 URL: https://issues.apache.org/jira/browse/IGNITE-7796
 Project: Ignite
  Issue Type: Sub-task
  Components: ml
Reporter: Aleksey Zinoviev
Assignee: Aleksey Zinoviev






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

Re: [Apache Ignite Survey] Closed, results are attached

[Dmitry Pavlov]

Hi Denis,

Interesting results, thank you.

Unfortunately Ignite Persistence came twice in used features.

And it becomes a a little bit unclear which measurement should be
considered correct: max, min, or average.

Sincerely,
Dmitriy Pavlov


чт, 22 февр. 2018 г. в 4:17, Dmitriy Setrakyan :

> Very useful.
>
> BTW, here is the ticket for MultiMap implementation. It has a very nice
> design proposal and looks fairly simple to implement.
> https://issues.apache.org/jira/browse/IGNITE-640
>
> Hope someone in the community can pick it up.
>
> D.
>
> On Wed, Feb 21, 2018 at 3:56 PM, Denis Magda  wrote:
>
> > Igniters,
> >
> > The survey is off and here is a snapshot of the results:
> > https://www.surveymonkey.com/results/SM-2T8S87DH8/
> >
> > Noteworthy observations:
> >
> >- 87% of respondents are software architects and engineers. These are
> >the folks who help us to drive the project!
> >
> >
> >- Most of Ignite use cases are in Banks and HighTech - this is what
> the
> >consistency and in-memory speed are valued for!
> >
> >
> >- Majority of the deployments store up to 100 GB of data in up to 20
> >nodes clusters while 10% of deployments maintain hundreds and
> thousands
> >nodes clusters - getting ready, community!
> >
> >
> >- Ignite persistence is getting as valuable as the compute grid.
> >
> > Pay attention to the last question that contains a written individual
> > feedback. It should guide our plans. For instance, I like this proposal:
> >
> > MultiMap support like in Guava is badly needed. Hazelcast has this and is
> > highly used collection type, so much so this forces us to have to use
> > Hazelcast over Ignite sadly in many apps
> >
> > --
> > Denis
> >
>

[GitHub] ignite pull request #3564: Ignite gg 13518

[alamar]

GitHub user alamar opened a pull request:

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

Ignite gg 13518



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

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

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

https://github.com/apache/ignite/pull/3564.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 #3564


commit f3f726e9059e492573dc5125fd5edb5d2f71e9d3
Author: Andrey V. Mashenkov 
Date:   2017-06-13T11:11:17Z

IGNITE-4196: Added means to specify port for H2 debug console. This closes 
#1486.

(cherry picked from commit b246260)

commit c2c237d1222557d3e6b35d9a51a61a4c78e56782
Author: Sergey Kalashnikov 
Date:   2017-02-03T08:41:14Z

IGNITE-4196: Added means to specify port for H2 debug console. This closes 
#1486.

(cherry picked from commit b246260)

commit 4a8f295f2f2f34e8472b1d1320f03744135b2504
Author: Igor Sapego 
Date:   2017-06-13T16:47:00Z

IGNITE-5478: ODBC: SQLNumParams now returns number of required parameters.

(cherry picked from commit b1c56a1)

commit a2a4ec1ee9794cb542f146a07c6c67002cad444e
Author: Igor Sapego 
Date:   2017-06-14T09:16:43Z

IGNITE-5478: Fix for cherry pick

commit d268b32cb252a5f06887d2b803d27ddc20ded95f
Author: Igor Sapego 
Date:   2017-06-16T09:27:35Z

IGNITE-4370: Implemented writing of batch of parameters for ODBC.

(cherry picked from commit c10be5780589cc84e7929e234e4411d515166e0b)

commit 7fbaecc67f1b204162bda4595d6c118ddd45f963
Author: Andrey V. Mashenkov 
Date:   2017-06-16T17:01:49Z

IGNITE-5527: Prevent starvation in stripe pool on unstable topology.

commit f81964f59b0ea5b8dfdc8eb2acc34d2a5b8fee07
Author: sboikov 
Date:   2017-01-10T13:59:17Z

Do not evict removed entries, otherwise removes can be lost.

(cherry picked from commit 55ac6e7)

commit 5dd74ff635de50ff9561ccdb51bdeb620f60c3db
Author: sboikov 
Date:   2017-01-10T13:59:17Z

Do not evict removed entries, otherwise removes can be lost.

(cherry picked from commit 55ac6e7)

commit 5fb5c7e3b54ae4efb7a6a1832ba647677d93e0cd
Author: Evgenii Zhuravlev 
Date:   2017-06-22T06:43:03Z

IGNITE-5399 Manual cache rebalancing feature is broken

commit 01d41b72ecc3e81dfc8966cc0e395c247037241c
Author: Evgenii Zhuravlev 
Date:   2017-06-21T10:48:15Z

GG-12256 H2Indexes are not deleted if key class implements Externalizable

commit 5ac9afc719138e37a7d97d9d9db05243eee9a942
Author: Evgenii Zhuravlev 
Date:   2017-06-22T09:36:14Z

IGNITE-5399 add test to testsuite

commit a935d40a80e2f928a84a145aba540a45b156687f
Author: Evgenii Zhuravlev 
Date:   2017-06-22T12:10:32Z

GG-12256 Minor fixes

commit 7e2468770a4eb47a4f61204d8c2000b6ab67c967
Author: nikolay_tikhonov 
Date:   2017-06-22T13:13:01Z

IGNITE-GG-12197 Fixed "Ignore events for discarded update in CLOCK mode".

Signed-off-by: nikolay_tikhonov 

commit 5858efd406bb54352de14a0a7e7f21c2ac7bf899
Author: sboikov 
Date:   2016-12-16T16:23:29Z

IGNITE-2412 - Do not acquire asyncSemaphore for synchronous operations 
(cherry-picked from master)

(cherry picked from commit 82b4073)

commit 113a1380da34ea804d68757d39926da97dee09b6
Author: Alexey Goncharuk 
Date:   2017-06-13T05:20:22Z

GG-12355: Backported IO latency test.

commit 540ca449f1bd2386d3ba0722afb21dd3a504d044
Author: Alexey Goncharuk 
Date:   2017-06-13T17:55:38Z

GG-12355: Added discovery ring latency test + made it available from MBean 
(cherry-picked from master).

commit 0fc6271d8e39125bf5ee341e50a2665a04fc8b1e
Author: Andrey V. Mashenkov 
Date:   2017-06-21T10:42:12Z

GG-12350: GridDhtAtomicSingleUpdateRequest misses topologyVersion() method 
override.

commit f8224d13cf9a6432ba65e0016370ba51bbb544e9
Author: Alexey Goncharuk 
Date:   2017-06-15T19:49:45Z

GG-12299: Make sure concurrent type registrations do not trigger multiple 
cache updates.

commit 4ffc3acfa1bc43bea8c79bfd1864787c15cfc4de
Author: Alexey Goncharuk 
Date:   2017-06-20T04:59:09Z

IGNITE-5528 - IS_EVICT_DISABLED flag is not cleared on cache store 
exception.

commit 8cd9e829380f4c91cc9bb126169863286d1cb323
Author: Andrey V. Mashenkov 
Date:   2017-06-21T12:40:14Z

GG-12353: Added local binary context flag.

Backport of IGNITE-5223 with fixes.

commit 9036ad239d68eff663bc73a81baab2826b054d9a
Author: Andrey V. Mashenkov 
Date:   2017-06-21T15:25:31Z

Added MBean for system cache 

[GitHub] ignite pull request #3563: Ignite gg 13518

[alamar]

GitHub user alamar opened a pull request:

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

Ignite gg 13518



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

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

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

https://github.com/apache/ignite/pull/3563.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 #3563


commit f3f726e9059e492573dc5125fd5edb5d2f71e9d3
Author: Andrey V. Mashenkov 
Date:   2017-06-13T11:11:17Z

IGNITE-4196: Added means to specify port for H2 debug console. This closes 
#1486.

(cherry picked from commit b246260)

commit c2c237d1222557d3e6b35d9a51a61a4c78e56782
Author: Sergey Kalashnikov 
Date:   2017-02-03T08:41:14Z

IGNITE-4196: Added means to specify port for H2 debug console. This closes 
#1486.

(cherry picked from commit b246260)

commit 4a8f295f2f2f34e8472b1d1320f03744135b2504
Author: Igor Sapego 
Date:   2017-06-13T16:47:00Z

IGNITE-5478: ODBC: SQLNumParams now returns number of required parameters.

(cherry picked from commit b1c56a1)

commit a2a4ec1ee9794cb542f146a07c6c67002cad444e
Author: Igor Sapego 
Date:   2017-06-14T09:16:43Z

IGNITE-5478: Fix for cherry pick

commit d268b32cb252a5f06887d2b803d27ddc20ded95f
Author: Igor Sapego 
Date:   2017-06-16T09:27:35Z

IGNITE-4370: Implemented writing of batch of parameters for ODBC.

(cherry picked from commit c10be5780589cc84e7929e234e4411d515166e0b)

commit 7fbaecc67f1b204162bda4595d6c118ddd45f963
Author: Andrey V. Mashenkov 
Date:   2017-06-16T17:01:49Z

IGNITE-5527: Prevent starvation in stripe pool on unstable topology.

commit f81964f59b0ea5b8dfdc8eb2acc34d2a5b8fee07
Author: sboikov 
Date:   2017-01-10T13:59:17Z

Do not evict removed entries, otherwise removes can be lost.

(cherry picked from commit 55ac6e7)

commit 5dd74ff635de50ff9561ccdb51bdeb620f60c3db
Author: sboikov 
Date:   2017-01-10T13:59:17Z

Do not evict removed entries, otherwise removes can be lost.

(cherry picked from commit 55ac6e7)

commit 5fb5c7e3b54ae4efb7a6a1832ba647677d93e0cd
Author: Evgenii Zhuravlev 
Date:   2017-06-22T06:43:03Z

IGNITE-5399 Manual cache rebalancing feature is broken

commit 01d41b72ecc3e81dfc8966cc0e395c247037241c
Author: Evgenii Zhuravlev 
Date:   2017-06-21T10:48:15Z

GG-12256 H2Indexes are not deleted if key class implements Externalizable

commit 5ac9afc719138e37a7d97d9d9db05243eee9a942
Author: Evgenii Zhuravlev 
Date:   2017-06-22T09:36:14Z

IGNITE-5399 add test to testsuite

commit a935d40a80e2f928a84a145aba540a45b156687f
Author: Evgenii Zhuravlev 
Date:   2017-06-22T12:10:32Z

GG-12256 Minor fixes

commit 7e2468770a4eb47a4f61204d8c2000b6ab67c967
Author: nikolay_tikhonov 
Date:   2017-06-22T13:13:01Z

IGNITE-GG-12197 Fixed "Ignore events for discarded update in CLOCK mode".

Signed-off-by: nikolay_tikhonov 

commit 5858efd406bb54352de14a0a7e7f21c2ac7bf899
Author: sboikov 
Date:   2016-12-16T16:23:29Z

IGNITE-2412 - Do not acquire asyncSemaphore for synchronous operations 
(cherry-picked from master)

(cherry picked from commit 82b4073)

commit 113a1380da34ea804d68757d39926da97dee09b6
Author: Alexey Goncharuk 
Date:   2017-06-13T05:20:22Z

GG-12355: Backported IO latency test.

commit 540ca449f1bd2386d3ba0722afb21dd3a504d044
Author: Alexey Goncharuk 
Date:   2017-06-13T17:55:38Z

GG-12355: Added discovery ring latency test + made it available from MBean 
(cherry-picked from master).

commit 0fc6271d8e39125bf5ee341e50a2665a04fc8b1e
Author: Andrey V. Mashenkov 
Date:   2017-06-21T10:42:12Z

GG-12350: GridDhtAtomicSingleUpdateRequest misses topologyVersion() method 
override.

commit f8224d13cf9a6432ba65e0016370ba51bbb544e9
Author: Alexey Goncharuk 
Date:   2017-06-15T19:49:45Z

GG-12299: Make sure concurrent type registrations do not trigger multiple 
cache updates.

commit 4ffc3acfa1bc43bea8c79bfd1864787c15cfc4de
Author: Alexey Goncharuk 
Date:   2017-06-20T04:59:09Z

IGNITE-5528 - IS_EVICT_DISABLED flag is not cleared on cache store 
exception.

commit 8cd9e829380f4c91cc9bb126169863286d1cb323
Author: Andrey V. Mashenkov 
Date:   2017-06-21T12:40:14Z

GG-12353: Added local binary context flag.

Backport of IGNITE-5223 with fixes.

commit 9036ad239d68eff663bc73a81baab2826b054d9a
Author: Andrey V. Mashenkov 
Date:   2017-06-21T15:25:31Z

Added MBean for system cache 

[jira] [Created] (IGNITE-7795) Correct handling partitions restored in RENTING state

[Pavel Kovalenko (JIRA)]

Pavel Kovalenko created IGNITE-7795:
---

 Summary: Correct handling partitions restored in RENTING state
 Key: IGNITE-7795
 URL: https://issues.apache.org/jira/browse/IGNITE-7795
 Project: Ignite
  Issue Type: Bug
  Components: cache, persistence
Affects Versions: 2.3, 2.2, 2.1, 2.4
Reporter: Pavel Kovalenko
 Fix For: 2.5


Let's we have node which has partition in state RENTING after start. It could 
happen if node was stopped during partition eviction.

Started up node is only one owner by affinity for this partition.

Currently we will own this partition during rebalance preparing phase which 
seems is not correct. 

If we don't have owners for some partitions we should fail activation process, 
move this partition to MOVING state and clear it.



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

[GitHub] ignite pull request #3562: Ignite 1.7.19

[pvinokurov]

GitHub user pvinokurov opened a pull request:

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

Ignite 1.7.19



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

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

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

https://github.com/apache/ignite/pull/3562.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 #3562


commit 9c6824b4f33fbdead64299d9e0c34365d5d4a570
Author: nikolay_tikhonov 
Date:   2016-11-24T13:27:05Z

IGNITE-3958 Fixed "Client node should not start rest processor".

commit 56998e704e9a67760c70481c10c56e72c0a866bb
Author: Konstantin Dudkov 
Date:   2016-10-28T13:27:34Z

ignite-4088 Added methods to create/destroy multiple caches. This closes 
#1174.

(cherry picked from commit f445e7b)

commit 3e2ccfd30427ba0552eea8667c0129ae5ace9c0b
Author: Igor Sapego 
Date:   2016-11-25T11:26:54Z

IGNITE-4299: Fixes for examples.

commit 6fbaef45af8f40062a95058df7ec0984c99035b9
Author: Konstantin Dudkov 
Date:   2016-11-25T10:58:58Z

IGNITE-4305 marshalling fix in GridNearAtomicSingleUpdateInvokeRequest

commit 1a2de51f5807a91ce0d5dff28f24ed5bf7abebbc
Author: Konstantin Dudkov 
Date:   2016-11-28T09:59:02Z

IGNITE-4305 marshalling fix

commit c06e4017771603df7118974758d3d6b9cadc41b5
Author: Eduard Shangareev 
Date:   2016-11-30T11:34:47Z

ignite-4332 Usage of cache.getEntry inside GridCacheQueryManager.runQuery 
causes to remote operations

commit 066691098797be8c01daa0e8dc2ba94d4ad73561
Author: sboikov 
Date:   2016-12-01T14:16:28Z

ignite-4344 Do not create offheap map on client nodes.

commit e9ace7730773a6d4a1d30b271854f1fe8a7ba632
Author: Alexey Kuznetsov 
Date:   2016-12-02T09:06:41Z

Improved exception handling.

commit 12bdd6a031a33eda004a66e73cee9628f073ed68
Author: Alexey Kuznetsov 
Date:   2016-12-02T09:09:29Z

Updated classnames.properties for running nodes in IDE.

commit 33dda46061aae73e5c138851cfdd5f49a1c254cb
Author: sboikov 
Date:   2016-12-02T09:13:38Z

ignite-4285 For serializable txs allow multiple threads to get read lock 
for the same key

commit cc13d9d155f70e22e08ef203ac64e5cc0aa0a50f
Author: dkarachentsev 
Date:   2016-11-28T08:30:14Z

IGNITE-4026: Fixed BinaryObjectBuilder.build() can fail if one of the 
fields is Externalizable, enum from binary object. This closes #1281. This 
closes #1289.

(cherry picked from commit 0b7c62d)

commit b4aedfd5350b4a318f1608596a171789513835a4
Author: Igor Sapego 
Date:   2016-12-02T17:10:09Z

IGNITE-4347: Fixed NPE.

commit acf20b32d8fb68e42b904b091fb2b943f4558cef
Author: sboikov 
Date:   2016-12-05T11:01:28Z

ignite-4296 Optimize GridDhtPartitionsSingleMessage processing
- optimized processing of GridDhtPartitionsSingleMessage
- minor optimizations for RendezvousAffinityFunction
 - fixed heartbeats sending in tcp discovery

commit 6ba1711a1fa10d8276974227491136070c3ed43a
Author: Anton Vinogradov 
Date:   2016-12-06T09:55:41Z

IGNITE-4242 ExchangeManager should wait for cache rebalancing in async way

commit 0d4a1b7381fece47ee480f3a06bff7c51a7fead4
Author: Alexey Kuznetsov 
Date:   2016-12-07T11:02:49Z

Improved exception handling for failed queries.

commit ac8602dbdf2bbf5b16a611eaf6d520a0a7b0010b
Author: Sergi Vladykin 
Date:   2016-08-15T13:46:54Z

ignite-3685 - fixed

commit bbaa79af8ef526b5d2684db0e3d71d60a8f1ebe7
Author: agura 
Date:   2016-12-07T16:36:11Z

IGNITE-3770 GridLogThrottle.warn ignores the exception

commit 18598574bb2992aa193eed1d72ca333a1e21ad72
Author: Andrey V. Mashenkov 
Date:   2016-12-08T09:36:07Z

GG-11746: Backport of IGNITE-4379:  Fixed broken local SqlFieldsQuery.

commit 671a77a2d81cac401765dddf25f30fba4e4ab17f
Author: sboikov 
Date:   2016-12-08T09:56:46Z

ignite-4154 Fixed node version check for compression feature usage

commit 391f4be4c687a7f325aeec8b727c9c85ca003454
Author: agura 
Date:   2016-12-07T17:11:50Z

ignite-2358 toString() method for cache store implementations

commit bc977d3211906ef94e1f7d3f0f988efbed65034f
Author: Alexey Kuznetsov 
Date:   2016-12-09T09:11:31Z

IGNITE-4350 Reworked JdbcTypesDefaultTransformed logic. Improved improved 
error messages in CacheJdbcPojoStore.

commit b83ec8e57c7c48f2baa4780cf3b2e46df075f3df
Author: sboikov 
Date:   2016-12-09T11:32:42Z

IGNITE-500 CacheLoadingConcurrentGridStartSelfTest fails: prevent 
'localUpdate' execution while top read lock is held.

commit 6e485637e2738a7e809eac1a802f0964dc12383d
Author: Andrey V. 

[GitHub] ignite pull request #3495: ignite-7193: IgniteReflectionFactory should prope...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] ignite pull request #3561: Ignite 1.7 master

[alamar]

GitHub user alamar opened a pull request:

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

Ignite 1.7 master



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

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

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

https://github.com/apache/ignite/pull/3561.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 #3561


commit 9c6824b4f33fbdead64299d9e0c34365d5d4a570
Author: nikolay_tikhonov 
Date:   2016-11-24T13:27:05Z

IGNITE-3958 Fixed "Client node should not start rest processor".

commit 56998e704e9a67760c70481c10c56e72c0a866bb
Author: Konstantin Dudkov 
Date:   2016-10-28T13:27:34Z

ignite-4088 Added methods to create/destroy multiple caches. This closes 
#1174.

(cherry picked from commit f445e7b)

commit 3e2ccfd30427ba0552eea8667c0129ae5ace9c0b
Author: Igor Sapego 
Date:   2016-11-25T11:26:54Z

IGNITE-4299: Fixes for examples.

commit 6fbaef45af8f40062a95058df7ec0984c99035b9
Author: Konstantin Dudkov 
Date:   2016-11-25T10:58:58Z

IGNITE-4305 marshalling fix in GridNearAtomicSingleUpdateInvokeRequest

commit 1a2de51f5807a91ce0d5dff28f24ed5bf7abebbc
Author: Konstantin Dudkov 
Date:   2016-11-28T09:59:02Z

IGNITE-4305 marshalling fix

commit c06e4017771603df7118974758d3d6b9cadc41b5
Author: Eduard Shangareev 
Date:   2016-11-30T11:34:47Z

ignite-4332 Usage of cache.getEntry inside GridCacheQueryManager.runQuery 
causes to remote operations

commit 066691098797be8c01daa0e8dc2ba94d4ad73561
Author: sboikov 
Date:   2016-12-01T14:16:28Z

ignite-4344 Do not create offheap map on client nodes.

commit e9ace7730773a6d4a1d30b271854f1fe8a7ba632
Author: Alexey Kuznetsov 
Date:   2016-12-02T09:06:41Z

Improved exception handling.

commit 12bdd6a031a33eda004a66e73cee9628f073ed68
Author: Alexey Kuznetsov 
Date:   2016-12-02T09:09:29Z

Updated classnames.properties for running nodes in IDE.

commit 33dda46061aae73e5c138851cfdd5f49a1c254cb
Author: sboikov 
Date:   2016-12-02T09:13:38Z

ignite-4285 For serializable txs allow multiple threads to get read lock 
for the same key

commit cc13d9d155f70e22e08ef203ac64e5cc0aa0a50f
Author: dkarachentsev 
Date:   2016-11-28T08:30:14Z

IGNITE-4026: Fixed BinaryObjectBuilder.build() can fail if one of the 
fields is Externalizable, enum from binary object. This closes #1281. This 
closes #1289.

(cherry picked from commit 0b7c62d)

commit b4aedfd5350b4a318f1608596a171789513835a4
Author: Igor Sapego 
Date:   2016-12-02T17:10:09Z

IGNITE-4347: Fixed NPE.

commit acf20b32d8fb68e42b904b091fb2b943f4558cef
Author: sboikov 
Date:   2016-12-05T11:01:28Z

ignite-4296 Optimize GridDhtPartitionsSingleMessage processing
- optimized processing of GridDhtPartitionsSingleMessage
- minor optimizations for RendezvousAffinityFunction
 - fixed heartbeats sending in tcp discovery

commit 6ba1711a1fa10d8276974227491136070c3ed43a
Author: Anton Vinogradov 
Date:   2016-12-06T09:55:41Z

IGNITE-4242 ExchangeManager should wait for cache rebalancing in async way

commit 0d4a1b7381fece47ee480f3a06bff7c51a7fead4
Author: Alexey Kuznetsov 
Date:   2016-12-07T11:02:49Z

Improved exception handling for failed queries.

commit ac8602dbdf2bbf5b16a611eaf6d520a0a7b0010b
Author: Sergi Vladykin 
Date:   2016-08-15T13:46:54Z

ignite-3685 - fixed

commit bbaa79af8ef526b5d2684db0e3d71d60a8f1ebe7
Author: agura 
Date:   2016-12-07T16:36:11Z

IGNITE-3770 GridLogThrottle.warn ignores the exception

commit 18598574bb2992aa193eed1d72ca333a1e21ad72
Author: Andrey V. Mashenkov 
Date:   2016-12-08T09:36:07Z

GG-11746: Backport of IGNITE-4379:  Fixed broken local SqlFieldsQuery.

commit 671a77a2d81cac401765dddf25f30fba4e4ab17f
Author: sboikov 
Date:   2016-12-08T09:56:46Z

ignite-4154 Fixed node version check for compression feature usage

commit 391f4be4c687a7f325aeec8b727c9c85ca003454
Author: agura 
Date:   2016-12-07T17:11:50Z

ignite-2358 toString() method for cache store implementations

commit bc977d3211906ef94e1f7d3f0f988efbed65034f
Author: Alexey Kuznetsov 
Date:   2016-12-09T09:11:31Z

IGNITE-4350 Reworked JdbcTypesDefaultTransformed logic. Improved improved 
error messages in CacheJdbcPojoStore.

commit b83ec8e57c7c48f2baa4780cf3b2e46df075f3df
Author: sboikov 
Date:   2016-12-09T11:32:42Z

IGNITE-500 CacheLoadingConcurrentGridStartSelfTest fails: prevent 
'localUpdate' execution while top read lock is held.

commit 6e485637e2738a7e809eac1a802f0964dc12383d
Author: Andrey V. 

[jira] [Created] (IGNITE-7794) Marshaller mappings are not saved to disk on joining nodes

[Denis Mekhanikov (JIRA)]

Denis Mekhanikov created IGNITE-7794:


 Summary: Marshaller mappings are not saved to disk on joining nodes
 Key: IGNITE-7794
 URL: https://issues.apache.org/jira/browse/IGNITE-7794
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.4
Reporter: Denis Mekhanikov
 Fix For: 2.5
 Attachments: GridMarshallerMappingConsistencyTest.java

Find attached test class.

When a node connects to a cluster, that already has some marshaller mappings, 
they are not saved to disk on the joining node. It may result in "Unknown pair" 
error, if a cluster has persistence enabled, and a nodes without needed 
mappings start and try to read persisted data.



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

[jira] [Created] (IGNITE-7793) SQL does not work if value has index filed which name equals to affinity key name

[Mikhail Cherkasov (JIRA)]

Mikhail Cherkasov created IGNITE-7793:
-

 Summary: SQL does not work if value has index filed which name 
equals to affinity key name
 Key: IGNITE-7793
 URL: https://issues.apache.org/jira/browse/IGNITE-7793
 Project: Ignite
  Issue Type: Bug
  Components: sql
Affects Versions: 2.3
Reporter: Mikhail Cherkasov
 Fix For: 2.5


SQL does not work if value has index filed which name equals to affinity key 
name:
{code:java}
public class AKey {
@AffinityKeyMapped
int a;
public AKey(int a) {
this.a = a;
}
}

public class AVal {
@QuerySqlField
int a;
public AVal(int a) {
this.a = a;
}
}

AKey aKey = new AKey(1);
AVal aVal = new AVal(0);

IgniteCache cache = ignite.cache("Instrument");
cache.put(aKey, aVal);

SqlFieldsQuery query = new SqlFieldsQuery("select * from \"Instrument\".AVal it 
where it.a=?");

List res = cache.query(query.setArgs(0)).getAll();

if(res.isEmpty()) {
System.out.println("! FAILED !!!");
}


{code}



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

[GitHub] ignite pull request #3560: IGNITE-7698: Fixed test hangup, avoid to double l...

[dspavlov]

GitHub user dspavlov opened a pull request:

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

IGNITE-7698: Fixed test hangup, avoid to double lock page in case of …

…restore is done.

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

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

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

https://github.com/apache/ignite/pull/3560.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 #3560


commit aaff74d1c1e91559ffd2123d350ca0895e6d2f76
Author: dpavlov 
Date:   2018-02-22T13:15:10Z

IGNITE-7698: Fixed test hangup, avoid to double lock page in case of 
restore is done.




---

Re: TeamCity. Ignite RDD tests

[Nikolay Izhikov]

Dmitriy.

OK, I get it.

Looks like scala-test-plugin I added in IGNITE-7042 doesn't handle `-Dtest=XXX` 
properly.
I will investigate and fixed it.

В Чт, 22/02/2018 в 10:28 +, Dmitry Pavlov пишет:
> It seems that tests I've previously muted were started in wrong configs.
> 
> Is it possible IgniteRDDSpec.IgniteRDD  became unit tests, which is started
> with code compile?
> 
> This can be reason these tests appeared in suites which is not related to
> IgniteRDD, such as Scala Examples.
> 
> чт, 22 февр. 2018 г. в 13:20, Nikolay Izhikov :
> 
> > Hello, Dmitriy
> > 
> > I'm looked in TeamCity but not sure what should I do.
> > Can you explain it to me, please?
> > 
> > В Чт, 22/02/2018 в 10:13 +, Dmitry Pavlov пишет:
> > > Hi Nikolay,
> > > 
> > > It seems
> > > IgniteRDDSpec.IgniteRDD  has appeared in configurations it is not
> > 
> > expected
> > > to run.
> > > 
> > > Please see investigations assigned to you. What can we change to avoid
> > > these tests to be included into run other suites?
> > > 
> > > Sincerely,
> > > Dmitriy Pavlov
> > > 
> > > пт, 16 февр. 2018 г. в 7:35, Nikolay Izhikov :
> > > 
> > > > Hello, Igniters.
> > > > 
> > > > I'm working on issue [1].
> > > > 
> > > > Team City doesn't collect info about scalatest execution because of
> > 
> > wrong
> > > > pom.xml
> > > > I'm fixed it in PR [3]
> > > > 
> > > > It happens there is a 2 broken tests written in Scala - [4]
> > > > 
> > > > 1. IgniteRDDSpec.IgniteRDD should successfully store data to ignite
> > 
> > using
> > > > saveValues
> > > > 2. IgniteRDDSpec.IgniteRDD should successfully store data to ignite
> > 
> > using
> > > > saveValues with inline transformation
> > > > 
> > > > It seems they are been here for a while.
> > > > I propose to mute or disable it on TeamCity before merging my PR.
> > > > I've created ticket for fixing tests - [5].
> > > > 
> > > > Thoughts?
> > > > 
> > > > [1] https://issues.apache.org/jira/browse/IGNITE-7042
> > > > 
> > > > [2]
> > > > 
> > 
> > https://ci.ignite.apache.org/viewLog.html?buildId=1096059=buildResultsDiv=IgniteTests24Java8_IgniteRdd
> > > > 
> > > > [3] https://github.com/apache/ignite/pull/3530
> > > > 
> > > > [4]
> > > > 
> > 
> > https://ci.ignite.apache.org/viewLog.html?buildId=1095218=IgniteTests24Java8_IgniteRdd=testsInfo
> > > > 
> > > > [5] https://issues.apache.org/jira/browse/IGNITE-7727

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

[GitHub] ignite pull request #3559: IGNITE-6552 ability to set WAL history size in MB...

[akalash]

GitHub user akalash opened a pull request:

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

IGNITE-6552 ability to set WAL history size in MBytes



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

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

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

https://github.com/apache/ignite/pull/3559.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 #3559


commit 10a7221392d00caa25f99f7f1aa33408c085e759
Author: Anton Kalashnikov 
Date:   2018-02-22T11:57:38Z

IGNITE-6552 ability to set WAL history size in MBytes

commit 1bf01c091e064bc48fe49a3b750e1c47e68fbc4a
Author: Anton Kalashnikov 
Date:   2018-02-22T13:00:59Z

IGNITE-6552 change FileDescriptor header




---

[GitHub] ignite pull request #3558: IGNITE-6890 General way for handling Ignite failu...

[anton-vinogradov]

GitHub user anton-vinogradov opened a pull request:

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

IGNITE-6890 General way for handling Ignite failures (NodeInvalidator…

… should be replaced with IgniteFailureProcessor)

Signed-off-by: Anton Vinogradov 

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

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

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

https://github.com/apache/ignite/pull/3558.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 #3558


commit 4730f6c7511a715789fcf2ac1139f3c1526e7d19
Author: Anton Vinogradov 
Date:   2018-02-22T12:58:35Z

IGNITE-6890 General way for handling Ignite failures (NodeInvalidator 
should be replaced with IgniteFailureProcessor)

Signed-off-by: Anton Vinogradov 




---

[jira] [Created] (IGNITE-7792) IgniteDatabaseSharedManager refactoring

[Igor Seliverstov (JIRA)]

Igor Seliverstov created IGNITE-7792:


 Summary: IgniteDatabaseSharedManager refactoring
 Key: IGNITE-7792
 URL: https://issues.apache.org/jira/browse/IGNITE-7792
 Project: Ignite
  Issue Type: Task
  Components: cache
Reporter: Igor Seliverstov


Currently there is no mapping of cacheId to page memory which prevents adding 
custom persistent structures 
({{GridCacheDatabaseSharedManager.WriteCheckpointPages#run}}).



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

[GitHub] ignite pull request #3463: IGNITE-7489 Factor total allocated pages in data ...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] ignite pull request #3557: IGNITE-7763: Fixed C++ Win32 test failures

[isapego]

GitHub user isapego opened a pull request:

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

IGNITE-7763: Fixed C++ Win32 test failures



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

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

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

https://github.com/apache/ignite/pull/3557.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 #3557


commit f7b5c71d76c01e84da6dedb0ba1dfedac79640eb
Author: Igor Sapego 
Date:   2018-02-21T17:08:35Z

IGNITE-7763: Fixed test configurations




---

[jira] [Created] (IGNITE-7791) Ignite Client Nodes: failed test IgniteClientReconnectCacheTest.testReconnectCacheDestroyedAndCreated()

[Sergey Chugunov (JIRA)]

Sergey Chugunov created IGNITE-7791:
---

 Summary: Ignite Client Nodes: failed test 
IgniteClientReconnectCacheTest.testReconnectCacheDestroyedAndCreated()
 Key: IGNITE-7791
 URL: https://issues.apache.org/jira/browse/IGNITE-7791
 Project: Ignite
  Issue Type: Bug
Reporter: Sergey Chugunov
 Fix For: 2.5


Test is flaky, success rate: 32.4%, test history is 
[here|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-9174769196124217030=testDetails]

Reproducible locally.

Test fails on waiting for disco cache content:
{noformat}
junit.framework.AssertionFailedError
at junit.framework.Assert.fail(Assert.java:55)
at junit.framework.Assert.assertTrue(Assert.java:22)
at junit.framework.Assert.assertTrue(Assert.java:31)
at junit.framework.TestCase.assertTrue(TestCase.java:201)
at 
org.apache.ignite.internal.IgniteClientReconnectCacheTest.checkCacheDiscoveryData(IgniteClientReconnectCacheTest.java:1414)
at 
org.apache.ignite.internal.IgniteClientReconnectCacheTest.testReconnectCacheDestroyedAndCreated(IgniteClientReconnectCacheTest.java:897)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at junit.framework.TestCase.runTest(TestCase.java:176)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2001)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:133)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1916)
at java.lang.Thread.run(Thread.java:745)
{noformat}

This fail may be caused by another exception earlier in the log:
{noformat}
[2018-02-22 
14:32:57,972][ERROR][exchange-worker-#3025%internal.IgniteClientReconnectCacheTest3%][GridDhtPartitionsExchangeFuture]
 Failed to reinitialize local partitions (preloading will be stopped): 
GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=6, 
minorTopVer=1], discoEvt=DiscoveryCustomEvent 
[customMsg=CacheAffinityChangeMessage 
[id=3cea94db161-760b7b18-b776-4ee7-ae5a-64f9494eaa36, 
topVer=AffinityTopologyVersion [topVer=3, minorTopVer=0], exchId=null, 
partsMsg=null, exchangeNeeded=true], affTopVer=AffinityTopologyVersion 
[topVer=6, minorTopVer=1], super=DiscoveryEvent [evtNode=TcpDiscoveryNode 
[id=1b7f7330-69d8-4bd0-b2e9-71773610, addrs=[127.0.0.1], 
sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1, intOrder=1, 
lastExchangeTime=1519299177395, loc=false, ver=2.5.0#19700101-sha1:, 
isClient=false], topVer=6, nodeId8=658aeb36, msg=null, 
type=DISCOVERY_CUSTOM_EVT, tstamp=1519299177971]], nodeId=1b7f7330, 
evt=DISCOVERY_CUSTOM_EVT]
java.lang.AssertionError: 236160867
at 
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager$CachesInfo.group(CacheAffinitySharedManager.java:2636)
at 
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager$8.applyx(CacheAffinitySharedManager.java:989)
at 
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager$8.applyx(CacheAffinitySharedManager.java:983)
at 
org.apache.ignite.internal.util.lang.IgniteInClosureX.apply(IgniteInClosureX.java:38)
at 
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.forAllCacheGroups(CacheAffinitySharedManager.java:1118)
at 
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.onChangeAffinityMessage(CacheAffinitySharedManager.java:983)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onAffinityChangeRequest(GridDhtPartitionsExchangeFuture.java:992)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:648)
at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2337)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:745)
{noformat}



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

[jira] [Created] (IGNITE-7790) All critical errors health should be covered by IgniteFailureProcessor

[Anton Vinogradov (JIRA)]

Anton Vinogradov created IGNITE-7790:


 Summary: All critical errors health should be covered by 
IgniteFailureProcessor
 Key: IGNITE-7790
 URL: https://issues.apache.org/jira/browse/IGNITE-7790
 Project: Ignite
  Issue Type: Task
Reporter: Anton Vinogradov


List of errors to be handled 

- Persistence errors
- IOOM errors (part of persistence errors?)
- IO errors (list to be provided)
- Assertion errors (we should handle assertions as failures in case -ea flag 
set)



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

Re: Stop nodes after test by default - IGNITE-6842

[Dmitry Pavlov]

Hi Maxim,

Thank you.

To my mind stopAllGrids call should be kept in afterTestsStop(). If
developer forgot to call super(), he will see exception from beforeTestsStart()
added by you.

If you think patch is ready to be reviewed, please change JIRA status to
"Patch Available".

Optionally you can create Upsource review. It would be easier for multiple
reviewers to handle this patch. This test framework is used by all Igniters
so Upsource would be good option (https://reviews.ignite.apache.org/ ).

Sincerely,
Dmitriy Pavlov

чт, 22 февр. 2018 г. в 13:44, Maxim Muzafarov :

> Hi all,
>
> I've made some changes based on our previous discusstions, please see PR
> [1]:
> 1) Remove duplicated code for stopGrid (by index and by name);
> 2) Add new method that thows exception if not all grids haven't stopped
> correctly;
> 3)  Change tests that have been affected by this changes;
>
> Also, I have some thoughts for clarification:
> 1) beforeTestsStart() - I expect here in subtests that grids are not
> started yet. Am I right?
> 2) I think we should call stopAllGrids in tearDown method. So, if in some
> cases we'll override afterTestsStop in subclasses and forgot to call
> super() it won't lead us to exception.
>
> [1] https://github.com/apache/ignite/pull/3542
> [2] https://ci.ignite.apache.org/viewModification.html?modId=717275
> [3] https://issues.apache.org/jira/browse/IGNITE-6842
>
>
> ср, 7 февр. 2018 г. в 18:28, Maxim Muzafarov :
>
> > Thank you all,
> >
> > I'll add this comment's for JIRA ticket, if you don't mind.
> >
> > ср, 7 февр. 2018 г. в 15:16, Dmitry Pavlov :
> >
> >> Yes, this solution allows to cover both cases:
> >> a) not stopped node from previous test and
> >> b) allows to remove useless code that stops Ignite nodes from each test.
> >>
> >> ср, 7 февр. 2018 г. в 15:13, Anton Vinogradov  >:
> >>
> >> > Maxim,
> >> >
> >> > We discussed with Dima privately, and decided
> >> >
> >> > 1) We have to assert that there is no alive nodes at
> GridAbstractTest's
> >> > beforeTestsStarted
> >> > 2) We have to kill all alive nodes (without force) at
> GridAbstractTest's
> >> > afterTestsStopped
> >> > 3) In case of any exceptions at #2 we have to see test error
> >> > 4) We can get rid of all useless stopAllGrids at GridAbstractTest's
> >> > subclasses.
> >> >
> >> >
> >> >
> >> > On Wed, Feb 7, 2018 at 2:32 PM, Dmitry Pavlov 
> >> > wrote:
> >> >
> >> > > > Let's just add stopAllGrids(flase) to GridAbstractTest 's
> >> > > afterTestsStopped
> >> > > method body.
> >> > >
> >> > > Can't agree with it becase implicit silent shutdown of nodes from
> test
> >> > > framework may cause a lot of bugs introduced to Ignite.
> >> > >
> >> > > I think stop+test fail should occur.
> >> > > In that case author of incorrect test or not consistent Ignite
> >> shutdown
> >> > > will see problem.
> >> > >
> >> > > 'Fail fast' if always better than hidding real problem under
> automatic
> >> > > framework feature.
> >> > >
> >> > > ср, 7 февр. 2018 г. в 14:05, Anton Vinogradov <
> >> avinogra...@gridgain.com
> >> > >:
> >> > >
> >> > > > Hi all,
> >> > > >
> >> > > > > I've made some research about this problem and i think that in
> >> > general
> >> > > we
> >> > > > > should move stopAllGrids method in GridAbstractTest class to
> >> > > > > afterTestsStopped method with some changes. Am I right?
> >> > > > Let's just add stopAllGrids(flase) to GridAbstractTest 's
> >> > > > afterTestsStopped method
> >> > > > body.
> >> > > >
> >> > > > > I have a question about stopAllGrids(boolean cancel) this
> "cancel"
> >> > > > That's just a flag means "do not wait for any operations finish"
> >> > > > See no reason to set it true in that case.
> >> > > >
> >> > > > > If you delegate closing to afterTestsStopped this will affect
> only
> >> > > > > last test (method).
> >> > > > The idea is to stop all nodes at last test's method finish.
> >> > > >
> >> > > > >  Nodes that survive between tests can affect successive
> >> > > > tests.
> >> > > > Thats ok. we have a lot tests where nodes reusable between test's
> >> > > methods.
> >> > > >
> >> > > >
> >> > > > On Wed, Feb 7, 2018 at 1:20 PM, Dmitry Pavlov <
> >> dpavlov@gmail.com>
> >> > > > wrote:
> >> > > >
> >> > > > > Hi Igniters,
> >> > > > >
> >> > > > > IMO nodes that survive between tests is not general practice and
> >> I'm
> >> > > not
> >> > > > > sure is a best practice. I suggest to mark such tests with some
> >> > method
> >> > > > > overriden from AbstractTest.
> >> > > > >
> >> > > > > About cancel flag, please note stopAllGrids(boolean cancel)
> >> > > cancel=false
> >> > > > > allows to wait of checkpoint ends in case persistence enabled.
> >> > > > >
> >> > > > > I still suggest to avoid stopping any nodes by test, but
> validate
> >> not
> >> > > > > stopped node exist and fail test instead of siltent implicit
> >> actions.
> >> > > > >
> >> > 

Re: Stop nodes after test by default - IGNITE-6842

[Maxim Muzafarov]

Hi all,

I've made some changes based on our previous discusstions, please see PR
[1]:
1) Remove duplicated code for stopGrid (by index and by name);
2) Add new method that thows exception if not all grids haven't stopped
correctly;
3)  Change tests that have been affected by this changes;

Also, I have some thoughts for clarification:
1) beforeTestsStart() - I expect here in subtests that grids are not
started yet. Am I right?
2) I think we should call stopAllGrids in tearDown method. So, if in some
cases we'll override afterTestsStop in subclasses and forgot to call
super() it won't lead us to exception.

[1] https://github.com/apache/ignite/pull/3542
[2] https://ci.ignite.apache.org/viewModification.html?modId=717275
[3] https://issues.apache.org/jira/browse/IGNITE-6842


ср, 7 февр. 2018 г. в 18:28, Maxim Muzafarov :

> Thank you all,
>
> I'll add this comment's for JIRA ticket, if you don't mind.
>
> ср, 7 февр. 2018 г. в 15:16, Dmitry Pavlov :
>
>> Yes, this solution allows to cover both cases:
>> a) not stopped node from previous test and
>> b) allows to remove useless code that stops Ignite nodes from each test.
>>
>> ср, 7 февр. 2018 г. в 15:13, Anton Vinogradov :
>>
>> > Maxim,
>> >
>> > We discussed with Dima privately, and decided
>> >
>> > 1) We have to assert that there is no alive nodes at GridAbstractTest's
>> > beforeTestsStarted
>> > 2) We have to kill all alive nodes (without force) at GridAbstractTest's
>> > afterTestsStopped
>> > 3) In case of any exceptions at #2 we have to see test error
>> > 4) We can get rid of all useless stopAllGrids at GridAbstractTest's
>> > subclasses.
>> >
>> >
>> >
>> > On Wed, Feb 7, 2018 at 2:32 PM, Dmitry Pavlov 
>> > wrote:
>> >
>> > > > Let's just add stopAllGrids(flase) to GridAbstractTest 's
>> > > afterTestsStopped
>> > > method body.
>> > >
>> > > Can't agree with it becase implicit silent shutdown of nodes from test
>> > > framework may cause a lot of bugs introduced to Ignite.
>> > >
>> > > I think stop+test fail should occur.
>> > > In that case author of incorrect test or not consistent Ignite
>> shutdown
>> > > will see problem.
>> > >
>> > > 'Fail fast' if always better than hidding real problem under automatic
>> > > framework feature.
>> > >
>> > > ср, 7 февр. 2018 г. в 14:05, Anton Vinogradov <
>> avinogra...@gridgain.com
>> > >:
>> > >
>> > > > Hi all,
>> > > >
>> > > > > I've made some research about this problem and i think that in
>> > general
>> > > we
>> > > > > should move stopAllGrids method in GridAbstractTest class to
>> > > > > afterTestsStopped method with some changes. Am I right?
>> > > > Let's just add stopAllGrids(flase) to GridAbstractTest 's
>> > > > afterTestsStopped method
>> > > > body.
>> > > >
>> > > > > I have a question about stopAllGrids(boolean cancel) this "cancel"
>> > > > That's just a flag means "do not wait for any operations finish"
>> > > > See no reason to set it true in that case.
>> > > >
>> > > > > If you delegate closing to afterTestsStopped this will affect only
>> > > > > last test (method).
>> > > > The idea is to stop all nodes at last test's method finish.
>> > > >
>> > > > >  Nodes that survive between tests can affect successive
>> > > > tests.
>> > > > Thats ok. we have a lot tests where nodes reusable between test's
>> > > methods.
>> > > >
>> > > >
>> > > > On Wed, Feb 7, 2018 at 1:20 PM, Dmitry Pavlov <
>> dpavlov@gmail.com>
>> > > > wrote:
>> > > >
>> > > > > Hi Igniters,
>> > > > >
>> > > > > IMO nodes that survive between tests is not general practice and
>> I'm
>> > > not
>> > > > > sure is a best practice. I suggest to mark such tests with some
>> > method
>> > > > > overriden from AbstractTest.
>> > > > >
>> > > > > About cancel flag, please note stopAllGrids(boolean cancel)
>> > > cancel=false
>> > > > > allows to wait of checkpoint ends in case persistence enabled.
>> > > > >
>> > > > > I still suggest to avoid stopping any nodes by test, but validate
>> not
>> > > > > stopped node exist and fail test instead of siltent implicit
>> actions.
>> > > > >
>> > > > > Sincerely,
>> > > > > Dmitriy Pavlov
>> > > > >
>> > > > > ср, 7 февр. 2018 г. в 13:04, Andrey Kuznetsov > >:
>> > > > >
>> > > > > > Hi Maxim,
>> > > > > >
>> > > > > > Regarding your first question, the use of afterTestsStopped is
>> not
>> > > > enough
>> > > > > > to stop all nodes, since each individual test (method) can start
>> > > custom
>> > > > > set
>> > > > > > of notes during its operation, and this very test should stop
>> all
>> > > those
>> > > > > > nodes. If you delegate closing to afterTestsStopped this will
>> > affect
>> > > > only
>> > > > > > last test (method). Nodes that survive between tests can affect
>> > > > > successive
>> > > > > > tests.
>> > > > > >
>> > > > > > 2018-02-07 1:10 GMT+03:00 Maxim Muzafarov :
>> > > > > >
>> > > > > > > Hello,
>> > > > > > >
>> > 

[jira] [Created] (IGNITE-7789) Ignite Client Nodes: failed test IgniteClientReconnectApiExceptionTest.testErrorOnDisconnect()

[Sergey Chugunov (JIRA)]

Sergey Chugunov created IGNITE-7789:
---

 Summary: Ignite Client Nodes: failed test 
IgniteClientReconnectApiExceptionTest.testErrorOnDisconnect()
 Key: IGNITE-7789
 URL: https://issues.apache.org/jira/browse/IGNITE-7789
 Project: Ignite
  Issue Type: Bug
Reporter: Sergey Chugunov
 Fix For: 2.5


Test is flaky, success rate: 47.9%

May fail in two different ways.
*1 Assertion error in test code*

Rarely reproducible locally.

{noformat}
Caused by: class 
org.apache.ignite.internal.processors.cache.CachePartialUpdateCheckedException: 
Failed to update keys (retry update if possible).: [1]
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.onPrimaryError(GridNearAtomicAbstractUpdateFuture.java:397)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.onPrimaryResponse(GridNearAtomicSingleUpdateFuture.java:253)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.processNearAtomicUpdateResponse(GridDhtAtomicCache.java:3073)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$500(GridDhtAtomicCache.java:130)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$6.apply(GridDhtAtomicCache.java:285)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$6.apply(GridDhtAtomicCache.java:280)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1060)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:579)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:378)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:304)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:99)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:293)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1554)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1182)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:125)
at 
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1089)
at 
org.apache.ignite.internal.util.StripedExecutor$Stripe.run(StripedExecutor.java:499)
at java.lang.Thread.run(Thread.java:745)
Suppressed: class org.apache.ignite.IgniteCheckedException: Failed to 
update keys on primary node.
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.UpdateErrors.addFailedKeys(UpdateErrors.java:124)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateResponse.addFailedKeys(GridNearAtomicUpdateResponse.java:342)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1785)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1628)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.processNearAtomicUpdateRequest(GridDhtAtomicCache.java:3055)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$400(GridDhtAtomicCache.java:130)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$5.apply(GridDhtAtomicCache.java:266)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$5.apply(GridDhtAtomicCache.java:261)
... 12 more
Suppressed: java.lang.AssertionError: Assertion error on search row: 
org.apache.ignite.internal.processors.cache.tree.SearchRow@511c0beb
at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invoke(BPlusTree.java:1633)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:1199)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.invoke(IgniteCacheOffheapManagerImpl.java:345)
at 
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerUpdate(GridCacheMapEntry.java:1767)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateSingle(GridDhtAtomicCache.java:2420)
at 

Re: TeamCity. Ignite RDD tests

[Dmitry Pavlov]

It seems that tests I've previously muted were started in wrong configs.

Is it possible IgniteRDDSpec.IgniteRDD  became unit tests, which is started
with code compile?

This can be reason these tests appeared in suites which is not related to
IgniteRDD, such as Scala Examples.

чт, 22 февр. 2018 г. в 13:20, Nikolay Izhikov :

> Hello, Dmitriy
>
> I'm looked in TeamCity but not sure what should I do.
> Can you explain it to me, please?
>
> В Чт, 22/02/2018 в 10:13 +, Dmitry Pavlov пишет:
> > Hi Nikolay,
> >
> > It seems
> > IgniteRDDSpec.IgniteRDD  has appeared in configurations it is not
> expected
> > to run.
> >
> > Please see investigations assigned to you. What can we change to avoid
> > these tests to be included into run other suites?
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > пт, 16 февр. 2018 г. в 7:35, Nikolay Izhikov :
> >
> > > Hello, Igniters.
> > >
> > > I'm working on issue [1].
> > >
> > > Team City doesn't collect info about scalatest execution because of
> wrong
> > > pom.xml
> > > I'm fixed it in PR [3]
> > >
> > > It happens there is a 2 broken tests written in Scala - [4]
> > >
> > > 1. IgniteRDDSpec.IgniteRDD should successfully store data to ignite
> using
> > > saveValues
> > > 2. IgniteRDDSpec.IgniteRDD should successfully store data to ignite
> using
> > > saveValues with inline transformation
> > >
> > > It seems they are been here for a while.
> > > I propose to mute or disable it on TeamCity before merging my PR.
> > > I've created ticket for fixing tests - [5].
> > >
> > > Thoughts?
> > >
> > > [1] https://issues.apache.org/jira/browse/IGNITE-7042
> > >
> > > [2]
> > >
> https://ci.ignite.apache.org/viewLog.html?buildId=1096059=buildResultsDiv=IgniteTests24Java8_IgniteRdd
> > >
> > > [3] https://github.com/apache/ignite/pull/3530
> > >
> > > [4]
> > >
> https://ci.ignite.apache.org/viewLog.html?buildId=1095218=IgniteTests24Java8_IgniteRdd=testsInfo
> > >
> > > [5] https://issues.apache.org/jira/browse/IGNITE-7727

Re: TeamCity. Ignite RDD tests

[Vyacheslav Daradur]

Hi, Nikolay

Please login to TeamCity and choose "My Investigations" [1] in account menu.

[1] https://ci.ignite.apache.org/investigations.html?init=1

On Thu, Feb 22, 2018 at 1:25 PM, Vyacheslav Daradur  wrote:
> Hi, Nikolay
>
> Please login to TeamCity and choose "My
>
>
> On Thu, Feb 22, 2018 at 1:20 PM, Nikolay Izhikov  wrote:
>> Hello, Dmitriy
>>
>> I'm looked in TeamCity but not sure what should I do.
>> Can you explain it to me, please?
>>
>> В Чт, 22/02/2018 в 10:13 +, Dmitry Pavlov пишет:
>>> Hi Nikolay,
>>>
>>> It seems
>>> IgniteRDDSpec.IgniteRDD  has appeared in configurations it is not expected
>>> to run.
>>>
>>> Please see investigations assigned to you. What can we change to avoid
>>> these tests to be included into run other suites?
>>>
>>> Sincerely,
>>> Dmitriy Pavlov
>>>
>>> пт, 16 февр. 2018 г. в 7:35, Nikolay Izhikov :
>>>
>>> > Hello, Igniters.
>>> >
>>> > I'm working on issue [1].
>>> >
>>> > Team City doesn't collect info about scalatest execution because of wrong
>>> > pom.xml
>>> > I'm fixed it in PR [3]
>>> >
>>> > It happens there is a 2 broken tests written in Scala - [4]
>>> >
>>> > 1. IgniteRDDSpec.IgniteRDD should successfully store data to ignite using
>>> > saveValues
>>> > 2. IgniteRDDSpec.IgniteRDD should successfully store data to ignite using
>>> > saveValues with inline transformation
>>> >
>>> > It seems they are been here for a while.
>>> > I propose to mute or disable it on TeamCity before merging my PR.
>>> > I've created ticket for fixing tests - [5].
>>> >
>>> > Thoughts?
>>> >
>>> > [1] https://issues.apache.org/jira/browse/IGNITE-7042
>>> >
>>> > [2]
>>> > https://ci.ignite.apache.org/viewLog.html?buildId=1096059=buildResultsDiv=IgniteTests24Java8_IgniteRdd
>>> >
>>> > [3] https://github.com/apache/ignite/pull/3530
>>> >
>>> > [4]
>>> > https://ci.ignite.apache.org/viewLog.html?buildId=1095218=IgniteTests24Java8_IgniteRdd=testsInfo
>>> >
>>> > [5] https://issues.apache.org/jira/browse/IGNITE-7727
>
>
>
> --
> Best Regards, Vyacheslav D.



-- 
Best Regards, Vyacheslav D.

Re: TeamCity. Ignite RDD tests

[Vyacheslav Daradur]

Hi, Nikolay

Please login to TeamCity and choose "My


On Thu, Feb 22, 2018 at 1:20 PM, Nikolay Izhikov  wrote:
> Hello, Dmitriy
>
> I'm looked in TeamCity but not sure what should I do.
> Can you explain it to me, please?
>
> В Чт, 22/02/2018 в 10:13 +, Dmitry Pavlov пишет:
>> Hi Nikolay,
>>
>> It seems
>> IgniteRDDSpec.IgniteRDD  has appeared in configurations it is not expected
>> to run.
>>
>> Please see investigations assigned to you. What can we change to avoid
>> these tests to be included into run other suites?
>>
>> Sincerely,
>> Dmitriy Pavlov
>>
>> пт, 16 февр. 2018 г. в 7:35, Nikolay Izhikov :
>>
>> > Hello, Igniters.
>> >
>> > I'm working on issue [1].
>> >
>> > Team City doesn't collect info about scalatest execution because of wrong
>> > pom.xml
>> > I'm fixed it in PR [3]
>> >
>> > It happens there is a 2 broken tests written in Scala - [4]
>> >
>> > 1. IgniteRDDSpec.IgniteRDD should successfully store data to ignite using
>> > saveValues
>> > 2. IgniteRDDSpec.IgniteRDD should successfully store data to ignite using
>> > saveValues with inline transformation
>> >
>> > It seems they are been here for a while.
>> > I propose to mute or disable it on TeamCity before merging my PR.
>> > I've created ticket for fixing tests - [5].
>> >
>> > Thoughts?
>> >
>> > [1] https://issues.apache.org/jira/browse/IGNITE-7042
>> >
>> > [2]
>> > https://ci.ignite.apache.org/viewLog.html?buildId=1096059=buildResultsDiv=IgniteTests24Java8_IgniteRdd
>> >
>> > [3] https://github.com/apache/ignite/pull/3530
>> >
>> > [4]
>> > https://ci.ignite.apache.org/viewLog.html?buildId=1095218=IgniteTests24Java8_IgniteRdd=testsInfo
>> >
>> > [5] https://issues.apache.org/jira/browse/IGNITE-7727



-- 
Best Regards, Vyacheslav D.

Re: TeamCity. Ignite RDD tests

[Nikolay Izhikov]

Hello, Dmitriy

I'm looked in TeamCity but not sure what should I do.
Can you explain it to me, please?

В Чт, 22/02/2018 в 10:13 +, Dmitry Pavlov пишет:
> Hi Nikolay,
> 
> It seems
> IgniteRDDSpec.IgniteRDD  has appeared in configurations it is not expected
> to run.
> 
> Please see investigations assigned to you. What can we change to avoid
> these tests to be included into run other suites?
> 
> Sincerely,
> Dmitriy Pavlov
> 
> пт, 16 февр. 2018 г. в 7:35, Nikolay Izhikov :
> 
> > Hello, Igniters.
> > 
> > I'm working on issue [1].
> > 
> > Team City doesn't collect info about scalatest execution because of wrong
> > pom.xml
> > I'm fixed it in PR [3]
> > 
> > It happens there is a 2 broken tests written in Scala - [4]
> > 
> > 1. IgniteRDDSpec.IgniteRDD should successfully store data to ignite using
> > saveValues
> > 2. IgniteRDDSpec.IgniteRDD should successfully store data to ignite using
> > saveValues with inline transformation
> > 
> > It seems they are been here for a while.
> > I propose to mute or disable it on TeamCity before merging my PR.
> > I've created ticket for fixing tests - [5].
> > 
> > Thoughts?
> > 
> > [1] https://issues.apache.org/jira/browse/IGNITE-7042
> > 
> > [2]
> > https://ci.ignite.apache.org/viewLog.html?buildId=1096059=buildResultsDiv=IgniteTests24Java8_IgniteRdd
> > 
> > [3] https://github.com/apache/ignite/pull/3530
> > 
> > [4]
> > https://ci.ignite.apache.org/viewLog.html?buildId=1095218=IgniteTests24Java8_IgniteRdd=testsInfo
> > 
> > [5] https://issues.apache.org/jira/browse/IGNITE-7727

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

[GitHub] ignite pull request #3556: IGNITE-3077: Test fixed

[asfgit]

Github user asfgit closed the pull request at:

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


---

Re: TeamCity. Ignite RDD tests

[Dmitry Pavlov]

Hi Nikolay,

It seems
IgniteRDDSpec.IgniteRDD  has appeared in configurations it is not expected
to run.

Please see investigations assigned to you. What can we change to avoid
these tests to be included into run other suites?

Sincerely,
Dmitriy Pavlov

пт, 16 февр. 2018 г. в 7:35, Nikolay Izhikov :

> Hello, Igniters.
>
> I'm working on issue [1].
>
> Team City doesn't collect info about scalatest execution because of wrong
> pom.xml
> I'm fixed it in PR [3]
>
> It happens there is a 2 broken tests written in Scala - [4]
>
> 1. IgniteRDDSpec.IgniteRDD should successfully store data to ignite using
> saveValues
> 2. IgniteRDDSpec.IgniteRDD should successfully store data to ignite using
> saveValues with inline transformation
>
> It seems they are been here for a while.
> I propose to mute or disable it on TeamCity before merging my PR.
> I've created ticket for fixing tests - [5].
>
> Thoughts?
>
> [1] https://issues.apache.org/jira/browse/IGNITE-7042
>
> [2]
> https://ci.ignite.apache.org/viewLog.html?buildId=1096059=buildResultsDiv=IgniteTests24Java8_IgniteRdd
>
> [3] https://github.com/apache/ignite/pull/3530
>
> [4]
> https://ci.ignite.apache.org/viewLog.html?buildId=1095218=IgniteTests24Java8_IgniteRdd=testsInfo
>
> [5] https://issues.apache.org/jira/browse/IGNITE-7727

[jira] [Created] (IGNITE-7788) Data loss after cold restart with PDS and cache group change

[Alexandr Kuramshin (JIRA)]

Alexandr Kuramshin created IGNITE-7788:
--

 Summary: Data loss after cold restart with PDS and cache group 
change
 Key: IGNITE-7788
 URL: https://issues.apache.org/jira/browse/IGNITE-7788
 Project: Ignite
  Issue Type: Bug
  Components: persistence
Affects Versions: 2.3
Reporter: Alexandr Kuramshin


Reproduced by improved test 
{{IgnitePdsCacheRestoreTest.testRestoreAndNewCache6}}



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

[jira] [Created] (IGNITE-7786) Changing baseline topology on big cluster may have error in control.sh utility

[Dmitry Sherstobitov (JIRA)]

Dmitry Sherstobitov created IGNITE-7786:
---

 Summary: Changing baseline topology on big cluster may have error 
in control.sh utility
 Key: IGNITE-7786
 URL: https://issues.apache.org/jira/browse/IGNITE-7786
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.3
Reporter: Dmitry Sherstobitov


Looks like there is hardcoded timeout for waiting result of change baseline 
operation

In big cluster there is following behaviour: (154 nodes)
 # Set new baseline topology version
 # Utility connects, but then fails by connection error
 # Cluster successfully activated



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

[jira] [Created] (IGNITE-7787) Better error reporting when issuing PDS corruptions.

[Alexei Scherbakov (JIRA)]

Alexei Scherbakov created IGNITE-7787:
-

 Summary: Better error reporting when issuing PDS corruptions.
 Key: IGNITE-7787
 URL: https://issues.apache.org/jira/browse/IGNITE-7787
 Project: Ignite
  Issue Type: Improvement
Affects Versions: 2.3
Reporter: Alexei Scherbakov
 Fix For: 2.5


If PDS is corrupted in any way and update hits bad page shown error message is 
not very helping, usually something like "Failed to get page IO instance (page 
content is corrupted)"

For corruptions related to CacheDataRowStore error should contain information 
about how to fix the issue: clear data for cache/group and restart node for 
partition reloading.

For corruptions related to H2Tree (SQL indexes) error should contain suggestion 
to remove index.bin for broken partition and restart node allowing index to 
rebuild.





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

[GitHub] ignite pull request #3556: IGNITE-3077: Test fixed

[nizhikov]

GitHub user nizhikov opened a pull request:

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

IGNITE-3077: Test fixed



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

$ git pull https://github.com/nizhikov/ignite IGNITE-3077

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

https://github.com/apache/ignite/pull/3556.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 #3556


commit 0ca135a02aaad79260af140a709e0b2fcb60cab0
Author: Nikolay Izhikov 
Date:   2018-02-22T09:24:10Z

IGNITE-3077: Test fixed




---

[GitHub] ignite pull request #3541: IGNITE-7750 Fixed testMultiThreadStatisticsEnable...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] ignite pull request #3540: IGNITE-7749 Fixed testDiscoCacheReuseOnNodeJoin t...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] ignite pull request #3529: IGNITE-7698: Page read during replacement should ...

[asfgit]

Github user asfgit closed the pull request at:

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


---

Re: Nodes which started in separate JVM couldn't stop properly (in tests)

[Vyacheslav Daradur]

Hi Igniters!

I have investigated the issue [1] and found that stopping node in
separate JVM may stuck thread or leave system process alive after test
finished.
The main reason is *StopGridTask* that we send from node in local JVM
to node in separate JVM via remote computing.
We send job synchronously to be sure that node will be stopped, but
job calls synchronously *G.stop(igniteInstanceName, cancel))* with
*cancel = false*, that means node must wait to compute jobs before it
goes down what leads to some kind of deadlock. Using of *cancel =
true* would solve the issue but may break some tests’ logic, for this
reason, I've reworked the method’s synchronization logic [2].

We have not noticed that before because we use only *stopAllGrids()*
in out tests which stop local JVM without waiting for nodes in other
JVMs.
I believe this fix should reduce the number of flaky tests on
TeamCity, especially which fails because of a cluster from the
previous test has not been stopped properly.

Ci.tests [3] look a bit better than in master.
Please review prepared PR [2] and share your thoughts.

[1] https://issues.apache.org/jira/browse/IGNITE-5910
[2] https://github.com/apache/ignite/pull/2382
[3] https://ci.ignite.apache.org/viewLog.html?buildId=1105939


On Fri, Aug 4, 2017 at 11:41 AM, Vyacheslav Daradur  wrote:
> Hi Igniters,
>
> Working on my task I found a bug at call the method #stopGrid(name),
> it produced ClassCastException. I created a ticket[1].
>
> After it was fixed[2] I saw that nodes which was started in a separate JVM
> could stay in process of operation system.
> It was fixed too, but not sure is it fixed in proper way or not.
>
> Could someone review it?
>
> [1] https://issues.apache.org/jira/browse/IGNITE-5910
> [2] https://github.com/apache/ignite/pull/2382
>
> --
> Best Regards, Vyacheslav D.



-- 
Best Regards, Vyacheslav D.

[jira] [Created] (IGNITE-7785) SQL query with COUNT and UNION in sub-query produces JdbcSQLException

[Pavel Vinokurov (JIRA)]

Pavel Vinokurov created IGNITE-7785:
---

 Summary: SQL query with COUNT and UNION in sub-query produces 
JdbcSQLException
 Key: IGNITE-7785
 URL: https://issues.apache.org/jira/browse/IGNITE-7785
 Project: Ignite
  Issue Type: Bug
  Components: sql
Affects Versions: 2.3, 2.1
Reporter: Pavel Vinokurov


SQL initial script:

CREATE TABLE Person(id INTEGER PRIMARY KEY, company_id INTEGER);
CREATE TABLE Company(id INTEGER PRIMARY KEY, name VARCHAR);
INSERT INTO Person(id,company_id) VALUES (1, 1), (2, 2), (3, 3);
INSERT INTO Company(id,name) VALUES (1,'n1'), (2,'n2'), (3,'n3');

SQL Query:

SELECT count(*) FROM person p
LEFT JOIN (select id from company union select id from company) as c on 
c.id=p.company_id

SQL error:

Caused by: org.h2.jdbc.JdbcSQLException: Column "P__Z0.COMPANY_ID" must be in 
the GROUP BY list; SQL statement:
SELECT
P__Z0.COMPANY_ID __C0_0,
COUNT(*) __C0_1
FROM PUBLIC.PERSON P__Z0 [90016-195]

 



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