[jira] [Updated] (IGNITE-15457) Move thread pools metrics registration to pool processor.
[ https://issues.apache.org/jira/browse/IGNITE-15457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Petrov updated IGNITE-15457: Summary: Move thread pools metrics registration to pool processor. (was: Move polls metrics registration to pool processor.) > Move thread pools metrics registration to pool processor. > - > > Key: IGNITE-15457 > URL: https://issues.apache.org/jira/browse/IGNITE-15457 > Project: Ignite > Issue Type: Improvement >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > It is needed to move Ignite pool metrics registration to PoolProcessor. It > helps to encapsulate pools related logic in one place and take the load off > the IgniteKernal. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15457) Move thread pools metrics registration to pool processor.
[ https://issues.apache.org/jira/browse/IGNITE-15457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Petrov updated IGNITE-15457: Description: It is needed to move Ignite thread pool metrics registration to PoolProcessor. It helps to encapsulate tread pools related logic in one place and take the load off the IgniteKernal. (was: It is needed to move Ignite pool metrics registration to PoolProcessor. It helps to encapsulate pools related logic in one place and take the load off the IgniteKernal.) > Move thread pools metrics registration to pool processor. > - > > Key: IGNITE-15457 > URL: https://issues.apache.org/jira/browse/IGNITE-15457 > Project: Ignite > Issue Type: Improvement >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > It is needed to move Ignite thread pool metrics registration to > PoolProcessor. It helps to encapsulate tread pools related logic in one place > and take the load off the IgniteKernal. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-15474) Describe RAFT threading model in the module documentation
Alexey Scherbakov created IGNITE-15474: -- Summary: Describe RAFT threading model in the module documentation Key: IGNITE-15474 URL: https://issues.apache.org/jira/browse/IGNITE-15474 Project: Ignite Issue Type: Task Reporter: Alexey Scherbakov Assignee: Alexey Scherbakov Fix For: 3.0.0-alpha3 This is a documentation improvement task -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-15470) Java thin client: Use partition awareness for ScanQuery with specified partition
[
https://issues.apache.org/jira/browse/IGNITE-15470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17411756#comment-17411756
]
Ignite TC Bot commented on IGNITE-15470:
{panel:title=Branch: [pull/9384/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9384/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Thin Client: Java{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6169269]]
* {color:#013220}ClientTestSuite:
ThinClientPartitionAwarenessStableTopologyTest.testScanQuery - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6169348&buildTypeId=IgniteTests24Java8_RunAll]
> Java thin client: Use partition awareness for ScanQuery with specified
> partition
>
>
> Key: IGNITE-15470
> URL: https://issues.apache.org/jira/browse/IGNITE-15470
> Project: Ignite
> Issue Type: Improvement
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, partition awareness is used by java thin client only for
> single-key operations.
> For scan queries we can also use the benefits of partition awareness if
> partition for the query is specified explicitly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-15456) Integrate RocksDBKeyValueStorage into the production code
[ https://issues.apache.org/jira/browse/IGNITE-15456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17411760#comment-17411760 ] Ivan Bessonov commented on IGNITE-15456: Looks good to me, I'll merge it > Integrate RocksDBKeyValueStorage into the production code > - > > Key: IGNITE-15456 > URL: https://issues.apache.org/jira/browse/IGNITE-15456 > Project: Ignite > Issue Type: Task >Reporter: Aleksandr Polovtcev >Assignee: Aleksandr Polovtcev >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha3 > > Time Spent: 40m > Remaining Estimate: 0h > > Persistent storage for the MetaStorage has been introduced in IGNITE-14982, > but it hasn't been integrated into the production code, > SimpleInMemoryKeyValueStorage is still used instead and should be replaced. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-15384) Daemon node fails to perform any operation that requires authorization with security enabled.
[
https://issues.apache.org/jira/browse/IGNITE-15384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17411766#comment-17411766
]
Mikhail Petrov commented on IGNITE-15384:
-
[~NSAmelchev], thanks a lot for the review.
> Daemon node fails to perform any operation that requires authorization with
> security enabled.
> -
>
> Key: IGNITE-15384
> URL: https://issues.apache.org/jira/browse/IGNITE-15384
> Project: Ignite
> Issue Type: Bug
>Reporter: Mikhail Petrov
>Assignee: Mikhail Petrov
>Priority: Major
> Fix For: 2.12
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Exception:
> {code:java}
> java.lang.AssertionError
> at
> org.apache.ignite.internal.processors.security.IgniteSecurityProcessor.authorize(IgniteSecurityProcessor.java:232)
> at
> org.apache.ignite.internal.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:617)
> at
> org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:508)
> at
> org.apache.ignite.internal.processors.closure.GridClosureProcessor.runAsync(GridClosureProcessor.java:244)
> at
> org.apache.ignite.internal.processors.closure.GridClosureProcessor.runAsync(GridClosureProcessor.java:216)
> at
> org.apache.ignite.internal.IgniteComputeImpl.runAsync0(IgniteComputeImpl.java:690)
> at
> org.apache.ignite.internal.IgniteComputeImpl.runAsync(IgniteComputeImpl.java:675)
> at
> org.apache.ignite.internal.processors.cluster.GridClusterStateProcessor.sendComputeChangeGlobalState(GridClusterStateProcessor.java:1381)
> at
> org.apache.ignite.internal.processors.cluster.GridClusterStateProcessor.changeGlobalState(GridClusterStateProcessor.java:1125)
> at
> org.apache.ignite.internal.processors.cluster.GridClusterStateProcessor.changeGlobalState(GridClusterStateProcessor.java:1026)
> at
> org.apache.ignite.internal.cluster.IgniteClusterImpl.state(IgniteClusterImpl.java:379)
> at org.apache.ignite.TestClass.test(TestClass.java:48)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> {code}
> Reproducer:
> {code:java}
> /** */
> public class TestClass extends AbstractSecurityTest {
> /** */
> @Override protected IgniteConfiguration getConfiguration(
> String instanceName,
> AbstractTestSecurityPluginProvider pluginProv
> ) throws Exception {
> return super.getConfiguration(instanceName, pluginProv)
> .setDaemon(instanceName.contains("daemon"))
> .setClusterStateOnStart(INACTIVE);
> }
> /** */
> @Test
> public void test() throws Exception {
> startGridAllowAll("crd");
> IgniteEx daemonNode = startGridAllowAll("daemon");
> daemonNode.cluster().state(ACTIVE);
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-15300) Test testSnapshotRestoreCancelAndStatus flaky in Zookeepr SPI environment
[
https://issues.apache.org/jira/browse/IGNITE-15300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17411795#comment-17411795
]
Pavel Pereslegin commented on IGNITE-15300:
---
The test hangs when the restore process is initiated from node 1, whose
communication is later blocked (and cannot be unblocked).
The test flaky fails due to a state sync issue. We are canceling the process on
two nodes, but only waiting on the initiator to complete (this has been fixed
in IGNITE-14794).
It looks like the patch proposed in IGNITE-14794 fixes this completely.
Checked it on TeamCity (the problem is hardly reproducible locally), suite
started 80+ times.
Execution timeouts (not related to this issue) - 2 times.
testBaselineCollectCrd - 6 failures.
testBaselineCollect - 1 failure.
testSnapshotRestoreCancelAndStatus - *0* failures.
> Test testSnapshotRestoreCancelAndStatus flaky in Zookeepr SPI environment
> -
>
> Key: IGNITE-15300
> URL: https://issues.apache.org/jira/browse/IGNITE-15300
> Project: Ignite
> Issue Type: Test
>Reporter: Maxim Muzafarov
>Assignee: Pavel Pereslegin
>Priority: Major
> Labels: iep-43
> Time Spent: 10m
> Remaining Estimate: 0h
>
> https://ci.ignite.apache.org/viewLog.html?buildId=6123288&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_ControlUtilityZookeeper#testNameId-4389213602152674112
> {code}
> [2021-08-09 22:59:49,757][ERROR][main][root] Test failed
> [test=GridCommandHandlerTest#testSnapshotRestoreCancelAndStatus,
> duration=16514]
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertTrue(Assert.java:52)
> at
> org.apache.ignite.testframework.GridTestUtils.assertContains(GridTestUtils.java:391)
> at
> org.apache.ignite.util.GridCommandHandlerTest.testSnapshotRestoreCancelAndStatus(GridCommandHandlerTest.java:3312)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2432)
> {code}
> Sometimes zk suite hangs ([execution
> timeout|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_ControlUtilityZookeeper&tab=buildTypeHistoryList&branch_IgniteTests24Java8=%3Cdefault%3E&state=failed])
> on this test with the following stacktrace.
> {noformat}
> "rest-#15365%gridCommandHandlerTest0%" #16591 prio=5 os_prio=0
> tid=0x7f7e7842b800 nid=0x1a79 waiting on condition [0x7f7e30416000]
>java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:178)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:141)
> at
> org.apache.ignite.internal.util.future.IgniteFutureImpl.get(IgniteFutureImpl.java:152)
> at
> org.apache.ignite.internal.processors.cache.persistence.snapshot.SnapshotRestoreCancelTask$1.execute(SnapshotRestoreCancelTask.java:43)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:601)
> at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:7270)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:595)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:522)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:125)
> at
> org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1305)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.sendRequest(GridTaskWorker.java:1435)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.processMappedJobs(GridTaskWorker.java:665)
> at
> org.apache.
[jira] [Comment Edited] (IGNITE-15300) Test testSnapshotRestoreCancelAndStatus flaky in Zookeepr SPI environment
[
https://issues.apache.org/jira/browse/IGNITE-15300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17411795#comment-17411795
]
Pavel Pereslegin edited comment on IGNITE-15300 at 9/8/21, 8:50 AM:
The test hangs when the restore process is initiated from node 1, whose
communication is later blocked (and cannot be unblocked).
The test flaky fails due to a state sync issue. We are canceling the process on
two nodes, but only waiting on the initiator to complete (this has been fixed
in IGNITE-14794).
It looks like the patch proposed in IGNITE-14794 fixes this completely.
Checked it on TeamCity (the problem is hardly reproducible locally), [suite
started 80+
times|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_ControlUtilityZookeeper&tab=buildTypeHistoryList&branch_IgniteTests24Java8=pull%2F9186%2Fhead].
Execution timeouts (not related to this issue) - 2 times.
testBaselineCollectCrd - 6 failures.
testBaselineCollect - 1 failure.
testSnapshotRestoreCancelAndStatus - *0* failures.
was (Author: xtern):
The test hangs when the restore process is initiated from node 1, whose
communication is later blocked (and cannot be unblocked).
The test flaky fails due to a state sync issue. We are canceling the process on
two nodes, but only waiting on the initiator to complete (this has been fixed
in IGNITE-14794).
It looks like the patch proposed in IGNITE-14794 fixes this completely.
Checked it on TeamCity (the problem is hardly reproducible locally), suite
started 80+ times.
Execution timeouts (not related to this issue) - 2 times.
testBaselineCollectCrd - 6 failures.
testBaselineCollect - 1 failure.
testSnapshotRestoreCancelAndStatus - *0* failures.
> Test testSnapshotRestoreCancelAndStatus flaky in Zookeepr SPI environment
> -
>
> Key: IGNITE-15300
> URL: https://issues.apache.org/jira/browse/IGNITE-15300
> Project: Ignite
> Issue Type: Test
>Reporter: Maxim Muzafarov
>Assignee: Pavel Pereslegin
>Priority: Major
> Labels: iep-43
> Time Spent: 10m
> Remaining Estimate: 0h
>
> https://ci.ignite.apache.org/viewLog.html?buildId=6123288&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_ControlUtilityZookeeper#testNameId-4389213602152674112
> {code}
> [2021-08-09 22:59:49,757][ERROR][main][root] Test failed
> [test=GridCommandHandlerTest#testSnapshotRestoreCancelAndStatus,
> duration=16514]
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertTrue(Assert.java:52)
> at
> org.apache.ignite.testframework.GridTestUtils.assertContains(GridTestUtils.java:391)
> at
> org.apache.ignite.util.GridCommandHandlerTest.testSnapshotRestoreCancelAndStatus(GridCommandHandlerTest.java:3312)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2432)
> {code}
> Sometimes zk suite hangs ([execution
> timeout|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_ControlUtilityZookeeper&tab=buildTypeHistoryList&branch_IgniteTests24Java8=%3Cdefault%3E&state=failed])
> on this test with the following stacktrace.
> {noformat}
> "rest-#15365%gridCommandHandlerTest0%" #16591 prio=5 os_prio=0
> tid=0x7f7e7842b800 nid=0x1a79 waiting on condition [0x7f7e30416000]
>java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:178)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:141)
> at
> org.apache.ignite.internal.util.future.IgniteFutureImpl.get(IgniteFutureImpl.java:152)
> at
> org.apache.ignite.internal.processors.cache.persistence.snapshot.SnapshotRestoreCancelTask$1.execute(
[jira] [Comment Edited] (IGNITE-15300) Test testSnapshotRestoreCancelAndStatus flaky in Zookeepr SPI environment
[
https://issues.apache.org/jira/browse/IGNITE-15300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17411795#comment-17411795
]
Pavel Pereslegin edited comment on IGNITE-15300 at 9/8/21, 8:54 AM:
The test hangs when the restore process is initiated from node 1, whose
communication is later blocked (and cannot be unblocked).
The test flaky fails due to a state sync issue. We are canceling the process on
two nodes, but only waiting on the initiator to complete (this has been fixed
in IGNITE-14794).
It looks like the patch proposed in IGNITE-14794 fixes this completely. Checked
it on TeamCity (the problem is hardly reproducible locally), [suite started 80+
times|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_ControlUtilityZookeeper&tab=buildTypeHistoryList&branch_IgniteTests24Java8=pull%2F9186%2Fhead]:
* Execution timeouts (not related to this issue) - 2 times.
* testBaselineCollectCrd - 6 failures.
* testBaselineCollect - 1 failure.
* testSnapshotRestoreCancelAndStatus - *0* failures.
was (Author: xtern):
The test hangs when the restore process is initiated from node 1, whose
communication is later blocked (and cannot be unblocked).
The test flaky fails due to a state sync issue. We are canceling the process on
two nodes, but only waiting on the initiator to complete (this has been fixed
in IGNITE-14794).
It looks like the patch proposed in IGNITE-14794 fixes this completely.
Checked it on TeamCity (the problem is hardly reproducible locally), [suite
started 80+
times|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_ControlUtilityZookeeper&tab=buildTypeHistoryList&branch_IgniteTests24Java8=pull%2F9186%2Fhead].
Execution timeouts (not related to this issue) - 2 times.
testBaselineCollectCrd - 6 failures.
testBaselineCollect - 1 failure.
testSnapshotRestoreCancelAndStatus - *0* failures.
> Test testSnapshotRestoreCancelAndStatus flaky in Zookeepr SPI environment
> -
>
> Key: IGNITE-15300
> URL: https://issues.apache.org/jira/browse/IGNITE-15300
> Project: Ignite
> Issue Type: Test
>Reporter: Maxim Muzafarov
>Assignee: Pavel Pereslegin
>Priority: Major
> Labels: iep-43
> Time Spent: 10m
> Remaining Estimate: 0h
>
> https://ci.ignite.apache.org/viewLog.html?buildId=6123288&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_ControlUtilityZookeeper#testNameId-4389213602152674112
> {code}
> [2021-08-09 22:59:49,757][ERROR][main][root] Test failed
> [test=GridCommandHandlerTest#testSnapshotRestoreCancelAndStatus,
> duration=16514]
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertTrue(Assert.java:52)
> at
> org.apache.ignite.testframework.GridTestUtils.assertContains(GridTestUtils.java:391)
> at
> org.apache.ignite.util.GridCommandHandlerTest.testSnapshotRestoreCancelAndStatus(GridCommandHandlerTest.java:3312)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2432)
> {code}
> Sometimes zk suite hangs ([execution
> timeout|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_ControlUtilityZookeeper&tab=buildTypeHistoryList&branch_IgniteTests24Java8=%3Cdefault%3E&state=failed])
> on this test with the following stacktrace.
> {noformat}
> "rest-#15365%gridCommandHandlerTest0%" #16591 prio=5 os_prio=0
> tid=0x7f7e7842b800 nid=0x1a79 waiting on condition [0x7f7e30416000]
>java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:178)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:141)
> at
> org.apache.ignite.interna
[jira] [Commented] (IGNITE-15457) Move thread pools metrics registration to pool processor.
[ https://issues.apache.org/jira/browse/IGNITE-15457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17411818#comment-17411818 ] Nikolay Izhikov commented on IGNITE-15457: -- LGTM > Move thread pools metrics registration to pool processor. > - > > Key: IGNITE-15457 > URL: https://issues.apache.org/jira/browse/IGNITE-15457 > Project: Ignite > Issue Type: Improvement >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > It is needed to move Ignite thread pool metrics registration to > PoolProcessor. It helps to encapsulate tread pools related logic in one place > and take the load off the IgniteKernal. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-15288) Fully implement RaftGroupService
[ https://issues.apache.org/jira/browse/IGNITE-15288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17411823#comment-17411823 ] Alexander Lapin commented on IGNITE-15288: -- [~kgusakov] Please check my comments in PR. > Fully implement RaftGroupService > > > Key: IGNITE-15288 > URL: https://issues.apache.org/jira/browse/IGNITE-15288 > Project: Ignite > Issue Type: Improvement >Affects Versions: 3.0.0-alpha2 >Reporter: Alexey Scherbakov >Assignee: Kirill Gusakov >Priority: Major > Labels: ignite-3 > Time Spent: 5h 10m > Remaining Estimate: 0h > > There are two ways to achive this: > 1) Delegate to org.apache.ignite.raft.jraft.rpc.impl.cli.CliClientServiceImpl > by introducing dependency from ignite-client to ignite-raft (and removing > opposite dependency) > 2) Copy org.apache.ignite.raft.jraft.rpc.CliRequests messages to raft-client > and adjust RaftGroupServiceImpl to send these messages. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-15475) Describe SQL threading model in the module documentation
Yury Gerzhedovich created IGNITE-15475: -- Summary: Describe SQL threading model in the module documentation Key: IGNITE-15475 URL: https://issues.apache.org/jira/browse/IGNITE-15475 Project: Ignite Issue Type: Task Components: sql Reporter: Yury Gerzhedovich Fix For: 3.0.0-alpha3 It is necessary to prepare a description of the threading model for the SQL part. The description should contain a list of the pools used and the data flow between the pool flows when sending and receiving messages. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-15469) Update Ignite dependency: MySQL Connector
[ https://issues.apache.org/jira/browse/IGNITE-15469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17411853#comment-17411853 ] Andrey Mashenkov edited comment on IGNITE-15469 at 9/8/21, 10:51 AM: - There are unrelated changes in the PR. was (Author: amashenkov): There are unrelated changed in the PR. > Update Ignite dependency: MySQL Connector > -- > > Key: IGNITE-15469 > URL: https://issues.apache.org/jira/browse/IGNITE-15469 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr >Assignee: Aleksandr >Priority: Major > Labels: newbie > Fix For: 2.12 > > Time Spent: 20m > Remaining Estimate: 0h > > Update Ignite dependency: MySQL Connector 8.0.13 to 8.0.26 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-15476) Possibility of tunning SQL thread pools
Yury Gerzhedovich created IGNITE-15476: -- Summary: Possibility of tunning SQL thread pools Key: IGNITE-15476 URL: https://issues.apache.org/jira/browse/IGNITE-15476 Project: Ignite Issue Type: Improvement Components: sql Reporter: Yury Gerzhedovich Fix For: 3.0.0-alpha3 Need to introduce the ability to tune SQL thread pools through configuration and create a separate task to document each of them. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15461) Bugyard feedback #6: Specify that near-caches are not created on thin clients
[ https://issues.apache.org/jira/browse/IGNITE-15461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-15461: -- Fix Version/s: 2.12 > Bugyard feedback #6: Specify that near-caches are not created on thin clients > - > > Key: IGNITE-15461 > URL: https://issues.apache.org/jira/browse/IGNITE-15461 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Igor Gusev >Assignee: Igor Gusev >Priority: Major > Fix For: 2.12 > > Time Spent: 20m > Remaining Estimate: 0h > > Bugyard feedback 6 asks if near caches are available on thin clients. We > should specify that it only affects thick clients and servers on the near > cache page > https://ignite.apache.org/docs/latest/configuring-caches/near-cache. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-15107) Integrate DDL handler into Ignite 3.0
[
https://issues.apache.org/jira/browse/IGNITE-15107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17411856#comment-17411856
]
Evgeny Stanilovsky commented on IGNITE-15107:
-
[~korlov] [~amashenkov] guys thanks ! i fix all your comments.
> Integrate DDL handler into Ignite 3.0
> -
>
> Key: IGNITE-15107
> URL: https://issues.apache.org/jira/browse/IGNITE-15107
> Project: Ignite
> Issue Type: Sub-task
> Components: sql
>Reporter: Konstantin Orlov
>Assignee: Evgeny Stanilovsky
>Priority: Major
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> Need to implement handler of the following basic commands:
> * Create table
> * Alter table
> * Drop table
> * Create index
> * Drop index
> Reference point is
> {{org.apache.ignite.internal.processors.query.calcite.exec.ddl.DdlCommandHandler}}.
> Required tests are available in following classes:
> {{org.apache.ignite.internal.processors.query.calcite.integration.IndexDdlIntegrationTest}}
> {{org.apache.ignite.internal.processors.query.calcite.integration.TableDdlIntegrationTest}}
> NB: all referenced classes are resided in ignite-2 codebase in
> {{sql-calcite}} branch.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-15457) Move thread pools metrics registration to pool processor.
[ https://issues.apache.org/jira/browse/IGNITE-15457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17411861#comment-17411861 ] Andrey Mashenkov commented on IGNITE-15457: --- Would you mind to change legacy prefixed in processors names, e.g. "GridUtilityCacheExecutor" -> "IgniteUtilityCacheExecutor"? Overall PR looks good. > Move thread pools metrics registration to pool processor. > - > > Key: IGNITE-15457 > URL: https://issues.apache.org/jira/browse/IGNITE-15457 > Project: Ignite > Issue Type: Improvement >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > It is needed to move Ignite thread pool metrics registration to > PoolProcessor. It helps to encapsulate tread pools related logic in one place > and take the load off the IgniteKernal. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-15457) Move thread pools metrics registration to pool processor.
[ https://issues.apache.org/jira/browse/IGNITE-15457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17411861#comment-17411861 ] Andrey Mashenkov edited comment on IGNITE-15457 at 9/8/21, 11:11 AM: - I don't insist, but would you mind to change legacy prefixed in processors names, e.g. "GridUtilityCacheExecutor" -> "IgniteUtilityCacheExecutor"? Overall PR looks good. was (Author: amashenkov): Would you mind to change legacy prefixed in processors names, e.g. "GridUtilityCacheExecutor" -> "IgniteUtilityCacheExecutor"? Overall PR looks good. > Move thread pools metrics registration to pool processor. > - > > Key: IGNITE-15457 > URL: https://issues.apache.org/jira/browse/IGNITE-15457 > Project: Ignite > Issue Type: Improvement >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > It is needed to move Ignite thread pool metrics registration to > PoolProcessor. It helps to encapsulate tread pools related logic in one place > and take the load off the IgniteKernal. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-15457) Move thread pools metrics registration to pool processor.
[ https://issues.apache.org/jira/browse/IGNITE-15457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17411861#comment-17411861 ] Andrey Mashenkov edited comment on IGNITE-15457 at 9/8/21, 11:11 AM: - I don't insist, but would you mind changing legacy prefixed in processors names, e.g. "GridUtilityCacheExecutor" -> "IgniteUtilityCacheExecutor"? Overall PR looks good. was (Author: amashenkov): I don't insist, but would you mind to change legacy prefixed in processors names, e.g. "GridUtilityCacheExecutor" -> "IgniteUtilityCacheExecutor"? Overall PR looks good. > Move thread pools metrics registration to pool processor. > - > > Key: IGNITE-15457 > URL: https://issues.apache.org/jira/browse/IGNITE-15457 > Project: Ignite > Issue Type: Improvement >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > It is needed to move Ignite thread pool metrics registration to > PoolProcessor. It helps to encapsulate tread pools related logic in one place > and take the load off the IgniteKernal. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-15475) Describe SQL threading model in the module documentation
[ https://issues.apache.org/jira/browse/IGNITE-15475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Orlov reassigned IGNITE-15475: - Assignee: Konstantin Orlov > Describe SQL threading model in the module documentation > > > Key: IGNITE-15475 > URL: https://issues.apache.org/jira/browse/IGNITE-15475 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Yury Gerzhedovich >Assignee: Konstantin Orlov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha3 > > > It is necessary to prepare a description of the threading model for the SQL > part. The description should contain a list of the pools used and the data > flow between the pool flows when sending and receiving messages. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-15477) Describe messaging service threading model in network module documentation
Sergey Chugunov created IGNITE-15477: Summary: Describe messaging service threading model in network module documentation Key: IGNITE-15477 URL: https://issues.apache.org/jira/browse/IGNITE-15477 Project: Ignite Issue Type: Task Components: networking Reporter: Sergey Chugunov Fix For: 3.0.0-alpha3 The following points should be covered in Readme.MD of network module: # List of thread pools with threads' naming. # Data flow between threads processing incoming and outgoing messages for different nodes. # Message handling guarantees: listeners calling order etc. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-15457) Move thread pools metrics registration to pool processor.
[ https://issues.apache.org/jira/browse/IGNITE-15457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17411889#comment-17411889 ] Mikhail Petrov commented on IGNITE-15457: - [~amashenkov], I'm not sure, but aren't the metric names part of the public API? Since the use of metrics after they have been exported by the user is based on their names, we cannot so easily change them. WDYT? > Move thread pools metrics registration to pool processor. > - > > Key: IGNITE-15457 > URL: https://issues.apache.org/jira/browse/IGNITE-15457 > Project: Ignite > Issue Type: Improvement >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > It is needed to move Ignite thread pool metrics registration to > PoolProcessor. It helps to encapsulate tread pools related logic in one place > and take the load off the IgniteKernal. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-15107) Integrate DDL handler into Ignite 3.0
[
https://issues.apache.org/jira/browse/IGNITE-15107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17411890#comment-17411890
]
Andrey Mashenkov commented on IGNITE-15107:
---
[~zstan], please check TC. There is a compilation issue.
> Integrate DDL handler into Ignite 3.0
> -
>
> Key: IGNITE-15107
> URL: https://issues.apache.org/jira/browse/IGNITE-15107
> Project: Ignite
> Issue Type: Sub-task
> Components: sql
>Reporter: Konstantin Orlov
>Assignee: Evgeny Stanilovsky
>Priority: Major
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> Need to implement handler of the following basic commands:
> * Create table
> * Alter table
> * Drop table
> * Create index
> * Drop index
> Reference point is
> {{org.apache.ignite.internal.processors.query.calcite.exec.ddl.DdlCommandHandler}}.
> Required tests are available in following classes:
> {{org.apache.ignite.internal.processors.query.calcite.integration.IndexDdlIntegrationTest}}
> {{org.apache.ignite.internal.processors.query.calcite.integration.TableDdlIntegrationTest}}
> NB: all referenced classes are resided in ignite-2 codebase in
> {{sql-calcite}} branch.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-15469) Update Ignite dependency: MySQL Connector
[
https://issues.apache.org/jira/browse/IGNITE-15469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17411901#comment-17411901
]
Ignite TC Bot commented on IGNITE-15469:
{panel:title=Branch: [pull/9385/head] Base: [master] : Possible Blockers
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 6{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6170542]]
{panel}
{panel:title=Branch: [pull/9385/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6170582&buildTypeId=IgniteTests24Java8_RunAll]
> Update Ignite dependency: MySQL Connector
> --
>
> Key: IGNITE-15469
> URL: https://issues.apache.org/jira/browse/IGNITE-15469
> Project: Ignite
> Issue Type: Improvement
>Reporter: Aleksandr
>Assignee: Aleksandr
>Priority: Major
> Labels: newbie
> Fix For: 2.12
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Update Ignite dependency: MySQL Connector 8.0.13 to 8.0.26
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14703) Add merge-sort reducer for cache queries.
[ https://issues.apache.org/jira/browse/IGNITE-14703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17411904#comment-17411904 ] Andrey Mashenkov commented on IGNITE-14703: --- [~timonin.maksim], now looks much better. I've left few comments to the PR. Please, just keep in mind, there may be 1k+ nodes in the grid. So, having redundant collections or iterating over collections may cost a bit. > Add merge-sort reducer for cache queries. > - > > Key: IGNITE-14703 > URL: https://issues.apache.org/jira/browse/IGNITE-14703 > Project: Ignite > Issue Type: New Feature >Reporter: Maksim Timonin >Assignee: Maksim Timonin >Priority: Major > Labels: IEP-71 > Time Spent: 20h 50m > Remaining Estimate: 0h > > MergeSort reducer is required for TextQueries (and IndexQuery in future) that > should provide a sorted result for user. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-15344) Reduce amount of output for printing node2part map
[
https://issues.apache.org/jira/browse/IGNITE-15344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17411915#comment-17411915
]
Chandresh Pancholi commented on IGNITE-15344:
-
[~mmuzaf] I was going through the code for first contribution. nodeId is a UUID
and shown here is an integer. is this the right format?
> Reduce amount of output for printing node2part map
> --
>
> Key: IGNITE-15344
> URL: https://issues.apache.org/jira/browse/IGNITE-15344
> Project: Ignite
> Issue Type: Task
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Major
> Labels: newbie
>
> _Current output_
> {code}
> GridDhtPartitionFullMap [nodeId=768c4f3b-95e3-411b-b341-e93129b0,
> nodeOrder=1, updateSeq=3, size=2,
> map={bb16a275-c308-477b-a13b-723f5421=GridDhtPartitionMap [moving=0,
> top=AffinityTopologyVersion [topVer=2, minorTopVer=1], updateSeq=2, size=100,
> map={0=OWNING, 1=OWNING, 2=OWNING, 3=OWNING, 4=OWNING, 5=OWNING, 6=OWNING,
> 7=OWNING, 8=OWNING, 9=OWNING, 10=OWNING, 11=OWNING, 12=OWNING, 13=OWNING,
> 14=OWNING, 15=OWNING, 16=OWNING, 17=OWNING, 18=OWNING, 19=OWNING, 20=OWNING,
> 21=OWNING, 22=OWNING, 23=OWNING, 24=OWNING, 25=OWNING, 26=OWNING, 27=OWNING,
> 28=OWNING, 29=OWNING, 30=OWNING, 31=OWNING, 32=OWNING, 33=OWNING, 34=OWNING,
> 35=OWNING, 36=OWNING, 37=OWNING, 38=OWNING, 39=OWNING, 40=OWNING, 41=OWNING,
> 42=OWNING, 43=OWNING, 44=OWNING, 45=OWNING, 46=OWNING, 47=OWNING, 48=OWNING,
> 49=OWNING, 50=OWNING, 51=OWNING, 52=OWNING, 53=OWNING, 54=OWNING, 55=OWNING,
> 56=OWNING, 57=OWNING, 58=OWNING, 59=OWNING, 60=OWNING, 61=OWNING, 62=OWNING,
> 63=OWNING, 64=OWNING, 65=OWNING, 66=OWNING, 67=OWNING, 68=OWNING, 69=OWNING,
> 70=OWNING, 71=OWNING, 72=OWNING, 73=OWNING, 74=OWNING, 75=OWNING, 76=OWNING,
> 77=OWNING, 78=OWNING, 79=OWNING, 80=OWNING, 81=OWNING, 82=OWNING, 83=OWNING,
> 84=OWNING, 85=OWNING, 86=OWNING, 87=OWNING, 88=OWNING, 89=OWNING, 90=OWNING,
> 91=OWNING, 92=OWNING, 93=OWNING, 94=OWNING, 95=OWNING, 96=OWNING, 97=OWNING,
> 98=OWNING, 99=OWNING}],
> {code}
> _Proposed output_
> {code}
> GridDhtPartitionFullMap [nodeId=768c4f3b-95e3-411b-b341-e93129b0,
> nodeOrder=1, updateSeq=3, size=2,
> map={bb16a275-c308-477b-a13b-723f5421=GridDhtPartitionMap [moving=0,
> top=AffinityTopologyVersion [topVer=2, minorTopVer=1], updateSeq=2, size=100,
> map={OWNING=0-100}],
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-15457) Move thread pools metrics registration to pool processor.
[ https://issues.apache.org/jira/browse/IGNITE-15457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17411919#comment-17411919 ] Andrey Mashenkov commented on IGNITE-15457: --- [~PetrovMikhail], agree. We can do this in the next major release. > Move thread pools metrics registration to pool processor. > - > > Key: IGNITE-15457 > URL: https://issues.apache.org/jira/browse/IGNITE-15457 > Project: Ignite > Issue Type: Improvement >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > It is needed to move Ignite thread pool metrics registration to > PoolProcessor. It helps to encapsulate tread pools related logic in one place > and take the load off the IgniteKernal. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-15457) Move thread pools metrics registration to pool processor.
[
https://issues.apache.org/jira/browse/IGNITE-15457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17411920#comment-17411920
]
Ignite TC Bot commented on IGNITE-15457:
{panel:title=Branch: [pull/9381/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9381/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6168534&buildTypeId=IgniteTests24Java8_RunAll]
> Move thread pools metrics registration to pool processor.
> -
>
> Key: IGNITE-15457
> URL: https://issues.apache.org/jira/browse/IGNITE-15457
> Project: Ignite
> Issue Type: Improvement
>Reporter: Mikhail Petrov
>Assignee: Mikhail Petrov
>Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> It is needed to move Ignite thread pool metrics registration to
> PoolProcessor. It helps to encapsulate tread pools related logic in one place
> and take the load off the IgniteKernal.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13631) Improve names and descriptions of data storage metrics
[ https://issues.apache.org/jira/browse/IGNITE-13631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17411923#comment-17411923 ] Andrey Mashenkov commented on IGNITE-13631: --- [~dmekhanikov], [~agura], is it actual? > Improve names and descriptions of data storage metrics > -- > > Key: IGNITE-13631 > URL: https://issues.apache.org/jira/browse/IGNITE-13631 > Project: Ignite > Issue Type: Improvement >Reporter: Denis Mekhanikov >Assignee: Denis Mekhanikov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Data storage metrics have unclear descriptions. They need to be improved. > ||Metric||Description||Comment|| > |*WalLoggingRate*|Average number of WAL records per second written during the > last time interval.|The "time interval" part is unclear. Which time interval?| > |*WalFsyncTimeDuration*|Total duration of fsync|Why not just > *WalFsyncDuration*? > The description could be more verbose.| > |*WalFsyncTimeNum*|Total count of fsync|Why not just *WalFsyncNum*? The > description could be more verbose| > |*WalBuffPollSpinsRate*|WAL buffer poll spins number over the last time > interval. |Over which time interval?| > |*LastCheckpointMarkDuration*|Duration of the checkpoint lock wait in > milliseconds |The description doesn't match the name.| > |*CheckpointTotalTime*|Total duration of checkpoint|Is it the duration of the > last checkpoint or all checkpoints from the beginning?| > |*StorageSize*|Storage space allocated, in bytes.|It's unclear which storage > this is about. Is disk included, or is it just about memory?| > |*WalTotalSize*|Total size in bytes for storage wal files.|WAL should be > capital. The grammar| -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-15478) Add access to the IgniteMBeanManager via KernalContext
Mikhail Petrov created IGNITE-15478: --- Summary: Add access to the IgniteMBeanManager via KernalContext Key: IGNITE-15478 URL: https://issues.apache.org/jira/browse/IGNITE-15478 Project: Ignite Issue Type: Improvement Reporter: Mikhail Petrov It is needed to add an access to the IgniteMBeanManager via KernalContext. It helps to access the IgniteMBeanManager in the same way as for other Ignite components, and allows Ignite components to register needed MBeans from their own implementations. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15478) Add access to the IgniteMBeanManager via KernalContext
[ https://issues.apache.org/jira/browse/IGNITE-15478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Petrov updated IGNITE-15478: Description: It is needed to add an access to the IgniteMBeanManager via KernalContext. It helps to access the IgniteMBeanManager in the same way as for other Ignite components, and allows Ignite components to register needed MBeans from their own implementations. It's also proposed to refactor MBeans registration to be performed explicitly via IgniteMBeanManager. was:It is needed to add an access to the IgniteMBeanManager via KernalContext. It helps to access the IgniteMBeanManager in the same way as for other Ignite components, and allows Ignite components to register needed MBeans from their own implementations. > Add access to the IgniteMBeanManager via KernalContext > -- > > Key: IGNITE-15478 > URL: https://issues.apache.org/jira/browse/IGNITE-15478 > Project: Ignite > Issue Type: Improvement >Reporter: Mikhail Petrov >Priority: Minor > > It is needed to add an access to the IgniteMBeanManager via KernalContext. It > helps to access the IgniteMBeanManager in the same way as for other Ignite > components, and allows Ignite components to register needed MBeans from their > own implementations. > It's also proposed to refactor MBeans registration to be performed explicitly > via IgniteMBeanManager. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15478) Add access to the IgniteMBeanManager via KernalContext
[ https://issues.apache.org/jira/browse/IGNITE-15478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Petrov updated IGNITE-15478: Description: It is needed to add an access to the IgniteMBeanManager via KernalContext. It helps to access the IgniteMBeanManager in the same way as for other Ignite components, and allows Ignite components to register needed MBeans from their own implementations. It's also proposed to refactor MBeans registration to be performed explicitly via IgniteMBeanManager. As an example we can eliminate GridQueryIndexing#registerMxBeans method and registers beans directly. was: It is needed to add an access to the IgniteMBeanManager via KernalContext. It helps to access the IgniteMBeanManager in the same way as for other Ignite components, and allows Ignite components to register needed MBeans from their own implementations. It's also proposed to refactor MBeans registration to be performed explicitly via IgniteMBeanManager. > Add access to the IgniteMBeanManager via KernalContext > -- > > Key: IGNITE-15478 > URL: https://issues.apache.org/jira/browse/IGNITE-15478 > Project: Ignite > Issue Type: Improvement >Reporter: Mikhail Petrov >Priority: Minor > > It is needed to add an access to the IgniteMBeanManager via KernalContext. It > helps to access the IgniteMBeanManager in the same way as for other Ignite > components, and allows Ignite components to register needed MBeans from their > own implementations. > It's also proposed to refactor MBeans registration to be performed explicitly > via IgniteMBeanManager. As an example we can eliminate > GridQueryIndexing#registerMxBeans method and registers beans directly. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-15344) Reduce amount of output for printing node2part map
[
https://issues.apache.org/jira/browse/IGNITE-15344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov reassigned IGNITE-15344:
Assignee: (was: Maxim Muzafarov)
> Reduce amount of output for printing node2part map
> --
>
> Key: IGNITE-15344
> URL: https://issues.apache.org/jira/browse/IGNITE-15344
> Project: Ignite
> Issue Type: Task
>Reporter: Maxim Muzafarov
>Priority: Major
> Labels: newbie
>
> _Current output_
> {code}
> GridDhtPartitionFullMap [nodeId=768c4f3b-95e3-411b-b341-e93129b0,
> nodeOrder=1, updateSeq=3, size=2,
> map={bb16a275-c308-477b-a13b-723f5421=GridDhtPartitionMap [moving=0,
> top=AffinityTopologyVersion [topVer=2, minorTopVer=1], updateSeq=2, size=100,
> map={0=OWNING, 1=OWNING, 2=OWNING, 3=OWNING, 4=OWNING, 5=OWNING, 6=OWNING,
> 7=OWNING, 8=OWNING, 9=OWNING, 10=OWNING, 11=OWNING, 12=OWNING, 13=OWNING,
> 14=OWNING, 15=OWNING, 16=OWNING, 17=OWNING, 18=OWNING, 19=OWNING, 20=OWNING,
> 21=OWNING, 22=OWNING, 23=OWNING, 24=OWNING, 25=OWNING, 26=OWNING, 27=OWNING,
> 28=OWNING, 29=OWNING, 30=OWNING, 31=OWNING, 32=OWNING, 33=OWNING, 34=OWNING,
> 35=OWNING, 36=OWNING, 37=OWNING, 38=OWNING, 39=OWNING, 40=OWNING, 41=OWNING,
> 42=OWNING, 43=OWNING, 44=OWNING, 45=OWNING, 46=OWNING, 47=OWNING, 48=OWNING,
> 49=OWNING, 50=OWNING, 51=OWNING, 52=OWNING, 53=OWNING, 54=OWNING, 55=OWNING,
> 56=OWNING, 57=OWNING, 58=OWNING, 59=OWNING, 60=OWNING, 61=OWNING, 62=OWNING,
> 63=OWNING, 64=OWNING, 65=OWNING, 66=OWNING, 67=OWNING, 68=OWNING, 69=OWNING,
> 70=OWNING, 71=OWNING, 72=OWNING, 73=OWNING, 74=OWNING, 75=OWNING, 76=OWNING,
> 77=OWNING, 78=OWNING, 79=OWNING, 80=OWNING, 81=OWNING, 82=OWNING, 83=OWNING,
> 84=OWNING, 85=OWNING, 86=OWNING, 87=OWNING, 88=OWNING, 89=OWNING, 90=OWNING,
> 91=OWNING, 92=OWNING, 93=OWNING, 94=OWNING, 95=OWNING, 96=OWNING, 97=OWNING,
> 98=OWNING, 99=OWNING}],
> {code}
> _Proposed output_
> {code}
> GridDhtPartitionFullMap [nodeId=768c4f3b-95e3-411b-b341-e93129b0,
> nodeOrder=1, updateSeq=3, size=2,
> map={bb16a275-c308-477b-a13b-723f5421=GridDhtPartitionMap [moving=0,
> top=AffinityTopologyVersion [topVer=2, minorTopVer=1], updateSeq=2, size=100,
> map={OWNING=0-100}],
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-15344) Reduce amount of output for printing node2part map
[
https://issues.apache.org/jira/browse/IGNITE-15344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17411935#comment-17411935
]
Maxim Muzafarov commented on IGNITE-15344:
--
[~Chandresh Pancholi] Hello, can you clarify your question, please?
This is an output for a map of maps.
the key - nodeId=768c4f3b-95e3-411b-b341-e93129b0
the value - map of partition id an its state, where the key - partition id,
value - partition state.
The inner map of partitions states can be grouped by not by partition id but by
partition state either, with using the
{{GridToStringBuilder#compact(java.util.Collection)}}
additional function over the set of partitions you can get a shorter string
output.
> Reduce amount of output for printing node2part map
> --
>
> Key: IGNITE-15344
> URL: https://issues.apache.org/jira/browse/IGNITE-15344
> Project: Ignite
> Issue Type: Task
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Major
> Labels: newbie
>
> _Current output_
> {code}
> GridDhtPartitionFullMap [nodeId=768c4f3b-95e3-411b-b341-e93129b0,
> nodeOrder=1, updateSeq=3, size=2,
> map={bb16a275-c308-477b-a13b-723f5421=GridDhtPartitionMap [moving=0,
> top=AffinityTopologyVersion [topVer=2, minorTopVer=1], updateSeq=2, size=100,
> map={0=OWNING, 1=OWNING, 2=OWNING, 3=OWNING, 4=OWNING, 5=OWNING, 6=OWNING,
> 7=OWNING, 8=OWNING, 9=OWNING, 10=OWNING, 11=OWNING, 12=OWNING, 13=OWNING,
> 14=OWNING, 15=OWNING, 16=OWNING, 17=OWNING, 18=OWNING, 19=OWNING, 20=OWNING,
> 21=OWNING, 22=OWNING, 23=OWNING, 24=OWNING, 25=OWNING, 26=OWNING, 27=OWNING,
> 28=OWNING, 29=OWNING, 30=OWNING, 31=OWNING, 32=OWNING, 33=OWNING, 34=OWNING,
> 35=OWNING, 36=OWNING, 37=OWNING, 38=OWNING, 39=OWNING, 40=OWNING, 41=OWNING,
> 42=OWNING, 43=OWNING, 44=OWNING, 45=OWNING, 46=OWNING, 47=OWNING, 48=OWNING,
> 49=OWNING, 50=OWNING, 51=OWNING, 52=OWNING, 53=OWNING, 54=OWNING, 55=OWNING,
> 56=OWNING, 57=OWNING, 58=OWNING, 59=OWNING, 60=OWNING, 61=OWNING, 62=OWNING,
> 63=OWNING, 64=OWNING, 65=OWNING, 66=OWNING, 67=OWNING, 68=OWNING, 69=OWNING,
> 70=OWNING, 71=OWNING, 72=OWNING, 73=OWNING, 74=OWNING, 75=OWNING, 76=OWNING,
> 77=OWNING, 78=OWNING, 79=OWNING, 80=OWNING, 81=OWNING, 82=OWNING, 83=OWNING,
> 84=OWNING, 85=OWNING, 86=OWNING, 87=OWNING, 88=OWNING, 89=OWNING, 90=OWNING,
> 91=OWNING, 92=OWNING, 93=OWNING, 94=OWNING, 95=OWNING, 96=OWNING, 97=OWNING,
> 98=OWNING, 99=OWNING}],
> {code}
> _Proposed output_
> {code}
> GridDhtPartitionFullMap [nodeId=768c4f3b-95e3-411b-b341-e93129b0,
> nodeOrder=1, updateSeq=3, size=2,
> map={bb16a275-c308-477b-a13b-723f5421=GridDhtPartitionMap [moving=0,
> top=AffinityTopologyVersion [topVer=2, minorTopVer=1], updateSeq=2, size=100,
> map={OWNING=0-100}],
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15457) Move thread pools metrics registration to pool processor.
[ https://issues.apache.org/jira/browse/IGNITE-15457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-15457: - Fix Version/s: 2.12 > Move thread pools metrics registration to pool processor. > - > > Key: IGNITE-15457 > URL: https://issues.apache.org/jira/browse/IGNITE-15457 > Project: Ignite > Issue Type: Improvement >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Minor > Fix For: 2.12 > > Time Spent: 20m > Remaining Estimate: 0h > > It is needed to move Ignite thread pool metrics registration to > PoolProcessor. It helps to encapsulate tread pools related logic in one place > and take the load off the IgniteKernal. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-15457) Move thread pools metrics registration to pool processor.
[ https://issues.apache.org/jira/browse/IGNITE-15457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17411946#comment-17411946 ] Mikhail Petrov commented on IGNITE-15457: - [~nizhikov], Thanks for the review. > Move thread pools metrics registration to pool processor. > - > > Key: IGNITE-15457 > URL: https://issues.apache.org/jira/browse/IGNITE-15457 > Project: Ignite > Issue Type: Improvement >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Minor > Fix For: 2.12 > > Time Spent: 20m > Remaining Estimate: 0h > > It is needed to move Ignite thread pool metrics registration to > PoolProcessor. It helps to encapsulate tread pools related logic in one place > and take the load off the IgniteKernal. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-15372) Remove companies logos from the homepage
[ https://issues.apache.org/jira/browse/IGNITE-15372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl reassigned IGNITE-15372: --- Assignee: Mauricio Stekl > Remove companies logos from the homepage > > > Key: IGNITE-15372 > URL: https://issues.apache.org/jira/browse/IGNITE-15372 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Critical > > We have to remove the logos of the companies that use Ignite from the > homepage (this rule doesn't apply to other pages). > WHY: the ASF is strictly vendor-neutral. Listing company names and/or logos > on a project's home page is disallowed as it can imply "ownership" or > preferred status or otherwise imbalanced relationship. Whether this is the > case or not, it is not acceptable. The policy is the same as "thanking" > companies for their support of a project > [http://apache.org/foundation/marks/linking#projectthanks] > As an alternative, we can create a "powered by" section similar to what the > Kafka community has: http://kafka.apache.org > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14596) Calcite engine. Support for function TYPEOF
[
https://issues.apache.org/jira/browse/IGNITE-14596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Plekhanov updated IGNITE-14596:
---
Labels: calcite3-required (was: calcite2-required calcite3-required)
> Calcite engine. Support for function TYPEOF
> ---
>
> Key: IGNITE-14596
> URL: https://issues.apache.org/jira/browse/IGNITE-14596
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Konstantin Orlov
>Assignee: Aleksey Plekhanov
>Priority: Minor
> Labels: calcite3-required
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently a function TYPEOF is not supported.
> Affected tests:
> {{src/test/sql/types/decimal/decimal_aggregates.test_ignored}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14596) Calcite engine. Support for function TYPEOF
[
https://issues.apache.org/jira/browse/IGNITE-14596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17411998#comment-17411998
]
Aleksey Plekhanov commented on IGNITE-14596:
[~tledkov-gridgain], thanks for the review! Merged to sql-calcite branch.
> Calcite engine. Support for function TYPEOF
> ---
>
> Key: IGNITE-14596
> URL: https://issues.apache.org/jira/browse/IGNITE-14596
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Konstantin Orlov
>Assignee: Aleksey Plekhanov
>Priority: Minor
> Labels: calcite2-required, calcite3-required
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently a function TYPEOF is not supported.
> Affected tests:
> {{src/test/sql/types/decimal/decimal_aggregates.test_ignored}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-14209) Data rebalancing
[ https://issues.apache.org/jira/browse/IGNITE-14209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin reassigned IGNITE-14209: Assignee: Kirill Gusakov (was: Vyacheslav Koptilin) > Data rebalancing > > > Key: IGNITE-14209 > URL: https://issues.apache.org/jira/browse/IGNITE-14209 > Project: Ignite > Issue Type: New Feature >Reporter: Vyacheslav Koptilin >Assignee: Kirill Gusakov >Priority: Major > Labels: ignite-3 > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14749) Calcite engine. Create table and use of this table in one statement doesn't work
[
https://issues.apache.org/jira/browse/IGNITE-14749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yury Gerzhedovich updated IGNITE-14749:
---
Labels: calcite3-required (was: calcite2-required calcite3-required)
> Calcite engine. Create table and use of this table in one statement doesn't
> work
>
>
> Key: IGNITE-14749
> URL: https://issues.apache.org/jira/browse/IGNITE-14749
> Project: Ignite
> Issue Type: Bug
>Reporter: Aleksey Plekhanov
>Assignee: Ivan Daschinsky
>Priority: Major
> Labels: calcite3-required
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
>
> If a statement consists of substatements and a table is created in one of
> these substatement and then used by another, preparation of this statement
> failed. For example:
> {code:java}
> executeSql("CREATE TABLE test (val int); INSERT INTO test VALUES (0);");
> {code}
> Failed with:
>
> {noformat}
> Caused by: org.apache.calcite.tools.ValidationException:
> org.apache.calcite.runtime.CalciteContextException: From line 1, column 42 to
> line 1, column 45: Object 'TEST' not found
> at
> org.apache.ignite.internal.processors.query.calcite.prepare.IgnitePlanner.validate(IgnitePlanner.java:180)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.prepareDml(ExecutionServiceImpl.java:597)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.prepareSingle(ExecutionServiceImpl.java:561)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.prepareQuery(ExecutionServiceImpl.java:520)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15479) Sometimes not all response read from socket in python sync client
[ https://issues.apache.org/jira/browse/IGNITE-15479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Daschinsky updated IGNITE-15479: - Attachment: dt_bug.py > Sometimes not all response read from socket in python sync client > - > > Key: IGNITE-15479 > URL: https://issues.apache.org/jira/browse/IGNITE-15479 > Project: Ignite > Issue Type: Bug > Components: python, thin client >Affects Versions: python-0.4.0, python-0.5.0, python-0.5.1 >Reporter: Ivan Daschinsky >Assignee: Ivan Daschinsky >Priority: Major > Attachments: dt_bug.py > > > Sometimes not all data received from socket in response, reading stopped too > early. > Reproducer is attached -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15479) Sometimes not all response read from socket in python sync client
[ https://issues.apache.org/jira/browse/IGNITE-15479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Daschinsky updated IGNITE-15479: - Description: Sometimes not all data received from socket in response, reading stopped too early. Reproducer is attached > Sometimes not all response read from socket in python sync client > - > > Key: IGNITE-15479 > URL: https://issues.apache.org/jira/browse/IGNITE-15479 > Project: Ignite > Issue Type: Bug > Components: python, thin client >Affects Versions: python-0.4.0, python-0.5.0, python-0.5.1 >Reporter: Ivan Daschinsky >Assignee: Ivan Daschinsky >Priority: Major > Attachments: dt_bug.py > > > Sometimes not all data received from socket in response, reading stopped too > early. > Reproducer is attached -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-15479) Sometimes not all response read from socket in python sync client
Ivan Daschinsky created IGNITE-15479: Summary: Sometimes not all response read from socket in python sync client Key: IGNITE-15479 URL: https://issues.apache.org/jira/browse/IGNITE-15479 Project: Ignite Issue Type: Bug Components: python, thin client Affects Versions: python-0.4.0, python-0.5.0, python-0.5.1 Reporter: Ivan Daschinsky Assignee: Ivan Daschinsky Attachments: dt_bug.py -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15479) Sometimes not all response read from socket in python sync client
[ https://issues.apache.org/jira/browse/IGNITE-15479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Daschinsky updated IGNITE-15479: - Attachment: docker-compose.yml > Sometimes not all response read from socket in python sync client > - > > Key: IGNITE-15479 > URL: https://issues.apache.org/jira/browse/IGNITE-15479 > Project: Ignite > Issue Type: Bug > Components: python, thin client >Affects Versions: python-0.4.0, python-0.5.0, python-0.5.1 >Reporter: Ivan Daschinsky >Assignee: Ivan Daschinsky >Priority: Major > Attachments: docker-compose.yml, dt_bug.py > > > Sometimes not all data received from socket in response, reading stopped too > early. > Reproducer is attached -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13980) Remove duplicated ping: processing and raising StatusCheckMessage.
[
https://issues.apache.org/jira/browse/IGNITE-13980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17412068#comment-17412068
]
Ignite TC Bot commented on IGNITE-13980:
{panel:title=Branch: [pull/8696/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8696/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6170374&buildTypeId=IgniteTests24Java8_RunAll]
> Remove duplicated ping: processing and raising StatusCheckMessage.
> --
>
> Key: IGNITE-13980
> URL: https://issues.apache.org/jira/browse/IGNITE-13980
> Project: Ignite
> Issue Type: Improvement
>Reporter: Vladimir Steshin
>Assignee: Vladimir Steshin
>Priority: Minor
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> Suggestion: remove duplicated ‘ping’, make the code simpler.
> To ensure some node isn't failed TcpDiscoverySpi has robust ping
> (TcpDiscoveryConnectionCheckMessage) and the backward connection check. But
> there is also status check message (TcpDiscoveryStatusCheckMessage) which
> looks outdated. This message was introduced with first versions of the
> discovery when the cluster stability and message delivery were under
> developing.
> Currently, TcpDiscoveryStatusCheckMessage is actually launched only at
> cluster start sometimes. And doesn't happen later due to the ping. The ping
> updates time of the message received which is the reason not to raise the
> status check.
> It is possible that node loses all incoming connection but keeps connection
> to next node. In this case the node gets removed from the ring by its
> follower. But cannot recognize the failure because it still successfully send
> message to next node. Instead of complex processing of
> TcpDiscoveryStatusCheckMessage, it iseems enough to answer on message 'OK,
> but you are not in the ring'. Every other node sees failure of malfunction
> node and can notify about it in the message response.
> The ticket has been additionally verified with the integration discovery
> test: https://github.com/apache/ignite/pull/8716
> We can keep TcpDiscoveryStatusCheckMessage for backward compatibility with
> older versions of Ignite. The subtask (IGNITE-14053) suggests complete
> removal of TcpDiscoveryStatusCheckMessage.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-15480) Refactor index column mapping
Alexander Lapin created IGNITE-15480: Summary: Refactor index column mapping Key: IGNITE-15480 URL: https://issues.apache.org/jira/browse/IGNITE-15480 Project: Ignite Issue Type: Improvement Reporter: Alexander Lapin -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-15015) CPP: Add support for affinity field in binary objects
[
https://issues.apache.org/jira/browse/IGNITE-15015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17412097#comment-17412097
]
Ignite TC Bot commented on IGNITE-15015:
{panel:title=Branch: [pull/9370/head] Base: [master] : Possible Blockers
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}[Check Code Style]{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6170717]]
{panel}
{panel:title=Branch: [pull/9370/head] Base: [master] : New Tests
(2048)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Platform C++ CMake (Win x64 / Debug){color} [[tests
1022|https://ci.ignite.apache.org/viewLog.html?buildId=6170720]]
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite: SelectTwoValues
- PASSED{color}
* {color:#013220}IgniteOdbcTest: SqlNumericFunctionTestSuite:
TestNumericFunctionFloor - PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite:
SelectSingleValue - PASSED{color}
* {color:#013220}IgniteOdbcTest: SqlNumericFunctionTestSuite:
TestNumericFunctionLog - PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite:
CreateTableInsertSelect - PASSED{color}
* {color:#013220}IgniteOdbcTest: SqlDateTimeFunctionTestSuite: TestCurrentDate
- PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite:
SelectTwoValuesInDifferentOrder - PASSED{color}
* {color:#013220}IgniteCoreTest: ClusterTestSuite: IgniteForCacheNodes -
PASSED{color}
* {color:#013220}IgniteCoreTest: ClusterTestSuite: IgniteForClientNodes -
PASSED{color}
* {color:#013220}IgniteCoreTest: CacheQueryTestSuite:
TestFieldsQueryByteArrayInsertSelect - PASSED{color}
* {color:#013220}IgniteCoreTest: ClusterTestSuite: IgniteForDaemons -
PASSED{color}
... and 1011 new tests
{color:#8b}Platform C++ (Win x64 / Debug){color} [[tests
1010|https://ci.ignite.apache.org/viewLog.html?buildId=6170713]]
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite: SelectTwoValues
- PASSED{color}
* {color:#013220}IgniteOdbcTest: SqlNumericFunctionTestSuite:
TestNumericFunctionFloor - PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite:
SelectSingleValue - PASSED{color}
* {color:#013220}IgniteOdbcTest: SqlNumericFunctionTestSuite:
TestNumericFunctionLog - PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite:
CreateTableInsertSelect - PASSED{color}
* {color:#013220}IgniteOdbcTest: SqlDateTimeFunctionTestSuite: TestCurrentDate
- PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite:
SelectTwoValuesInDifferentOrder - PASSED{color}
* {color:#013220}IgniteCoreTest: ClusterTestSuite: IgniteForCacheNodes -
PASSED{color}
* {color:#013220}IgniteCoreTest: CacheQueryTestSuite:
TestFieldsQueryByteArrayInsertSelect - PASSED{color}
* {color:#013220}IgniteCoreTest: ClusterTestSuite: IgniteForClientNodes -
PASSED{color}
* {color:#013220}IgniteCoreTest: ClusterTestSuite: IgniteForDaemons -
PASSED{color}
... and 999 new tests
{color:#8b}Platform C++ CMake (Win x64 / Release){color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=6170721]]
* {color:#013220}IgniteCoreTest: InteropTestSuite: PutObjectByCppThenByJava -
PASSED{color}
* {color:#013220}IgniteThinClientTest: InteropTestSuite:
PutObjectPointerByCppThenByJava - PASSED{color}
* {color:#013220}IgniteThinClientTest: InteropTestSuite:
PutObjectByCppThenByJava - PASSED{color}
* {color:#013220}IgniteCoreTest: InteropTestSuite:
PutObjectPointerByCppThenByJava - PASSED{color}
{color:#8b}Platform C++ (Win x64 / Release){color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=6170714]]
* {color:#013220}IgniteCoreTest: InteropTestSuite: PutObjectByCppThenByJava -
PASSED{color}
* {color:#013220}IgniteThinClientTest: InteropTestSuite:
PutObjectPointerByCppThenByJava - PASSED{color}
* {color:#013220}IgniteThinClientTest: InteropTestSuite:
PutObjectByCppThenByJava - PASSED{color}
* {color:#013220}IgniteCoreTest: InteropTestSuite:
PutObjectPointerByCppThenByJava - PASSED{color}
{color:#8b}Platform C++ CMake (Linux){color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=6170719]]
* {color:#013220}IgniteCoreTest: InteropTestSuite: PutObjectByCppThenByJava -
PASSED{color}
* {color:#013220}IgniteThinClientTest: InteropTestSuite:
PutObjectPointerByCppThenByJava - PASSED{color}
* {color:#013220}IgniteThinClientTest: InteropTestSuite:
PutObjectByCppThenByJava - PASSED{color}
* {color:#013220}IgniteCoreTest: InteropTestSuite:
PutObjectPointerByCppThenByJava - PASSED{color}
{color:#8b}Platform C++ CMake (Linux Clang){color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=6170718]]
* {color:#013220}IgniteCoreTest: InteropTestSuite: PutObjectByCppThenByJava -
PASSED{color}
* {color:#013220}IgniteThinClientTest: InteropTestSuite:
PutObjec
[jira] [Commented] (IGNITE-12779) Split implementations of Ignite and IgniteMXBean, make behavior of their active(boolean) different
[
https://issues.apache.org/jira/browse/IGNITE-12779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17412106#comment-17412106
]
Ignite TC Bot commented on IGNITE-12779:
{panel:title=Branch: [pull/7531/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/7531/head] Base: [master] : New Tests
(3)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}PDS 4{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6162382]]
* {color:#013220}IgnitePdsTestSuite4:
IgniteClusterActivateDeactivateTestWithPersistenceAndMemoryReuse.testDeactivateMXBean
- PASSED{color}
{color:#8b}PDS 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6162379]]
* {color:#013220}IgnitePdsTestSuite:
IgniteClusterActivateDeactivateTestWithPersistence.testDeactivateMXBean -
PASSED{color}
{color:#8b}Activate / Deactivate Cluster{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6162313]]
* {color:#013220}IgniteStandByClusterSuite:
IgniteClusterActivateDeactivateTest.testDeactivateMXBean - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6170476&buildTypeId=IgniteTests24Java8_RunAll]
> Split implementations of Ignite and IgniteMXBean, make behavior of their
> active(boolean) different
> ---
>
> Key: IGNITE-12779
> URL: https://issues.apache.org/jira/browse/IGNITE-12779
> Project: Ignite
> Issue Type: Sub-task
>Affects Versions: 2.8
>Reporter: Vladimir Steshin
>Assignee: Vladimir Steshin
>Priority: Major
> Fix For: 2.12
>
> Time Spent: 3h 20m
> Remaining Estimate: 0h
>
> To make cluster deactivation through JMX without sudden erasure of in-memory
> data we should:
> 1) Set IgniteMXBean.active(false) and IgniteMXBean.state("inactive") throwing
> an exception if deactivation would clear in-memory data.
> 2) Extract IgniteMXBean from IgniteKernal.
> 3) Add IgniteMXBean.state(String, boolean)
> Additionally, as discussed, we should improve comments
> {code:java}
> /** If {@code true}, cluster deactivation will be forced. */
> {code}
> Let's add a link to a full description.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-15382) Decouple API and implementation for Tuple and Schema.
[ https://issues.apache.org/jira/browse/IGNITE-15382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17412135#comment-17412135 ] Yury Gerzhedovich commented on IGNITE-15382: [~agura] could you please review the patch > Decouple API and implementation for Tuple and Schema. > - > > Key: IGNITE-15382 > URL: https://issues.apache.org/jira/browse/IGNITE-15382 > Project: Ignite > Issue Type: Improvement >Reporter: Andrey Mashenkov >Assignee: Andrey Mashenkov >Priority: Major > Labels: UX, ignite-3 > Fix For: 3.0.0-alpha3 > > Time Spent: 10m > Remaining Estimate: 0h > > For now, TupleImpl is a part of public API, but should be internal class. > SchemaBuilders, on the opposite, relates to a public API, but is hidden in > schema-module. > With Jigsaw it is impossible to have packages of the same name in different > modules. > Let's > # Move TupleImpl to an internal package of the ignite-table module. > # Move SchemaBuilders to the public package of the ignite-api module. > # Use a ServiceLoader for factories for these classes in ignite-api module -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-15470) Java thin client: Use partition awareness for ScanQuery with specified partition
[ https://issues.apache.org/jira/browse/IGNITE-15470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17412175#comment-17412175 ] Amelchev Nikita commented on IGNITE-15470: -- [~alex_pl], LGTM. > Java thin client: Use partition awareness for ScanQuery with specified > partition > > > Key: IGNITE-15470 > URL: https://issues.apache.org/jira/browse/IGNITE-15470 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksey Plekhanov >Assignee: Aleksey Plekhanov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Currently, partition awareness is used by java thin client only for > single-key operations. > For scan queries we can also use the benefits of partition awareness if > partition for the query is specified explicitly. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-15344) Reduce amount of output for printing node2part map
[
https://issues.apache.org/jira/browse/IGNITE-15344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chandresh Pancholi reassigned IGNITE-15344:
---
Assignee: Chandresh Pancholi
> Reduce amount of output for printing node2part map
> --
>
> Key: IGNITE-15344
> URL: https://issues.apache.org/jira/browse/IGNITE-15344
> Project: Ignite
> Issue Type: Task
>Reporter: Maxim Muzafarov
>Assignee: Chandresh Pancholi
>Priority: Major
> Labels: newbie
>
> _Current output_
> {code}
> GridDhtPartitionFullMap [nodeId=768c4f3b-95e3-411b-b341-e93129b0,
> nodeOrder=1, updateSeq=3, size=2,
> map={bb16a275-c308-477b-a13b-723f5421=GridDhtPartitionMap [moving=0,
> top=AffinityTopologyVersion [topVer=2, minorTopVer=1], updateSeq=2, size=100,
> map={0=OWNING, 1=OWNING, 2=OWNING, 3=OWNING, 4=OWNING, 5=OWNING, 6=OWNING,
> 7=OWNING, 8=OWNING, 9=OWNING, 10=OWNING, 11=OWNING, 12=OWNING, 13=OWNING,
> 14=OWNING, 15=OWNING, 16=OWNING, 17=OWNING, 18=OWNING, 19=OWNING, 20=OWNING,
> 21=OWNING, 22=OWNING, 23=OWNING, 24=OWNING, 25=OWNING, 26=OWNING, 27=OWNING,
> 28=OWNING, 29=OWNING, 30=OWNING, 31=OWNING, 32=OWNING, 33=OWNING, 34=OWNING,
> 35=OWNING, 36=OWNING, 37=OWNING, 38=OWNING, 39=OWNING, 40=OWNING, 41=OWNING,
> 42=OWNING, 43=OWNING, 44=OWNING, 45=OWNING, 46=OWNING, 47=OWNING, 48=OWNING,
> 49=OWNING, 50=OWNING, 51=OWNING, 52=OWNING, 53=OWNING, 54=OWNING, 55=OWNING,
> 56=OWNING, 57=OWNING, 58=OWNING, 59=OWNING, 60=OWNING, 61=OWNING, 62=OWNING,
> 63=OWNING, 64=OWNING, 65=OWNING, 66=OWNING, 67=OWNING, 68=OWNING, 69=OWNING,
> 70=OWNING, 71=OWNING, 72=OWNING, 73=OWNING, 74=OWNING, 75=OWNING, 76=OWNING,
> 77=OWNING, 78=OWNING, 79=OWNING, 80=OWNING, 81=OWNING, 82=OWNING, 83=OWNING,
> 84=OWNING, 85=OWNING, 86=OWNING, 87=OWNING, 88=OWNING, 89=OWNING, 90=OWNING,
> 91=OWNING, 92=OWNING, 93=OWNING, 94=OWNING, 95=OWNING, 96=OWNING, 97=OWNING,
> 98=OWNING, 99=OWNING}],
> {code}
> _Proposed output_
> {code}
> GridDhtPartitionFullMap [nodeId=768c4f3b-95e3-411b-b341-e93129b0,
> nodeOrder=1, updateSeq=3, size=2,
> map={bb16a275-c308-477b-a13b-723f5421=GridDhtPartitionMap [moving=0,
> top=AffinityTopologyVersion [topVer=2, minorTopVer=1], updateSeq=2, size=100,
> map={OWNING=0-100}],
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12464) Service metrics
[
https://issues.apache.org/jira/browse/IGNITE-12464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17412236#comment-17412236
]
Ignite TC Bot commented on IGNITE-12464:
{panel:title=Branch: [pull/7622/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/7622/head] Base: [master] : New Tests
(18)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Service Grid (legacy mode){color} [[tests
9|https://ci.ignite.apache.org/viewLog.html?buildId=6162292]]
* {color:#013220}IgniteServiceGridTestSuite:
GridServiceMetricsTest.testMetricNaming - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
GridServiceMetricsTest.testMultipleDeployment - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
GridServiceMetricsTest.testServiceMetricsMultyFew - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
GridServiceMetricsTest.testServiceMetricsSingle - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
GridServiceMetricsTest.testServiceMetricsMulty - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
GridServiceMetricsTest.testServiceMetricsMultyDuplicated - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
GridServiceMetricsTest.testServiceMetricsMultyFewDuplicated - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
GridServiceMetricsTest.testMetricDeplotmentUndeployment - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
GridServiceMetricsTest.testServiceMetricsEnabledDisabled - PASSED{color}
{color:#8b}Service Grid{color} [[tests
9|https://ci.ignite.apache.org/viewLog.html?buildId=6162291]]
* {color:#013220}IgniteServiceGridTestSuite:
GridServiceMetricsTest.testMetricNaming - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
GridServiceMetricsTest.testMultipleDeployment - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
GridServiceMetricsTest.testServiceMetricsMultyFew - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
GridServiceMetricsTest.testServiceMetricsSingle - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
GridServiceMetricsTest.testServiceMetricsMulty - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
GridServiceMetricsTest.testServiceMetricsMultyDuplicated - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
GridServiceMetricsTest.testServiceMetricsMultyFewDuplicated - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
GridServiceMetricsTest.testMetricDeplotmentUndeployment - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
GridServiceMetricsTest.testServiceMetricsEnabledDisabled - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6162307&buildTypeId=IgniteTests24Java8_RunAll]
> Service metrics
> ---
>
> Key: IGNITE-12464
> URL: https://issues.apache.org/jira/browse/IGNITE-12464
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.8
>Reporter: Nikolay Izhikov
>Assignee: Vladimir Steshin
>Priority: Minor
> Labels: IEP-35
> Time Spent: 20.5h
> Remaining Estimate: 0h
>
> We should provide the following metrics for each deployed service:
> * -Count of executions- - this number seems useless, because, we can compute
> it just by summing all histograms values.
> * Histogram of executions duration
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-15107) Integrate DDL handler into Ignite 3.0
[
https://issues.apache.org/jira/browse/IGNITE-15107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17412341#comment-17412341
]
Evgeny Stanilovsky commented on IGNITE-15107:
-
[~amashenkov] my fault, now seems all ok. There are some api restrictions (we
are talking about) possibly we can merge it as is (if all other ok).
[~korlov] thanks for review, any additional suggestions?
> Integrate DDL handler into Ignite 3.0
> -
>
> Key: IGNITE-15107
> URL: https://issues.apache.org/jira/browse/IGNITE-15107
> Project: Ignite
> Issue Type: Sub-task
> Components: sql
>Reporter: Konstantin Orlov
>Assignee: Evgeny Stanilovsky
>Priority: Major
> Time Spent: 2h 40m
> Remaining Estimate: 0h
>
> Need to implement handler of the following basic commands:
> * Create table
> * Alter table
> * Drop table
> * Create index
> * Drop index
> Reference point is
> {{org.apache.ignite.internal.processors.query.calcite.exec.ddl.DdlCommandHandler}}.
> Required tests are available in following classes:
> {{org.apache.ignite.internal.processors.query.calcite.integration.IndexDdlIntegrationTest}}
> {{org.apache.ignite.internal.processors.query.calcite.integration.TableDdlIntegrationTest}}
> NB: all referenced classes are resided in ignite-2 codebase in
> {{sql-calcite}} branch.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-15470) Java thin client: Use partition awareness for ScanQuery with specified partition
[ https://issues.apache.org/jira/browse/IGNITE-15470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17412354#comment-17412354 ] Aleksey Plekhanov commented on IGNITE-15470: [~NSAmelchev] thanks for the review! Merged to master > Java thin client: Use partition awareness for ScanQuery with specified > partition > > > Key: IGNITE-15470 > URL: https://issues.apache.org/jira/browse/IGNITE-15470 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksey Plekhanov >Assignee: Aleksey Plekhanov >Priority: Major > Fix For: 2.12 > > Time Spent: 20m > Remaining Estimate: 0h > > Currently, partition awareness is used by java thin client only for > single-key operations. > For scan queries we can also use the benefits of partition awareness if > partition for the query is specified explicitly. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15470) Java thin client: Use partition awareness for ScanQuery with specified partition
[ https://issues.apache.org/jira/browse/IGNITE-15470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Plekhanov updated IGNITE-15470: --- Fix Version/s: 2.12 > Java thin client: Use partition awareness for ScanQuery with specified > partition > > > Key: IGNITE-15470 > URL: https://issues.apache.org/jira/browse/IGNITE-15470 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksey Plekhanov >Assignee: Aleksey Plekhanov >Priority: Major > Fix For: 2.12 > > Time Spent: 20m > Remaining Estimate: 0h > > Currently, partition awareness is used by java thin client only for > single-key operations. > For scan queries we can also use the benefits of partition awareness if > partition for the query is specified explicitly. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-15469) Update Ignite dependency: MySQL Connector
[
https://issues.apache.org/jira/browse/IGNITE-15469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17412382#comment-17412382
]
Ignite TC Bot commented on IGNITE-15469:
{panel:title=Branch: [pull/9385/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9385/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6170582&buildTypeId=IgniteTests24Java8_RunAll]
> Update Ignite dependency: MySQL Connector
> --
>
> Key: IGNITE-15469
> URL: https://issues.apache.org/jira/browse/IGNITE-15469
> Project: Ignite
> Issue Type: Improvement
>Reporter: Aleksandr
>Assignee: Aleksandr
>Priority: Major
> Labels: newbie
> Fix For: 2.12
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Update Ignite dependency: MySQL Connector 8.0.13 to 8.0.26
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-15469) Update Ignite dependency: MySQL Connector
[ https://issues.apache.org/jira/browse/IGNITE-15469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17412388#comment-17412388 ] Aleksandr commented on IGNITE-15469: [~amashenkov] Hi, in my opinion, the ticket and PR now look correct, I do not know whose PR#9388 but now it duplicates my PR#9385 > Update Ignite dependency: MySQL Connector > -- > > Key: IGNITE-15469 > URL: https://issues.apache.org/jira/browse/IGNITE-15469 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr >Assignee: Aleksandr >Priority: Major > Labels: newbie > Fix For: 2.12 > > Time Spent: 40m > Remaining Estimate: 0h > > Update Ignite dependency: MySQL Connector 8.0.13 to 8.0.26 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-15469) Update Ignite dependency: MySQL Connector
[ https://issues.apache.org/jira/browse/IGNITE-15469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17412388#comment-17412388 ] Aleksandr edited comment on IGNITE-15469 at 9/9/21, 6:52 AM: - [~amashenkov] Hi, in my opinion, the ticket and PR now look correct, I do not know whose PR#9388 but now it duplicates my PR#9385. I do not know how correct it will be if I just delete someone else's PR from my ticket was (Author: aonikolaev): [~amashenkov] Hi, in my opinion, the ticket and PR now look correct, I do not know whose PR#9388 but now it duplicates my PR#9385 > Update Ignite dependency: MySQL Connector > -- > > Key: IGNITE-15469 > URL: https://issues.apache.org/jira/browse/IGNITE-15469 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr >Assignee: Aleksandr >Priority: Major > Labels: newbie > Fix For: 2.12 > > Time Spent: 40m > Remaining Estimate: 0h > > Update Ignite dependency: MySQL Connector 8.0.13 to 8.0.26 -- This message was sent by Atlassian Jira (v8.3.4#803005)
