[jira] [Commented] (IGNITE-13558) GridCacheProcessor should implement better parallelization when restoring partition states on startup
[ https://issues.apache.org/jira/browse/IGNITE-13558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17397096#comment-17397096 ] Kirill Tkalenko commented on IGNITE-13558: -- [~Denis Chudov] Put new comments in the PR, please comment on the proposals above. > GridCacheProcessor should implement better parallelization when restoring > partition states on startup > - > > Key: IGNITE-13558 > URL: https://issues.apache.org/jira/browse/IGNITE-13558 > Project: Ignite > Issue Type: Improvement > Components: persistence >Reporter: Sergey Chugunov >Assignee: Denis Chudov >Priority: Major > Time Spent: 2h 20m > Remaining Estimate: 0h > > GridCacheProcessor#restorePartitionStates method tries to employ striped pool > to restore partition states in parallel but level of parallelization is down > only to cache group per thread. > It is not enough and not utilizes resources effectively in case of one cache > group much bigger than the others. > We need to parallel restore process down to individual partitions to get the > most from the available resources and speed up node startup. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-15267) A lot of spam in logs on thick client: "Unable to save statistics obsolescence info on non server node."
[ https://issues.apache.org/jira/browse/IGNITE-15267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17397058#comment-17397058 ] Alexander Belyak commented on IGNITE-15267: --- Have changes in the same classes and some test from 15281 lead to changes in 15267. So branch 15267 was started from 15281's branch. > A lot of spam in logs on thick client: "Unable to save statistics > obsolescence info on non server node." > > > Key: IGNITE-15267 > URL: https://issues.apache.org/jira/browse/IGNITE-15267 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 2.10 >Reporter: Ilya Kazakov >Assignee: Alexander Belyak >Priority: Major > > In logs on thick client there are a lot of such messages: > 2021-08-05 18:28:26,870 17371453 INFO > [grid-timeout-worker-#22%member-checkin-data-s] java.JavaLogger ( > JavaLogger.java: 284) - Unable to save statistics obsolescence info on non > server node. > It looks like unexpected calls to save stat on thick client. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13441) Cache (Restarts) 1 failed with Execution timeout
[ https://issues.apache.org/jira/browse/IGNITE-13441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17396915#comment-17396915 ] Alexey Scherbakov commented on IGNITE-13441: [~mmuzaf] Why we should revert the commit ? It fixes a lot of bugs. But not all of them. > Cache (Restarts) 1 failed with Execution timeout > > > Key: IGNITE-13441 > URL: https://issues.apache.org/jira/browse/IGNITE-13441 > Project: Ignite > Issue Type: Task >Reporter: Nikita Tolstunov >Assignee: Alexey Scherbakov >Priority: Major > Attachments: > Ignite_Tests_2.4_Java_8_9_10_11_Cache_Restarts_1_22724.log.zip > > Time Spent: 20m > Remaining Estimate: 0h > > Suite [Cache(Restarts) > 1|https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_CacheRestarts1?branch=%3Cdefault%3E&mode=builds] > regularly fails with execution timeout. > I found that in some cases > IgniteCacheNearRestartRollbackSelfTest#testRestarts caused it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-15283) Remove duplicated managing of CacheDataStore in offheap manager
Maxim Muzafarov created IGNITE-15283:
Summary: Remove duplicated managing of CacheDataStore in offheap
manager
Key: IGNITE-15283
URL: https://issues.apache.org/jira/browse/IGNITE-15283
Project: Ignite
Issue Type: Task
Reporter: Maxim Muzafarov
Assignee: Maxim Muzafarov
Fix For: 2.12
The cache group patition topology provides the same view on created cache data
stores. , so managing of data stores in the offeap manager can be omitted.
{code}
protected final ConcurrentMap partDataStores = new
ConcurrentHashMap<>();
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-10999) NOT NULL sql constraint is not checked for data streamer operations
[
https://issues.apache.org/jira/browse/IGNITE-10999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17396890#comment-17396890
]
Maksim Timonin commented on IGNITE-10999:
-
Also broken QuerySqlField.precision param.
> NOT NULL sql constraint is not checked for data streamer operations
> ---
>
> Key: IGNITE-10999
> URL: https://issues.apache.org/jira/browse/IGNITE-10999
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.7
>Reporter: Ivan Pavlukhin
>Priority: Major
> Labels: newbie
> Attachments: SqlNotNullDataStreamer.java
>
>
> It is possible to violate NOT NULL constraint when using
> {{IgniteDataStreamer}}. See attached reproducer.
> Attention should be paid to various SQL commands using data streamer
> internally. Among them:
> 1. {{COPY}} command.
> 2. Operations executed with {{SET STREAMING ON}} mode.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-15256) ClassNotFoundException on attempt to invoke service method from Java ThinClient after cluster failover
[
https://issues.apache.org/jira/browse/IGNITE-15256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17396885#comment-17396885
]
Ignite TC Bot commented on IGNITE-15256:
{panel:title=Branch: [pull/9307/head] Base: [master] : Possible Blockers
(98)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Control Utility (Zookeeper){color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6124885]]
{color:#d04437}Platform .NET (Core Linux){color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6124867]]
{color:#d04437}Cache (Restarts) 1{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6124844]]
{color:#d04437}Cache 7{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6124853]]
{color:#d04437}SPI{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6124821]]
{color:#d04437}Scala (Examples){color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6124826]]
{color:#d04437}Cache 2{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6124848]]
{color:#d04437}RDD{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6124816]]
{color:#d04437}Examples{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6124803]]
{color:#d04437}Cache 6{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6124852]]
{color:#d04437}Basic 1{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6124831]]
{color:#d04437}ZooKeeper (Discovery) 1{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6124828]]
{color:#d04437}Platform .NET{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6124866]]
{color:#d04437}Cache 9{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6124855]]
{color:#d04437}Thin client: Node.js{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6124887]]
{color:#d04437}Continuous Query 4{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6124857]]
{color:#d04437}Cache (Failover) 2{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6124840]]
{color:#d04437}Platform .NET (Long Running){color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6124869]]
{color:#d04437}Java Client{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6124810]]
{color:#d04437}PDS 4{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6124865]]
{color:#d04437}Control Utility{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6124884]]
{color:#d04437}Cache 8{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6124854]]
{color:#d04437}Queries 2{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6124817]]
{color:#d04437}Binary Objects{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6124795]]
{color:#d04437}PDS 2{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6124863]]
{color:#d04437}Cache 5{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6124851]]
{color:#d04437}JDBC Driver{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6124814]]
{color:#d04437}PDS (Indexing){color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6124860]]
{color:#d04437}Thin client: Python{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6124889]]
{color:#d04437}ZooKeeper (Discovery) 3{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6124872]]
{color:#d04437}Cache (Failover) 1{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6124839]]
{color:#d04437}Queries 1{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6124871]]
{color:#d04437}Continuous Query 3{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6124856]]
{color:#d04437}Thin client: PHP{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6124888]]
{color:#d04437}Cache 1{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6124847]]
{color:#d04437}Security{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6124879]]
{color:#d04437}PDS (Compatibility)*{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6124859]]
{color:#d04437}Start Nodes{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6124820]]
{color:#d04437}ZooKeeper (Discovery) 4{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html
[jira] [Created] (IGNITE-15282) Remove unused private method GridDhtLocalPartition#clear
Maxim Muzafarov created IGNITE-15282:
Summary: Remove unused private method GridDhtLocalPartition#clear
Key: IGNITE-15282
URL: https://issues.apache.org/jira/browse/IGNITE-15282
Project: Ignite
Issue Type: Task
Reporter: Maxim Muzafarov
Assignee: Maxim Muzafarov
Fix For: 2.12
The *private* method {{GridDhtLocalPartition#clear}} is unused. Currently, the
{{clearAll}} medhod is used for partition clearing process.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13441) Cache (Restarts) 1 failed with Execution timeout
[ https://issues.apache.org/jira/browse/IGNITE-13441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17396842#comment-17396842 ] Maxim Muzafarov commented on IGNITE-13441: -- Folks, Commit still in the master branch, should we revert it and rework? > Cache (Restarts) 1 failed with Execution timeout > > > Key: IGNITE-13441 > URL: https://issues.apache.org/jira/browse/IGNITE-13441 > Project: Ignite > Issue Type: Task >Reporter: Nikita Tolstunov >Assignee: Alexey Scherbakov >Priority: Major > Attachments: > Ignite_Tests_2.4_Java_8_9_10_11_Cache_Restarts_1_22724.log.zip > > Time Spent: 20m > Remaining Estimate: 0h > > Suite [Cache(Restarts) > 1|https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_CacheRestarts1?branch=%3Cdefault%3E&mode=builds] > regularly fails with execution timeout. > I found that in some cases > IgniteCacheNearRestartRollbackSelfTest#testRestarts caused it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-15281) DistributedMetaStoragePersistentTest.testDeactivateActivate is flaky in master
Alexander Belyak created IGNITE-15281: - Summary: DistributedMetaStoragePersistentTest.testDeactivateActivate is flaky in master Key: IGNITE-15281 URL: https://issues.apache.org/jira/browse/IGNITE-15281 Project: Ignite Issue Type: Bug Components: sql Reporter: Alexander Belyak Assignee: Alexander Belyak Flacky test https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_ZooKeeperDiscovery4/6121759?showLog=6121759_110043_1600.110028.110043.111054.111871 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-15208) Remove unnecessary rebalance order classes for exchange thread
[
https://issues.apache.org/jira/browse/IGNITE-15208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17396711#comment-17396711
]
Pavel Tupitsyn commented on IGNITE-15208:
-
[~mmuzaf] thanks!
> Remove unnecessary rebalance order classes for exchange thread
> --
>
> Key: IGNITE-15208
> URL: https://issues.apache.org/jira/browse/IGNITE-15208
> Project: Ignite
> Issue Type: Task
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Major
> Fix For: 2.12
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> Some pieces of code related to the ordering of cache groups for the rebalance
> procedure can be removed. These parts of the code have been written to
> support Ignite under java 7 and no more actual.
> E.g.
> {code}
> for (Map.Entry e :
> assignsMap.entrySet()) {
> int grpId = e.getKey();
> CacheGroupContext grp = cctx.cache().cacheGroup(grpId);
> CacheRebalanceOrder order = new CacheRebalanceOrder(
> grp.config().getRebalanceOrder(),
> grp.config().getRebalanceMode());
> if (orderMap.get(order) == null)
> orderMap.put(order, new ArrayList(size));
> orderMap.get(order).add(grpId);
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-15271) ITNodeTest.testFollowerStartStopFollowing is still flaky
[
https://issues.apache.org/jira/browse/IGNITE-15271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17396704#comment-17396704
]
Alexey Scherbakov edited comment on IGNITE-15271 at 8/10/21, 2:14 PM:
--
The reason of test failure is a possible race between requestvote message and
appendentires message.
If a latter comes first from the elected leader it forces the node to step down
to follower mode. When a former is processed, it can force the node to stop
following the leader.
was (Author: ascherbakov):
The reason of test failure is a possible race between requestvote message and
appendentires message.
If a latter comes first it forces the node to step down to follower mode. When
a former is processed, it can step down the node again clearing the leader for
this term.
> ITNodeTest.testFollowerStartStopFollowing is still flaky
>
>
> Key: IGNITE-15271
> URL: https://issues.apache.org/jira/browse/IGNITE-15271
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 3.0.0-alpha2
>Reporter: Alexey Scherbakov
>Assignee: Alexey Scherbakov
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha3
>
>
> {noformat}
> org.opentest4j.AssertionFailedError
> org.opentest4j.AssertionFailedError: expected: but was:
> at
> org.apache.ignite.raft.jraft.core.ITNodeTest.testFollowerStartStopFollowing(ITNodeTest.java:2678)
> {noformat}
> The issue is caused by (unexpected) excessive number of state changes during
> leader election on term=2:
> {noformat}
> INFO: onStartFollowing: LeaderChangeContext [leaderId=172.17.0.6:5004,
> term=2, status=Status[ENEWLEADER<10011>: Follower receives message from new
> leader with the same term.]].
> Aug 09, 2021 9:32:37 AM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: onStartFollowing: LeaderChangeContext [leaderId=172.17.0.6:5004,
> term=2, status=Status[ENEWLEADER<10011>: Follower receives message from new
> leader with the same term.]].
> Aug 09, 2021 9:32:37 AM org.apache.ignite.lang.IgniteLogger logInternal
> Aug 09, 2021 9:32:37 AM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: onStartFollowing: LeaderChangeContext [leaderId=172.17.0.6:5004,
> term=2, status=Status[ENEWLEADER<10011>: Follower receives message from new
> leader with the same term.]].
> Aug 09, 2021 9:32:37 AM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: onStopFollowing: LeaderChangeContext [leaderId=172.17.0.6:5004, term=2,
> status=Status[EVOTEFORCANDIDATE<10010>: Raft node votes for some candidate,
> step down to restart election_timer.]].
> Aug 09, 2021 9:32:37 AM org.apache.ignite.lang.IgniteLogger logInternal
> Aug 09, 2021 9:32:37 AM org.apache.ignite.lang.IgniteLogger logInternal
> WARNING: Node received invalid RequestVoteResponse
> from 172.17.0.6:5006, state not in STATE_CANDIDATE but STATE_LEADER.
> Aug 09, 2021 9:32:37 AM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: onStartFollowing: LeaderChangeContext [leaderId=172.17.0.6:5004,
> term=2, status=Status[ENEWLEADER<10011>: Follower receives message from new
> leader with the same term.]].
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-15271) ITNodeTest.testFollowerStartStopFollowing is still flaky
[
https://issues.apache.org/jira/browse/IGNITE-15271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17396704#comment-17396704
]
Alexey Scherbakov commented on IGNITE-15271:
The reason of test failure is a possible race between requestvote message and
appendentires message.
If a latter comes first it forces the node to step down to follower mode. When
a former is processed, it can step down the node again clearing the leader for
this term.
> ITNodeTest.testFollowerStartStopFollowing is still flaky
>
>
> Key: IGNITE-15271
> URL: https://issues.apache.org/jira/browse/IGNITE-15271
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 3.0.0-alpha2
>Reporter: Alexey Scherbakov
>Assignee: Alexey Scherbakov
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha3
>
>
> {noformat}
> org.opentest4j.AssertionFailedError
> org.opentest4j.AssertionFailedError: expected: but was:
> at
> org.apache.ignite.raft.jraft.core.ITNodeTest.testFollowerStartStopFollowing(ITNodeTest.java:2678)
> {noformat}
> The issue is caused by (unexpected) excessive number of state changes during
> leader election on term=2:
> {noformat}
> INFO: onStartFollowing: LeaderChangeContext [leaderId=172.17.0.6:5004,
> term=2, status=Status[ENEWLEADER<10011>: Follower receives message from new
> leader with the same term.]].
> Aug 09, 2021 9:32:37 AM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: onStartFollowing: LeaderChangeContext [leaderId=172.17.0.6:5004,
> term=2, status=Status[ENEWLEADER<10011>: Follower receives message from new
> leader with the same term.]].
> Aug 09, 2021 9:32:37 AM org.apache.ignite.lang.IgniteLogger logInternal
> Aug 09, 2021 9:32:37 AM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: onStartFollowing: LeaderChangeContext [leaderId=172.17.0.6:5004,
> term=2, status=Status[ENEWLEADER<10011>: Follower receives message from new
> leader with the same term.]].
> Aug 09, 2021 9:32:37 AM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: onStopFollowing: LeaderChangeContext [leaderId=172.17.0.6:5004, term=2,
> status=Status[EVOTEFORCANDIDATE<10010>: Raft node votes for some candidate,
> step down to restart election_timer.]].
> Aug 09, 2021 9:32:37 AM org.apache.ignite.lang.IgniteLogger logInternal
> Aug 09, 2021 9:32:37 AM org.apache.ignite.lang.IgniteLogger logInternal
> WARNING: Node received invalid RequestVoteResponse
> from 172.17.0.6:5006, state not in STATE_CANDIDATE but STATE_LEADER.
> Aug 09, 2021 9:32:37 AM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: onStartFollowing: LeaderChangeContext [leaderId=172.17.0.6:5004,
> term=2, status=Status[ENEWLEADER<10011>: Follower receives message from new
> leader with the same term.]].
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-15267) A lot of spam in logs on thick client: "Unable to save statistics obsolescence info on non server node."
[ https://issues.apache.org/jira/browse/IGNITE-15267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Belyak reassigned IGNITE-15267: - Assignee: Alexander Belyak > A lot of spam in logs on thick client: "Unable to save statistics > obsolescence info on non server node." > > > Key: IGNITE-15267 > URL: https://issues.apache.org/jira/browse/IGNITE-15267 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 2.10 >Reporter: Ilya Kazakov >Assignee: Alexander Belyak >Priority: Major > > In logs on thick client there are a lot of such messages: > 2021-08-05 18:28:26,870 17371453 INFO > [grid-timeout-worker-#22%member-checkin-data-s] java.JavaLogger ( > JavaLogger.java: 284) - Unable to save statistics obsolescence info on non > server node. > It looks like unexpected calls to save stat on thick client. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15264) DistributedConfigurationStorage violates MetaStorageManager watch contract
[
https://issues.apache.org/jira/browse/IGNITE-15264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mirza Aliev updated IGNITE-15264:
-
Reviewer: Mirza Aliev
> DistributedConfigurationStorage violates MetaStorageManager watch contract
> --
>
> Key: IGNITE-15264
> URL: https://issues.apache.org/jira/browse/IGNITE-15264
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 3.0.0-alpha2
>Reporter: Ivan Bessonov
>Assignee: Ivan Bessonov
>Priority: Major
> Labels: iep-55, ignite-3
> Fix For: 3.0.0-alpha3
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> There are a few issues with the {{DistributedConfigurationStorage}} and
> related classes:
> * {{MetaStorageManager#DISTRIBUTED_PREFIX}} is located in the wrong class;
> * {{MetaStorageManager#APPLIED_REV}} constant should be changed;
> * {{DistributedConfigurationStorage#MASTER_KEY}} is confused with
> {{APPLIED_REV}} in some places, so
> {{DistributedConfigurationStorage#readAll}} returns god knows what;
> * watch callback in
> {{DistributedConfigurationStorage#registerConfigurationListener}} returns
> from {{onUpdate}} before notifications are processed.
> {{DistributedConfigurationStorage#notifyApplied}} doesn't work properly as
> well.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-15265) Update Ignite dependency: Netty
[ https://issues.apache.org/jira/browse/IGNITE-15265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17396680#comment-17396680 ] Dmitry Pavlov commented on IGNITE-15265: [~aonikolaev] could you please somehow exclude documenation update from the PR? > Update Ignite dependency: Netty > --- > > Key: IGNITE-15265 > URL: https://issues.apache.org/jira/browse/IGNITE-15265 > Project: Ignite > Issue Type: Improvement >Reporter: Alexandr >Assignee: Alexandr >Priority: Major > Labels: newbie > Fix For: 2.12 > > > Update Netty dependency 4.1.54.Final to 4.1.66.Final > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-15264) DistributedConfigurationStorage violates MetaStorageManager watch contract
[
https://issues.apache.org/jira/browse/IGNITE-15264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17396681#comment-17396681
]
Mirza Aliev commented on IGNITE-15264:
--
Hello [~ibessonov]! Changes look good to me!
> DistributedConfigurationStorage violates MetaStorageManager watch contract
> --
>
> Key: IGNITE-15264
> URL: https://issues.apache.org/jira/browse/IGNITE-15264
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 3.0.0-alpha2
>Reporter: Ivan Bessonov
>Assignee: Ivan Bessonov
>Priority: Major
> Labels: iep-55, ignite-3
> Fix For: 3.0.0-alpha3
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> There are a few issues with the {{DistributedConfigurationStorage}} and
> related classes:
> * {{MetaStorageManager#DISTRIBUTED_PREFIX}} is located in the wrong class;
> * {{MetaStorageManager#APPLIED_REV}} constant should be changed;
> * {{DistributedConfigurationStorage#MASTER_KEY}} is confused with
> {{APPLIED_REV}} in some places, so
> {{DistributedConfigurationStorage#readAll}} returns god knows what;
> * watch callback in
> {{DistributedConfigurationStorage#registerConfigurationListener}} returns
> from {{onUpdate}} before notifications are processed.
> {{DistributedConfigurationStorage#notifyApplied}} doesn't work properly as
> well.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15265) Update Ignite dependency: Netty
[ https://issues.apache.org/jira/browse/IGNITE-15265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Pavlov updated IGNITE-15265: --- Fix Version/s: 2.12 > Update Ignite dependency: Netty > --- > > Key: IGNITE-15265 > URL: https://issues.apache.org/jira/browse/IGNITE-15265 > Project: Ignite > Issue Type: Improvement >Reporter: Alexandr >Assignee: Alexandr >Priority: Major > Labels: newbie > Fix For: 2.12 > > > Update Netty dependency 4.1.54.Final to 4.1.66.Final > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15265) Update Ignite dependency: Netty
[ https://issues.apache.org/jira/browse/IGNITE-15265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Pavlov updated IGNITE-15265: --- Labels: newbie (was: ) > Update Ignite dependency: Netty > --- > > Key: IGNITE-15265 > URL: https://issues.apache.org/jira/browse/IGNITE-15265 > Project: Ignite > Issue Type: Improvement >Reporter: Alexandr >Assignee: Alexandr >Priority: Major > Labels: newbie > > Update Netty dependency 4.1.54.Final to 4.1.66.Final > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15265) Update Ignite dependency: Netty
[ https://issues.apache.org/jira/browse/IGNITE-15265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Pavlov updated IGNITE-15265: --- Ignite Flags: (was: Docs Required,Release Notes Required) > Update Ignite dependency: Netty > --- > > Key: IGNITE-15265 > URL: https://issues.apache.org/jira/browse/IGNITE-15265 > Project: Ignite > Issue Type: Improvement >Reporter: Alexandr >Assignee: Alexandr >Priority: Major > Labels: newbie > Fix For: 2.12 > > > Update Netty dependency 4.1.54.Final to 4.1.66.Final > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15259) Update Ignite dependencies
[ https://issues.apache.org/jira/browse/IGNITE-15259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Pavlov updated IGNITE-15259: --- Ignite Flags: Release Notes Required (was: Docs Required,Release Notes Required) > Update Ignite dependencies > -- > > Key: IGNITE-15259 > URL: https://issues.apache.org/jira/browse/IGNITE-15259 > Project: Ignite > Issue Type: Improvement >Reporter: Alexandr >Assignee: Alexandr >Priority: Major > > During the Igine analysis, there were some dependencies that can be updated > without affecting the work. In this ticket, I plan to collect the required > update modules. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14805) Avoid unconditional Lucene index creation in case of a String value type for a table
[
https://issues.apache.org/jira/browse/IGNITE-14805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-14805:
--
Release Note: Add distributed SQL property
'sql.disableCreateLuceneIndexForStringValueType' ('false' by default) to
disable creation lucene index by default for the String value type. If the
property is set to 'true' lucene index isn't created for the tables with String
value type. (was: Add distributed SQL property
'sql.createLuceneIndexForStringValueType' ('false' by default) to disable
creation lucene index by default for the String value type. If the property
is set to 'true' lucene index isn't created for the tables with String value
type.)
> Avoid unconditional Lucene index creation in case of a String value type for
> a table
>
>
> Key: IGNITE-14805
> URL: https://issues.apache.org/jira/browse/IGNITE-14805
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Affects Versions: 2.10
>Reporter: Vladimir Pligin
>Assignee: Taras Ledkov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In the H2TableDescriptor class there's a piece of code:
> {code:java}
> if (type().valueClass() == String.class) {
> try {
> luceneIdx = new GridLuceneIndex(idx.kernalContext(), tbl.cacheName(),
> type);
> }
> catch (IgniteCheckedException e1) {
> throw new IgniteException(e1);
> }
> }
> {code}
> For most cases it could be avoided.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14805) Avoid unconditional Lucene index creation in case of a String value type for a table
[
https://issues.apache.org/jira/browse/IGNITE-14805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-14805:
--
Release Note: Add distributed SQL property
'sql.createLuceneIndexForStringValueType' ('false' by default) to disable
creation lucene index by default for the String value type. If the property
is set to 'true' lucene index isn't created for the tables with String value
type.
> Avoid unconditional Lucene index creation in case of a String value type for
> a table
>
>
> Key: IGNITE-14805
> URL: https://issues.apache.org/jira/browse/IGNITE-14805
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Affects Versions: 2.10
>Reporter: Vladimir Pligin
>Assignee: Taras Ledkov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In the H2TableDescriptor class there's a piece of code:
> {code:java}
> if (type().valueClass() == String.class) {
> try {
> luceneIdx = new GridLuceneIndex(idx.kernalContext(), tbl.cacheName(),
> type);
> }
> catch (IgniteCheckedException e1) {
> throw new IgniteException(e1);
> }
> }
> {code}
> For most cases it could be avoided.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15278) Top level node start/stop refactoring
[ https://issues.apache.org/jira/browse/IGNITE-15278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-15278: - Labels: ignite-3 (was: ) > Top level node start/stop refactoring > - > > Key: IGNITE-15278 > URL: https://issues.apache.org/jira/browse/IGNITE-15278 > Project: Ignite > Issue Type: Improvement >Reporter: Alexander Lapin >Assignee: Alexander Lapin >Priority: Major > Labels: ignite-3 > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15278) Top level node start/stop refactoring
[ https://issues.apache.org/jira/browse/IGNITE-15278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-15278: - Ignite Flags: (was: Docs Required,Release Notes Required) > Top level node start/stop refactoring > - > > Key: IGNITE-15278 > URL: https://issues.apache.org/jira/browse/IGNITE-15278 > Project: Ignite > Issue Type: Improvement >Reporter: Alexander Lapin >Assignee: Alexander Lapin >Priority: Major > Labels: ignite-3 > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15280) Git rid of sequential reads in raft group
[ https://issues.apache.org/jira/browse/IGNITE-15280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-15280: - Labels: ignite-3 (was: ) > Git rid of sequential reads in raft group > - > > Key: IGNITE-15280 > URL: https://issues.apache.org/jira/browse/IGNITE-15280 > Project: Ignite > Issue Type: Improvement >Affects Versions: 3.0.0-alpha2 >Reporter: Alexey Scherbakov >Priority: Major > Labels: ignite-3 > > Current jraft read implementation uses read batching, efficiently making all > reads sequential [1] [2]. > Another issue is a absense of read batching in [3] > We should think about making reads concurrent. > Another task is to switch to lease reads as a default method to achieve > lowest latency. > [1] org.apache.ignite.raft.jraft.ReadOnlyService#addRequest > [2]org.apache.ignite.raft.jraft.core.ReadOnlyServiceImpl#notifySuccess > [3] > org.apache.ignite.raft.jraft.rpc.impl.client.ActionRequestProcessor#handleRequest -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15271) ITNodeTest.testFollowerStartStopFollowing is still flaky
[
https://issues.apache.org/jira/browse/IGNITE-15271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-15271:
-
Labels: ignite-3 (was: )
> ITNodeTest.testFollowerStartStopFollowing is still flaky
>
>
> Key: IGNITE-15271
> URL: https://issues.apache.org/jira/browse/IGNITE-15271
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 3.0.0-alpha2
>Reporter: Alexey Scherbakov
>Assignee: Alexey Scherbakov
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha3
>
>
> {noformat}
> org.opentest4j.AssertionFailedError
> org.opentest4j.AssertionFailedError: expected: but was:
> at
> org.apache.ignite.raft.jraft.core.ITNodeTest.testFollowerStartStopFollowing(ITNodeTest.java:2678)
> {noformat}
> The issue is caused by (unexpected) excessive number of state changes during
> leader election on term=2:
> {noformat}
> INFO: onStartFollowing: LeaderChangeContext [leaderId=172.17.0.6:5004,
> term=2, status=Status[ENEWLEADER<10011>: Follower receives message from new
> leader with the same term.]].
> Aug 09, 2021 9:32:37 AM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: onStartFollowing: LeaderChangeContext [leaderId=172.17.0.6:5004,
> term=2, status=Status[ENEWLEADER<10011>: Follower receives message from new
> leader with the same term.]].
> Aug 09, 2021 9:32:37 AM org.apache.ignite.lang.IgniteLogger logInternal
> Aug 09, 2021 9:32:37 AM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: onStartFollowing: LeaderChangeContext [leaderId=172.17.0.6:5004,
> term=2, status=Status[ENEWLEADER<10011>: Follower receives message from new
> leader with the same term.]].
> Aug 09, 2021 9:32:37 AM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: onStopFollowing: LeaderChangeContext [leaderId=172.17.0.6:5004, term=2,
> status=Status[EVOTEFORCANDIDATE<10010>: Raft node votes for some candidate,
> step down to restart election_timer.]].
> Aug 09, 2021 9:32:37 AM org.apache.ignite.lang.IgniteLogger logInternal
> Aug 09, 2021 9:32:37 AM org.apache.ignite.lang.IgniteLogger logInternal
> WARNING: Node received invalid RequestVoteResponse
> from 172.17.0.6:5006, state not in STATE_CANDIDATE but STATE_LEADER.
> Aug 09, 2021 9:32:37 AM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: onStartFollowing: LeaderChangeContext [leaderId=172.17.0.6:5004,
> term=2, status=Status[ENEWLEADER<10011>: Follower receives message from new
> leader with the same term.]].
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15244) testLearnerServices is still flaky
[
https://issues.apache.org/jira/browse/IGNITE-15244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-15244:
-
Ignite Flags: (was: Docs Required,Release Notes Required)
> testLearnerServices is still flaky
> --
>
> Key: IGNITE-15244
> URL: https://issues.apache.org/jira/browse/IGNITE-15244
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexey Scherbakov
>Priority: Major
> Labels: ignite-3
>
> It seems the elected leader has stepped down because it decides all other
> nodes are dead, which means no hearbeats has been acked [1].
> another problem - after joining a new learner cluster state is not the same.
> Aug 03, 2021 5:54:46 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Start ensureSame, leader=JRaftNode
> [nodeId=]
> Aug 03, 2021 5:55:06 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: End ensureSame, leader=JRaftNode
> [nodeId=]
> [1]
> {noformat}
> java.lang.NullPointerException
> at
> org.apache.ignite.raft.jraft.core.ITCliServiceTest.sendTestTaskAndWait(ITCliServiceTest.java:178)
> at
> org.apache.ignite.raft.jraft.core.ITCliServiceTest.testLearnerServices(ITCliServiceTest.java:187)
> --- Stderr: ---
> Aug 03, 2021 7:31:39 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: >>> Start test method: testLearnerServices()
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Connection created [address=/0.0.0.0:5003]
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Node joined: ClusterNode [id=5073c9e7-ee54-4c04-898d-eb6017045dab,
> name=172.17.0.6:5003, address=172.17.0.6:5003]
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Topology snapshot [nodes=1]
> ^-- ClusterNode [id=5073c9e7-ee54-4c04-898d-eb6017045dab,
> name=172.17.0.6:5003, address=172.17.0.6:5003]
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Starts FSMCaller successfully.
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> WARNING: No data for snapshot reader
> target/work/ITCliServiceTest/testLearnerServices_1628008299722/172.17.0.6_5003/snapshot.
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Node init, term=0, lastLogId=LogId
> [index=0, term=0],
> conf=172.17.0.6:5003,172.17.0.6:5004,172.17.0.6:5005,172.17.0.6:5103/learner,172.17.0.6:5104/learner,
> oldConf=.
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Start the RaftGroupService successfully
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Connection created [address=/0.0.0.0:5004]
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Node joined: ClusterNode [id=cd7f54af-1ca4-46f8-899e-e6b6c137a8d0,
> name=172.17.0.6:5004, address=172.17.0.6:5004]
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Topology snapshot [nodes=2]
> ^-- ClusterNode [id=cd7f54af-1ca4-46f8-899e-e6b6c137a8d0,
> name=172.17.0.6:5004, address=172.17.0.6:5004]
> ^-- ClusterNode [id=5073c9e7-ee54-4c04-898d-eb6017045dab,
> name=172.17.0.6:5003, address=172.17.0.6:5003]
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Node joined: ClusterNode [id=5073c9e7-ee54-4c04-898d-eb6017045dab,
> name=172.17.0.6:5003, address=172.17.0.6:5003]
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Topology snapshot [nodes=1]
> ^-- ClusterNode [id=5073c9e7-ee54-4c04-898d-eb6017045dab,
> name=172.17.0.6:5003, address=172.17.0.6:5003]
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Node joined: ClusterNode [id=cd7f54af-1ca4-46f8-899e-e6b6c137a8d0,
> name=172.17.0.6:5004, address=172.17.0.6:5004]
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Topology snapshot [nodes=2]
> ^-- ClusterNode [id=cd7f54af-1ca4-46f8-899e-e6b6c137a8d0,
> name=172.17.0.6:5004, address=172.17.0.6:5004]
> ^-- ClusterNode [id=5073c9e7-ee54-4c04-898d-eb6017045dab,
> name=172.17.0.6:5003, address=172.17.0.6:5003]
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Starts FSMCaller successfully.
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> WARNING: No data for snapshot reader
> target/work/ITCliServiceTest/testLearnerServices_1628008299722/172.17.0.6_5004/snapshot.
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Node init, term=0, lastLogId=LogId
> [index=0, term=0],
> conf=172.17.0.6:5003,172.17.0.6:5004,172.17.0.6:5005,172.17.0.6:5103/learner,172.17.0.6:5104/learner,
> oldConf=.
> Aug 03, 2021 7:31:41 PM org.apache.igni
[jira] [Updated] (IGNITE-15244) testLearnerServices is still flaky
[
https://issues.apache.org/jira/browse/IGNITE-15244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-15244:
-
Labels: ignite-3 (was: )
> testLearnerServices is still flaky
> --
>
> Key: IGNITE-15244
> URL: https://issues.apache.org/jira/browse/IGNITE-15244
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexey Scherbakov
>Priority: Major
> Labels: ignite-3
>
> It seems the elected leader has stepped down because it decides all other
> nodes are dead, which means no hearbeats has been acked [1].
> another problem - after joining a new learner cluster state is not the same.
> Aug 03, 2021 5:54:46 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Start ensureSame, leader=JRaftNode
> [nodeId=]
> Aug 03, 2021 5:55:06 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: End ensureSame, leader=JRaftNode
> [nodeId=]
> [1]
> {noformat}
> java.lang.NullPointerException
> at
> org.apache.ignite.raft.jraft.core.ITCliServiceTest.sendTestTaskAndWait(ITCliServiceTest.java:178)
> at
> org.apache.ignite.raft.jraft.core.ITCliServiceTest.testLearnerServices(ITCliServiceTest.java:187)
> --- Stderr: ---
> Aug 03, 2021 7:31:39 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: >>> Start test method: testLearnerServices()
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Connection created [address=/0.0.0.0:5003]
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Node joined: ClusterNode [id=5073c9e7-ee54-4c04-898d-eb6017045dab,
> name=172.17.0.6:5003, address=172.17.0.6:5003]
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Topology snapshot [nodes=1]
> ^-- ClusterNode [id=5073c9e7-ee54-4c04-898d-eb6017045dab,
> name=172.17.0.6:5003, address=172.17.0.6:5003]
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Starts FSMCaller successfully.
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> WARNING: No data for snapshot reader
> target/work/ITCliServiceTest/testLearnerServices_1628008299722/172.17.0.6_5003/snapshot.
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Node init, term=0, lastLogId=LogId
> [index=0, term=0],
> conf=172.17.0.6:5003,172.17.0.6:5004,172.17.0.6:5005,172.17.0.6:5103/learner,172.17.0.6:5104/learner,
> oldConf=.
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Start the RaftGroupService successfully
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Connection created [address=/0.0.0.0:5004]
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Node joined: ClusterNode [id=cd7f54af-1ca4-46f8-899e-e6b6c137a8d0,
> name=172.17.0.6:5004, address=172.17.0.6:5004]
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Topology snapshot [nodes=2]
> ^-- ClusterNode [id=cd7f54af-1ca4-46f8-899e-e6b6c137a8d0,
> name=172.17.0.6:5004, address=172.17.0.6:5004]
> ^-- ClusterNode [id=5073c9e7-ee54-4c04-898d-eb6017045dab,
> name=172.17.0.6:5003, address=172.17.0.6:5003]
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Node joined: ClusterNode [id=5073c9e7-ee54-4c04-898d-eb6017045dab,
> name=172.17.0.6:5003, address=172.17.0.6:5003]
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Topology snapshot [nodes=1]
> ^-- ClusterNode [id=5073c9e7-ee54-4c04-898d-eb6017045dab,
> name=172.17.0.6:5003, address=172.17.0.6:5003]
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Node joined: ClusterNode [id=cd7f54af-1ca4-46f8-899e-e6b6c137a8d0,
> name=172.17.0.6:5004, address=172.17.0.6:5004]
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Topology snapshot [nodes=2]
> ^-- ClusterNode [id=cd7f54af-1ca4-46f8-899e-e6b6c137a8d0,
> name=172.17.0.6:5004, address=172.17.0.6:5004]
> ^-- ClusterNode [id=5073c9e7-ee54-4c04-898d-eb6017045dab,
> name=172.17.0.6:5003, address=172.17.0.6:5003]
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Starts FSMCaller successfully.
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> WARNING: No data for snapshot reader
> target/work/ITCliServiceTest/testLearnerServices_1628008299722/172.17.0.6_5004/snapshot.
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: Node init, term=0, lastLogId=LogId
> [index=0, term=0],
> conf=172.17.0.6:5003,172.17.0.6:5004,172.17.0.6:5005,172.17.0.6:5103/learner,172.17.0.6:5104/learner,
> oldConf=.
> Aug 03, 2021 7:31:41 PM org.apache.ignite.lang.IgniteLogger logInternal
>
[jira] [Commented] (IGNITE-15208) Remove unnecessary rebalance order classes for exchange thread
[
https://issues.apache.org/jira/browse/IGNITE-15208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17396627#comment-17396627
]
Ignite TC Bot commented on IGNITE-15208:
{panel:title=Branch: [pull/9310/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9310/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=6123019&buildTypeId=IgniteTests24Java8_RunAll]
> Remove unnecessary rebalance order classes for exchange thread
> --
>
> Key: IGNITE-15208
> URL: https://issues.apache.org/jira/browse/IGNITE-15208
> Project: Ignite
> Issue Type: Task
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Major
> Fix For: 2.12
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> Some pieces of code related to the ordering of cache groups for the rebalance
> procedure can be removed. These parts of the code have been written to
> support Ignite under java 7 and no more actual.
> E.g.
> {code}
> for (Map.Entry e :
> assignsMap.entrySet()) {
> int grpId = e.getKey();
> CacheGroupContext grp = cctx.cache().cacheGroup(grpId);
> CacheRebalanceOrder order = new CacheRebalanceOrder(
> grp.config().getRebalanceOrder(),
> grp.config().getRebalanceMode());
> if (orderMap.get(order) == null)
> orderMap.put(order, new ArrayList(size));
> orderMap.get(order).add(grpId);
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-15208) Remove unnecessary rebalance order classes for exchange thread
[
https://issues.apache.org/jira/browse/IGNITE-15208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17396628#comment-17396628
]
Maxim Muzafarov commented on IGNITE-15208:
--
[~ptupitsyn]
I've merged the fix.
> Remove unnecessary rebalance order classes for exchange thread
> --
>
> Key: IGNITE-15208
> URL: https://issues.apache.org/jira/browse/IGNITE-15208
> Project: Ignite
> Issue Type: Task
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Major
> Fix For: 2.12
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> Some pieces of code related to the ordering of cache groups for the rebalance
> procedure can be removed. These parts of the code have been written to
> support Ignite under java 7 and no more actual.
> E.g.
> {code}
> for (Map.Entry e :
> assignsMap.entrySet()) {
> int grpId = e.getKey();
> CacheGroupContext grp = cctx.cache().cacheGroup(grpId);
> CacheRebalanceOrder order = new CacheRebalanceOrder(
> grp.config().getRebalanceOrder(),
> grp.config().getRebalanceMode());
> if (orderMap.get(order) == null)
> orderMap.put(order, new ArrayList(size));
> orderMap.get(order).add(grpId);
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15280) Git rid of sequential reads in raft group
[ https://issues.apache.org/jira/browse/IGNITE-15280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Scherbakov updated IGNITE-15280: --- Description: Current jraft read implementation uses read batching, efficiently making all reads sequential [1] [2]. Another issue is a absense of read batching in [3] We should think about making reads concurrent. Another task is to switch to lease reads as a default method to achieve lowest latency. [1] org.apache.ignite.raft.jraft.ReadOnlyService#addRequest [2]org.apache.ignite.raft.jraft.core.ReadOnlyServiceImpl#notifySuccess [3] org.apache.ignite.raft.jraft.rpc.impl.client.ActionRequestProcessor#handleRequest was: Current jraft read implementation uses read batching, efficiently making all reads sequential [1] [2]. Another issues is a absense of read batching in [3] We should think about making reads concurrent. Another task is to switch to lease reads as a default method to achieve lowest latency. [1] org.apache.ignite.raft.jraft.ReadOnlyService#addRequest [2]org.apache.ignite.raft.jraft.core.ReadOnlyServiceImpl#notifySuccess [3] org.apache.ignite.raft.jraft.rpc.impl.client.ActionRequestProcessor#handleRequest > Git rid of sequential reads in raft group > - > > Key: IGNITE-15280 > URL: https://issues.apache.org/jira/browse/IGNITE-15280 > Project: Ignite > Issue Type: Improvement >Affects Versions: 3.0.0-alpha2 >Reporter: Alexey Scherbakov >Priority: Major > > Current jraft read implementation uses read batching, efficiently making all > reads sequential [1] [2]. > Another issue is a absense of read batching in [3] > We should think about making reads concurrent. > Another task is to switch to lease reads as a default method to achieve > lowest latency. > [1] org.apache.ignite.raft.jraft.ReadOnlyService#addRequest > [2]org.apache.ignite.raft.jraft.core.ReadOnlyServiceImpl#notifySuccess > [3] > org.apache.ignite.raft.jraft.rpc.impl.client.ActionRequestProcessor#handleRequest -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15280) Git rid of sequential reads in raft group
[ https://issues.apache.org/jira/browse/IGNITE-15280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Scherbakov updated IGNITE-15280: --- Description: Current jraft read implementation uses read batching, efficiently making all reads sequential [1] [2]. Another issues is a absense of read batching in [3] We should think about making reads concurrent. Another task is to switch to lease reads as a default method to achieve lowest latency. [1] org.apache.ignite.raft.jraft.ReadOnlyService#addRequest [2]org.apache.ignite.raft.jraft.core.ReadOnlyServiceImpl#notifySuccess [3] org.apache.ignite.raft.jraft.rpc.impl.client.ActionRequestProcessor#handleRequest was: Current jraft read implementation uses read batching, efficiently making all reads sequential [1] [2]. Another issues is a absense of batching in [2] We should think about making reads concurrent. Another task is to switch to lease reads as a default method to achieve lowest latency. [1] org.apache.ignite.raft.jraft.ReadOnlyService#addRequest [2]org.apache.ignite.raft.jraft.core.ReadOnlyServiceImpl#notifySuccess [3] org.apache.ignite.raft.jraft.rpc.impl.client.ActionRequestProcessor#handleRequest > Git rid of sequential reads in raft group > - > > Key: IGNITE-15280 > URL: https://issues.apache.org/jira/browse/IGNITE-15280 > Project: Ignite > Issue Type: Improvement >Affects Versions: 3.0.0-alpha2 >Reporter: Alexey Scherbakov >Priority: Major > > Current jraft read implementation uses read batching, efficiently making all > reads sequential [1] [2]. > Another issues is a absense of read batching in [3] > We should think about making reads concurrent. > Another task is to switch to lease reads as a default method to achieve > lowest latency. > [1] org.apache.ignite.raft.jraft.ReadOnlyService#addRequest > [2]org.apache.ignite.raft.jraft.core.ReadOnlyServiceImpl#notifySuccess > [3] > org.apache.ignite.raft.jraft.rpc.impl.client.ActionRequestProcessor#handleRequest -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15280) Git rid of sequential reads in raft group
[ https://issues.apache.org/jira/browse/IGNITE-15280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Scherbakov updated IGNITE-15280: --- Description: Current jraft read implementation uses read batching, efficiently making all reads sequential [1] [2]. Another issues is a absense of batching in [2] We should think about making reads concurrent. Another task is to switch to lease reads as a default method to achieve lowest latency. [1] org.apache.ignite.raft.jraft.ReadOnlyService#addRequest [2]org.apache.ignite.raft.jraft.core.ReadOnlyServiceImpl#notifySuccess [3] org.apache.ignite.raft.jraft.rpc.impl.client.ActionRequestProcessor#handleRequest was: Current jraft read implementation uses read batching, efficiently making all reads sequential[1] [2]. Another issues is a absense of batching in [2] We should think about making reads concurrent. Another task is to switch to lease reads as a default method to achieve lowest latency. [1] org.apache.ignite.raft.jraft.ReadOnlyService#addRequest [2]org.apache.ignite.raft.jraft.core.ReadOnlyServiceImpl#notifySuccess [3] org.apache.ignite.raft.jraft.rpc.impl.client.ActionRequestProcessor#handleRequest > Git rid of sequential reads in raft group > - > > Key: IGNITE-15280 > URL: https://issues.apache.org/jira/browse/IGNITE-15280 > Project: Ignite > Issue Type: Improvement >Affects Versions: 3.0.0-alpha2 >Reporter: Alexey Scherbakov >Priority: Major > > Current jraft read implementation uses read batching, efficiently making all > reads sequential [1] [2]. > Another issues is a absense of batching in [2] > We should think about making reads concurrent. > Another task is to switch to lease reads as a default method to achieve > lowest latency. > [1] org.apache.ignite.raft.jraft.ReadOnlyService#addRequest > [2]org.apache.ignite.raft.jraft.core.ReadOnlyServiceImpl#notifySuccess > [3] > org.apache.ignite.raft.jraft.rpc.impl.client.ActionRequestProcessor#handleRequest -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15280) Git rid of sequential reads in raft group
[ https://issues.apache.org/jira/browse/IGNITE-15280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Scherbakov updated IGNITE-15280: --- Description: Current jraft read implementation uses read batching, efficiently making all reads sequential[1] [2]. Another issues is a absense of batching in [2] We should think about making reads concurrent. Another task is to switch to lease reads as a default method to achieve lowest latency. [1] org.apache.ignite.raft.jraft.ReadOnlyService#addRequest [2]org.apache.ignite.raft.jraft.core.ReadOnlyServiceImpl#notifySuccess [3] org.apache.ignite.raft.jraft.rpc.impl.client.ActionRequestProcessor#handleRequest was: Due to some legacy issues all reads are implemented using [1] callback, efficiently making it sequential. If a lease-based read (having lowest latency) model is used this is pointless, even for a readindex method reads can be concurrent. We should refactor org.apache.ignite.internal.table.distributed.raft.PartitionListener#onRead for allowing concurrent batched reads. Another task is to switch to lease reads as a default method. [1] org.apache.ignite.internal.table.distributed.raft.PartitionListener#onRead > Git rid of sequential reads in raft group > - > > Key: IGNITE-15280 > URL: https://issues.apache.org/jira/browse/IGNITE-15280 > Project: Ignite > Issue Type: Improvement >Affects Versions: 3.0.0-alpha2 >Reporter: Alexey Scherbakov >Priority: Major > > Current jraft read implementation uses read batching, efficiently making all > reads sequential[1] [2]. > Another issues is a absense of batching in [2] > We should think about making reads concurrent. > Another task is to switch to lease reads as a default method to achieve > lowest latency. > [1] org.apache.ignite.raft.jraft.ReadOnlyService#addRequest > [2]org.apache.ignite.raft.jraft.core.ReadOnlyServiceImpl#notifySuccess > [3] > org.apache.ignite.raft.jraft.rpc.impl.client.ActionRequestProcessor#handleRequest -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-15261) Update Ignite dependency: Jackson
[ https://issues.apache.org/jira/browse/IGNITE-15261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17396594#comment-17396594 ] Dmitry Pavlov commented on IGNITE-15261: [~aonikolaev] LGTM, merged to master - https://github.com/apache/ignite/commit/7897ac2cad7a534a9df0da3b4d99a22380b8205b. Thank you for contribution > Update Ignite dependency: Jackson > - > > Key: IGNITE-15261 > URL: https://issues.apache.org/jira/browse/IGNITE-15261 > Project: Ignite > Issue Type: Improvement >Reporter: Alexandr >Assignee: Alexandr >Priority: Major > Labels: newbie > Fix For: 2.12 > > > Update jackson dependency 2.9.10 to 2.12.4 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15261) Update Ignite dependency: Jackson
[ https://issues.apache.org/jira/browse/IGNITE-15261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Pavlov updated IGNITE-15261: --- Labels: newbie (was: ) > Update Ignite dependency: Jackson > - > > Key: IGNITE-15261 > URL: https://issues.apache.org/jira/browse/IGNITE-15261 > Project: Ignite > Issue Type: Improvement >Reporter: Alexandr >Assignee: Alexandr >Priority: Major > Labels: newbie > Fix For: 2.12 > > > Update jackson dependency 2.9.10 to 2.12.4 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15259) Update Ignite dependencies
[ https://issues.apache.org/jira/browse/IGNITE-15259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Pavlov updated IGNITE-15259: --- Summary: Update Ignite dependencies (was: Update Ignite dependency) > Update Ignite dependencies > -- > > Key: IGNITE-15259 > URL: https://issues.apache.org/jira/browse/IGNITE-15259 > Project: Ignite > Issue Type: Improvement >Reporter: Alexandr >Assignee: Alexandr >Priority: Major > > During the Igine analysis, there were some dependencies that can be updated > without affecting the work. In this ticket, I plan to collect the required > update modules. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15261) Update Ignite dependency: Jackson
[ https://issues.apache.org/jira/browse/IGNITE-15261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Pavlov updated IGNITE-15261: --- Ignite Flags: (was: Docs Required,Release Notes Required) > Update Ignite dependency: Jackson > - > > Key: IGNITE-15261 > URL: https://issues.apache.org/jira/browse/IGNITE-15261 > Project: Ignite > Issue Type: Improvement >Reporter: Alexandr >Assignee: Alexandr >Priority: Major > Fix For: 2.12 > > > Update jackson dependency 2.9.10 to 2.12.4 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15261) Update Ignite dependency: Jackson
[ https://issues.apache.org/jira/browse/IGNITE-15261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Pavlov updated IGNITE-15261: --- Fix Version/s: 2.12 > Update Ignite dependency: Jackson > - > > Key: IGNITE-15261 > URL: https://issues.apache.org/jira/browse/IGNITE-15261 > Project: Ignite > Issue Type: Improvement >Reporter: Alexandr >Assignee: Alexandr >Priority: Major > Fix For: 2.12 > > > Update jackson dependency 2.9.10 to 2.12.4 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15280) Git rid of sequential reads in raft group
[ https://issues.apache.org/jira/browse/IGNITE-15280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Scherbakov updated IGNITE-15280: --- Description: Due to some legacy issues all reads are implemented using [1] callback, efficiently making it sequential. If a lease-based read (having lowest latency) model is used this is pointless, even for a readindex method reads can be concurrent. We should refactor org.apache.ignite.internal.table.distributed.raft.PartitionListener#onRead for allowing concurrent batched reads. Another task is to switch to lease reads as a default method. [1] org.apache.ignite.internal.table.distributed.raft.PartitionListener#onRead was: Due to some legacy issues all reads are implemented using [1] callback, efficiently making it sequential. If a lease-based read (having lowest latency) model is used this is pointless, even for a readindex method reads can be concurrent. We should refactor org.apache.ignite.internal.table.distributed.raft.PartitionListener#onRead for allowing concurrent batched reads. Another task is to switch to lease reads as a default method. [1] org.apache.ignite.internal.table.distributed.raft.PartitionListener#onRead > Git rid of sequential reads in raft group > - > > Key: IGNITE-15280 > URL: https://issues.apache.org/jira/browse/IGNITE-15280 > Project: Ignite > Issue Type: Improvement >Affects Versions: 3.0.0-alpha2 >Reporter: Alexey Scherbakov >Priority: Major > > Due to some legacy issues all reads are implemented using [1] callback, > efficiently making it sequential. > If a lease-based read (having lowest latency) model is used this is > pointless, even for a readindex method reads can be concurrent. > We should refactor > org.apache.ignite.internal.table.distributed.raft.PartitionListener#onRead > for allowing concurrent batched reads. > Another task is to switch to lease reads as a default method. > [1] org.apache.ignite.internal.table.distributed.raft.PartitionListener#onRead -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15280) Git rid of sequential reads in raft group
[ https://issues.apache.org/jira/browse/IGNITE-15280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Scherbakov updated IGNITE-15280: --- Description: Due to some legacy issues all reads are implemented using [1] callback, efficiently making it sequential. If a lease-based read (having lowest latency) model is used this is pointless, even for a readindex method reads can be concurrent. We should refactor org.apache.ignite.internal.table.distributed.raft.PartitionListener#onRead for allowing concurrent batched reads. Another task is to switch to lease reads as a default method. [1] org.apache.ignite.internal.table.distributed.raft.PartitionListener#onRead was: Due to some legacy issues all reads are implemented using [1] callback, efficiently making it sequential. If a lease-based read (having lowest latency) model is used this is pointless, even for a readindex method reads can be concurrent. We should refactor org.apache.ignite.internal.table.distributed.raft.PartitionListener#onRead for allowing concurrent batched reads. [1] org.apache.ignite.internal.table.distributed.raft.PartitionListener#onRead > Git rid of sequential reads in raft group > - > > Key: IGNITE-15280 > URL: https://issues.apache.org/jira/browse/IGNITE-15280 > Project: Ignite > Issue Type: Improvement >Affects Versions: 3.0.0-alpha2 >Reporter: Alexey Scherbakov >Priority: Major > > Due to some legacy issues all reads are implemented using [1] callback, > efficiently making it sequential. > If a lease-based read (having lowest latency) model is used this is > pointless, even for a readindex method reads can be concurrent. > We should refactor > org.apache.ignite.internal.table.distributed.raft.PartitionListener#onRead > for allowing concurrent batched reads. > Another task is to switch to lease reads as a default method. > [1] org.apache.ignite.internal.table.distributed.raft.PartitionListener#onRead -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-15280) Git rid of sequential reads in raft group
Alexey Scherbakov created IGNITE-15280: -- Summary: Git rid of sequential reads in raft group Key: IGNITE-15280 URL: https://issues.apache.org/jira/browse/IGNITE-15280 Project: Ignite Issue Type: Improvement Affects Versions: 3.0.0-alpha2 Reporter: Alexey Scherbakov Due to some legacy issues all reads are implemented using [1] callback, efficiently making it sequential. If a lease-based read (having lowest latency) model is used this is pointless, even for a readindex method reads can be concurrent. We should refactor org.apache.ignite.internal.table.distributed.raft.PartitionListener#onRead for allowing concurrent batched reads. [1] org.apache.ignite.internal.table.distributed.raft.PartitionListener#onRead -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14790) Replace a storage map in RAFT partition listener to the persistence storage
[
https://issues.apache.org/jira/browse/IGNITE-14790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Bessonov updated IGNITE-14790:
---
Ignite Flags: (was: Docs Required,Release Notes Required)
> Replace a storage map in RAFT partition listener to the persistence storage
> ---
>
> Key: IGNITE-14790
> URL: https://issues.apache.org/jira/browse/IGNITE-14790
> Project: Ignite
> Issue Type: Improvement
>Reporter: Vladislav Pyatkov
>Assignee: Semyon Danilov
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha3
>
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> The map is using as a temporary solution until storage will be implemented.
> Here we need to implement the RAFT listener through the persistent layer:
> {code:java}
> /**
> * Storage.
> * This is a temporary solution, it will apply until persistence layer
> would not be implemented.
> * TODO: Replace in the future.
> */
> private ConcurrentHashMap storage = new
> ConcurrentHashMap<>();
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14790) Replace a storage map in RAFT partition listener to the persistence storage
[
https://issues.apache.org/jira/browse/IGNITE-14790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Bessonov updated IGNITE-14790:
---
Labels: ignite-3 (was: )
> Replace a storage map in RAFT partition listener to the persistence storage
> ---
>
> Key: IGNITE-14790
> URL: https://issues.apache.org/jira/browse/IGNITE-14790
> Project: Ignite
> Issue Type: Improvement
>Reporter: Vladislav Pyatkov
>Assignee: Semyon Danilov
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha3
>
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> The map is using as a temporary solution until storage will be implemented.
> Here we need to implement the RAFT listener through the persistent layer:
> {code:java}
> /**
> * Storage.
> * This is a temporary solution, it will apply until persistence layer
> would not be implemented.
> * TODO: Replace in the future.
> */
> private ConcurrentHashMap storage = new
> ConcurrentHashMap<>();
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15158) Integration Tests logs are too big
[ https://issues.apache.org/jira/browse/IGNITE-15158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Bessonov updated IGNITE-15158: --- Fix Version/s: 3.0.0-alpha3 > Integration Tests logs are too big > -- > > Key: IGNITE-15158 > URL: https://issues.apache.org/jira/browse/IGNITE-15158 > Project: Ignite > Issue Type: Improvement >Affects Versions: 3.0.0-alpha2 >Reporter: Ivan Bessonov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha3 > > > Logs for integration tests exceed 60 Mb already, this is not ok. It's > impossible to attach full build log to the Jira issue for further > investigation, for example. > > Link to the suite: > https://ci.ignite.apache.org/buildConfiguration/ignite3_Test_IntegrationTests_IntegrationTests?branch=%3Cdefault%3E&buildTypeTab=overview&mode=builds#all-projects -- 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=17396556#comment-17396556
]
Ignite TC Bot commented on IGNITE-14703:
{panel:title=Branch: [pull/9081/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9081/head] Base: [master] : New Tests
(20)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Cache 9{color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=6123126]]
* {color:#013220}IgniteCacheTestSuite9:
CacheMetricsAddRemoveTest.testCacheMetricsNotRemovedOnStop[cacheMode=PARTITIONED,nearEnabled=false]
- PASSED{color}
* {color:#013220}IgniteCacheTestSuite9:
CacheMetricsAddRemoveTest.testCacheMetricsNotRemovedOnStop[cacheMode=PARTITIONED,nearEnabled=true]
- PASSED{color}
* {color:#013220}IgniteCacheTestSuite9:
CacheMetricsAddRemoveTest.testCacheMetricsNotRemovedOnStop[cacheMode=REPLICATED,nearEnabled=false]
- PASSED{color}
* {color:#013220}IgniteCacheTestSuite9:
CacheMetricsAddRemoveTest.testCacheMetricsNotRemovedOnStop[cacheMode=REPLICATED,nearEnabled=true]
- PASSED{color}
{color:#8b}Queries 1{color} [[tests
11|https://ci.ignite.apache.org/viewLog.html?buildId=6123480]]
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
GridCacheFullTextQueryLimitTest.testResultOrderedByScore[nodesCnt=7] -
PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
GridCacheFullTextQueryLimitTest.testResultOrderedByScore[nodesCnt=8] -
PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
GridCacheFullTextQueryLimitTest.testResultOrderedByScore[nodesCnt=1] -
PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
GridCacheFullTextQueryLimitTest.testResultOrderedByScore[nodesCnt=2] -
PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
GridCacheFullTextQueryLimitTest.testResultOrderedByScore[nodesCnt=5] -
PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
GridCacheFullTextQueryLimitTest.testResultOrderedByScore[nodesCnt=6] -
PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
GridCacheFullTextQueryLimitTest.testResultOrderedByScore[nodesCnt=3] -
PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
GridCacheFullTextQueryLimitTest.testResultOrderedByScore[nodesCnt=4] -
PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
GridCacheFullTextQueryPagesTest.testTextQueryHighLimitedMultiplePages -
PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
GridCacheFullTextQueryPagesTest.testTextQueryMultiplePagesNoLimit -
PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
GridCacheFullTextQueryPagesTest.testTextQueryLimitedMultiplePages -
PASSED{color}
... and 0 new tests
{color:#8b}Cache 1{color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=6123118]]
* {color:#013220}IgniteBinaryCacheTestSuite:
DataStorageConfigurationValidationTest.testSetWalSegmentSizeShouldBeOkWhenSizeBetween512KbAnd2Gb
- PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
DataStorageConfigurationValidationTest.testWalSegmentSizeOverflow -
PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
DataStorageConfigurationValidationTest.testSetWalSegmentSizeShouldThrowExceptionWhenSizeLessThen512Kb
- PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
DataStorageConfigurationValidationTest.testSetWalSegmentsCountShouldThrowExceptionThenLessThan2
- PASSED{color}
{color:#8b}PDS 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6123133]]
* {color:#013220}IgnitePdsTestSuite:
SegmentAwareTest.testAssertFail_WhenReleaseUnreservedSegment - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6123163&buildTypeId=IgniteTests24Java8_RunAll]
> 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: 18h 20m
> 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] [Updated] (IGNITE-13668) Type system. Number(n) and Decimal native types.
[
https://issues.apache.org/jira/browse/IGNITE-13668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Mashenkov updated IGNITE-13668:
--
Description:
Let's extend native support for Numeric types.
* Number( n ) is an {{n}}-bytes two-complement integer signed value encoded in
the varlong style represented as {{BigInteger}}.
* Decimal is a direct mapping to BigDecimal value.
Each number must have a single binary representation.
In general, Decimal allows different equal representations for the same number
"10" and "10.0".
So, to fix this Decimals must be converted to the column scale before being
saved.
Actually, serialization with preserving is not necessary because indices may
have their own format for inline values.
was:
Let's extend native support for Numeric types.
* Number( n ) is an {{n}}-bytes two-complement integer signed value encoded in
the varlong style
(so that Number(4) can be mapped to integer and Number(8) can be mapped to long
during (de)serialization).
* Larger numbers can be represented as {{BigInteger}}.
* The Number( n ) is a varlen type, so it will take two additional bytes in the
varlen table, so types smaller than Number(4) are better represented by
{{byte}} and {{short}} and {{int}} types as their fixlen encoding takes exactly
1, 2, 4 bytes respectively.
* Decimal is a direct mapping to BigDecimal value.
> Type system. Number(n) and Decimal native types.
>
>
> Key: IGNITE-13668
> URL: https://issues.apache.org/jira/browse/IGNITE-13668
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Assignee: Vladimir Ermakov
>Priority: Major
> Labels: iep-54, ignite-3
> Fix For: 3.0.0-alpha3
>
> Original Estimate: 168h
> Time Spent: 7.5h
> Remaining Estimate: 160.5h
>
> Let's extend native support for Numeric types.
> * Number( n ) is an {{n}}-bytes two-complement integer signed value encoded
> in the varlong style represented as {{BigInteger}}.
> * Decimal is a direct mapping to BigDecimal value.
> Each number must have a single binary representation.
> In general, Decimal allows different equal representations for the same
> number "10" and "10.0".
> So, to fix this Decimals must be converted to the column scale before being
> saved.
> Actually, serialization with preserving is not necessary because indices may
> have their own format for inline values.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
