[jira] [Created] (IGNITE-13297) The ignite-zookeeper module does not work properly in Hadoop YARN environment.

2020-07-24 Thread YuJue Li (Jira)
YuJue Li created IGNITE-13297:
-

 Summary: The ignite-zookeeper module does not work properly in 
Hadoop YARN environment.
 Key: IGNITE-13297
 URL: https://issues.apache.org/jira/browse/IGNITE-13297
 Project: Ignite
  Issue Type: Bug
  Components: zookeeper
Affects Versions: 2.8.1
Reporter: YuJue Li
 Fix For: 2.10
 Attachments: image-2020-07-25-10-03-54-464.png

The ignite-zookeeper module does not work properly in Hadoop YARN environment, 
the issue should be related to the version conflict of curator, the errors are 
as follows:

!image-2020-07-25-10-03-54-464.png!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (IGNITE-11942) IGFS and Hadoop Accelerator Discontinuation

2020-07-24 Thread Igor Seliverstov (Jira)


[ 
https://issues.apache.org/jira/browse/IGNITE-11942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17164607#comment-17164607
 ] 

Igor Seliverstov commented on IGNITE-11942:
---

[~akalashnikov], Java part looks OK, quickly looked at js part, seems it's OK 
too, if [~kuaw26] and [~vsisko] don't mind, proceed with merging.

> IGFS and Hadoop Accelerator Discontinuation
> ---
>
> Key: IGNITE-11942
> URL: https://issues.apache.org/jira/browse/IGNITE-11942
> Project: Ignite
>  Issue Type: Task
>Reporter: Denis A. Magda
>Assignee: Anton Kalashnikov
>Priority: Blocker
> Fix For: 2.9
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The community has voted for the following decision:
> * IGFS and In-Memory Hadoop Accelerator components are to be discontinued and 
> no longer supported by the community 
> * The existing source code of IGFS and In-Memory Hadoop Accelerator is to be 
> removed from Ignite master. Before that, a special branch like 
> "ignite-igfs-and-hadoop-accelerator" to be forked off the master in order to 
> preserve the sources in Git history for those who might need it. 
> The voting thread:
> http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Complete-Discontinuation-of-IGFS-and-Hadoop-Accelerator-td42405.html
> Once the changes are made for Ignite 2.8, please contact Denis Magda to 
> update a public documentation.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (IGNITE-13291) Remove unnecessary dependency to curator-client from ZookeeperDiscoverySpi

2020-07-24 Thread Ivan Daschinskiy (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-13291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ivan Daschinskiy updated IGNITE-13291:
--
Ignite Flags:   (was: Docs Required,Release Notes Required)

> Remove unnecessary dependency to curator-client from ZookeeperDiscoverySpi
> --
>
> Key: IGNITE-13291
> URL: https://issues.apache.org/jira/browse/IGNITE-13291
> Project: Ignite
>  Issue Type: Improvement
>  Components: zookeeper
>Affects Versions: 2.9
>Reporter: Ivan Daschinskiy
>Assignee: Ivan Daschinskiy
>Priority: Trivial
> Fix For: 2.10
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently, I suppose by mistake, we use 
> {{org.apache.curator.utils.PathUtils#validatePath(java.lang.String)}} from 
> {{curator-client}}
> in {{ZookeeperDiscoverySpi}}. Generally, this discovery implementation 
> doesn't depend on curator framework at all, except some test code. We should 
> remove this dependency and add this utility method to our codebase.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (IGNITE-13291) Remove unnecessary dependency to curator-client from ZookeeperDiscoverySpi

2020-07-24 Thread Ignite TC Bot (Jira)


[ 
https://issues.apache.org/jira/browse/IGNITE-13291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17164494#comment-17164494
 ] 

Ignite TC Bot commented on IGNITE-13291:


{panel:title=Branch: [pull/8080/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8080/head] Base: [master] : New Tests 
(16)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}ZooKeeper (Discovery) 1{color} [[tests 
8|https://ci.ignite.apache.org/viewLog.html?buildId=5488110]]
* {color:#013220}ZookeeperDiscoverySpiTestSuite1: 
ZookeeperValidatePathsTest$ZoookeperCommonValidatePathsTest.testValidatePath[input
 string = /apacheIgnite/./root, expected error = relative paths not allowed 
@14] - PASSED{color}
* {color:#013220}ZookeeperDiscoverySpiTestSuite1: 
ZookeeperValidatePathsTest$ZoookeperCommonValidatePathsTest.testValidatePath[input
 string = /apacheIgnite/../root, expected error = relative paths not allowed 
@15] - PASSED{color}
* {color:#013220}ZookeeperDiscoverySpiTestSuite1: 
ZookeeperValidatePathsTest$ZoookeperCommonValidatePathsTest.testValidatePath[input
 string = , expected error = Path length must be  0] - PASSED{color}
* {color:#013220}ZookeeperDiscoverySpiTestSuite1: 
ZookeeperValidatePathsTest$ZoookeperCommonValidatePathsTest.testValidatePath[input
 string = null, expected error = Path cannot be null] - PASSED{color}
* {color:#013220}ZookeeperDiscoverySpiTestSuite1: 
ZookeeperValidatePathsTest$ZoookeperCommonValidatePathsTest.testValidatePath[input
 string = /apacheIgnite, expected error = null] - PASSED{color}
* {color:#013220}ZookeeperDiscoverySpiTestSuite1: 
ZookeeperValidatePathsTest$ZookeeperUnprintableCharactersValidatePathTest.testValidatePathWithUnprintableCharacters
 - PASSED{color}
* {color:#013220}ZookeeperDiscoverySpiTestSuite1: 
ZookeeperValidatePathsTest$ZoookeperCommonValidatePathsTest.testValidatePath[input
 string = /apacheIgnite/, expected error = Path must not end with / character] 
- PASSED{color}
* {color:#013220}ZookeeperDiscoverySpiTestSuite1: 
ZookeeperValidatePathsTest$ZoookeperCommonValidatePathsTest.testValidatePath[input
 string = /apacheIgnite//root, expected error = empty node name specified @14] 
- PASSED{color}

{color:#8b}Service Grid{color} [[tests 
4|https://ci.ignite.apache.org/viewLog.html?buildId=5487964]]
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple 
[val1=DiscoveryEvent [evtNode=d7d462f4-63bc-48a1-bd69-f5599238f3c6, topVer=0, 
msgTemplate=null, span=null, nodeId8=1c82fb8a, msg=, type=NODE_JOINED, 
tstamp=1595590130398], val2=AffinityTopologyVersion 
[topVer=-8269426557086687585, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple 
[val1=DiscoveryEvent [evtNode=d7d462f4-63bc-48a1-bd69-f5599238f3c6, topVer=0, 
msgTemplate=null, span=null, nodeId8=1c82fb8a, msg=, type=NODE_JOINED, 
tstamp=1595590130398], val2=AffinityTopologyVersion 
[topVer=-8269426557086687585, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple 
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest 
[id=f972f908371-d920e840-65d0-4173-9357-5b636c63ddf5, reqs=SingletonList 
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent 
[evtNode=c2be829a-4238-49ee-99ec-367ba4d3e9ad, topVer=0, msgTemplate=null, 
span=null, nodeId8=c2be829a, msg=null, type=DISCOVERY_CUSTOM_EVT, 
tstamp=1595590130398]], val2=AffinityTopologyVersion 
[topVer=-1159666316104886390, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple 
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest 
[id=f972f908371-d920e840-65d0-4173-9357-5b636c63ddf5, reqs=SingletonList 
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent 
[evtNode=c2be829a-4238-49ee-99ec-367ba4d3e9ad, topVer=0, msgTemplate=null, 
span=null, nodeId8=c2be829a, msg=null, type=DISCOVERY_CUSTOM_EVT, 
tstamp=1595590130398]], val2=AffinityTopologyVersion 
[topVer=-1159666316104886390, minorTopVer=0]]] - PASSED{color}

{color:#8b}Service Grid (legacy mode){color} [[tests 
4|https://ci.ignite.apache.org/viewLog.html?buildId=5487965]]
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple 
[val1=DiscoveryEvent [evtNode=7276804f-39be-4a6e-8b48-7bf276229151, topVer=0, 
msgTemplate=null, span=null, nodeId8=fec4c1da, msg=, type=NODE_JOINED, 
tstamp=1595589896490], val2=AffinityTopologyVersion 
[topVer=5196619265185798363, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 

[jira] [Updated] (IGNITE-13263) PDS 4 suite timeout and stabilization

2020-07-24 Thread Sergey Chugunov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-13263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Chugunov updated IGNITE-13263:
-
Ignite Flags:   (was: Docs Required,Release Notes Required)

> PDS 4 suite timeout and stabilization
> -
>
> Key: IGNITE-13263
> URL: https://issues.apache.org/jira/browse/IGNITE-13263
> Project: Ignite
>  Issue Type: Bug
>Reporter: Nikita Tolstunov
>Assignee: Nikita Tolstunov
>Priority: Major
> Fix For: 2.10
>
> Attachments: Ignite_Tests_2.4_Java_8_9_10_11_PDS_4_18257.log.zip
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Build fails sometimes with timeout or 137 codes
> https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_Pds4?branch==overview=builds
> log in attach
> Detailed issues:
> # possible OOM when DataRegionConfiguration isn't set in test(by default 20%, 
> which may be calculated incorrectly in docker containers) 
> # some tests doesn't use base test and doesn't have any timeout
> # 137 code may be caused by the same reason, as in IGNITE-13266



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Assigned] (IGNITE-13102) IgniteCache#isClosed() returns false on server node even if the cache had been closed before.

2020-07-24 Thread Konstantin Sirotkin (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-13102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Konstantin Sirotkin reassigned IGNITE-13102:


Assignee: Konstantin Sirotkin

> IgniteCache#isClosed() returns false on server node even if the cache had 
> been closed before.
> -
>
> Key: IGNITE-13102
> URL: https://issues.apache.org/jira/browse/IGNITE-13102
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.8, 2.8.1
>Reporter: Sergey Antonov
>Assignee: Konstantin Sirotkin
>Priority: Major
> Fix For: 2.10
>
>
> IgniteCache#isClosed() still returns {{false}} even after 
> {{IgniteCache#close()}}. Only server nodes affect by this problem. 
> Simple reproducer:
> {code:java}
> @Test
> public void test() throws Exception {
> IgniteEx node = startGrid(0);
> IgniteCache cache = 
> node.getOrCreateCache(DEFAULT_CACHE_NAME);
> assertFalse(cache.isClosed());
> cache.close();
> // java.lang.AssertionError
> assertTrue(cache.isClosed());
> }
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (IGNITE-13263) PDS 4 suite timeout and stabilization

2020-07-24 Thread Nikita Tolstunov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-13263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nikita Tolstunov updated IGNITE-13263:
--
Fix Version/s: 2.10

> PDS 4 suite timeout and stabilization
> -
>
> Key: IGNITE-13263
> URL: https://issues.apache.org/jira/browse/IGNITE-13263
> Project: Ignite
>  Issue Type: Bug
>Reporter: Nikita Tolstunov
>Assignee: Nikita Tolstunov
>Priority: Major
> Fix For: 2.10
>
> Attachments: Ignite_Tests_2.4_Java_8_9_10_11_PDS_4_18257.log.zip
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Build fails sometimes with timeout or 137 codes
> https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_Pds4?branch==overview=builds
> log in attach
> Detailed issues:
> # possible OOM when DataRegionConfiguration isn't set in test(by default 20%, 
> which may be calculated incorrectly in docker containers) 
> # some tests doesn't use base test and doesn't have any timeout
> # 137 code may be caused by the same reason, as in IGNITE-13266



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (IGNITE-13013) Thick client must not open server sockets when used by serverless functions

2020-07-24 Thread Ignite TC Bot (Jira)


[ 
https://issues.apache.org/jira/browse/IGNITE-13013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17164399#comment-17164399
 ] 

Ignite TC Bot commented on IGNITE-13013:


{panel:title=Branch: [pull/8074/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8074/head] Base: [master] : New Tests 
(9)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}SPI{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=5485623]]
* {color:#013220}IgniteSpiTestSuite: 
GridTotallyUnreachableClientTest.testTotallyUnreachableClient - PASSED{color}

{color:#8b}Service Grid{color} [[tests 
4|https://ci.ignite.apache.org/viewLog.html?buildId=5485687]]
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple 
[val1=DiscoveryEvent [evtNode=4974d836-2569-46ed-91dc-6786e3379bf0, topVer=0, 
msgTemplate=null, span=null, nodeId8=44d830af, msg=, type=NODE_JOINED, 
tstamp=1595491594440], val2=AffinityTopologyVersion 
[topVer=2446643712338799655, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple 
[val1=DiscoveryEvent [evtNode=4974d836-2569-46ed-91dc-6786e3379bf0, topVer=0, 
msgTemplate=null, span=null, nodeId8=44d830af, msg=, type=NODE_JOINED, 
tstamp=1595491594440], val2=AffinityTopologyVersion 
[topVer=2446643712338799655, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple 
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest 
[id=cc0b5ba7371-8e41e22c-a539-4518-bcd1-a96657eb2503, reqs=SingletonList 
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent 
[evtNode=56ddeff7-de5a-443e-9397-d7470d270de1, topVer=0, msgTemplate=null, 
span=null, nodeId8=56ddeff7, msg=null, type=DISCOVERY_CUSTOM_EVT, 
tstamp=1595491594440]], val2=AffinityTopologyVersion 
[topVer=5569973235457393409, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple 
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest 
[id=cc0b5ba7371-8e41e22c-a539-4518-bcd1-a96657eb2503, reqs=SingletonList 
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent 
[evtNode=56ddeff7-de5a-443e-9397-d7470d270de1, topVer=0, msgTemplate=null, 
span=null, nodeId8=56ddeff7, msg=null, type=DISCOVERY_CUSTOM_EVT, 
tstamp=1595491594440]], val2=AffinityTopologyVersion 
[topVer=5569973235457393409, minorTopVer=0]]] - PASSED{color}

{color:#8b}Service Grid (legacy mode){color} [[tests 
4|https://ci.ignite.apache.org/viewLog.html?buildId=5485688]]
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple 
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest 
[id=24302ca7371-f88d7ce1-c209-4e51-957b-74efa283b3f8, reqs=SingletonList 
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent 
[evtNode=8b19b365-cb41-46ca-a327-c6da287bf94e, topVer=0, msgTemplate=null, 
span=null, nodeId8=8b19b365, msg=null, type=DISCOVERY_CUSTOM_EVT, 
tstamp=1595491730222]], val2=AffinityTopologyVersion 
[topVer=2283060003126171735, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple 
[val1=DiscoveryEvent [evtNode=dc4a9197-a793-4a64-b445-d55e4ed6b004, topVer=0, 
msgTemplate=null, span=null, nodeId8=9cf55548, msg=, type=NODE_JOINED, 
tstamp=1595491730222], val2=AffinityTopologyVersion 
[topVer=-7994999231815152273, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple 
[val1=DiscoveryEvent [evtNode=dc4a9197-a793-4a64-b445-d55e4ed6b004, topVer=0, 
msgTemplate=null, span=null, nodeId8=9cf55548, msg=, type=NODE_JOINED, 
tstamp=1595491730222], val2=AffinityTopologyVersion 
[topVer=-7994999231815152273, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple 
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest 
[id=24302ca7371-f88d7ce1-c209-4e51-957b-74efa283b3f8, reqs=SingletonList 
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent 
[evtNode=8b19b365-cb41-46ca-a327-c6da287bf94e, topVer=0, msgTemplate=null, 
span=null, nodeId8=8b19b365, msg=null, type=DISCOVERY_CUSTOM_EVT, 
tstamp=1595491730222]], val2=AffinityTopologyVersion 
[topVer=2283060003126171735, minorTopVer=0]]] - PASSED{color}

{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5485710buildTypeId=IgniteTests24Java8_RunAll]

[jira] [Updated] (IGNITE-13266) PDS (Indexing) fails with 'Exit code 137'

2020-07-24 Thread Ivan Bessonov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-13266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ivan Bessonov updated IGNITE-13266:
---
Summary: PDS (Indexing) fails with 'Exit code 137'  (was: PDS (Indexing) 
fails with 'Exit code 137)

> PDS (Indexing) fails with 'Exit code 137'
> -
>
> Key: IGNITE-13266
> URL: https://issues.apache.org/jira/browse/IGNITE-13266
> Project: Ignite
>  Issue Type: Test
>Reporter: Ivan Bessonov
>Assignee: Ivan Bessonov
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> [https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_PdsIndexing_IgniteTests24Java8=%3Cdefault%3E=buildTypeHistoryList]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (IGNITE-13266) PDS (Indexing) fails with 'Exit code 137

2020-07-24 Thread Ivan Bessonov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-13266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ivan Bessonov updated IGNITE-13266:
---
Summary: PDS (Indexing) fails with 'Exit code 137  (was: PDS (Indexing) 
fails with 'Exit code 137")

> PDS (Indexing) fails with 'Exit code 137
> 
>
> Key: IGNITE-13266
> URL: https://issues.apache.org/jira/browse/IGNITE-13266
> Project: Ignite
>  Issue Type: Test
>Reporter: Ivan Bessonov
>Assignee: Ivan Bessonov
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> [https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_PdsIndexing_IgniteTests24Java8=%3Cdefault%3E=buildTypeHistoryList]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Assigned] (IGNITE-13296) .NET: TransactionImpl finalizer can crash the process

2020-07-24 Thread Sergey Stronchinskiy (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-13296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Stronchinskiy reassigned IGNITE-13296:
-

Assignee: Sergey Stronchinskiy  (was: Pavel Tupitsyn)

> .NET: TransactionImpl finalizer can crash the process
> -
>
> Key: IGNITE-13296
> URL: https://issues.apache.org/jira/browse/IGNITE-13296
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Sergey Stronchinskiy
>Priority: Major
>  Labels: .NET
> Fix For: 2.10
>
>
> ~TransactionImpl potentially throws an exception (e.g. when grid is stopped), 
> causing the entire process to abort.
> GetLocalActiveTransactions is especially problematic - the method is 
> informational, yet will result in all the returned transactions to be 
> finalized later.
> * Finalizers should not throw exceptions
> * Stopped grid is a valid use case
> * GetLocalActiveTransactions should be fixed to return "read-only" 
> transactions that won't be finalized
> Review all filalizers and make sure they are safe.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (IGNITE-13069) Rewrite creation of IgniteInClosure and IgniteOutClosure as lambda expression

2020-07-24 Thread Ignite TC Bot (Jira)


[ 
https://issues.apache.org/jira/browse/IGNITE-13069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17164362#comment-17164362
 ] 

Ignite TC Bot commented on IGNITE-13069:


{panel:title=Branch: [pull/8063/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8063/head] Base: [master] : No new tests 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *-- Run :: Basic Tests* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5487741buildTypeId=IgniteTests24Java8_RunBasicTests]

> Rewrite creation of IgniteInClosure and IgniteOutClosure as lambda expression
> -
>
> Key: IGNITE-13069
> URL: https://issues.apache.org/jira/browse/IGNITE-13069
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Affects Versions: 2.8.1
>Reporter: Nikolay Izhikov
>Assignee: Konstantin Sirotkin
>Priority: Trivial
>  Labels: newbie
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> We can use lambda expression instead of direct instantiation of 
> IgniteInClosure, IgniteOutClosure.
> This:
> {code:java}
> state = new DirectMessageState<>(StateItem.class, new 
> IgniteOutClosure() {
> @Override public StateItem apply() {
> return new StateItem(msgFactory, protoVer);
> }
> });
> {code}
> Can be replaced with:
> {code:java}
> state = new DirectMessageState<>(StateItem.class, () -> new 
> StateItem(msgFactory, protoVer));
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (IGNITE-13069) Rewrite creation of IgniteInClosure and IgniteOutClosure as lambda expression

2020-07-24 Thread Konstantin Sirotkin (Jira)


[ 
https://issues.apache.org/jira/browse/IGNITE-13069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17164364#comment-17164364
 ] 

Konstantin Sirotkin commented on IGNITE-13069:
--

[~agoncharuk], can you review?

> Rewrite creation of IgniteInClosure and IgniteOutClosure as lambda expression
> -
>
> Key: IGNITE-13069
> URL: https://issues.apache.org/jira/browse/IGNITE-13069
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Affects Versions: 2.8.1
>Reporter: Nikolay Izhikov
>Assignee: Konstantin Sirotkin
>Priority: Trivial
>  Labels: newbie
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> We can use lambda expression instead of direct instantiation of 
> IgniteInClosure, IgniteOutClosure.
> This:
> {code:java}
> state = new DirectMessageState<>(StateItem.class, new 
> IgniteOutClosure() {
> @Override public StateItem apply() {
> return new StateItem(msgFactory, protoVer);
> }
> });
> {code}
> Can be replaced with:
> {code:java}
> state = new DirectMessageState<>(StateItem.class, () -> new 
> StateItem(msgFactory, protoVer));
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (IGNITE-12744) Add user attributes to GridRestRequest creation routine

2020-07-24 Thread Ignite TC Bot (Jira)


[ 
https://issues.apache.org/jira/browse/IGNITE-12744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17164284#comment-17164284
 ] 

Ignite TC Bot commented on IGNITE-12744:


{panel:title=Branch: [pull/8069/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8069/head] Base: [master] : New Tests 
(8)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Service Grid{color} [[tests 
4|https://ci.ignite.apache.org/viewLog.html?buildId=5485520]]
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple 
[val1=DiscoveryEvent [evtNode=7371817b-4cd5-4a4b-9929-468aba2b329a, topVer=0, 
msgTemplate=null, span=null, nodeId8=fcec0d30, msg=, type=NODE_JOINED, 
tstamp=1595485847276], val2=AffinityTopologyVersion 
[topVer=-7704618605425072970, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple 
[val1=DiscoveryEvent [evtNode=7371817b-4cd5-4a4b-9929-468aba2b329a, topVer=0, 
msgTemplate=null, span=null, nodeId8=fcec0d30, msg=, type=NODE_JOINED, 
tstamp=1595485847276], val2=AffinityTopologyVersion 
[topVer=-7704618605425072970, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple 
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest 
[id=223d76a7371-641a3df2-6401-4252-bce0-7bfa24ec0562, reqs=SingletonList 
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent 
[evtNode=2671abfe-d767-40fc-8529-1f021ceee62c, topVer=0, msgTemplate=null, 
span=null, nodeId8=2671abfe, msg=null, type=DISCOVERY_CUSTOM_EVT, 
tstamp=1595485847276]], val2=AffinityTopologyVersion 
[topVer=3628703394509619604, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple 
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest 
[id=223d76a7371-641a3df2-6401-4252-bce0-7bfa24ec0562, reqs=SingletonList 
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent 
[evtNode=2671abfe-d767-40fc-8529-1f021ceee62c, topVer=0, msgTemplate=null, 
span=null, nodeId8=2671abfe, msg=null, type=DISCOVERY_CUSTOM_EVT, 
tstamp=1595485847276]], val2=AffinityTopologyVersion 
[topVer=3628703394509619604, minorTopVer=0]]] - PASSED{color}

{color:#8b}Service Grid (legacy mode){color} [[tests 
4|https://ci.ignite.apache.org/viewLog.html?buildId=5485521]]
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple 
[val1=DiscoveryEvent [evtNode=53411e25-bf0f-4509-87eb-6fc9aa929560, topVer=0, 
msgTemplate=null, span=null, nodeId8=c5cbda87, msg=, type=NODE_JOINED, 
tstamp=1595485481690], val2=AffinityTopologyVersion 
[topVer=4395901037028225243, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple 
[val1=DiscoveryEvent [evtNode=53411e25-bf0f-4509-87eb-6fc9aa929560, topVer=0, 
msgTemplate=null, span=null, nodeId8=c5cbda87, msg=, type=NODE_JOINED, 
tstamp=1595485481690], val2=AffinityTopologyVersion 
[topVer=4395901037028225243, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple 
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest 
[id=eda685a7371-c3a58a96-83e6-481f-8c3f-e8673a642595, reqs=SingletonList 
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent 
[evtNode=3c12ef57-8ccf-4ad2-b9b8-072c2e275a9f, topVer=0, msgTemplate=null, 
span=null, nodeId8=3c12ef57, msg=null, type=DISCOVERY_CUSTOM_EVT, 
tstamp=1595485481690]], val2=AffinityTopologyVersion 
[topVer=5395345419712661732, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple 
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest 
[id=eda685a7371-c3a58a96-83e6-481f-8c3f-e8673a642595, reqs=SingletonList 
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent 
[evtNode=3c12ef57-8ccf-4ad2-b9b8-072c2e275a9f, topVer=0, msgTemplate=null, 
span=null, nodeId8=3c12ef57, msg=null, type=DISCOVERY_CUSTOM_EVT, 
tstamp=1595485481690]], val2=AffinityTopologyVersion 
[topVer=5395345419712661732, minorTopVer=0]]] - PASSED{color}

{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5485543buildTypeId=IgniteTests24Java8_RunAll]

> Add user attributes to GridRestRequest creation routine
> ---
>
> Key: IGNITE-12744
> URL: 

[jira] [Commented] (IGNITE-13295) Expiration of cache entries, which relate to a non-persistent data region in the persistent cluster, results in AssertionError

2020-07-24 Thread Vyacheslav Koptilin (Jira)


[ 
https://issues.apache.org/jira/browse/IGNITE-13295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17164283#comment-17164283
 ] 

Vyacheslav Koptilin commented on IGNITE-13295:
--

Hello [~alex_pl],

Could you please take a look at PR?

Thanks,
S.

> Expiration of cache entries, which relate to a non-persistent data region in 
> the persistent cluster, results in AssertionError
> --
>
> Key: IGNITE-13295
> URL: https://issues.apache.org/jira/browse/IGNITE-13295
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.8.1
>Reporter: Vyacheslav Koptilin
>Assignee: Vyacheslav Koptilin
>Priority: Major
> Fix For: 2.10
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> In the case of the cluster uses AI native persistent and, at the same time, 
> it has a non-persistent data region and cache related to that non-persistent 
> region with expiry policy specified, the following Exception is thrown:
> {noformat}
> java.lang.AssertionError
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.remove(IgniteCacheOffheapManagerImpl.java:2678)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.remove(IgniteCacheOffheapManagerImpl.java:619)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.removeValue(GridCacheMapEntry.java:4411)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.onExpired(GridCacheMapEntry.java:4103)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.onTtlExpired(GridCacheMapEntry.java:4028)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheTtlManager$1.applyx(GridCacheTtlManager.java:76)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheTtlManager$1.applyx(GridCacheTtlManager.java:67)
>   at 
> org.apache.ignite.internal.util.lang.IgniteInClosure2X.apply(IgniteInClosure2X.java:38)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.expireInternal(IgniteCacheOffheapManagerImpl.java:1422)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.expire(IgniteCacheOffheapManagerImpl.java:1367)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheTtlManager.expire(GridCacheTtlManager.java:243)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheSharedTtlCleanupManager$CleanupWorker.lambda$body$0(GridCacheSharedTtlCleanupManager.java:179)
>   at 
> java.util.concurrent.ConcurrentHashMap.computeIfPresent(ConcurrentHashMap.java:1769)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheSharedTtlCleanupManager$CleanupWorker.body(GridCacheSharedTtlCleanupManager.java:178)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
>   at java.lang.Thread.run(Thread.java:748)
> {noformat}
> The root cause of the issue is the fact that 
> {{IgniteCacheOffheapManagerImpl#expireInternal}} does not try to acquire a 
> checkpoint read lock at all.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (IGNITE-13295) Expiration of cache entries, which relate to a non-persistent data region in the persistent cluster, results in AssertionError

2020-07-24 Thread Ignite TC Bot (Jira)


[ 
https://issues.apache.org/jira/browse/IGNITE-13295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17164270#comment-17164270
 ] 

Ignite TC Bot commented on IGNITE-13295:


{panel:title=Branch: [pull/8079/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8079/head] Base: [master] : New Tests 
(11)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}PDS 1{color} [[tests 
3|https://ci.ignite.apache.org/viewLog.html?buildId=5487292]]
* {color:#013220}IgnitePdsTestSuite: 
IgnitePdsWithTtlTest.testExpirationNonPersistentRegion - PASSED{color}
* {color:#013220}IgnitePdsTestSuite: 
IgnitePdsWithTtlTest.testConcurrentPutOpsToCacheWithExpirationCompleteSuccesfully
 - PASSED{color}
* {color:#013220}IgnitePdsTestSuite: 
IgnitePdsWithTtlTest.testPutOpsIntoCacheWithExpirationConcurrentlyWithCheckpointCompleteSuccessfully
 - PASSED{color}

{color:#8b}Service Grid{color} [[tests 
4|https://ci.ignite.apache.org/viewLog.html?buildId=5487308]]
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple 
[val1=DiscoveryEvent [evtNode=ba79a999-155b-4c6e-b14c-0f8c7d5738d9, topVer=0, 
msgTemplate=null, span=null, nodeId8=d345d9a2, msg=, type=NODE_JOINED, 
tstamp=1595551682139], val2=AffinityTopologyVersion 
[topVer=-4727994427501359550, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple 
[val1=DiscoveryEvent [evtNode=ba79a999-155b-4c6e-b14c-0f8c7d5738d9, topVer=0, 
msgTemplate=null, span=null, nodeId8=d345d9a2, msg=, type=NODE_JOINED, 
tstamp=1595551682139], val2=AffinityTopologyVersion 
[topVer=-4727994427501359550, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple 
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest 
[id=67df35e7371-241216b5-04c7-4aec-be3c-b7d2d3e5d17a, reqs=SingletonList 
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent 
[evtNode=cc715108-c28b-48e3-bb1b-7697ce72b94d, topVer=0, msgTemplate=null, 
span=null, nodeId8=cc715108, msg=null, type=DISCOVERY_CUSTOM_EVT, 
tstamp=1595551682139]], val2=AffinityTopologyVersion 
[topVer=-186258574758623406, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple 
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest 
[id=67df35e7371-241216b5-04c7-4aec-be3c-b7d2d3e5d17a, reqs=SingletonList 
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent 
[evtNode=cc715108-c28b-48e3-bb1b-7697ce72b94d, topVer=0, msgTemplate=null, 
span=null, nodeId8=cc715108, msg=null, type=DISCOVERY_CUSTOM_EVT, 
tstamp=1595551682139]], val2=AffinityTopologyVersion 
[topVer=-186258574758623406, minorTopVer=0]]] - PASSED{color}

{color:#8b}Service Grid (legacy mode){color} [[tests 
4|https://ci.ignite.apache.org/viewLog.html?buildId=5487309]]
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple 
[val1=DiscoveryEvent [evtNode=bbd06e2c-838a-43e2-b4b9-0b47b10f82d2, topVer=0, 
msgTemplate=null, span=null, nodeId8=4514dd59, msg=, type=NODE_JOINED, 
tstamp=1595551700472], val2=AffinityTopologyVersion 
[topVer=1595447559602639000, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple 
[val1=DiscoveryEvent [evtNode=bbd06e2c-838a-43e2-b4b9-0b47b10f82d2, topVer=0, 
msgTemplate=null, span=null, nodeId8=4514dd59, msg=, type=NODE_JOINED, 
tstamp=1595551700472], val2=AffinityTopologyVersion 
[topVer=1595447559602639000, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple 
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest 
[id=cf5da4e7371-7a3c0727-2313-4f2d-811e-36d38688a0fc, reqs=SingletonList 
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent 
[evtNode=0fa26950-d0c1-425c-b898-162b3157d587, topVer=0, msgTemplate=null, 
span=null, nodeId8=0fa26950, msg=null, type=DISCOVERY_CUSTOM_EVT, 
tstamp=1595551700472]], val2=AffinityTopologyVersion 
[topVer=7597681489777051144, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple 
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest 
[id=cf5da4e7371-7a3c0727-2313-4f2d-811e-36d38688a0fc, reqs=SingletonList 
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent 
[evtNode=0fa26950-d0c1-425c-b898-162b3157d587, topVer=0, msgTemplate=null, 
span=null, nodeId8=0fa26950, 

[jira] [Updated] (IGNITE-13290) SpringTransactionManager adds support for REQUIRES_NEW transaction propagation

2020-07-24 Thread Ivan Pavlukhin (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-13290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ivan Pavlukhin updated IGNITE-13290:

Summary: SpringTransactionManager adds support for REQUIRES_NEW transaction 
propagation  (was: SpringTransactionManager adds support for nested 
transactions)

> SpringTransactionManager adds support for REQUIRES_NEW transaction propagation
> --
>
> Key: IGNITE-13290
> URL: https://issues.apache.org/jira/browse/IGNITE-13290
> Project: Ignite
>  Issue Type: Bug
>  Components: spring
>Affects Versions: 2.8.1
>Reporter: YuJue Li
>Priority: Minor
> Fix For: 2.10
>
>
> If the transaction propagation of the outer method is REQUIRED, the 
> transaction propagation of the inner method is REQUIRES_NEW, the following 
> error will be prompted:
> org.springframework.transaction.TransactionSuspensionNotSupportedException: 
> Transaction manager 
> [org.apache.ignite.transactions.spring.SpringTransactionManager] does not 
> support transaction suspension
> But we see, Ignite's org.apache.ignite.transactions.Transaction, there are 
> suspend() and resume() methods, and the function is normal, so 
> SpringTransactionManager should support similar functions.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (IGNITE-13289) PagesWriteThrottleSmokeTest.testThrottle start to fail on TC.

2020-07-24 Thread Aleksey Plekhanov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-13289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksey Plekhanov updated IGNITE-13289:
---
Fix Version/s: (was: 2.10)
   2.9

> PagesWriteThrottleSmokeTest.testThrottle start to fail on TC.
> -
>
> Key: IGNITE-13289
> URL: https://issues.apache.org/jira/browse/IGNITE-13289
> Project: Ignite
>  Issue Type: Bug
>  Components: persistence
>Affects Versions: 2.9
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
> Fix For: 2.9
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> PagesWriteThrottleSmokeTest.testThrottle start to fail on master, possible 
> after IGNITE-12802 was merged.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (IGNITE-13289) PagesWriteThrottleSmokeTest.testThrottle start to fail on TC.

2020-07-24 Thread Aleksey Plekhanov (Jira)


[ 
https://issues.apache.org/jira/browse/IGNITE-13289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17164231#comment-17164231
 ] 

Aleksey Plekhanov commented on IGNITE-13289:


Thank you. Cherry-picked to 2.9

> PagesWriteThrottleSmokeTest.testThrottle start to fail on TC.
> -
>
> Key: IGNITE-13289
> URL: https://issues.apache.org/jira/browse/IGNITE-13289
> Project: Ignite
>  Issue Type: Bug
>  Components: persistence
>Affects Versions: 2.9
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
> Fix For: 2.10
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> PagesWriteThrottleSmokeTest.testThrottle start to fail on master, possible 
> after IGNITE-12802 was merged.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (IGNITE-13289) PagesWriteThrottleSmokeTest.testThrottle start to fail on TC.

2020-07-24 Thread Stanilovsky Evgeny (Jira)


[ 
https://issues.apache.org/jira/browse/IGNITE-13289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17164217#comment-17164217
 ] 

Stanilovsky Evgeny commented on IGNITE-13289:
-

Thank you! One more green test almost good choice ) And what about production 
functional i really don`t know here .. Looks like this little changes can`t 
broke something, it would be better to merge them. 

> PagesWriteThrottleSmokeTest.testThrottle start to fail on TC.
> -
>
> Key: IGNITE-13289
> URL: https://issues.apache.org/jira/browse/IGNITE-13289
> Project: Ignite
>  Issue Type: Bug
>  Components: persistence
>Affects Versions: 2.9
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
> Fix For: 2.10
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> PagesWriteThrottleSmokeTest.testThrottle start to fail on master, possible 
> after IGNITE-12802 was merged.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (IGNITE-13289) PagesWriteThrottleSmokeTest.testThrottle start to fail on TC.

2020-07-24 Thread Aleksey Plekhanov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-13289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksey Plekhanov updated IGNITE-13289:
---
Fix Version/s: 2.10

> PagesWriteThrottleSmokeTest.testThrottle start to fail on TC.
> -
>
> Key: IGNITE-13289
> URL: https://issues.apache.org/jira/browse/IGNITE-13289
> Project: Ignite
>  Issue Type: Bug
>  Components: persistence
>Affects Versions: 2.9
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
> Fix For: 2.10
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> PagesWriteThrottleSmokeTest.testThrottle start to fail on master, possible 
> after IGNITE-12802 was merged.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (IGNITE-13289) PagesWriteThrottleSmokeTest.testThrottle start to fail on TC.

2020-07-24 Thread Aleksey Plekhanov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-13289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksey Plekhanov updated IGNITE-13289:
---
Affects Version/s: (was: 2.8.1)
   2.9

> PagesWriteThrottleSmokeTest.testThrottle start to fail on TC.
> -
>
> Key: IGNITE-13289
> URL: https://issues.apache.org/jira/browse/IGNITE-13289
> Project: Ignite
>  Issue Type: Bug
>  Components: persistence
>Affects Versions: 2.9
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> PagesWriteThrottleSmokeTest.testThrottle start to fail on master, possible 
> after IGNITE-12802 was merged.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (IGNITE-13296) .NET: TransactionImpl finalizer can crash the process

2020-07-24 Thread Pavel Tupitsyn (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-13296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Tupitsyn updated IGNITE-13296:

Description: 
~TransactionImpl potentially throws an exception (e.g. when grid is stopped), 
causing the entire process to abort.
GetLocalActiveTransactions is especially problematic - the method is 
informational, yet will result in all the returned transactions to be finalized 
later.

* Finalizers should not throw exceptions
* Stopped grid is a valid use case
* GetLocalActiveTransactions should be fixed to return "read-only" transactions 
that won't be finalized

Review all filalizers and make sure they are safe.

  was:
~TransactionImpl potentially throws an exception (e.g. when grid is stopped), 
causing the entire process to abort.
* Finalizers should not throw exceptions
* Stopped grid is a valid use case

Review all filalizers and make sure they are safe.


> .NET: TransactionImpl finalizer can crash the process
> -
>
> Key: IGNITE-13296
> URL: https://issues.apache.org/jira/browse/IGNITE-13296
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
>  Labels: .NET
> Fix For: 2.10
>
>
> ~TransactionImpl potentially throws an exception (e.g. when grid is stopped), 
> causing the entire process to abort.
> GetLocalActiveTransactions is especially problematic - the method is 
> informational, yet will result in all the returned transactions to be 
> finalized later.
> * Finalizers should not throw exceptions
> * Stopped grid is a valid use case
> * GetLocalActiveTransactions should be fixed to return "read-only" 
> transactions that won't be finalized
> Review all filalizers and make sure they are safe.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (IGNITE-13296) .NET: TransactionImpl finalizer can crash the process

2020-07-24 Thread Pavel Tupitsyn (Jira)
Pavel Tupitsyn created IGNITE-13296:
---

 Summary: .NET: TransactionImpl finalizer can crash the process
 Key: IGNITE-13296
 URL: https://issues.apache.org/jira/browse/IGNITE-13296
 Project: Ignite
  Issue Type: Bug
  Components: platforms
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 2.10


~TransactionImpl potentially throws an exception (e.g. when grid is stopped), 
causing the entire process to abort.
* Finalizers should not throw exceptions
* Stopped grid is a valid use case

Review all filalizers and make sure they are safe.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (IGNITE-12930) DistributedProcess fails node if unable to send single message to coordinator

2020-07-24 Thread Aleksey Plekhanov (Jira)


[ 
https://issues.apache.org/jira/browse/IGNITE-12930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17164205#comment-17164205
 ] 

Aleksey Plekhanov commented on IGNITE-12930:


Cherry-picked to 2.9

> DistributedProcess fails node if unable to send single message to coordinator
> -
>
> Key: IGNITE-12930
> URL: https://issues.apache.org/jira/browse/IGNITE-12930
> Project: Ignite
>  Issue Type: Bug
>Reporter: Maxim Muzafarov
>Assignee: Amelchev Nikita
>Priority: Critical
> Fix For: 2.9
>
>  Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> The 
> [DistributedProcess|https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/util/distributed/DistributedProcess.java]
>  fails the local node ({{FailureHandler}} CRITICAL_ERROR thrown) if unable to 
> send a message to the coordinator (e.g. the coordinator fails right before 
> the single message is sent).
> {code:java}
> try {
> ctx.io().sendToGridTopic(p.crdId, 
> GridTopic.TOPIC_DISTRIBUTED_PROCESS, singleMsg, SYSTEM_POOL);
> }
> catch (IgniteCheckedException e) {
> log.error("Unable to send message to coordinator.", e);
> ctx.failure().process(new FailureContext(CRITICAL_ERROR,
> new Exception("Unable to send message to coordinator.", 
> e)));
> }
> {code}
> h4. Expected behaviour
> If the {{ClusterTopologyCheckedException}} occurs need to wait for the 
> NODE_LEFT event of the coordinator node and re-init the distributed process 
> future.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (IGNITE-12438) Extend communication protocol to establish client-server connection

2020-07-24 Thread Aleksey Plekhanov (Jira)


[ 
https://issues.apache.org/jira/browse/IGNITE-12438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17164204#comment-17164204
 ] 

Aleksey Plekhanov commented on IGNITE-12438:


Cherrry-picked to 2.9

> Extend communication protocol to establish client-server connection
> ---
>
> Key: IGNITE-12438
> URL: https://issues.apache.org/jira/browse/IGNITE-12438
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Assignee: Ivan Bessonov
>Priority: Major
> Fix For: 2.9
>
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> Recently there was quite a lot of questions related to thick clients 
> connectivity issues when the clients are deployed in a k8s pod [1]. The 
> general issue here is clients reporting network address which are not 
> reachable from server nodes. At the same time, the clients can connect to 
> server nodes.
> An idea of how to fix this is as follows:
>  * Make sure that think clients discovery SPI always maintains a connection 
> to a server node (this should be already implemented)
>  * (Optionally) detect when a client has only one-way connectivity with the 
> server nodes. This part should be investigated. We need this to avoid server 
> nodes attempt to connect to a client and send communication request to the 
> client node faster
>  * When a server attempts to establish a connection with a client, check if 
> client is unreachable or the previous connection attempt failed. If so, send 
> a discovery message to the client to force a client-server connection. In 
> this case, server will be able to send the original message via the newly 
> established connection.
> [1] 
> https://stackoverflow.com/questions/59192075/ignite-communicationspi-questions-in-paas-environment/59232504



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (IGNITE-13038) Phase out Ignite Web Console

2020-07-24 Thread Aleksey Plekhanov (Jira)


[ 
https://issues.apache.org/jira/browse/IGNITE-13038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17164198#comment-17164198
 ] 

Aleksey Plekhanov commented on IGNITE-13038:


Cherry-picked to 2.9

> Phase out Ignite Web Console
> 
>
> Key: IGNITE-13038
> URL: https://issues.apache.org/jira/browse/IGNITE-13038
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Denis A. Magda
>Assignee: Alexey Kuznetsov
>Priority: Critical
> Fix For: 2.10
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> The community voted to stop the development and maintenance of Ignite Web 
> Console:
> http://apache-ignite-developers.2346864.n4.nabble.com/RESULT-VOTE-Stop-Maintenance-of-Ignite-Web-Console-td47548.html
> The following needs to be done:
> * Move the tool's source code from the Ignite core to its own repository 
> (https://github.com/apache/ignite-web-console)
> * Update the repository description highlighting that the tool is no longer 
> supported by the community.
> * Unlist Web Console documentation from the navigation and main menus. Do NOT 
> remove as long as there are many pages referring to the docs. Just hide.
> * Put a callout on all the hidden documentation pages saying that the tool's 
> source code is archived (provide a reference to the repo).
> * Close all the JIRA tickets created for Web Console with the notice that the 
> tool is discontinued and no longer supported.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (IGNITE-13038) Phase out Ignite Web Console

2020-07-24 Thread Aleksey Plekhanov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-13038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksey Plekhanov updated IGNITE-13038:
---
Fix Version/s: (was: 2.10)
   2.9

> Phase out Ignite Web Console
> 
>
> Key: IGNITE-13038
> URL: https://issues.apache.org/jira/browse/IGNITE-13038
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Denis A. Magda
>Assignee: Alexey Kuznetsov
>Priority: Critical
> Fix For: 2.9
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> The community voted to stop the development and maintenance of Ignite Web 
> Console:
> http://apache-ignite-developers.2346864.n4.nabble.com/RESULT-VOTE-Stop-Maintenance-of-Ignite-Web-Console-td47548.html
> The following needs to be done:
> * Move the tool's source code from the Ignite core to its own repository 
> (https://github.com/apache/ignite-web-console)
> * Update the repository description highlighting that the tool is no longer 
> supported by the community.
> * Unlist Web Console documentation from the navigation and main menus. Do NOT 
> remove as long as there are many pages referring to the docs. Just hide.
> * Put a callout on all the hidden documentation pages saying that the tool's 
> source code is archived (provide a reference to the repo).
> * Close all the JIRA tickets created for Web Console with the notice that the 
> tool is discontinued and no longer supported.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (IGNITE-13295) Expiration of cache entries, which relate to a non-persistent data region in the persistent cluster, results in AssertionError

2020-07-24 Thread Vyacheslav Koptilin (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-13295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vyacheslav Koptilin updated IGNITE-13295:
-
Description: 
In the case of the cluster uses AI native persistent and, at the same time, it 
has a non-persistent data region and cache related to that non-persistent 
region with expiry policy specified, the following Exception is thrown:

{noformat}
java.lang.AssertionError
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.remove(IgniteCacheOffheapManagerImpl.java:2678)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.remove(IgniteCacheOffheapManagerImpl.java:619)
at 
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.removeValue(GridCacheMapEntry.java:4411)
at 
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.onExpired(GridCacheMapEntry.java:4103)
at 
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.onTtlExpired(GridCacheMapEntry.java:4028)
at 
org.apache.ignite.internal.processors.cache.GridCacheTtlManager$1.applyx(GridCacheTtlManager.java:76)
at 
org.apache.ignite.internal.processors.cache.GridCacheTtlManager$1.applyx(GridCacheTtlManager.java:67)
at 
org.apache.ignite.internal.util.lang.IgniteInClosure2X.apply(IgniteInClosure2X.java:38)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.expireInternal(IgniteCacheOffheapManagerImpl.java:1422)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.expire(IgniteCacheOffheapManagerImpl.java:1367)
at 
org.apache.ignite.internal.processors.cache.GridCacheTtlManager.expire(GridCacheTtlManager.java:243)
at 
org.apache.ignite.internal.processors.cache.GridCacheSharedTtlCleanupManager$CleanupWorker.lambda$body$0(GridCacheSharedTtlCleanupManager.java:179)
at 
java.util.concurrent.ConcurrentHashMap.computeIfPresent(ConcurrentHashMap.java:1769)
at 
org.apache.ignite.internal.processors.cache.GridCacheSharedTtlCleanupManager$CleanupWorker.body(GridCacheSharedTtlCleanupManager.java:178)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748)
{noformat}

The root cause of the issue is the fact that 
{{IgniteCacheOffheapManagerImpl#expireInternal}} does not try to acquire a 
checkpoint read lock at all.

  was:
In the case of the cluster uses AI native persistent and, in the same time, it 
has a non-persistent data region and cache related to that non-persistent 
region with expiry policy specified, the following Exception is thrown:

{noformat}
java.lang.AssertionError
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.remove(IgniteCacheOffheapManagerImpl.java:2678)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.remove(IgniteCacheOffheapManagerImpl.java:619)
at 
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.removeValue(GridCacheMapEntry.java:4411)
at 
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.onExpired(GridCacheMapEntry.java:4103)
at 
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.onTtlExpired(GridCacheMapEntry.java:4028)
at 
org.apache.ignite.internal.processors.cache.GridCacheTtlManager$1.applyx(GridCacheTtlManager.java:76)
at 
org.apache.ignite.internal.processors.cache.GridCacheTtlManager$1.applyx(GridCacheTtlManager.java:67)
at 
org.apache.ignite.internal.util.lang.IgniteInClosure2X.apply(IgniteInClosure2X.java:38)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.expireInternal(IgniteCacheOffheapManagerImpl.java:1422)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.expire(IgniteCacheOffheapManagerImpl.java:1367)
at 
org.apache.ignite.internal.processors.cache.GridCacheTtlManager.expire(GridCacheTtlManager.java:243)
at 
org.apache.ignite.internal.processors.cache.GridCacheSharedTtlCleanupManager$CleanupWorker.lambda$body$0(GridCacheSharedTtlCleanupManager.java:179)
at 
java.util.concurrent.ConcurrentHashMap.computeIfPresent(ConcurrentHashMap.java:1769)
at 
org.apache.ignite.internal.processors.cache.GridCacheSharedTtlCleanupManager$CleanupWorker.body(GridCacheSharedTtlCleanupManager.java:178)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748)
{noformat}

The root cause of the issue is the fact that 
{{IgniteCacheOffheapManagerImpl#expireInternal}} does not try to acquire a 
checkpoint read lock at all.


> Expiration of cache entries, which relate to a non-persistent data region in 
> the persistent cluster, results in 

[jira] [Commented] (IGNITE-13266) PDS (Indexing) fails with 'Exit code 137"

2020-07-24 Thread Ivan Bessonov (Jira)


[ 
https://issues.apache.org/jira/browse/IGNITE-13266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17164186#comment-17164186
 ] 

Ivan Bessonov commented on IGNITE-13266:


"Cache 7" suite: 
[https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Cache7_IgniteTests24Java8=pull%2F8051%2Fhead=buildTypeStatusDiv]

> PDS (Indexing) fails with 'Exit code 137"
> -
>
> Key: IGNITE-13266
> URL: https://issues.apache.org/jira/browse/IGNITE-13266
> Project: Ignite
>  Issue Type: Test
>Reporter: Ivan Bessonov
>Assignee: Ivan Bessonov
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> [https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_PdsIndexing_IgniteTests24Java8=%3Cdefault%3E=buildTypeHistoryList]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)