Re: Ignite 2.6 emergency release suggestion

[Alexey Goncharuk]

Ignite-2.6 branch is created, all mentioned fixes were pushed. I also
included the fix for [1] because the issue could lead to a hanging PME in
some circumstances.
Will trigger TC shortly.

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

вт, 5 июн. 2018 г. в 21:18, Ivan Rakov :

> I'd like to add that first issue [1] has a follow-up fix [2]. It should
> be backported along with the first fix.
>
> [1] - https://issues.apache.org/jira/browse/IGNITE-8476
> [2] - https://issues.apache.org/jira/browse/IGNITE-8682
>
> Best Regards,
> Ivan Rakov
>
> On 05.06.2018 20:57, Ivan Rakov wrote:
> > I agree in general. First issue is severe usability issue, while
> > second one may fail crash recovery and cause data loss. This makes AI
> > 2.5 not recommended for using.
> >
> > Best Regards,
> > Ivan Rakov
> >
> > On 05.06.2018 19:39, Alexey Goncharuk wrote:
> >> Igniters,
> >>
> >> Recently we've stumbled across the following two tickets [1], [2] which
> >> seem to be very critical from the usability and stability points of
> >> view.
> >> The [1] results in clients not being able to update persistence-enabled
> >> clusters unless the client configuration is identical to the server
> >> configuration. The [2] may result in incorrect node state recovery and
> >> either corrupted storage or lost updates.
> >>
> >> I suggest we make an emergency release (to my knowledge, we already had
> >> such a practice with Ignite 2.3) and include the fixes for both of the
> >> issues to it.
> >>
> >> Thoughts?
> >>
> >> [1] https://issues.apache.org/jira/browse/IGNITE-8476
> >> [2] https://issues.apache.org/jira/browse/IGNITE-8685
> >>
> >> --AG
> >>
> >
>
>

[GitHub] ignite pull request #4177: IGNITE-8179: Fluky test.

[BiryukovVA]

GitHub user BiryukovVA opened a pull request:

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

IGNITE-8179: Fluky test.



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

$ git pull https://github.com/BiryukovVA/ignite IGNITE-8179

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

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


commit 543d6af8c3a458700fda6b2958de2634e14c2707
Author: Vitaliy Biryukov 
Date:   2018-06-09T17:38:12Z

GNITE-8179: Test fixed.

commit 0a25439bc1d79bc2edfc1fab15d68f33999685ad
Author: Vitaliy Biryukov 
Date:   2018-06-09T17:41:59Z

GNITE-8179: For TC testing.




---

[GitHub] ignite pull request #4176: Ignite 2.4.5.b3

[ezhuravl]

GitHub user ezhuravl opened a pull request:

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

Ignite 2.4.5.b3



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

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

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

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


commit 915dd2966084d78f7b4f3d482e6bd25f860c1e23
Author: Alexey Goncharuk 
Date:   2018-01-31T08:22:26Z

IGNITE-7569 Fixed index rebuild future - Fixes #3454.

commit 8ea8609259039852ab0c26f26ac528c1ffae7c94
Author: Alexey Goncharuk 
Date:   2018-01-31T08:24:57Z

IGNITE-7577 Fixing public API active flag on baseline changes - Fixes #3455.

commit c8ce1f66e98b3174d771a3b801a2538499dc2c3d
Author: Ivan Rakov 
Date:   2018-01-31T09:51:09Z

IGNITE-7475 Improved VerifyBackupPartitionsTask to calculate partition 
hashes in parallel - Fixes #3407.

Signed-off-by: Alexey Goncharuk 

commit 258ff4299da20122d7c387cb8579264035c93c18
Author: Alexey Goncharuk 
Date:   2018-01-31T13:52:24Z

IGNITE-7573 Fixed full API tests to be compliant with baseline topology

commit 254ed3a9c32d092702a0461509bf867cbd7cdee6
Author: Alexey Kuznetsov 
Date:   2018-02-01T08:22:53Z

ignite-2.4.0 Update version.

(cherry picked from commit 2e43749)

commit c1a9c0a404d77fba08170bedf14844f87abe3028
Author: Alexey Goncharuk 
Date:   2018-02-01T10:17:28Z

IGNITE-7569 Fixing index rebuild future

commit e43799ce70cdbe03d9e206381d1d5138b820b075
Author: Alexey Goncharuk 
Date:   2018-02-01T13:39:17Z

IGNITE-7520 Provide util-methods to get baseline from context - Fixes #3431.

commit 8f5fc7cfb0624cf2048efad38dfff32f782116e8
Author: Sergey Chugunov 
Date:   2018-02-02T08:24:29Z

IGNITE-7580 Fix compatibilityMode flag consistency

This closes #3466

(cherry picked from commit 8f2045e)

commit d3ddd50cb2b889173176b6c47c9ff61410e1d909
Author: Ilya Lantukh 
Date:   2018-02-07T10:33:28Z

IGNITE-7514 Affinity assignment should be recalculated when primary node is 
not OWNER

(cherry picked from commit faf50f1)

commit d3745e9d0a3ff5a64fba494889b7e2605f3af6bb
Author: Alexey Goncharuk 
Date:   2018-02-07T18:10:32Z

IGNITE-7639 Fixed NPE

commit f7c16855ba802d9d47048521aec7e14285e4a281
Author: Pavel Kovalenko 
Date:   2018-02-09T13:55:15Z

IGNITE-7540 Prevent page memory metadata corruption during checkpoint and 
group destroying. - Fixes #3490.

Signed-off-by: Alexey Goncharuk 

commit c92f167fc491078f02b9f94fe89edafc2902ebc2
Author: ilantukh 
Date:   2018-02-14T12:40:13Z

Updated version in properties.

commit 1ecf348dd429cf7861b414e0e5a7776b72dba281
Author: Sergey Chugunov 
Date:   2018-02-16T13:21:12Z

IGNITE-7699 BinaryMetadata exchange should not be triggered if metadata was 
not updated - Fixes #3523.

Signed-off-by: Alexey Goncharuk 

(cherry-picked from commit bcd3881)

commit 2458bd08a5b501b3eeb5caf0ae6dcaa2bcccd915
Author: EdShangGG 
Date:   2018-02-16T13:29:49Z

IGNITE-7676 Add affinity version to snapshot plugin stub - Fixes #3510.

Signed-off-by: Alexey Goncharuk 
(cherry picked from commit b6d21fb)

commit bfdcda7a2a6b5cf64f15ed169d2beb886f131fac
Author: EdShangGG 
Date:   2018-02-12T16:36:30Z

IGNITE-7626 Unify code in test which cleans up persistence directories - 
Fixes #3477.

Signed-off-by: Alexey Goncharuk 
(cherry picked from commit a0997b9)

commit 2e92e0094b270aa8489e66d94bfcf15eadabfb4f
Author: EdShangGG 
Date:   2018-02-12T18:44:10Z

IGNITE-7626 Unify code in test which clean up persistence directories - 
Fixes #3512.

Signed-off-by: Alexey Goncharuk 
(cherry picked from commit 6f6f8dd)

commit 3f86c127c78065999663a4fc4eaedb5e5d4bee1c
Author: EdShangGG 
Date:   2018-02-12T18:26:31Z

compilation fix

commit 0b9322c566f9b464291854142ac02495bd1817e4
Author: gg-shq 
Date:   2018-02-07T11:28:04Z

IGNITE-6917: Implemented SQL COPY command.

commit c5e386ca96750213bddcd98d0af0c589fee476ca
Author: gg-shq 
Date:   2018-02-07T15:31:27Z

IGNITE-7586: Added COPY command into the JDBC example.

This closes #3485

commit d8203e2d81f8fbf0f7fbe5e710c9908f2fcb8307
Author: shq 
Date:   2018-02-15T10:36:00Z

IGNITE-7709: SQL COPY command: make sure file name is always quoted. This 
closes #3526.

commit 1185993ee7cd83695388f698f18f95b43e15de06
Author: devozerov 
Date:   2018-02-15T11:00:42Z

IGNITE-7714: SQL COPY command: fixed "Table not found" issue on the client 
node.

commit 88c8bdcc0dc2fdf2b2b22562a6b30031e053f671
Author: devozerov 
Date:   2018-02-16T14:54:24Z

IGNITE-7737: SQL COPY: renamed BUFFER_SIZE to PACKET_SIZE. This closes 
#3533.

commit bc331f9de716c30d6f733e28821ab44da7ed0cf7
Author: Alexander Paschenko 

[GitHub] ignite pull request #4175: Ignite 2.4.6

[slukyano]

GitHub user slukyano opened a pull request:

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

Ignite 2.4.6



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

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

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

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


commit 254ed3a9c32d092702a0461509bf867cbd7cdee6
Author: Alexey Kuznetsov 
Date:   2018-02-01T08:22:53Z

ignite-2.4.0 Update version.

(cherry picked from commit 2e43749)

commit c1a9c0a404d77fba08170bedf14844f87abe3028
Author: Alexey Goncharuk 
Date:   2018-02-01T10:17:28Z

IGNITE-7569 Fixing index rebuild future

commit e43799ce70cdbe03d9e206381d1d5138b820b075
Author: Alexey Goncharuk 
Date:   2018-02-01T13:39:17Z

IGNITE-7520 Provide util-methods to get baseline from context - Fixes #3431.

commit 8f5fc7cfb0624cf2048efad38dfff32f782116e8
Author: Sergey Chugunov 
Date:   2018-02-02T08:24:29Z

IGNITE-7580 Fix compatibilityMode flag consistency

This closes #3466

(cherry picked from commit 8f2045e)

commit d3ddd50cb2b889173176b6c47c9ff61410e1d909
Author: Ilya Lantukh 
Date:   2018-02-07T10:33:28Z

IGNITE-7514 Affinity assignment should be recalculated when primary node is 
not OWNER

(cherry picked from commit faf50f1)

commit d3745e9d0a3ff5a64fba494889b7e2605f3af6bb
Author: Alexey Goncharuk 
Date:   2018-02-07T18:10:32Z

IGNITE-7639 Fixed NPE

commit f7c16855ba802d9d47048521aec7e14285e4a281
Author: Pavel Kovalenko 
Date:   2018-02-09T13:55:15Z

IGNITE-7540 Prevent page memory metadata corruption during checkpoint and 
group destroying. - Fixes #3490.

Signed-off-by: Alexey Goncharuk 

commit c92f167fc491078f02b9f94fe89edafc2902ebc2
Author: ilantukh 
Date:   2018-02-14T12:40:13Z

Updated version in properties.

commit 1ecf348dd429cf7861b414e0e5a7776b72dba281
Author: Sergey Chugunov 
Date:   2018-02-16T13:21:12Z

IGNITE-7699 BinaryMetadata exchange should not be triggered if metadata was 
not updated - Fixes #3523.

Signed-off-by: Alexey Goncharuk 

(cherry-picked from commit bcd3881)

commit 2458bd08a5b501b3eeb5caf0ae6dcaa2bcccd915
Author: EdShangGG 
Date:   2018-02-16T13:29:49Z

IGNITE-7676 Add affinity version to snapshot plugin stub - Fixes #3510.

Signed-off-by: Alexey Goncharuk 
(cherry picked from commit b6d21fb)

commit bfdcda7a2a6b5cf64f15ed169d2beb886f131fac
Author: EdShangGG 
Date:   2018-02-12T16:36:30Z

IGNITE-7626 Unify code in test which cleans up persistence directories - 
Fixes #3477.

Signed-off-by: Alexey Goncharuk 
(cherry picked from commit a0997b9)

commit 2e92e0094b270aa8489e66d94bfcf15eadabfb4f
Author: EdShangGG 
Date:   2018-02-12T18:44:10Z

IGNITE-7626 Unify code in test which clean up persistence directories - 
Fixes #3512.

Signed-off-by: Alexey Goncharuk 
(cherry picked from commit 6f6f8dd)

commit 3f86c127c78065999663a4fc4eaedb5e5d4bee1c
Author: EdShangGG 
Date:   2018-02-12T18:26:31Z

compilation fix

commit 0b9322c566f9b464291854142ac02495bd1817e4
Author: gg-shq 
Date:   2018-02-07T11:28:04Z

IGNITE-6917: Implemented SQL COPY command.

commit c5e386ca96750213bddcd98d0af0c589fee476ca
Author: gg-shq 
Date:   2018-02-07T15:31:27Z

IGNITE-7586: Added COPY command into the JDBC example.

This closes #3485

commit d8203e2d81f8fbf0f7fbe5e710c9908f2fcb8307
Author: shq 
Date:   2018-02-15T10:36:00Z

IGNITE-7709: SQL COPY command: make sure file name is always quoted. This 
closes #3526.

commit 1185993ee7cd83695388f698f18f95b43e15de06
Author: devozerov 
Date:   2018-02-15T11:00:42Z

IGNITE-7714: SQL COPY command: fixed "Table not found" issue on the client 
node.

commit 88c8bdcc0dc2fdf2b2b22562a6b30031e053f671
Author: devozerov 
Date:   2018-02-16T14:54:24Z

IGNITE-7737: SQL COPY: renamed BUFFER_SIZE to PACKET_SIZE. This closes 
#3533.

commit bc331f9de716c30d6f733e28821ab44da7ed0cf7
Author: Alexander Paschenko 
Date:   2018-02-16T20:22:03Z

IGNITE-7253: Streaming mode for JDBC thin driver. This closes #3499.

(cherry picked from commit 692e488)

commit 6707ac0792c63efd073dd6c26edb5c6a1f6b7c3f
Author: dpavlov 
Date:   2018-02-13T17:19:31Z

IGNITE-7695: Enable Ignite Update Notifier tests - Fixes #3516.

Signed-off-by: Alexey Goncharuk 

(cherry-picked from commit e3f2259)

commit 9ba660cab2799f0606ff59997075f764b367b2aa
Author: devozerov 
Date:   2018-02-19T14:49:35Z

Release notes for COPY and streaming.

commit 9ef88099d844f7d32df747d6e3c6fd00c64dd684
Author: Ilya Lantukh 
Date:   2018-02-19T15:06:56Z

IGNITE-7594 Fixed performance drop after WAL optimization for FSYNC mode by 
reverting the old implementation - Fixes #3521.

[GitHub] ignite pull request #3762: Ignite-7772-review

[agura]

Github user agura closed the pull request at:

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


---

[GitHub] ignite pull request #3904: Ignite 2.5.1

[agura]

Github user agura closed the pull request at:

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


---

[GitHub] ignite pull request #4041: Apache ignite 2.5 release notes

[agura]

Github user agura closed the pull request at:

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


---

[GitHub] ignite pull request #3984: IGNITE-8471 Dependencies upgraded

[agura]

Github user agura closed the pull request at:

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


---

[GitHub] ignite pull request #4174: IGNITE-8073 Cache read metric is calculated incor...

[voipp]

GitHub user voipp opened a pull request:

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

IGNITE-8073 Cache read metric is calculated incorrectly in atomic cache.



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

$ git pull https://github.com/voipp/ignite IGNITE-8073

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

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


commit e404757231de50e15416dae2f4795e17e1d777c4
Author: voipp 
Date:   2018-06-09T14:36:11Z

#draft




---

[jira] [Created] (IGNITE-8771) OutOfMemory in Cache2 suite in master branch on TC

[Sergey Chugunov (JIRA)]

Sergey Chugunov created IGNITE-8771:
---

 Summary: OutOfMemory in Cache2 suite in master branch on TC
 Key: IGNITE-8771
 URL: https://issues.apache.org/jira/browse/IGNITE-8771
 Project: Ignite
  Issue Type: Bug
Reporter: Sergey Chugunov
 Fix For: 2.6


OutOfMemory error happened in Cache2 suite for the first time in a while: 
[https://ci.ignite.apache.org/viewLog.html?buildId=1372380=buildResultsDiv=IgniteTests24Java8_Cache2]

Recent history doesn't contain any OOMs or execution timeouts for this suite: 
[TC 
link|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Cache2_IgniteTests24Java8=%3Cdefault%3E=buildTypeStatusDiv]



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

[jira] [Created] (IGNITE-8770) OutOfMemory in Queries1 suite in master branch on TC

[Sergey Chugunov (JIRA)]

Sergey Chugunov created IGNITE-8770:
---

 Summary: OutOfMemory in Queries1 suite in master branch on TC
 Key: IGNITE-8770
 URL: https://issues.apache.org/jira/browse/IGNITE-8770
 Project: Ignite
  Issue Type: Bug
 Environment: OutOfMemory happened for the first time in a while for 
this suite: [TC 
link|https://ci.ignite.apache.org/viewLog.html?buildId=1372426=buildResultsDiv=IgniteTests24Java8_Queries1]

No execution timeouts or OOM errors in recent history: [TC 
link|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Queries1_IgniteTests24Java8=%3Cdefault%3E=buildTypeStatusDiv]
Reporter: Sergey Chugunov
 Fix For: 2.6






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

[GitHub] ignite pull request #4123: 1.9.13 stale

[antkr]

GitHub user antkr reopened a pull request:

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

1.9.13 stale

CI partial tests

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

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

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

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


commit 024a01d6bf91b4f301c4aee7f4a747e810a9a30b
Author: nikolay_tikhonov 
Date:   2017-07-05T15:58:00Z

Merged 1.7.12 into 1.8.9

Signed-off-by: nikolay_tikhonov 

commit 3536a58982e4c264bb72b2ccc1953049d2b5c67f
Author: Alexey Kukushkin 
Date:   2017-07-05T16:36:41Z

IGNITE-4901 Decrease logging level for DataStremer retry

commit 6d3a3ff2d99697882232070e715928336a9180cd
Author: Alexey Kukushkin 
Date:   2017-07-05T17:05:02Z

Fixed merge conflicts

commit aedc6aa8b17a39a6460c4b7f69255cd07d635bfb
Author: nikolay_tikhonov 
Date:   2017-07-05T17:42:15Z

Merge branch 'ignite-1.7.12' into ignite-1.9.4

Signed-off-by: nikolay_tikhonov 

commit acfc400b22738fa46397d392f88d49614e687969
Author: nikolay_tikhonov 
Date:   2017-07-05T17:42:48Z

Merge branch 'ignite-1.7.12' into ignite-1.9.4

Signed-off-by: nikolay_tikhonov 

commit 8dea19ba41bb9eda16f47933b2c46a081116d5f7
Author: Andrey V. Mashenkov 
Date:   2017-07-06T09:02:07Z

Minor fix.

commit f208f434f944196d531a1b51066dfe8d6394d739
Author: Andrey V. Mashenkov 
Date:   2017-07-06T12:17:50Z

Test fixed "IGNITE-5390: Bug in 
IgniteCacheTxStoreSessionWriteBehindCoalescingTest."

commit 355a5283559c885f57c4557bba2c6d9170a9b5fc
Author: mcherkasov 
Date:   2017-06-30T17:23:55Z

IGNITE-5554 ServiceProcessor may process failed reassignments in timeout 
thread

commit 92aa7c6e3c0d9b5cc68002433861b175d54f9421
Author: agura 
Date:   2017-07-04T13:56:40Z

ignite-5685 JDBC prepared statement shouldn't clear parameters after 
execution

commit 9165a0f93b5173b543cc6b4fad5fde37bd215f91
Author: Slava Koptilin 
Date:   2017-07-07T12:35:33Z

ignite-5562: assert statements were changed to the 'if' blocks

commit d9fc20a61d5ac0a6e63b26faa7fa0af753b2fa06
Author: Dmitriy Govorukhin 
Date:   2017-04-07T11:28:22Z

IGNITE-4889 - Changed Hibernate integration to use custom keys

(cherry picked from commit 6b62a20)

commit 16067300c9124b79bfee42139eb881ae585c0914
Author: Dmitriy Govorukhin 
Date:   2017-04-07T11:28:22Z

IGNITE-4889 - Changed Hibernate integration to use custom keys

(cherry picked from commit 6b62a20)

commit c82e25d67a2f6825a27d26933199a436f6eabba2
Author: Dmitriy Govorukhin 
Date:   2017-04-07T11:28:22Z

IGNITE-4889 - Changed Hibernate integration to use custom keys

(cherry picked from commit 6b62a20)

commit a352951d91edde9c0029a8bf435d61b4a7cd8c11
Author: Andrey V. Mashenkov 
Date:   2017-07-04T17:24:52Z

IGNITE-4831: Add an option to disable MBeans.

commit e4d141e97ab4ec34b5fe6a7bc599413223944438
Author: dkarachentsev 
Date:   2017-07-14T11:40:02Z

IGNITE-5103 - Server drops client node from cluster when no heartbeat 
messages received in interval heartBeatsFrequency * maxMissedClientHeartBeats.

commit 45573945066113fd29548699f23c2bc9f22cef36
Author: Tikhonov Nikolay 
Date:   2017-06-21T14:55:05Z

ignite-5489 Fixed possible connection leaks when loadPreviousValue set to 
true

commit 37535634ef3325aaf9923fd17d24038dfd5cee38
Author: agura 
Date:   2017-07-11T13:24:54Z

ignite-5722 Cache entries stay in onheap after scan query execution for 
OFFHEAP_TIRED cache with expiry policy

commit c3e2eebeccbdc4bb3a7a0a70d09a8a7b63399c2c
Author: Evgenii Zhuravlev 
Date:   2017-07-18T15:50:48Z

IGNITE 5776 Add option to turn on filter reachable addresses in 
TcpCommunicationSpi

commit 97d3f42c1c95a6aafce1d0c300ccfe6708398c17
Author: shtykh_roman 
Date:   2016-09-07T05:35:31Z

IGNITE-3809: Fix for ArrayIndexOutOfBoundsException in GridUnsafeLru.

(cherry picked from commit 31b9bb8)

commit c2062d52a227dda5afee560d80c3bb4dd2ce09eb
Author: dkarachentsev 
Date:   2017-07-19T05:41:46Z

Remove empty test_utils.cpp

commit 45cbba4853bab1ba4ffe2ea0d3add99a9d454aab
Author: dkarachentsev 
Date:   2017-07-19T07:44:04Z

IGNITE-5768 - Retry resolving class name from marshaller cache and 
.classname file.

commit f24969f7e908645444df622642967a5f7fd3db23
Author: Evgenii Zhuravlev 
Date:   2017-07-19T16:30:07Z

IGNITE 5775 JobsProcessor fix bug with delay in compute

commit e5aab82f5629c2705e9bc82a7676f63c7c77062a
Author: dkarachentsev 
Date:   2017-07-20T07:37:08Z

Merge branch 'ignite-1.7.13' into ignite-1.8.9

# Conflicts:
#   
modules/core/src/main/java/org/apache/ignite/internal/jdbc2/JdbcPreparedStatement.java
#   

[GitHub] ignite pull request #4173: IGNITE-8562: As single large commit.

[andrey-kuznetsov]

GitHub user andrey-kuznetsov opened a pull request:

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

IGNITE-8562: As single large commit.



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

$ git pull https://github.com/andrey-kuznetsov/ignite ignite-8562-2

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

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


commit 1d8b7ce77fb2b5adb1f7a5e8e0ec85ec9c9c9e13
Author: Andrey Kuznetsov 
Date:   2018-06-09T15:34:48Z

IGNITE-8562: As single large commit.




---

[GitHub] ignite pull request #4168: IGNITE-8764: Fixed issue with Informatica on Wind...

[asfgit]

Github user asfgit closed the pull request at:

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


---

Re: MTCGA: Hot failures

[Dmitry Pavlov]

Hi Igniters,

Please pay attention to recent emails on dev.list: Sergey Chugunov has
created several issues according to master TC status.

I find this contributions as strongly needed for community,

I'm calling to all contributors to check following failures
 (IGNITE-8769) JVM crash in Basic1 suite in master branch on TC
 (IGNITE-8768) JVM crash in PDS1 suite in master branch
 (IGNITE-8767) JavaClient test suite times out in master branch

Sincerely,
Dmitriy Pavlov

вт, 3 апр. 2018 г. в 17:55, Dmitry Pavlov :

> Hi Igniters,
>
> Thanks to all who assigned tickets. All excepting Data Structure failures
> and https://issues.apache.org/jira/browse/IGNITE-8089 is now assigned.
>
> Your contributions will help to improve TeamCity resutls so we could avoid
> new failures introduction.
>
> Sincerely,
> Dmitriy Pavlov
>
> пт, 30 мар. 2018 г. в 18:43, Dmitry Pavlov :
>
>>
>> Hi Igniters,
>>
>> Let me share some updates on test failures:
>>
>>   Basic [2] https://issues.apache.org/jira/browse/IGNITE-8079  -
>> probably the same problem with
>> https://issues.apache.org/jira/browse/IGNITE-7708
>>
>>   Binary Objects (Simple Mapper Basic)
>> 
>> - Waiting for fix, https://issues.apache.org/jira/browse/IGNITE-8058, -
>> assigned.
>>
>>  Ignite Data Structures
>> 
>>  - I hope Anton V. Will take a look to
>>
>>IgniteCacheDataStructuresSelfTestSuite:
>> IgnitePartitionedCountDownLatchSelfTest.testLatchMultinode1 (master fail
>> rate 12,4%)
>> 
>>
>>IgniteCacheDataStructuresSelfTestSuite:
>> IgniteClientDataStructuresTest.testSequence (master fail rate 11,9%)
>> 
>>
>>IgniteCacheDataStructuresSelfTestSuite:
>> IgniteClientDataStructuresTest.testReentrantLock (master fail rate 10,3%)
>> 
>>
>>  Ignite Start Nodes
>> 
>> test ticket https://issues.apache.org/jira/browse/IGNITE-8085 created,
>> feel free to assign it to yourself.
>>
>>
>>  Activate | Deactivate Cluster
>> 
>>
>>
>> https://issues.apache.org/jira/browse/IGNITE-8086 - test timeouts,
>> unassigned
>>
>> https://issues.apache.org/jira/browse/IGNITE-8088 - flaky assertions for
>> cahe presence validation
>>
>> https://issues.apache.org/jira/browse/IGNITE-8089 - Cache group presence
>> assertion failed in (PM) exchange in
>> IgniteStandByClientReconnectToNewClusterTest
>>
>> Last one it is 100th MTCGA ticket with empty resolution (opened).
>>
>> Committers, please identify related to your maintained features tickets
>> and assign it to you.
>>
>> Sincerely,
>>
>> Dmitriy Pavlov
>>
>>
>> ср, 28 мар. 2018 г. в 13:21, Anton Vinogradov :
>>
>>> Dmitriy,
>>>
>>> Have no chances to check TC this week, may be later.
>>>
>>> 2018-03-28 13:16 GMT+03:00 Dmitry Pavlov :
>>>
>>> > Dmitriy, defenetely at first stage we need issues to be created.
>>> > summary= TestN failed
>>> > labels=MakeTeamCityGreenAgain
>>> > text=Desctiption of failure.
>>> >
>>> > I hope Igniters could provide assitance in creation of issues related
>>> to
>>> > these failures.
>>> >
>>> > Anton,
>>> >
>>> > as expert in Data Structures could you please check failures in DS
>>> suite?
>>> >
>>> > Sincerely,
>>> > Dmitriy Pavlov
>>> >
>>> > ср, 28 мар. 2018 г. в 3:15, Dmitriy Setrakyan :
>>> >
>>> > > Dmitriy,
>>> > >
>>> > > I think it would make sense to create a ticket for every single one
>>> of
>>> > > these, or at least try to group them in to several tickets. What do
>>> you
>>> > > think?
>>> > >
>>> > > D.
>>> > >
>>> > > On Tue, Mar 27, 2018 at 5:17 AM, Dmitry Pavlov <
>>> dpavlov@gmail.com>
>>> > > wrote:
>>> > >
>>> > > > Hi Igniters,
>>> > > >
>>> > > > I’ve filtered report of master failures to find most failing tests.
>>> > > > Following is 5 failing suites and their frequently failed test with
>>> > links
>>> > > > to TC.
>>> > > >
>>> > > > Igniters, please reply who would like to pick up
>>> > > >
>>> > > > - test failures context research,
>>> > > >
>>> > > > - tickets creation
>>> > > >
>>> > > > - and (the best option) fixing these fails.
>>> > > >
>>> > > > Sincerely,
>>> > > >
>>> > > > Dmitriy Pavlov
>>> > > >
>>> > > >   Basic [2]
>>> > > > 

IEP-18 TDE: Prototype

[Nikolay Izhikov]

Hello, guys.

I've implement prototype of TDE implementation [1]
Vladimir, can you do some prereview of this prototype?
Any feedback on public API or any other part of implementation are welcome.

I have several questions I want to discuss.

1. Right place for a cache(data) key:

Currently, all options that controls data persistence located in 
DataStorageConfiguration
And TDE design propose to store key for a cache encryption in Cache 
Metadata.

We can store cache key in Cache Metadata(I already implemented it in 
prototype).
But, wouldn't it be more convenient to have encrypted DataRegion, so 
all caches that use encrypted DataRegion will become encrypted?

2. Encryption key for a WAL.

Should we use separate key for a WAL encryption?
If we want to use cache keys for a WAL encryption it adds some 
difficulties to implement:

1. We should add cacheId for each encrypted record to have 
possibility to decrypt it.
2. We can't decrypt Wal record if cache was destroyed after 
record creation.

Thoughts?

Prototype restrictions:

Currently, size of encrypted data should be equal to clear data because 
FilaPageStore checks it on file validation.
Actually, AES CBC algorithm discussed in IEP adds some extra bytes to encrypted 
data.
So, I plan to implement possibility to enhance page size on FilePageStore level 
in a few days.

[1] https://github.com/apache/ignite/pull/4167

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

[jira] [Created] (IGNITE-8769) JVM crash in Basic1 suite in master branch on TC

[Sergey Chugunov (JIRA)]

Sergey Chugunov created IGNITE-8769:
---

 Summary: JVM crash in Basic1 suite in master branch on TC
 Key: IGNITE-8769
 URL: https://issues.apache.org/jira/browse/IGNITE-8769
 Project: Ignite
  Issue Type: Bug
Reporter: Sergey Chugunov
 Fix For: 2.6


Latest build with crash: [TC 
link|https://ci.ignite.apache.org/viewLog.html?buildId=1373991=buildResultsDiv=IgniteTests24Java8_Basic1]

There is another crash in the history: [TC 
link|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Basic1_IgniteTests24Java8=%3Cdefault%3E=buildTypeStatusDiv]



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

[GitHub] ignite pull request #4149: IGNITE-8713 Spring Data dependencies upgraded

[agura]

Github user agura closed the pull request at:

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


---

[jira] [Created] (IGNITE-8768) JVM crash in PDS1 suite in master branch

[Sergey Chugunov (JIRA)]

Sergey Chugunov created IGNITE-8768:
---

 Summary: JVM crash in PDS1 suite in master branch
 Key: IGNITE-8768
 URL: https://issues.apache.org/jira/browse/IGNITE-8768
 Project: Ignite
  Issue Type: Bug
Reporter: Sergey Chugunov
 Fix For: 2.6


JVM crash in latest build: [TC 
link|https://ci.ignite.apache.org/viewLog.html?buildId=1372456=buildResultsDiv=IgniteTests24Java8_Pds1]

It is the first crash is latest 15 builds: [TC 
link|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Pds1_IgniteTests24Java8=%3Cdefault%3E=buildTypeStatusDiv]



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

[GitHub] ignite pull request #4172: GG-13911

[ilantukh]

GitHub user ilantukh opened a pull request:

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

GG-13911



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

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

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

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


commit fbee7a93f6af633b5c197634b277873ed43bce8e
Author: Ilya Lantukh 
Date:   2018-06-09T14:59:38Z

GG-13911 : ExchangeFuture will not complete with Exception on concurrent 
snapshot.




---

[jira] [Created] (IGNITE-8767) JavaClient test suite times out in master branch

[Sergey Chugunov (JIRA)]

Sergey Chugunov created IGNITE-8767:
---

 Summary: JavaClient test suite times out in master branch
 Key: IGNITE-8767
 URL: https://issues.apache.org/jira/browse/IGNITE-8767
 Project: Ignite
  Issue Type: Bug
  Components: clients
Reporter: Sergey Chugunov
 Fix For: 2.6


Latest execution timeout: [link to 
TC|https://ci.ignite.apache.org/viewLog.html?buildId=1372416=buildResultsDiv=IgniteTests24Java8_JavaClient]

Suite hangs regularly in master branch: [link to 
TC|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_JavaClient_IgniteTests24Java8=%3Cdefault%3E=buildTypeStatusDiv]

Looks like culprit test is 
JettyRestProcessorAuthenticationWithCredsSelfTest.testDeactivateActivate.





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

[jira] [Created] (IGNITE-8766) TcpDiscoverySpi: discovery threads naming

[Sergey Chugunov (JIRA)]

Sergey Chugunov created IGNITE-8766:
---

 Summary: TcpDiscoverySpi: discovery threads naming
 Key: IGNITE-8766
 URL: https://issues.apache.org/jira/browse/IGNITE-8766
 Project: Ignite
  Issue Type: Improvement
  Components: general
Reporter: Sergey Chugunov


Including information about next/prev nodes into names of discovery-related 
threads could be very helpful when investigating situations of network glitches.

tcp-disco-sock-reader and tcp-disco-msg-worker threads must include such 
information in their names.



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

[GitHub] ignite pull request #4171: IGNITE-8751 Failure handler accordingly to segmen...

[agura]

GitHub user agura opened a pull request:

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

IGNITE-8751 Failure handler accordingly to segmentation policy should be 
invoked on node segmentation instead of configured failure handler

… be invoked on node segmentation instead of configured failure handler

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

$ git pull https://github.com/agura/incubator-ignite ignite-8751

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

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


commit 56f02086cdabe05af5001fb228406935ca000994
Author: Andrey Gura 
Date:   2018-06-09T13:37:49Z

IGNITE-8751 Failure handler accordingly to segmentation policy should be 
invoked on node segmentation instead of configured failure handler




---

[GitHub] ignite pull request #4170: Ignite 8748

[SpiderRus]

GitHub user SpiderRus opened a pull request:

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

Ignite 8748



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

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

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

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


commit 1e0a82961b22e9d923d9d13a44ccc0b3f47c0b1e
Author: Sergey Chugunov 
Date:   2018-06-06T10:02:47Z

GG-13865 wal files should be preallocated and fsynced in mmap mode

commit d52186206bb72efec4cff8e64f874cadf1734ef1
Author: Sergey Chugunov 
Date:   2018-06-06T14:11:12Z

GG-13865 filling wal segments with non-zero values

commit 413b7a80949c59fe3883ec34de6d5c67e8f68ecd
Author: Alexey Stelmak 
Date:   2018-06-07T09:51:57Z

gg-13865 JVM crash if there is no space for wal storage

commit dfe4a46bf101caa6e55d31dbb0b6642f5b163b0b
Author: Alexey Stelmak 
Date:   2018-06-07T10:13:03Z

gg-13865 JVM crash if there is no space for wal storage

commit a3461d9725d28e8723d7d9720fbd7f2e0d3c1426
Author: Alexey Stelmak 
Date:   2018-06-09T12:37:51Z

Add failure handler




---

[jira] [Created] (IGNITE-8765) SQL event is not fired when query is reduced to local form

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-8765:
---

 Summary: SQL event is not fired when query is reduced to local form
 Key: IGNITE-8765
 URL: https://issues.apache.org/jira/browse/IGNITE-8765
 Project: Ignite
  Issue Type: Bug
  Components: sql
Affects Versions: 2.5, 2.4
Reporter: Vladimir Ozerov


*Reproducer*
{{org.apache.ignite.internal.processors.cache.IgniteCacheAbstractQuerySelfTest#testSqlQueryEvents}}

*Root Cause*
Local and non-local query execution is performed differently. Local query is 
logged early. However, non-local query could be reduced after that. As a 
result, event is missed. Try change 
{{org.apache.ignite.internal.processors.query.h2.sql.GridSqlQueryParser#isLocalQuery}}
 method to always return {{false}} and then re-run failed test to see the 
difference.



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

[GitHub] ignite pull request #4169: GNITE-8699: For TC.

[BiryukovVA]

GitHub user BiryukovVA opened a pull request:

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

GNITE-8699: For TC.



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

$ git pull https://github.com/BiryukovVA/ignite IGNITE_8699_TC

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

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


commit 740bd7b8a096c7b90051df235c2c4fc52ed7b53a
Author: Vitaliy Biryukov 
Date:   2018-06-09T11:27:27Z

GNITE-8699: For TC.




---

[GitHub] ignite pull request #4168: IGNITE-8764: Fixed issue with Informatica on Wind...

[isapego]

GitHub user isapego opened a pull request:

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

IGNITE-8764: Fixed issue with Informatica on Windows



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

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

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

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


commit abd7d59fb02b4a3346999bd7efea9d5568831808
Author: Igor Sapego 
Date:   2018-06-09T11:17:59Z

IGNITE-8764: Fixed issue with Informatica on Windows




---

[jira] [Created] (IGNITE-8764) Informatica can not connect to a cluster using ODBC driver on Windows

[Igor Sapego (JIRA)]

Igor Sapego created IGNITE-8764:
---

 Summary: Informatica can not connect to a cluster using ODBC 
driver on Windows
 Key: IGNITE-8764
 URL: https://issues.apache.org/jira/browse/IGNITE-8764
 Project: Ignite
  Issue Type: Bug
  Components: odbc
Affects Versions: 2.5
Reporter: Igor Sapego
Assignee: Igor Sapego
 Fix For: 2.6


It crashes or returns garbage on attempt to connect to a server node.



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

[jira] [Created] (IGNITE-8763) java.nio.file.AccessDeniedException is not handled with default failure handler

[Andrey Gura (JIRA)]

Andrey Gura created IGNITE-8763:
---

 Summary: java.nio.file.AccessDeniedException is not handled with 
default failure handler
 Key: IGNITE-8763
 URL: https://issues.apache.org/jira/browse/IGNITE-8763
 Project: Ignite
  Issue Type: Improvement
Affects Versions: 2.5
Reporter: Andrey Gura
 Fix For: 2.6


java.nio.file.AccessDeniedException is not handled with default failure handler

1. Start cluster(4 nodes).
2. Upload some data.
3. Make files in metastore read only.
4. Deactivate grid.
5. Activate grid.

On this step I see java.nio.file.AccessDeniedException:

{noformat}
[17:55:40,035][INFO][exchange-worker-#62][GridCacheDatabaseSharedManager] Read 
checkpoint status 
[startMarker=/storage/ssd/avolkov/tiden/iep_14-180517-175425/test_iep_14/ignite.server.1/work/db/node1/cp/1526568907638-46128a87-562a-45fc-8d73-75ccb1490d63-START.bin,
 
endMarker=/storage/ssd/avolkov/tiden/iep_14-180517-175425/test_iep_14/ignite.server.1/work/db/node1/cp/1526568907638-46128a87-562a-45fc-8d73-75ccb1490d63-END.bin]
[17:55:40,037][SEVERE][exchange-worker-#62][GridDhtPartitionsExchangeFuture] 
Failed to activate node components 
[nodeId=bd7115d5-1f95-4673-9f40-47056b0b1a58, client=false, 
topVer=AffinityTopologyVersion [topVer=4, minorTopVer=5]]
class org.apache.ignite.IgniteCheckedException: Error while creating file page 
store 
[file=/storage/ssd/avolkov/tiden/iep_14-180517-175425/test_iep_14/ignite.server.1/work/db/node1/metastorage/part-0.bin]:
at 
org.apache.ignite.internal.processors.cache.persistence.file.FileVersionCheckingFactory.createPageStore(FileVersionCheckingFactory.java:98)
at 
org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.initDir(FilePageStoreManager.java:463)
at 
org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.initializeForMetastorage(FilePageStoreManager.java:234)
at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.readCheckpointAndRestoreMemory(GridCacheDatabaseSharedManager.java:743)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onClusterStateChangeRequest(GridDhtPartitionsExchangeFuture.java:896)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:643)
at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2419)
at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2299)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.nio.file.AccessDeniedException: 
/storage/ssd/avolkov/tiden/iep_14-180517-175425/test_iep_14/ignite.server.1/work/db/node1/metastorage/part-0.bin
at 
sun.nio.fs.UnixException.translateToIOException(UnixException.java:84)
at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
at 
sun.nio.fs.UnixFileSystemProvider.newAsynchronousFileChannel(UnixFileSystemProvider.java:196)
at 
java.nio.channels.AsynchronousFileChannel.open(AsynchronousFileChannel.java:248)
at 
java.nio.channels.AsynchronousFileChannel.open(AsynchronousFileChannel.java:301)
at 
org.apache.ignite.internal.processors.cache.persistence.file.AsyncFileIO.(AsyncFileIO.java:57)
at 
org.apache.ignite.internal.processors.cache.persistence.file.AsyncFileIOFactory.create(AsyncFileIOFactory.java:53)
at 
org.apache.ignite.internal.processors.cache.persistence.file.AsyncFileIOFactory.create(AsyncFileIOFactory.java:41)
at 
org.apache.ignite.internal.processors.cache.persistence.file.FileVersionCheckingFactory.createPageStore(FileVersionCheckingFactory.java:78)
... 9 more
{noformat}

Situation led to NPE exception after AccessDeniedException looks like this:

1. AccessDeniedException was thrown in ExchangeFuture right before affinity 
initialization so affinity was never initialized.
 2.   After that node receives PartitionSingleMessage and tries to access 
affinity information. Null is returned because of exception in step #1.





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

[jira] [Created] (IGNITE-8762) TcpDiscoverySpi: additional validation on handshake phase

[Sergey Chugunov (JIRA)]

Sergey Chugunov created IGNITE-8762:
---

 Summary: TcpDiscoverySpi: additional validation on handshake phase
 Key: IGNITE-8762
 URL: https://issues.apache.org/jira/browse/IGNITE-8762
 Project: Ignite
  Issue Type: Improvement
  Components: general
Reporter: Sergey Chugunov


Extra information about topology should be added to Handshake phase of 
establishing discovery connection between two nodes, e.g. info about current 
coordinator, current topology version, topology hash.

Node processing Handshake request will be able to validate this information and 
make a decision about next steps from printing warning to logs to forcibly 
stopping other node.



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

[GitHub] ignite pull request #3979: Ignite-5945: Flaky failure in IgniteCache 5: Igni...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] ignite pull request #4166: IGNITE-8131 ZookeeperDiscoverySpiTest#testClientR...

[dgarus]

GitHub user dgarus opened a pull request:

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

IGNITE-8131 ZookeeperDiscoverySpiTest#testClientReconnectSessionExpire* 
tests fail on TC



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

$ git pull https://github.com/dgarus/ignite ignite-8131

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

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


commit 28fe7b5b9c5c6c07015d3ff99cb249f89493a47f
Author: Garus Denis 
Date:   2018-06-09T10:12:08Z

IGNITE-8131. check TC fail




---

Re: Ignite schedule module

[Dmitry Pavlov]

ok. thanks

чт, 7 июн. 2018 г. в 19:44, Alexey Kuznetsov :

> Dima,
>
> See https://issues.apache.org/jira/browse/IGNITE-5565
>
> On Thu, Jun 7, 2018 at 10:09 PM, Dmitry Pavlov 
> wrote:
>
> > Hi Ilya, I appreciate you answer.
> >
> > Sincerely,
> >
> > чт, 7 июн. 2018 г. в 17:16, Ilya Kasnacheev :
> >
> > > Hello!
> > >
> > > This module depends on a library which is under LGPL.
> > >
> > > This means you will have to build this module yourself, deploy to your
> > > local maven, to satisfly licences' terms. This is the reason it's not
> > > published. There's ongoing discussion about replacing scheduler
> > > implementation to one with less restrictive license, resume publishing
> > this
> > > module.
> > >
> > > Regards,
> > >
> > > --
> > > Ilya Kasnacheev
> > >
> > > 2018-06-06 19:05 GMT+03:00 Dmitry Pavlov :
> > >
> > > > Hi Igniters,
> > > >
> > > > I've tried to use
> > > >
> > > > ignite.scheduler().scheduleLocal(this::checkFailures, "? * * * * *");
> > > >
> > > > Result is
> > > > class org.apache.ignite.IgniteException: Current Ignite configuration
> > > does
> > > > not support schedule functionality (consider adding ignite-schedule
> > > module
> > > > to classpath).
> > > > at
> > > > org.apache.ignite.internal.processors.schedule.
> > > > IgniteNoopScheduleProcessor.processorException(
> > > > IgniteNoopScheduleProcessor.java:50)
> > > >
> > > > Maven repos does not contain this module.
> > > > I guess ignite-schedule is not deployed:
> > > >
> > > > org.apache.maven.plugins
> > > > maven-deploy-plugin
> > > > 
> > > > true
> > > > 
> > > >
> > > > What should I do? Error message refers I should add unexistent module
> > to
> > > > classpath, but
> > > > https://mvnrepository.com/artifact/org.apache.ignite/ignite-schedule
> > is
> > > > not
> > > > available since 2015.
> > > >
> > > > Sincerely,
> > > > Dmitriy Pavlov
> > > >
> > >
> >
>
>
>
> --
> Alexey Kuznetsov
>

Fwd: Question on peer class loading

[Dmitry Pavlov]

Hi,

Cross posting to user list. dev list is intended for contribution related
discussions.

Sincerely,

-- Forwarded message -
From: vbm 
Date: чт, 7 июн. 2018 г. в 10:55
Subject: Question on peer class loading
To: 


Hi,

I have a Ignite server running with 3rd partyDB (MYSQL). I have the below
configuration in xml file:


  
   
  
  



* *
  ...



On the server the jar for mysql jdbc driver is present iand the servers are
coming up successfully.
I have placed the mysql jdbc driver in a seperate folder and added it to the
path using USER_LIBS env.


Now if I try to start a client, with the same the xml (only extra thing is
the client mode part), the client ignite node doesn't start and throws below
error.

* org.springframework.beans.MethodInvocationException: Property
'driverClassName' threw exception; nested exception is
java.lang.IllegalStateException: Could not load JDBC driver class
[com.mysql.jdbc.Driver]*

As peer class loading is enabled, I expect the client to get the class from
the server. Why is this not happening ?













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

[jira] [Created] (IGNITE-8761) WAL fsync at rollover should be asynchronous in LOG_ONLY and BACKGROUND modes

[Ivan Rakov (JIRA)]

Ivan Rakov created IGNITE-8761:
--

 Summary: WAL fsync at rollover should be asynchronous in LOG_ONLY 
and BACKGROUND modes
 Key: IGNITE-8761
 URL: https://issues.apache.org/jira/browse/IGNITE-8761
 Project: Ignite
  Issue Type: Improvement
  Components: persistence
Reporter: Ivan Rakov
 Fix For: 2.6


Transactions may periodically hang for a few seconds in LOG_ONLY or BACKGROUND 
persistent modes. Thread dumps show that threads are hanging on syncing 
previous WAL segment during rollover:
{noformat}
  java.lang.Thread.State: RUNNABLE
   at java.nio.MappedByteBuffer.force0(MappedByteBuffer.java:-1)
   at java.nio.MappedByteBuffer.force(MappedByteBuffer.java:203)
   at 
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileWriteHandle.close(FileWriteAheadLogManager.java:2843)
   at 
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileWriteHandle.access$600(FileWriteAheadLogManager.java:2483)
   at 
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.rollOver(FileWriteAheadLogManager.java:1094)
{noformat}
Waiting for this fsync is not necessary action to ensure crash recovery 
guarantees. Instead of this, we should just perform fsyncs asychronously and 
ensure that they are completed prior to next checkpoint start.



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

[jira] [Created] (IGNITE-8760) TcpDiscoverySpi: validation of discovery message path on each node

[Sergey Chugunov (JIRA)]

Sergey Chugunov created IGNITE-8760:
---

 Summary: TcpDiscoverySpi: validation of discovery message path on 
each node
 Key: IGNITE-8760
 URL: https://issues.apache.org/jira/browse/IGNITE-8760
 Project: Ignite
  Issue Type: Improvement
Reporter: Sergey Chugunov


As each discovery message goes across the ring it can record all nodes it was 
handled on.

It gives discovery protocol an opportunity to set up a constant monitoring of 
cluster topology: each node on receiving discovery message will compare path 
recorded by the message and its local picture of current topology. On detecting 
any discrepancy node may at least print warning or take other actions.

Path recording may be expensive in terms of network traffic so it is better to 
add this logic to specific types of discovery messages: all topology changing 
messages and (may be) heartbeats.



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

[GitHub] ignite pull request #4165: IGNITE-8747: Remove\RemoveAll shouldn't report of...

[AMashenkov]

GitHub user AMashenkov opened a pull request:

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

IGNITE-8747: Remove\RemoveAll shouldn't report of successful deletion for 
expired entries.

(cherry picked from commit f65f0a5)

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

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

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

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


commit ec567c0e5bd0b13f2ea9e097057c2cb4b57f2467
Author: Andrey V. Mashenkov 
Date:   2018-06-09T08:52:38Z

IGNITE-8747: Apply AccessPolicy instantly on first touch.

(cherry picked from commit f65f0a5)




---

[jira] [Created] (IGNITE-8759) TcpDiscoverySpi: detailed info about current state in MBean

[Sergey Chugunov (JIRA)]

Sergey Chugunov created IGNITE-8759:
---

 Summary: TcpDiscoverySpi: detailed info about current state in 
MBean
 Key: IGNITE-8759
 URL: https://issues.apache.org/jira/browse/IGNITE-8759
 Project: Ignite
  Issue Type: Improvement
  Components: general
Reporter: Sergey Chugunov


When TcpDiscoverySpi is used all nodes keep information about current topology 
locally. Discovery protocol is responsible of keeping this information 
consistent across all nodes.

However in situations of network glitches some nodes may have different 
pictures of current state and topology of the cluster.

To make it easier to monitor state of the whole cluster and identify such nodes 
quicker the following information should be presented via MBean interface on 
each node:
* Current topology version;
* Hash of current topology (e.g. sum of hash codes of all nodeIds) (to allow 
quick matching);
* Pretty-formatted snapshot of current topology visible from the node;
* Information about nodes visible/invisible to local one;
* Other information useful to monitoring of topology state.



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

[GitHub] ignite pull request #4164: IGNITE-6295

[devozerov]

GitHub user devozerov opened a pull request:

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

IGNITE-6295



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

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

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

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


commit 5defccc2898049b1f40cb97873bc53e8e95e594d
Author: devozerov 
Date:   2018-06-09T09:34:02Z

Implemented base logic, need to run tests.




---

[GitHub] ignite pull request #4163: IGNITE-1094 Ignite.createCache(CacheConfiguration...

[sk0x50]

GitHub user sk0x50 opened a pull request:

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

IGNITE-1094 Ignite.createCache(CacheConfiguration) hangs if some exception 
occurs during cache initialization



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

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

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

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


commit 51f13379fc920f1f9412bcc07025ceadab28666c
Author: Slava Koptilin 
Date:   2018-06-08T10:14:16Z

added IgniteDynamicCacheStartFailSelfTest

commit 1e85bb15db98fd2b8bc3ea338f1b528945d3d5f4
Author: Slava Koptilin 
Date:   2018-06-08T10:16:21Z

added new attribute ATTR_DYNAMIC_CACHE_START_ROLLBACK_SUPPORTED which 
indicates that rollback of exchange is supported

commit 8907568fe7292ab78b64f82475dd3ddf77e07f34
Author: Slava Koptilin 
Date:   2018-06-08T10:18:45Z

added convenience method to check that all nodes has an attribute and its 
value equals to expected value.

commit d937eefdb3715f54d01bec9379649fb284e9ed93
Author: Slava Koptilin 
Date:   2018-06-08T10:22:01Z

added DynamicCacheChangeFailureMessage that represents exchange failure due 
to dynamic cache start.

commit 3580d89045754cf7763b56aea9a40176c532add8
Author: Slava Koptilin 
Date:   2018-06-08T20:43:40Z

added rollback dynamically started caches

commit b184de02feffab58916378185dad1a7e6132c5b5
Author: Slava Koptilin 
Date:   2018-06-08T21:21:15Z

merged with master

commit f82b99c07ac8fe094698d626ec99dfb594edaf63
Author: Slava Koptilin 
Date:   2018-06-08T21:27:40Z

updated test suite




---