[jira] [Commented] (IGNITE-11087) GridJobCheckpointCleanupSelfTest.testCheckpointCleanup is flaky

2019-10-18 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-11087:


{panel:title=Branch: [pull/6987/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4707285buildTypeId=IgniteTests24Java8_RunAll]

> GridJobCheckpointCleanupSelfTest.testCheckpointCleanup is flaky
> ---
>
> Key: IGNITE-11087
> URL: https://issues.apache.org/jira/browse/IGNITE-11087
> Project: Ignite
>  Issue Type: Bug
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
>  Labels: MakeTeamcityGreenAgain
> Attachments: #removeCheckpoint is called once more.txt, 
> #removeCheckpoint isn't called.txt
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The method of remove a checkpoint is sometimes not called or is called once 
> more. Test has a very low fail rate, 1 per 366 runs on 
> [TeamCity|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-7655052229521669617=testDetails_IgniteTests24Java8=%3Cdefault%3E]
>  and 1 per 412 on TC Bot. On local machine approximately 1 failure per 100 
> runs. Logs in the attachment.
> Test is flaky for a long time. Before replacing IP Finder in IGNITE-10555, 
> test was slower, which made fail rate even less.
>  
> {code:java}
> [2019-01-25 14:49:03,050][ERROR][main][root] Test failed.
> junit.framework.AssertionFailedError: expected:<1> but was:<0>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:234)
> at junit.framework.Assert.assertEquals(Assert.java:241)
> at 
> org.apache.ignite.internal.GridJobCheckpointCleanupSelfTest.testCheckpointCleanup(GridJobCheckpointCleanupSelfTest.java:88)
> at sun.reflect.GeneratedMethodAccessor22.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2088)
> at java.lang.Thread.run(Thread.java:748){code}
>  
> [^#removeCheckpoint isn't called.txt]
> ^_^
>  
> {code:java}
> [2019-01-25 14:50:03,282][ERROR][main][root] Test failed.
> junit.framework.AssertionFailedError: expected:<-1> but was:<0>
>  at junit.framework.Assert.fail(Assert.java:57)
>  at junit.framework.Assert.failNotEquals(Assert.java:329)
>  at junit.framework.Assert.assertEquals(Assert.java:78)
>  at junit.framework.Assert.assertEquals(Assert.java:234)
>  at junit.framework.Assert.assertEquals(Assert.java:241)
>  at 
> org.apache.ignite.internal.GridJobCheckpointCleanupSelfTest.testCheckpointCleanup(GridJobCheckpointCleanupSelfTest.java:88)
>  at sun.reflect.GeneratedMethodAccessor22.invoke(Unknown Source)
>  at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  at java.lang.reflect.Method.invoke(Method.java:498)
>  at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
>  at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>  at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
>  at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
>  at 
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2088)
>  at java.lang.Thread.run(Thread.java:748){code}
> [^#removeCheckpoint is called once more.txt]



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


[jira] [Commented] (IGNITE-12302) Test ZookeeperDiscoveryTopologyChangeAndReconnectTest.testDuplicatedNodeId is broken.

2019-10-18 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12302:


{panel:title=Branch: [pull/6986/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4705571buildTypeId=IgniteTests24Java8_RunAll]

> Test ZookeeperDiscoveryTopologyChangeAndReconnectTest.testDuplicatedNodeId is 
> broken.
> -
>
> Key: IGNITE-12302
> URL: https://issues.apache.org/jira/browse/IGNITE-12302
> Project: Ignite
>  Issue Type: Bug
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
>Priority: Minor
> Fix For: 2.8
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Test checks that a new node will not be started with the same node id. 
> Newly added SystemView creates table on node startup and fails with error:
> {noformat}
> java.lang.AssertionError: Unexpected exception
>   at 
> org.apache.ignite.testframework.GridTestUtils.fail(GridTestUtils.java:622)
>   at 
> org.apache.ignite.testframework.GridTestUtils.assertThrowsAnyCause(GridTestUtils.java:465)
>   at 
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryTopologyChangeAndReconnectTest.testDuplicatedNodeId(ZookeeperDiscoveryTopologyChangeAndReconnectTest.java:582)
>   at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.base/java.lang.reflect.Method.invoke(Method.java:566)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2090)
>   at java.base/java.lang.Thread.run(Thread.java:834)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to register 
> system view.
>   at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1401)
>   at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2038)
>   at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1703)
>   at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1117)
>   at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:615)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:983)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:924)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:912)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:878)
>   at 
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryTopologyChangeAndReconnectTest.lambda$testDuplicatedNodeId$0(ZookeeperDiscoveryTopologyChangeAndReconnectTest.java:583)
>   at 
> org.apache.ignite.testframework.GridTestUtils.assertThrowsAnyCause(GridTestUtils.java:449)
>   ... 11 more
> Caused by: class org.apache.ignite.IgniteException: Failed to register system 
> view.
>   at 
> org.apache.ignite.internal.processors.query.h2.SchemaManager.createSystemView(SchemaManager.java:238)
>   at 
> org.apache.ignite.internal.processors.query.h2.SchemaManager.createSystemViews(SchemaManager.java:247)
>   at 
> org.apache.ignite.internal.processors.query.h2.SchemaManager.start(SchemaManager.java:195)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.start(IgniteH2Indexing.java:2083)
> [2019-10-17 21:50:42,017][INFO ][main][root] >>> Stopping test: 
> ZookeeperDiscoveryTopologyChangeAndReconnectTest#testDuplicatedNodeId in 261 
> ms <<<
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.start(GridQueryProcessor.java:250)
>   at 
> org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1977)
>   at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1213)
>   ... 21 more
> Caused by: org.h2.jdbc.JdbcSQLException: Таблица "NODE_ATTRIBUTES" уже 
> существует
> Table "NODE_ATTRIBUTES" already 

[jira] [Commented] (IGNITE-6804) Print a warning if HashMap is passed into bulk update operations

2019-10-17 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-6804:
---

{panel:title=Branch: [pull/6976/head] Base: [master] : Possible Blockers 
(3)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Start Nodes{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=4697296]]
* IgniteStartStopRestartTestSuite: 
IgniteProjectionStartStopRestartSelfTest.testStartOneNode - Test has low fail 
rate in base branch 0,0% and is not flaky

{color:#d04437}Platform .NET (Inspections)*{color} [[tests 0 Failure on metric 
|https://ci.ignite.apache.org/viewLog.html?buildId=4698855]]

{color:#d04437}~Build Apache Ignite~{color} [[tests 0 Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=4705081]]

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

> Print a warning if HashMap is passed into bulk update operations
> 
>
> Key: IGNITE-6804
> URL: https://issues.apache.org/jira/browse/IGNITE-6804
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Reporter: Denis A. Magda
>Assignee: Ilya Kasnacheev
>Priority: Critical
>  Labels: usability
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> Ignite newcomers tend to stumble on deadlocks simply because the keys are 
> passed in an unordered HashMap. Propose to do the following:
> * update bulk operations Java docs.
> * print out a warning if not SortedMap (e.g. HashMap, 
> Weak/Identity/Concurrent/Linked HashMap etc) is passed into
> a bulk method (instead of SortedMap) and contains more than 1 element. 
> However, we should make sure that we only print that warning once and not 
> every time the API is called.
> * do not produce warning for explicit optimistic transactions
> More details are here:
> http://apache-ignite-developers.2346864.n4.nabble.com/Re-Ignite-2-0-0-GridUnsafe-unmonitor-td23706.html



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


[jira] [Commented] (IGNITE-6804) Print a warning if HashMap is passed into bulk update operations

2019-10-17 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-6804:
---

{panel:title=Branch: [pull/6976/head] Base: [master] : Possible Blockers 
(3)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Start Nodes{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=4697296]]
* IgniteStartStopRestartTestSuite: 
IgniteProjectionStartStopRestartSelfTest.testStartOneNode - Test has low fail 
rate in base branch 0,0% and is not flaky

{color:#d04437}Platform .NET (Inspections)*{color} [[tests 0 Failure on metric 
|https://ci.ignite.apache.org/viewLog.html?buildId=4698855]]

{color:#d04437}~Build Apache Ignite~{color} [[tests 0 Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=4704733]]

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

> Print a warning if HashMap is passed into bulk update operations
> 
>
> Key: IGNITE-6804
> URL: https://issues.apache.org/jira/browse/IGNITE-6804
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Reporter: Denis A. Magda
>Assignee: Ilya Kasnacheev
>Priority: Critical
>  Labels: usability
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> Ignite newcomers tend to stumble on deadlocks simply because the keys are 
> passed in an unordered HashMap. Propose to do the following:
> * update bulk operations Java docs.
> * print out a warning if not SortedMap (e.g. HashMap, 
> Weak/Identity/Concurrent/Linked HashMap etc) is passed into
> a bulk method (instead of SortedMap) and contains more than 1 element. 
> However, we should make sure that we only print that warning once and not 
> every time the API is called.
> * do not produce warning for explicit optimistic transactions
> More details are here:
> http://apache-ignite-developers.2346864.n4.nabble.com/Re-Ignite-2-0-0-GridUnsafe-unmonitor-td23706.html



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


[jira] [Commented] (IGNITE-12186) TDE - Phase-2. Master key rotation.

2019-10-17 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12186:


{panel:title=Branch: [pull/6937/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4687563buildTypeId=IgniteTests24Java8_RunAll]

> TDE - Phase-2. Master key rotation.
> ---
>
> Key: IGNITE-12186
> URL: https://issues.apache.org/jira/browse/IGNITE-12186
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
>Priority: Major
>  Labels: IEP-18
> Fix For: 2.9
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Need to implement master key rotation process. Master key(MK) rotation 
> required in case of it compromising or at the end of crypto period(key 
> validity period). 
> [Design 
> (cwiki).|https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=95652381]



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


[jira] [Commented] (IGNITE-11704) Write tombstones during rebalance to get rid of deferred delete buffer

2019-10-17 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-11704:


{panel:title=Branch: [pull/6931/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4701586buildTypeId=IgniteTests24Java8_RunAll]

> Write tombstones during rebalance to get rid of deferred delete buffer
> --
>
> Key: IGNITE-11704
> URL: https://issues.apache.org/jira/browse/IGNITE-11704
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Assignee: Pavel Kovalenko
>Priority: Major
>  Labels: rebalance
> Fix For: 2.8
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently Ignite relies on deferred delete buffer in order to handle 
> write-remove conflicts during rebalance. Given the limit size of the buffer, 
> this approach is fundamentally flawed, especially in case when persistence is 
> enabled.
> I suggest to extend the logic of data storage to be able to store key 
> tombstones - to keep version for deleted entries. The tombstones will be 
> stored when rebalance is in progress and should be cleaned up when rebalance 
> is completed.
> Later this approach may be used to implement fast partition rebalance based 
> on merkle trees (in this case, tombstones should be written on an incomplete 
> baseline).



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


[jira] [Commented] (IGNITE-11898) Java Thin: Implement Best Effort Affinity

2019-10-16 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-11898:


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

> Java Thin: Implement Best Effort Affinity
> -
>
> Key: IGNITE-11898
> URL: https://issues.apache.org/jira/browse/IGNITE-11898
> Project: Ignite
>  Issue Type: New Feature
>  Components: thin client
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
>  Labels: iep-23
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> See linked IEP-23.



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


[jira] [Commented] (IGNITE-12259) Create new module for support spring-5.2.X and spring-data-2.2.X

2019-10-16 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12259:


{panel:title=Branch: [pull/6978/head] Base: [master] : Possible Blockers 
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}ZooKeeper (Discovery) 1{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=4700852]]
* ZookeeperDiscoverySpiTestSuite1: 
ZookeeperDiscoveryConcurrentStartAndStartStopTest.testStartStop2 - Test has low 
fail rate in base branch 0,0% and is not flaky

{color:#d04437}Platform .NET (Inspections)*{color} [[tests 0 Failure on metric 
|https://ci.ignite.apache.org/viewLog.html?buildId=4700901]]

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

> Create new module for support spring-5.2.X and spring-data-2.2.X
> 
>
> Key: IGNITE-12259
> URL: https://issues.apache.org/jira/browse/IGNITE-12259
> Project: Ignite
>  Issue Type: Wish
>Reporter: Surkov Aleksandr
>Assignee: Surkov Aleksandr
>Priority: Minor
> Fix For: 2.8
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> The actual spring version is 
> [5.2.0.RELEASE|https://mvnrepository.com/artifact/org.springframework/spring-context/5.2.0.RELEASE],
>  spring data version is 
> [2.2.0.RELEASE.|https://mvnrepository.com/artifact/org.springframework.data/spring-data-commons/2.2.0.RELEASE]
> It would be nice to add a module to support these versions.



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


[jira] [Commented] (IGNITE-12292) Java thin client: In some cases txId intersection (tx started on different nodes) leads to errors

2019-10-16 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12292:


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

> Java thin client: In some cases txId intersection (tx started on different 
> nodes) leads to errors
> -
>
> Key: IGNITE-12292
> URL: https://issues.apache.org/jira/browse/IGNITE-12292
> Project: Ignite
>  Issue Type: Bug
>  Components: thin client
>Affects Versions: 2.8
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Fix For: 2.8
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Reproducer:
> {code:java}
> public void testTxWithIdIntersection() throws Exception {
> int CLUSTER_SIZE = 2;
> try (LocalIgniteCluster cluster = LocalIgniteCluster.start(CLUSTER_SIZE);
>  IgniteClient client = Ignition.startClient(new ClientConfiguration()
>  .setAddresses(cluster.clientAddresses().toArray(new 
> String[CLUSTER_SIZE])))
> ) {
> ClientCache cache = client.createCache(new 
> ClientCacheConfiguration().setName("cache")
> .setAtomicityMode(CacheAtomicityMode.TRANSACTIONAL));
> CyclicBarrier barrier = new CyclicBarrier(2);
> GridTestUtils.runAsync(() -> {
> try {
> // Another thread starts transaction here.
> barrier.await(1, TimeUnit.SECONDS);
> for (int i = 0; i < CLUSTER_SIZE; i++)
> dropAllThinClientConnections(Ignition.allGrids().get(i));
> ClientTransaction tx = client.transactions().txStart();
> barrier.await(1, TimeUnit.SECONDS);
> // Another thread puts to cache here.
> barrier.await(1, TimeUnit.SECONDS);
> tx.commit();
> barrier.await(1, TimeUnit.SECONDS);
> }
> catch (Exception e) {
> log.error("Unexpected error", e);
> }
> });
> ClientTransaction tx = client.transactions().txStart();
> barrier.await(1, TimeUnit.SECONDS);
> // Another thread drops connections and create new transaction here, 
> which started on another node with the
> // same transaction id as we started in this thread.
> barrier.await(1, TimeUnit.SECONDS);
> try {
> cache.put(0, 0);
> fail("Exception expected");
> }
> catch (ClientException expected) {
> // No-op.
> }
> tx.close();
> barrier.await(1, TimeUnit.SECONDS);
> // Another thread commit transaction here.
> barrier.await(1, TimeUnit.SECONDS);
> assertFalse(cache.containsKey(0));
> }
> }
> {code}



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


[jira] [Commented] (IGNITE-11852) Assertion errors when changing PME coordinator to locally joining node

2019-10-15 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-11852:


{panel:title=Branch: [pull/6539/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4696234buildTypeId=IgniteTests24Java8_RunAll]

> Assertion errors when changing PME coordinator to locally joining node
> --
>
> Key: IGNITE-11852
> URL: https://issues.apache.org/jira/browse/IGNITE-11852
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.5, 2.7
>Reporter: Pavel Kovalenko
>Assignee: Pavel Kovalenko
>Priority: Critical
> Fix For: 2.8
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> When PME coordinator changed to locally joining node several assertion errors 
> may occur:
> 1. When some other joining nodes finished PME:
> {noformat}
> [13:49:58] (err) Failed to notify listener: 
> o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$8$1$1...@27296181java.lang.AssertionError:
>  AffinityTopologyVersion [topVer=2, minorTopVer=0]
>   at 
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager$11.applyx(CacheAffinitySharedManager.java:1546)
>   at 
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager$11.applyx(CacheAffinitySharedManager.java:1535)
>   at 
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.lambda$forAllRegisteredCacheGroups$e0a6939d$1(CacheAffinitySharedManager.java:1281)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.doInParallel(IgniteUtils.java:10929)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.doInParallel(IgniteUtils.java:10831)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.doInParallel(IgniteUtils.java:10811)
>   at 
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.forAllRegisteredCacheGroups(CacheAffinitySharedManager.java:1280)
>   at 
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.onLocalJoin(CacheAffinitySharedManager.java:1535)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.processFullMessage(GridDhtPartitionsExchangeFuture.java:4189)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onBecomeCoordinator(GridDhtPartitionsExchangeFuture.java:4731)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.access$3400(GridDhtPartitionsExchangeFuture.java:145)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$8$1$1.apply(GridDhtPartitionsExchangeFuture.java:4622)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$8$1$1.apply(GridDhtPartitionsExchangeFuture.java:4611)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:398)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:346)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:334)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:510)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:489)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:466)
>   at 
> org.apache.ignite.internal.util.future.GridCompoundFuture.checkComplete(GridCompoundFuture.java:281)
>   at 
> org.apache.ignite.internal.util.future.GridCompoundFuture.apply(GridCompoundFuture.java:143)
>   at 
> org.apache.ignite.internal.util.future.GridCompoundFuture.apply(GridCompoundFuture.java:44)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:398)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:346)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:334)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:510)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:489)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:455)
>   at 
> 

[jira] [Commented] (IGNITE-6804) Print a warning if HashMap is passed into bulk update operations

2019-10-15 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-6804:
---

{panel:title=Branch: [pull/6976/head] Base: [master] : Possible Blockers 
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET (Inspections)*{color} [[tests 0 Failure on metric 
|https://ci.ignite.apache.org/viewLog.html?buildId=4698855]]

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

> Print a warning if HashMap is passed into bulk update operations
> 
>
> Key: IGNITE-6804
> URL: https://issues.apache.org/jira/browse/IGNITE-6804
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Reporter: Denis A. Magda
>Assignee: Ilya Kasnacheev
>Priority: Critical
>  Labels: usability
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Ignite newcomers tend to stumble on deadlocks simply because the keys are 
> passed in an unordered HashMap. Propose to do the following:
> * update bulk operations Java docs.
> * print out a warning if not SortedMap (e.g. HashMap, 
> Weak/Identity/Concurrent/Linked HashMap etc) is passed into
> a bulk method (instead of SortedMap) and contains more than 1 element. 
> However, we should make sure that we only print that warning once and not 
> every time the API is called.
> * do not produce warning for explicit optimistic transactions
> More details are here:
> http://apache-ignite-developers.2346864.n4.nabble.com/Re-Ignite-2-0-0-GridUnsafe-unmonitor-td23706.html



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


[jira] [Commented] (IGNITE-10771) Print troubleshooting hint when exchange latch got stucked

2019-10-15 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-10771:


{panel:title=Branch: [pull/6968/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4688174buildTypeId=IgniteTests24Java8_RunAll]

> Print troubleshooting hint when exchange latch got stucked
> --
>
> Key: IGNITE-10771
> URL: https://issues.apache.org/jira/browse/IGNITE-10771
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: 2.5
>Reporter: Pavel Kovalenko
>Assignee: Pavel Kovalenko
>Priority: Minor
>  Labels: usability
> Fix For: 2.8
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Sometimes users face with a problem when exchange latch can't be completed:
> {noformat}
> 2018-12-12 07:07:57:563 [exchange-worker-#42] WARN 
> o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture:488 - Unable to await 
> partitions release latch within timeout: ClientLatch 
> [coordinator=ZookeeperClusterNode [id=6b9fc6e4-5b6a-4a98-be4d-6bc1aa5c014c, 
> addrs=[172.17.0.1, 10.0.230.117, 0:0:0:0:0:0:0:1%lo, 127.0.0.1], order=3, 
> loc=false, client=false], ackSent=true, super=CompletableLatch [id=exchange, 
> topVer=AffinityTopologyVersion [topVer=45, minorTopVer=1]]] 
> {noformat}
> It may indicate that some node in a cluster can' t finish partitions release 
> (finish all ongoing operations at the previous topology version) or it can be 
> silent network problem.
> We should print to log a hint how to troubleshoot it to reduce the number of 
> questions about such problem.



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


[jira] [Commented] (IGNITE-6930) Optionally to do not write free list updates to WAL

2019-10-14 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-6930:
---

{panel:title=Branch: [pull/6893/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4696109buildTypeId=IgniteTests24Java8_RunAll]

> Optionally to do not write free list updates to WAL
> ---
>
> Key: IGNITE-6930
> URL: https://issues.apache.org/jira/browse/IGNITE-6930
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Reporter: Vladimir Ozerov
>Assignee: Aleksey Plekhanov
>Priority: Major
>  Labels: IEP-8, performance
> Fix For: 2.8
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> When cache entry is created, we need to write update the free list. When 
> entry is updated, we need to update free list(s) several times. Currently 
> free list is persistent structure, so every update to it must be logged to be 
> able to recover after crash. This may incur significant overhead, especially 
> for small entries.
> E.g. this is how WAL for a single update looks like. "D" - updates with real 
> data, "F" - free-list management:
> {code}
>  1. [D] DataRecord [writeEntries=[UnwrapDataEntry[k = key, v = [ BinaryObject 
> [idHash=2053299190, hash=1986931360, typeId=-1580729813]], super = [DataEntry 
> [cacheId=94416770, op=UPDATE, writeVer=GridCacheVersion [topVer=122147562, 
> order=1510667560607, nodeOrder=1], partId=0, partCnt=4, super=WALRecord 
> [size=0, chainSize=0, pos=null, type=DATA_RECORD]]
>  2. [F] PagesListRemovePageRecord [rmvdPageId=00010005, 
> pageId=00010006, grpId=94416770, super=PageDeltaRecord 
> [grpId=94416770, pageId=00010006, super=WALRecord [size=37, 
> chainSize=0, pos=null, type=PAGES_LIST_REMOVE_PAGE]]]
>  3. [D] DataPageInsertRecord [super=PageDeltaRecord [grpId=94416770, 
> pageId=00010005, super=WALRecord [size=129, chainSize=0, pos=null, 
> type=DATA_PAGE_INSERT_RECORD]]]
>  4. [F] PagesListAddPageRecord [dataPageId=00010005, 
> super=PageDeltaRecord [grpId=94416770, pageId=00010008, 
> super=WALRecord [size=37, chainSize=0, pos=null, type=PAGES_LIST_ADD_PAGE]]]
>  5. [F] DataPageSetFreeListPageRecord [freeListPage=281474976710664, 
> super=PageDeltaRecord [grpId=94416770, pageId=00010005, 
> super=WALRecord [size=37, chainSize=0, pos=null, 
> type=DATA_PAGE_SET_FREE_LIST_PAGE]]]
>  6. [D] ReplaceRecord [io=DataLeafIO[ver=1], idx=0, super=PageDeltaRecord 
> [grpId=94416770, pageId=00010004, super=WALRecord [size=47, 
> chainSize=0, pos=null, type=BTREE_PAGE_REPLACE]]]
>  7. [F] DataPageRemoveRecord [itemId=0, super=PageDeltaRecord 
> [grpId=94416770, pageId=00010005, super=WALRecord [size=30, 
> chainSize=0, pos=null, type=DATA_PAGE_REMOVE_RECORD]]]
>  8. [F] PagesListRemovePageRecord [rmvdPageId=00010005, 
> pageId=00010008, grpId=94416770, super=PageDeltaRecord 
> [grpId=94416770, pageId=00010008, super=WALRecord [size=37, 
> chainSize=0, pos=null, type=PAGES_LIST_REMOVE_PAGE]]]
>  9. [F] DataPageSetFreeListPageRecord [freeListPage=0, super=PageDeltaRecord 
> [grpId=94416770, pageId=00010005, super=WALRecord [size=37, 
> chainSize=0, pos=null, type=DATA_PAGE_SET_FREE_LIST_PAGE]]]
> 10. [F] PagesListAddPageRecord [dataPageId=00010005, 
> super=PageDeltaRecord [grpId=94416770, pageId=00010006, 
> super=WALRecord [size=37, chainSize=0, pos=null, type=PAGES_LIST_ADD_PAGE]]]
> 11. [F] DataPageSetFreeListPageRecord [freeListPage=281474976710662, 
> super=PageDeltaRecord [grpId=94416770, pageId=00010005, 
> super=WALRecord [size=37, chainSize=0, pos=null, 
> type=DATA_PAGE_SET_FREE_LIST_PAGE]]]
> {code}
> If you sum all space required for operation (size in p.3 is shown incorrectly 
> here), you will see that data update required ~300 bytes, so do free list 
> update! 
> *Proposed solution*
> 1) Optionally do not write free list updates to WAL
> 2) In case of node restart we start with empty free lists, so data inserts 
> will have to allocate new pages
> 3) When old data page is read, add it to the free list
> 4) Start a background thread which will iterate over all old data pages and 
> re-create the free list, so that eventually all data pages are tracked.



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


[jira] [Commented] (IGNITE-6804) Print a warning if HashMap is passed into bulk update operations

2019-10-14 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-6804:
---

{panel:title=Branch: [pull/6976/head] Base: [master] : Possible Blockers 
(113)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform C++ (Linux)*{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4696766]]

{color:#d04437}Cache 6{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4696795]]

{color:#d04437}SPI{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4696757]]

{color:#d04437}ZooKeeper (Discovery) 3{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4696819]]

{color:#d04437}ZooKeeper (Discovery) 1{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4696764]]

{color:#d04437}Scala (Examples){color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4696762]]

{color:#d04437}Platform .NET (Long Running){color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4696815]]

{color:#d04437}Examples{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4696738]]

{color:#d04437}PDS (Compatibility){color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4696804]]

{color:#d04437}Scala (Visor Console){color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4696763]]

{color:#d04437}RDD{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4696751]]

{color:#d04437}PDS (Indexing){color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4696805]]

{color:#d04437}Cache (Expiry Policy){color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4696780]]

{color:#d04437}ZooKeeper (Discovery) 2{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4696765]]

{color:#d04437}Streamers{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4696755]]

{color:#d04437}Cache 2{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4696791]]

{color:#d04437}Start Nodes{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4696756]]

{color:#d04437}Platform .NET{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4696811]]

{color:#d04437}Platform .NET (Core Linux){color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4696812]]

{color:#d04437}MVCC Queries{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4696775]]

{color:#d04437}Continuous Query 3{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4696800]]

{color:#d04437}Cache 5{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4696794]]

{color:#d04437}PDS 1{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4696807]]

{color:#d04437}Queries 1{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4696817]]

{color:#d04437}ZooKeeper (Discovery) 4{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4696820]]

{color:#d04437}MVCC PDS 1{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4696834]]

{color:#d04437}Cache 1{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4696790]]

{color:#d04437}Thin Client: Java{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4696748]]

{color:#d04437}Compute (Grid){color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4696735]]

{color:#d04437}Basic 3{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4696770]]

{color:#d04437}Data Structures{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4696802]]

{color:#d04437}MVCC PDS 2{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4696835]]

{color:#d04437}Cache 7{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4696796]]

{color:#d04437}Continuous Query 4{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4696801]]

{color:#d04437}Basic 1{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4696769]]

{color:#d04437}MVCC Cache 1{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4696825]]

{color:#d04437}Cache 8{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4696797]]

{color:#d04437}Cache 3{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4696792]]

{color:#d04437}PDS 3{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4696809]]


[jira] [Commented] (IGNITE-8473) Add option to enable/disable WAL for several caches with single command

2019-10-12 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-8473:
---

{panel:title=Branch: [pull/6971/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4691610buildTypeId=IgniteTests24Java8_RunAll]

> Add option to enable/disable WAL for several caches with single command
> ---
>
> Key: IGNITE-8473
> URL: https://issues.apache.org/jira/browse/IGNITE-8473
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Ivan Rakov
>Assignee: Sergei Ryzhov
>Priority: Major
>  Labels: newbie
> Fix For: 2.8
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> API method for disabling WAL in IgniteCluster accepts only one cache name. 
> Every call triggers exchange and checkpoints cluster-wide - it takes plenty 
> of time to disable/enable WAL for multiple caches.
> We should add option to disable/enable WAL for several caches with single 
> command. 
> New proposed API methods:
> {noformat}
> IgniteCluster.disableWal(Collection cacheNames)
> IgniteCluster.enableWal(Collection cacheNames)
> IgniteCluster.disableWal() // Disables WAL for all caches.
> IgniteCluster.enableWal() // Enables WAL for all caches.
> {noformat}
> Methods should return true if WAL state of at least one cache was actually 
> changed by the call.



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


[jira] [Commented] (IGNITE-9165) FindBugs: Methods may fail to close stream in core module

2019-10-12 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-9165:
---

{panel:title=Branch: [pull/4481/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4688935buildTypeId=IgniteTests24Java8_RunAll]

> FindBugs: Methods may fail to close stream in core module
> -
>
> Key: IGNITE-9165
> URL: https://issues.apache.org/jira/browse/IGNITE-9165
> Project: Ignite
>  Issue Type: Bug
>  Components: binary
>Affects Versions: 2.6
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
>  Labels: newbie
> Fix For: 2.9
>
> Attachments: 
> findbugs-result-apache-ignite[ignite-core]_2018_08_02_12_38_02.html
>
>
> The method creates an IO stream object, does not assign it to any fields, 
> pass it to other methods that might close it, or return it, and does not 
> appear to close the stream on all paths out of the method.  This may result 
> in a file descriptor leak.
> Example:
>  
> {code:java}
> // GridCacheAbstractLoadTest#GridCacheAbstractLoadTest()
> try {
>  props.load(new FileReader(GridTestUtils.resolveIgnitePath(
>  "modules/tests/config/cache-load.properties")));
> }
> catch (IOException e) {
>  throw new RuntimeException(e);
> }{code}
>  
>  One of possible solutions:
> {code:java}
> try (Reader reader = new FileReader(GridTestUtils.resolveIgnitePath(
> "modules/tests/config/cache-load.properties"))) {
> props.load(reader);
> }
> catch (IOException e) {
> throw new RuntimeException(e);
> }{code}
> List of classes in "core" module:
>   
>  +org.apache.ignite.internal:+   
>  * *BinaryContext*#classesInPackage(String)
>  * *GridClientJdkMarshaller*#marshal(Object, int)
>  * 
> *IgniteExplicitImplicitDeploymentSelfTest*$GridDeploymentResourceTestJob#execute()
>  * *OptimizedObjectStreamSelfTest*#testReadLine()
>  * *PageIdDistributionTest*#_testRealHistory()
>  * *HttpIgniteUpdatesChecker*#getUpdates(boolean)
>  * *IpcSharedMemoryNativeLoaderSelfTest*#readStreams(Process)
> +org.apache.ignite:+
>  * *GridCacheAbstractLoadTest*#GridCacheAbstractLoadTest()
>  * *GridTestUtils*.sslContext()



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


[jira] [Commented] (IGNITE-9160) FindBugs: NPE and CCE on equals() methods

2019-10-12 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-9160:
---

{panel:title=Branch: [pull/6967/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4687940buildTypeId=IgniteTests24Java8_RunAll]

> FindBugs: NPE and CCE on equals() methods
> -
>
> Key: IGNITE-9160
> URL: https://issues.apache.org/jira/browse/IGNITE-9160
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.6
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
>  Labels: newbie
> Fix For: 2.9
>
> Attachments: check.txt, reproduce.txt
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Some classes have Incorrect equals() method:
> {code:java}
> // GridDhtPartitionMap.java
> @Override public boolean equals(Object o) {
> if (this == o)
> return true;
> GridDhtPartitionMap other = (GridDhtPartitionMap)o;
> return other.nodeId.equals(nodeId) && other.updateSeq == updateSeq;
> }{code}
> In this case, we can get CCE  
> {code:java}
> GridDhtPartitionMap gridDhtPartMap = new GridDhtPartitionMap();
> gridDhtPartMap.equals(new Object());
> --
> Exception in thread "main" java.lang.ClassCastException: java.lang.Object 
> cannot be cast to 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap.equals(GridDhtPartitionMap.java:319)
> at ru.zzzadruga.Ignite.main(Ignite.java:9){code}
>  Or NPE 
> {code:java}
> GridDhtPartitionMap gridDhtPartMap = new GridDhtPartitionMap();
> gridDhtPartMap.equals(null);
> --
> Exception in thread "main" java.lang.NullPointerException
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap.equals(GridDhtPartitionMap.java:321)
> at ru.zzzadruga.Ignite.main(Ignite.java:9){code}
>  The following code will prevent this
> {code:java}
> if (o == null || getClass() != o.getClass())
>     return false;{code}
> + List of classes with similar problems: +
>  * *GridTopic$T1-T8* - NPE
>  * *GridCachePreloadLifecycleAbstractTest -* NPE
>  * *GridDhtPartitionFullMap -* NPE and CCE
>  * *GridDhtPartitionMap -* NPE and CCE
>  * *OptimizedMarshallerSelfTest -* NPE and CCE
>  * *GatewayProtectedCacheProxy -* NPE and CCE
>  * *GridNearOptimisticTxPrepareFuture -* NPE and CCE
>  * *GridCacheDistributedQueryManager -* NPE and CCE
>  * *GridServiceMethodReflectKey -* NPE and CCE
>  *  *GridListSetSelfTest -* NPE and CCE
>  * *GridTestKey -* NPE and CCE
>  * *GridCacheMvccCandidate -* CCE
>  * *GridDhtPartitionExchangeId -* CCE
>  * *GridTuple6 -* CCE



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


[jira] [Commented] (IGNITE-12285) Remove boilerplate code in test PluginProvider implementations.

2019-10-12 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12285:


{panel:title=Branch: [pull/6969/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4691098buildTypeId=IgniteTests24Java8_RunAll]

> Remove boilerplate code in test PluginProvider implementations.
> ---
>
> Key: IGNITE-12285
> URL: https://issues.apache.org/jira/browse/IGNITE-12285
> Project: Ignite
>  Issue Type: Improvement
>Reporter: PetrovMikhail
>Priority: Minor
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> It's needed to remove boilerplate code in test PluginProvider implementations.



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


[jira] [Commented] (IGNITE-12212) Nodes system view

2019-10-12 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12212:


{panel:title=Branch: [pull/6927/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4691219buildTypeId=IgniteTests24Java8_RunAll]

> Nodes system view
> -
>
> Key: IGNITE-12212
> URL: https://issues.apache.org/jira/browse/IGNITE-12212
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
>  Labels: IEP-35, await
> Fix For: 2.8
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> IGNITE-12145 finished
> We should add nodes system views.
> System view should track current topology nodes.



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


[jira] [Commented] (IGNITE-12252) Unchecked exceptions during rebalancing should be handled

2019-10-12 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12252:


{panel:title=Branch: [pull/6965/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4686231buildTypeId=IgniteTests24Java8_RunAll]

> Unchecked exceptions during rebalancing should be handled
> -
>
> Key: IGNITE-12252
> URL: https://issues.apache.org/jira/browse/IGNITE-12252
> Project: Ignite
>  Issue Type: Bug
>Reporter: Aleksey Plekhanov
>Assignee: Nikolai Kulagin
>Priority: Critical
> Fix For: 2.8
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Rebalancing should handle unchecked exceptions by failure handler. In current 
> implementation unchecked exceptions just ignored. They were handled by IO 
> worker before IGNITE-3195.
> Reproducer:
> {code:java}
> @Test
> public void testRebalanceUncheckedError() throws Exception {
> IgniteEx ignite0 = startGrid(new 
> IgniteConfiguration().setIgniteInstanceName("ignite0"));
> IgniteCache cache = 
> ignite0.getOrCreateCache(DEFAULT_CACHE_NAME);
> IgniteDataStreamer streamer = 
> ignite0.dataStreamer(DEFAULT_CACHE_NAME);
> for (int i = 0; i < 100_000; i++)
> streamer.addData(i, i);
> streamer.flush();
> IgniteEx ignite1 = startGrid(new 
> IgniteConfiguration().setIgniteInstanceName("ignite1")
> 
> .setIncludeEventTypes(EventType.EVT_CACHE_REBALANCE_OBJECT_LOADED));
> ignite1.events().localListen(e -> {
> throw new Error();
> }, EventType.EVT_CACHE_REBALANCE_OBJECT_LOADED);
> awaitPartitionMapExchange();
> }
> {code}



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


[jira] [Commented] (IGNITE-12271) Persistence can't read pages from disk on Big Endian architectures

2019-10-11 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12271:


{panel:title=Branch: [pull/6953/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4673521buildTypeId=IgniteTests24Java8_RunAll]

> Persistence can't read pages from disk on Big Endian architectures
> --
>
> Key: IGNITE-12271
> URL: https://issues.apache.org/jira/browse/IGNITE-12271
> Project: Ignite
>  Issue Type: Bug
>  Components: persistence
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> So we are trying to start master on Big Endian, and we get the following 
> exceptions:
> {code}
> Runtime failure on row: Row@5bf1ee15[ snip, ver: GridCacheVersion 
> [topVer=180723326, order=1569259166164, nodeOrder=1] ][ 1307496, 32211, 3, 0 
> ]" [5-197]
> at 
> org.h2.message.DbException.getJdbcSQLException(DbException.java:357)
> ... 41 more
> Caused by: class 
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
>  Runtime failure on row: Row@5bf1ee15[ snip], ver: GridCacheVersion 
> [topVer=180723326, order=1569259166164, nodeOrder=1] ][ 1307496, 32211, 3, 0 ]
> at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doPut(BPlusTree.java:2320)
> at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.putx(BPlusTree.java:2267)
> at 
> org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.putx(H2TreeIndex.java:323)
> ... 38 more
> Caused by: java.lang.IllegalStateException: Failed to get page IO instance 
> (page content is corrupted)
> at 
> org.apache.ignite.internal.processors.cache.persistence.tree.io.IOVersions.forVersion(IOVersions.java:84)
> at 
> org.apache.ignite.internal.processors.cache.persistence.tree.io.IOVersions.forPage(IOVersions.java:96)
> at 
> org.apache.ignite.internal.processors.cache.persistence.CacheDataRowAdapter.initFromLink(CacheDataRowAdapter.java:153)
> at 
> org.apache.ignite.internal.processors.cache.persistence.CacheDataRowAdapter.initFromLink(CacheDataRowAdapter.java:107)
> at 
> org.apache.ignite.internal.processors.query.h2.database.H2RowFactory.getRow(H2RowFactory.java:61)
> at 
> org.apache.ignite.internal.processors.query.h2.database.H2Tree.createRowFromLink(H2Tree.java:221)
> at 
> org.apache.ignite.internal.processors.query.h2.database.io.AbstractH2ExtrasLeafIO.getLookupRow(AbstractH2ExtrasLeafIO.java:153)
> at 
> org.apache.ignite.internal.processors.query.h2.database.io.AbstractH2ExtrasLeafIO.getLookupRow(AbstractH2ExtrasLeafIO.java:35)
> {code}



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


[jira] [Commented] (IGNITE-12268) Adds possibility to set up custom REST processor.

2019-10-11 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12268:


{panel:title=Branch: [pull/6948/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4683540buildTypeId=IgniteTests24Java8_RunAll]

> Adds possibility to set up custom REST processor.
> -
>
> Key: IGNITE-12268
> URL: https://issues.apache.org/jira/browse/IGNITE-12268
> Project: Ignite
>  Issue Type: Improvement
>Reporter: PetrovMikhail
>Assignee: PetrovMikhail
>Priority: Major
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> It's needed to add ability to configure your own REST processor via 
> functionality of Ignite plugins.



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


[jira] [Commented] (IGNITE-11410) Sandbox for user-defined code

2019-10-11 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-11410:


{panel:title=Branch: [pull/6707/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4683179buildTypeId=IgniteTests24Java8_RunAll]

> Sandbox for user-defined code
> -
>
> Key: IGNITE-11410
> URL: https://issues.apache.org/jira/browse/IGNITE-11410
> Project: Ignite
>  Issue Type: Task
>Reporter: Anton Vinogradov
>Assignee: Denis Garus
>Priority: Major
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> We should provide a restricted environment (sandbox) in which to run 
> user-defined code securely. To get it done, we would use the java sandbox 
> model.
>  The java sandbox model allows restricting access from user-defined code to 
> the system resources or security-sensitive feature of java, for example, 
> reflection.
> The user-defined code contains:
>  - StreamReceiver for DataStreamer:
>  - EntryProcessor;
>  - ComputeJob;
>  - filter and transformer for ScanQuery.
> The user-defined code will get permissions from GridSecuerityProcessor 
> (security plugin).



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


[jira] [Commented] (IGNITE-12193) [Phase-1] Rebalancing cache group keys metric counters

2019-10-10 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12193:


{panel:title=Branch: [pull/6960/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4682945buildTypeId=IgniteTests24Java8_RunAll]

> [Phase-1] Rebalancing cache group keys metric counters
> --
>
> Key: IGNITE-12193
> URL: https://issues.apache.org/jira/browse/IGNITE-12193
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Maxim Muzafarov
>Assignee: Nikolai Kulagin
>Priority: Major
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Implement metrics counters related to the cache group:
> * rebalancingPartitionsLeft long metric
> * rebalancingReceivedKeys long metric
> * rebalancingReceivedBytes long metric
> * rebalancingStartTime long metric
> * rebalancingFinishTime long metric



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


[jira] [Commented] (IGNITE-12220) Allow to use cache-related permissions both at system and per-cache levels

2019-10-10 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12220:


{panel:title=Branch: [pull/6904/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4683308buildTypeId=IgniteTests24Java8_RunAll]

> Allow to use cache-related permissions both at system and per-cache levels
> --
>
> Key: IGNITE-12220
> URL: https://issues.apache.org/jira/browse/IGNITE-12220
> Project: Ignite
>  Issue Type: Task
>  Components: security
>Affects Versions: 2.7.6
>Reporter: Andrey Kuznetsov
>Assignee: Sergei Ryzhov
>Priority: Major
> Fix For: 2.8
>
>  Time Spent: 3.5h
>  Remaining Estimate: 0h
>
> Currently, {{CACHE_CREATE}} and {{CACHE_DESTROY}} permissions are enforced to 
> be system-level permissions, see for instance 
> {{SecurityPermissionSetBuilder#appendCachePermissions}}. This looks 
> inflexible: Ignite Security implementations are not able to manage cache 
> creation and deletion permissions on per-cache basis (unlike get/put/remove 
> permissions). All such limitations should be found and removed in order to 
> allow all {{CACHE_*}} permissions to be set both at system and per-cache 
> levels.



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


[jira] [Commented] (IGNITE-12189) Implement correct limit for TextQuery

2019-10-10 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12189:


{panel:title=Branch: [pull/6917/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4679683buildTypeId=IgniteTests24Java8_RunAll]

> Implement correct limit for TextQuery
> -
>
> Key: IGNITE-12189
> URL: https://issues.apache.org/jira/browse/IGNITE-12189
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Reporter: Yuriy Shuliha 
>Assignee: Yuriy Shuliha 
>Priority: Major
> Fix For: 2.8
>
>  Time Spent: 2h 40m
>  Remaining Estimate: 0h
>
> PROBLEM
> For now each server-node returns all response records to the client-node and 
> it may contain ~thousands, ~hundred thousands records.
>  Event if we need only first 10-100. Again, all the results are added to 
> queue in _*GridCacheQueryFutureAdapter*_ in arbitrary order by pages.
>  There are no any means to deliver deterministic result.
> SOLUTION
>  Implement _*limit*_ as parameter for _*TextQuery*_ and 
> _*GridCacheQueryRequest*_ 
>  It should be passed as limit  parameter in Lucene's  
> _*IndexSearcher.search()*_ in _*GridLuceneIndex*_.
> For distributed queries _*limit*_ will also trim response queue when merging 
> results.
> Type: long
>  Special value: : 0 -> No limit (Integer.MAX_VALUE);



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


[jira] [Commented] (IGNITE-12233) Merge benchmarks sql index benchmarks from ignite-2.7 to master

2019-10-10 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12233:


{panel:title=Branch: [pull/6913/head] Base: [master] : Possible Blockers 
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}[Check Code Style]{color} [[tests 0 Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=4682477]]

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

> Merge benchmarks sql index benchmarks from ignite-2.7 to master
> ---
>
> Key: IGNITE-12233
> URL: https://issues.apache.org/jira/browse/IGNITE-12233
> Project: Ignite
>  Issue Type: Task
>  Components: yardstick
>Reporter: Ilya Suntsov
>Assignee: Ilya Suntsov
>Priority: Major
>
> The following benchmarks are missed in master but exist in ignite-2.7:
>  * IgniteSqlUpdateFilteredBenchmark
>  * IgniteSqlInsertIndexedValue1Benchmark
>  * IgniteSqlInsertIndexedValue2Benchmark
>  * IgniteSqlInsertIndexedValue8Benchmark



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


[jira] [Commented] (IGNITE-11977) Data streamer pool MXBean is registered as ThreadPoolMXBean instead of StripedExecutorMXBean

2019-10-09 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-11977:


{panel:title=Branch: [pull/6695/head] Base: [master] : Possible Blockers 
(16)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}PDS (Indexing){color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=4676430]]
* IgnitePdsWithIndexingCoreTestSuite: 
IgniteWalRecoveryTest.testWalBigObjectNodeCancel - Test has low fail rate in 
base branch 0,0% and is not flaky

{color:#d04437}Cache 2{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=4676416]]
* IgniteCacheTestSuite2: 
GridCacheAtomicNearReadersSelfTest.testTwoNodesTwoKeysNoBackups - Test has low 
fail rate in base branch 0,0% and is not flaky

{color:#d04437}MVCC Queries{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=4676400]]
* IgniteCacheMvccSqlTestSuite: 
CacheMvccPartitionedSqlTxQueriesTest.testAccountsTxDmlSql_WithRemoves_SingleNode_Persistence
 - Test has low fail rate in base branch 0,0% and is not flaky

{color:#d04437}Queries 1{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=4676442]]
* IgniteBinaryCacheQueryTestSuite: 
IndexingCachePartitionLossPolicySelfTest.testReadWriteSafeWithBackupsAfterKillCrd[TRANSACTIONAL]
 - Test has low fail rate in base branch 0,0% and is not flaky

{color:#d04437}MVCC PDS 2{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=4676460]]
* IgnitePdsMvccTestSuite2: IgniteNodeStoppedDuringDisableWALTest.test - History 
for base branch is absent.

{color:#d04437}MVCC PDS 4{color} [[tests 
2|https://ci.ignite.apache.org/viewLog.html?buildId=4676462]]
* IgnitePdsMvccTestSuite4: ResetLostPartitionTest.testResetLostPartitions - 
Test has low fail rate in base branch 0,0% and is not flaky
* IgnitePdsMvccTestSuite4: 
ResetLostPartitionTest.testReactivateGridBeforeResetLostPartitions - Test has 
low fail rate in base branch 0,0% and is not flaky

{color:#d04437}Cache 8{color} [[tests 
2|https://ci.ignite.apache.org/viewLog.html?buildId=4676422]]
* IgniteCacheTestSuite8: GridCacheRebalancingSyncSelfTest.testLoadRebalancing - 
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheTestSuite8: 
GridCacheRebalancingAsyncSelfTest.testComplexRebalancing - Test has low fail 
rate in base branch 0,0% and is not flaky

{color:#d04437}PDS 2{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=4676433]]
* IgnitePdsTestSuite2: IgniteNodeStoppedDuringDisableWALTest.test - New test 
duration 170s is more that 1 minute

{color:#d04437}MVCC Cache{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=4676398]]
* IgniteCacheMvccTestSuite: CacheMvccTransactionsTest.testNodesRestartNoHang - 
Test has low fail rate in base branch 0,0% and is not flaky

{color:#d04437}Queries 2{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=4676377]]
* IgniteBinaryCacheQueryTestSuite2: IgniteCacheQueriesLoadTest1.testQueries - 
New test duration 169s is more that 1 minute

{color:#d04437}MVCC Cache 7{color} [[tests 
2|https://ci.ignite.apache.org/viewLog.html?buildId=4676456]]
* IgniteCacheMvccTestSuite7: 
MvccCacheGroupMetricsMBeanTest.testCacheGroupMetrics - History for base branch 
is absent.
* IgniteCacheMvccTestSuite7: 
GridCacheRebalancingWithAsyncClearingMvccTest.testPartitionClearingNotBlockExchange
 - Test has low fail rate in base branch 0,0% and is not flaky

{color:#d04437}Cache (Restarts) 2{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=4676413]]
* IgniteCacheRestartTestSuite2: 
IgniteCacheGetRestartTest.testGetRestartPartitioned2 - Test has low fail rate 
in base branch 0,0% and is not flaky

{color:#d04437}[Licenses Headers]{color} [[tests 0 Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=4676403]]

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

> Data streamer pool MXBean is registered as ThreadPoolMXBean instead of 
> StripedExecutorMXBean
> 
>
> Key: IGNITE-11977
> URL: https://issues.apache.org/jira/browse/IGNITE-11977
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Stanislav Lukyanov
>Assignee: Ruslan Kamashev
>Priority: Major
> Fix For: 2.8
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Data streamer pool is registered with a ThreadPoolMXBean while it is actually 
> a StripedExecutor and can use a StripedExecutorMXBean.
> Need to change the registration in the IgniteKernal code. It should be 
> registered the same way as the striped executor pool.



--
This message was sent by 

[jira] [Commented] (IGNITE-12268) Adds possibility to set up custom REST processor.

2019-10-09 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12268:


{panel:title=Branch: [pull/6948/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4677911buildTypeId=IgniteTests24Java8_RunAll]

> Adds possibility to set up custom REST processor.
> -
>
> Key: IGNITE-12268
> URL: https://issues.apache.org/jira/browse/IGNITE-12268
> Project: Ignite
>  Issue Type: Improvement
>Reporter: PetrovMikhail
>Assignee: PetrovMikhail
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> It's needed to add ability to configure your own REST processor via 
> functionality of Ignite plugins.



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


[jira] [Commented] (IGNITE-12189) Implement correct limit for TextQuery

2019-10-09 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12189:


{panel:title=Branch: [pull/6917/head] Base: [master] : Possible Blockers 
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}PDS (Indexing){color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=4678107]]
* IgnitePdsWithIndexingCoreTestSuite: 
IgniteLogicalRecoveryTest.testRecoveryOnJoinToInactiveCluster - Test has low 
fail rate in base branch 0,0% and is not flaky

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

> Implement correct limit for TextQuery
> -
>
> Key: IGNITE-12189
> URL: https://issues.apache.org/jira/browse/IGNITE-12189
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Reporter: Yuriy Shuliha 
>Assignee: Yuriy Shuliha 
>Priority: Major
> Fix For: 2.8
>
>  Time Spent: 2h 40m
>  Remaining Estimate: 0h
>
> PROBLEM
> For now each server-node returns all response records to the client-node and 
> it may contain ~thousands, ~hundred thousands records.
>  Event if we need only first 10-100. Again, all the results are added to 
> queue in _*GridCacheQueryFutureAdapter*_ in arbitrary order by pages.
>  There are no any means to deliver deterministic result.
> SOLUTION
>  Implement _*limit*_ as parameter for _*TextQuery*_ and 
> _*GridCacheQueryRequest*_ 
>  It should be passed as limit  parameter in Lucene's  
> _*IndexSearcher.search()*_ in _*GridLuceneIndex*_.
> For distributed queries _*limit*_ will also trim response queue when merging 
> results.
> Type: long
>  Special value: : 0 -> No limit (Integer.MAX_VALUE);



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


[jira] [Commented] (IGNITE-12236) RepositoryFactorySupport#getQueryLookupStrategy no longer overriden in IgniteRepositoryFactory

2019-10-09 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12236:


{panel:title=Branch: [pull/6956/head] Base: [master] : Possible Blockers 
(4)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}ZooKeeper (Discovery) 1{color} [[tests 
2|https://ci.ignite.apache.org/viewLog.html?buildId=4677010]]
* ZookeeperDiscoverySpiTestSuite1: 
ZookeeperDiscoveryClientDisconnectTest.testStartNoServers_FailOnTimeout - Test 
has low fail rate in base branch 0,0% and is not flaky
* ZookeeperDiscoverySpiTestSuite1: 
ZookeeperDiscoveryClientDisconnectTest.testServersLeft_FailOnTimeout - Test has 
low fail rate in base branch 0,0% and is not flaky

{color:#d04437}Platform .NET (Core Linux){color} [[tests 0 Exit Code , 
TC_SERVICE_MESSAGE |https://ci.ignite.apache.org/viewLog.html?buildId=4677058]]

{color:#d04437}Cache 5{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=4677040]]
* IgniteCacheTestSuite5: 
IgniteCachePartitionLossPolicySelfTest.testReadWriteSafeAfterKillTwoNodesWithDelayWithPersistence[TRANSACTIONAL]
 - Test has low fail rate in base branch 0,0% and is not flaky

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

> RepositoryFactorySupport#getQueryLookupStrategy no longer overriden in 
> IgniteRepositoryFactory
> --
>
> Key: IGNITE-12236
> URL: https://issues.apache.org/jira/browse/IGNITE-12236
> Project: Ignite
>  Issue Type: Improvement
>  Components: spring
>Affects Versions: 2.8, 2.7.6
>Reporter: Thibaut
>Priority: Major
>  Labels: newbie, patch
> Fix For: 2.8
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Hello,
> org.apache.ignite.springdata20.repository.support.IgniteRepositoryFactory#getQueryLookupStrategy
> does not override 
> org.springframework.data.repository.core.support.RepositoryFactorySupport#getQueryLookupStrategy
> since this commit
> [https://github.com/spring-projects/spring-data-commons/commit/a6215fbe0f5c9a254cddacb12763737f2c286ad5]
>  
> this results in a thrown exception in 
> org.springframework.data.repository.core.support.RepositoryFactorySupport.QueryExecutorMethodInterceptor#QueryExecutorMethodInterceptor
>  
>  This prevents using ignite with any up to date version of spring. Fixing 
> this would require updating  that's the reason I'm 
> puting this as Improvement.



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


[jira] [Commented] (IGNITE-12261) Issue with adding nested index dynamically

2019-10-08 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12261:


{panel:title=Branch: [pull/6949/head] Base: [master] : Possible Blockers 
(3)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}PDS (Indexing){color} [[tests 0 TIMEOUT , Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=4674337]]

{color:#d04437}MVCC PDS 1{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=4674366]]
* IgnitePdsMvccTestSuite: 
IgnitePdsDataRegionMetricsTxTest.testMemoryUsageSingleNode - Test has low fail 
rate in base branch 0,0% and is not flaky

{color:#d04437}SPI (URI Deploy){color} [[tests 0 TIMEOUT , Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=4674290]]

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

>   Issue with adding nested index dynamically 
> -
>
> Key: IGNITE-12261
> URL: https://issues.apache.org/jira/browse/IGNITE-12261
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.7.6
>Reporter: Hemambara
>Assignee: Hemambara
>Priority: Major
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> [http://apache-ignite-users.70518.x6.nabble.com/Issue-with-adding-nested-index-dynamically-tt29571.html]
>  



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


[jira] [Commented] (IGNITE-10554) .NET: Jars are not copied to target dir under .NET Core

2019-10-08 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-10554:


{panel:title=Branch: [pull/6954/head] Base: [master] : Possible Blockers 
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 5{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=4674452]]
* IgniteCacheWithIndexingTestSuite: 
CacheRegisterMetadataLocallyTest.testClientFindsValueByAffinityKeyDynamicCacheWithoutExtraRequest
 - Test has low fail rate in base branch 0,0% and is not flaky

{color:#d04437}Activate / Deactivate Cluster{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=4674389]]
* IgniteStandByClusterSuite: 
IgniteClusterActivateDeactivateTest.testDeactivateSimple_5_Servers_5_Clients_FromClient
 - Test has low fail rate in base branch 0,0% and is not flaky

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

> .NET: Jars are not copied to target dir under .NET Core
> ---
>
> Key: IGNITE-10554
> URL: https://issues.apache.org/jira/browse/IGNITE-10554
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 2.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Critical
>  Labels: .NET
> Fix For: 2.8
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> We use PowerShell script to update post-build event in the target project and 
> copy jar files to target directory during build.
> However, this no longer works with .NET Core.
> nuspec file should be updated with new format, see example from 
> https://github.com/NuGet/Samples/blob/master/ContentFilesExample/authoring/ContentFilesExample.nuspec:
> {code}
> 
> 
>   
> ContentFilesExample
> 1.0.0
> nuget
> nuget
> false
> A content v2 example package.
> contentv2 contentFiles
> 
> 
> 
> 
> 
> 
>  copyToOutput="true" />
> 
>   
>  {code}
> *UPDATE: this breaks NuGet package usage completely under .NET Core 3.0*
> [NuGet behavior has 
> changed|https://docs.microsoft.com/en-us/dotnet/core/whats-new/dotnet-core-3-0#build-copies-dependencies]
>  in .NET Core 3.0:
> ??The dotnet build command now copies NuGet dependencies for your application 
> from the NuGet cache to the build output folder??
> In .NET Core 2.x dependencies are used directly from NuGet cache, so JAR 
> files are resolved.
> In 3.0 this does not work anymore, we should find a way to copy JAR files to 
> the output folder.
> Test cases:
> * .NET 4.x
> * .NET Core 2.x, 3.x Windows & Linux
> * LINQPad
> * Binary zip distribution (examples, .NET Core examples)



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


[jira] [Commented] (IGNITE-12192) visorcmd hangs if you ^D to quit

2019-10-08 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12192:


{panel:title=Branch: [pull/6877/head] Base: [master] : Possible Blockers 
(64)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 6{color} [[tests 0 Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=4674082]]

{color:#d04437}ZooKeeper (Discovery) 2{color} [[tests 
61|https://ci.ignite.apache.org/viewLog.html?buildId=4674052]]
* ZookeeperDiscoverySpiTestSuite2: 
GridCacheReplicatedMultiNodeFullApiSelfTest.testWithSkipStore - Test has low 
fail rate in base branch 0,0% and is not flaky
* ZookeeperDiscoverySpiTestSuite2: 
GridCacheReplicatedMultiNodeFullApiSelfTest.testLocalEvict - Test has low fail 
rate in base branch 0,0% and is not flaky
* ZookeeperDiscoverySpiTestSuite2: 
GridCacheReplicatedMultiNodeFullApiSelfTest.testPessimisticTxRepeatableReadOnUpdate
 - Test has low fail rate in base branch 0,0% and is not flaky
* ZookeeperDiscoverySpiTestSuite2: 
GridCacheReplicatedMultiNodeFullApiSelfTest.testGlobalClearKeysAsyncOld - Test 
has low fail rate in base branch 0,0% and is not flaky
* ZookeeperDiscoverySpiTestSuite2: 
GridCacheReplicatedMultiNodeFullApiSelfTest.testPessimisticTxRepeatableReadInTx 
- Test has low fail rate in base branch 0,0% and is not flaky
* ZookeeperDiscoverySpiTestSuite2: 
GridCacheReplicatedMultiNodeFullApiSelfTest.testWithSkipStoreTx - Test has low 
fail rate in base branch 0,0% and is not flaky
* ZookeeperDiscoverySpiTestSuite2: 
GridCacheReplicatedMultiNodeFullApiSelfTest.testReplace - Test has low fail 
rate in base branch 0,0% and is not flaky
* ZookeeperDiscoverySpiTestSuite2: 
GridCacheReplicatedMultiNodeFullApiSelfTest.testRemoveAllDuplicates - Test has 
low fail rate in base branch 0,0% and is not flaky
* ZookeeperDiscoverySpiTestSuite2: 
GridCacheReplicatedMultiNodeFullApiSelfTest.testPeekExpiredTx - Test has low 
fail rate in base branch 0,0% and is not flaky
* ZookeeperDiscoverySpiTestSuite2: 
GridCacheReplicatedMultiNodeFullApiSelfTest.testGetAndReplaceAsyncOld - Test 
has low fail rate in base branch 0,0% and is not flaky
* ZookeeperDiscoverySpiTestSuite2: 
GridCacheReplicatedMultiNodeFullApiSelfTest.testTransformAllPessimisticRepeatableRead
 - Test has low fail rate in base branch 0,0% and is not flaky
... and 50 tests blockers

{color:#d04437}Cache (Expiry Policy){color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=4674067]]
* IgniteCacheExpiryPolicyTestSuite: 
IgniteCacheAtomicExpiryPolicyTest.testCreateUpdate - Test has low fail rate in 
base branch 0,0% and is not flaky

{color:#d04437}Thin client: Node.js{color} [[tests 0 Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=4674055]]

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

> visorcmd hangs if you ^D to quit
> 
>
> Key: IGNITE-12192
> URL: https://issues.apache.org/jira/browse/IGNITE-12192
> Project: Ignite
>  Issue Type: Bug
>  Components: visor
>Affects Versions: 2.7.5
>Reporter: Stephen Darlington
>Assignee: Stephen Darlington
>Priority: Major
> Fix For: 2.8
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> You can exit most Unix utilities by pressing ^D. However, if you do that in 
> ignitevisorcmd when you're connected to a cluster, the process hangs. You 
> have to press ^C to quit. (It does work as expected if you close the 
> connection first.)



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


[jira] [Commented] (IGNITE-12182) ExecutorService is inconsistent with Compute and Services, runs on clients

2019-10-08 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12182:


{panel:title=Branch: [pull/6876/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4674012buildTypeId=IgniteTests24Java8_RunAll]

> ExecutorService is inconsistent with Compute and Services, runs on clients
> --
>
> Key: IGNITE-12182
> URL: https://issues.apache.org/jira/browse/IGNITE-12182
> Project: Ignite
>  Issue Type: Bug
>  Components: compute
>Affects Versions: 2.7.5
>Reporter: Stephen Darlington
>Assignee: Stephen Darlington
>Priority: Major
> Fix For: 2.8
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> In IGNITE-860 the default behaviour was changed so that compute and service 
> tasks would be executed only on server nodes. This is a sensible default and 
> it's confusing that it's not also true for jobs run using the ExecutorService.



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


[jira] [Commented] (IGNITE-12271) Persistence can't read pages from disk on Big Endian architectures

2019-10-08 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12271:


{panel:title=Branch: [pull/6953/head] Base: [master] : Possible Blockers 
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}PDS (Indexing){color} [[tests 0 Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=4673485]]

{color:#d04437}Basic 1{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=4673449]]
* IgniteBasicTestSuite: GridEventConsumeSelfTest.testEventsByFilter - Test has 
low fail rate in base branch 0,0% and is not flaky

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

> Persistence can't read pages from disk on Big Endian architectures
> --
>
> Key: IGNITE-12271
> URL: https://issues.apache.org/jira/browse/IGNITE-12271
> Project: Ignite
>  Issue Type: Bug
>  Components: persistence
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> So we are trying to start master on Big Endian, and we get the following 
> exceptions:
> {code}
> Runtime failure on row: Row@5bf1ee15[ snip, ver: GridCacheVersion 
> [topVer=180723326, order=1569259166164, nodeOrder=1] ][ 1307496, 32211, 3, 0 
> ]" [5-197]
> at 
> org.h2.message.DbException.getJdbcSQLException(DbException.java:357)
> ... 41 more
> Caused by: class 
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
>  Runtime failure on row: Row@5bf1ee15[ snip], ver: GridCacheVersion 
> [topVer=180723326, order=1569259166164, nodeOrder=1] ][ 1307496, 32211, 3, 0 ]
> at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doPut(BPlusTree.java:2320)
> at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.putx(BPlusTree.java:2267)
> at 
> org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.putx(H2TreeIndex.java:323)
> ... 38 more
> Caused by: java.lang.IllegalStateException: Failed to get page IO instance 
> (page content is corrupted)
> at 
> org.apache.ignite.internal.processors.cache.persistence.tree.io.IOVersions.forVersion(IOVersions.java:84)
> at 
> org.apache.ignite.internal.processors.cache.persistence.tree.io.IOVersions.forPage(IOVersions.java:96)
> at 
> org.apache.ignite.internal.processors.cache.persistence.CacheDataRowAdapter.initFromLink(CacheDataRowAdapter.java:153)
> at 
> org.apache.ignite.internal.processors.cache.persistence.CacheDataRowAdapter.initFromLink(CacheDataRowAdapter.java:107)
> at 
> org.apache.ignite.internal.processors.query.h2.database.H2RowFactory.getRow(H2RowFactory.java:61)
> at 
> org.apache.ignite.internal.processors.query.h2.database.H2Tree.createRowFromLink(H2Tree.java:221)
> at 
> org.apache.ignite.internal.processors.query.h2.database.io.AbstractH2ExtrasLeafIO.getLookupRow(AbstractH2ExtrasLeafIO.java:153)
> at 
> org.apache.ignite.internal.processors.query.h2.database.io.AbstractH2ExtrasLeafIO.getLookupRow(AbstractH2ExtrasLeafIO.java:35)
> {code}



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


[jira] [Commented] (IGNITE-12189) Implement correct limit for TextQuery

2019-10-08 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12189:


{panel:title=Branch: [pull/6917/head] Base: [master] : Possible Blockers 
(5)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Queries 1{color} [[tests 
2|https://ci.ignite.apache.org/viewLog.html?buildId=4661690]]
* IgniteBinaryCacheQueryTestSuite: 
BasicIndexMultinodeTest.testDynamicIndexesWithPersistenceIndexRebuild - Test 
has low fail rate in base branch 0,0% and is not flaky
* IgniteBinaryCacheQueryTestSuite: 
BasicIndexMultinodeTest.testAllIndexesWithPersistence - Test has low fail rate 
in base branch 0,0% and is not flaky

{color:#d04437}MVCC PDS 1{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=4661707]]
* IgnitePdsMvccTestSuite: 
IgniteClusterActivateDeactivateTestWithPersistence.testDeactivateSimple_5_Servers_5_Clients_FromClient
 - Test has low fail rate in base branch 0,0% and is not flaky

{color:#d04437}Thin client: PHP{color} [[tests 0 Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=4661649]]

{color:#d04437}[Check Code Style]{color} [[tests 0 Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=4661712]]

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

> Implement correct limit for TextQuery
> -
>
> Key: IGNITE-12189
> URL: https://issues.apache.org/jira/browse/IGNITE-12189
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Reporter: Yuriy Shuliha 
>Assignee: Yuriy Shuliha 
>Priority: Major
> Fix For: 2.8
>
>  Time Spent: 2h 40m
>  Remaining Estimate: 0h
>
> PROBLEM
> For now each server-node returns all response records to the client-node and 
> it may contain ~thousands, ~hundred thousands records.
>  Event if we need only first 10-100. Again, all the results are added to 
> queue in _*GridCacheQueryFutureAdapter*_ in arbitrary order by pages.
>  There are no any means to deliver deterministic result.
> SOLUTION
>  Implement _*limit*_ as parameter for _*TextQuery*_ and 
> _*GridCacheQueryRequest*_ 
>  It should be passed as limit  parameter in Lucene's  
> _*IndexSearcher.search()*_ in _*GridLuceneIndex*_.
> For distributed queries _*limit*_ will also trim response queue when merging 
> results.
> Type: long
>  Special value: : 0 -> No limit (Integer.MAX_VALUE);



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


[jira] [Commented] (IGNITE-12267) ClassCastException after change column type (drop, add)

2019-10-08 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12267:


{panel:title=Branch: [pull/6945/head] Base: [master] : Possible Blockers 
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 5{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=4670720]]
* IgniteCacheWithIndexingTestSuite: 
CacheRegisterMetadataLocallyTest.testClientFindsValueByAffinityKeyStaticCacheWithoutExtraRequest
 - Test has low fail rate in base branch 0,0% and is not flaky

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

> ClassCastException after change column type (drop, add)
> ---
>
> Key: IGNITE-12267
> URL: https://issues.apache.org/jira/browse/IGNITE-12267
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Kirill Tkalenko
>Assignee: Kirill Tkalenko
>Priority: Major
> Fix For: 2.8
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> SQL column type change is not present, but it is possible to delete and 
> create with a new type.
> The application of the migration script passes without errors.
> The error occurs whenever the column is accessed.



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


[jira] [Commented] (IGNITE-12214) Continuous query system view

2019-10-05 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12214:


{panel:title=Branch: [pull/6923/head] Base: [master] : Possible Blockers 
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}ZooKeeper (Discovery) 1{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=4663970]]
* ZookeeperDiscoverySpiTestSuite1: ZookeeperClientTest.testConnectionLoss2 - 
Test has low fail rate in base branch 0,0% and is not flaky

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

> Continuous query system view
> 
>
> Key: IGNITE-12214
> URL: https://issues.apache.org/jira/browse/IGNITE-12214
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
>  Labels: IEP-35, await
> Fix For: 2.8
>
>  Time Spent: 4h 40m
>  Remaining Estimate: 0h
>
> IGNITE-12145 finished
> We should add continuous query system views.



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


[jira] [Commented] (IGNITE-12255) Cache affinity fetching and calculation on client nodes may be broken in some cases

2019-10-04 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12255:


{panel:title=Branch: [pull/6933/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4658217buildTypeId=IgniteTests24Java8_RunAll]

> Cache affinity fetching and calculation on client nodes may be broken in some 
> cases
> ---
>
> Key: IGNITE-12255
> URL: https://issues.apache.org/jira/browse/IGNITE-12255
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.5, 2.7
>Reporter: Pavel Kovalenko
>Assignee: Pavel Kovalenko
>Priority: Critical
> Fix For: 2.8
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> We have a cluster with server and client nodes.
> We dynamically start several caches on a cluster.
> Periodically we create and destroy some temporary cache in a cluster to move 
> up cluster topology version.
> At the same time, a random client node chooses a random existing cache and 
> performs operations on that cache.
> It leads to an exception on client node that affinity is not initialized for 
> a cache during cache operation like:
> Affinity for topology version is not initialized [topVer = 8:10, head = 8:2]
> This exception means that the last affinity for a cache is calculated on 
> version [8,2]. This is a cache start version. It happens because during 
> creating/destroying some temporary cache we don’t re-calculate affinity for 
> all existing but not already accessed caches on client nodes. Re-calculate in 
> this case is cheap - we just copy affinity assignment and increment topology 
> version.
> As a solution, we need to fetch affinity on client node join for all caches. 
> Also, we need to re-calculate affinity for all affinity holders (not only for 
> started caches or only configured caches) for all topology events that 
> happened in a cluster on a client node.
> This solution showed the existing race between client node join and 
> concurrent cache destroy.
> The race is the following:
> Client node (with some configured caches) joins to a cluster sending 
> SingleMessage to coordinator during client PME. This SingleMessage contains 
> affinity fetch requests for all cluster caches. When SingleMessage is 
> in-flight server nodes finish client PME and also process and finish cache 
> destroy PME. When a cache is destroyed affinity for that cache is cleared. 
> When SingleMessage delivered to coordinator it doesn’t have affinity for a 
> requested cache because the cache is already destroyed. It leads to assertion 
> error on the coordinator and unpredictable behavior on the client node.
> The race may be fixed with the following change:
> If the coordinator doesn’t have an affinity for requested cache from the 
> client node, it doesn’t break PME with assertion error, just doesn’t send 
> affinity for that cache to a client node. When the client node receives 
> FullMessage and sees that affinity for some requested cache doesn’t exist, it 
> just closes cache proxy for user interactions which throws CacheStopped 
> exception for every attempt to use that cache. This is safe behavior because 
> cache destroy event should be happened on the client node soon and destroy 
> that cache completely.



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


[jira] [Commented] (IGNITE-12129) Upgrade spring-5.0.X and spring-data-2.0.X dependencies to latest versions

2019-10-04 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12129:


{panel:title=Branch: [pull/6935/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4660628buildTypeId=IgniteTests24Java8_RunAll]

> Upgrade spring-5.0.X and spring-data-2.0.X dependencies to latest versions
> --
>
> Key: IGNITE-12129
> URL: https://issues.apache.org/jira/browse/IGNITE-12129
> Project: Ignite
>  Issue Type: Wish
>  Components: spring
>Reporter: Pavel
>Assignee: Surkov Aleksandr
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> The actual spring version is 5.1.9.RELEASE, spring boot version is 
> 2.1.7.RELEASE
> In Ignite master branch spring versions are 5.0.8.RELEASE and 2.0.9.RELEASE



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


[jira] [Commented] (IGNITE-12254) IO errors during write header of WAL files in FSYNC mode should be handled by failure handler

2019-10-04 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12254:


{panel:title=Branch: [pull/6934/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4660105buildTypeId=IgniteTests24Java8_RunAll]

> IO errors during write header of WAL files in FSYNC mode should be handled by 
> failure handler
> -
>
> Key: IGNITE-12254
> URL: https://issues.apache.org/jira/browse/IGNITE-12254
> Project: Ignite
>  Issue Type: Bug
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Blocker
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Currently, such errors can hang the cluster.
> Reproducer:
> {code:java}
> @Test
> public void testWalFsyncIOError() throws Exception {
> cleanPersistenceDir();
> IgniteConfiguration cfg = new IgniteConfiguration();
> cfg.setCacheConfiguration(new 
> CacheConfiguration(DEFAULT_CACHE_NAME).setAtomicityMode(ATOMIC));
> cfg.setDataStorageConfiguration(
> new DataStorageConfiguration()
> .setDefaultDataRegionConfiguration(
> new DataRegionConfiguration()
> .setMaxSize(100L * 1024 * 1024)
> .setPersistenceEnabled(true))
> .setWalMode(WALMode.FSYNC)
> .setWalSegmentSize(512 * 1024)
> .setWalBufferSize(512 * 1024));
> IgniteEx ignite0 = startGrid(new 
> IgniteConfiguration(cfg).setIgniteInstanceName("ignite0"));
> IgniteEx ignite1 = startGrid(new 
> IgniteConfiguration(cfg).setIgniteInstanceName("ignite1"));
> ignite0.cluster().active(true);
> IgniteCache cache = ignite0.cache(DEFAULT_CACHE_NAME);
> for (int i = 0; i < 1_000; i++)
> cache.put(i, "Test value " + i);
> 
> ((FileWriteAheadLogManager)ignite1.context().cache().context().wal()).setFileIOFactory(new
>  FileIOFactory() {
> FileIOFactory delegateFactory = new RandomAccessFileIOFactory();
> @Override public FileIO create(File file, OpenOption... modes) 
> throws IOException {
> final FileIO delegate = delegateFactory.create(file, modes);
> return new FileIODecorator(delegate) {
> @Override public int write(ByteBuffer srcBuf) throws 
> IOException {
> throw new IOException("No space left on device");
> }
> };
> }
> });
> for (int i = 0; i < 2_000; i++)
> try {
> cache.put(i, "Test value " + i);
> }
> catch (Exception ignore) {
> }
> }
> {code}



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


[jira] [Commented] (IGNITE-12213) Sql objects system views

2019-10-04 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12213:


{panel:title=Branch: [pull/6916/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4660221buildTypeId=IgniteTests24Java8_RunAll]

> Sql objects system views
> 
>
> Key: IGNITE-12213
> URL: https://issues.apache.org/jira/browse/IGNITE-12213
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
>  Labels: IEP-35, await
> Fix For: 2.8
>
>  Time Spent: 3.5h
>  Remaining Estimate: 0h
>
> IGNITE-12145 finished
> We should add SQL objects system views.
> * Schemas
> * Tables
> * Indexes
> * SQL queries



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


[jira] [Commented] (IGNITE-11704) Write tombstones during rebalance to get rid of deferred delete buffer

2019-10-04 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-11704:


{panel:title=Branch: [pull/6931/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4657057buildTypeId=IgniteTests24Java8_RunAll]

> Write tombstones during rebalance to get rid of deferred delete buffer
> --
>
> Key: IGNITE-11704
> URL: https://issues.apache.org/jira/browse/IGNITE-11704
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Assignee: Pavel Kovalenko
>Priority: Major
>  Labels: rebalance
> Fix For: 2.8
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently Ignite relies on deferred delete buffer in order to handle 
> write-remove conflicts during rebalance. Given the limit size of the buffer, 
> this approach is fundamentally flawed, especially in case when persistence is 
> enabled.
> I suggest to extend the logic of data storage to be able to store key 
> tombstones - to keep version for deleted entries. The tombstones will be 
> stored when rebalance is in progress and should be cleaned up when rebalance 
> is completed.
> Later this approach may be used to implement fast partition rebalance based 
> on merkle trees (in this case, tombstones should be written on an incomplete 
> baseline).



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


[jira] [Commented] (IGNITE-6930) Optionally to do not write free list updates to WAL

2019-10-04 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-6930:
---

{panel:title=Branch: [pull/6893/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4654547buildTypeId=IgniteTests24Java8_RunAll]

> Optionally to do not write free list updates to WAL
> ---
>
> Key: IGNITE-6930
> URL: https://issues.apache.org/jira/browse/IGNITE-6930
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Reporter: Vladimir Ozerov
>Assignee: Aleksey Plekhanov
>Priority: Major
>  Labels: IEP-8, performance
> Fix For: 2.8
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> When cache entry is created, we need to write update the free list. When 
> entry is updated, we need to update free list(s) several times. Currently 
> free list is persistent structure, so every update to it must be logged to be 
> able to recover after crash. This may incur significant overhead, especially 
> for small entries.
> E.g. this is how WAL for a single update looks like. "D" - updates with real 
> data, "F" - free-list management:
> {code}
>  1. [D] DataRecord [writeEntries=[UnwrapDataEntry[k = key, v = [ BinaryObject 
> [idHash=2053299190, hash=1986931360, typeId=-1580729813]], super = [DataEntry 
> [cacheId=94416770, op=UPDATE, writeVer=GridCacheVersion [topVer=122147562, 
> order=1510667560607, nodeOrder=1], partId=0, partCnt=4, super=WALRecord 
> [size=0, chainSize=0, pos=null, type=DATA_RECORD]]
>  2. [F] PagesListRemovePageRecord [rmvdPageId=00010005, 
> pageId=00010006, grpId=94416770, super=PageDeltaRecord 
> [grpId=94416770, pageId=00010006, super=WALRecord [size=37, 
> chainSize=0, pos=null, type=PAGES_LIST_REMOVE_PAGE]]]
>  3. [D] DataPageInsertRecord [super=PageDeltaRecord [grpId=94416770, 
> pageId=00010005, super=WALRecord [size=129, chainSize=0, pos=null, 
> type=DATA_PAGE_INSERT_RECORD]]]
>  4. [F] PagesListAddPageRecord [dataPageId=00010005, 
> super=PageDeltaRecord [grpId=94416770, pageId=00010008, 
> super=WALRecord [size=37, chainSize=0, pos=null, type=PAGES_LIST_ADD_PAGE]]]
>  5. [F] DataPageSetFreeListPageRecord [freeListPage=281474976710664, 
> super=PageDeltaRecord [grpId=94416770, pageId=00010005, 
> super=WALRecord [size=37, chainSize=0, pos=null, 
> type=DATA_PAGE_SET_FREE_LIST_PAGE]]]
>  6. [D] ReplaceRecord [io=DataLeafIO[ver=1], idx=0, super=PageDeltaRecord 
> [grpId=94416770, pageId=00010004, super=WALRecord [size=47, 
> chainSize=0, pos=null, type=BTREE_PAGE_REPLACE]]]
>  7. [F] DataPageRemoveRecord [itemId=0, super=PageDeltaRecord 
> [grpId=94416770, pageId=00010005, super=WALRecord [size=30, 
> chainSize=0, pos=null, type=DATA_PAGE_REMOVE_RECORD]]]
>  8. [F] PagesListRemovePageRecord [rmvdPageId=00010005, 
> pageId=00010008, grpId=94416770, super=PageDeltaRecord 
> [grpId=94416770, pageId=00010008, super=WALRecord [size=37, 
> chainSize=0, pos=null, type=PAGES_LIST_REMOVE_PAGE]]]
>  9. [F] DataPageSetFreeListPageRecord [freeListPage=0, super=PageDeltaRecord 
> [grpId=94416770, pageId=00010005, super=WALRecord [size=37, 
> chainSize=0, pos=null, type=DATA_PAGE_SET_FREE_LIST_PAGE]]]
> 10. [F] PagesListAddPageRecord [dataPageId=00010005, 
> super=PageDeltaRecord [grpId=94416770, pageId=00010006, 
> super=WALRecord [size=37, chainSize=0, pos=null, type=PAGES_LIST_ADD_PAGE]]]
> 11. [F] DataPageSetFreeListPageRecord [freeListPage=281474976710662, 
> super=PageDeltaRecord [grpId=94416770, pageId=00010005, 
> super=WALRecord [size=37, chainSize=0, pos=null, 
> type=DATA_PAGE_SET_FREE_LIST_PAGE]]]
> {code}
> If you sum all space required for operation (size in p.3 is shown incorrectly 
> here), you will see that data update required ~300 bytes, so do free list 
> update! 
> *Proposed solution*
> 1) Optionally do not write free list updates to WAL
> 2) In case of node restart we start with empty free lists, so data inserts 
> will have to allocate new pages
> 3) When old data page is read, add it to the free list
> 4) Start a background thread which will iterate over all old data pages and 
> re-create the free list, so that eventually all data pages are tracked.



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


[jira] [Commented] (IGNITE-12250) Adds REST requests processing logging.

2019-10-03 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12250:


{panel:title=Branch: [pull/6928/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4656414buildTypeId=IgniteTests24Java8_RunAll]

> Adds REST requests processing logging.
> --
>
> Key: IGNITE-12250
> URL: https://issues.apache.org/jira/browse/IGNITE-12250
> Project: Ignite
>  Issue Type: Improvement
>Reporter: PetrovMikhail
>Assignee: PetrovMikhail
>Priority: Major
>  Time Spent: 2h 10m
>  Remaining Estimate: 0h
>
> It's needed to add logging of each REST request processing result including 
> errors. 



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


[jira] [Commented] (IGNITE-12181) Rebalance hangs on BLT change on cluster with in-memory regions

2019-10-03 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12181:


{panel:title=Branch: [pull/6929/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4654959buildTypeId=IgniteTests24Java8_RunAll]

> Rebalance hangs on BLT change on cluster with in-memory regions
> ---
>
> Key: IGNITE-12181
> URL: https://issues.apache.org/jira/browse/IGNITE-12181
> Project: Ignite
>  Issue Type: Bug
>Reporter: Maxim Muzafarov
>Assignee: Pavel Pereslegin
>Priority: Blocker
> Fix For: 2.8
>
> Attachments: RebalanceInMemoryWithPersistence.java
>
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> # Configured BLT on the _node-1_ (cluster activated)
> # Configured in-memory region with a single cache on the _node-1_
> # A new _node-2_  join to the cluster
> # Set new BLT based on two nodes
> # Rebalance hangs
> Reproducer attached.



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


[jira] [Commented] (IGNITE-12181) Rebalance hangs on BLT change on cluster with in-memory regions

2019-10-02 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12181:


{panel:title=Branch: [pull/6929/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4653528buildTypeId=IgniteTests24Java8_RunAll]

> Rebalance hangs on BLT change on cluster with in-memory regions
> ---
>
> Key: IGNITE-12181
> URL: https://issues.apache.org/jira/browse/IGNITE-12181
> Project: Ignite
>  Issue Type: Bug
>Reporter: Maxim Muzafarov
>Assignee: Pavel Pereslegin
>Priority: Blocker
> Fix For: 2.8
>
> Attachments: RebalanceInMemoryWithPersistence.java
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> # Configured BLT on the _node-1_ (cluster activated)
> # Configured in-memory region with a single cache on the _node-1_
> # A new _node-2_  join to the cluster
> # Set new BLT based on two nodes
> # Rebalance hangs
> Reproducer attached.



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


[jira] [Commented] (IGNITE-12209) Transaction system view

2019-10-01 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12209:


{panel:title=Branch: [pull/6896/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4650342buildTypeId=IgniteTests24Java8_RunAll]

> Transaction system view
> ---
>
> Key: IGNITE-12209
> URL: https://issues.apache.org/jira/browse/IGNITE-12209
> Project: Ignite
>  Issue Type: Sub-task
>Affects Versions: 2.7.6
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
>  Labels: IEP-35
> Fix For: 2.8
>
>  Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> IGNITE-12145 finished
> We should add transactions to the system views.



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


[jira] [Commented] (IGNITE-12238) RobinHoodBackwardShiftHashMap works incorrectly on big endian architectures

2019-09-30 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12238:


{panel:title=Branch: [pull/6921/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4641839buildTypeId=IgniteTests24Java8_RunAll]

> RobinHoodBackwardShiftHashMap works incorrectly on big endian architectures
> ---
>
> Key: IGNITE-12238
> URL: https://issues.apache.org/jira/browse/IGNITE-12238
> Project: Ignite
>  Issue Type: Bug
>Reporter: Andrey N. Gura
>Assignee: Andrey N. Gura
>Priority: Major
> Fix For: 2.8
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> {{RobinHoodBackwardShiftHashMap}} has bug that can be reproduced only on big 
> endinan architectures. In order to reproduce the problem run the following 
> tests:
> * {{RobinHoodBackwardShiftHashMapTest.testCollisionOnRemove}}
> * {{testRandomOpsPutRemove}}
> The problem is {{setIdealBucket()}} method writes {{long}} value to the 
> offheap memory, while {{getIdealBucket()}} reads {{int}} value. For little 
> endian architectures it works because meaningful 4 bytes will written first  
> to the memory and leading zero bytes will be rewriteen by the next operation. 
> On big endian architecture always 4 zero bytes will be written to the memory.



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


[jira] [Commented] (IGNITE-12232) NPE while node join processing

2019-09-30 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12232:


{panel:title=Branch: [pull/6911/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4635678buildTypeId=IgniteTests24Java8_RunAll]

> NPE while node join processing
> --
>
> Key: IGNITE-12232
> URL: https://issues.apache.org/jira/browse/IGNITE-12232
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.7.6
>Reporter: PetrovMikhail
>Assignee: Ryabov Dmitrii
>Priority: Major
> Fix For: 2.8
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> ServerImpl.RingMessageWorker#processNodeAddedMessage method throws npe 
> exception in case DiscoverySpiNodeAuthenticator#authenticateNode returns null.



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


[jira] [Commented] (IGNITE-11976) @SpringResource is silently ignored if no Spring context is provided

2019-09-28 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-11976:


{panel:title=Branch: [pull/6868/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *- Run :: Cache* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4644282buildTypeId=IgniteTests24Java8_RunCache]

> @SpringResource is silently ignored if no Spring context is provided
> 
>
> Key: IGNITE-11976
> URL: https://issues.apache.org/jira/browse/IGNITE-11976
> Project: Ignite
>  Issue Type: Improvement
>  Components: spring
>Affects Versions: 2.7
>Reporter: Stanislav Lukyanov
>Assignee: kcheng.mvp
>Priority: Major
>  Labels: newbie
>
> @SpringResource annotation is silently ignored and the annotated field is 
> null if Spring context.
> For @SpringResource to work the node needs to be started with 
> IgniteSpring::start instead of Ignition::start, but the user may not know 
> that.
> Need to add a warning for this.



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


[jira] [Commented] (IGNITE-11976) @SpringResource is silently ignored if no Spring context is provided

2019-09-28 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-11976:


{panel:title=Branch: [pull/6868/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4638685buildTypeId=IgniteTests24Java8_RunAll]

> @SpringResource is silently ignored if no Spring context is provided
> 
>
> Key: IGNITE-11976
> URL: https://issues.apache.org/jira/browse/IGNITE-11976
> Project: Ignite
>  Issue Type: Improvement
>  Components: spring
>Affects Versions: 2.7
>Reporter: Stanislav Lukyanov
>Assignee: kcheng.mvp
>Priority: Major
>  Labels: newbie
>
> @SpringResource annotation is silently ignored and the annotated field is 
> null if Spring context.
> For @SpringResource to work the node needs to be started with 
> IgniteSpring::start instead of Ignition::start, but the user may not know 
> that.
> Need to add a warning for this.



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


[jira] [Commented] (IGNITE-11992) Improvements for new security approach

2019-09-27 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-11992:


{panel:title=Branch: [pull/6918/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4639369buildTypeId=IgniteTests24Java8_RunAll]

> Improvements for new security approach
> --
>
> Key: IGNITE-11992
> URL: https://issues.apache.org/jira/browse/IGNITE-11992
> Project: Ignite
>  Issue Type: Improvement
>  Components: security
>Affects Versions: 2.8
>Reporter: Stepachev Maksim
>Assignee: Stepachev Maksim
>Priority: Major
> Fix For: 2.8
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> 1. The visor tasks lost permission. 
>  The method VisorQueryUtils#scheduleQueryStart makes a new thread and loses 
> context.
>  3. The GridRestProcessor does tasks outside "withContext" section. As result 
> context loses.
>  4. The GridRestProcessor isn't client, we can't read security subject from 
> node attribute. 
>  We should transmit secCtx for fake nodes and secSubjId for real.



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


[jira] [Commented] (IGNITE-12230) Partition eviction during cache stop / deactivation may cause errors leading to node failure and storage corruption

2019-09-27 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12230:


{panel:title=Branch: [pull/6906/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4633004buildTypeId=IgniteTests24Java8_RunAll]

> Partition eviction during cache stop / deactivation may cause errors leading 
> to node failure and storage corruption
> ---
>
> Key: IGNITE-12230
> URL: https://issues.apache.org/jira/browse/IGNITE-12230
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Stepachev Maksim
>Assignee: Stepachev Maksim
>Priority: Major
> Fix For: 2.8
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> PartitionEvictionTask may produce NullPointerException if cache / cache group 
> / cluser is stopping / deactivating.
>  



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


[jira] [Commented] (IGNITE-12231) RollbackRecord's must be flushed after logging to WAL

2019-09-26 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12231:


{panel:title=Branch: [pull/6908/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4633828buildTypeId=IgniteTests24Java8_RunAll]

> RollbackRecord's must be flushed after logging to WAL
> -
>
> Key: IGNITE-12231
> URL: https://issues.apache.org/jira/browse/IGNITE-12231
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Andrey N. Gura
>Assignee: Andrey N. Gura
>Priority: Major
> Fix For: 2.8
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Every record or records batch logged to WAL must call {{wal().flush()}} in 
> order to save data on storage device.
> {{TxPartitionCounterStateOnePrimaryTwoBackupsHistoryRebalanceTest.testPartialPrepare_2TX_1_1}}
>  test fails periodically with disabled MMAP.



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


[jira] [Commented] (IGNITE-11008) JDBC Metadata: redundant spaces IS_GENERATEDCOLUMN & BUFFER_LENGTH

2019-09-26 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-11008:


{panel:title=Branch: [pull/6885/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4634670buildTypeId=IgniteTests24Java8_RunAll]

> JDBC Metadata: redundant spaces IS_GENERATEDCOLUMN & BUFFER_LENGTH
> --
>
> Key: IGNITE-11008
> URL: https://issues.apache.org/jira/browse/IGNITE-11008
> Project: Ignite
>  Issue Type: Bug
>  Components: jdbc
>Affects Versions: 2.7
>Reporter: Stepan Pilschikov
>Assignee: kcheng.mvp
>Priority: Minor
> Fix For: 2.8
>
>
> Found redundant spaces in 
> org.apache.ignite.internal.jdbc.thin.JdbcThinDatabaseMetadata#getColumns
> "IS_GENERATEDCOLUMN "
> "BUFFER_LENGTH "



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


[jira] [Commented] (IGNITE-12108) [IEP-35] Migrate Communication Metrics.

2019-09-26 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12108:


{panel:title=Branch: [pull/6814/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4634554buildTypeId=IgniteTests24Java8_RunAll]

> [IEP-35] Migrate Communication Metrics.
> ---
>
> Key: IGNITE-12108
> URL: https://issues.apache.org/jira/browse/IGNITE-12108
> Project: Ignite
>  Issue Type: New Feature
>Reporter: Ivan Bessonov
>Assignee: Ivan Bessonov
>Priority: Major
>  Labels: IEP-35
> Fix For: 2.8
>
>  Time Spent: 3h 50m
>  Remaining Estimate: 0h
>
> ||*Name*||*Description*||
> |communication.tcp.outboundMessagesQueueSize|Number of messages waiting to be 
> sent|
> |communication.tcp.sentBytes|Total number of bytes received by current node|
> |communication.tcp.receivedBytes|Total number of bytes sent by current node|
> |communication.tcp.sentMessagesCount|Total number of messages sent by current 
> node|
> |communication.tcp.receivedMessagesCount|Total number of messages received by 
> current node|
> |communication.tcp.sentMessagesByType.|Total number of messages 
> with given type sent by current node|
> |communication.tcp.receivedMessagesByType.|Total number of 
> messages with given type received by current node|
> |communication.tcp..sentMessagesToNode|Total number of messages sent 
> by current node to the given node|
> |communication.tcp..receivedMessagesFromNode|Total number of messages 
> received by current node from the given node|
>  



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


[jira] [Commented] (IGNITE-11094) Add SSL support for ignite zookeeper SPI

2019-09-26 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-11094:


{panel:title=Branch: [pull/6910/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4634438buildTypeId=IgniteTests24Java8_RunAll]

> Add SSL support for ignite zookeeper SPI
> 
>
> Key: IGNITE-11094
> URL: https://issues.apache.org/jira/browse/IGNITE-11094
> Project: Ignite
>  Issue Type: Improvement
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Assignee: Ryabov Dmitrii
>Priority: Major
> Fix For: 2.8
>
>  Time Spent: 6h 50m
>  Remaining Estimate: 0h
>
> ZK 3.5.4-beta is already supporting SSL [1]. We should add SSL support to ZK 
> server connections  if Zookeeper SPI used.
> 1. 
> https://cwiki.apache.org/confluence/display/ZOOKEEPER/ZooKeeper+SSL+User+Guide



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


[jira] [Commented] (IGNITE-12220) Allow to use cache-related permissions both at system and per-cache levels

2019-09-26 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12220:


{panel:title=Branch: [pull/6904/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4637637buildTypeId=IgniteTests24Java8_RunAll]

> Allow to use cache-related permissions both at system and per-cache levels
> --
>
> Key: IGNITE-12220
> URL: https://issues.apache.org/jira/browse/IGNITE-12220
> Project: Ignite
>  Issue Type: Task
>  Components: security
>Affects Versions: 2.7.6
>Reporter: Andrey Kuznetsov
>Assignee: Sergei Ryzhov
>Priority: Major
> Fix For: 2.8
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Currently, {{CACHE_CREATE}} and {{CACHE_DESTROY}} permissions are enforced to 
> be system-level permissions, see for instance 
> {{SecurityPermissionSetBuilder#appendCachePermissions}}. This looks 
> inflexible: Ignite Security implementations are not able to manage cache 
> creation and deletion permissions on per-cache basis (unlike get/put/remove 
> permissions). All such limitations should be found and removed in order to 
> allow all {{CACHE_*}} permissions to be set both at system and per-cache 
> levels.



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


[jira] [Commented] (IGNITE-12220) Allow to use cache-related permissions both at system and per-cache levels

2019-09-26 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12220:


{panel:title=Branch: [pull/6904/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4637637buildTypeId=IgniteTests24Java8_RunAll]

> Allow to use cache-related permissions both at system and per-cache levels
> --
>
> Key: IGNITE-12220
> URL: https://issues.apache.org/jira/browse/IGNITE-12220
> Project: Ignite
>  Issue Type: Task
>  Components: security
>Affects Versions: 2.7.6
>Reporter: Andrey Kuznetsov
>Assignee: Sergei Ryzhov
>Priority: Major
> Fix For: 2.8
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Currently, {{CACHE_CREATE}} and {{CACHE_DESTROY}} permissions are enforced to 
> be system-level permissions, see for instance 
> {{SecurityPermissionSetBuilder#appendCachePermissions}}. This looks 
> inflexible: Ignite Security implementations are not able to manage cache 
> creation and deletion permissions on per-cache basis (unlike get/put/remove 
> permissions). All such limitations should be found and removed in order to 
> allow all {{CACHE_*}} permissions to be set both at system and per-cache 
> levels.



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


[jira] [Commented] (IGNITE-12220) Allow to use cache-related permissions both at system and per-cache levels

2019-09-26 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12220:


{panel:title=Branch: [pull/6904/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4637637buildTypeId=IgniteTests24Java8_RunAll]

> Allow to use cache-related permissions both at system and per-cache levels
> --
>
> Key: IGNITE-12220
> URL: https://issues.apache.org/jira/browse/IGNITE-12220
> Project: Ignite
>  Issue Type: Task
>  Components: security
>Affects Versions: 2.7.6
>Reporter: Andrey Kuznetsov
>Assignee: Sergei Ryzhov
>Priority: Major
> Fix For: 2.8
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Currently, {{CACHE_CREATE}} and {{CACHE_DESTROY}} permissions are enforced to 
> be system-level permissions, see for instance 
> {{SecurityPermissionSetBuilder#appendCachePermissions}}. This looks 
> inflexible: Ignite Security implementations are not able to manage cache 
> creation and deletion permissions on per-cache basis (unlike get/put/remove 
> permissions). All such limitations should be found and removed in order to 
> allow all {{CACHE_*}} permissions to be set both at system and per-cache 
> levels.



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


[jira] [Commented] (IGNITE-12220) Allow to use cache-related permissions both at system and per-cache levels

2019-09-26 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12220:


{panel:title=Branch: [pull/6904/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4637637buildTypeId=IgniteTests24Java8_RunAll]

> Allow to use cache-related permissions both at system and per-cache levels
> --
>
> Key: IGNITE-12220
> URL: https://issues.apache.org/jira/browse/IGNITE-12220
> Project: Ignite
>  Issue Type: Task
>  Components: security
>Affects Versions: 2.7.6
>Reporter: Andrey Kuznetsov
>Assignee: Sergei Ryzhov
>Priority: Major
> Fix For: 2.8
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Currently, {{CACHE_CREATE}} and {{CACHE_DESTROY}} permissions are enforced to 
> be system-level permissions, see for instance 
> {{SecurityPermissionSetBuilder#appendCachePermissions}}. This looks 
> inflexible: Ignite Security implementations are not able to manage cache 
> creation and deletion permissions on per-cache basis (unlike get/put/remove 
> permissions). All such limitations should be found and removed in order to 
> allow all {{CACHE_*}} permissions to be set both at system and per-cache 
> levels.



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


[jira] [Commented] (IGNITE-10113) Failure during build index isn't handled by failure handler

2019-09-26 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-10113:


{panel:title=Branch: [pull/6801/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4601030buildTypeId=IgniteTests24Java8_RunAll]

> Failure during build index isn't handled by failure handler
> ---
>
> Key: IGNITE-10113
> URL: https://issues.apache.org/jira/browse/IGNITE-10113
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Sergey Antonov
>Assignee: Ivan Bessonov
>Priority: Major
> Fix For: 2.8
>
> Attachments: StopNodeOnRebuildIndexFailureTest.java
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> If exception will be thrown during index build, failure handler doesn't 
> handle this exception. 



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


[jira] [Commented] (IGNITE-12234) .NET: Fix flaky tests

2019-09-25 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12234:


{panel:title=Branch: [pull/6914/head] Base: [master] : Possible Blockers 
(5)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 6{color} [[tests 0 Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=4635513]]

{color:#d04437}RDD{color} [[tests 0 Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=4635469]]

{color:#d04437}Cache 2{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=4635509]]
* IgniteCacheTestSuite2: 
GridCachePartitionedEvictionSelfTest.testEvictionTxOptimisticRepeatableRead - 
Test has low fail rate in base branch 0,0% and is not flaky

{color:#d04437}Cassandra Store{color} [[tests 
2|https://ci.ignite.apache.org/viewLog.html?buildId=4635556]]
* IgniteCassandraStoreTestSuite: 
CassandraDirectPersistenceTest.pojoStrategyTest - Test has low fail rate in 
base branch 0,0% and is not flaky
* IgniteCassandraStoreTestSuite: 
CassandraDirectPersistenceTest.pojoStrategyTransactionTest - Test has low fail 
rate in base branch 0,0% and is not flaky

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

> .NET: Fix flaky tests
> -
>
> Key: IGNITE-12234
> URL: https://issues.apache.org/jira/browse/IGNITE-12234
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
>  Labels: .NET
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Known flaky tests:
> * CacheTestSsl.TestAsyncCompletionOrder
> * DataStorageMetricsTest.TestDataStorageMetrics
> * PersistenceTest.TestBaselineTopology
> * CancellationTest.TestTask



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


[jira] [Commented] (IGNITE-9638) .NET: JVM keeps track of CLR Threads, even when they are finished

2019-09-25 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-9638:
---

{panel:title=Branch: [pull/6912/head] Base: [master] : Possible Blockers 
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 6{color} [[tests 0 Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=4635271]]

{color:#d04437}Client Nodes{color} [[tests 0 TIMEOUT , Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=4635208]]

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

> .NET: JVM keeps track of CLR Threads, even when they are finished 
> --
>
> Key: IGNITE-9638
> URL: https://issues.apache.org/jira/browse/IGNITE-9638
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 2.6
>Reporter: Ilya Kasnacheev
>Assignee: Pavel Tupitsyn
>Priority: Major
>  Labels: .NET
> Fix For: 2.8
>
> Attachments: IgniteRepro.zip
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> When you create a Thread in C#, JVM creates corresponding thread 
> "Thread-" which is visible in jstack. When C# joins this thread, it is 
> not removed from JVM and is kept around. This means that jstack may show 
> thousands of threads which are not there. Reproducer is attached. It is 
> presumed that memory will be exhausted eventually.



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


[jira] [Commented] (IGNITE-10113) Failure during build index isn't handled by failure handler

2019-09-25 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-10113:


{panel:title=Branch: [pull/6801/head] Base: [master] : Possible Blockers 
(4)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}MVCC PDS 4{color} [[tests 
2|https://ci.ignite.apache.org/viewLog.html?buildId=4633590]]
* IgnitePdsMvccTestSuite4: ResetLostPartitionTest.testResetLostPartitions - 
Test has low fail rate in base branch 0,0% and is not flaky
* IgnitePdsMvccTestSuite4: 
ResetLostPartitionTest.testReactivateGridBeforeResetLostPartitions - Test has 
low fail rate in base branch 0,0% and is not flaky

{color:#d04437}Cache 8{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=4633592]]
* IgniteCacheTestSuite8: 
GridCacheRebalancingAsyncSelfTest.testComplexRebalancing - Test has low fail 
rate in base branch 0,0% and is not flaky

{color:#d04437}MVCC Cache 7{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=4633594]]
* IgniteCacheMvccTestSuite7: 
GridCacheRebalancingWithAsyncClearingMvccTest.testPartitionClearingNotBlockExchange
 - Test has low fail rate in base branch 0,0% and is not flaky

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

> Failure during build index isn't handled by failure handler
> ---
>
> Key: IGNITE-10113
> URL: https://issues.apache.org/jira/browse/IGNITE-10113
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Sergey Antonov
>Assignee: Ivan Bessonov
>Priority: Major
> Fix For: 2.8
>
> Attachments: StopNodeOnRebuildIndexFailureTest.java
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> If exception will be thrown during index build, failure handler doesn't 
> handle this exception. 



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


[jira] [Commented] (IGNITE-11976) @SpringResource is silently ignored if no Spring context is provided

2019-09-25 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-11976:


{panel:title=Branch: [pull/6868/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4617661buildTypeId=IgniteTests24Java8_RunAll]

> @SpringResource is silently ignored if no Spring context is provided
> 
>
> Key: IGNITE-11976
> URL: https://issues.apache.org/jira/browse/IGNITE-11976
> Project: Ignite
>  Issue Type: Improvement
>  Components: spring
>Affects Versions: 2.7
>Reporter: Stanislav Lukyanov
>Assignee: kcheng.mvp
>Priority: Major
>  Labels: newbie
>
> @SpringResource annotation is silently ignored and the annotated field is 
> null if Spring context.
> For @SpringResource to work the node needs to be started with 
> IgniteSpring::start instead of Ignition::start, but the user may not know 
> that.
> Need to add a warning for this.



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


[jira] [Commented] (IGNITE-12197) Incorrect way for getting value of persistent enabled in CacheGroupMetricsImpl

2019-09-25 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12197:


{panel:title=Branch: [pull/6879/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4629976buildTypeId=IgniteTests24Java8_RunAll]

> Incorrect way for getting value of persistent enabled in CacheGroupMetricsImpl
> --
>
> Key: IGNITE-12197
> URL: https://issues.apache.org/jira/browse/IGNITE-12197
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Andrey Gura
>Assignee: Andrey Gura
>Priority: Minor
>  Labels: IEP-35
> Fix For: 2.8
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> IGNITE-12027 introduces possible bug  due to incorrect way for getting value 
> of persistent enabled property in {{CacheGroupMetricsImpl}}



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


[jira] [Commented] (IGNITE-12211) Client connections system view

2019-09-25 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12211:


{panel:title=Branch: [pull/6898/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4630626buildTypeId=IgniteTests24Java8_RunAll]

> Client connections system view
> --
>
> Key: IGNITE-12211
> URL: https://issues.apache.org/jira/browse/IGNITE-12211
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
>  Labels: IEP-35
> Fix For: 2.8
>
>  Time Spent: 2h
>  Remaining Estimate: 0h
>
> IGNITE-12145 finished
> We should add client connections to the system views.
> System view should track JDBC, ODBC and thin connections.



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


[jira] [Commented] (IGNITE-12226) Improve BinaryObjectException message

2019-09-25 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12226:


{panel:title=Branch: [pull/6903/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4630381buildTypeId=IgniteTests24Java8_RunAll]

> Improve BinaryObjectException message
> -
>
> Key: IGNITE-12226
> URL: https://issues.apache.org/jira/browse/IGNITE-12226
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Kirill Tkalenko
>Assignee: Kirill Tkalenko
>Priority: Major
> Fix For: 2.8
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> We are getting the following exception in case of different type IDs:
> {noformat}
> org.apache.ignite.binary.BinaryObjectException: Failed to get field because 
> type ID of passed object differs from type ID this BinaryField belongs to 
> [expected=-635374417, actual=1778229603]
>  at 
> org.apache.ignite.internal.binary.BinaryFieldImpl.fieldOrder(BinaryFieldImpl.java:287)
>  at 
> org.apache.ignite.internal.binary.BinaryFieldImpl.value(BinaryFieldImpl.java:109)
>  at 
> org.apache.ignite.internal.processors.query.property.QueryBinaryProperty.fieldValue(QueryBinaryProperty.java:220)
>  at 
> org.apache.ignite.internal.processors.query.property.QueryBinaryProperty.value(QueryBinaryProperty.java:116)
>  at 
> org.apache.ignite.internal.processors.query.h2.opt.GridH2RowDescriptor.columnValue(GridH2RowDescriptor.java:331)
>  at 
> org.apache.ignite.internal.processors.query.h2.opt.GridH2KeyValueRowOnheap.getValue0(GridH2KeyValueRowOnheap.java:122)
>  at 
> org.apache.ignite.internal.processors.query.h2.opt.GridH2KeyValueRowOnheap.getValue(GridH2KeyValueRowOnheap.java:106)
>  at 
> org.apache.ignite.internal.processors.query.h2.database.H2Tree.compare(H2Tree.java:350)
>  at 
> org.apache.ignite.internal.processors.query.h2.database.H2Tree.compare(H2Tree.java:56)
>  at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.compare(BPlusTree.java:4614)
>  at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.findInsertionPoint(BPlusTree.java:4534)
>  at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.access$1300(BPlusTree.java:92)
>  at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Search.run0(BPlusTree.java:296)
>  at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$GetPageHandler.run(BPlusTree.java:4967)
>  at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Search.run(BPlusTree.java:276)
>  at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$GetPageHandler.run(BPlusTree.java:4952)
>  at 
> org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.readPage(PageHandler.java:161)
>  at 
> org.apache.ignite.internal.processors.cache.persistence.DataStructure.read(DataStructure.java:348)
>  at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.putDown(BPlusTree.java:2450)
>  at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doPut(BPlusTree.java:2203)
> {noformat}
> This message isn't informative. We should print more detailes about types, 
> for example classname, class structure (if applicable), which field in class 
> we tried to read.



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


[jira] [Commented] (IGNITE-11312) JDBC: Thin driver doesn't reports incorrect property names

2019-09-25 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-11312:


{panel:title=Branch: [pull/6900/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4632091buildTypeId=IgniteTests24Java8_RunAll]

> JDBC: Thin driver doesn't reports incorrect property names
> --
>
> Key: IGNITE-11312
> URL: https://issues.apache.org/jira/browse/IGNITE-11312
> Project: Ignite
>  Issue Type: Improvement
>  Components: jdbc
>Reporter: Stanislav Lukyanov
>Assignee: Suraj Singh
>Priority: Major
>  Labels: newbie
> Fix For: 2.8
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> JDBC driver reports the properties it supports via getPropertyInfo method. It 
> currently reports the property names as simple strings, like 
> "enforceJoinOrder". However, when the properties are processed on connect 
> they are looked up with prefix "ignite.jdbc", e.g. 
> "ignite.jdbc.enforceJoinOrder".
> Because of this UI tools like DBeaver can't properly pass the properties to 
> Ignite. For example, when "enforceJoinOrder" is set to true in "Connection 
> settings" -> "Driver properties" menu of DBeaver it has no effect.



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


[jira] [Commented] (IGNITE-11949) Yardstick benchmarks for WAL page snapshot compression

2019-09-24 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-11949:


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

> Yardstick benchmarks for WAL page snapshot compression
> --
>
> Key: IGNITE-11949
> URL: https://issues.apache.org/jira/browse/IGNITE-11949
> Project: Ignite
>  Issue Type: Improvement
>  Components: yardstick
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
>  Labels: iep-20, yardstick
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> WAL page snapshots compression (implemented by IGNITE-11336) can be enabled 
> by modifying config.xml file. It will be better to configure benchmarks by 
> command line options.
> Also, some new probes (WAL size for example) can be added.



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


[jira] [Commented] (IGNITE-12206) Partition state validation warns are not printed to log

2019-09-24 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12206:


{panel:title=Branch: [pull/6888/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4617294buildTypeId=IgniteTests24Java8_RunAll]

> Partition state validation warns are not printed to log
> ---
>
> Key: IGNITE-12206
> URL: https://issues.apache.org/jira/browse/IGNITE-12206
> Project: Ignite
>  Issue Type: Bug
>Reporter: Stepachev Maksim
>Assignee: Stepachev Maksim
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> GridDhtPartitionsExchangeFuture.java
>  
> {code:java}
>  if (grpCtx == null
> || grpCtx.config().isReadThrough()
> || grpCtx.config().isWriteThrough()
> || grpCtx.config().getCacheStoreFactory() != null
> || grpCtx.config().getRebalanceDelay() == -1
> || grpCtx.config().getRebalanceMode() == 
> CacheRebalanceMode.NONE
> || grpCtx.config().getExpiryPolicyFactory() == null
> || SKIP_PARTITION_SIZE_VALIDATION)
> return null;{code}
>  
> Looks like a typo, probably it should be 
> grpCtx.config().getExpiryPolicyFactory() != null



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


[jira] [Commented] (IGNITE-12203) Rebalance is loading partitions already loading after cancellation without WAL

2019-09-23 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12203:


{panel:title=Branch: [pull/6892/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4618218buildTypeId=IgniteTests24Java8_RunAll]

> Rebalance is loading partitions already loading after cancellation without WAL
> --
>
> Key: IGNITE-12203
> URL: https://issues.apache.org/jira/browse/IGNITE-12203
> Project: Ignite
>  Issue Type: Bug
>Reporter: Vladislav Pyatkov
>Assignee: Vladislav Pyatkov
>Priority: Major
> Fix For: 2.8
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> I have seen from log partition miss warnings and after that rebelance was 
> canceled and was forcibly restarted but already over another suppliers. In 
> case when added nodes without a storage in persistent cluster it can lead to 
> several times fully rebalance. It seem to bee because we have not updated 
> partitions state until rebalance finished.
> Should to prevent partition eviction until rebalance on all nodes completed.



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


[jira] [Commented] (IGNITE-12032) Server node prints exception when ODBC driver disconnects

2019-09-23 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12032:


{panel:title=Branch: [pull/6897/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4626227buildTypeId=IgniteTests24Java8_RunAll]

> Server node prints exception when ODBC driver disconnects
> -
>
> Key: IGNITE-12032
> URL: https://issues.apache.org/jira/browse/IGNITE-12032
> Project: Ignite
>  Issue Type: Bug
>  Components: thin client
>Affects Versions: 2.7.5
>Reporter: Evgenii Zhuravlev
>Assignee: Lev Agafonov
>Priority: Minor
>  Labels: newbie, usability
> Fix For: 2.8
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Whenever a process using ODBC clients is finished, it's printing in the 
> node logs this exception: 
> {code:java}
> *[07:45:19,559][SEVERE][grid-nio-worker-client-listener-1-#30][ClientListenerProcessor]
>  
> Failed to process selector key [s 
> es=GridSelectorNioSessionImpl [worker=ByteBufferNioClientWorker 
> [readBuf=java.nio.HeapByteBuffer[pos=0 lim=8192 cap=8192 
> ], super=AbstractNioClientWorker [idx=1, bytesRcvd=0, bytesSent=0, 
> bytesRcvd0=0, bytesSent0=0, select=true, super=GridWo 
> rker [name=grid-nio-worker-client-listener-1, igniteInstanceName=null, 
> finished=false, heartbeatTs=1564289118230, hashCo 
> de=1829856117, interrupted=false, 
> runner=grid-nio-worker-client-listener-1-#30]]], writeBuf=null, 
> readBuf=null, inRecove 
> ry=null, outRecovery=null, super=GridNioSessionImpl 
> [locAddr=/0:0:0:0:0:0:0:1:10800, rmtAddr=/0:0:0:0:0:0:0:1:63697, cre 
> ateTime=1564289116225, closeTime=0, bytesSent=1346, bytesRcvd=588, 
> bytesSent0=0, bytesRcvd0=0, sndSchedTime=156428911623 
> 5, lastSndTime=1564289116235, lastRcvTime=1564289116235, readsPaused=false, 
> filterChain=FilterChain[filters=[GridNioAsyn 
> cNotifyFilter, GridNioCodecFilter [parser=ClientListenerBufferedParser, 
> directMode=false]], accepted=true, markedForClos 
> e=false]]] 
> java.io.IOException: An existing connection was forcibly closed by the 
> remote host 
> at sun.nio.ch.SocketDispatcher.read0(Native Method) 
> at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:43) 
> at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223) 
> at sun.nio.ch.IOUtil.read(IOUtil.java:197) 
> at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380) 
> at 
> org.apache.ignite.internal.util.nio.GridNioServer$ByteBufferNioClientWorker.processRead(GridNioServer.java:11
>  
> 04) 
> at 
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNi
>  
> oServer.java:2389) 
> at 
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:215
>  
> 6) 
> at 
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1797)
>  
> at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120) 
> at java.lang.Thread.run(Thread.java:748)* 
> {code}
> It's absolutely normal behavior when ODBC client disconnects from the node, 
> so, we shouldn't print exception in the log. We should replace it with 
> something like INFO message about ODBC client disconnection.
> Thread from user list: 
> http://apache-ignite-users.70518.x6.nabble.com/exceptions-in-Ignite-node-when-a-thin-client-process-ends-td28970.html



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


[jira] [Commented] (IGNITE-11868) GridClient#data() should be deprecated/removed.

2019-09-23 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-11868:


{panel:title=Branch: [pull/6894/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4624628buildTypeId=IgniteTests24Java8_RunAll]

> GridClient#data() should be deprecated/removed.
> ---
>
> Key: IGNITE-11868
> URL: https://issues.apache.org/jira/browse/IGNITE-11868
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Vyacheslav Koptilin
>Assignee: kcheng.mvp
>Priority: Minor
>  Labels: newbie
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> It seems that {{GridClient#data()}} does not make sense after IGNITE-3488 and 
> therefore it can be removed.



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


[jira] [Commented] (IGNITE-12145) [IEP-35] Monitoring list engine

2019-09-21 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12145:


{panel:title=Branch: [pull/6845/head] Base: [master] : Possible Blockers 
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}SPI{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=4621625]]
* IgniteSpiTestSuite: TcpDiscoverySslTrustedSelfTest.testFailedNodes3 - Test 
has low fail rate in base branch 0,0% and is not flaky

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

> [IEP-35] Monitoring list engine
> ---
>
> Key: IGNITE-12145
> URL: https://issues.apache.org/jira/browse/IGNITE-12145
> Project: Ignite
>  Issue Type: Sub-task
>Affects Versions: 2.7.5
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
>  Labels: IEP-35
> Fix For: 2.8
>
>  Time Spent: 20.5h
>  Remaining Estimate: 0h
>
> The base engine for the monitoring list.



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


[jira] [Commented] (IGNITE-12199) WAL record with data entries doesn't flushes on backups for transactional cache

2019-09-20 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12199:


{panel:title=Branch: [pull/6881/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4610733buildTypeId=IgniteTests24Java8_RunAll]

> WAL record with data entries doesn't flushes on backups for transactional 
> cache
> ---
>
> Key: IGNITE-12199
> URL: https://issues.apache.org/jira/browse/IGNITE-12199
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Andrey Gura
>Assignee: Andrey Gura
>Priority: Major
> Fix For: 2.8
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> WAL record with data entries doesn't flushes on backups for transactional 
> cache.
> This issue can be reproduced for example by 
> {{TxPartitionCounterStateConsistencyTest.testSingleThreadedUpdateOrder}} test 
> with disabled MMAP mode.
> Problem place in code is {{GridDistributedTxRemoteAdapter#commitIfLocked}} 
> where {{wal.log()}} doesn't assign returned file pointer to the {{ptr}} 
> variable.



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


[jira] [Commented] (IGNITE-12044) [IEP-35] JmxExporterSpi displays histogram values incorrectly

2019-09-19 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12044:


{panel:title=Branch: [pull/6882/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4614493buildTypeId=IgniteTests24Java8_RunAll]

> [IEP-35] JmxExporterSpi displays histogram values incorrectly
> -
>
> Key: IGNITE-12044
> URL: https://issues.apache.org/jira/browse/IGNITE-12044
> Project: Ignite
>  Issue Type: Bug
>Reporter: Andrey Gura
>Assignee: Nikolay Izhikov
>Priority: Major
>  Labels: IEP-35
> Fix For: 2.8
>
>  Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> {{JmxExporterSpi}} exposes histogram values incorrectly. It looks like:
> {noformat}
> durationHistogramlong[5]
> {noformat}
> I think exporter should register attribute for each histogram bucket. 
> Something like this:
> {noformat}
> durationHistogram.10 0
> durationHistogram.50 0
> durationHistogram.1000
> durationHistogram.2500
> durationHistogram.5000
> {noformat}



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


[jira] [Commented] (IGNITE-12109) The distributed metastorage must support read/write operation on an inactive cluster.

2019-09-19 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12109:


{panel:title=Branch: [pull/6873/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4605325buildTypeId=IgniteTests24Java8_RunAll]

> The distributed metastorage must support read/write operation on an inactive 
> cluster.
> -
>
> Key: IGNITE-12109
> URL: https://issues.apache.org/jira/browse/IGNITE-12109
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Ivan Bessonov
>Assignee: Ivan Bessonov
>Priority: Major
> Fix For: 2.8
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> The metastorage isn't able to propagate value on an inactive cluster.



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


[jira] [Commented] (IGNITE-12110) Bugs & tests fixes

2019-09-19 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12110:


{panel:title=Branch: [pull/6815/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4608200buildTypeId=IgniteTests24Java8_RunAll]

>  Bugs & tests fixes
> ---
>
> Key: IGNITE-12110
> URL: https://issues.apache.org/jira/browse/IGNITE-12110
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Govorukhin
>Assignee: Sergey Chugunov
>Priority: Major
> Fix For: 2.8
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Fixed test:
> - *.testMassiveServersShutdown2
> - Fixed isStopped flag was't set during disconnect
> - Don't allow "NodeStoppingException" to fail checkpoint thread on stopping
> Test improvements:
> - Add page lock tracker and failure handler for all BPlustTree tests



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


[jira] [Commented] (IGNITE-12179) Test and javadoc fixes

2019-09-19 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12179:


{panel:title=Branch: [pull/6878/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4608084buildTypeId=IgniteTests24Java8_RunAll]

> Test and javadoc fixes
> --
>
> Key: IGNITE-12179
> URL: https://issues.apache.org/jira/browse/IGNITE-12179
> Project: Ignite
>  Issue Type: Bug
>Reporter: Anton Kalashnikov
>Assignee: Anton Kalashnikov
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> *.testTtlNoTx flaky failed on TC
> TcpCommunicationSpiFreezingClientTest failed
> TcpCommunicationSpiFaultyClientSslTest.testNotAcceptedConnection failed
> testCacheIdleVerifyPrintLostPartitions failed



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


[jira] [Commented] (IGNITE-12027) NPE on try to read the MinimumNumberOfPartitionCopies metric.

2019-09-17 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12027:


{panel:title=Branch: [pull/6738/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4606238buildTypeId=IgniteTests24Java8_RunAll]

> NPE on try to read the MinimumNumberOfPartitionCopies metric.
> -
>
> Key: IGNITE-12027
> URL: https://issues.apache.org/jira/browse/IGNITE-12027
> Project: Ignite
>  Issue Type: Bug
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
>Priority: Major
>  Labels: IEP-35
> Fix For: 2.8
>
>  Time Spent: 2h 10m
>  Remaining Estimate: 0h
>
> NPE on try to read the MinimumNumberOfPartitionCopies metric before node 
> starts.
> Details:
> {noformat}
> java.lang.NullPointerException
>   at 
> org.apache.ignite.internal.processors.cache.CacheGroupMetricsImpl.numberOfPartitionCopies(CacheGroupMetricsImpl.java:218)
>   at 
> org.apache.ignite.internal.processors.cache.CacheGroupMetricsImpl.getMinimumNumberOfPartitionCopies(CacheGroupMetricsImpl.java:232)
>   at 
> org.apache.ignite.internal.util.lang.GridFunc.lambda$nonThrowableSupplier$2(GridFunc.java:3302)
>   at 
> org.apache.ignite.internal.processors.metric.impl.IntGauge.value(IntGauge.java:45)
>   at 
> org.apache.ignite.spi.metric.opencensus.OpenCensusMetricExporterSpi.lambda$null$5(OpenCensusMetricExporterSpi.java:152)
>   at java.lang.Iterable.forEach(Iterable.java:75)
>   at 
> org.apache.ignite.spi.metric.opencensus.OpenCensusMetricExporterSpi.lambda$export$6(OpenCensusMetricExporterSpi.java:141)
>   at java.lang.Iterable.forEach(Iterable.java:75)
>   at 
> org.apache.ignite.spi.metric.opencensus.OpenCensusMetricExporterSpi.export(OpenCensusMetricExporterSpi.java:137)
>   at 
> org.apache.ignite.internal.processors.metric.PushMetricsExporterAdapter.lambda$spiStart$0(PushMetricsExporterAdapter.java:57)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>   at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>   at java.lang.Thread.run(Thread.java:748)
> {noformat}
> Reason: {{GridDhtPartitionFullMap partFullMap = 
> ctx.topology().partitionMap(false);}} is null.



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


[jira] [Commented] (IGNITE-12176) .NET: Apache.Ignite.exe fails when config has custom logger or plugins

2019-09-17 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12176:


{panel:title=Branch: [pull/6872/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4605195buildTypeId=IgniteTests24Java8_RunAll]

> .NET: Apache.Ignite.exe fails when config has custom logger or plugins
> --
>
> Key: IGNITE-12176
> URL: https://issues.apache.org/jira/browse/IGNITE-12176
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
>  Labels: .NET
>
> Steps to reproduce:
> * Implement Apache.Ignite.Core.Log.ILogger interface, compiled into assembly
> * Create a config file with that logger:
> {code}
> 
> 
>  type="Apache.Ignite.Core.IgniteConfigurationSection, Apache.Ignite.Core" />
> 
>  xmlns="http://ignite.apache.org/schema/dotnet/IgniteConfigurationSection;>
> 
> 
> 
> {code}
> * Run Apache.Ignite.exe with that config file while CustomAsm is in a 
> separate dir:
> {code}
> Apache.Ignite.exe -ConfigFileName=myconfig.xml -assembly=c:\w\CustomAsm.dll
> {code}



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Commented] (IGNITE-12122) Remove setIncludeEventTypes from GridAbstractTest.

2019-09-16 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12122:


{panel:title=Branch: [pull/6825/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4600914buildTypeId=IgniteTests24Java8_RunAll]

> Remove setIncludeEventTypes from GridAbstractTest.
> --
>
> Key: IGNITE-12122
> URL: https://issues.apache.org/jira/browse/IGNITE-12122
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 2.7.5
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
> Attachments: flamegraph-18988.svg
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Simple cache.put() hot threads measurements shows that  
> GridCacheEventManager::addEvent consumes about 7% of  overall time, i suggest 
> to remove this events from GridAbstractTest::getConfiguration and stores only 
> for really requiring tests.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Commented] (IGNITE-12027) NPE on try to read the MinimumNumberOfPartitionCopies metric.

2019-09-16 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12027:


{panel:title=Branch: [pull/6738/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4602165buildTypeId=IgniteTests24Java8_RunAll]

> NPE on try to read the MinimumNumberOfPartitionCopies metric.
> -
>
> Key: IGNITE-12027
> URL: https://issues.apache.org/jira/browse/IGNITE-12027
> Project: Ignite
>  Issue Type: Bug
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
>Priority: Major
>  Labels: IEP-35
> Fix For: 2.8
>
>  Time Spent: 2h 10m
>  Remaining Estimate: 0h
>
> NPE on try to read the MinimumNumberOfPartitionCopies metric before node 
> starts.
> Details:
> {noformat}
> java.lang.NullPointerException
>   at 
> org.apache.ignite.internal.processors.cache.CacheGroupMetricsImpl.numberOfPartitionCopies(CacheGroupMetricsImpl.java:218)
>   at 
> org.apache.ignite.internal.processors.cache.CacheGroupMetricsImpl.getMinimumNumberOfPartitionCopies(CacheGroupMetricsImpl.java:232)
>   at 
> org.apache.ignite.internal.util.lang.GridFunc.lambda$nonThrowableSupplier$2(GridFunc.java:3302)
>   at 
> org.apache.ignite.internal.processors.metric.impl.IntGauge.value(IntGauge.java:45)
>   at 
> org.apache.ignite.spi.metric.opencensus.OpenCensusMetricExporterSpi.lambda$null$5(OpenCensusMetricExporterSpi.java:152)
>   at java.lang.Iterable.forEach(Iterable.java:75)
>   at 
> org.apache.ignite.spi.metric.opencensus.OpenCensusMetricExporterSpi.lambda$export$6(OpenCensusMetricExporterSpi.java:141)
>   at java.lang.Iterable.forEach(Iterable.java:75)
>   at 
> org.apache.ignite.spi.metric.opencensus.OpenCensusMetricExporterSpi.export(OpenCensusMetricExporterSpi.java:137)
>   at 
> org.apache.ignite.internal.processors.metric.PushMetricsExporterAdapter.lambda$spiStart$0(PushMetricsExporterAdapter.java:57)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>   at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>   at java.lang.Thread.run(Thread.java:748)
> {noformat}
> Reason: {{GridDhtPartitionFullMap partFullMap = 
> ctx.topology().partitionMap(false);}} is null.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Commented] (IGNITE-12165) Negative time in Transaction time dump

2019-09-13 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12165:


{panel:title=Branch: [pull/6864/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4591557buildTypeId=IgniteTests24Java8_RunAll]

> Negative time in Transaction time dump
> --
>
> Key: IGNITE-12165
> URL: https://issues.apache.org/jira/browse/IGNITE-12165
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Denis Chudov
>Assignee: Denis Chudov
>Priority: Major
>
> After implementing ticket IGNITE-12063 we have transaction dumps in the logs.
>  there are some issues with information in these dumps:
> {code:java}
> [11:53:36,154][INFO][snapshot-scheduler-restats-#69][GridNearTxLocal] 
> Transaction time dump [startTime=11:53:36.081, totalTime=65, systemTime=3, 
> userTime=62, cacheOperationsTime=-41943785508, rollbackTime=41943785512, 
> tx=GridNearTxLocal [mappings=IgniteTxMappingsImpl [], 
> nearLocallyMapped=false, colocatedLocallyMapped=false, needCheckBackup=null, 
> hasRemoteLocks=true, trackTimeout=false, systemTime=3953576, 
> systemStartTime=0, prepareStartTime=0, prepareTime=0, 
> commitOrRollbackStartTime=0, commitOrRollbackTime=41943785512318555, 
> txDumpsThrottling=org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager$TxDumpsThrottling@760d8025,
>  lb=null, thread=snapshot-scheduler-restats-#69, 
> mappings=IgniteTxMappingsImpl [], super=GridDhtTxLocalAdapter 
> [nearOnOriginatingNode=false, nearNodes=KeySetView [], dhtNodes=KeySetView 
> [], explicitLock=false, super=IgniteTxLocalAdapter [completedBase=null, 
> sndTransformedVals=false, depEnabled=false, txState=IgniteTxStateImpl 
> [activeCacheIds=[-2100569601], recovery=false, txMap=HashSet [IgniteTxEntry 
> [key=KeyCacheObjectImpl [part=2, val=SnapshotScheduleKey [id=_SCHEDULES_], 
> hasValBytes=true], cacheId=-2100569601, txKey=IgniteTxKey 
> [key=KeyCacheObjectImpl [part=2, val=SnapshotScheduleKey [id=_SCHEDULES_], 
> hasValBytes=true], cacheId=-2100569601], val=[op=READ, val=null], 
> prevVal=[op=NOOP, val=null], oldVal=[op=NOOP, val=null], 
> entryProcessorsCol=null, ttl=-1, conflictExpireTime=-1, conflictVer=null, 
> explicitVer=null, dhtVer=null, filters=null, filtersPassed=false, 
> filtersSet=true, entry=GridCacheMapEntry [key=KeyCacheObjectImpl [part=2, 
> val=SnapshotScheduleKey [id=_SCHEDULES_], hasValBytes=true], val=null, 
> ver=GridCacheVersion [topVer=0, order=0, nodeOrder=0], hash=886348002, 
> extras=null, flags=0]GridDistributedCacheEntry 
> [super=]GridDhtDetachedCacheEntry [super=], prepared=0, locked=true, 
> nodeId=1adbae78-40fe-480d-803d-4d498919ae63, locMapped=false, expiryPlc=null, 
> transferExpiryPlc=false, flags=0, partUpdateCntr=0, serReadVer=null, 
> xidVer=GridCacheVersion [topVer=179672005, order=1568192005565, 
> nodeOrder=1, super=IgniteTxAdapter [xidVer=GridCacheVersion 
> [topVer=179672005, order=1568192005565, nodeOrder=1], writeVer=null, 
> implicit=false, loc=true, threadId=125, startTime=1568192016081, 
> nodeId=9e00ae45-4084-4f29-949f-c19c933f4299, startVer=GridCacheVersion 
> [topVer=179672005, order=1568192005565, nodeOrder=1], endVer=null, 
> isolation=REPEATABLE_READ, concurrency=PESSIMISTIC, timeout=0, 
> sysInvalidate=false, sys=true, plc=5, commitVer=null, finalizing=NONE, 
> invalidParts=null, state=ROLLED_BACK, timedOut=false, 
> topVer=AffinityTopologyVersion [topVer=4, minorTopVer=1], duration=60ms, 
> onePhaseCommit=false], size=1
> {code}
> For example:
>  # Negative time: cacheOperationsTime=-41943785508,
>  # Huge times: rollbackTime=41943785512



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Commented] (IGNITE-12027) NPE on try to read the MinimumNumberOfPartitionCopies metric.

2019-09-12 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12027:


{panel:title=Branch: [pull/6738/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=457buildTypeId=IgniteTests24Java8_RunAll]

> NPE on try to read the MinimumNumberOfPartitionCopies metric.
> -
>
> Key: IGNITE-12027
> URL: https://issues.apache.org/jira/browse/IGNITE-12027
> Project: Ignite
>  Issue Type: Bug
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
>Priority: Major
>  Labels: IEP-35
> Fix For: 2.8
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> NPE on try to read the MinimumNumberOfPartitionCopies metric before node 
> starts.
> Details:
> {noformat}
> java.lang.NullPointerException
>   at 
> org.apache.ignite.internal.processors.cache.CacheGroupMetricsImpl.numberOfPartitionCopies(CacheGroupMetricsImpl.java:218)
>   at 
> org.apache.ignite.internal.processors.cache.CacheGroupMetricsImpl.getMinimumNumberOfPartitionCopies(CacheGroupMetricsImpl.java:232)
>   at 
> org.apache.ignite.internal.util.lang.GridFunc.lambda$nonThrowableSupplier$2(GridFunc.java:3302)
>   at 
> org.apache.ignite.internal.processors.metric.impl.IntGauge.value(IntGauge.java:45)
>   at 
> org.apache.ignite.spi.metric.opencensus.OpenCensusMetricExporterSpi.lambda$null$5(OpenCensusMetricExporterSpi.java:152)
>   at java.lang.Iterable.forEach(Iterable.java:75)
>   at 
> org.apache.ignite.spi.metric.opencensus.OpenCensusMetricExporterSpi.lambda$export$6(OpenCensusMetricExporterSpi.java:141)
>   at java.lang.Iterable.forEach(Iterable.java:75)
>   at 
> org.apache.ignite.spi.metric.opencensus.OpenCensusMetricExporterSpi.export(OpenCensusMetricExporterSpi.java:137)
>   at 
> org.apache.ignite.internal.processors.metric.PushMetricsExporterAdapter.lambda$spiStart$0(PushMetricsExporterAdapter.java:57)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>   at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>   at java.lang.Thread.run(Thread.java:748)
> {noformat}
> Reason: {{GridDhtPartitionFullMap partFullMap = 
> ctx.topology().partitionMap(false);}} is null.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Commented] (IGNITE-12162) Add the cluster name to the promt message "--deactivate" the control.sh

2019-09-11 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12162:


{panel:title=Branch: [pull/6863/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4589123buildTypeId=IgniteTests24Java8_RunAll]

> Add the cluster name to the promt message "--deactivate" the control.sh
> ---
>
> Key: IGNITE-12162
> URL: https://issues.apache.org/jira/browse/IGNITE-12162
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Kirill Tkalenko
>Assignee: Kirill Tkalenko
>Priority: Major
> Fix For: 2.8
>
>
> Add the cluster name to the promt message "--deactivate" the control.sh



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Commented] (IGNITE-12163) .NET: CacheEntryEventType.Removed is not being risen

2019-09-11 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12163:


{panel:title=Branch: [pull/6862/head] Base: [master] : Possible Blockers 
(3)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}ZooKeeper (Discovery) 1{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=4588926]]
* ZookeeperDiscoverySpiTestSuite1: 
ZookeeperDiscoveryCustomEventsTest.testCustomEvents_FastStopProcess_2 - Test 
has low fail rate in base branch 0,0% and is not flaky

{color:#d04437}Basic 1{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=4588931]]
* IgniteBasicTestSuite: 
IgniteExceptionRegistrySelfTest.testMultiThreadedMaxSize - Test has low fail 
rate in base branch 0,0% and is not flaky

{color:#d04437}Platform .NET (Integrations){color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4589007]]

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

> .NET: CacheEntryEventType.Removed is not being risen
> 
>
> Key: IGNITE-12163
> URL: https://issues.apache.org/jira/browse/IGNITE-12163
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 2.7.5
>Reporter: Alexandr Shapkin
>Assignee: Alexandr Shapkin
>Priority: Critical
>  Labels: .NET
> Fix For: 2.7.6
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Steps to reproduce:
>  * Create a cache with user-defined type
>  * Add an ICacheEntryEventListener in order to be notified of 
> CacheEntryEventType.Removed events
>  * Put a value in the cache
>  * Remove that value
> Expected: CacheEntryEventType.Removed event get captured
> Actual: CacheEntryEventType.Updated event get captured
> Update:
> After these changes https://issues.apache.org/jira/browse/IGNITE-8714
> New logic of detecting events (ContinuousQueryUtils.cs) now relies on the 
> Object.Equals method which is not intuitive at all.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Commented] (IGNITE-12153) Control.sh add test for checking that help and cache help output are not broken.

2019-09-11 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12153:


{panel:title=Branch: [pull/6860/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4588347buildTypeId=IgniteTests24Java8_RunAll]

> Control.sh add test for checking that help and cache help output are not 
> broken.
> 
>
> Key: IGNITE-12153
> URL: https://issues.apache.org/jira/browse/IGNITE-12153
> Project: Ignite
>  Issue Type: Bug
>Reporter: Sergey Antonov
>Assignee: Sergey Antonov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> We should store "ideal" outputs in resorces and compare with current.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Commented] (IGNITE-12153) Control.sh add test for checking that help and cache help output are not broken.

2019-09-11 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12153:


{panel:title=Branch: [pull/6860/head] Base: [master] : Possible Blockers 
(4)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}SPI{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=4588263]]
* IgniteSpiTestSuite: 
TcpClientDiscoverySpiFailureTimeoutSelfTest.testDisconnectAfterNetworkTimeout - 
Test has low fail rate in base branch 0,0% and is not flaky

{color:#d04437}Cache 2{color} [[tests 0 TIMEOUT , Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=4588297]]

{color:#d04437}MVCC Cache 1{color} [[tests 0 TIMEOUT , Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=4588331]]

{color:#d04437}PDS 4{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=4588316]]
* IgnitePdsTestSuite4: PageLockTrackerManagerTest.testMemoryCalculation - Test 
has low fail rate in base branch 0,0% and is not flaky

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

> Control.sh add test for checking that help and cache help output are not 
> broken.
> 
>
> Key: IGNITE-12153
> URL: https://issues.apache.org/jira/browse/IGNITE-12153
> Project: Ignite
>  Issue Type: Bug
>Reporter: Sergey Antonov
>Assignee: Sergey Antonov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> We should store "ideal" outputs in resorces and compare with current.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Commented] (IGNITE-5795) Binary metadata is not registered during start of cache

2019-09-10 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-5795:
---

{panel:title=Branch: [pull/6854/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4581437buildTypeId=IgniteTests24Java8_RunAll]

> Binary metadata is not registered during start of cache
> ---
>
> Key: IGNITE-5795
> URL: https://issues.apache.org/jira/browse/IGNITE-5795
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.0
>Reporter: Dmitry Karachentsev
>Assignee: Anton Kalashnikov
>Priority: Major
>  Labels: usability
> Fix For: 2.8
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> When cache configured with QueryEntity and used key type with 
> @AffinityKeyMapped field, it will be ignored and wrong partition calculated. 
> This happens because QueryEntity processing precedes key type registering in 
> binary meta cache. On that step 
> CacheObjectBinaryProcessorImpl#affinityKeyField called and unable to resolve 
> type, so null returned and null putted in affKeyFields.
> On next put/get operation CacheObjectBinaryProcessorImpl#affinityKeyField 
> will return null from affKeyFields, but should be affinity key field.
> Test that reproduces problem in [PR 
> 2330|https://github.com/apache/ignite/pull/2330]
> To wrorkaround the issue, set IgniteConfiguration#setKeyConfiguration(), it 
> will force registering key.
> *Root cause of this behaviour* is that in during cache registration 
> registration of metadata doesn't happen. It lead to exchange messages like 
> (MappingProposedMessage, MetadataRequestMessage etc.) which are often 
> redundant and also lead to behaviour described above(unhandled 
> AffinityKeyMapped).
> Main idea to fix this problem it is registration of metadata locally in 
> during cache start  on each node without messages exchange.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Commented] (IGNITE-12106) Rework ignite binary metadata exception for ease of troubleshooting

2019-09-10 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12106:


{panel:title=Branch: [pull/6855/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4582560buildTypeId=IgniteTests24Java8_RunAll]

> Rework ignite binary metadata exception for ease of troubleshooting
> ---
>
> Key: IGNITE-12106
> URL: https://issues.apache.org/jira/browse/IGNITE-12106
> Project: Ignite
>  Issue Type: Bug
>  Components: cache, persistence
>Affects Versions: 2.7.5, 2.7.6
>Reporter: Denis Magda
>Assignee: Alexey Goncharuk
>Priority: Blocker
> Fix For: 2.7.6
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> An exception of this kind happens regularly and its message doesn't suggest 
> why it took place and how to fix the issue:
> {noformat}
> Cannot find metadata for object with compact footer: 2097659979
> {noformat}
> See this thread for more details:
> http://apache-ignite-developers.2346864.n4.nabble.com/Metastore-disappears-in-Docker-on-restarts-td43107.html
> As a solution, let's rework this exception to ensure that the way like that 
> "Ignite work directory might be cleared on restarts. Ensure that IGNITE_HOME 
> doesn't point to a temp folder or any other folder that is destroyed/erased 
> on restarts. Presently, IGNITE_HOME points to..."



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Commented] (IGNITE-12123) Cache throws npe at {null, null, null} array key.

2019-09-09 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12123:


{panel:title=Branch: [pull/6828/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4552044buildTypeId=IgniteTests24Java8_RunAll]

> Cache throws npe at {null, null, null} array key.
> -
>
> Key: IGNITE-12123
> URL: https://issues.apache.org/jira/browse/IGNITE-12123
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.8
>Reporter: Stepachev Maksim
>Assignee: Stepachev Maksim
>Priority: Major
> Fix For: 2.8
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> When we put null-key to ignite cache we get NPE with the problem description
> "java.lang.NullPointerException: Ouch! Argument cannot be null: key"
> But when we put "new String[]
> {"c", *null*, "a"}



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Commented] (IGNITE-12128) Potentially pds corruption on a failed node during checkpoint

2019-09-09 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12128:


{panel:title=Branch: [pull/6851/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4574261buildTypeId=IgniteTests24Java8_RunAll]

> Potentially pds corruption on a failed node during checkpoint
> -
>
> Key: IGNITE-12128
> URL: https://issues.apache.org/jira/browse/IGNITE-12128
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Govorukhin
>Assignee: Anton Kalashnikov
>Priority: Critical
> Fix For: 2.7.6
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> There are the case when we start a checkpoint but not create CP file marker, 
> but PageMemory may start to flush dirty pages from checkpoint pages to page 
> store.  If node crashed at this moment, we can get inconsistency state, 
> because we still not write checkpoint marker to disk but already write some 
> pages for this checkpoint. If we try to recover from this state we cat get 
> any sort of corruption problem. Recovery logic may not recognize that crash 
> was during checkpoint because we did not write file marker when we start 
> checkpoint but write some pages for this checkpoint.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Commented] (IGNITE-11410) Sandbox for user-defined code

2019-09-06 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-11410:


{panel:title=Branch: [pull/6750/head] Base: [master] : Possible Blockers 
(115)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform C++ (Linux)*{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574670]]

{color:#d04437}Cache 6{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574699]]

{color:#d04437}PDS (Indexing){color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574709]]

{color:#d04437}Data Structures{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574706]]

{color:#d04437}ZooKeeper (Discovery) 1{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574668]]

{color:#d04437}Scala (Examples){color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574666]]

{color:#d04437}MVCC PDS 2{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574739]]

{color:#d04437}MVCC PDS 4{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574741]]

{color:#d04437}ZooKeeper (Discovery) 2{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574669]]

{color:#d04437}Platform .NET (Long Running){color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574719]]

{color:#d04437}SPI{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574661]]

{color:#d04437}Cache 8{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574701]]

{color:#d04437}Cache 5{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574698]]

{color:#d04437}Cache 3{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574696]]

{color:#d04437}Platform .NET (Core Linux){color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574716]]

{color:#d04437}PDS (Compatibility){color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574708]]

{color:#d04437}Scala (Visor Console){color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574667]]

{color:#d04437}RDD{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574655]]

{color:#d04437}Examples{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574642]]

{color:#d04437}MVCC Cache 7{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574735]]

{color:#d04437}Platform .NET{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574715]]

{color:#d04437}Start Nodes{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574660]]

{color:#d04437}Cache (Expiry Policy){color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574684]]

{color:#d04437}PDS 2{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574712]]

{color:#d04437}Streamers{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574659]]

{color:#d04437}Cache 2{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574695]]

{color:#d04437}MVCC Cache 8{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574736]]

{color:#d04437}PDS 3{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574713]]

{color:#d04437}Queries 1{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574721]]

{color:#d04437}Continuous Query 3{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574704]]

{color:#d04437}ZooKeeper (Discovery) 3{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574723]]

{color:#d04437}ZooKeeper (Discovery) 4{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574724]]

{color:#d04437}Continuous Query 4{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574705]]

{color:#d04437}Basic 1{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574673]]

{color:#d04437}Cache (Restarts) 1{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574691]]

{color:#d04437}Cache 1{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574694]]

{color:#d04437}MVCC Queries{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574679]]

{color:#d04437}PDS 4{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574714]]

{color:#d04437}MVCC Cache 1{color} [[tests 0 
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574729]]


[jira] [Commented] (IGNITE-8622) Zookeeper and TCP discovery SPI' getSpiState method inconsistent

2019-09-06 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-8622:
---

{panel:title=Branch: [pull/6844/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4570624buildTypeId=IgniteTests24Java8_RunAll]

> Zookeeper and TCP discovery SPI' getSpiState method inconsistent
> 
>
> Key: IGNITE-8622
> URL: https://issues.apache.org/jira/browse/IGNITE-8622
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Max Shonichev
>Assignee: Ryabov Dmitrii
>Priority: Minor
>  Labels: jmx
> Fix For: 2.8
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> getSpiState of TcpDiscoverySpi Mbean returns uppercased human-readable state, 
> e.g. 'CONNECTED'
> getSpiState of ZookeeperDiscoverySpi Mbean returns camelcased one, e.g. 
> 'Connected'



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Commented] (IGNITE-11829) Distribute joins fail if number of tables > 7

2019-09-05 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-11829:


{panel:title=Branch: [pull/6842/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4569463buildTypeId=IgniteTests24Java8_RunAll]

> Distribute joins fail if number of tables > 7
> -
>
> Key: IGNITE-11829
> URL: https://issues.apache.org/jira/browse/IGNITE-11829
> Project: Ignite
>  Issue Type: Improvement
>  Components: sql
>Affects Versions: 2.7
>Reporter: Stanislav Lukyanov
>Assignee: Diana Iakovleva
>Priority: Major
>  Labels: newbie
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Distributed joins fail with ArrayIndexOutOfBounds when the total number of 
> tables is > 7.
> Example:
> {code}
> try (Ignite ignite = 
> Ignition.start("examples/config/example-ignite.xml");) {
> IgniteCache cache = ignite.createCache("foo");
> cache.query(new SqlFieldsQuery("CREATE TABLE Person(ID INTEGER 
> PRIMARY KEY, NAME VARCHAR(100));"));
> cache.query(new SqlFieldsQuery("INSERT INTO Person(ID, NAME) 
> VALUES (1, 'Ed'), (2, 'Ann'), (3, 'Emma');"));
> cache.query(new SqlFieldsQuery("SELECT *\n" +
> "FROM PERSON P1\n" +
> "JOIN PERSON P2 ON P1.ID = P2.ID\n" +
> "JOIN PERSON P3 ON P1.ID = P3.ID\n" +
> "JOIN PERSON P4 ON P1.ID = P4.ID\n" +
> "JOIN PERSON P5 ON P1.ID = P5.ID\n" +
> "JOIN PERSON P6 ON P1.ID = P6.ID\n" +
> "JOIN PERSON P7 ON P1.ID = P7.ID\n" +
> "JOIN PERSON P8 ON P1.ID = 
> P8.ID").setDistributedJoins(true).setEnforceJoinOrder(false));
> }
> {code}
> throws
> {code}
> Exception in thread "main" javax.cache.CacheException: General error: 
> "java.lang.ArrayIndexOutOfBoundsException" [5-197]
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:832)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:765)
>   at 
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.query(GatewayProtectedCacheProxy.java:403)
>   at 
> org.apache.ignite.examples.ExampleNodeStartup.main(ExampleNodeStartup.java:60)
> Caused by: class 
> org.apache.ignite.internal.processors.query.IgniteSQLException: General 
> error: "java.lang.ArrayIndexOutOfBoundsException" [5-197]
>   at 
> org.apache.ignite.internal.processors.query.h2.QueryParser.parseH2(QueryParser.java:454)
>   at 
> org.apache.ignite.internal.processors.query.h2.QueryParser.parse0(QueryParser.java:156)
>   at 
> org.apache.ignite.internal.processors.query.h2.QueryParser.parse(QueryParser.java:121)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.querySqlFields(IgniteH2Indexing.java:1191)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$3.applyx(GridQueryProcessor.java:2261)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$3.applyx(GridQueryProcessor.java:2257)
>   at 
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:53)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2767)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.lambda$querySqlFields$1(GridQueryProcessor.java:2277)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuerySafe(GridQueryProcessor.java:2297)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2250)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2177)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:817)
>   ... 3 more
> Caused by: org.h2.jdbc.JdbcSQLException: General error: 
> "java.lang.ArrayIndexOutOfBoundsException" [5-197]
>   at org.h2.message.DbException.getJdbcSQLException(DbException.java:357)
>   at org.h2.message.DbException.get(DbException.java:168)
>   at org.h2.message.DbException.convert(DbException.java:307)
>   at org.h2.message.DbException.toSQLException(DbException.java:280)
>   at org.h2.message.TraceObject.logAndConvert(TraceObject.java:357)
>   at org.h2.jdbc.JdbcConnection.prepareStatement(JdbcConnection.java:308)
>   at 
> 

  1   2   3   4   5   6   7   8   9   10   >