[MTCGA]: new failures in builds [2093987] needs to be handled

[dpavlov . tasks]

Hi Igniters,

 I've detected some new issue on TeamCity to be handled. You are more than 
welcomed to help.

 If your changes can lead to this failure(s): We're grateful that you were a 
volunteer to make the contribution to this project, but things change and you 
may no longer be able to finalize your contribution.
 Could you respond to this email and indicate if you wish to continue and fix 
test failures or step down and some committer may revert you commit. 

 *New stable failure of a flaky test in master 
TcpDiscoverySslTrustedSelfTest.testNodeShutdownOnRingMessageWorkerStartNotFinished
 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=4205209624038097982&branch=%3Cdefault%3E&tab=testDetails
 No changes in the build

 - Here's a reminder of what contributors were agreed to do 
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute 
 - Should you have any questions please contact dev@ignite.apache.org 

Best Regards,
Apache Ignite TeamCity Bot 
https://github.com/apache/ignite-teamcity-bot
Notification generated at 08:40:43 16-10-2018 

Re: Python thin client

[Dmitry Melnichuk]

Igor,

I do not have access to edit wiki pages, so please fill it.

All the features are supported, except for:

- Query API: ScanQuery with filter,
- Binary API: Get object in BinaryObject form, BinaryObject building,
- Additional Features: Best effort affinity,
- Type registration: Enum registration, Type name registration.

On 10/15/18 9:17 PM, Igor Sapego wrote:

Dmitry,

Since Python thin client is now in master, can you please add it to our
"Thin clients features" wiki page, so we can track the feature parity
of our clients? Or just tell me which features are supported, so I can fill
it myself.

[1] -
https://cwiki.apache.org/confluence/display/IGNITE/Thin+clients+features

Best Regards,
Igor

[GitHub] ignite pull request #4997: Ignite-2.5.1-p141-reconnect-fix

[dgovorukhin]

GitHub user dgovorukhin opened a pull request:

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

Ignite-2.5.1-p141-reconnect-fix



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

$ git pull https://github.com/gridgain/apache-ignite 
ignite-2.5.1-p141-reconnect-fix

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

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


commit 6ea23844cfb0294a0cf3f3c21787aeff30939bcf
Author: Dmitriy Sorokin 
Date:   2018-06-06T11:34:04Z

IGNITE-8311 IgniteClientRejoinTest.testClientsReconnectDisabled causes 
exchange-worker to terminate via NPE

Signed-off-by: Andrey Gura 

commit bad52d3843925d831e6d357a4382731751ae6bb7
Author: Ilya Lantukh 
Date:   2018-06-04T14:07:52Z

GG-13862 : Disabled fast eviction.

(cherry picked from commit 786633d)

commit 6956097ceedd2e3e9edcb627d97e49afb7f0a26d
Author: Pavel Kovalenko 
Date:   2018-06-06T12:24:39Z

IGNITE-8482 Skip 2-phase partition release wait in case of activation or 
dynamic caches start - Fixes #4078.

Signed-off-by: Alexey Goncharuk 

(cherry picked from commit 7c565d2)

commit d777c76eadd0a2ccc50f1031c42626b135da5906
Author: Dmitriy Govorukhin 
Date:   2018-06-06T14:20:18Z

IGNITE-8685 Fixed switch segment record size - Fixes #4130.

Signed-off-by: Alexey Goncharuk 

(cherry picked from commit 2a048bd)

commit ef4782d8a60eea870b43933480f2c9695c9fc55d
Author: Alexey Goncharuk 
Date:   2018-06-07T11:55:13Z

IGNITE-8706 Fixed testMemoryUsageMultipleNodes

commit 6902383e01ee69d7efff9613a68f3fc419152305
Author: Pavel Kovalenko 
Date:   2018-05-14T10:14:52Z

IGNITE-8422 Tests fix for Zookeeper discovery split brain detection 
shouldn't consider client nodes - Fixes #3975.

Signed-off-by: dpavlov 

(cherry-picked from commit #19cbf8058b48a1f8fec60f7ceac70229e7c5391a)

commit 6eef070f8e0627e2986d870cc09ceb9cb351ee0d
Author: Sergey Chugunov 
Date:   2018-05-14T17:09:33Z

IGNITE-8487 tmpfs is employed by ZooKeeper tests - Fixes #3994.

Signed-off-by: dpavlov 

(cherry-picked from commit #67be050a2c7b9efdef2388c579fc060c68ff8a38)

commit c9b82cc632ad1cac51661f729f8605ab6c97c1dd
Author: Anton Kalashnikov 
Date:   2018-06-08T15:24:09Z

IGNITE-8739 Implemented WA for tcp communication SPI hanging on descriptor 
reservation - Fixes #4148.

Signed-off-by: Alexey Goncharuk 

(cherry picked from commit 7021651)

commit 45953256ef0f09fd5450f6f6c6967a539c5cd395
Author: Pavel Kovalenko 
Date:   2018-05-03T14:01:20Z

IGNITE-8226 Improved logging - Fixes #3796.

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

commit 77d089d857876f1901ade5a017a92c9835e2976a
Author: Sergey Kosarev 
Date:   2018-06-13T14:24:42Z

IGNITE-8736 Add transaction label to CU.txString() method output - Fixes 
#4152.

Signed-off-by: Alexey Goncharuk 

commit c3c80439945134867e28e8d2c6db5ef9295141b6
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

commit d33fe100bc9fdbcb66754d43ec0199e44233190b
Author: Andrey Gura 
Date:   2018-06-13T14:30:18Z

IGNITE-8781 GridNioServer accepter threads should have different names

commit d2c304ca415919f0933461dde92fdf354539529b
Author: Aleksey Plekhanov 
Date:   2018-06-14T17:41:31Z

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

Signed-off-by: Andrey Gura 

commit 2545a4d65ae9c0289c9f6faf9d2ee498375aa3c7
Author: Sergey Chugunov 
Date:   2018-06-15T08:31:33Z

IGNITE-8657 Simultaneous start of multiple clients may lead to client start 
hang when exchange history size is too short - Fixes #4102.

Signed-off-by: Alexey Goncharuk 

(cherry-picked from commit #2b928c702b2d6a7c1de8d1b3b0a1e0e65e653f21)

commit f4511d921c34fc1fc048afaf3ec10307b0f3bea2
Author: Pavel Kovalenko 
Date:   2018-06-15T09:48:24Z

IGNITE-8610 Fixed checkpoint record search for WAL delta rebalancing - 
Fixes #4090.

Signed-off-by: Alexey Goncharuk 

(cherry picked from commit 10aa02a)

commit 1a8e9fcafa3a6d53ab01901be798cc8957252fe6
Author: EdShangGG 
Date:   2018-06-15T16:35:00Z

IGNITE-8610 Fix compilation

(cherry picked from commit 55af7d1)

commit 298ca37aea710e098d033fcc5750e408b4a07c24
Author: Ilya Lantukh 
Date:   2018-05-23T15:02:23Z

IGNITE-7809 fixed stable failures of IgniteWalFlushDefaultSelfTest in 
Ignite PDS 2 & PDS 2 Direct IO, new tests were added. - Fixes #3569.

Signed-off-by: dpavlov 

(cherry picked from commit fed2c02)

commit 3a1645135cf474f5760319a3c2dd7712041

[jira] [Created] (IGNITE-9893) add hibernate-5.2 module

[Scott Feldstein (JIRA)]

Scott Feldstein created IGNITE-9893:
---

 Summary: add hibernate-5.2 module
 Key: IGNITE-9893
 URL: https://issues.apache.org/jira/browse/IGNITE-9893
 Project: Ignite
  Issue Type: New Feature
  Components: hibernate
Reporter: Scott Feldstein


hi,

I have ported hibernate-5.2 to ignite 2.7.0-SNAPSHOT HEAD.

commit: 
[https://github.com/scottmf/ignite/commit/4f2caafb8c433e3f840d14f91c2d83da1052afd9]

All tests pass except CacheHibernateBlobStoreSelfTest.testSimpleMultithreading 
which is carryover from the hibernate-5.1 implementation. There is a bug 
already associated with the failure:

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



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

[GitHub] ignite pull request #4996: Ignite-9830

[ascherbakoff]

GitHub user ascherbakoff opened a pull request:

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

Ignite-9830



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

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

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

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


commit 50e40353ba7d6fb9cc25da8b251a24e3e16f65e1
Author: Aleksei Scherbakov 
Date:   2018-10-09T15:13:17Z

IGNITE-9830 wip.

commit 63c8ffc0d0ea9254d9fe70bd1cde6bc5d46b1f22
Author: ascherbakoff 
Date:   2018-10-13T18:06:30Z

IGNITE-9830 wip.

commit efc3343f58053c7294a6ece9a7e58e6086b506f7
Author: ascherbakoff 
Date:   2018-10-14T10:16:08Z

IGNITE-9830 reporducer.

commit b7651e197be71decfc6fa07dd933024cc6bfee94
Author: ascherbakoff 
Date:   2018-10-14T15:08:26Z

IGNITE-9830 wip.

commit 9cb2bf7fe812e19f0a41cb35fc70d9271bd38183
Author: ascherbakoff 
Date:   2018-10-14T15:13:07Z

IGNITE-9830 wip.

commit 3b41ad7ce95fa6f89f9cf48342a2d2f14b3aedf1
Author: ascherbakoff 
Date:   2018-10-14T18:33:24Z

IGNITE-9830 wip.

commit 7142c78c155f28cf3c104e215ff3086bcdb851d8
Author: ascherbakoff 
Date:   2018-10-14T19:33:57Z

IGNITE-9830 wip.

commit 96bdfb6baffbc14b380cc48419d1f9dd77fade89
Author: ascherbakoff 
Date:   2018-10-15T09:04:02Z

IGNITE-9830 wip.

commit d1d6c0e5e895bba2b6da37307c3fbfca8470f904
Author: ascherbakoff 
Date:   2018-10-15T09:04:19Z

Merge branch 'master' of https://github.com/apache/ignite into ignite-9830

commit cd9b1197f0d03c64293a051ddf977efab521be9e
Author: ascherbakoff 
Date:   2018-10-15T09:16:26Z

IGNITE-9830 wip.

commit 6af22f5e8d7c876cddfa05f7d97f7e77e6e6b3f1
Author: ascherbakoff 
Date:   2018-10-15T11:56:32Z

IGNITE-9830 wip.

commit f738aaf7aa1cc54888e124ba816af6dd34d27d29
Author: ascherbakoff 
Date:   2018-10-15T12:19:45Z

IGNITE-9830 wip.

commit dcceed758ae83df79bf1ec4ef2c8c228f07a7897
Author: ascherbakoff 
Date:   2018-10-15T12:21:25Z

IGNITE-9830 wip.

commit 14c1ff57dfcaf71b627aae7743f7c25a06d3cc9a
Author: ascherbakoff 
Date:   2018-10-15T12:22:49Z

IGNITE-9830 wip.

commit 430e1f115fa592eb55e286a27edf18de9171733c
Author: ascherbakoff 
Date:   2018-10-15T15:11:50Z

IGNITE-9830 wip.

commit e8ec406afa7d4ad2edb5285e10c256713ccba254
Author: ascherbakoff 
Date:   2018-10-15T17:06:10Z

IGNITE-9830 wip.

commit f44b8f7e63da4e42eba6867f1fa72932276392ee
Author: ascherbakoff 
Date:   2018-10-15T17:24:42Z

IGNITE-9830 wip.

commit 79ec54bea9f7551ff70d5a0b8b582e74712a8116
Author: ascherbakoff 
Date:   2018-10-15T17:33:00Z

IGNITE-9830 wip.

commit 33f89e67482509f959a238ebdfc65f1aa403008b
Author: ascherbakoff 
Date:   2018-10-15T17:33:38Z

IGNITE-9830 wip.

commit 6ace2477f8cd3c1ca6e117739b33e269ad20011b
Author: ascherbakoff 
Date:   2018-10-15T17:51:11Z

IGNITE-9830 wip.

commit 5ce1d0dad43aa42d3423a9225e9fc76e19ae238f
Author: ascherbakoff 
Date:   2018-10-15T18:13:24Z

IGNITE-9830 wip.

commit 44eec4da359cd20aa3f019bf240461bfbc83dc2f
Author: ascherbakoff 
Date:   2018-10-15T18:14:05Z

Merge branch 'master' of https://github.com/apache/ignite into ignite-9830

commit 54ec42b89340d574e8cf9f45de2c9b6f601a35f3
Author: ascherbakoff 
Date:   2018-10-15T18:17:21Z

IGNITE-9830 wip.

commit 41280797dff9164b88d263a20c53d4bec7042cfa
Author: ascherbakoff 
Date:   2018-10-15T18:24:14Z

IGNITE-9830 wip.




---

[GitHub] ignite pull request #4995: IGNITE-9891: SQLTables fix for ODBC

[isapego]

GitHub user isapego opened a pull request:

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

IGNITE-9891: SQLTables fix for ODBC



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

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

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

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


commit a26c9727cad7c8724f44e182805fe25e94073943
Author: Igor Sapego 
Date:   2018-10-15T16:56:06Z

IGNITE-9891: Added test

commit d4ce7417abe47bff84848ee7b84d7a60606a9fc5
Author: Igor Sapego 
Date:   2018-10-15T16:58:02Z

IGNITE-9891: Fixed an issue




---

[jira] [Created] (IGNITE-9892) MVCC: Exchange hangs on mvcc coordinator fail

[Roman Kondakov (JIRA)]

Roman Kondakov created IGNITE-9892:
--

 Summary: MVCC: Exchange hangs on mvcc coordinator fail
 Key: IGNITE-9892
 URL: https://issues.apache.org/jira/browse/IGNITE-9892
 Project: Ignite
  Issue Type: Bug
  Components: mvcc
Affects Versions: 2.7
Reporter: Roman Kondakov


Test 
{{CacheMvccPartitionedSqlCoordinatorFailoverTest#testAccountsTxSql_Server_Backups0_CoordinatorFails}}
 hangs sporadically on exchange.

Stacktrace:

{code:java}
[11:33:18]W: [org.apache.ignite:ignite-indexing] Thread 
[name="exchange-worker-#151671%mvcc.CacheMvccPartitionedSqlCoordinatorFailoverTest1%",
 id=165981, state=TIMED_WAITING, blockCnt=69, waitCnt=36]
[11:33:18]W: [org.apache.ignite:ignite-indexing] at 
sun.misc.Unsafe.park(Native Method)
[11:33:18]W: [org.apache.ignite:ignite-indexing] at 
java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:338)
[11:33:18]W: [org.apache.ignite:ignite-indexing] at 
o.a.i.i.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:219)
[11:33:18]W: [org.apache.ignite:ignite-indexing] at 
o.a.i.i.util.future.GridFutureAdapter.get(GridFutureAdapter.java:160)
[11:33:18]W: [org.apache.ignite:ignite-indexing] at 
o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.waitPartitionRelease(GridDhtPartitionsExchangeFuture.java:1433)
[11:33:18]W: [org.apache.ignite:ignite-indexing] at 
o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchangeFuture.java:1271)
[11:33:18]W: [org.apache.ignite:ignite-indexing] at 
o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:789)
[11:33:18]W: [org.apache.ignite:ignite-indexing] at 
o.a.i.i.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2657)
[11:33:18]W: [org.apache.ignite:ignite-indexing] at 
o.a.i.i.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2529)
[11:33:18]W: [org.apache.ignite:ignite-indexing] at 
o.a.i.i.util.worker.GridWorker.run(GridWorker.java:120)
[11:33:18]W: [org.apache.ignite:ignite-indexing] at 
java.lang.Thread.run(Thread.java:748)
[11:33:18]W: [org.apache.ignite:ignite-indexing] Thread 
[name="test-runner-#151510%mvcc.CacheMvccPartitionedSqlCoordinatorFailoverTest%",
 id=165803, state=RUNNABLE, blockCnt=70, waitCnt=1710]
[11:33:18]W: [org.apache.ignite:ignite-indexing] at 
sun.management.ThreadImpl.dumpThreads0(Native Method)
[11:33:18]W: [org.apache.ignite:ignite-indexing] at 
sun.management.ThreadImpl.dumpAllThreads(ThreadImpl.java:454)
[11:33:18]W: [org.apache.ignite:ignite-indexing] at 
o.a.i.i.util.IgniteUtils.dumpThreads(IgniteUtils.java:1356)
[11:33:18]W: [org.apache.ignite:ignite-indexing] at 
o.a.i.testframework.junits.common.GridCommonAbstractTest.awaitPartitionMapExchange(GridCommonAbstractTest.java:724)
[11:33:18]W: [org.apache.ignite:ignite-indexing] at 
o.a.i.testframework.junits.common.GridCommonAbstractTest.awaitPartitionMapExchange(GridCommonAbstractTest.java:549)
[11:33:18]W: [org.apache.ignite:ignite-indexing] at 
o.a.i.testframework.junits.common.GridCommonAbstractTest.awaitPartitionMapExchange(GridCommonAbstractTest.java:533)
[11:33:18]W: [org.apache.ignite:ignite-indexing] at 
o.a.i.i.processors.cache.mvcc.CacheMvccAbstractTest.readWriteTest(CacheMvccAbstractTest.java:1382)
[11:33:18]W: [org.apache.ignite:ignite-indexing] at 
o.a.i.i.processors.cache.mvcc.CacheMvccAbstractTest.accountsTxReadAll(CacheMvccAbstractTest.java:773)
[11:33:18]W: [org.apache.ignite:ignite-indexing] at 
o.a.i.i.processors.cache.mvcc.CacheMvccAbstractSqlCoordinatorFailoverTest.testAccountsTxSql_Server_Backups0_CoordinatorFails(CacheMvccAbstractSqlCoordinatorFailoverTest.java:35)
[11:33:18]W: [org.apache.ignite:ignite-indexing] at 
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[11:33:18]W: [org.apache.ignite:ignite-indexing] at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
[11:33:18]W: [org.apache.ignite:ignite-indexing] at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[11:33:18]W: [org.apache.ignite:ignite-indexing] at 
java.lang.reflect.Method.invoke(Method.java:498)
[11:33:18]W: [org.apache.ignite:ignite-indexing] at 
junit.framework.TestCase.runTest(TestCase.java:176)
[11:33:18]W: [org.apache.ignite:ignite-indexing]

[jira] [Created] (IGNITE-9891) ODBC: SQLTables does not work with list of table types

[Igor Sapego (JIRA)]

Igor Sapego created IGNITE-9891:
---

 Summary: ODBC: SQLTables does not work with list of table types
 Key: IGNITE-9891
 URL: https://issues.apache.org/jira/browse/IGNITE-9891
 Project: Ignite
  Issue Type: Bug
  Components: odbc
Affects Versions: 2.6
Reporter: Igor Sapego
Assignee: Igor Sapego


{{SQLTables}} do not work with list of table types as stated in 
https://docs.microsoft.com/en-us/sql/odbc/reference/syntax/sqltables-function?view=sql-server-2017



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

Re: Hadoop Suite constantly failing

[Vladimir Ozerov]

I set "blocker" priority. Ticket is under investigation.

On Mon, Oct 15, 2018 at 1:04 PM Maxim Muzafarov  wrote:

> Vladimir,
>
> Thank you!
> I propose to mark this ticket as `Blocker` or move it to 2.8.
>
>
> On Mon, 15 Oct 2018 at 12:42 Vladimir Ozerov  wrote:
>
> > Hi Maxim,
> >
> > I created a ticket for this [1]. Appears to be a kind of regression.
> Needs
> > to be fixed in AI 2.7 scope.
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-9882
> >
> > On Mon, Oct 15, 2018 at 11:18 AM Maxim Muzafarov 
> > wrote:
> >
> > > Igniters,
> > >
> > > Hadoop Test Suite started to fall [1] constantly from October 12 with
> > `Out
> > > of memory` or `Execution timeouts` or `Assertion errors`. Does anyone
> > > investigate this problem?
> > >
> > > Maybe some serious problem is hidden but at least it's a waste of TC
> > agent
> > > resources. It seems to me that there are several problems stratified at
> > > once.
> > >
> > > [1]
> > >
> > >
> >
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Hadoop&page=2&tab=buildTypeHistoryList&branch_IgniteTests24Java8=%3Cdefault%3E
> > > --
> > > --
> > > Maxim Muzafarov
> > >
> >
> --
> --
> Maxim Muzafarov
>

[GitHub] ignite pull request #4993: IGNITE-9882 OOME in Hadoop suite

[tledkov-gridgain]

Github user tledkov-gridgain closed the pull request at:

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


---

[jira] [Created] (IGNITE-9890) Refactor CachePartitionPartialCountersMap#fromCountersMap, no need to sort partitions any time it called.

[Stanilovsky Evgeny (JIRA)]

Stanilovsky Evgeny created IGNITE-9890:
--

 Summary: Refactor 
CachePartitionPartialCountersMap#fromCountersMap, no need to sort partitions 
any time it called.
 Key: IGNITE-9890
 URL: https://issues.apache.org/jira/browse/IGNITE-9890
 Project: Ignite
  Issue Type: Improvement
  Components: general
Affects Versions: 2.6
Reporter: Stanilovsky Evgeny
Assignee: Stanilovsky Evgeny
 Fix For: 2.8


{code:java}
CachePartitionPartialCountersMap#fromCountersMap{code}
we need to store sorted partitions for 
{code:java}
partitionIndex(int partId) {return Arrays.binarySearch{code}
method. Hope need some refactoring here, no need to sort it any time it called, 
we just need to store already sorted collection here.



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

[GitHub] ignite pull request #4994: IGNITE-9889: Add JavaDoc group for TensorFlow.

[dmitrievanthony]

GitHub user dmitrievanthony opened a pull request:

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

IGNITE-9889: Add JavaDoc group for TensorFlow.



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

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

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

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


commit 5c2c711a7d773f48543f936524dc75d151a1d862
Author: Anton Dmitriev 
Date:   2018-10-15T14:59:27Z

IGNITE-9889: Add JavaDoc group for TensorFlow.




---

[jira] [Created] (IGNITE-9889) ML: TensorFlow module is not mentioned in JavaDoc groups

[Anton Dmitriev (JIRA)]

Anton Dmitriev created IGNITE-9889:
--

 Summary: ML: TensorFlow module is not mentioned in JavaDoc groups
 Key: IGNITE-9889
 URL: https://issues.apache.org/jira/browse/IGNITE-9889
 Project: Ignite
  Issue Type: Bug
  Components: ml
Reporter: Anton Dmitriev
Assignee: Anton Dmitriev


Packages from TensorFlow module are not mentioned in JavaDoc groups. We need to 
fix it.



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

[jira] [Created] (IGNITE-9888) Document MVCC continuous queries

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-9888:
---

 Summary: Document MVCC continuous queries
 Key: IGNITE-9888
 URL: https://issues.apache.org/jira/browse/IGNITE-9888
 Project: Ignite
  Issue Type: Task
  Components: documentation
Reporter: Vladimir Ozerov
Assignee: Artem Budnikov
 Fix For: 2.7


Key differences with continuous queries for non-MVCC caches:
1) When event is received, subsequent read of the same key may still return 
previous value for some time (i.e. no guarantee of happens-before between event 
and subsequent read)
2) Keys for notification are kept in memory. If transaction is too large, OOME 
could happen. In order to avoid that, we skip notification of too large 
transactions.

[~rkondakov], could you please elaborate on how is this implemented?



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

Re: Apache Ignite 2.7. Last Mile

[Andrey Gura]

Nikolay,

I'm looking at IGNITE-9737 and IGNITE-9710 which are critical issues
from my point of view.
I need some time for review, possible fixes and merge.
I will keep you informed.
On Mon, Oct 15, 2018 at 1:46 PM Igor Sapego  wrote:
>
> Guys, Python client is in the master and ignite-2.7 already.
>
> Best Regards,
> Igor
>
>
> On Mon, Oct 15, 2018 at 11:33 AM Vladimir Ozerov 
> wrote:
>
> > Nikolay,
> >
> > AI 2.7 will include Python thin client. TC suite is crucial part of this
> > feature, so we should keep the ticket in AI 2.7 scope.
> >
> > On Mon, Oct 15, 2018 at 10:57 AM Nikolay Izhikov 
> > wrote:
> >
> > > Hello, Igniters.
> > >
> > > There is no progress till Friday.
> > > We have 14 tickets mapped to 2.7.
> > >
> > > В Пт, 12/10/2018 в 08:29 +0300, Nikolay Izhikov пишет:
> > > > Hello, Igniters.
> > > >
> > > > We made some progress yesterday.
> > > >
> > > > Please, note, we have 1 new ticket mapped to 2.7 "IGNITE-9852: Create
> > > TeamCity suite for Python thin client"
> > > >
> > > > This ticket doesn't sound like a blocker to me. Let's exclude it from
> > > release scope.
> > > > Thoughts?
> > > >
> > > > Here is the list of remaining tickets(14) mapped to 2.7.
> > > >
> > > > Peter Ivanov - IGNITE-9852, IGNITE-9685,
> > > > Alexey Goncharuk   - IGNITE-9784
> > > > Andrey Kuznetsov   - IGNITE-9737, IGNITE-9710
> > > > Igor Seliverstov   - IGNITE-9749, IGNITE-9292
> > > > Dmitry Melnichuk   - IGNITE-7782
> > > > Ivan Pavlukhin - IGNITE-5935
> > > > Yury Babak - IGNITE-8670
> > > > Roman Kondakov - IGNITE-7953
> > > > Igor Sapego  - IGNITE-9620
> > > > Alexey Stelmak - IGNITE-9776
> > > >
> > > > Unassigned:
> > > >
> > > > IGNITE-9663 - MVCC: Data node failure can cause TX hanging.
> > > >
> > > >
> > > > В Чт, 11/10/2018 в 13:50 +0300, Nikolay Izhikov пишет:
> > > > > Alexey, we all agreed to merge in 2.7 blockers only.
> > > > >
> > > > > Is this a blocker?
> > > > >
> > > > > Anyway, you are more experienced Igniter that I am.
> > > > > If you think we should include this ticket to 2.7 - please, do it.
> > > > >
> > > > > В Чт, 11/10/2018 в 13:08 +0300, Alexey Goncharuk пишет:
> > > > > > Nikolay,
> > > > > >
> > > > > > I am waiting for final benchmark results for 9784, after that I
> > will
> > > merge
> > > > > > the change.
> > > > > >
> > > > > > On the subject of Ignite 2.7 scope, our fellow Igniter Alexey
> > > Platonov have
> > > > > > found another case when a failure handler is incorrectly called on
> > > node
> > > > > > stop: https://issues.apache.org/jira/browse/IGNITE-9834. The case
> > > is rare,
> > > > > > but it is quite an unpleasant UX. Should we include it to 2.7 as
> > > well?
> > > > > >
> > > > > > чт, 11 окт. 2018 г. в 11:22, Nikolay Izhikov  > >:
> > > > > >
> > > > > > > Hello, Igniters.
> > > > > > >
> > > > > > > We made a good progress yesterday.
> > > > > > >
> > > > > > > Here is the list of remaining tickets(17) mapped to 2.7:
> > > > > > >
> > > > > > > Alexey Goncharuk   - IGNITE-9784
> > > > > > > Taras Ledkov   - IGNITE-9171
> > > > > > > Andrey Kuznetsov   - IGNITE-9737, IGNITE-9710
> > > > > > > Peter Ivanov   - IGNITE-9583, IGNITE-9823, IGNITE-9685
> > > > > > > Igor Seliverstov   - IGNITE-9749, IGNITE-9292
> > > > > > > Dmitry Melnichuk   - IGNITE-7782
> > > > > > > Ivan Pavlukhin - IGNITE-5935
> > > > > > > Yury Babak - IGNITE-8670
> > > > > > > Roman Kondakov - IGNITE-7953, IGNITE-9446
> > > > > > > Alexey Stelmak - IGNITE-9776
> > > > > > >
> > > > > > > Unassigned:
> > > > > > >
> > > > > > > IGNITE-9620 - MVCC: select throwing `Transaction is already
> > > completed`> >
> > > > > > > > exception after mvcc missmatch
> > > > > > >
> > > > > > > IGNITE-9663 - MVCC: Data node failure can cause TX hanging.
> > > > > > >
> > > > > > >
> > > > > > > В Чт, 11/10/2018 в 10:40 +0300, Vladimir Ozerov пишет:
> > > > > > > > What kind of help is needed?
> > > > > > > >
> > > > > > > > On Wed, Oct 10, 2018 at 11:51 PM Dmitriy Setrakyan <
> > > > > > >
> > > > > > > dsetrak...@apache.org>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Vladimir Ozerov,
> > > > > > > > >
> > > > > > > > > Can you help with the unassigned MVCC tickets?
> > > > > > > > >
> > > > > > > > > D.
> > > > > > > > >
> > > > > > > > > On Wed, Oct 10, 2018 at 3:32 AM Nikolay Izhikov <
> > > nizhi...@apache.org>
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Hello, Igniters.
> > > > > > > > > >
> > > > > > > > > > I list all contributors that assigned to the 2.7 tickets.
> > > > > > > > > > If you can help them to finish that tickets - please, do.
> > > > > > > > > > Assigners, if you need any help - please, respond to this
> > > thread.
> > > > > > > > > >
> > > > > > > > > > NOTE: We have 6 Unassigned tickets for 2.7. Let's start
> > work
> > > on it!
> > > > > > > > > >
> > > > > > > > > > Peter Ivanov   - IGNITE-9559, IGNITE-9583, IGNITE-9685,
> > > > > > >
> > > > > > > IGNITE-9823
> > > > > > > >

[GitHub] ignite pull request #4767: IGNITE-7953: MVCC TX: continuous queries.

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] ignite pull request #4993: IGNITE-9882 OOME in Hadoop suite

[tledkov-gridgain]

GitHub user tledkov-gridgain opened a pull request:

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

IGNITE-9882  OOME in Hadoop suite

…loses #4514. This closes #4538. This closes #4870."

This reverts commit f97ebff

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

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

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

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


commit 13ddd1db0da4b1f9c2dd90f6f6477cc9393f6610
Author: tledkov-gridgain 
Date:   2018-10-15T14:07:51Z

Revert "IGNITE-9171: SQL: always execute queries in lazy mode. This closes 
#4514. This closes #4538. This closes #4870."

This reverts commit f97ebff




---

[jira] [Created] (IGNITE-9887) A lot of exceptions on cluster deactivation.

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-9887:


 Summary: A lot of exceptions on cluster deactivation.
 Key: IGNITE-9887
 URL: https://issues.apache.org/jira/browse/IGNITE-9887
 Project: Ignite
  Issue Type: Bug
  Components: sql
Reporter: Alexey Kuznetsov


Start node with caches configured via config.
Activate cluster.
Deactivate cluster - got following exception for almost for all caches.

{code}
[2018-10-15 10:31:56,715][ERROR][exchange-worker-#44%tester%][IgniteH2Indexing] 
Failed to drop schema on cache stop (will ignore): c_partitioned
class org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to 
execute statement: DROP SCHEMA IF EXISTS "c_partitioned"
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSystemStatement(IgniteH2Indexing.java:763)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.dropSchema(IgniteH2Indexing.java:715)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.unregisterCache(IgniteH2Indexing.java:3577)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStop0(GridQueryProcessor.java:1693)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStop(GridQueryProcessor.java:885)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.stopCache(GridCacheProcessor.java:1375)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStop(GridCacheProcessor.java:2336)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.processCacheStopRequestOnExchangeDone(GridCacheProcessor.java:2488)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.onExchangeDone(GridCacheProcessor.java:2557)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:1921)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.finishExchangeOnCoordinator(GridDhtPartitionsExchangeFuture.java:3265)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onAllReceived(GridDhtPartitionsExchangeFuture.java:2973)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchangeFuture.java:1321)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:789)
at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2657)
at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2529)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.h2.jdbc.JdbcSQLException: Невозможно удалить "c_partitioned", 
пока существует зависимый объект "SLEEP, SQUARE, UPPERCASE, _LENGTH_, _CUBE_"
Cannot drop "c_partitioned" because "SLEEP, SQUARE, UPPERCASE, _LENGTH_, 
_CUBE_" depends on it; SQL statement:
DROP SCHEMA IF EXISTS "c_partitioned" [90107-197]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:357)
at org.h2.message.DbException.get(DbException.java:179)
at org.h2.command.ddl.DropSchema.update(DropSchema.java:59)
at org.h2.command.CommandContainer.update(CommandContainer.java:102)
at org.h2.command.Command.executeUpdate(Command.java:261)
at 
org.h2.jdbc.JdbcStatement.executeUpdateInternal(JdbcStatement.java:169)
at org.h2.jdbc.JdbcStatement.executeUpdate(JdbcStatement.java:126)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSystemStatement(IgniteH2Indexing.java:758)
... 17 more
{code}



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

[GitHub] ignite pull request #4992: IGNITE-9884 Some tests are incorrectly muted

[oignatenko]

GitHub user oignatenko opened a pull request:

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

IGNITE-9884 Some tests are incorrectly muted



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

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

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

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


commit 1eeca908a8076a8317947dac8a46845964d1d7ea
Author: Oleg Ignatenko 
Date:   2018-08-23T13:13:28Z

IGNITE-9348 ML examples improvements
- wip (logging improved)
-- verified with diffs overview, executing the examples and studying 
execution logs

commit e50b89c392568ba9b93935c4fa6c7f7f93f5ec6f
Author: Oleg Ignatenko 
Date:   2018-08-23T14:45:57Z

Revert "IGNITE-9348 ML examples improvements"

This reverts commit 1eeca908a8076a8317947dac8a46845964d1d7ea.

commit 474024b4c5bbdb3c0a4ed2f0a66238c8054c6674
Author: Oleg Ignatenko 
Date:   2018-08-23T14:57:34Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit 9642b233b5701bdad47ebea163079160227c582a
Author: Oleg Ignatenko 
Date:   2018-08-28T14:01:11Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit 7fc16d013ab725d2ff2e1a1b042c983f11d0c4d4
Author: Oleg Ignatenko 
Date:   2018-08-28T15:13:02Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit d2caba67b156674f051f50faebeafe0871bf0914
Author: Oleg Ignatenko 
Date:   2018-08-29T13:14:07Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit 16775dff51d71ea68b4a3dea98be552130c493ed
Author: Oleg Ignatenko 
Date:   2018-08-30T09:00:56Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit aedb59929974fe205b949225c1a338c68c60cfc8
Author: Oleg Ignatenko 
Date:   2018-08-30T09:42:38Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit 39c6482fcdca506aa33011ed21c98060b4a8c68b
Author: Oleg Ignatenko 
Date:   2018-08-30T11:28:05Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit 33b32a2760a6559c78283b927e3191180d8ed9e1
Author: Oleg Ignatenko 
Date:   2018-08-30T12:31:16Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit 9531028ddd1aef9e95f7e8c8b528086739bbb1b0
Author: Oleg Ignatenko 
Date:   2018-08-30T14:06:34Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit 28f22c6e2fffcb82717ba5da7be2cfd39715c4e3
Author: Oleg Ignatenko 
Date:   2018-08-30T16:41:51Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit aacac88db519187413b0fc5ff9d0e55b8f8cff22
Author: Oleg Ignatenko 
Date:   2018-08-31T10:12:32Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit 897f920dde46022849b13f9fb86dba8e54119a56
Author: Oleg Ignatenko 
Date:   2018-08-31T13:57:14Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit 114c79e54c1b316006ccc3ff22d20d902f9313df
Author: Oleg Ignatenko 
Date:   2018-08-31T17:39:16Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit fd6b659bb8be1992618ce4ce91f568a0988b3afa
Author: Oleg Ignatenko 
Date:   2018-09-02T06:11:42Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit 6ae6d1d3cf9743d8d466be0330511ddc8589e944
Author: Oleg Ignatenko 
Date:   2018-09-03T10:27:35Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit e8b27dbd3d0c1cbdb7a7659175f5c7bb447482bf
Author: Oleg Ignatenko 
Date:   2018-09-04T09:49:44Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit 622c82efdd0aa182fadea6b7ffa5d4615521a3f5
Author: Oleg Ignatenko 
Date:   2018-09-05T10:50:28Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit fb844fe3751e2e8ae87e6b8030b0e4bd659df9c2
Author: Oleg Ignatenko 
Date:   2018-09-05T11:45:58Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit 480ed78869277d7e32f725ab71bec9621f1ac03a
Author: Oleg Ignatenko 
Date:   2018-09-06T07:52:55Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit c99762498f617c0e98ea3062a43c0b30092166ef
Author: Oleg Ignatenko 
Date:   2018-09-06T14:45:04Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit 2e17175225c72f747d370b5fee96f8be69d6d2cb
Author: Oleg Ignatenko 
Date:   2018-09-06T17:33:54Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit 9ebcd9a2fe5966b0bf42a95484395867c15d863f
Author: Oleg Ignatenko 
Date:   2018-09-07T13:38:51Z

Merge branch 'master' of https://github.com/apache/ignite 

Re: I want to contribute | Help Needed

[Павлухин Иван]

Hi Snigdhadeb,

Welcome to Apache Ignite Community!

Usually each contribution is related to a ticket in Jira
https://issues.apache.org/jira/projects/IGNITE. Do you have such ticket
already?
To start working on a ticket you need to get a contributor rights to assign
ticket to yourself. Please share your account name in Jira.
After that you can create pull request from any fork to
https://github.com/apache/ignite.

Do not hesitate to ask on dev list in case of any question.

P.S. Additional references that should boost your on-boarding.

Get familiar with Apache 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

сб, 13 окт. 2018 г. в 17:02, Snigdhadeb Mukherjee <
snigdhadeb.mukher...@live.com>:

> Hi,
>
>
> Adding dpavlov from community mail id.
>
> I being the very first timer need help and guidance.
>
>
> Regards,
> Snigdhadeb
>
> 
> From: Snigdhadeb Mukherjee
> Sent: Saturday, October 13, 2018 3:46 PM
> To: dev@ignite.apache.org
> Subject: I want to contribute | Help Needed
>
>
> HI Team,
>
>
> I would very much like to contribute to the Ignite project. Could you
> please guide and help me in this regard?
>
>
> Regards,
>
> Snigdhadeb
>


-- 
Best regards,
Ivan Pavlukhin

[GitHub] ignite pull request #4991: IGNITE-9886: Split Continuous Query 1 onto severa...

[avplatonov]

GitHub user avplatonov opened a pull request:

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

IGNITE-9886: Split Continuous Query 1 onto several configs



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

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

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

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


commit 8fe4973fc059729ea06c0fd5193930fe9e12a4a0
Author: Alexey Platonov 
Date:   2018-10-15T13:09:37Z

splitting long suite onto three ones




---

[GitHub] ignite pull request #4990: ignite-2.5.1-141-IL-1

[dgovorukhin]

GitHub user dgovorukhin opened a pull request:

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

ignite-2.5.1-141-IL-1



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

$ git pull https://github.com/gridgain/apache-ignite ignite-2.5.1-141-IL-1

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

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


commit dc8ba0932a944f3e966ebbe2af053488d1fe9b28
Author: Sergey Chugunov 
Date:   2018-05-04T12:26:02Z

IGNITE-8421 new implementation of getChildren method is added tolerating 
KeeperException.NoNodeException - Fixes #3939.

Signed-off-by: dpavlov 

(cherry-picked from commit #02e9ca993178d4aa648d06cb93ce1a9277eb22b1)

commit 0d37bd6749829ce07fbd4b0d2344b62588177628
Author: Ivan Rakov 
Date:   2018-06-05T11:42:43Z

IGNITE-8682 Attempt to configure IGFS in persistent mode without specific 
data region ends with AssertionError

(cherry picked from commit 2fe0a10)

commit 0c20c51025e5a550b7f3d8458acae27ec8cdcef5
Author: a-polyakov 
Date:   2018-06-05T15:49:19Z

IGNITE-8602 Add support filter "label null" for control.sh tx utility - 
Fixes #4073.

Signed-off-by: Alexey Goncharuk 

(cherry picked from commit 3372590)

commit 455777d2cd2bd6b83d69dbdbbd7e95b4f375bb75
Author: a-polyakov 
Date:   2018-06-05T16:01:03Z

IGNITE-8467 Fixed filter minSize for transactions utility control.sh. Fixes 
#4069

(cherry picked from commit d61c068)

commit c40f7659f24b6037485a5ac5e1965b0c6bd573bb
Author: Sergey Kosarev 
Date:   2018-06-06T08:19:26Z

IGNITE-8587 GridToStringBuilder use ConcurrentHashMap to avoid global locks 
on classCache - Fixes #4059.

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

commit af026c7840101e2c57c7dd882baabddb6df2fa82
Author: Ilya Lantukh 
Date:   2018-06-04T22:24:37Z

IGNITE-8693 SQL JOIN between PARTITIONED and REPLICATED cache fails - Fixes 
#4120.

Signed-off-by: Ivan Rakov 

(cherry picked from commit bc35ce0)

commit a84538a9df8ace432411736289ec8371dee215e2
Author: Sergey Kosarev 
Date:   2018-06-06T09:59:28Z

IGNITE-8696 control.sh utility does not show atomicity mode - Fixes #4127.

Signed-off-by: Ivan Rakov 
(cherry picked from commit 78e5d970be74c04b01857123b1a623038aa18440)

commit fff8a4cc48ae7d8a47f8911763a71d0d59042d87
Author: Andrey Kuznetsov 
Date:   2018-06-06T12:02:35Z

IGNITE-8642 Added thread dumping to FailureProcessor

Signed-off-by: Andrey Gura 

commit 6ea23844cfb0294a0cf3f3c21787aeff30939bcf
Author: Dmitriy Sorokin 
Date:   2018-06-06T11:34:04Z

IGNITE-8311 IgniteClientRejoinTest.testClientsReconnectDisabled causes 
exchange-worker to terminate via NPE

Signed-off-by: Andrey Gura 

commit bad52d3843925d831e6d357a4382731751ae6bb7
Author: Ilya Lantukh 
Date:   2018-06-04T14:07:52Z

GG-13862 : Disabled fast eviction.

(cherry picked from commit 786633d)

commit 6956097ceedd2e3e9edcb627d97e49afb7f0a26d
Author: Pavel Kovalenko 
Date:   2018-06-06T12:24:39Z

IGNITE-8482 Skip 2-phase partition release wait in case of activation or 
dynamic caches start - Fixes #4078.

Signed-off-by: Alexey Goncharuk 

(cherry picked from commit 7c565d2)

commit d777c76eadd0a2ccc50f1031c42626b135da5906
Author: Dmitriy Govorukhin 
Date:   2018-06-06T14:20:18Z

IGNITE-8685 Fixed switch segment record size - Fixes #4130.

Signed-off-by: Alexey Goncharuk 

(cherry picked from commit 2a048bd)

commit ef4782d8a60eea870b43933480f2c9695c9fc55d
Author: Alexey Goncharuk 
Date:   2018-06-07T11:55:13Z

IGNITE-8706 Fixed testMemoryUsageMultipleNodes

commit 6902383e01ee69d7efff9613a68f3fc419152305
Author: Pavel Kovalenko 
Date:   2018-05-14T10:14:52Z

IGNITE-8422 Tests fix for Zookeeper discovery split brain detection 
shouldn't consider client nodes - Fixes #3975.

Signed-off-by: dpavlov 

(cherry-picked from commit #19cbf8058b48a1f8fec60f7ceac70229e7c5391a)

commit 6eef070f8e0627e2986d870cc09ceb9cb351ee0d
Author: Sergey Chugunov 
Date:   2018-05-14T17:09:33Z

IGNITE-8487 tmpfs is employed by ZooKeeper tests - Fixes #3994.

Signed-off-by: dpavlov 

(cherry-picked from commit #67be050a2c7b9efdef2388c579fc060c68ff8a38)

commit c9b82cc632ad1cac51661f729f8605ab6c97c1dd
Author: Anton Kalashnikov 
Date:   2018-06-08T15:24:09Z

IGNITE-8739 Implemented WA for tcp communication SPI hanging on descriptor 
reservation - Fixes #4148.

Signed-off-by: Alexey Goncharuk 

(cherry picked from commit 7021651)

commit 45953256ef0f09fd5450f6f6c6967a539c5cd395
Author: Pavel Kovalenko 
Date:   2018-05-03T14:01:20Z

IGNITE-8226 Improved logging - Fixes #3796.

Signed-o

[jira] [Created] (IGNITE-9886) Split Continuous Query 1 onto several config

[Alexey Platonov (JIRA)]

Alexey Platonov created IGNITE-9886:
---

 Summary: Split Continuous Query 1 onto several config
 Key: IGNITE-9886
 URL: https://issues.apache.org/jira/browse/IGNITE-9886
 Project: Ignite
  Issue Type: Bug
Reporter: Alexey Platonov
Assignee: Alexey Platonov


At the current state this config require a lot of time for one test-run 
(>100min). We need to split this onto several configs with running time <= 
60min.



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

[GitHub] ignite pull request #4989: IGNITE-9883 Do not wait for topology exchange whi...

[ibessonov]

GitHub user ibessonov opened a pull request:

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

IGNITE-9883 Do not wait for topology exchange while other cache starts or 
stops.



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

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

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

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


commit d84b5d639863ea39e585478b2db8c58af4203c4e
Author: ibessonov 
Date:   2018-10-15T12:55:27Z

IGNITE-9883 Do not wait for topology exchange while other cache starts or 
stops.




---

[jira] [Created] (IGNITE-9885) Issue in termination of GridWorkerFuture

[Vladislav Pyatkov (JIRA)]

Vladislav Pyatkov created IGNITE-9885:
-

 Summary: Issue in termination of GridWorkerFuture
 Key: IGNITE-9885
 URL: https://issues.apache.org/jira/browse/IGNITE-9885
 Project: Ignite
  Issue Type: Improvement
Reporter: Vladislav Pyatkov


Can to start a closure through method like 
{{GridClosureProcessor#runLocalSafe(java.lang.Runnable)}}

but does not possible to wait termination of the task after cancellation.

For understanding need to look at {{GridWorkerFuture.cancel}}. The method affix 
an {{interrupted}} flag on executed thread, but not wait task termination. 
Having an instance of GridWorkerFuture, you can not to await real termination 
of task.



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

[jira] [Created] (IGNITE-9884) Some tests are incorrectly muted

[Oleg Ignatenko (JIRA)]

Oleg Ignatenko created IGNITE-9884:
--

 Summary: Some tests are incorrectly muted
 Key: IGNITE-9884
 URL: https://issues.apache.org/jira/browse/IGNITE-9884
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.6
Reporter: Oleg Ignatenko


The following tests pass when unmuted. It looks like the reasons that made them 
fail in the past were somehow resolved by later code changes but tests were 
forgotten to unmute:
{panel}
GridCacheStoreManagerDeserializationTest#_testBinaryStream
IgniteCacheConfigVariationsFullApiTest#_testDeletedEntriesFlag
IgniteCacheConfigVariationsFullApiTest#_testEvictExpired
GridCacheStoreManagerDeserializationTest#_testBinaryStream
PageIdDistributionTest#_testRealHistory
GridEventConsumeSelfTest#_testMultithreadedWithNodeRestart
BPlusTreeSelfTest#_testBenchInvoke
IgniteClientReconnectMassiveShutdownTest#_testMassiveServersShutdown1
IgniteClientReconnectMassiveShutdownTest#_testMassiveServersShutdown3
TcpDiscoveryMultiThreadedTest#_testMultiThreadedServersRestart (passes)
GridServiceProcessorBatchDeploySelfTest#_testDeployAllTopologyChange
GridServiceProcessorBatchDeploySelfTest#_testDeployAllTopologyChangeFail
GridServiceProcessorBatchDeploySelfTest#_testCancelAllTopologyChange
{panel}

The following tests are muted by renaming (prefixing with underscore, 
{{_test...}}, should use standard muting by known JIRA tickets instead:
{panel}
- GridCacheAbstractFullApiSelfTest#_testInvokeAllMultithreaded
  should fail with the reference to IGNITE-4380
- CacheMvccTransactionsTest#_testNodesRestartNoHang
  should fail with the reference to IGNITE-5935
{panel}



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

Applicability of term 'cache' to Apache Ignite

[Ilya Lantukh]

Hi Igniters,

I would like to rise a question how we use the term *'cache'* in Ignite and
how it corresponds to terminology in IT industry in general.

>From wikipedia:
In computing , a *cache* /kæʃ/
 *kash*
, is a
hardware or software component that stores data so that future requests for
that data can be served faster; the data stored in a cache might be the
result of an earlier computation or a copy of data stored elsewhere. [1]

When the first version of Ignite was released, this term was correct. We
positioned Ignite mostly as an intermediate storage layer between
application and a database, designed to make data access faster.

However, since addition of native persistence we started to call Ignite a
"memory-centric database", and as far as I know, some organizations now use
it as a primary data storage, without underlying database. In this case,
calling our storage unit a *'cache'* causes unnecessary confusion.

Thus, I suggest to rename IgniteCache in Ignite 3.0 to something that would
fit both use-cases.
Personally I like the term IgniteSpace.

[1] https://en.wikipedia.org/wiki/Cache_(computing)
-- 
Best regards,
Ilya

[jira] [Created] (IGNITE-9883) Do not block get/getAll during start/stop operations on other cache.

[Ivan Bessonov (JIRA)]

Ivan Bessonov created IGNITE-9883:
-

 Summary: Do not block get/getAll during start/stop operations on 
other cache.
 Key: IGNITE-9883
 URL: https://issues.apache.org/jira/browse/IGNITE-9883
 Project: Ignite
  Issue Type: Sub-task
Reporter: Ivan Bessonov
Assignee: Ivan Bessonov


Do not block get/getAll during start/stop operations on other cache.



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

Re: Python thin client

[Igor Sapego]

Dmitry,

Since Python thin client is now in master, can you please add it to our
"Thin clients features" wiki page, so we can track the feature parity
of our clients? Or just tell me which features are supported, so I can fill
it myself.

[1] -
https://cwiki.apache.org/confluence/display/IGNITE/Thin+clients+features

Best Regards,
Igor


On Mon, Oct 15, 2018 at 1:38 PM Igor Sapego  wrote:

> Hi,
>
> I've just merged Python thin client to the master and ignite-2.7
>
> Also, I like how the python's results improved and now are comparable to
> node.js.
>
> Great job, guys!
>
> Best Regards,
> Igor
>
>
> On Sat, Oct 13, 2018 at 3:53 PM Степан Пильщиков <
> pilshchikov@gmail.com> wrote:
>
>> Hi
>>
>> Made new run and client definitely become faster
>> I think its right direction for improvements
>>
>> Also rerun java bench with compiler=none option
>>
>> All results you can get in
>> https://issues.apache.org/jira/browse/IGNITE-9824
>> (last comment)
>>
>> сб, 13 окт. 2018 г. в 4:56, Pavel Petroshenko :
>>
>> > Hi Stepan,
>> >
>> > Re your performance questions.
>> >
>> > Firstly, please pull out the latest sources from the ignite-7782 branch
>> as
>> > it has some performance optimizations recently implemented.
>> >
>> > Secondly, Hotspot is a pretty advanced dynamic adaptive compiler and
>> it's
>> > not fair to compare it to a purely interpreted Python language
>> > implementation. To get comparable results, please run your Java
>> benchmark
>> > with -Djava.compiler=NONE. It turns the dynamic compiler off at
>> runtime. I
>> > just did this exercise myself and got comparable scores.
>> >
>> > Please let me know if you still see any significant difference with the
>> > flag set.
>> >
>> > Thanks,
>> > P.
>> >
>> > On Fri, Oct 12, 2018 at 10:02 AM Dmitry Melnichuk <
>> > dmitry.melnic...@nobitlost.com> wrote:
>> >
>> >> Igor,
>> >>
>> >> I fixed my files.
>> >>
>> >> Dmitry
>> >>
>> >> On 10/13/18 12:14 AM, Igor Sapego wrote:
>> >> > Dmitry,
>> >> >
>> >> > I've run the tests and it appears that there are a lot of files
>> without
>> >> > Apache
>> >> > licenses in Python client: [1] (See Unapproved licenses list).
>> >> >
>> >> > Can you either add headers or exclude file from the check, if you can
>> >> not
>> >> > add one? I.e. to this list: [2]
>> >> >
>> >> > [1] -
>> >> >
>> >>
>> https://ci.ignite.apache.org/repository/download/IgniteTests24Java8_LicensesHeaders/2069024:id/rat.zip%21/target/rat.txt
>> >> > [2] -
>> https://github.com/apache/ignite/blob/master/parent/pom.xml#L817
>> >> >
>> >> > Best Regards,
>> >> > Igor
>> >> >
>> >> >
>> >> > On Thu, Oct 11, 2018 at 1:13 PM Igor Sapego 
>> wrote:
>> >> >
>> >> >> Ok, I've filed a ticket [1] for the performance investigation and
>> >> targeted
>> >> >> it to 2.8. Feel free to assign it to yourself.
>> >> >>
>> >> >> I'm going to merge the ticket to master and ignite-2.7 branches by
>> the
>> >> >> end of the week, if no one have any objections.
>> >> >>
>> >> >> [1] - https://issues.apache.org/jira/browse/IGNITE-9850
>> >> >>
>> >> >> Best Regards,
>> >> >> Igor
>> >> >>
>> >> >>
>> >> >> On Thu, Oct 11, 2018 at 12:18 PM Dmitry Melnichuk <
>> >> >> dmitry.melnic...@nobitlost.com> wrote:
>> >> >>
>> >> >>> Stepan,
>> >> >>>
>> >> >>> Thank you for answering my question and for the updated results.
>> >> >>>
>> >> >>> I have ran the profiler (cProfile) against the benchmark code you
>> >> >>> provided and have not found any particular bottleneck. One cycle
>> took
>> >> me
>> >> >>> 434 μs, which is the same order of magnitude as your result.
>> >> >>>
>> >> >>> I will need more time to analyze the performance of my client and
>> >> find a
>> >> >>> way to improve it. But is it a real stopper/blocker for the client
>> >> >>> itself? If there are no other issues, may we merge and release the
>> >> >>> client? Plus submit a jira-improvement to further investigate the
>> >> >>> performance of the Python platform.
>> >> >>>
>> >> >>> Dmitry
>> >> >>>
>> >> >>> On 10/11/18 4:19 PM, Степан Пильщиков wrote:
>> >>  Dmitry,
>> >> 
>> >>  pip install -e from latest sources
>> >> 
>> >>  On Thu, 11 Oct 2018, 06:37 Dmitry Melnichuk, <
>> >> >>> dmitry.melnic...@nobitlost.com>
>> >>  wrote:
>> >> 
>> >> > Stepan!
>> >> >
>> >> > Please tell me one thing about how you created the environment
>> for
>> >> your
>> >> > benchmarks, namely: how did you install the Python client. Did
>> you
>> >> just
>> >> > do `pip install pyignite`, or did you pull my working branch from
>> >> the
>> >> > downstream repository and did `pip install -e
>> >> > ignite/modules/platforms/python`?
>> >> >
>> >> > I highly recommend the latter, because PyPI version do not yet
>> >> include
>> >> > the latest improvements I did thanks to Dmitriy “qvad”
>> Sherstobitov.
>> >> > These improvements can have a noticeable positive effect on
>> speed.
>> >> >
>> >> > Dmitry
>> >> >
>> >> > On 10/10/18 11:06 P

[GitHub] ignite pull request #4988: IGNITE-9854 Correct remove from dirtyPages and se...

[ivandasch]

GitHub user ivandasch opened a pull request:

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

IGNITE-9854 Correct remove from dirtyPages and segCheckpointPages



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

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

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

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


commit 154de1f30913663a7a9458a691d7a5da3b8a2814
Author: Ivan Daschinskiy 
Date:   2018-10-15T10:45:49Z

IGNITE-9854 Correct remove from dirtyPages and segCheckpointPages




---

Re: Apache Ignite 2.7. Last Mile

[Igor Sapego]

Guys, Python client is in the master and ignite-2.7 already.

Best Regards,
Igor


On Mon, Oct 15, 2018 at 11:33 AM Vladimir Ozerov 
wrote:

> Nikolay,
>
> AI 2.7 will include Python thin client. TC suite is crucial part of this
> feature, so we should keep the ticket in AI 2.7 scope.
>
> On Mon, Oct 15, 2018 at 10:57 AM Nikolay Izhikov 
> wrote:
>
> > Hello, Igniters.
> >
> > There is no progress till Friday.
> > We have 14 tickets mapped to 2.7.
> >
> > В Пт, 12/10/2018 в 08:29 +0300, Nikolay Izhikov пишет:
> > > Hello, Igniters.
> > >
> > > We made some progress yesterday.
> > >
> > > Please, note, we have 1 new ticket mapped to 2.7 "IGNITE-9852: Create
> > TeamCity suite for Python thin client"
> > >
> > > This ticket doesn't sound like a blocker to me. Let's exclude it from
> > release scope.
> > > Thoughts?
> > >
> > > Here is the list of remaining tickets(14) mapped to 2.7.
> > >
> > > Peter Ivanov - IGNITE-9852, IGNITE-9685,
> > > Alexey Goncharuk   - IGNITE-9784
> > > Andrey Kuznetsov   - IGNITE-9737, IGNITE-9710
> > > Igor Seliverstov   - IGNITE-9749, IGNITE-9292
> > > Dmitry Melnichuk   - IGNITE-7782
> > > Ivan Pavlukhin - IGNITE-5935
> > > Yury Babak - IGNITE-8670
> > > Roman Kondakov - IGNITE-7953
> > > Igor Sapego  - IGNITE-9620
> > > Alexey Stelmak - IGNITE-9776
> > >
> > > Unassigned:
> > >
> > > IGNITE-9663 - MVCC: Data node failure can cause TX hanging.
> > >
> > >
> > > В Чт, 11/10/2018 в 13:50 +0300, Nikolay Izhikov пишет:
> > > > Alexey, we all agreed to merge in 2.7 blockers only.
> > > >
> > > > Is this a blocker?
> > > >
> > > > Anyway, you are more experienced Igniter that I am.
> > > > If you think we should include this ticket to 2.7 - please, do it.
> > > >
> > > > В Чт, 11/10/2018 в 13:08 +0300, Alexey Goncharuk пишет:
> > > > > Nikolay,
> > > > >
> > > > > I am waiting for final benchmark results for 9784, after that I
> will
> > merge
> > > > > the change.
> > > > >
> > > > > On the subject of Ignite 2.7 scope, our fellow Igniter Alexey
> > Platonov have
> > > > > found another case when a failure handler is incorrectly called on
> > node
> > > > > stop: https://issues.apache.org/jira/browse/IGNITE-9834. The case
> > is rare,
> > > > > but it is quite an unpleasant UX. Should we include it to 2.7 as
> > well?
> > > > >
> > > > > чт, 11 окт. 2018 г. в 11:22, Nikolay Izhikov  >:
> > > > >
> > > > > > Hello, Igniters.
> > > > > >
> > > > > > We made a good progress yesterday.
> > > > > >
> > > > > > Here is the list of remaining tickets(17) mapped to 2.7:
> > > > > >
> > > > > > Alexey Goncharuk   - IGNITE-9784
> > > > > > Taras Ledkov   - IGNITE-9171
> > > > > > Andrey Kuznetsov   - IGNITE-9737, IGNITE-9710
> > > > > > Peter Ivanov   - IGNITE-9583, IGNITE-9823, IGNITE-9685
> > > > > > Igor Seliverstov   - IGNITE-9749, IGNITE-9292
> > > > > > Dmitry Melnichuk   - IGNITE-7782
> > > > > > Ivan Pavlukhin - IGNITE-5935
> > > > > > Yury Babak - IGNITE-8670
> > > > > > Roman Kondakov - IGNITE-7953, IGNITE-9446
> > > > > > Alexey Stelmak - IGNITE-9776
> > > > > >
> > > > > > Unassigned:
> > > > > >
> > > > > > IGNITE-9620 - MVCC: select throwing `Transaction is already
> > completed`> >
> > > > > > > exception after mvcc missmatch
> > > > > >
> > > > > > IGNITE-9663 - MVCC: Data node failure can cause TX hanging.
> > > > > >
> > > > > >
> > > > > > В Чт, 11/10/2018 в 10:40 +0300, Vladimir Ozerov пишет:
> > > > > > > What kind of help is needed?
> > > > > > >
> > > > > > > On Wed, Oct 10, 2018 at 11:51 PM Dmitriy Setrakyan <
> > > > > >
> > > > > > dsetrak...@apache.org>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Vladimir Ozerov,
> > > > > > > >
> > > > > > > > Can you help with the unassigned MVCC tickets?
> > > > > > > >
> > > > > > > > D.
> > > > > > > >
> > > > > > > > On Wed, Oct 10, 2018 at 3:32 AM Nikolay Izhikov <
> > nizhi...@apache.org>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Hello, Igniters.
> > > > > > > > >
> > > > > > > > > I list all contributors that assigned to the 2.7 tickets.
> > > > > > > > > If you can help them to finish that tickets - please, do.
> > > > > > > > > Assigners, if you need any help - please, respond to this
> > thread.
> > > > > > > > >
> > > > > > > > > NOTE: We have 6 Unassigned tickets for 2.7. Let's start
> work
> > on it!
> > > > > > > > >
> > > > > > > > > Peter Ivanov   - IGNITE-9559, IGNITE-9583, IGNITE-9685,
> > > > > >
> > > > > > IGNITE-9823
> > > > > > > > > Andrey Kuznetsov   - IGNITE-9737, IGNITE-9710
> > > > > > > > > Taras Ledkov   - IGNITE-9171
> > > > > > > > > Alexey Goncharuk   - IGNITE-9784
> > > > > > > > > Dmitriy Govorukhin - IGNITE-9550
> > > > > > > > > Igor Seliverstov   - IGNITE-9749
> > > > > > > > > Dmitry Melnichuk   - IGNITE-7782
> > > > > > > > > Alexey Platonov- IGNITE-9726
> > > > > > > > > Ivan Pavlukhin - IGNITE-5935
> > > > > > > > > Yury Babak - IGNITE-8670
> > > > > > > > > Roman Kondakov - IGNITE-7953, 

Re: Python thin client

[Igor Sapego]

Hi,

I've just merged Python thin client to the master and ignite-2.7

Also, I like how the python's results improved and now are comparable to
node.js.

Great job, guys!

Best Regards,
Igor


On Sat, Oct 13, 2018 at 3:53 PM Степан Пильщиков 
wrote:

> Hi
>
> Made new run and client definitely become faster
> I think its right direction for improvements
>
> Also rerun java bench with compiler=none option
>
> All results you can get in
> https://issues.apache.org/jira/browse/IGNITE-9824
> (last comment)
>
> сб, 13 окт. 2018 г. в 4:56, Pavel Petroshenko :
>
> > Hi Stepan,
> >
> > Re your performance questions.
> >
> > Firstly, please pull out the latest sources from the ignite-7782 branch
> as
> > it has some performance optimizations recently implemented.
> >
> > Secondly, Hotspot is a pretty advanced dynamic adaptive compiler and it's
> > not fair to compare it to a purely interpreted Python language
> > implementation. To get comparable results, please run your Java benchmark
> > with -Djava.compiler=NONE. It turns the dynamic compiler off at runtime.
> I
> > just did this exercise myself and got comparable scores.
> >
> > Please let me know if you still see any significant difference with the
> > flag set.
> >
> > Thanks,
> > P.
> >
> > On Fri, Oct 12, 2018 at 10:02 AM Dmitry Melnichuk <
> > dmitry.melnic...@nobitlost.com> wrote:
> >
> >> Igor,
> >>
> >> I fixed my files.
> >>
> >> Dmitry
> >>
> >> On 10/13/18 12:14 AM, Igor Sapego wrote:
> >> > Dmitry,
> >> >
> >> > I've run the tests and it appears that there are a lot of files
> without
> >> > Apache
> >> > licenses in Python client: [1] (See Unapproved licenses list).
> >> >
> >> > Can you either add headers or exclude file from the check, if you can
> >> not
> >> > add one? I.e. to this list: [2]
> >> >
> >> > [1] -
> >> >
> >>
> https://ci.ignite.apache.org/repository/download/IgniteTests24Java8_LicensesHeaders/2069024:id/rat.zip%21/target/rat.txt
> >> > [2] -
> https://github.com/apache/ignite/blob/master/parent/pom.xml#L817
> >> >
> >> > Best Regards,
> >> > Igor
> >> >
> >> >
> >> > On Thu, Oct 11, 2018 at 1:13 PM Igor Sapego 
> wrote:
> >> >
> >> >> Ok, I've filed a ticket [1] for the performance investigation and
> >> targeted
> >> >> it to 2.8. Feel free to assign it to yourself.
> >> >>
> >> >> I'm going to merge the ticket to master and ignite-2.7 branches by
> the
> >> >> end of the week, if no one have any objections.
> >> >>
> >> >> [1] - https://issues.apache.org/jira/browse/IGNITE-9850
> >> >>
> >> >> Best Regards,
> >> >> Igor
> >> >>
> >> >>
> >> >> On Thu, Oct 11, 2018 at 12:18 PM Dmitry Melnichuk <
> >> >> dmitry.melnic...@nobitlost.com> wrote:
> >> >>
> >> >>> Stepan,
> >> >>>
> >> >>> Thank you for answering my question and for the updated results.
> >> >>>
> >> >>> I have ran the profiler (cProfile) against the benchmark code you
> >> >>> provided and have not found any particular bottleneck. One cycle
> took
> >> me
> >> >>> 434 μs, which is the same order of magnitude as your result.
> >> >>>
> >> >>> I will need more time to analyze the performance of my client and
> >> find a
> >> >>> way to improve it. But is it a real stopper/blocker for the client
> >> >>> itself? If there are no other issues, may we merge and release the
> >> >>> client? Plus submit a jira-improvement to further investigate the
> >> >>> performance of the Python platform.
> >> >>>
> >> >>> Dmitry
> >> >>>
> >> >>> On 10/11/18 4:19 PM, Степан Пильщиков wrote:
> >>  Dmitry,
> >> 
> >>  pip install -e from latest sources
> >> 
> >>  On Thu, 11 Oct 2018, 06:37 Dmitry Melnichuk, <
> >> >>> dmitry.melnic...@nobitlost.com>
> >>  wrote:
> >> 
> >> > Stepan!
> >> >
> >> > Please tell me one thing about how you created the environment for
> >> your
> >> > benchmarks, namely: how did you install the Python client. Did you
> >> just
> >> > do `pip install pyignite`, or did you pull my working branch from
> >> the
> >> > downstream repository and did `pip install -e
> >> > ignite/modules/platforms/python`?
> >> >
> >> > I highly recommend the latter, because PyPI version do not yet
> >> include
> >> > the latest improvements I did thanks to Dmitriy “qvad”
> Sherstobitov.
> >> > These improvements can have a noticeable positive effect on speed.
> >> >
> >> > Dmitry
> >> >
> >> > On 10/10/18 11:06 PM, Степан Пильщиков wrote:
> >> >> Dmitry,
> >> >>
> >> >> Thanks for review
> >> >>
> >> >> Agree with all suggestions.
> >> >>
> >> >> Made and run new benches without any redundant operations
> (prints,
> >> >>> time
> >> >> calculation), only with "put" in "while true" cycle (almost)
> >> >> Case description, environment, results and code in ticket
> >> >> https://issues.apache.org/jira/browse/IGNITE-9824 (last comment)
> >> >>
> >> >> Please review new metrics
> >> >> Because picture is not changed so much, python still have
> >> pe

[GitHub] ignite pull request #4278: IGNITE-7782 Thin Client lib: Python

[asfgit]

Github user asfgit closed the pull request at:

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


---

Re: Hadoop Suite constantly failing

[Maxim Muzafarov]

Vladimir,

Thank you!
I propose to mark this ticket as `Blocker` or move it to 2.8.


On Mon, 15 Oct 2018 at 12:42 Vladimir Ozerov  wrote:

> Hi Maxim,
>
> I created a ticket for this [1]. Appears to be a kind of regression. Needs
> to be fixed in AI 2.7 scope.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-9882
>
> On Mon, Oct 15, 2018 at 11:18 AM Maxim Muzafarov 
> wrote:
>
> > Igniters,
> >
> > Hadoop Test Suite started to fall [1] constantly from October 12 with
> `Out
> > of memory` or `Execution timeouts` or `Assertion errors`. Does anyone
> > investigate this problem?
> >
> > Maybe some serious problem is hidden but at least it's a waste of TC
> agent
> > resources. It seems to me that there are several problems stratified at
> > once.
> >
> > [1]
> >
> >
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Hadoop&page=2&tab=buildTypeHistoryList&branch_IgniteTests24Java8=%3Cdefault%3E
> > --
> > --
> > Maxim Muzafarov
> >
>
-- 
--
Maxim Muzafarov

[GitHub] ignite pull request #4987: Ignite 9630

[SGrimstad]

GitHub user SGrimstad opened a pull request:

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

Ignite 9630



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

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

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

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


commit 1a41a15edf6ad9f394fc09fc91052abbf7004d7f
Author: SGrimstad 
Date:   2018-09-27T14:23:28Z

IGNITE-9632 implementation

commit 03d73e26e4ccee1753f213d01f5656788c135d85
Author: SGrimstad 
Date:   2018-10-12T13:58:09Z

IGNITE-9630 implementation

commit dd43a544e2ae29595090fc29efd404f3df58d002
Author: SGrimstad 
Date:   2018-10-15T09:11:03Z

Merge branch 'master' into IGNITE-9630




---

Re: Hadoop Suite constantly failing

[Vladimir Ozerov]

Hi Maxim,

I created a ticket for this [1]. Appears to be a kind of regression. Needs
to be fixed in AI 2.7 scope.

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

On Mon, Oct 15, 2018 at 11:18 AM Maxim Muzafarov  wrote:

> Igniters,
>
> Hadoop Test Suite started to fall [1] constantly from October 12 with `Out
> of memory` or `Execution timeouts` or `Assertion errors`. Does anyone
> investigate this problem?
>
> Maybe some serious problem is hidden but at least it's a waste of TC agent
> resources. It seems to me that there are several problems stratified at
> once.
>
> [1]
>
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Hadoop&page=2&tab=buildTypeHistoryList&branch_IgniteTests24Java8=%3Cdefault%3E
> --
> --
> Maxim Muzafarov
>

[jira] [Created] (IGNITE-9882) OOME in Hadoop suite

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-9882:
---

 Summary: OOME in Hadoop suite
 Key: IGNITE-9882
 URL: https://issues.apache.org/jira/browse/IGNITE-9882
 Project: Ignite
  Issue Type: Task
  Components: hadoop, sql
Reporter: Vladimir Ozerov
Assignee: Taras Ledkov
 Fix For: 2.7


Hadoop suite starts failing with OOME after several commits were merged. I 
suspect that it may be related to IGNITE-9171 merge. See two runs:
1) Before: https://ci.ignite.apache.org/viewLog.html?buildId=2088527&;
2) After: https://ci.ignite.apache.org/viewLog.html?buildId=2088768&;



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

[GitHub] ignite pull request #4945: IGNITE-9685 [ML] Add ignite-tensorflow module to ...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] ignite pull request #4986: Ignite-2.5.1-p141-pme-2

[dgovorukhin]

GitHub user dgovorukhin opened a pull request:

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

Ignite-2.5.1-p141-pme-2



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

$ git pull https://github.com/gridgain/apache-ignite ignite-2.5.1-p141-pme-2

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

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


commit 6ea23844cfb0294a0cf3f3c21787aeff30939bcf
Author: Dmitriy Sorokin 
Date:   2018-06-06T11:34:04Z

IGNITE-8311 IgniteClientRejoinTest.testClientsReconnectDisabled causes 
exchange-worker to terminate via NPE

Signed-off-by: Andrey Gura 

commit bad52d3843925d831e6d357a4382731751ae6bb7
Author: Ilya Lantukh 
Date:   2018-06-04T14:07:52Z

GG-13862 : Disabled fast eviction.

(cherry picked from commit 786633d)

commit 6956097ceedd2e3e9edcb627d97e49afb7f0a26d
Author: Pavel Kovalenko 
Date:   2018-06-06T12:24:39Z

IGNITE-8482 Skip 2-phase partition release wait in case of activation or 
dynamic caches start - Fixes #4078.

Signed-off-by: Alexey Goncharuk 

(cherry picked from commit 7c565d2)

commit d777c76eadd0a2ccc50f1031c42626b135da5906
Author: Dmitriy Govorukhin 
Date:   2018-06-06T14:20:18Z

IGNITE-8685 Fixed switch segment record size - Fixes #4130.

Signed-off-by: Alexey Goncharuk 

(cherry picked from commit 2a048bd)

commit ef4782d8a60eea870b43933480f2c9695c9fc55d
Author: Alexey Goncharuk 
Date:   2018-06-07T11:55:13Z

IGNITE-8706 Fixed testMemoryUsageMultipleNodes

commit 6902383e01ee69d7efff9613a68f3fc419152305
Author: Pavel Kovalenko 
Date:   2018-05-14T10:14:52Z

IGNITE-8422 Tests fix for Zookeeper discovery split brain detection 
shouldn't consider client nodes - Fixes #3975.

Signed-off-by: dpavlov 

(cherry-picked from commit #19cbf8058b48a1f8fec60f7ceac70229e7c5391a)

commit 6eef070f8e0627e2986d870cc09ceb9cb351ee0d
Author: Sergey Chugunov 
Date:   2018-05-14T17:09:33Z

IGNITE-8487 tmpfs is employed by ZooKeeper tests - Fixes #3994.

Signed-off-by: dpavlov 

(cherry-picked from commit #67be050a2c7b9efdef2388c579fc060c68ff8a38)

commit c9b82cc632ad1cac51661f729f8605ab6c97c1dd
Author: Anton Kalashnikov 
Date:   2018-06-08T15:24:09Z

IGNITE-8739 Implemented WA for tcp communication SPI hanging on descriptor 
reservation - Fixes #4148.

Signed-off-by: Alexey Goncharuk 

(cherry picked from commit 7021651)

commit 45953256ef0f09fd5450f6f6c6967a539c5cd395
Author: Pavel Kovalenko 
Date:   2018-05-03T14:01:20Z

IGNITE-8226 Improved logging - Fixes #3796.

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

commit 77d089d857876f1901ade5a017a92c9835e2976a
Author: Sergey Kosarev 
Date:   2018-06-13T14:24:42Z

IGNITE-8736 Add transaction label to CU.txString() method output - Fixes 
#4152.

Signed-off-by: Alexey Goncharuk 

commit c3c80439945134867e28e8d2c6db5ef9295141b6
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

commit d33fe100bc9fdbcb66754d43ec0199e44233190b
Author: Andrey Gura 
Date:   2018-06-13T14:30:18Z

IGNITE-8781 GridNioServer accepter threads should have different names

commit d2c304ca415919f0933461dde92fdf354539529b
Author: Aleksey Plekhanov 
Date:   2018-06-14T17:41:31Z

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

Signed-off-by: Andrey Gura 

commit 2545a4d65ae9c0289c9f6faf9d2ee498375aa3c7
Author: Sergey Chugunov 
Date:   2018-06-15T08:31:33Z

IGNITE-8657 Simultaneous start of multiple clients may lead to client start 
hang when exchange history size is too short - Fixes #4102.

Signed-off-by: Alexey Goncharuk 

(cherry-picked from commit #2b928c702b2d6a7c1de8d1b3b0a1e0e65e653f21)

commit f4511d921c34fc1fc048afaf3ec10307b0f3bea2
Author: Pavel Kovalenko 
Date:   2018-06-15T09:48:24Z

IGNITE-8610 Fixed checkpoint record search for WAL delta rebalancing - 
Fixes #4090.

Signed-off-by: Alexey Goncharuk 

(cherry picked from commit 10aa02a)

commit 1a8e9fcafa3a6d53ab01901be798cc8957252fe6
Author: EdShangGG 
Date:   2018-06-15T16:35:00Z

IGNITE-8610 Fix compilation

(cherry picked from commit 55af7d1)

commit 298ca37aea710e098d033fcc5750e408b4a07c24
Author: Ilya Lantukh 
Date:   2018-05-23T15:02:23Z

IGNITE-7809 fixed stable failures of IgniteWalFlushDefaultSelfTest in 
Ignite PDS 2 & PDS 2 Direct IO, new tests were added. - Fixes #3569.

Signed-off-by: dpavlov 

(cherry picked from commit fed2c02)

commit 3a1645135cf474f5760319a3c2dd7712041cc6f4
Author: dpa

[jira] [Created] (IGNITE-9881) Management events for webconsole and visor

[Andrey Aleksandrov (JIRA)]

Andrey Aleksandrov created IGNITE-9881:
--

 Summary: Management events for webconsole and visor
 Key: IGNITE-9881
 URL: https://issues.apache.org/jira/browse/IGNITE-9881
 Project: Ignite
  Issue Type: New Feature
Affects Versions: 2.6
Reporter: Andrey Aleksandrov
Assignee: Andrey Aleksandrov
 Fix For: 2.8


New events for the handling of the tasks that were started on web console or 
visor could be helpful for tracking the user activities.

At the moment all events will be handled as data node events. So it could be 
difficult to understand why they were fired in case if it was done on web 
console or visor.



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

Re: Apache Ignite 2.7. Last Mile

[Vladimir Ozerov]

Nikolay,

AI 2.7 will include Python thin client. TC suite is crucial part of this
feature, so we should keep the ticket in AI 2.7 scope.

On Mon, Oct 15, 2018 at 10:57 AM Nikolay Izhikov 
wrote:

> Hello, Igniters.
>
> There is no progress till Friday.
> We have 14 tickets mapped to 2.7.
>
> В Пт, 12/10/2018 в 08:29 +0300, Nikolay Izhikov пишет:
> > Hello, Igniters.
> >
> > We made some progress yesterday.
> >
> > Please, note, we have 1 new ticket mapped to 2.7 "IGNITE-9852: Create
> TeamCity suite for Python thin client"
> >
> > This ticket doesn't sound like a blocker to me. Let's exclude it from
> release scope.
> > Thoughts?
> >
> > Here is the list of remaining tickets(14) mapped to 2.7.
> >
> > Peter Ivanov - IGNITE-9852, IGNITE-9685,
> > Alexey Goncharuk   - IGNITE-9784
> > Andrey Kuznetsov   - IGNITE-9737, IGNITE-9710
> > Igor Seliverstov   - IGNITE-9749, IGNITE-9292
> > Dmitry Melnichuk   - IGNITE-7782
> > Ivan Pavlukhin - IGNITE-5935
> > Yury Babak - IGNITE-8670
> > Roman Kondakov - IGNITE-7953
> > Igor Sapego  - IGNITE-9620
> > Alexey Stelmak - IGNITE-9776
> >
> > Unassigned:
> >
> > IGNITE-9663 - MVCC: Data node failure can cause TX hanging.
> >
> >
> > В Чт, 11/10/2018 в 13:50 +0300, Nikolay Izhikov пишет:
> > > Alexey, we all agreed to merge in 2.7 blockers only.
> > >
> > > Is this a blocker?
> > >
> > > Anyway, you are more experienced Igniter that I am.
> > > If you think we should include this ticket to 2.7 - please, do it.
> > >
> > > В Чт, 11/10/2018 в 13:08 +0300, Alexey Goncharuk пишет:
> > > > Nikolay,
> > > >
> > > > I am waiting for final benchmark results for 9784, after that I will
> merge
> > > > the change.
> > > >
> > > > On the subject of Ignite 2.7 scope, our fellow Igniter Alexey
> Platonov have
> > > > found another case when a failure handler is incorrectly called on
> node
> > > > stop: https://issues.apache.org/jira/browse/IGNITE-9834. The case
> is rare,
> > > > but it is quite an unpleasant UX. Should we include it to 2.7 as
> well?
> > > >
> > > > чт, 11 окт. 2018 г. в 11:22, Nikolay Izhikov :
> > > >
> > > > > Hello, Igniters.
> > > > >
> > > > > We made a good progress yesterday.
> > > > >
> > > > > Here is the list of remaining tickets(17) mapped to 2.7:
> > > > >
> > > > > Alexey Goncharuk   - IGNITE-9784
> > > > > Taras Ledkov   - IGNITE-9171
> > > > > Andrey Kuznetsov   - IGNITE-9737, IGNITE-9710
> > > > > Peter Ivanov   - IGNITE-9583, IGNITE-9823, IGNITE-9685
> > > > > Igor Seliverstov   - IGNITE-9749, IGNITE-9292
> > > > > Dmitry Melnichuk   - IGNITE-7782
> > > > > Ivan Pavlukhin - IGNITE-5935
> > > > > Yury Babak - IGNITE-8670
> > > > > Roman Kondakov - IGNITE-7953, IGNITE-9446
> > > > > Alexey Stelmak - IGNITE-9776
> > > > >
> > > > > Unassigned:
> > > > >
> > > > > IGNITE-9620 - MVCC: select throwing `Transaction is already
> completed`> >
> > > > > > exception after mvcc missmatch
> > > > >
> > > > > IGNITE-9663 - MVCC: Data node failure can cause TX hanging.
> > > > >
> > > > >
> > > > > В Чт, 11/10/2018 в 10:40 +0300, Vladimir Ozerov пишет:
> > > > > > What kind of help is needed?
> > > > > >
> > > > > > On Wed, Oct 10, 2018 at 11:51 PM Dmitriy Setrakyan <
> > > > >
> > > > > dsetrak...@apache.org>
> > > > > > wrote:
> > > > > >
> > > > > > > Vladimir Ozerov,
> > > > > > >
> > > > > > > Can you help with the unassigned MVCC tickets?
> > > > > > >
> > > > > > > D.
> > > > > > >
> > > > > > > On Wed, Oct 10, 2018 at 3:32 AM Nikolay Izhikov <
> nizhi...@apache.org>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Hello, Igniters.
> > > > > > > >
> > > > > > > > I list all contributors that assigned to the 2.7 tickets.
> > > > > > > > If you can help them to finish that tickets - please, do.
> > > > > > > > Assigners, if you need any help - please, respond to this
> thread.
> > > > > > > >
> > > > > > > > NOTE: We have 6 Unassigned tickets for 2.7. Let's start work
> on it!
> > > > > > > >
> > > > > > > > Peter Ivanov   - IGNITE-9559, IGNITE-9583, IGNITE-9685,
> > > > >
> > > > > IGNITE-9823
> > > > > > > > Andrey Kuznetsov   - IGNITE-9737, IGNITE-9710
> > > > > > > > Taras Ledkov   - IGNITE-9171
> > > > > > > > Alexey Goncharuk   - IGNITE-9784
> > > > > > > > Dmitriy Govorukhin - IGNITE-9550
> > > > > > > > Igor Seliverstov   - IGNITE-9749
> > > > > > > > Dmitry Melnichuk   - IGNITE-7782
> > > > > > > > Alexey Platonov- IGNITE-9726
> > > > > > > > Ivan Pavlukhin - IGNITE-5935
> > > > > > > > Yury Babak - IGNITE-8670
> > > > > > > > Roman Kondakov - IGNITE-7953, IGNITE-9446
> > > > > > > > Maxim Pudov- IGNITE-9126
> > > > > > > > Alexey Stelmak - IGNITE-9776
> > > > > > > > Alexey Kuznetsov   - IGNITE-7926
> > > > > > > >
> > > > > > > > Unassigned tickets:
> > > > > > > >
> > > > > > > > IGNITE-9781 - JDK11: SSL handshake is failed
> > > > > > > > IGNITE-9620 - MVCC: select throwing `Transaction is already
> > > > >
> > > > > completed`
> > > > > > > > excep

[GitHub] ignite pull request #4985: IGNITE-9780 SQL system view for cache groups

[alex-plekhanov]

GitHub user alex-plekhanov opened a pull request:

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

IGNITE-9780 SQL system view for cache groups



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

$ git pull https://github.com/alex-plekhanov/ignite ignite-9780

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

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


commit 1999c811eb49a9ab4422f6b5edc3a44e60fe8f4e
Author: Aleksey Plekhanov 
Date:   2018-10-03T13:53:59Z

IGNITE-9780 SQL system view for cache groups

commit b137d5aae744753c106817dd119aa543903c9077
Author: Aleksey Plekhanov 
Date:   2018-10-03T15:21:21Z

IGNITE-9780 Unit test




---

Hadoop Suite constantly failing

[Maxim Muzafarov]

Igniters,

Hadoop Test Suite started to fall [1] constantly from October 12 with `Out
of memory` or `Execution timeouts` or `Assertion errors`. Does anyone
investigate this problem?

Maybe some serious problem is hidden but at least it's a waste of TC agent
resources. It seems to me that there are several problems stratified at
once.

[1]
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Hadoop&page=2&tab=buildTypeHistoryList&branch_IgniteTests24Java8=%3Cdefault%3E
-- 
--
Maxim Muzafarov

Re: Apache Ignite 2.7. Last Mile

[Nikolay Izhikov]

Hello, Igniters.

There is no progress till Friday.
We have 14 tickets mapped to 2.7.

В Пт, 12/10/2018 в 08:29 +0300, Nikolay Izhikov пишет:
> Hello, Igniters.
> 
> We made some progress yesterday.
> 
> Please, note, we have 1 new ticket mapped to 2.7 "IGNITE-9852: Create 
> TeamCity suite for Python thin client"
> 
> This ticket doesn't sound like a blocker to me. Let's exclude it from release 
> scope.
> Thoughts?
> 
> Here is the list of remaining tickets(14) mapped to 2.7.
> 
> Peter Ivanov - IGNITE-9852, IGNITE-9685, 
> Alexey Goncharuk   - IGNITE-9784
> Andrey Kuznetsov   - IGNITE-9737, IGNITE-9710
> Igor Seliverstov   - IGNITE-9749, IGNITE-9292
> Dmitry Melnichuk   - IGNITE-7782
> Ivan Pavlukhin - IGNITE-5935
> Yury Babak - IGNITE-8670
> Roman Kondakov - IGNITE-7953
> Igor Sapego  - IGNITE-9620
> Alexey Stelmak - IGNITE-9776
> 
> Unassigned:
> 
> IGNITE-9663 - MVCC: Data node failure can cause TX hanging.
> 
> 
> В Чт, 11/10/2018 в 13:50 +0300, Nikolay Izhikov пишет:
> > Alexey, we all agreed to merge in 2.7 blockers only.
> > 
> > Is this a blocker?
> > 
> > Anyway, you are more experienced Igniter that I am.
> > If you think we should include this ticket to 2.7 - please, do it.
> > 
> > В Чт, 11/10/2018 в 13:08 +0300, Alexey Goncharuk пишет:
> > > Nikolay,
> > > 
> > > I am waiting for final benchmark results for 9784, after that I will merge
> > > the change.
> > > 
> > > On the subject of Ignite 2.7 scope, our fellow Igniter Alexey Platonov 
> > > have
> > > found another case when a failure handler is incorrectly called on node
> > > stop: https://issues.apache.org/jira/browse/IGNITE-9834. The case is rare,
> > > but it is quite an unpleasant UX. Should we include it to 2.7 as well?
> > > 
> > > чт, 11 окт. 2018 г. в 11:22, Nikolay Izhikov :
> > > 
> > > > Hello, Igniters.
> > > > 
> > > > We made a good progress yesterday.
> > > > 
> > > > Here is the list of remaining tickets(17) mapped to 2.7:
> > > > 
> > > > Alexey Goncharuk   - IGNITE-9784
> > > > Taras Ledkov   - IGNITE-9171
> > > > Andrey Kuznetsov   - IGNITE-9737, IGNITE-9710
> > > > Peter Ivanov   - IGNITE-9583, IGNITE-9823, IGNITE-9685
> > > > Igor Seliverstov   - IGNITE-9749, IGNITE-9292
> > > > Dmitry Melnichuk   - IGNITE-7782
> > > > Ivan Pavlukhin - IGNITE-5935
> > > > Yury Babak - IGNITE-8670
> > > > Roman Kondakov - IGNITE-7953, IGNITE-9446
> > > > Alexey Stelmak - IGNITE-9776
> > > > 
> > > > Unassigned:
> > > > 
> > > > IGNITE-9620 - MVCC: select throwing `Transaction is already completed`> 
> > > > >
> > > > > exception after mvcc missmatch
> > > > 
> > > > IGNITE-9663 - MVCC: Data node failure can cause TX hanging.
> > > > 
> > > > 
> > > > В Чт, 11/10/2018 в 10:40 +0300, Vladimir Ozerov пишет:
> > > > > What kind of help is needed?
> > > > > 
> > > > > On Wed, Oct 10, 2018 at 11:51 PM Dmitriy Setrakyan <
> > > > 
> > > > dsetrak...@apache.org>
> > > > > wrote:
> > > > > 
> > > > > > Vladimir Ozerov,
> > > > > > 
> > > > > > Can you help with the unassigned MVCC tickets?
> > > > > > 
> > > > > > D.
> > > > > > 
> > > > > > On Wed, Oct 10, 2018 at 3:32 AM Nikolay Izhikov 
> > > > > > 
> > > > > > wrote:
> > > > > > 
> > > > > > > Hello, Igniters.
> > > > > > > 
> > > > > > > I list all contributors that assigned to the 2.7 tickets.
> > > > > > > If you can help them to finish that tickets - please, do.
> > > > > > > Assigners, if you need any help - please, respond to this thread.
> > > > > > > 
> > > > > > > NOTE: We have 6 Unassigned tickets for 2.7. Let's start work on 
> > > > > > > it!
> > > > > > > 
> > > > > > > Peter Ivanov   - IGNITE-9559, IGNITE-9583, IGNITE-9685,
> > > > 
> > > > IGNITE-9823
> > > > > > > Andrey Kuznetsov   - IGNITE-9737, IGNITE-9710
> > > > > > > Taras Ledkov   - IGNITE-9171
> > > > > > > Alexey Goncharuk   - IGNITE-9784
> > > > > > > Dmitriy Govorukhin - IGNITE-9550
> > > > > > > Igor Seliverstov   - IGNITE-9749
> > > > > > > Dmitry Melnichuk   - IGNITE-7782
> > > > > > > Alexey Platonov- IGNITE-9726
> > > > > > > Ivan Pavlukhin - IGNITE-5935
> > > > > > > Yury Babak - IGNITE-8670
> > > > > > > Roman Kondakov - IGNITE-7953, IGNITE-9446
> > > > > > > Maxim Pudov- IGNITE-9126
> > > > > > > Alexey Stelmak - IGNITE-9776
> > > > > > > Alexey Kuznetsov   - IGNITE-7926
> > > > > > > 
> > > > > > > Unassigned tickets:
> > > > > > > 
> > > > > > > IGNITE-9781 - JDK11: SSL handshake is failed
> > > > > > > IGNITE-9620 - MVCC: select throwing `Transaction is already
> > > > 
> > > > completed`
> > > > > > > exception after mvcc missmatch
> > > > > > > IGNITE-9292 - MVCC SQL: Unexpected state exception when updating
> > > > 
> > > > backup
> > > > > > > IGNITE-9663 - MVCC: Data node failure can cause TX hanging.
> > > > > > > IGNITE-9724 - MVCC SQL: Test
> > > > > > > 
> > > > 
> > > > CacheMvccSelectForUpdateQueryAbstractTest.testSelectForUpdateDistributed
> > > > > > > hangs sporadically.
> > > > > > > IGNITE-

[jira] [Created] (IGNITE-9880) Document MVCC write conflict exceptions

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-9880:
---

 Summary: Document MVCC write conflict exceptions
 Key: IGNITE-9880
 URL: https://issues.apache.org/jira/browse/IGNITE-9880
 Project: Ignite
  Issue Type: Task
  Components: documentation
Reporter: Vladimir Ozerov
Assignee: Artem Budnikov
 Fix For: 2.7


When an entry is read (1) inside a transaction and then updated (2), there is a 
chance that concurrent transaction will modify that entry in between (1) and 
(2). In this case an error is thrown from the first transaction when action (2) 
is performed and transaction is marked as "rollback only". User need to re-try 
the whole transaction in this case.

When native APi is used, then {{CacheException}} is thrown with special message 
{{Cannot serialize transaction due to write conflict (transaction is marked for 
rollback)}}. This will be changed in future (AI 2.8|) - special exception type 
will be thrown.

When JDBC or ODBC are used, then special SQLSTATE code 40001 (aka 
"Serialization failure") is propagated to user.



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

[GitHub] ignite pull request #4952: IGNITE-9620

[devozerov]

Github user devozerov closed the pull request at:

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


---

[jira] [Created] (IGNITE-9879) Web console: split major features to modules - configuration

[Ilya Borisov (JIRA)]

Ilya Borisov created IGNITE-9879:


 Summary: Web console: split major features to modules - 
configuration
 Key: IGNITE-9879
 URL: https://issues.apache.org/jira/browse/IGNITE-9879
 Project: Ignite
  Issue Type: Improvement
  Components: wizards
Reporter: Ilya Borisov
Assignee: Ilya Borisov


The issue:
 1. _app.js_ is massive, hard to maintain and often a source of various merge 
conflicts.
 2. Even if some code is de facto separated by feature 
(configuration/queries/admin/profile), no agreement was made on how to 
structure directories, which leads to confusion and app.js growth.

I propose to:
 1. Reorganize source code file structure:
{noformat}
frontend
app
configuration
queries
profile
admin
common
{noformat}
2. Slim _app.js_ down to something like this:
{noformat}
import common from './common'
import configuration from './configuration'
import queries from './queries'
import profile from './profile'
import admin from './admin'

export default angular.module('ignite-console', [
common.name,
configuration.name,
queries.name,
profile.name,
admin.name
])
{noformat}
Each directory inside app will follow the same module structure as agreed upon 
before (i.e. components/services/filters, etc).
3. In order to test water, update the configuration module first and if 
everything goes as expect proceed with other modules.

[~kuaw26], [~anovikov] what do you think?



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