[jira] [Updated] (IGNITE-7147) Implement connected clusters component

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-7147:
-
Summary: Implement connected clusters component  (was: Implemente connected 
clusters component)

> Implement connected clusters component
> --
>
> Key: IGNITE-7147
> URL: https://issues.apache.org/jira/browse/IGNITE-7147
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Dmitriy Shabalin
>Assignee: Pavel Konstantinov
> Fix For: 2.4
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-7153) Redis: BufferUnderflowException at GridRedisProtocolParser.readBulkStr for values > 8kb

[Roman Shtykh (JIRA)]

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

Roman Shtykh commented on IGNITE-7153:
--

Needs to be handled with {{ParserState}}

> Redis: BufferUnderflowException at GridRedisProtocolParser.readBulkStr for 
> values > 8kb
> ---
>
> Key: IGNITE-7153
> URL: https://issues.apache.org/jira/browse/IGNITE-7153
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 2.3
> Environment: Win, PHP 7, php_redis-3.1.1-7.0
>Reporter: Alexey Popov
>Assignee: Roman Shtykh
>  Labels: redis
>
> Exception:
> {noformat}
> [15:03:23,690][SEVERE][grid-nio-worker-tcp-rest-0-#36][GridTcpRestProtocol] 
> Failed to process selector key [ses=GridSelectorNioSessionImpl 
> [worker=ByteBufferNioClientWorker [readBuf=java.nio.HeapByteBuffer[pos=28 
> lim=8192 cap=8192], super=AbstractNioClientWorker [idx=0, bytesRcvd=0, 
> bytesSent=0, bytesRcvd0=0, bytesSent0=0, select=true, super=GridWorker 
> [name=grid-nio-worker-tcp-rest-0, igniteInstanceName=null, finished=false, 
> hashCode=396395638, interrupted=false, 
> runner=grid-nio-worker-tcp-rest-0-#36]]], writeBuf=null, readBuf=null, 
> inRecovery=null, outRecovery=null, super=GridNioSessionImpl 
> [locAddr=/127.0.0.1:6380, rmtAddr=/127.0.0.1:51794, createTime=1512734602674, 
> closeTime=0, bytesSent=0, bytesRcvd=8192, bytesSent0=0, bytesRcvd0=8192, 
> sndSchedTime=1512734602674, lastSndTime=1512734602674, 
> lastRcvTime=1512734602674, readsPaused=false, 
> filterChain=FilterChain[filters=[GridNioCodecFilter [parser=GridTcpRestParser 
> [jdkMarshaller=JdkMarshaller [], routerClient=false], directMode=false]], 
> accepted=true]]]
> java.nio.BufferUnderflowException
>   at java.nio.HeapByteBuffer.get(HeapByteBuffer.java:151)
>   at 
> org.apache.ignite.internal.processors.rest.protocols.tcp.redis.GridRedisProtocolParser.readBulkStr(GridRedisProtocolParser.java:107)
>   at 
> org.apache.ignite.internal.processors.rest.protocols.tcp.redis.GridRedisProtocolParser.readArray(GridRedisProtocolParser.java:86)
>   at 
> org.apache.ignite.internal.processors.rest.protocols.tcp.GridTcpRestParser.decode(GridTcpRestParser.java:150)
>   at 
> org.apache.ignite.internal.processors.rest.protocols.tcp.GridTcpRestParser.decode(GridTcpRestParser.java:70)
>   at 
> org.apache.ignite.internal.util.nio.GridNioCodecFilter.onMessageReceived(GridNioCodecFilter.java:114)
>   at 
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$HeadFilter.onMessageReceived(GridNioServer.java:3392)
>   at 
> org.apache.ignite.internal.util.nio.GridNioFilterChain.onMessageReceived(GridNioFilterChain.java:175)
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$ByteBufferNioClientWorker.processRead(GridNioServer.java:1096)
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNioServer.java:2272)
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:2048)
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1717)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at java.lang.Thread.run(Thread.java:748)
> [15:03:23,691][SEVERE][grid-nio-worker-tcp-rest-0-#36][GridTcpRestProtocol] 
> Closing NIO session because of unhandled exception.
> class org.apache.ignite.internal.util.nio.GridNioException: null
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNioServer.java:2296)
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:2048)
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1717)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at java.lang.Thread.run(Thread.java:748)
> Caused by: java.nio.BufferUnderflowException
>   at java.nio.HeapByteBuffer.get(HeapByteBuffer.java:151)
>   at 
> org.apache.ignite.internal.processors.rest.protocols.tcp.redis.GridRedisProtocolParser.readBulkStr(GridRedisProtocolParser.java:107)
>   at 
> org.apache.ignite.internal.processors.rest.protocols.tcp.redis.GridRedisProtocolParser.readArray(GridRedisProtocolParser.java:86)
>   at 
> org.apache.ignite.internal.processors.rest.protocols.tcp.GridTcpRestParser.decode(GridTcpRestParser.java:150)
>   at 
> 

[jira] [Updated] (IGNITE-7166) SQL join with partition and replicated caches fails if number of partitions is too low.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-7166:

Component/s: sql

> SQL join with partition and replicated caches fails if number of partitions 
> is too low.
> ---
>
> Key: IGNITE-7166
> URL: https://issues.apache.org/jira/browse/IGNITE-7166
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.3
>Reporter: Alexei Scherbakov
> Fix For: 2.4
>
>
> If not all nodes receive primary partition, we fail to validate nodes 
> predicate:
> {code}
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor#stableDataNodes
> ...
> else if (!isReplicatedOnly && extraCctx.isReplicated()) {
> if (!extraNodes.containsAll(nodes))
> {code}
> Solution: remove from validation nodes containing no primary partitions for 
> replicated cache.
> Reproducer:
> {noformat}
> /*
>  * Licensed to the Apache Software Foundation (ASF) under one or more
>  * contributor license agreements.  See the NOTICE file distributed with
>  * this work for additional information regarding copyright ownership.
>  * The ASF licenses this file to You under the Apache License, Version 2.0
>  * (the "License"); you may not use this file except in compliance with
>  * the License.  You may obtain a copy of the License at
>  *
>  *  http://www.apache.org/licenses/LICENSE-2.0
>  *
>  * Unless required by applicable law or agreed to in writing, software
>  * distributed under the License is distributed on an "AS IS" BASIS,
>  * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
>  * See the License for the specific language governing permissions and
>  * limitations under the License.
>  */
> package org.apache.ignite.internal.processors.cache.distributed.replicated;
> import java.util.List;
> import org.apache.ignite.Ignite;
> import org.apache.ignite.cache.affinity.rendezvous.RendezvousAffinityFunction;
> import org.apache.ignite.cache.query.FieldsQueryCursor;
> import org.apache.ignite.cache.query.SqlFieldsQuery;
> import org.apache.ignite.cache.query.annotations.QuerySqlField;
> import org.apache.ignite.configuration.CacheConfiguration;
> import org.apache.ignite.configuration.IgniteConfiguration;
> import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
> import static org.apache.ignite.cache.CacheAtomicityMode.TRANSACTIONAL;
> import static org.apache.ignite.cache.CacheMode.PARTITIONED;
> import static org.apache.ignite.cache.CacheMode.REPLICATED;
> import static org.apache.ignite.cache.CacheWriteSynchronizationMode.FULL_SYNC;
> /**
>  * Tests non collocated join with replicated cache.
>  */
> public class IgniteCacheReplicatedJoinSelfTest extends GridCommonAbstractTest 
> {
> /** */
> public static final String REP_CACHE_NAME = "repCache";
> /** */
> public static final String PART_CACHE_NAME = "partCache";
> /** */
> public static final int REP_CNT = 3;
> /** */
> public static final int PART_CNT = 10_000;
> /** {@inheritDoc} */
> @Override protected IgniteConfiguration getConfiguration(String 
> igniteInstanceName) throws Exception {
> final IgniteConfiguration cfg = 
> super.getConfiguration(igniteInstanceName);
> cfg.setClientMode("client".equals(igniteInstanceName));
> final CacheConfiguration ccfg1 = new 
> CacheConfiguration(PART_CACHE_NAME);
> ccfg1.setCacheMode(PARTITIONED);
> ccfg1.setAtomicityMode(TRANSACTIONAL);
> ccfg1.setWriteSynchronizationMode(FULL_SYNC);
> ccfg1.setIndexedTypes(Integer.class, PartValue.class);
> final CacheConfiguration ccfg2 = new 
> CacheConfiguration(REP_CACHE_NAME);
> ccfg2.setAffinity(new RendezvousAffinityFunction(false, REP_CNT));
> ccfg2.setCacheMode(REPLICATED);
> ccfg2.setAtomicityMode(TRANSACTIONAL);
> ccfg2.setWriteSynchronizationMode(FULL_SYNC);
> ccfg2.setIndexedTypes(Integer.class, RepValue.class);
> cfg.setCacheConfiguration(ccfg1, ccfg2);
> return cfg;
> }
> /**
>  *
>  * @throws Exception
>  */
> public void testJoinNonCollocated() throws Exception {
> startGridsMultiThreaded(3);
> final Ignite client = startGrid("client");
> for (int i = 0; i < REP_CNT; i++)
> client.cache(REP_CACHE_NAME).put(i, new RepValue(i, "rep" + i));
> for (int i = 0; i < PART_CNT; i++)
> client.cache(PART_CACHE_NAME).put(i, new PartValue(i, "part" + i, 
> ((i + 1) % REP_CNT)));
> final FieldsQueryCursor qry = client.cache(PART_CACHE_NAME).
> query(new SqlFieldsQuery("select PartValue._VAL, r._VAL from 
> PartValue, 

[jira] [Assigned] (IGNITE-7147) Implemente connected clusters component

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov reassigned IGNITE-7147:


Resolution: Fixed
  Assignee: Pavel Konstantinov  (was: Alexey Kuznetsov)

Looks good. Merged to master.

> Implemente connected clusters component
> ---
>
> Key: IGNITE-7147
> URL: https://issues.apache.org/jira/browse/IGNITE-7147
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Dmitriy Shabalin
>Assignee: Pavel Konstantinov
> Fix For: 2.4
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-7168) Web Console: Cleanup webAgentDownloadVisibleStates

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-7168:
-
Priority: Minor  (was: Major)

> Web Console: Cleanup webAgentDownloadVisibleStates
> --
>
> Key: IGNITE-7168
> URL: https://issues.apache.org/jira/browse/IGNITE-7168
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Ilya Borisov
>Priority: Minor
> Fix For: 2.4
>
>
> We moved "Agent download" to footer.
> Lets cleanup unused code шт header see "connectedClustersUnvisibleStates" in 
> app\components\web-console-header.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-7168) Web Console: Cleanup webAgentDownloadVisibleStates

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-7168:


 Summary: Web Console: Cleanup webAgentDownloadVisibleStates
 Key: IGNITE-7168
 URL: https://issues.apache.org/jira/browse/IGNITE-7168
 Project: Ignite
  Issue Type: Improvement
  Components: wizards
Reporter: Alexey Kuznetsov
Assignee: Ilya Borisov
 Fix For: 2.4


We moved "Agent download" to footer.
Lets cleanup unused code шт header see "connectedClustersUnvisibleStates" in 
app\components\web-console-header.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (IGNITE-6976) Visor CMD: Add ability to put/get/remove data to caches via command line Visor.

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov edited comment on IGNITE-6976 at 12/12/17 3:48 AM:
--

Tested. Can be merged.


was (Author: pkonstantinov):
Tested

> Visor CMD: Add ability to put/get/remove data to caches via command line 
> Visor.
> ---
>
> Key: IGNITE-6976
> URL: https://issues.apache.org/jira/browse/IGNITE-6976
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Konstantinov
> Fix For: 2.4
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6976) Visor CMD: Add ability to put/get/remove data to caches via command line Visor.

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-6976:


Tested

> Visor CMD: Add ability to put/get/remove data to caches via command line 
> Visor.
> ---
>
> Key: IGNITE-6976
> URL: https://issues.apache.org/jira/browse/IGNITE-6976
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Konstantinov
> Fix For: 2.4
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-7168) Web Console: Cleanup webAgentDownloadVisibleStates

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-7168:
-
Description: 
We moved "Agent download" to footer.
Lets cleanup unused code in header see "connectedClustersUnvisibleStates" in 
app\components\web-console-header.

  was:
We moved "Agent download" to footer.
Lets cleanup unused code шт header see "connectedClustersUnvisibleStates" in 
app\components\web-console-header.


> Web Console: Cleanup webAgentDownloadVisibleStates
> --
>
> Key: IGNITE-7168
> URL: https://issues.apache.org/jira/browse/IGNITE-7168
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Ilya Borisov
>Priority: Minor
> Fix For: 2.4
>
>
> We moved "Agent download" to footer.
> Lets cleanup unused code in header see "connectedClustersUnvisibleStates" in 
> app\components\web-console-header.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-7160) Ignore messages from not alive and failed nodes

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7160:


GitHub user akuramshingg opened a pull request:

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

IGNITE-7160 Ignore messages from not alive and failed nodes.



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

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

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

https://github.com/apache/ignite/pull/3201.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3201


commit a4dd068ab27d864f159d45e4b963215b332b0fac
Author: Alexandr Kuramshin 
Date:   2017-12-12T04:03:20Z

IGNITE-7160 Ignore messages from not alive and failed nodes.

Add TcpDiscoverySplitTest.

commit b8c08ed35262b7b2eaff4557e267338b8803d4dd
Author: Alexandr Kuramshin 
Date:   2017-12-12T04:04:58Z

IGNITE-7160 Ignore messages from not alive and failed nodes.

Fix flaky and mute failing tests.

commit 3f2cdeca44c4d1979f4762a6c67979ceb51e0269
Author: Alexandr Kuramshin 
Date:   2017-12-12T04:24:55Z

IGNITE-7160 Ignore messages from not alive and failed nodes.

SocketReader refactoring.




> Ignore messages from not alive and failed nodes
> ---
>
> Key: IGNITE-7160
> URL: https://issues.apache.org/jira/browse/IGNITE-7160
> Project: Ignite
>  Issue Type: Sub-task
>  Components: general
>Affects Versions: 2.3
>Reporter: Alexandr Kuramshin
>Assignee: Alexandr Kuramshin
>
> Current implementation of {{ServerImpl}} accepts and processes messages from 
> any other remote node even it was failed or removed from the ring.
> Proposed to process only specific messages (which have to be processed in the 
> current node state). Some messages could be silently ignored, receiving other 
> undesirable messages causes the remote socket disconnect.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-7121) visorcmd: there is no output for last command in batch mode in case of using -nq option

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov reassigned IGNITE-7121:


Assignee: Pavel Konstantinov  (was: Alexey Kuznetsov)

Looks good. Merged to master.

> visorcmd: there is no output for last command in batch mode in case of using 
> -nq option
> ---
>
> Key: IGNITE-7121
> URL: https://issues.apache.org/jira/browse/IGNITE-7121
> Project: Ignite
>  Issue Type: Bug
>  Components: visor
>Affects Versions: 2.3
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
> Fix For: 2.4
>
>
> To reproduce try to execute visorcmd in batch mode 
> {code}
> ignitevisorcmd.bat "-nq -b=commands.visor"
> {code}
> with command file
> {code}
> open -cpath=config/your-config.xml
> config
> {code}
> output of 'config' command will not displayed



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-6976) Visor CMD: Add ability to put/get/remove data to caches via command line Visor.

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov reassigned IGNITE-6976:
--

Assignee: Alexey Kuznetsov  (was: Pavel Konstantinov)

> Visor CMD: Add ability to put/get/remove data to caches via command line 
> Visor.
> ---
>
> Key: IGNITE-6976
> URL: https://issues.apache.org/jira/browse/IGNITE-6976
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
> Fix For: 2.4
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-7147) Implemente connected clusters component

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov reassigned IGNITE-7147:
--

Assignee: Alexey Kuznetsov  (was: Pavel Konstantinov)

> Implemente connected clusters component
> ---
>
> Key: IGNITE-7147
> URL: https://issues.apache.org/jira/browse/IGNITE-7147
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Dmitriy Shabalin
>Assignee: Alexey Kuznetsov
> Fix For: 2.4
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-7040) Web console: Invalid user table height

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-7040:


Tested on branch

> Web console: Invalid user table height
> --
>
> Key: IGNITE-7040
> URL: https://issues.apache.org/jira/browse/IGNITE-7040
> Project: Ignite
>  Issue Type: Bug
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
> Fix For: 2.4
>
>
> # Filter user list (f.e. to 2 rows)
> # Change period of showed activity metrics.
> Height of table changed to maximum available but show only filtered rows.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-7040) Web console: Invalid user table height

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov reassigned IGNITE-7040:
--

Assignee: Alexey Kuznetsov  (was: Pavel Konstantinov)

> Web console: Invalid user table height
> --
>
> Key: IGNITE-7040
> URL: https://issues.apache.org/jira/browse/IGNITE-7040
> Project: Ignite
>  Issue Type: Bug
>Reporter: Vasiliy Sisko
>Assignee: Alexey Kuznetsov
> Fix For: 2.4
>
>
> # Filter user list (f.e. to 2 rows)
> # Change period of showed activity metrics.
> Height of table changed to maximum available but show only filtered rows.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-7147) Implemente connected clusters component

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-7147:


Tested.

> Implemente connected clusters component
> ---
>
> Key: IGNITE-7147
> URL: https://issues.apache.org/jira/browse/IGNITE-7147
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Dmitriy Shabalin
>Assignee: Pavel Konstantinov
> Fix For: 2.4
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-7121) visorcmd: there is no output for last command in batch mode in case of using -nq option

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko reassigned IGNITE-7121:
-

Assignee: Alexey Kuznetsov  (was: Vasiliy Sisko)

> visorcmd: there is no output for last command in batch mode in case of using 
> -nq option
> ---
>
> Key: IGNITE-7121
> URL: https://issues.apache.org/jira/browse/IGNITE-7121
> Project: Ignite
>  Issue Type: Bug
>  Components: visor
>Affects Versions: 2.3
>Reporter: Pavel Konstantinov
>Assignee: Alexey Kuznetsov
> Fix For: 2.4
>
>
> To reproduce try to execute visorcmd in batch mode 
> {code}
> ignitevisorcmd.bat "-nq -b=commands.visor"
> {code}
> with command file
> {code}
> open -cpath=config/your-config.xml
> config
> {code}
> output of 'config' command will not displayed



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-7121) visorcmd: there is no output for last command in batch mode in case of using -nq option

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko commented on IGNITE-7121:
---

Fixed. Master merged.

> visorcmd: there is no output for last command in batch mode in case of using 
> -nq option
> ---
>
> Key: IGNITE-7121
> URL: https://issues.apache.org/jira/browse/IGNITE-7121
> Project: Ignite
>  Issue Type: Bug
>  Components: visor
>Affects Versions: 2.3
>Reporter: Pavel Konstantinov
>Assignee: Vasiliy Sisko
> Fix For: 2.4
>
>
> To reproduce try to execute visorcmd in batch mode 
> {code}
> ignitevisorcmd.bat "-nq -b=commands.visor"
> {code}
> with command file
> {code}
> open -cpath=config/your-config.xml
> config
> {code}
> output of 'config' command will not displayed



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-7153) Redis: BufferUnderflowException at GridRedisProtocolParser.readBulkStr for values > 8kb

[Roman Shtykh (JIRA)]

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

Roman Shtykh reassigned IGNITE-7153:


Assignee: Roman Shtykh

> Redis: BufferUnderflowException at GridRedisProtocolParser.readBulkStr for 
> values > 8kb
> ---
>
> Key: IGNITE-7153
> URL: https://issues.apache.org/jira/browse/IGNITE-7153
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 2.3
> Environment: Win, PHP 7, php_redis-3.1.1-7.0
>Reporter: Alexey Popov
>Assignee: Roman Shtykh
>  Labels: redis
>
> Exception:
> {noformat}
> [15:03:23,690][SEVERE][grid-nio-worker-tcp-rest-0-#36][GridTcpRestProtocol] 
> Failed to process selector key [ses=GridSelectorNioSessionImpl 
> [worker=ByteBufferNioClientWorker [readBuf=java.nio.HeapByteBuffer[pos=28 
> lim=8192 cap=8192], super=AbstractNioClientWorker [idx=0, bytesRcvd=0, 
> bytesSent=0, bytesRcvd0=0, bytesSent0=0, select=true, super=GridWorker 
> [name=grid-nio-worker-tcp-rest-0, igniteInstanceName=null, finished=false, 
> hashCode=396395638, interrupted=false, 
> runner=grid-nio-worker-tcp-rest-0-#36]]], writeBuf=null, readBuf=null, 
> inRecovery=null, outRecovery=null, super=GridNioSessionImpl 
> [locAddr=/127.0.0.1:6380, rmtAddr=/127.0.0.1:51794, createTime=1512734602674, 
> closeTime=0, bytesSent=0, bytesRcvd=8192, bytesSent0=0, bytesRcvd0=8192, 
> sndSchedTime=1512734602674, lastSndTime=1512734602674, 
> lastRcvTime=1512734602674, readsPaused=false, 
> filterChain=FilterChain[filters=[GridNioCodecFilter [parser=GridTcpRestParser 
> [jdkMarshaller=JdkMarshaller [], routerClient=false], directMode=false]], 
> accepted=true]]]
> java.nio.BufferUnderflowException
>   at java.nio.HeapByteBuffer.get(HeapByteBuffer.java:151)
>   at 
> org.apache.ignite.internal.processors.rest.protocols.tcp.redis.GridRedisProtocolParser.readBulkStr(GridRedisProtocolParser.java:107)
>   at 
> org.apache.ignite.internal.processors.rest.protocols.tcp.redis.GridRedisProtocolParser.readArray(GridRedisProtocolParser.java:86)
>   at 
> org.apache.ignite.internal.processors.rest.protocols.tcp.GridTcpRestParser.decode(GridTcpRestParser.java:150)
>   at 
> org.apache.ignite.internal.processors.rest.protocols.tcp.GridTcpRestParser.decode(GridTcpRestParser.java:70)
>   at 
> org.apache.ignite.internal.util.nio.GridNioCodecFilter.onMessageReceived(GridNioCodecFilter.java:114)
>   at 
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$HeadFilter.onMessageReceived(GridNioServer.java:3392)
>   at 
> org.apache.ignite.internal.util.nio.GridNioFilterChain.onMessageReceived(GridNioFilterChain.java:175)
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$ByteBufferNioClientWorker.processRead(GridNioServer.java:1096)
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNioServer.java:2272)
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:2048)
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1717)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at java.lang.Thread.run(Thread.java:748)
> [15:03:23,691][SEVERE][grid-nio-worker-tcp-rest-0-#36][GridTcpRestProtocol] 
> Closing NIO session because of unhandled exception.
> class org.apache.ignite.internal.util.nio.GridNioException: null
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNioServer.java:2296)
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:2048)
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1717)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at java.lang.Thread.run(Thread.java:748)
> Caused by: java.nio.BufferUnderflowException
>   at java.nio.HeapByteBuffer.get(HeapByteBuffer.java:151)
>   at 
> org.apache.ignite.internal.processors.rest.protocols.tcp.redis.GridRedisProtocolParser.readBulkStr(GridRedisProtocolParser.java:107)
>   at 
> org.apache.ignite.internal.processors.rest.protocols.tcp.redis.GridRedisProtocolParser.readArray(GridRedisProtocolParser.java:86)
>   at 
> org.apache.ignite.internal.processors.rest.protocols.tcp.GridTcpRestParser.decode(GridTcpRestParser.java:150)
>   at 
> 

[jira] [Commented] (IGNITE-7058) Make out a site page for ACID Transactions

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-7058:
-

The page is ready. Need to come up with a diagram for the page:
http://localhost:8080/features/transactions.html

> Make out a site page for ACID Transactions
> --
>
> Key: IGNITE-7058
> URL: https://issues.apache.org/jira/browse/IGNITE-7058
> Project: Ignite
>  Issue Type: Task
>  Components: site
>Reporter: Denis Magda
>Assignee: Denis Magda
> Fix For: 2.4
>
>
> ACID transactions are a major feature of Ignite and have to be exposed under 
> the Features menu on the site.
> Make out the page covering the following:
> * 2Phase Commit Protocol
> * Pessimistic and Optimistic Modes
> * Deadlock detection



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-7055) Text query for a particular field not working

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7055:


Github user asfgit closed the pull request at:

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


> Text query for a particular field not working
> -
>
> Key: IGNITE-7055
> URL: https://issues.apache.org/jira/browse/IGNITE-7055
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.3
>Reporter: Valentin Kulichenko
>Assignee: Roman Shtykh
> Fix For: 2.4
>
>
> Lucene queries allow to specify a specific field name to search in [1], 
> however this doesn't seem to work in latest versions of Ignite.
> To reproduce, modify {{CacheQueryExample#textQuery}} to use Lucene field 
> expression:
> {code}
> QueryCursor> masters =
> cache.query(new TextQuery(Person.class, "resume:Master"));
> {code}
> This query returns empty result.
> [1] 
> http://lucene.apache.org/core/5_5_2/queryparser/org/apache/lucene/queryparser/classic/package-summary.html#Fields



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (IGNITE-7055) Text query for a particular field not working

[Roman Shtykh (JIRA)]

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

Roman Shtykh closed IGNITE-7055.


> Text query for a particular field not working
> -
>
> Key: IGNITE-7055
> URL: https://issues.apache.org/jira/browse/IGNITE-7055
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.3
>Reporter: Valentin Kulichenko
>Assignee: Roman Shtykh
> Fix For: 2.4
>
>
> Lucene queries allow to specify a specific field name to search in [1], 
> however this doesn't seem to work in latest versions of Ignite.
> To reproduce, modify {{CacheQueryExample#textQuery}} to use Lucene field 
> expression:
> {code}
> QueryCursor> masters =
> cache.query(new TextQuery(Person.class, "resume:Master"));
> {code}
> This query returns empty result.
> [1] 
> http://lucene.apache.org/core/5_5_2/queryparser/org/apache/lucene/queryparser/classic/package-summary.html#Fields



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-7055) Text query for a particular field not working

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko commented on IGNITE-7055:
-

[~roman_s], agree, Ignite being consistent with Ignite makes sense to me :) 
Feel free to merge to master. Thanks!

> Text query for a particular field not working
> -
>
> Key: IGNITE-7055
> URL: https://issues.apache.org/jira/browse/IGNITE-7055
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.3
>Reporter: Valentin Kulichenko
>Assignee: Roman Shtykh
> Fix For: 2.4
>
>
> Lucene queries allow to specify a specific field name to search in [1], 
> however this doesn't seem to work in latest versions of Ignite.
> To reproduce, modify {{CacheQueryExample#textQuery}} to use Lucene field 
> expression:
> {code}
> QueryCursor> masters =
> cache.query(new TextQuery(Person.class, "resume:Master"));
> {code}
> This query returns empty result.
> [1] 
> http://lucene.apache.org/core/5_5_2/queryparser/org/apache/lucene/queryparser/classic/package-summary.html#Fields



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-7167) Optimize 'select count(*) from Table'

[Valentin Kulichenko (JIRA)]

Valentin Kulichenko created IGNITE-7167:
---

 Summary: Optimize 'select count(*) from Table'
 Key: IGNITE-7167
 URL: https://issues.apache.org/jira/browse/IGNITE-7167
 Project: Ignite
  Issue Type: Improvement
  Components: sql
Affects Versions: 2.3
Reporter: Valentin Kulichenko


Currently query like {{select count(*) from Table}} effectively scans the cache 
and take a lot of time for large datasets. Probably makes sense to optimize it 
to use {{IgniteCache#size}} directly when possible.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6740) Java 9: rework DirectBuffer.address() usages

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6740:


GitHub user andrey-kuznetsov opened a pull request:

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

IGNITE-6740: Replaced direct sun.nio.ch.DirectBuffer.address() call with 
reflective one



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

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

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

https://github.com/apache/ignite/pull/3199.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3199


commit 14f5e8ed3ada76464740e5a7d9def469a60e04db
Author: Andrey Kuznetsov 
Date:   2017-12-11T17:47:50Z

IGNITE-6740: Replaced direct sun.nio.ch.DirectBuffer.address() call with 
reflective one.




> Java 9: rework DirectBuffer.address() usages
> 
>
> Key: IGNITE-6740
> URL: https://issues.apache.org/jira/browse/IGNITE-6740
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Reporter: Vladimir Ozerov
>Assignee: Andrey Kuznetsov
> Fix For: 2.4
>
>
> We have two usages of {{DirectBuffer.address()}} method which is no longer 
> accessible in Java 9: 
> 1) {{DirectByteBufferStreamImplV1}}
> 2) {{DirectByteBufferStreamImplV2}}
> Need to rework this code using reflection and/or {{Unsafe}}, so that it 
> compiles and work on all Java versions.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (IGNITE-7056) Prepare Multi-Language support page for the site

[Denis Magda (JIRA)]

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

Denis Magda resolved IGNITE-7056.
-
Resolution: Fixed

> Prepare Multi-Language support page for the site
> 
>
> Key: IGNITE-7056
> URL: https://issues.apache.org/jira/browse/IGNITE-7056
> Project: Ignite
>  Issue Type: Task
>  Components: site
>Reporter: Denis Magda
>Assignee: Denis Magda
> Fix For: 2.4
>
>
> Prepare Ignite's multi-language page that will go under the features menu. 
> The page should encompass the following:
> * Java, .NET and C++ native APIs.
> * Supported drivers and protocols that can be used in various languages.
> * A couple of examples.
> Update the image by combining Java, NET and C++ logos.
> Remove the pages below setting up a redirect the multi-languages page:
> https://ignite.apache.org/features/java.html
> https://ignite.apache.org/features/dotnet.html
> https://ignite.apache.org/features/cpp.html
> https://ignite.apache.org/features/clientprotos.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (IGNITE-7056) Prepare Multi-Language support page for the site

[Denis Magda (JIRA)]

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

Denis Magda closed IGNITE-7056.
---

> Prepare Multi-Language support page for the site
> 
>
> Key: IGNITE-7056
> URL: https://issues.apache.org/jira/browse/IGNITE-7056
> Project: Ignite
>  Issue Type: Task
>  Components: site
>Reporter: Denis Magda
>Assignee: Denis Magda
> Fix For: 2.4
>
>
> Prepare Ignite's multi-language page that will go under the features menu. 
> The page should encompass the following:
> * Java, .NET and C++ native APIs.
> * Supported drivers and protocols that can be used in various languages.
> * A couple of examples.
> Update the image by combining Java, NET and C++ logos.
> Remove the pages below setting up a redirect the multi-languages page:
> https://ignite.apache.org/features/java.html
> https://ignite.apache.org/features/dotnet.html
> https://ignite.apache.org/features/cpp.html
> https://ignite.apache.org/features/clientprotos.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-7056) Prepare Multi-Language support page for the site

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-7056:
-

The page is ready and available at the following address:
http://localhost:8080/features/multilanguage.html

Will be reviewed and merged as a part of umbrella IGNITE-7061 ticket.

> Prepare Multi-Language support page for the site
> 
>
> Key: IGNITE-7056
> URL: https://issues.apache.org/jira/browse/IGNITE-7056
> Project: Ignite
>  Issue Type: Task
>  Components: site
>Reporter: Denis Magda
>Assignee: Denis Magda
> Fix For: 2.4
>
>
> Prepare Ignite's multi-language page that will go under the features menu. 
> The page should encompass the following:
> * Java, .NET and C++ native APIs.
> * Supported drivers and protocols that can be used in various languages.
> * A couple of examples.
> Update the image by combining Java, NET and C++ logos.
> Remove the pages below setting up a redirect the multi-languages page:
> https://ignite.apache.org/features/java.html
> https://ignite.apache.org/features/dotnet.html
> https://ignite.apache.org/features/cpp.html
> https://ignite.apache.org/features/clientprotos.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6880) KNN(k nearest neighbor) algorithm

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6880:


Github user asfgit closed the pull request at:

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


> KNN(k nearest neighbor) algorithm
> -
>
> Key: IGNITE-6880
> URL: https://issues.apache.org/jira/browse/IGNITE-6880
> Project: Ignite
>  Issue Type: New Feature
>  Components: ml
>Reporter: Yury Babak
>Assignee: Aleksey Zinoviev
>  Labels: important
> Fix For: 2.4
>
>
> We want to add KNN to Apache Ignite ML module.
> Our implementation should support two modes:
> * KNN-classifier(in this mode the output is a class membership. An object is 
> classified by a majority vote of its neighbors, with the object being 
> assigned to the class most common among its k nearest neighbors (k is a 
> positive integer, typically small). If k = 1, then the object is simply 
> assigned to the class of that single nearest neighbor)
> * KNN-regression(the output is the property value for the object. This value 
> is the average of the values of its k nearest neighbors.)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-3932) Return value for remove or putIfAbsent can be lost with onePhaseCommit

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov reassigned IGNITE-3932:


Assignee: (was: Anton Vinogradov)

> Return value for remove or putIfAbsent can be lost with onePhaseCommit
> --
>
> Key: IGNITE-3932
> URL: https://issues.apache.org/jira/browse/IGNITE-3932
> Project: Ignite
>  Issue Type: Bug
>Reporter: Anton Vinogradov
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-3303) Apache Flink Integration - Flink source to run a continuous query against one or multiple caches

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov reassigned IGNITE-3303:


Assignee: (was: Anton Vinogradov)

> Apache Flink Integration - Flink source to run a continuous query against one 
> or multiple caches
> 
>
> Key: IGNITE-3303
> URL: https://issues.apache.org/jira/browse/IGNITE-3303
> Project: Ignite
>  Issue Type: New Feature
>  Components: streaming
>Reporter: Saikat Maitra
> Attachments: Screen Shot 2016-10-07 at 12.44.47 AM.png, 
> testFlinkIgniteSourceWithLargeBatch.log, win7.PNG
>
>
> Apache Flink integration 
> +++ *Ignite as a bidirectional Connector* +++
> As a Flink source => run a continuous query against one or multiple
> caches [4].
> Related discussion : 
> http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Flink-lt-gt-Apache-Ignite-integration-td8163.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-5108) Fix JavaDoc warning

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov reassigned IGNITE-5108:


Assignee: (was: Anton Vinogradov)

> Fix JavaDoc warning
> ---
>
> Key: IGNITE-5108
> URL: https://issues.apache.org/jira/browse/IGNITE-5108
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 2.0
>Reporter: Vladimir Ozerov
>
> Currently JavaDoc build fails with the warnings below. Need to understand how 
> to avoid warning about duplicate {{package-info}} and check what causes 
> warning in {{HibernateRegionFactory}}.
> {code}
> [10:29:33][Step 7/7] [WARNING] Javadoc Warnings
> [10:29:33][Step 7/7] [WARNING] 
> /data/teamcity/work/a9543228d3ee824c/modules/hibernate-4.2/src/main/java/org/apache/ignite/cache/hibernate/package-info.java:24:
>  warning: a package-info.java file has already been seen for package 
> org.apache.ignite.cache.hibernate
> [10:29:33][Step 7/7] [WARNING] package org.apache.ignite.cache.hibernate;
> [10:29:33][Step 7/7] [WARNING] ^
> [10:29:33][Step 7/7] [WARNING] javadoc: warning - Multiple sources of package 
> comments found for package "org.apache.ignite.cache.hibernate"
> [10:29:33][Step 7/7] [WARNING] 
> /data/teamcity/work/a9543228d3ee824c/modules/hibernate-core/src/main/java/org/apache/ignite/cache/hibernate/package-info.java:24:
>  warning: a package-info.java file has already been seen for package 
> org.apache.ignite.cache.hibernate
> [10:29:33][Step 7/7] [WARNING] package org.apache.ignite.cache.hibernate;
> [10:29:33][Step 7/7] [WARNING] ^
> [10:29:33][Step 7/7] [WARNING] 
> /data/teamcity/work/a9543228d3ee824c/modules/hibernate-4.2/src/main/java/org/apache/ignite/cache/store/hibernate/package-info.java:22:
>  warning: a package-info.java file has already been seen for package 
> org.apache.ignite.cache.store.hibernate
> [10:29:33][Step 7/7] [WARNING] package 
> org.apache.ignite.cache.store.hibernate;
> [10:29:33][Step 7/7] [WARNING] ^
> [10:29:33][Step 7/7] [WARNING] javadoc: warning - Multiple sources of package 
> comments found for package "org.apache.ignite.cache.store.hibernate"
> [10:29:33][Step 7/7] [WARNING] 
> /data/teamcity/work/a9543228d3ee824c/modules/hibernate-4.2/src/main/java/org/apache/ignite/cache/hibernate/HibernateRegionFactory.java:24:
>  error: cannot find symbol
> [10:29:33][Step 7/7] [WARNING] import org.hibernate.cache.spi.CacheKey;
> [10:29:33][Step 7/7] [WARNING] ^
> [10:29:33][Step 7/7] [WARNING] symbol:   class CacheKey
> [10:29:33][Step 7/7] [WARNING] location: package org.hibernate.cache.spi
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-7165) Re-balancing is cancelled if client node joins

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov reassigned IGNITE-7165:


Assignee: Anton Vinogradov

> Re-balancing is cancelled if client node joins
> --
>
> Key: IGNITE-7165
> URL: https://issues.apache.org/jira/browse/IGNITE-7165
> Project: Ignite
>  Issue Type: Bug
>Reporter: Mikhail Cherkasov
>Assignee: Anton Vinogradov
>Priority: Critical
>
> Re-balancing is canceled if client node joins. Re-balancing can take hours 
> and each time when client node joins it starts again:
> [15:10:05,700][INFO][disco-event-worker-#61%statement_grid%][GridDiscoveryManager]
>  Added new node to topology: TcpDiscoveryNode 
> [id=979cf868-1c37-424a-9ad1-12db501f32ef, addrs=[0:0:0:0:0:0:0:1, 127.0.0.1, 
> 172.31.16.213], sockAddrs=[/0:0:0:0:0:0:0:1:0, /127.0.0.1:0, 
> /172.31.16.213:0], discPort=0, order=36, intOrder=24, 
> lastExchangeTime=1512907805688, loc=false, ver=2.3.1#20171129-sha1:4b1ec0fe, 
> isClient=true]
> [15:10:05,701][INFO][disco-event-worker-#61%statement_grid%][GridDiscoveryManager]
>  Topology snapshot [ver=36, servers=7, clients=5, CPUs=128, heap=160.0GB]
> [15:10:05,702][INFO][exchange-worker-#62%statement_grid%][time] Started 
> exchange init [topVer=AffinityTopologyVersion [topVer=36, minorTopVer=0], 
> crd=false, evt=NODE_JOINED, evtNode=979cf868-1c37-424a-9ad1-12db501f32ef, 
> customEvt=null, allowMerge=true]
> [15:10:05,702][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionsExchangeFuture]
>  Finish exchange future [startVer=AffinityTopologyVersion [topVer=36, 
> minorTopVer=0], resVer=AffinityTopologyVersion [topVer=36, minorTopVer=0], 
> err=null]
> [15:10:05,702][INFO][exchange-worker-#62%statement_grid%][time] Finished 
> exchange init [topVer=AffinityTopologyVersion [topVer=36, minorTopVer=0], 
> crd=false]
> [15:10:05,703][INFO][exchange-worker-#62%statement_grid%][GridCachePartitionExchangeManager]
>  Skipping rebalancing (nothing scheduled) [top=AffinityTopologyVersion 
> [topVer=36, minorTopVer=0], evt=NODE_JOINED, 
> node=979cf868-1c37-424a-9ad1-12db501f32ef]
> [15:10:08,706][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander]
>  Cancelled rebalancing from all nodes [topology=AffinityTopologyVersion 
> [topVer=35, minorTopVer=0]]
> [15:10:08,707][INFO][exchange-worker-#62%statement_grid%][GridCachePartitionExchangeManager]
>  Rebalancing scheduled [order=[statementp]]
> [15:10:08,707][INFO][exchange-worker-#62%statement_grid%][GridCachePartitionExchangeManager]
>  Rebalancing started [top=null, evt=NODE_JOINED, 
> node=a8be3c14-9add-48c3-b099-3fd304cfdbf4]
> [15:10:08,707][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander]
>  Starting rebalancing [mode=ASYNC, 
> fromNode=2f6bde48-ffb5-4815-bd32-df4e57dc13e0, partitionsCount=18, 
> topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], 
> updateSeq=-1754630006]
> [15:10:08,707][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander]
>  Starting rebalancing [mode=ASYNC, 
> fromNode=35d01141-4dce-47dd-adf6-a4f3b2bb9da9, partitionsCount=15, 
> topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], 
> updateSeq=-1754630006]
> [15:10:08,708][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander]
>  Starting rebalancing [mode=ASYNC, 
> fromNode=b3a8be53-e61f-4023-a906-a265923837ba, partitionsCount=15, 
> topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], 
> updateSeq=-1754630006]
> [15:10:08,708][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander]
>  Starting rebalancing [mode=ASYNC, 
> fromNode=f825cb4e-7dcc-405f-a40d-c1dc1a3ade5a, partitionsCount=12, 
> topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], 
> updateSeq=-1754630006]
> [15:10:08,708][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander]
>  Starting rebalancing [mode=ASYNC, 
> fromNode=4ae1db91-8b88-4180-a84b-127a303959e9, partitionsCount=11, 
> topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], 
> updateSeq=-1754630006]
> [15:10:08,708][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander]
>  Starting rebalancing [mode=ASYNC, 
> fromNode=7c286481-7638-49e4-8c68-fa6aa65d8b76, partitionsCount=18, 
> topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], 
> updateSeq=-1754630006]
> so in clusters with a big amount of data and the frequent client left/join 
> events this means that a new server will never receive its partitions.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-7165) Re-balancing is cancelled if client node joins

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov commented on IGNITE-7165:
--

Agree.

> Re-balancing is cancelled if client node joins
> --
>
> Key: IGNITE-7165
> URL: https://issues.apache.org/jira/browse/IGNITE-7165
> Project: Ignite
>  Issue Type: Bug
>Reporter: Mikhail Cherkasov
>Priority: Critical
>
> Re-balancing is canceled if client node joins. Re-balancing can take hours 
> and each time when client node joins it starts again:
> [15:10:05,700][INFO][disco-event-worker-#61%statement_grid%][GridDiscoveryManager]
>  Added new node to topology: TcpDiscoveryNode 
> [id=979cf868-1c37-424a-9ad1-12db501f32ef, addrs=[0:0:0:0:0:0:0:1, 127.0.0.1, 
> 172.31.16.213], sockAddrs=[/0:0:0:0:0:0:0:1:0, /127.0.0.1:0, 
> /172.31.16.213:0], discPort=0, order=36, intOrder=24, 
> lastExchangeTime=1512907805688, loc=false, ver=2.3.1#20171129-sha1:4b1ec0fe, 
> isClient=true]
> [15:10:05,701][INFO][disco-event-worker-#61%statement_grid%][GridDiscoveryManager]
>  Topology snapshot [ver=36, servers=7, clients=5, CPUs=128, heap=160.0GB]
> [15:10:05,702][INFO][exchange-worker-#62%statement_grid%][time] Started 
> exchange init [topVer=AffinityTopologyVersion [topVer=36, minorTopVer=0], 
> crd=false, evt=NODE_JOINED, evtNode=979cf868-1c37-424a-9ad1-12db501f32ef, 
> customEvt=null, allowMerge=true]
> [15:10:05,702][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionsExchangeFuture]
>  Finish exchange future [startVer=AffinityTopologyVersion [topVer=36, 
> minorTopVer=0], resVer=AffinityTopologyVersion [topVer=36, minorTopVer=0], 
> err=null]
> [15:10:05,702][INFO][exchange-worker-#62%statement_grid%][time] Finished 
> exchange init [topVer=AffinityTopologyVersion [topVer=36, minorTopVer=0], 
> crd=false]
> [15:10:05,703][INFO][exchange-worker-#62%statement_grid%][GridCachePartitionExchangeManager]
>  Skipping rebalancing (nothing scheduled) [top=AffinityTopologyVersion 
> [topVer=36, minorTopVer=0], evt=NODE_JOINED, 
> node=979cf868-1c37-424a-9ad1-12db501f32ef]
> [15:10:08,706][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander]
>  Cancelled rebalancing from all nodes [topology=AffinityTopologyVersion 
> [topVer=35, minorTopVer=0]]
> [15:10:08,707][INFO][exchange-worker-#62%statement_grid%][GridCachePartitionExchangeManager]
>  Rebalancing scheduled [order=[statementp]]
> [15:10:08,707][INFO][exchange-worker-#62%statement_grid%][GridCachePartitionExchangeManager]
>  Rebalancing started [top=null, evt=NODE_JOINED, 
> node=a8be3c14-9add-48c3-b099-3fd304cfdbf4]
> [15:10:08,707][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander]
>  Starting rebalancing [mode=ASYNC, 
> fromNode=2f6bde48-ffb5-4815-bd32-df4e57dc13e0, partitionsCount=18, 
> topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], 
> updateSeq=-1754630006]
> [15:10:08,707][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander]
>  Starting rebalancing [mode=ASYNC, 
> fromNode=35d01141-4dce-47dd-adf6-a4f3b2bb9da9, partitionsCount=15, 
> topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], 
> updateSeq=-1754630006]
> [15:10:08,708][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander]
>  Starting rebalancing [mode=ASYNC, 
> fromNode=b3a8be53-e61f-4023-a906-a265923837ba, partitionsCount=15, 
> topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], 
> updateSeq=-1754630006]
> [15:10:08,708][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander]
>  Starting rebalancing [mode=ASYNC, 
> fromNode=f825cb4e-7dcc-405f-a40d-c1dc1a3ade5a, partitionsCount=12, 
> topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], 
> updateSeq=-1754630006]
> [15:10:08,708][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander]
>  Starting rebalancing [mode=ASYNC, 
> fromNode=4ae1db91-8b88-4180-a84b-127a303959e9, partitionsCount=11, 
> topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], 
> updateSeq=-1754630006]
> [15:10:08,708][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander]
>  Starting rebalancing [mode=ASYNC, 
> fromNode=7c286481-7638-49e4-8c68-fa6aa65d8b76, partitionsCount=18, 
> topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], 
> updateSeq=-1754630006]
> so in clusters with a big amount of data and the frequent client left/join 
> events this means that a new server will never receive its partitions.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-7147) Implemente connected clusters component

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov reassigned IGNITE-7147:


Assignee: Pavel Konstantinov  (was: Alexey Kuznetsov)

> Implemente connected clusters component
> ---
>
> Key: IGNITE-7147
> URL: https://issues.apache.org/jira/browse/IGNITE-7147
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Dmitriy Shabalin
>Assignee: Pavel Konstantinov
> Fix For: 2.4
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-7165) Re-balancing is cancelled if client node joins

[Yakov Zhdanov (JIRA)]

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

Yakov Zhdanov commented on IGNITE-7165:
---

[~avinogradov] It looks like we can continue rebalancing if assignment has not 
been changed and local node still needs the partition being rebalanced. No 
matter how topology changed.

> Re-balancing is cancelled if client node joins
> --
>
> Key: IGNITE-7165
> URL: https://issues.apache.org/jira/browse/IGNITE-7165
> Project: Ignite
>  Issue Type: Bug
>Reporter: Mikhail Cherkasov
>Priority: Critical
>
> Re-balancing is canceled if client node joins. Re-balancing can take hours 
> and each time when client node joins it starts again:
> [15:10:05,700][INFO][disco-event-worker-#61%statement_grid%][GridDiscoveryManager]
>  Added new node to topology: TcpDiscoveryNode 
> [id=979cf868-1c37-424a-9ad1-12db501f32ef, addrs=[0:0:0:0:0:0:0:1, 127.0.0.1, 
> 172.31.16.213], sockAddrs=[/0:0:0:0:0:0:0:1:0, /127.0.0.1:0, 
> /172.31.16.213:0], discPort=0, order=36, intOrder=24, 
> lastExchangeTime=1512907805688, loc=false, ver=2.3.1#20171129-sha1:4b1ec0fe, 
> isClient=true]
> [15:10:05,701][INFO][disco-event-worker-#61%statement_grid%][GridDiscoveryManager]
>  Topology snapshot [ver=36, servers=7, clients=5, CPUs=128, heap=160.0GB]
> [15:10:05,702][INFO][exchange-worker-#62%statement_grid%][time] Started 
> exchange init [topVer=AffinityTopologyVersion [topVer=36, minorTopVer=0], 
> crd=false, evt=NODE_JOINED, evtNode=979cf868-1c37-424a-9ad1-12db501f32ef, 
> customEvt=null, allowMerge=true]
> [15:10:05,702][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionsExchangeFuture]
>  Finish exchange future [startVer=AffinityTopologyVersion [topVer=36, 
> minorTopVer=0], resVer=AffinityTopologyVersion [topVer=36, minorTopVer=0], 
> err=null]
> [15:10:05,702][INFO][exchange-worker-#62%statement_grid%][time] Finished 
> exchange init [topVer=AffinityTopologyVersion [topVer=36, minorTopVer=0], 
> crd=false]
> [15:10:05,703][INFO][exchange-worker-#62%statement_grid%][GridCachePartitionExchangeManager]
>  Skipping rebalancing (nothing scheduled) [top=AffinityTopologyVersion 
> [topVer=36, minorTopVer=0], evt=NODE_JOINED, 
> node=979cf868-1c37-424a-9ad1-12db501f32ef]
> [15:10:08,706][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander]
>  Cancelled rebalancing from all nodes [topology=AffinityTopologyVersion 
> [topVer=35, minorTopVer=0]]
> [15:10:08,707][INFO][exchange-worker-#62%statement_grid%][GridCachePartitionExchangeManager]
>  Rebalancing scheduled [order=[statementp]]
> [15:10:08,707][INFO][exchange-worker-#62%statement_grid%][GridCachePartitionExchangeManager]
>  Rebalancing started [top=null, evt=NODE_JOINED, 
> node=a8be3c14-9add-48c3-b099-3fd304cfdbf4]
> [15:10:08,707][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander]
>  Starting rebalancing [mode=ASYNC, 
> fromNode=2f6bde48-ffb5-4815-bd32-df4e57dc13e0, partitionsCount=18, 
> topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], 
> updateSeq=-1754630006]
> [15:10:08,707][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander]
>  Starting rebalancing [mode=ASYNC, 
> fromNode=35d01141-4dce-47dd-adf6-a4f3b2bb9da9, partitionsCount=15, 
> topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], 
> updateSeq=-1754630006]
> [15:10:08,708][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander]
>  Starting rebalancing [mode=ASYNC, 
> fromNode=b3a8be53-e61f-4023-a906-a265923837ba, partitionsCount=15, 
> topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], 
> updateSeq=-1754630006]
> [15:10:08,708][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander]
>  Starting rebalancing [mode=ASYNC, 
> fromNode=f825cb4e-7dcc-405f-a40d-c1dc1a3ade5a, partitionsCount=12, 
> topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], 
> updateSeq=-1754630006]
> [15:10:08,708][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander]
>  Starting rebalancing [mode=ASYNC, 
> fromNode=4ae1db91-8b88-4180-a84b-127a303959e9, partitionsCount=11, 
> topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], 
> updateSeq=-1754630006]
> [15:10:08,708][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander]
>  Starting rebalancing [mode=ASYNC, 
> fromNode=7c286481-7638-49e4-8c68-fa6aa65d8b76, partitionsCount=18, 
> topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], 
> updateSeq=-1754630006]
> so in clusters with a big amount of data and the frequent client left/join 
> events this means that a new server will never receive its partitions.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-7166) SQL join with partition and replicated caches fails if number of partitions is too low.

[Alexei Scherbakov (JIRA)]

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

Alexei Scherbakov updated IGNITE-7166:
--
Description: 
If not all nodes receive primary partition, we fail to validate nodes predicate:

{code}
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor#stableDataNodes
...
else if (!isReplicatedOnly && extraCctx.isReplicated()) {
if (!extraNodes.containsAll(nodes))
{code}

Solution: remove from validation nodes containing no primary partitions for 
replicated cache.

Reproducer:

{noformat}
/*
 * Licensed to the Apache Software Foundation (ASF) under one or more
 * contributor license agreements.  See the NOTICE file distributed with
 * this work for additional information regarding copyright ownership.
 * The ASF licenses this file to You under the Apache License, Version 2.0
 * (the "License"); you may not use this file except in compliance with
 * the License.  You may obtain a copy of the License at
 *
 *  http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 */

package org.apache.ignite.internal.processors.cache.distributed.replicated;

import java.util.List;
import org.apache.ignite.Ignite;
import org.apache.ignite.cache.affinity.rendezvous.RendezvousAffinityFunction;
import org.apache.ignite.cache.query.FieldsQueryCursor;
import org.apache.ignite.cache.query.SqlFieldsQuery;
import org.apache.ignite.cache.query.annotations.QuerySqlField;
import org.apache.ignite.configuration.CacheConfiguration;
import org.apache.ignite.configuration.IgniteConfiguration;
import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;

import static org.apache.ignite.cache.CacheAtomicityMode.TRANSACTIONAL;
import static org.apache.ignite.cache.CacheMode.PARTITIONED;
import static org.apache.ignite.cache.CacheMode.REPLICATED;
import static org.apache.ignite.cache.CacheWriteSynchronizationMode.FULL_SYNC;

/**
 * Tests non collocated join with replicated cache.
 */
public class IgniteCacheReplicatedJoinSelfTest extends GridCommonAbstractTest {
/** */
public static final String REP_CACHE_NAME = "repCache";

/** */
public static final String PART_CACHE_NAME = "partCache";

/** */
public static final int REP_CNT = 3;

/** */
public static final int PART_CNT = 10_000;

/** {@inheritDoc} */
@Override protected IgniteConfiguration getConfiguration(String 
igniteInstanceName) throws Exception {
final IgniteConfiguration cfg = 
super.getConfiguration(igniteInstanceName);

cfg.setClientMode("client".equals(igniteInstanceName));

final CacheConfiguration ccfg1 = new 
CacheConfiguration(PART_CACHE_NAME);
ccfg1.setCacheMode(PARTITIONED);
ccfg1.setAtomicityMode(TRANSACTIONAL);
ccfg1.setWriteSynchronizationMode(FULL_SYNC);
ccfg1.setIndexedTypes(Integer.class, PartValue.class);

final CacheConfiguration ccfg2 = new CacheConfiguration(REP_CACHE_NAME);
ccfg2.setAffinity(new RendezvousAffinityFunction(false, REP_CNT));
ccfg2.setCacheMode(REPLICATED);
ccfg2.setAtomicityMode(TRANSACTIONAL);
ccfg2.setWriteSynchronizationMode(FULL_SYNC);
ccfg2.setIndexedTypes(Integer.class, RepValue.class);

cfg.setCacheConfiguration(ccfg1, ccfg2);

return cfg;
}

/**
 *
 * @throws Exception
 */
public void testJoinNonCollocated() throws Exception {
startGridsMultiThreaded(3);

final Ignite client = startGrid("client");

for (int i = 0; i < REP_CNT; i++)
client.cache(REP_CACHE_NAME).put(i, new RepValue(i, "rep" + i));

for (int i = 0; i < PART_CNT; i++)
client.cache(PART_CACHE_NAME).put(i, new PartValue(i, "part" + i, 
((i + 1) % REP_CNT)));

final FieldsQueryCursor qry = client.cache(PART_CACHE_NAME).
query(new SqlFieldsQuery("select PartValue._VAL, r._VAL from 
PartValue, \"repCache\".RepValue as r where PartValue.repId=r.id"));

final List all = qry.getAll();

assertEquals(10_000, all.size());

for (List objects : all) {
final PartValue pv = (PartValue)objects.get(0);
final RepValue rv = (RepValue)objects.get(1);

assertNotNull(rv);

assertEquals(rv.getId(), pv.getRepId());
}
}

/** */
public static class PartValue {
/** Id. */
@QuerySqlField
private int id;

/** Name. */
@QuerySqlField
private String name;

/** Rep id. */
@QuerySqlField
private int 

[jira] [Commented] (IGNITE-7144) Java 9: fix build issue with tools.jar not found

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov commented on IGNITE-7144:
--

[~vveider]
Please see my comments at upsource.

> Java 9: fix build issue with tools.jar not found
> 
>
> Key: IGNITE-7144
> URL: https://issues.apache.org/jira/browse/IGNITE-7144
> Project: Ignite
>  Issue Type: Bug
>Reporter: Peter Ivanov
>Assignee: Peter Ivanov
>
> {code}
> [ERROR] Failed to execute goal on project ignite-tools: Could not resolve 
> dependencies for project org.apache.ignite:ignite-tools:jar:2.4.0-SNAPSHOT: 
> Could not find artifact com.sun:tools:jar:9.0.1 at specified path 
> /Library/Java/JavaVirtualMachines/jdk-9.0.1.jdk/Contents/Home/../lib/tools.jar
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-7166) SQL join with partition and replicated caches fails if number of partitions is too low.

[Alexei Scherbakov (JIRA)]

Alexei Scherbakov created IGNITE-7166:
-

 Summary: SQL join with partition and replicated caches fails if 
number of partitions is too low.
 Key: IGNITE-7166
 URL: https://issues.apache.org/jira/browse/IGNITE-7166
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.3
Reporter: Alexei Scherbakov
 Fix For: 2.4


Reproducer:

{noformat}
/*
 * Licensed to the Apache Software Foundation (ASF) under one or more
 * contributor license agreements.  See the NOTICE file distributed with
 * this work for additional information regarding copyright ownership.
 * The ASF licenses this file to You under the Apache License, Version 2.0
 * (the "License"); you may not use this file except in compliance with
 * the License.  You may obtain a copy of the License at
 *
 *  http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 */

package org.apache.ignite.internal.processors.cache.distributed.replicated;

import java.util.List;
import org.apache.ignite.Ignite;
import org.apache.ignite.cache.affinity.rendezvous.RendezvousAffinityFunction;
import org.apache.ignite.cache.query.FieldsQueryCursor;
import org.apache.ignite.cache.query.SqlFieldsQuery;
import org.apache.ignite.cache.query.annotations.QuerySqlField;
import org.apache.ignite.configuration.CacheConfiguration;
import org.apache.ignite.configuration.IgniteConfiguration;
import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;

import static org.apache.ignite.cache.CacheAtomicityMode.TRANSACTIONAL;
import static org.apache.ignite.cache.CacheMode.PARTITIONED;
import static org.apache.ignite.cache.CacheMode.REPLICATED;
import static org.apache.ignite.cache.CacheWriteSynchronizationMode.FULL_SYNC;

/**
 * Tests non collocated join with replicated cache.
 */
public class IgniteCacheReplicatedJoinSelfTest extends GridCommonAbstractTest {
/** */
public static final String REP_CACHE_NAME = "repCache";

/** */
public static final String PART_CACHE_NAME = "partCache";

/** */
public static final int REP_CNT = 3;

/** */
public static final int PART_CNT = 10_000;

/** {@inheritDoc} */
@Override protected IgniteConfiguration getConfiguration(String 
igniteInstanceName) throws Exception {
final IgniteConfiguration cfg = 
super.getConfiguration(igniteInstanceName);

cfg.setClientMode("client".equals(igniteInstanceName));

final CacheConfiguration ccfg1 = new 
CacheConfiguration(PART_CACHE_NAME);
ccfg1.setCacheMode(PARTITIONED);
ccfg1.setAtomicityMode(TRANSACTIONAL);
ccfg1.setWriteSynchronizationMode(FULL_SYNC);
ccfg1.setIndexedTypes(Integer.class, PartValue.class);

final CacheConfiguration ccfg2 = new CacheConfiguration(REP_CACHE_NAME);
ccfg2.setAffinity(new RendezvousAffinityFunction(false, REP_CNT));
ccfg2.setCacheMode(REPLICATED);
ccfg2.setAtomicityMode(TRANSACTIONAL);
ccfg2.setWriteSynchronizationMode(FULL_SYNC);
ccfg2.setIndexedTypes(Integer.class, RepValue.class);

cfg.setCacheConfiguration(ccfg1, ccfg2);

return cfg;
}

/**
 *
 * @throws Exception
 */
public void testJoinNonCollocated() throws Exception {
startGridsMultiThreaded(3);

final Ignite client = startGrid("client");

for (int i = 0; i < REP_CNT; i++)
client.cache(REP_CACHE_NAME).put(i, new RepValue(i, "rep" + i));

for (int i = 0; i < PART_CNT; i++)
client.cache(PART_CACHE_NAME).put(i, new PartValue(i, "part" + i, 
((i + 1) % REP_CNT)));

final FieldsQueryCursor qry = client.cache(PART_CACHE_NAME).
query(new SqlFieldsQuery("select PartValue._VAL, r._VAL from 
PartValue, \"repCache\".RepValue as r where PartValue.repId=r.id"));

final List all = qry.getAll();

assertEquals(10_000, all.size());

for (List objects : all) {
final PartValue pv = (PartValue)objects.get(0);
final RepValue rv = (RepValue)objects.get(1);

assertNotNull(rv);

assertEquals(rv.getId(), pv.getRepId());
}
}

/** */
public static class PartValue {
/** Id. */
@QuerySqlField
private int id;

/** Name. */
@QuerySqlField
private String name;

/** Rep id. */
@QuerySqlField
private int repId;

/**
 * @param id Id.
 * @param name Name.
 * @param repId Rep id.
 */
public PartValue(int id, String name, int repId) {
   

[jira] [Assigned] (IGNITE-4910) Add copyOnRead property for near cache.

[Vyacheslav Koptilin (JIRA)]

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

Vyacheslav Koptilin reassigned IGNITE-4910:
---

Assignee: Vyacheslav Koptilin

> Add copyOnRead property for near cache.
> ---
>
> Key: IGNITE-4910
> URL: https://issues.apache.org/jira/browse/IGNITE-4910
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: 2.1
>Reporter: Maksim Kozlov
>Assignee: Vyacheslav Koptilin
>
> Add {{setCopyOnRead}} to {{NearCacheConfiguration}} class.
> Continuation of the task from the ticket 
> [https://issues.apache.org/jira/browse/IGNITE-2558].



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-7145) Visor CMD: Fix tests for: Ignite Visor Console

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov reassigned IGNITE-7145:


Resolution: Fixed
  Assignee: Pavel Konstantinov  (was: Alexey Kuznetsov)

Looks good. Merged to master.

> Visor CMD: Fix tests for: Ignite Visor Console
> --
>
> Key: IGNITE-7145
> URL: https://issues.apache.org/jira/browse/IGNITE-7145
> Project: Ignite
>  Issue Type: Test
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
> Fix For: 2.4
>
>
> https://ci.ignite.apache.org/viewLog.html?buildId=984720=buildResultsDiv=Ignite20Tests_IgniteVisorConsoleTestDetach



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-7145) Visor CMD: Fix tests for: Ignite Visor Console

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-7145:
-
Fix Version/s: 2.4

> Visor CMD: Fix tests for: Ignite Visor Console
> --
>
> Key: IGNITE-7145
> URL: https://issues.apache.org/jira/browse/IGNITE-7145
> Project: Ignite
>  Issue Type: Test
>Reporter: Vasiliy Sisko
>Assignee: Alexey Kuznetsov
> Fix For: 2.4
>
>
> https://ci.ignite.apache.org/viewLog.html?buildId=984720=buildResultsDiv=Ignite20Tests_IgniteVisorConsoleTestDetach



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-7114) CPP: C++ node can't start without java examples folder

[Sergey Kalashnikov (JIRA)]

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

Sergey Kalashnikov commented on IGNITE-7114:


[~isapego], I did review the code and I'm OK with the changes.

> CPP: C++ node can't start without java examples folder
> --
>
> Key: IGNITE-7114
> URL: https://issues.apache.org/jira/browse/IGNITE-7114
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 2.1
>Reporter: Evgenii Zhuravlev
>Assignee: Igor Sapego
>Priority: Critical
> Fix For: 2.4
>
> Attachments: sample.png
>
>
> Error message: 
> ERROR: Java classpath is empty (did you set {{IGNITE_HOME}} environment 
> variable?)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-7157) Deadlock on partition eviction from multiple threads.

[Andrey Gura (JIRA)]

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

Andrey Gura commented on IGNITE-7157:
-

Merged to master branch.

> Deadlock on partition eviction from multiple threads.
> -
>
> Key: IGNITE-7157
> URL: https://issues.apache.org/jira/browse/IGNITE-7157
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
> Fix For: 2.4
>
> Attachments: thread-dump
>
>
> When node receive partition update message, it acquire partition and 
> checkpoint locks in different order than asyncronous eviction.
> PFA thread dump.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-7121) visorcmd: there is no output for last command in batch mode in case of using -nq option

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov reassigned IGNITE-7121:


Assignee: Vasiliy Sisko  (was: Alexey Kuznetsov)

I reviewed code.
Can you move adding "\n" logic near line VisorConsole.scala:166?

> visorcmd: there is no output for last command in batch mode in case of using 
> -nq option
> ---
>
> Key: IGNITE-7121
> URL: https://issues.apache.org/jira/browse/IGNITE-7121
> Project: Ignite
>  Issue Type: Bug
>  Components: visor
>Affects Versions: 2.3
>Reporter: Pavel Konstantinov
>Assignee: Vasiliy Sisko
> Fix For: 2.4
>
>
> To reproduce try to execute visorcmd in batch mode 
> {code}
> ignitevisorcmd.bat "-nq -b=commands.visor"
> {code}
> with command file
> {code}
> open -cpath=config/your-config.xml
> config
> {code}
> output of 'config' command will not displayed



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-7165) Re-balancing is cancelled if client node joins

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov commented on IGNITE-7165:
--

It looks like we can continue rebalancing in case joined/left node is a client.

> Re-balancing is cancelled if client node joins
> --
>
> Key: IGNITE-7165
> URL: https://issues.apache.org/jira/browse/IGNITE-7165
> Project: Ignite
>  Issue Type: Bug
>Reporter: Mikhail Cherkasov
>Assignee: Anton Vinogradov
>Priority: Critical
>
> Re-balancing is canceled if client node joins. Re-balancing can take hours 
> and each time when client node joins it starts again:
> [15:10:05,700][INFO][disco-event-worker-#61%statement_grid%][GridDiscoveryManager]
>  Added new node to topology: TcpDiscoveryNode 
> [id=979cf868-1c37-424a-9ad1-12db501f32ef, addrs=[0:0:0:0:0:0:0:1, 127.0.0.1, 
> 172.31.16.213], sockAddrs=[/0:0:0:0:0:0:0:1:0, /127.0.0.1:0, 
> /172.31.16.213:0], discPort=0, order=36, intOrder=24, 
> lastExchangeTime=1512907805688, loc=false, ver=2.3.1#20171129-sha1:4b1ec0fe, 
> isClient=true]
> [15:10:05,701][INFO][disco-event-worker-#61%statement_grid%][GridDiscoveryManager]
>  Topology snapshot [ver=36, servers=7, clients=5, CPUs=128, heap=160.0GB]
> [15:10:05,702][INFO][exchange-worker-#62%statement_grid%][time] Started 
> exchange init [topVer=AffinityTopologyVersion [topVer=36, minorTopVer=0], 
> crd=false, evt=NODE_JOINED, evtNode=979cf868-1c37-424a-9ad1-12db501f32ef, 
> customEvt=null, allowMerge=true]
> [15:10:05,702][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionsExchangeFuture]
>  Finish exchange future [startVer=AffinityTopologyVersion [topVer=36, 
> minorTopVer=0], resVer=AffinityTopologyVersion [topVer=36, minorTopVer=0], 
> err=null]
> [15:10:05,702][INFO][exchange-worker-#62%statement_grid%][time] Finished 
> exchange init [topVer=AffinityTopologyVersion [topVer=36, minorTopVer=0], 
> crd=false]
> [15:10:05,703][INFO][exchange-worker-#62%statement_grid%][GridCachePartitionExchangeManager]
>  Skipping rebalancing (nothing scheduled) [top=AffinityTopologyVersion 
> [topVer=36, minorTopVer=0], evt=NODE_JOINED, 
> node=979cf868-1c37-424a-9ad1-12db501f32ef]
> [15:10:08,706][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander]
>  Cancelled rebalancing from all nodes [topology=AffinityTopologyVersion 
> [topVer=35, minorTopVer=0]]
> [15:10:08,707][INFO][exchange-worker-#62%statement_grid%][GridCachePartitionExchangeManager]
>  Rebalancing scheduled [order=[statementp]]
> [15:10:08,707][INFO][exchange-worker-#62%statement_grid%][GridCachePartitionExchangeManager]
>  Rebalancing started [top=null, evt=NODE_JOINED, 
> node=a8be3c14-9add-48c3-b099-3fd304cfdbf4]
> [15:10:08,707][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander]
>  Starting rebalancing [mode=ASYNC, 
> fromNode=2f6bde48-ffb5-4815-bd32-df4e57dc13e0, partitionsCount=18, 
> topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], 
> updateSeq=-1754630006]
> [15:10:08,707][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander]
>  Starting rebalancing [mode=ASYNC, 
> fromNode=35d01141-4dce-47dd-adf6-a4f3b2bb9da9, partitionsCount=15, 
> topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], 
> updateSeq=-1754630006]
> [15:10:08,708][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander]
>  Starting rebalancing [mode=ASYNC, 
> fromNode=b3a8be53-e61f-4023-a906-a265923837ba, partitionsCount=15, 
> topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], 
> updateSeq=-1754630006]
> [15:10:08,708][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander]
>  Starting rebalancing [mode=ASYNC, 
> fromNode=f825cb4e-7dcc-405f-a40d-c1dc1a3ade5a, partitionsCount=12, 
> topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], 
> updateSeq=-1754630006]
> [15:10:08,708][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander]
>  Starting rebalancing [mode=ASYNC, 
> fromNode=4ae1db91-8b88-4180-a84b-127a303959e9, partitionsCount=11, 
> topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], 
> updateSeq=-1754630006]
> [15:10:08,708][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander]
>  Starting rebalancing [mode=ASYNC, 
> fromNode=7c286481-7638-49e4-8c68-fa6aa65d8b76, partitionsCount=18, 
> topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], 
> updateSeq=-1754630006]
> so in clusters with a big amount of data and the frequent client left/join 
> events this means that a new server will never receive its partitions.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-7113) "Key is missing from query" when creating table with key_type=java.lang.String

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-7113:
-

[~al.psc], IMO the problem is much wider - user may pass arbitrary class name 
and we cannot know whether this is a valid type for the given set of columns or 
not. For example, try passing {{java.lang.Number}} or {{java.util.ArrayList}}, 
etc. You will all sorts of weird errors. Moreover, the problem is not specific 
to {{CREATE TABLE}}, it could be reproduced using invalid {{QueryEntity}} and 
normal cache start.

IMO we should act differently here. First, we cannot check user-provided 
classes reliably as they may not exist on the client. But at the very least we 
can filter our abvios errors around JDK classes as follows:
1) Construct query entity as usual.
2) Add validation to {{QueryUtils#validateQueryEntity}}:
2.1) If key type is JDK type ({{IgniteUtils#isJdk}}), then check if it is SQL 
type and matches provided columns (i.e. repeat your current solution)
2.2) Do the same thing for value type

NB: It makes sense to overload {{IgniteUtils#isJdk}} accepting class name. This 
way you could avoid {{Class.forName}} call on arbitrary string which may lead 
to adverse effects.

> "Key is missing from query" when creating table with key_type=java.lang.String
> --
>
> Key: IGNITE-7113
> URL: https://issues.apache.org/jira/browse/IGNITE-7113
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.3
>Reporter: Ilya Kasnacheev
>Assignee: Alexander Paschenko
> Attachments: IgniteStringKeyTest.java
>
>
> When creating a table of
> {code}
> CREATE TABLE IF NOT EXISTS TableWithStringKey (
>   ID VARCHAR PRIMARY KEY,
>   DataNodeId VARCHAR
> ) WITH "backups=1, cache_name=TableWithStringKey, atomicity=transactional, 
> key_type=java.lang.String, value_type=TableWithStringKey"
> {code}
> and attempting an insert later
> {code}
> INSERT INTO TableWithStringKey (ID, DataNodeId) VALUES ('ref2', 'src2')
> {code}
> There's suddently an exception
> {code}
> javax.cache.CacheException: class 
> org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to 
> execute DML statement [stmt=INSERT INTO TableWithStringKey (ID, DataNodeId) 
> VALUES ('ref2', 'src2'), params=null]
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:597)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:560)
>   at 
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.query(GatewayProtectedCacheProxy.java:382)
>   at 
> com.gridgain.reproducer.IgniteStringKeyTest.insertTest(IgniteStringKeyTest.java:34)
>   ... 24 more
> Caused by: class 
> org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to 
> execute DML statement [stmt=INSERT INTO TableWithStringKey (ID, DataNodeId) 
> VALUES ('ref2', 'src2'), params=null]
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1459)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:1909)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:1907)
>   at 
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2445)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:1914)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:585)
>   ... 27 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Key is missing 
> from query
>   at 
> org.apache.ignite.internal.processors.query.h2.dml.UpdatePlanBuilder.createSupplier(UpdatePlanBuilder.java:369)
>   at 
> org.apache.ignite.internal.processors.query.h2.dml.UpdatePlanBuilder.planForInsert(UpdatePlanBuilder.java:211)
>   at 
> org.apache.ignite.internal.processors.query.h2.dml.UpdatePlanBuilder.planForStatement(UpdatePlanBuilder.java:98)
>   at 
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.getPlanForStatement(DmlStatementsProcessor.java:473)
>   at 
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFields(DmlStatementsProcessor.java:170)
>   at 
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFieldsDistributed(DmlStatementsProcessor.java:229)
>   at 
> 

[jira] [Created] (IGNITE-7165) Re-balancing is cancelled if client node joins

[Mikhail Cherkasov (JIRA)]

Mikhail Cherkasov created IGNITE-7165:
-

 Summary: Re-balancing is cancelled if client node joins
 Key: IGNITE-7165
 URL: https://issues.apache.org/jira/browse/IGNITE-7165
 Project: Ignite
  Issue Type: Bug
Reporter: Mikhail Cherkasov
Assignee: Anton Vinogradov
Priority: Critical


Re-balancing is canceled if client node joins. Re-balancing can take hours and 
each time when client node joins it starts again:

[15:10:05,700][INFO][disco-event-worker-#61%statement_grid%][GridDiscoveryManager]
 Added new node to topology: TcpDiscoveryNode 
[id=979cf868-1c37-424a-9ad1-12db501f32ef, addrs=[0:0:0:0:0:0:0:1, 127.0.0.1, 
172.31.16.213], sockAddrs=[/0:0:0:0:0:0:0:1:0, /127.0.0.1:0, /172.31.16.213:0], 
discPort=0, order=36, intOrder=24, lastExchangeTime=1512907805688, loc=false, 
ver=2.3.1#20171129-sha1:4b1ec0fe, isClient=true]
[15:10:05,701][INFO][disco-event-worker-#61%statement_grid%][GridDiscoveryManager]
 Topology snapshot [ver=36, servers=7, clients=5, CPUs=128, heap=160.0GB]
[15:10:05,702][INFO][exchange-worker-#62%statement_grid%][time] Started 
exchange init [topVer=AffinityTopologyVersion [topVer=36, minorTopVer=0], 
crd=false, evt=NODE_JOINED, evtNode=979cf868-1c37-424a-9ad1-12db501f32ef, 
customEvt=null, allowMerge=true]
[15:10:05,702][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionsExchangeFuture]
 Finish exchange future [startVer=AffinityTopologyVersion [topVer=36, 
minorTopVer=0], resVer=AffinityTopologyVersion [topVer=36, minorTopVer=0], 
err=null]
[15:10:05,702][INFO][exchange-worker-#62%statement_grid%][time] Finished 
exchange init [topVer=AffinityTopologyVersion [topVer=36, minorTopVer=0], 
crd=false]
[15:10:05,703][INFO][exchange-worker-#62%statement_grid%][GridCachePartitionExchangeManager]
 Skipping rebalancing (nothing scheduled) [top=AffinityTopologyVersion 
[topVer=36, minorTopVer=0], evt=NODE_JOINED, 
node=979cf868-1c37-424a-9ad1-12db501f32ef]
[15:10:08,706][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander]
 Cancelled rebalancing from all nodes [topology=AffinityTopologyVersion 
[topVer=35, minorTopVer=0]]
[15:10:08,707][INFO][exchange-worker-#62%statement_grid%][GridCachePartitionExchangeManager]
 Rebalancing scheduled [order=[statementp]]
[15:10:08,707][INFO][exchange-worker-#62%statement_grid%][GridCachePartitionExchangeManager]
 Rebalancing started [top=null, evt=NODE_JOINED, 
node=a8be3c14-9add-48c3-b099-3fd304cfdbf4]
[15:10:08,707][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander]
 Starting rebalancing [mode=ASYNC, 
fromNode=2f6bde48-ffb5-4815-bd32-df4e57dc13e0, partitionsCount=18, 
topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], 
updateSeq=-1754630006]
[15:10:08,707][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander]
 Starting rebalancing [mode=ASYNC, 
fromNode=35d01141-4dce-47dd-adf6-a4f3b2bb9da9, partitionsCount=15, 
topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], 
updateSeq=-1754630006]
[15:10:08,708][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander]
 Starting rebalancing [mode=ASYNC, 
fromNode=b3a8be53-e61f-4023-a906-a265923837ba, partitionsCount=15, 
topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], 
updateSeq=-1754630006]
[15:10:08,708][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander]
 Starting rebalancing [mode=ASYNC, 
fromNode=f825cb4e-7dcc-405f-a40d-c1dc1a3ade5a, partitionsCount=12, 
topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], 
updateSeq=-1754630006]
[15:10:08,708][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander]
 Starting rebalancing [mode=ASYNC, 
fromNode=4ae1db91-8b88-4180-a84b-127a303959e9, partitionsCount=11, 
topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], 
updateSeq=-1754630006]
[15:10:08,708][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander]
 Starting rebalancing [mode=ASYNC, 
fromNode=7c286481-7638-49e4-8c68-fa6aa65d8b76, partitionsCount=18, 
topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], 
updateSeq=-1754630006]

so in clusters with a big amount of data and the frequent client left/join 
events this means that a new server will never receive its partitions.




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-6995) Visor CMD: Actualize showed grid/cache configuration.

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov reassigned IGNITE-6995:


Assignee: Pavel Konstantinov  (was: Alexey Kuznetsov)

Please, test in branch

> Visor CMD: Actualize showed grid/cache configuration.
> -
>
> Key: IGNITE-6995
> URL: https://issues.apache.org/jira/browse/IGNITE-6995
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
> Fix For: 2.4
>
>
> Actualise in accordance to IGNITE-6649 changes.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6123) First performance measurement of implemented ml algorithms

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov commented on IGNITE-6123:
--

[~oignatenko]
Looks good to me.

[~chief]
Please perform final review and merge.

> First performance measurement of implemented ml algorithms
> --
>
> Key: IGNITE-6123
> URL: https://issues.apache.org/jira/browse/IGNITE-6123
> Project: Ignite
>  Issue Type: Improvement
>  Components: ml, yardstick
>Reporter: Yury Babak
>Assignee: Oleg Ignatenko
> Fix For: 2.4
>
>
> We want to start tracking our performance to avoid performance degradation. 
> Also we need some performance comparison with other ml libs.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-7164) SQL TX: Locking protocol for complex cases

[Igor Seliverstov (JIRA)]

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

Igor Seliverstov updated IGNITE-7164:
-
Fix Version/s: 2.5

> SQL TX: Locking protocol for complex cases
> --
>
> Key: IGNITE-7164
> URL: https://issues.apache.org/jira/browse/IGNITE-7164
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Igor Seliverstov
>  Labels: iep-3
> Fix For: 2.5
>
>
> Currently several features are still unimplemented:
> # Implicit transactions
> # Optimistic transactions
> # Transactional SQL updates during rebalancing
> # Updates on backup nodes/Replicated caches support
> # Near caches support
> # TX restore
> # Remap on topology changes



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-7164) SQL TX: Locking protocol for complex cases

[Igor Seliverstov (JIRA)]

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

Igor Seliverstov updated IGNITE-7164:
-
Labels: iep-3  (was: )

> SQL TX: Locking protocol for complex cases
> --
>
> Key: IGNITE-7164
> URL: https://issues.apache.org/jira/browse/IGNITE-7164
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Igor Seliverstov
>  Labels: iep-3
> Fix For: 2.5
>
>
> Currently several features are still unimplemented:
> # Implicit transactions
> # Optimistic transactions
> # Transactional SQL updates during rebalancing
> # Updates on backup nodes/Replicated caches support
> # Near caches support
> # TX restore
> # Remap on topology changes



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-7164) SQL TX: Locking protocol for complex cases

[Igor Seliverstov (JIRA)]

Igor Seliverstov created IGNITE-7164:


 Summary: SQL TX: Locking protocol for complex cases
 Key: IGNITE-7164
 URL: https://issues.apache.org/jira/browse/IGNITE-7164
 Project: Ignite
  Issue Type: Task
  Components: sql
Reporter: Igor Seliverstov


Currently several features are still unimplemented:
# Implicit transactions
# Optimistic transactions
# Transactional SQL updates during rebalancing
# Updates on backup nodes/Replicated caches support
# Near caches support
# TX restore
# Remap on topology changes



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5731) Wrong metrics calculation in ClusterMetricsSnapshot

[Andrey Gura (JIRA)]

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

Andrey Gura commented on IGNITE-5731:
-

Merged to master branch. Thanks for contribution!

> Wrong metrics calculation in ClusterMetricsSnapshot
> ---
>
> Key: IGNITE-5731
> URL: https://issues.apache.org/jira/browse/IGNITE-5731
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Evgenii Zhuravlev
>Assignee: Denis Loginov
>Priority: Minor
> Fix For: 2.4
>
>
>  Error in ClusterMetricsSnapshot constructor:
>  curWaitingJobs += m.getCurrentJobWaitTime();
>  avgWaitingJobs += m.getCurrentWaitingJobs();



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5731) Wrong metrics calculation in ClusterMetricsSnapshot

[Andrey Gura (JIRA)]

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

Andrey Gura updated IGNITE-5731:

Fix Version/s: 2.4

> Wrong metrics calculation in ClusterMetricsSnapshot
> ---
>
> Key: IGNITE-5731
> URL: https://issues.apache.org/jira/browse/IGNITE-5731
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Evgenii Zhuravlev
>Assignee: Denis Loginov
>Priority: Minor
> Fix For: 2.4
>
>
>  Error in ClusterMetricsSnapshot constructor:
>  curWaitingJobs += m.getCurrentJobWaitTime();
>  avgWaitingJobs += m.getCurrentWaitingJobs();



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (IGNITE-5731) Wrong metrics calculation in ClusterMetricsSnapshot

[Andrey Gura (JIRA)]

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

Andrey Gura resolved IGNITE-5731.
-
Resolution: Fixed

> Wrong metrics calculation in ClusterMetricsSnapshot
> ---
>
> Key: IGNITE-5731
> URL: https://issues.apache.org/jira/browse/IGNITE-5731
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Evgenii Zhuravlev
>Assignee: Denis Loginov
>Priority: Minor
> Fix For: 2.4
>
>
>  Error in ClusterMetricsSnapshot constructor:
>  curWaitingJobs += m.getCurrentJobWaitTime();
>  avgWaitingJobs += m.getCurrentWaitingJobs();



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-6740) Java 9: rework DirectBuffer.address() usages

[Andrey Kuznetsov (JIRA)]

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

Andrey Kuznetsov reassigned IGNITE-6740:


Assignee: Andrey Kuznetsov

> Java 9: rework DirectBuffer.address() usages
> 
>
> Key: IGNITE-6740
> URL: https://issues.apache.org/jira/browse/IGNITE-6740
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Reporter: Vladimir Ozerov
>Assignee: Andrey Kuznetsov
> Fix For: 2.4
>
>
> We have two usages of {{DirectBuffer.address()}} method which is no longer 
> accessible in Java 9: 
> 1) {{DirectByteBufferStreamImplV1}}
> 2) {{DirectByteBufferStreamImplV2}}
> Need to rework this code using reflection and/or {{Unsafe}}, so that it 
> compiles and work on all Java versions.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (IGNITE-5755) Wrong msg: calculation of memory policy size

[Andrey Gura (JIRA)]

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

Andrey Gura resolved IGNITE-5755.
-
Resolution: Fixed

> Wrong msg: calculation of memory policy size
> 
>
> Key: IGNITE-5755
> URL: https://issues.apache.org/jira/browse/IGNITE-5755
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 2.1
>Reporter: Alexander Belyak
>Assignee: Sergey Volkov
>Priority: Trivial
> Fix For: 2.4
>
>
> In PageMemoryNoStoreImpl:
> {noformat}
> throw new IgniteOutOfMemoryException("Not enough memory allocated 
> " +
> "(consider increasing memory policy size or enabling 
> evictions) " +
> "[policyName=" + memoryPolicyCfg.getName() +
> ", size=" + U.readableSize(memoryPolicyCfg.getMaxSize(), 
> true) + "]"
> {noformat}
> wrong usage of U.readableSize - we should use non "Si" (1024 instead of 1000) 
> multiplier. Right code is:
> {noformat}
> throw new IgniteOutOfMemoryException("Not enough memory allocated 
> " +
> "(consider increasing memory policy size or enabling 
> evictions) " +
> "[policyName=" + memoryPolicyCfg.getName() +
> ", size=" + U.readableSize(memoryPolicyCfg.getMaxSize(), 
> false) + "]"
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5755) Wrong msg: calculation of memory policy size

[Andrey Gura (JIRA)]

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

Andrey Gura commented on IGNITE-5755:
-

Merged to master branch. Thanks for contribution!

> Wrong msg: calculation of memory policy size
> 
>
> Key: IGNITE-5755
> URL: https://issues.apache.org/jira/browse/IGNITE-5755
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 2.1
>Reporter: Alexander Belyak
>Assignee: Sergey Volkov
>Priority: Trivial
> Fix For: 2.4
>
>
> In PageMemoryNoStoreImpl:
> {noformat}
> throw new IgniteOutOfMemoryException("Not enough memory allocated 
> " +
> "(consider increasing memory policy size or enabling 
> evictions) " +
> "[policyName=" + memoryPolicyCfg.getName() +
> ", size=" + U.readableSize(memoryPolicyCfg.getMaxSize(), 
> true) + "]"
> {noformat}
> wrong usage of U.readableSize - we should use non "Si" (1024 instead of 1000) 
> multiplier. Right code is:
> {noformat}
> throw new IgniteOutOfMemoryException("Not enough memory allocated 
> " +
> "(consider increasing memory policy size or enabling 
> evictions) " +
> "[policyName=" + memoryPolicyCfg.getName() +
> ", size=" + U.readableSize(memoryPolicyCfg.getMaxSize(), 
> false) + "]"
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5755) Wrong msg: calculation of memory policy size

[Andrey Gura (JIRA)]

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

Andrey Gura updated IGNITE-5755:

Fix Version/s: 2.4

> Wrong msg: calculation of memory policy size
> 
>
> Key: IGNITE-5755
> URL: https://issues.apache.org/jira/browse/IGNITE-5755
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 2.1
>Reporter: Alexander Belyak
>Assignee: Sergey Volkov
>Priority: Trivial
> Fix For: 2.4
>
>
> In PageMemoryNoStoreImpl:
> {noformat}
> throw new IgniteOutOfMemoryException("Not enough memory allocated 
> " +
> "(consider increasing memory policy size or enabling 
> evictions) " +
> "[policyName=" + memoryPolicyCfg.getName() +
> ", size=" + U.readableSize(memoryPolicyCfg.getMaxSize(), 
> true) + "]"
> {noformat}
> wrong usage of U.readableSize - we should use non "Si" (1024 instead of 1000) 
> multiplier. Right code is:
> {noformat}
> throw new IgniteOutOfMemoryException("Not enough memory allocated 
> " +
> "(consider increasing memory policy size or enabling 
> evictions) " +
> "[policyName=" + memoryPolicyCfg.getName() +
> ", size=" + U.readableSize(memoryPolicyCfg.getMaxSize(), 
> false) + "]"
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (IGNITE-6663) SQL: optimize primary key equality lookup

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov edited comment on IGNITE-6663 at 12/11/17 12:56 PM:


[~kirill.shirokov], in general fix is correct, but there are several minor 
issues to address:
1) Please avoid long variable and method names. They should be as compact as 
possible. Also abbreviations are not allowed in methods.
{{partitionRowFilterClo()}} -> {{filter()}}
{{gridCursor}} -> {{cursor}}
{{partitionFilter}} -> {{"p"}} or {{"filter"}}
2) {{SingletonCursor}} - looks like we could reuse 
{{org.h2.index.SingleRowCursor}} instead of creating our own implementation.
3) {{H2DynamicIndexAbstractSelfTest}} hosts tests for dynamic index create/drop 
routines only. So it is not appropriate place for new tests for this feature. 
IMO {{IgniteCacheAbstractFieldsQuerySelfTest}} should be enough.


was (Author: vozerov):
[~kirill.shirokov], in general fix is correct, but there are several minor 
issues to address:
1) Please avoid long variable and method names. They should be as compact as 
possible. Also abbreviations are not allowed in methods.
{{partitionRowFilterClo()}} -> {{filter()}}
{{gridCursor}} -> cursor}}
{{partitionFilter}} -> {{"p"}} or {{"filter"}}
2) {{SingletonCursor}} - looks like we could reuse 
{{org.h2.index.SingleRowCursor}} instead of creating our own implementation.
3) {{H2DynamicIndexAbstractSelfTest}} hosts tests for dynamic index create/drop 
routines only. So it is not appropriate place for new tests for this feature. 
IMO {{IgniteCacheAbstractFieldsQuerySelfTest}} should be enough.

> SQL: optimize primary key equality lookup
> -
>
> Key: IGNITE-6663
> URL: https://issues.apache.org/jira/browse/IGNITE-6663
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Kirill Shirokov
>  Labels: performance
> Fix For: 2.4
>
>
> H2 perform every index search through {{BaseIndex.find}} method. It contains 
> both {{first}} and {{last}} rows. If condition looks like {{attr = ?}}, then 
> both bounds are the same. When this call is propagated to our {{BPlusTree}}, 
> then two index lookups occur:
> - Lower bound: {{BPlusTree#findInsertionPoint}}
> - Upper bound: {{BPlusTree.ForwardCursor#findUpperBound}}
> This is done for a reason because we do not know in advance how many elements 
> are in between the bounds, so one lookup + scan is not an option in general 
> case. But in case of PK lookup with equality condition, when we know in 
> advance that only one row will be returned, this leads to additional 
> unnecessary comparisons. 
> Suggested fix:
> 1) Make sure that all rows in {{GridH2PlainRowFactory}} has correct 
> {{equals}} implementation.
> 2) Inside {{H2TreeIndex#find}}: if this is PK index (see constructor args) 
> and {{lower.equals(upper)}}, then use {{BPlusTree.findOne}} instead of 
> {{BPlusTree.find}}.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-7163) Validate connection from a pre-previous node

[Alexandr Kuramshin (JIRA)]

Alexandr Kuramshin created IGNITE-7163:
--

 Summary: Validate connection from a pre-previous node
 Key: IGNITE-7163
 URL: https://issues.apache.org/jira/browse/IGNITE-7163
 Project: Ignite
  Issue Type: Sub-task
Affects Versions: 2.3
Reporter: Alexandr Kuramshin
Assignee: Alexandr Kuramshin


If some pre-previous node connects to the local node with the previous node in 
the message's failed nodes collection additional steps should be done:

# Connection with the previous node should be validated.
# If a message from the previous node was not received a long time ago, the 
previous node should be considered as failed and the pre-previous node 
connection accepted.
# If the previous node connection is alive then different scenarios possible
## Answer with a new result code causing the pre-previous node to try to 
reconnect to the previous node
## Break connection with the pre-previous node causing to continue the possible 
cluster split.
## Check connections with nodes after pre-previous node and delay decision by 
answering RES_WAIT to get more predictable split and stable topology.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (IGNITE-6590) TCP port in bin/control.sh differs from default

[Andrey Gura (JIRA)]

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

Andrey Gura resolved IGNITE-6590.
-
Resolution: Fixed

> TCP port in bin/control.sh differs from default
> ---
>
> Key: IGNITE-6590
> URL: https://issues.apache.org/jira/browse/IGNITE-6590
> Project: Ignite
>  Issue Type: Bug
>  Components: clients
>Affects Versions: 2.2
>Reporter: Ilya Kasnacheev
>Assignee: Mike Zhuravlev
> Fix For: 2.4
>
>
> {code}
> % bin/ignite.sh -v
> >>> Local ports: TCP:8081 TCP:10800 TCP:11211 TCP:47100 TCP:47500 
> % bin/control.sh --host 127.0.0.1
> окт 10, 2017 3:01:26 PM org.apache.ignite.internal.client.impl.GridClientImpl 
> 
> WARNING: Failed to initialize topology on client start. Will retry in 
> background.
> Caused by: class 
> org.apache.ignite.internal.client.GridServerUnreachableException: Failed to 
> connect to any of the servers in list: [/127.0.0.1:11212]
> {code}
> 11212 != 11211. But it's very hard to spot visually. Please fix control.sh to 
> use correct port by default.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6590) TCP port in bin/control.sh differs from default

[Andrey Gura (JIRA)]

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

Andrey Gura commented on IGNITE-6590:
-

LGTM. Merged to master branch. 
Thanks for contribution!

> TCP port in bin/control.sh differs from default
> ---
>
> Key: IGNITE-6590
> URL: https://issues.apache.org/jira/browse/IGNITE-6590
> Project: Ignite
>  Issue Type: Bug
>  Components: clients
>Affects Versions: 2.2
>Reporter: Ilya Kasnacheev
>Assignee: Mike Zhuravlev
> Fix For: 2.4
>
>
> {code}
> % bin/ignite.sh -v
> >>> Local ports: TCP:8081 TCP:10800 TCP:11211 TCP:47100 TCP:47500 
> % bin/control.sh --host 127.0.0.1
> окт 10, 2017 3:01:26 PM org.apache.ignite.internal.client.impl.GridClientImpl 
> 
> WARNING: Failed to initialize topology on client start. Will retry in 
> background.
> Caused by: class 
> org.apache.ignite.internal.client.GridServerUnreachableException: Failed to 
> connect to any of the servers in list: [/127.0.0.1:11212]
> {code}
> 11212 != 11211. But it's very hard to spot visually. Please fix control.sh to 
> use correct port by default.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-6590) TCP port in bin/control.sh differs from default

[Andrey Gura (JIRA)]

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

Andrey Gura updated IGNITE-6590:

Fix Version/s: 2.4

> TCP port in bin/control.sh differs from default
> ---
>
> Key: IGNITE-6590
> URL: https://issues.apache.org/jira/browse/IGNITE-6590
> Project: Ignite
>  Issue Type: Bug
>  Components: clients
>Affects Versions: 2.2
>Reporter: Ilya Kasnacheev
>Assignee: Mike Zhuravlev
> Fix For: 2.4
>
>
> {code}
> % bin/ignite.sh -v
> >>> Local ports: TCP:8081 TCP:10800 TCP:11211 TCP:47100 TCP:47500 
> % bin/control.sh --host 127.0.0.1
> окт 10, 2017 3:01:26 PM org.apache.ignite.internal.client.impl.GridClientImpl 
> 
> WARNING: Failed to initialize topology on client start. Will retry in 
> background.
> Caused by: class 
> org.apache.ignite.internal.client.GridServerUnreachableException: Failed to 
> connect to any of the servers in list: [/127.0.0.1:11212]
> {code}
> 11212 != 11211. But it's very hard to spot visually. Please fix control.sh to 
> use correct port by default.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-7162) Control discovery messages processing time

[Alexandr Kuramshin (JIRA)]

Alexandr Kuramshin created IGNITE-7162:
--

 Summary: Control discovery messages processing time
 Key: IGNITE-7162
 URL: https://issues.apache.org/jira/browse/IGNITE-7162
 Project: Ignite
  Issue Type: Sub-task
  Components: general
Affects Versions: 2.3
Reporter: Alexandr Kuramshin
Assignee: Alexandr Kuramshin


The majority of discovery message processing occurs in a single thread.

If some message processing takes significant time it causes delaying of 
processing other messages and further undesirable effects on another protocols.

Proposed to control processing time on the every node and total processing time 
of any given message. If processing takes significant time - log the warning.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-3495) CacheMetrics.getAverage###Time is not calculated properly

[Vyacheslav Koptilin (JIRA)]

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

Vyacheslav Koptilin reassigned IGNITE-3495:
---

Assignee: (was: Vyacheslav Koptilin)

> CacheMetrics.getAverage###Time is not calculated properly
> -
>
> Key: IGNITE-3495
> URL: https://issues.apache.org/jira/browse/IGNITE-3495
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Denis Magda
>  Labels: iep-6
> Attachments: ExampleNodeStartupClient.java, IGNITE_3495.patch, 
> example-default.xml
>
>
> {{CacheMetrics.getAverageGetTime}}, {{CacheMetrics.getAveragePutTime}} and 
> {{CacheMetrics.getAverageRemoveTime}} are not calculated properly in the 
> following scenario:
> - start a server node;
> - start a client node that will perform gets and puts;
> - {{CacheMetrics.getAverage###Time}} will always be 0 for the server node's 
> cluster group.
> The issue happens because {{CacheMetricsImpl.add###TimeNanos}} method is not 
> called on the server side when a metric related event happens.
> In the attache you can find source that showcases the bug.
> - start basic {{ExampleNodeStartup}} using attached configuration 
> {{example-default.xml}} conjuration;
> - start {{ExampleNodeStartupClient}}. You will see that average metrics are 
> not incremented.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-7147) Implemente connected clusters component

[Dmitriy Shabalin (JIRA)]

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

Dmitriy Shabalin reassigned IGNITE-7147:


Assignee: Alexey Kuznetsov  (was: Dmitriy Shabalin)

> Implemente connected clusters component
> ---
>
> Key: IGNITE-7147
> URL: https://issues.apache.org/jira/browse/IGNITE-7147
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Dmitriy Shabalin
>Assignee: Alexey Kuznetsov
> Fix For: 2.4
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-7147) Implemente connected clusters component

[Dmitriy Shabalin (JIRA)]

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

Dmitriy Shabalin commented on IGNITE-7147:
--

[~kuaw26] fixed issues, pls review it

> Implemente connected clusters component
> ---
>
> Key: IGNITE-7147
> URL: https://issues.apache.org/jira/browse/IGNITE-7147
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Dmitriy Shabalin
>Assignee: Alexey Kuznetsov
> Fix For: 2.4
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-7039) SQL: local query should pin affected partitions

[Roman Kondakov (JIRA)]

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

Roman Kondakov commented on IGNITE-7039:


[~vozerov], please review, tests are ok.

> SQL: local query should pin affected partitions
> ---
>
> Key: IGNITE-7039
> URL: https://issues.apache.org/jira/browse/IGNITE-7039
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Roman Kondakov
>
> When distributed query is executed, we pin cache partitions for particular 
> topology version on map nodes [1]. However, it seems that we do no do that 
> for local queries. This is a bug because partition with required data could 
> be evicted from local node at any time, leading to incorrect results.
> [1] 
> https://github.com/apache/ignite/blob/ignite-2.3/modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/twostep/GridMapQueryExecutor.java#L288



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-7161) Detect self-freeze on remote node related operations with timeout

[Alexandr Kuramshin (JIRA)]

Alexandr Kuramshin created IGNITE-7161:
--

 Summary: Detect self-freeze on remote node related operations with 
timeout
 Key: IGNITE-7161
 URL: https://issues.apache.org/jira/browse/IGNITE-7161
 Project: Ignite
  Issue Type: Sub-task
Affects Versions: 2.3
Reporter: Alexandr Kuramshin
Assignee: Alexandr Kuramshin


After getting next timeout from 
{{IgniteSpiOperationTimeoutHelper.nextTimeoutChunk()}} we starting a network 
operation and expecting to end it at the specific timestamp (or near about).

We should take into account that some local thread freeze may be occurred. In 
such situation a remote node should not be considered as failed and the local 
network operation has to be retried.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (IGNITE-7134) Never-ending timeout in IgniteSpiOperationTimeoutHelper.nextTimeoutChunk()

[Alexandr Kuramshin (JIRA)]

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

Alexandr Kuramshin resolved IGNITE-7134.

   Resolution: Won't Fix
Fix Version/s: (was: 2.4)
   None

Actual problem described in the linked issue.

> Never-ending timeout in IgniteSpiOperationTimeoutHelper.nextTimeoutChunk()
> --
>
> Key: IGNITE-7134
> URL: https://issues.apache.org/jira/browse/IGNITE-7134
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 2.3
>Reporter: Alexandr Kuramshin
>Assignee: Alexandr Kuramshin
>Priority: Critical
> Fix For: None
>
>
> {noformat}
> org.apache.ignite.spi.IgniteSpiOperationTimeoutHelper#nextTimeoutChunk
> long curTs = U.currentTimeMillis();
> timeout = timeout - (curTs - lastOperStartTs);
> {noformat}
> Timeout will not be decreased at all if delay between successive calls to 
> nextTimeoutChunk() is smaller than U.currentTimeMillis() discretization. Such 
> behaviour could be easily achieved when getting an error right after the 
> nextTimeoutChunk() invocation and do the retry.
> Only rare calls (the first right before U.currentTimeMillis() and the second 
> right after that) may decrease timeout, so actual 
> IgniteSpiOperationTimeoutHelper timeout could be much bigger than the 
> failureDetectionTimeout.
> My opinion to not split failureDetectionTimeout between network operations, 
> but initialize first operation timestamp at first call to nextTimeoutChunk(), 
> and then calculate the timeout as a difference between the current timestamp 
> and the first operation timestamp.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-7160) Ignore messages from not alive and failed nodes

[Alexandr Kuramshin (JIRA)]

Alexandr Kuramshin created IGNITE-7160:
--

 Summary: Ignore messages from not alive and failed nodes
 Key: IGNITE-7160
 URL: https://issues.apache.org/jira/browse/IGNITE-7160
 Project: Ignite
  Issue Type: Sub-task
  Components: general
Affects Versions: 2.3
Reporter: Alexandr Kuramshin
Assignee: Alexandr Kuramshin


Current implementation of {{ServerImpl}} accepts and processes messages from 
any other remote node even it was failed or removed from the ring.

Proposed to process only specific messages (which have to be processed in the 
current node state). Some messages could be silently ignored, receiving other 
undesirable messages causes the remote socket disconnect.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-7159) Fix IGNITE-7086 fails IgniteCacheAtomicExpiryPolicyWithStoreTest.testGetReadThrough

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7159:


GitHub user dkarachentsev opened a pull request:

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

IGNITE-7159 - Fix IgniteCacheAtomicExpiryPolicyWithStoreTest.testGetR…

…eadThrough

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

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

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

https://github.com/apache/ignite/pull/3196.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3196


commit c190864356f56d7f0c73d405ba630bbdd5d88a26
Author: xmitya 
Date:   2017-12-11T11:11:40Z

IGNITE-7159 - Fix 
IgniteCacheAtomicExpiryPolicyWithStoreTest.testGetReadThrough




> Fix IGNITE-7086 fails 
> IgniteCacheAtomicExpiryPolicyWithStoreTest.testGetReadThrough
> ---
>
> Key: IGNITE-7159
> URL: https://issues.apache.org/jira/browse/IGNITE-7159
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitry Karachentsev
>Assignee: Dmitry Karachentsev
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-7159) Fix IGNITE-7086 fails IgniteCacheAtomicExpiryPolicyWithStoreTest.testGetReadThrough

[Dmitry Karachentsev (JIRA)]

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

Dmitry Karachentsev reassigned IGNITE-7159:
---

Assignee: Dmitry Karachentsev

> Fix IGNITE-7086 fails 
> IgniteCacheAtomicExpiryPolicyWithStoreTest.testGetReadThrough
> ---
>
> Key: IGNITE-7159
> URL: https://issues.apache.org/jira/browse/IGNITE-7159
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitry Karachentsev
>Assignee: Dmitry Karachentsev
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-7159) Fix IGNITE-7086 fails IgniteCacheAtomicExpiryPolicyWithStoreTest.testGetReadThrough

[Dmitry Karachentsev (JIRA)]

Dmitry Karachentsev created IGNITE-7159:
---

 Summary: Fix IGNITE-7086 fails 
IgniteCacheAtomicExpiryPolicyWithStoreTest.testGetReadThrough
 Key: IGNITE-7159
 URL: https://issues.apache.org/jira/browse/IGNITE-7159
 Project: Ignite
  Issue Type: Bug
Reporter: Dmitry Karachentsev






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-7158) TCP discovery improvement

[Alexandr Kuramshin (JIRA)]

Alexandr Kuramshin created IGNITE-7158:
--

 Summary: TCP discovery improvement
 Key: IGNITE-7158
 URL: https://issues.apache.org/jira/browse/IGNITE-7158
 Project: Ignite
  Issue Type: Improvement
  Components: general
Affects Versions: 2.3
Reporter: Alexandr Kuramshin
Assignee: Alexandr Kuramshin


Current TCP discovery implementation has different drawbacks which should be 
fixed.

See sub-tasks for details.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-7040) Web console: Invalid user table height

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-7040:
-
Fix Version/s: 2.4

> Web console: Invalid user table height
> --
>
> Key: IGNITE-7040
> URL: https://issues.apache.org/jira/browse/IGNITE-7040
> Project: Ignite
>  Issue Type: Bug
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
> Fix For: 2.4
>
>
> # Filter user list (f.e. to 2 rows)
> # Change period of showed activity metrics.
> Height of table changed to maximum available but show only filtered rows.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (IGNITE-6976) Visor CMD: Add ability to put/get/remove data to caches via command line Visor.

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko edited comment on IGNITE-6976 at 12/11/17 10:51 AM:
--

Fixed catching of exceptions on cache modify operation.


was (Author: vsisko):
Fixed catching of cache modify exception.

> Visor CMD: Add ability to put/get/remove data to caches via command line 
> Visor.
> ---
>
> Key: IGNITE-6976
> URL: https://issues.apache.org/jira/browse/IGNITE-6976
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Konstantinov
> Fix For: 2.4
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-6976) Visor CMD: Add ability to put/get/remove data to caches via command line Visor.

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko reassigned IGNITE-6976:
-

Assignee: Pavel Konstantinov  (was: Vasiliy Sisko)

> Visor CMD: Add ability to put/get/remove data to caches via command line 
> Visor.
> ---
>
> Key: IGNITE-6976
> URL: https://issues.apache.org/jira/browse/IGNITE-6976
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Konstantinov
> Fix For: 2.4
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6976) Visor CMD: Add ability to put/get/remove data to caches via command line Visor.

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko commented on IGNITE-6976:
---

Fixed catching of cache modify exception.

> Visor CMD: Add ability to put/get/remove data to caches via command line 
> Visor.
> ---
>
> Key: IGNITE-6976
> URL: https://issues.apache.org/jira/browse/IGNITE-6976
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Vasiliy Sisko
> Fix For: 2.4
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-7040) Web console: Invalid user table height

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov reassigned IGNITE-7040:


Assignee: Pavel Konstantinov  (was: Dmitriy Shabalin)

Please test in branch.

> Web console: Invalid user table height
> --
>
> Key: IGNITE-7040
> URL: https://issues.apache.org/jira/browse/IGNITE-7040
> Project: Ignite
>  Issue Type: Bug
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
>
> # Filter user list (f.e. to 2 rows)
> # Change period of showed activity metrics.
> Height of table changed to maximum available but show only filtered rows.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-7122) Page lock status is not checked in BPlusTree.treePrinter methods

[Kirill Shirokov (JIRA)]

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

Kirill Shirokov commented on IGNITE-7122:
-

[~gvvinblade], fixed.

> Page lock status is not checked in BPlusTree.treePrinter methods
> 
>
> Key: IGNITE-7122
> URL: https://issues.apache.org/jira/browse/IGNITE-7122
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.4
>Reporter: Kirill Shirokov
>Assignee: Kirill Shirokov
>
> The result of readLock(), which can be 0 is not checked in 
> BPlusTree.treePrinter getChildren() and formatTreeNode() calls:
> {noformat}
> java.lang.AssertionError: 0
> at 
> org.apache.ignite.internal.pagemem.PageUtils.getLong(PageUtils.java:117)
> at 
> org.apache.ignite.internal.processors.cache.persistence.tree.io.PageIO.getPageId(PageIO.java:279)
> at 
> org.apache.ignite.internal.processors.database.BPlusTreeSelfTest.checkPageId(BPlusTreeSelfTest.java:2307)
> at 
> org.apache.ignite.internal.processors.database.BPlusTreeSelfTest$TestTree.onReadUnlock(BPlusTreeSelfTest.java:2445)
> at 
> org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.readUnlock(PageHandler.java:203)
> at 
> org.apache.ignite.internal.processors.cache.persistence.DataStructure.readUnlock(DataStructure.java:186)
> at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.access$400(BPlusTree.java:82)
> at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$1.getChildren(BPlusTree.java:163)
> at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$1.getChildren(BPlusTree.java:120)
> at 
> org.apache.ignite.internal.util.lang.GridTreePrinter.printTree(GridTreePrinter.java:60)
> at 
> org.apache.ignite.internal.util.lang.GridTreePrinter.printTree(GridTreePrinter.java:67)
> at 
> org.apache.ignite.internal.util.lang.GridTreePrinter.print(GridTreePrinter.java:32)
> at 
> org.apache.ignite.internal.util.lang.GridTreePrinter.print(GridTreePrinter.java:43)
> at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.printTree(BPlusTree.java:1188)
> at 
> org.apache.ignite.internal.processors.database.BPlusTreeSelfTest$19.call(BPlusTreeSelfTest.java:1777)
> at 
> org.apache.ignite.internal.processors.database.BPlusTreeSelfTest$19.call(BPlusTreeSelfTest.java:1771)
> at 
> org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
> {noformat}
> ...which causes intermittent failures in the BPlusTree unit tests:
> BPlusTreePageMemoryImplTest.testPutRmvSizeSinglePageContention
> BPlusTreeReuseListPageMemoryImplTest.testPutRmvSizeSinglePageContention 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-7144) Java 9: fix build issue with tools.jar not found

[Peter Ivanov (JIRA)]

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

Peter Ivanov commented on IGNITE-7144:
--

[~avinogradov], please review.

> Java 9: fix build issue with tools.jar not found
> 
>
> Key: IGNITE-7144
> URL: https://issues.apache.org/jira/browse/IGNITE-7144
> Project: Ignite
>  Issue Type: Bug
>Reporter: Peter Ivanov
>Assignee: Peter Ivanov
>
> {code}
> [ERROR] Failed to execute goal on project ignite-tools: Could not resolve 
> dependencies for project org.apache.ignite:ignite-tools:jar:2.4.0-SNAPSHOT: 
> Could not find artifact com.sun:tools:jar:9.0.1 at specified path 
> /Library/Java/JavaVirtualMachines/jdk-9.0.1.jdk/Contents/Home/../lib/tools.jar
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (IGNITE-602) [Test] GridToStringBuilder is vulnerable for StackOverflowError caused by infinite recursion

[Ryabov Dmitrii (JIRA)]

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

Ryabov Dmitrii edited comment on IGNITE-602 at 12/11/17 10:07 AM:
--

[~agura], fixed. This test failed because of missing annotation 
{{@GridToStringExcelude}}. Now I write {{ByteBuffer}} s by their {{toString()}} 
as it's implementation returns only useful things (position, limit and 
capacity) without unnecessary phantom references like {{Cleaner}}.

[Now|https://ci.ignite.apache.org/viewLog.html?buildId=988843=buildResultsDiv=Ignite20Tests_RunAll]
 tests don't fail with StackOverflowError.


was (Author: somefire):
[~agura], fixed. This test failed because of missing annotation 
{{@GridToStringExcelude}}. Now I write {{ByteBuffer}} s by their {{toString()}} 
as it's implementation returns only useful things (position, limit and 
capacity) without unnecessary phantom references like {{Cleaner}}.

> [Test] GridToStringBuilder is vulnerable for StackOverflowError caused by 
> infinite recursion
> 
>
> Key: IGNITE-602
> URL: https://issues.apache.org/jira/browse/IGNITE-602
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Artem Shutak
>Assignee: Ryabov Dmitrii
>  Labels: MakeTeamcityGreenAgain, Muted_test
> Fix For: 2.4
>
>
> See test 
> org.gridgain.grid.util.tostring.GridToStringBuilderSelfTest#_testToStringCheckAdvancedRecursionPrevention
>  and related TODO in same source file.
> Also take a look at 
> http://stackoverflow.com/questions/11300203/most-efficient-way-to-prevent-an-infinite-recursion-in-tostring
> Test should be unmuted on TC after fix.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-6734) Java 9: do not use sun.misc.BASE64Encoder

[Andrey Kuznetsov (JIRA)]

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

Andrey Kuznetsov reassigned IGNITE-6734:


Assignee: Andrey Kuznetsov

> Java 9: do not use sun.misc.BASE64Encoder
> -
>
> Key: IGNITE-6734
> URL: https://issues.apache.org/jira/browse/IGNITE-6734
> Project: Ignite
>  Issue Type: Task
>  Components: general, rest
>Reporter: Vladimir Ozerov
>Assignee: Andrey Kuznetsov
> Fix For: 2.4
>
>
> For some reason we use {{sun.misc.BASE64Encoder}} in several places:
> 1) {{jiraslurp.groovy}}
> 2) Several REST-related classes in {{ignite-clients}} module.
> Need to remove this usages and use {{Base64}}. Note that this class is 
> available since Java 8. Hopefully we will move to Java 8 in the same release. 
> Otherwise we will have to apply some reflection-based hacks, I think.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-6925) Simplify cache metrics activation

[Aleksey Plekhanov (JIRA)]

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

Aleksey Plekhanov reassigned IGNITE-6925:
-

Assignee: Aleksey Plekhanov

> Simplify cache metrics activation
> -
>
> Key: IGNITE-6925
> URL: https://issues.apache.org/jira/browse/IGNITE-6925
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Denis Magda
>Assignee: Aleksey Plekhanov
>  Labels: iep-6, important
> Fix For: 2.4
>
>
> The user needs to do 3 things to enabled cache metrics:
> - set {{statisticsEnabled}} to {{true}}.
> - set not a dummy {{EventsStorageSpi}}
> - list metrics of the interest.
> This process has to be reduced to 2 steps or, preferably, to 1.
> More details are here: 
> http://apache-ignite-developers.2346864.n4.nabble.com/Annoying-extra-steps-for-enabling-metrics-td21865.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-7039) SQL: local query should pin affected partitions

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7039:


GitHub user dolphin1414 opened a pull request:

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

IGNITE-7039: SQL: local query now pin affected partitions.

Implemented partitions reservation for the local queries. Added a test.

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

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

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

https://github.com/apache/ignite/pull/3194.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3194


commit 9a851a58ad5eb43f5b868d4a72013ce4a9beb395
Author: rkondakov 
Date:   2017-12-09T17:39:26Z

IGNITE-7039: Partitions reservation for the local queries is implemented.

commit dac1fc52cef92eae848966e85218da79092a48fa
Author: rkondakov 
Date:   2017-12-11T09:52:04Z

IGNITE-7039: Tests implemented.

commit 769ac1a7f2d66677127cdbc1ea367ee873132220
Author: rkondakov 
Date:   2017-12-11T09:52:50Z

Merge branch 'master' of https://git-wip-us.apache.org/repos/asf/ignite 
into ignite-7039




> SQL: local query should pin affected partitions
> ---
>
> Key: IGNITE-7039
> URL: https://issues.apache.org/jira/browse/IGNITE-7039
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Roman Kondakov
>
> When distributed query is executed, we pin cache partitions for particular 
> topology version on map nodes [1]. However, it seems that we do no do that 
> for local queries. This is a bug because partition with required data could 
> be evicted from local node at any time, leading to incorrect results.
> [1] 
> https://github.com/apache/ignite/blob/ignite-2.3/modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/twostep/GridMapQueryExecutor.java#L288



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (IGNITE-7147) Implemente connected clusters component

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov edited comment on IGNITE-7147 at 12/11/17 9:48 AM:
--

Please do not show component :
- on home\sign in pages
- in demo mode
- 403\404 page

Other sides are correct. Verified under all supported browsers.


was (Author: pkonstantinov):
Please do not show component :
- on home\sign in pages
- in demo mode
- 403\404 page
Other sides are correct. Verified under all supported browsers.

> Implemente connected clusters component
> ---
>
> Key: IGNITE-7147
> URL: https://issues.apache.org/jira/browse/IGNITE-7147
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Dmitriy Shabalin
>Assignee: Dmitriy Shabalin
> Fix For: 2.4
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-6976) Visor CMD: Add ability to put/get/remove data to caches via command line Visor.

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov reassigned IGNITE-6976:
--

Assignee: Vasiliy Sisko  (was: Pavel Konstantinov)

> Visor CMD: Add ability to put/get/remove data to caches via command line 
> Visor.
> ---
>
> Key: IGNITE-6976
> URL: https://issues.apache.org/jira/browse/IGNITE-6976
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Vasiliy Sisko
> Fix For: 2.4
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (IGNITE-7147) Implemente connected clusters component

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov edited comment on IGNITE-7147 at 12/11/17 9:47 AM:
--

Please do not show component :
- on home\sign in pages
- in demo mode
- 403\404 page
Other sides are correct. Verified under all supported browsers.


was (Author: pkonstantinov):
Please do not show component :
- on home\sign in pages
- in demo mode
- 404 page
Other sides are correct. Verified under all supported browsers.

> Implemente connected clusters component
> ---
>
> Key: IGNITE-7147
> URL: https://issues.apache.org/jira/browse/IGNITE-7147
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Dmitriy Shabalin
>Assignee: Dmitriy Shabalin
> Fix For: 2.4
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (IGNITE-7147) Implemente connected clusters component

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov edited comment on IGNITE-7147 at 12/11/17 9:46 AM:
--

Please do not show component :
- on home\sign in pages
- in demo mode
- 404 page
Other sides are correct. Verified under all supported browsers.


was (Author: pkonstantinov):
Please do not show component :
- on home\sign in pages
- in demo mode
- 404 page

> Implemente connected clusters component
> ---
>
> Key: IGNITE-7147
> URL: https://issues.apache.org/jira/browse/IGNITE-7147
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Dmitriy Shabalin
>Assignee: Dmitriy Shabalin
> Fix For: 2.4
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (IGNITE-7147) Implemente connected clusters component

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov edited comment on IGNITE-7147 at 12/11/17 9:41 AM:
--

Please do not show component :
- on home\sign in pages
- in demo mode
- 404 page


was (Author: pkonstantinov):
Please do not show component :
- on home\sign in pages
- in demo mode

> Implemente connected clusters component
> ---
>
> Key: IGNITE-7147
> URL: https://issues.apache.org/jira/browse/IGNITE-7147
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Dmitriy Shabalin
>Assignee: Dmitriy Shabalin
> Fix For: 2.4
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6009) CacheExamplesSelfTest.testCacheSemaphoreExample fails sometimes due to timeout

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6009:


Github user andrey-kuznetsov closed the pull request at:

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


> CacheExamplesSelfTest.testCacheSemaphoreExample fails sometimes due to timeout
> --
>
> Key: IGNITE-6009
> URL: https://issues.apache.org/jira/browse/IGNITE-6009
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Ilya Lantukh
>Assignee: Andrey Kuznetsov
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.3
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-7147) Implemente connected clusters component

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov reassigned IGNITE-7147:
--

Assignee: Dmitriy Shabalin  (was: Pavel Konstantinov)

> Implemente connected clusters component
> ---
>
> Key: IGNITE-7147
> URL: https://issues.apache.org/jira/browse/IGNITE-7147
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Dmitriy Shabalin
>Assignee: Dmitriy Shabalin
> Fix For: 2.4
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-7147) Implemente connected clusters component

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-7147:


Please do not show component :
- on home\sign in pages
- in demo mode

> Implemente connected clusters component
> ---
>
> Key: IGNITE-7147
> URL: https://issues.apache.org/jira/browse/IGNITE-7147
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Dmitriy Shabalin
>Assignee: Pavel Konstantinov
> Fix For: 2.4
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-7157) Deadlock on partition eviction from multiple threads.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7157:


GitHub user AMashenkov opened a pull request:

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

IGNITE-7157: Fixed deadlock when partition eviction run in different 
threads.



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

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

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

https://github.com/apache/ignite/pull/3193.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3193


commit cec30537cd08de42ae1be43f36a1fc80c1577b32
Author: Andrey V. Mashenkov 
Date:   2017-12-07T16:16:25Z

IGNITE-7157: Fixed deadlock when partition eviction run in different 
threads.




> Deadlock on partition eviction from multiple threads.
> -
>
> Key: IGNITE-7157
> URL: https://issues.apache.org/jira/browse/IGNITE-7157
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
> Fix For: 2.4
>
> Attachments: thread-dump
>
>
> When node receive partition update message, it acquire partition and 
> checkpoint locks in different order than asyncronous eviction.
> PFA thread dump.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-7157) Deadlock on partition eviction from multiple threads.

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov updated IGNITE-7157:
-
Attachment: thread-dump

> Deadlock on partition eviction from multiple threads.
> -
>
> Key: IGNITE-7157
> URL: https://issues.apache.org/jira/browse/IGNITE-7157
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
> Fix For: 2.4
>
> Attachments: thread-dump
>
>
> When node receive partition update message, it acquire partition and 
> checkpoint locks in different order than asyncronous eviction.
> PFA thread dump.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-7157) Deadlock on partition eviction from multiple threads.

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov reassigned IGNITE-7157:


Assignee: Andrew Mashenkov

> Deadlock on partition eviction from multiple threads.
> -
>
> Key: IGNITE-7157
> URL: https://issues.apache.org/jira/browse/IGNITE-7157
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
> Fix For: 2.4
>
>
> When node receive partition update message, it acquire partition and 
> checkpoint locks in different order than asyncronous eviction.
> PFA thread dump.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-7147) Implemente connected clusters component

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-7147:
-
Fix Version/s: 2.4

> Implemente connected clusters component
> ---
>
> Key: IGNITE-7147
> URL: https://issues.apache.org/jira/browse/IGNITE-7147
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Dmitriy Shabalin
>Assignee: Alexey Kuznetsov
> Fix For: 2.4
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)