[jira] [Commented] (IGNITE-9406) Improve SQL "Performance and Debugging" page
[ https://issues.apache.org/jira/browse/IGNITE-9406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689137#comment-16689137 ] Vladimir Ozerov commented on IGNITE-9406: - [~Artem Budnikov], what kind of details are needed? > Improve SQL "Performance and Debugging" page > > > Key: IGNITE-9406 > URL: https://issues.apache.org/jira/browse/IGNITE-9406 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Major > Fix For: 2.7 > > Attachments: ignite_sql_perf.txt > > > I prepared a document for one of Ignite clients with some advanced > information about how various performance optimizations work in Ignite SQL. > Let's compare this document with our "Performance and Debugging" page [1], > and enhance the latter with missing info (if any). > P.S.: Document is attached. Russian language. > [1] > https://apacheignite-sql.readme.io/docs/performance-and-debugging#query-execution-flow-optimizations -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8765) SQL event is not fired when query is reduced to local form
[
https://issues.apache.org/jira/browse/IGNITE-8765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689136#comment-16689136
]
Vladimir Ozerov commented on IGNITE-8765:
-
[~pkouznet], please also pay attention to forced failure in
{{IgniteCacheReplicatedQuerySelfTest.testSqlQueryEvents}}. Most probably
correct fix will let this test pass.
> SQL event is not fired when query is reduced to local form
> --
>
> Key: IGNITE-8765
> URL: https://issues.apache.org/jira/browse/IGNITE-8765
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.4, 2.5
>Reporter: Vladimir Ozerov
>Assignee: Pavel Kuznetsov
>Priority: Major
>
> *Reproducer*
> {{org.apache.ignite.internal.processors.cache.IgniteCacheAbstractQuerySelfTest#testSqlQueryEvents}}
> *Root Cause*
> Local and non-local query execution is performed differently. Local query is
> logged early. However, non-local query could be reduced after that. As a
> result, event is missed. Try change
> {{org.apache.ignite.internal.processors.query.h2.sql.GridSqlQueryParser#isLocalQuery}}
> method to always return {{false}} and then re-run failed test to see the
> difference.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10291) Unable to find row by index created on partial baseline topology
Pavel Vinokurov created IGNITE-10291: Summary: Unable to find row by index created on partial baseline topology Key: IGNITE-10291 URL: https://issues.apache.org/jira/browse/IGNITE-10291 Project: Ignite Issue Type: Bug Components: cache, sql Affects Versions: 2.6, 2.5, 2.4 Reporter: Pavel Vinokurov Attachments: Reproducer.java Steps to reproduce: 1. Start two nodes cluster with persistence. 2. Create table CREATE TABLE PERSON ( FIRST_NAME VARCHAR, LAST_NAME VARCHAR, ADDRESS VARCHAR, LANG VARCHAR, BIRTH_DATE TIMESTAMP, CONSTRAINT PK_PESON PRIMARY KEY (FIRST_NAME,LAST_NAME,ADDRESS,LANG) ) WITH "key_type=PersonKeyType, CACHE_NAME=PersonCache, value_type=PersonValueType, AFFINITY_KEY=FIRST_NAME,template=PARTITIONED,backups=1" Insert 1000 rows. 3. Stop the second node. 4. Create index create index PERSON_FIRST_NAME_IDX on PERSON(FIRST_NAME) 5. Start the second node 6. Perform select query for each row: select * from PERSON use index(PERSON_FIRST_NAME_IDX) where FIRST_NAME=? and LAST_NAME=? and ADDRESS=? and LANG = ? Result: The select doesn't return row in half of cases. The reproducer is attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9517) Replace uses of ConcurrentHashSet with GridConcurrentHashSet in tests
[ https://issues.apache.org/jira/browse/IGNITE-9517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689135#comment-16689135 ] Roman Shtykh commented on IGNITE-9517: -- Tests looks ok (several flaky test). > Replace uses of ConcurrentHashSet with GridConcurrentHashSet in tests > - > > Key: IGNITE-9517 > URL: https://issues.apache.org/jira/browse/IGNITE-9517 > Project: Ignite > Issue Type: Improvement >Reporter: Ilya Kasnacheev >Assignee: Roman Shtykh >Priority: Major > Labels: test > > There are numerous tests where org.eclipse.jetty.util.ConcurrentHashSet is > used. > We should not refer to jetty's utils and use our GridConcurrentHashSet > instead. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10282) control.sh: implement proper shell arguments escaping due to the possible usage of regular expression in --cache command
[
https://issues.apache.org/jira/browse/IGNITE-10282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-10282:
-
Fix Version/s: (was: 2.7)
2.8
> control.sh: implement proper shell arguments escaping due to the possible
> usage of regular expression in --cache command
>
>
> Key: IGNITE-10282
> URL: https://issues.apache.org/jira/browse/IGNITE-10282
> Project: Ignite
> Issue Type: Bug
>Reporter: Max Shonichev
>Priority: Major
> Fix For: 2.8
>
>
> mandatory argument regexPattern after --cache list command is not
> shell-escaped, which leads to unexpected behaviour
> {noformat}
> $ IGNITE_HOME=`pwd` bin/control.sh --cache list '*' --config
> Control utility [ver. 2.5.1-p150#20181101-sha1:b46a69df]
> 2018 Copyright(C) Apache Software Foundation
> User: mshonichev
>
> Check arguments.
> Error: Invalid UUID string: benchmarks
> {noformat}
> {noformat}
> $ IGNITE_HOME=`pwd` bin/control.sh --cache list '.*' --config
> Control utility [ver. 2.5.1-p150#20181101-sha1:b46a69df]
> 2018 Copyright(C) Apache Software Foundation
> User: mshonichev
>
> Check arguments.
> Error: Invalid UUID string: ..
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10283) `control.sh --baseline` does not output other nodes when cluster is inactive
[
https://issues.apache.org/jira/browse/IGNITE-10283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-10283:
-
Fix Version/s: (was: 2.7)
2.8
> `control.sh --baseline` does not output other nodes when cluster is inactive
>
>
> Key: IGNITE-10283
> URL: https://issues.apache.org/jira/browse/IGNITE-10283
> Project: Ignite
> Issue Type: Bug
>Reporter: Max Shonichev
>Priority: Major
> Fix For: 2.8
>
>
> 1. start 2 nodes from clean LFS
> 2. control.sh --baseline
> expected: 0 baseline nodes, 2 other nodes
> actual: 0 baseline nodes, 0 other nodes, BUG
> {noformat}
> Control utility [ver. 2.5.1-p150#20181101-sha1:b46a69df]
> 2018 Copyright(C) Apache Software Foundation
> User: mshonichev
>
> Cluster state: inactive
> Current topology version: 2
> Baseline nodes not found.
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10292) ML: Replace IGFS by model storage for TensorFlow
Anton Dmitriev created IGNITE-10292: --- Summary: ML: Replace IGFS by model storage for TensorFlow Key: IGNITE-10292 URL: https://issues.apache.org/jira/browse/IGNITE-10292 Project: Ignite Issue Type: Improvement Components: ml Affects Versions: 2.8 Reporter: Anton Dmitriev Fix For: 2.8 Currently we have a TensorFlow IGFS plugin that provides a file system functionality (see https://github.com/tensorflow/tensorflow/tree/master/tensorflow/contrib/ignite). At the same time IGFS is deprecated and would be great to replace it by a simple model storage based on cache. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-6195) SQL: Do not allow JOINs on caches with different affinity functions
[
https://issues.apache.org/jira/browse/IGNITE-6195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-6195:
Labels: iep-24 sql-stability usability (was: sql-stability usability)
> SQL: Do not allow JOINs on caches with different affinity functions
> ---
>
> Key: IGNITE-6195
> URL: https://issues.apache.org/jira/browse/IGNITE-6195
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.1
>Reporter: Vladimir Ozerov
>Priority: Major
> Labels: iep-24, sql-stability, usability
> Fix For: 2.8
>
> Attachments: patch6195.patch
>
>
> Currently it is possible to execute JOIN on non-colocated caches. No
> exceptions will appear, user just receive incorrect result. We need to detect
> such situations and throw errors instead.
> *Proposed solution*
> Correct SQL result is possible when either distributed joins are enabled, or
> data is co-located properly. Under *proper* co-location we mean:
> 1) Participating {{PARTITIONED}} caches use the same affinity function
> 2) This affinity function doesn't depend on it's own previous state, i.e. it
> doesn't rely on {{AffinityFunctionContext.previousAssignment}}. For instance,
> {{RendezvousAffinityFunction}} doesn't use, while {{FairAffinityFunction}}
> does.
> As such, the following procedure should be implemented in order to determine
> whether SQL can be executed:
> 1) If {{distributedJoins}} are enabled - return, SQL can be executed
> 2) Get the list of participating caches
> 3) Exclude {{REPLICATED}} caches from that list
> 4) If all remaining caches belong to the same cache group - return, SQL can
> be executed
> 5) Get affinity function of the first cache
> 6) Check if affinity function doesn't use
> {{AffinityFunctionContext.previousAssignment}}. This could be controlled
> either through annotation, or through new method on {{AffinityFunction}}
> interface, e.g. {{boolean isDependOnPreviousState}}. If {{false}} - throw an
> exception
> 7) Check if affinity functions of all caches are equal through standard
> {{equals()}} method. If {{false}} - throw an exception.
> 8) Otherwise - SQL can be executed safely.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-6195) SQL: Do not allow JOINs on caches with different affinity functions
[
https://issues.apache.org/jira/browse/IGNITE-6195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov reassigned IGNITE-6195:
---
Assignee: (was: Sergey Grimstad)
> SQL: Do not allow JOINs on caches with different affinity functions
> ---
>
> Key: IGNITE-6195
> URL: https://issues.apache.org/jira/browse/IGNITE-6195
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.1
>Reporter: Vladimir Ozerov
>Priority: Major
> Labels: iep-24, sql-stability, usability
> Fix For: 2.8
>
> Attachments: patch6195.patch
>
>
> Currently it is possible to execute JOIN on non-colocated caches. No
> exceptions will appear, user just receive incorrect result. We need to detect
> such situations and throw errors instead.
> *Proposed solution*
> Correct SQL result is possible when either distributed joins are enabled, or
> data is co-located properly. Under *proper* co-location we mean:
> 1) Participating {{PARTITIONED}} caches use the same affinity function
> 2) This affinity function doesn't depend on it's own previous state, i.e. it
> doesn't rely on {{AffinityFunctionContext.previousAssignment}}. For instance,
> {{RendezvousAffinityFunction}} doesn't use, while {{FairAffinityFunction}}
> does.
> As such, the following procedure should be implemented in order to determine
> whether SQL can be executed:
> 1) If {{distributedJoins}} are enabled - return, SQL can be executed
> 2) Get the list of participating caches
> 3) Exclude {{REPLICATED}} caches from that list
> 4) If all remaining caches belong to the same cache group - return, SQL can
> be executed
> 5) Get affinity function of the first cache
> 6) Check if affinity function doesn't use
> {{AffinityFunctionContext.previousAssignment}}. This could be controlled
> either through annotation, or through new method on {{AffinityFunction}}
> interface, e.g. {{boolean isDependOnPreviousState}}. If {{false}} - throw an
> exception
> 7) Check if affinity functions of all caches are equal through standard
> {{equals()}} method. If {{false}} - throw an exception.
> 8) Otherwise - SQL can be executed safely.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9312) Remove unnecessary @SuppressWarnings annotation
[
https://issues.apache.org/jira/browse/IGNITE-9312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689179#comment-16689179
]
PetrovMikhail commented on IGNITE-9312:
---
{panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Queries 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2209567]]
* IgniteBinaryCacheQueryTestSuite2:
DynamicColumnsConcurrentTransactionalPartitionedSelfTest.testDropColumnCoordinatorChange
- 3,1% fails in last 100 master runs.
{color:#d04437}Client Nodes{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2209542]]
* IgniteClientNodesTestSuite:
IgniteClientReconnectCacheTest.testReconnectOperationInProgress - 0,0% fails in
last 100 master runs.
{color:#d04437}Continuous Query 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2209547]]
* IgniteCacheQuerySelfTestSuite3:
CacheContinuousQueryOrderingEventTest.testAtomicOnheapTwoBackupAsyncFullSync -
0,0% fails in last 100 master runs.
{color:#d04437}SPI{color} [[tests
6|https://ci.ignite.apache.org/viewLog.html?buildId=2209572]]
* IgniteSpiTestSuite: TcpDiscoveryWithWrongServerTest.testDisconnectOnRequest -
2,1% fails in last 100 master runs.
* IgniteSpiTestSuite:
TcpDiscoveryWithWrongServerTest.testWrongHandshakeResponse - 2,1% fails in last
100 master runs.
* IgniteSpiTestSuite: TcpDiscoveryWithWrongServerTest.testEarlyDisconnect -
2,1% fails in last 100 master runs.
* IgniteSpiTestSuite: TcpDiscoveryWithWrongServerTest.testNoHandshakeResponse -
2,1% fails in last 100 master runs.
{color:#d04437}Platform .NET{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=2209633]]
* exe: ClientConnectionTest.TestServerConnectionAborted - 3,0% fails in last
100 master runs.
* exe: ServicesTest.TestWithKeepBinaryClient - 0,0% fails in last 100 master
runs.
{color:#d04437}PDS 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2209630]]
* IgnitePdsTestSuite2:
IgniteAbsentEvictionNodeOutOfBaselineTest.testPartitionsRemovedIfJoiningNodeNotInBaseline
- 0,0% fails in last 100 master runs.
{color:#d04437}Cache (Failover) 3{color} [[tests
11|https://ci.ignite.apache.org/viewLog.html?buildId=2209600]]
* IgniteCacheFailoverTestSuite3: IgniteCachePutRetryAtomicSelfTest.testPutAsync
- 0,0% fails in last 100 master runs.
* IgniteCacheFailoverTestSuite3:
IgniteCachePutRetryAtomicSelfTest.testPutAsyncStoreEnabled - 0,0% fails in last
100 master runs.
{panel}
[TeamCity Run All
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2209645&buildTypeId=IgniteTests24Java8_RunAll]
> Remove unnecessary @SuppressWarnings annotation
> ---
>
> Key: IGNITE-9312
> URL: https://issues.apache.org/jira/browse/IGNITE-9312
> Project: Ignite
> Issue Type: Bug
>Reporter: Maxim Muzafarov
>Assignee: PetrovMikhail
>Priority: Minor
> Labels: inspections
> Fix For: 2.8
>
>
> New `Code Inspections` profile can be found
> \idea\ignite_inspections.xml.
> We will need to fix all methods with unnecessary {{@SuppressWarnings}}
> annotation regarding this inscpetion profile.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10293) VisorNodeDataCollectorJob should not collect caches info on inactive cluster
Alexey Kuznetsov created IGNITE-10293: - Summary: VisorNodeDataCollectorJob should not collect caches info on inactive cluster Key: IGNITE-10293 URL: https://issues.apache.org/jira/browse/IGNITE-10293 Project: Ignite Issue Type: Task Components: wizards Reporter: Alexey Kuznetsov Assignee: Alexey Kuznetsov Fix For: 2.8 When cluster is inactive, caches not available, so - no need to try to collect info. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-10233) GridAffinityAssignmentCache#cachedAffinity() should not check topology version in assertion, if cluster not activated.
[
https://issues.apache.org/jira/browse/IGNITE-10233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Antonov resolved IGNITE-10233.
-
Resolution: Won't Fix
> GridAffinityAssignmentCache#cachedAffinity() should not check topology
> version in assertion, if cluster not activated.
> ---
>
> Key: IGNITE-10233
> URL: https://issues.apache.org/jira/browse/IGNITE-10233
> Project: Ignite
> Issue Type: Bug
>Reporter: Sergey Antonov
>Assignee: Sergey Antonov
>Priority: Major
> Fix For: 2.8
>
>
> If cluster not activated we should not check this assertion.
> {code:java}
> assert topVer.topologyVersion() >= 0 : topVer;
> {code}
> It's needed for our proprietary plugin.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (IGNITE-10233) GridAffinityAssignmentCache#cachedAffinity() should not check topology version in assertion, if cluster not activated.
[
https://issues.apache.org/jira/browse/IGNITE-10233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Antonov closed IGNITE-10233.
---
Ignite Flags: (was: Docs Required)
> GridAffinityAssignmentCache#cachedAffinity() should not check topology
> version in assertion, if cluster not activated.
> ---
>
> Key: IGNITE-10233
> URL: https://issues.apache.org/jira/browse/IGNITE-10233
> Project: Ignite
> Issue Type: Bug
>Reporter: Sergey Antonov
>Assignee: Sergey Antonov
>Priority: Major
> Fix For: 2.8
>
>
> If cluster not activated we should not check this assertion.
> {code:java}
> assert topVer.topologyVersion() >= 0 : topVer;
> {code}
> It's needed for our proprietary plugin.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (IGNITE-10293) VisorNodeDataCollectorJob should not collect caches info on inactive cluster
[ https://issues.apache.org/jira/browse/IGNITE-10293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-10293. - > VisorNodeDataCollectorJob should not collect caches info on inactive cluster > > > Key: IGNITE-10293 > URL: https://issues.apache.org/jira/browse/IGNITE-10293 > Project: Ignite > Issue Type: Task > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.8 > > > When cluster is inactive, caches not available, so - no need to try to > collect info. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9312) Remove unnecessary @SuppressWarnings annotation
[
https://issues.apache.org/jira/browse/IGNITE-9312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689191#comment-16689191
]
PetrovMikhail commented on IGNITE-9312:
---
{panel:title=No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity Run All
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2209589&buildTypeId=IgniteTests24Java8_MvccCache_2]
> Remove unnecessary @SuppressWarnings annotation
> ---
>
> Key: IGNITE-9312
> URL: https://issues.apache.org/jira/browse/IGNITE-9312
> Project: Ignite
> Issue Type: Bug
>Reporter: Maxim Muzafarov
>Assignee: PetrovMikhail
>Priority: Minor
> Labels: inspections
> Fix For: 2.8
>
>
> New `Code Inspections` profile can be found
> \idea\ignite_inspections.xml.
> We will need to fix all methods with unnecessary {{@SuppressWarnings}}
> annotation regarding this inscpetion profile.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (IGNITE-9312) Remove unnecessary @SuppressWarnings annotation
[
https://issues.apache.org/jira/browse/IGNITE-9312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
PetrovMikhail updated IGNITE-9312:
--
Comment: was deleted
(was: {panel:title=No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity Run All
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2209589&buildTypeId=IgniteTests24Java8_MvccCache_2])
> Remove unnecessary @SuppressWarnings annotation
> ---
>
> Key: IGNITE-9312
> URL: https://issues.apache.org/jira/browse/IGNITE-9312
> Project: Ignite
> Issue Type: Bug
>Reporter: Maxim Muzafarov
>Assignee: PetrovMikhail
>Priority: Minor
> Labels: inspections
> Fix For: 2.8
>
>
> New `Code Inspections` profile can be found
> \idea\ignite_inspections.xml.
> We will need to fix all methods with unnecessary {{@SuppressWarnings}}
> annotation regarding this inscpetion profile.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (IGNITE-9312) Remove unnecessary @SuppressWarnings annotation
[
https://issues.apache.org/jira/browse/IGNITE-9312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
PetrovMikhail updated IGNITE-9312:
--
Comment: was deleted
(was: {panel:title=No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity Run All
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2209589&buildTypeId=IgniteTests24Java8_MvccCache_2])
> Remove unnecessary @SuppressWarnings annotation
> ---
>
> Key: IGNITE-9312
> URL: https://issues.apache.org/jira/browse/IGNITE-9312
> Project: Ignite
> Issue Type: Bug
>Reporter: Maxim Muzafarov
>Assignee: PetrovMikhail
>Priority: Minor
> Labels: inspections
> Fix For: 2.8
>
>
> New `Code Inspections` profile can be found
> \idea\ignite_inspections.xml.
> We will need to fix all methods with unnecessary {{@SuppressWarnings}}
> annotation regarding this inscpetion profile.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (IGNITE-9312) Remove unnecessary @SuppressWarnings annotation
[
https://issues.apache.org/jira/browse/IGNITE-9312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
PetrovMikhail updated IGNITE-9312:
--
Comment: was deleted
(was: {panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Queries 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2209567]]
* IgniteBinaryCacheQueryTestSuite2:
DynamicColumnsConcurrentTransactionalPartitionedSelfTest.testDropColumnCoordinatorChange
- 3,1% fails in last 100 master runs.
{color:#d04437}Client Nodes{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2209542]]
* IgniteClientNodesTestSuite:
IgniteClientReconnectCacheTest.testReconnectOperationInProgress - 0,0% fails in
last 100 master runs.
{color:#d04437}Continuous Query 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2209547]]
* IgniteCacheQuerySelfTestSuite3:
CacheContinuousQueryOrderingEventTest.testAtomicOnheapTwoBackupAsyncFullSync -
0,0% fails in last 100 master runs.
{color:#d04437}SPI{color} [[tests
6|https://ci.ignite.apache.org/viewLog.html?buildId=2209572]]
* IgniteSpiTestSuite: TcpDiscoveryWithWrongServerTest.testDisconnectOnRequest -
2,1% fails in last 100 master runs.
* IgniteSpiTestSuite:
TcpDiscoveryWithWrongServerTest.testWrongHandshakeResponse - 2,1% fails in last
100 master runs.
* IgniteSpiTestSuite: TcpDiscoveryWithWrongServerTest.testEarlyDisconnect -
2,1% fails in last 100 master runs.
* IgniteSpiTestSuite: TcpDiscoveryWithWrongServerTest.testNoHandshakeResponse -
2,1% fails in last 100 master runs.
{color:#d04437}Platform .NET{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=2209633]]
* exe: ClientConnectionTest.TestServerConnectionAborted - 3,0% fails in last
100 master runs.
* exe: ServicesTest.TestWithKeepBinaryClient - 0,0% fails in last 100 master
runs.
{color:#d04437}PDS 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2209630]]
* IgnitePdsTestSuite2:
IgniteAbsentEvictionNodeOutOfBaselineTest.testPartitionsRemovedIfJoiningNodeNotInBaseline
- 0,0% fails in last 100 master runs.
{color:#d04437}Cache (Failover) 3{color} [[tests
11|https://ci.ignite.apache.org/viewLog.html?buildId=2209600]]
* IgniteCacheFailoverTestSuite3: IgniteCachePutRetryAtomicSelfTest.testPutAsync
- 0,0% fails in last 100 master runs.
* IgniteCacheFailoverTestSuite3:
IgniteCachePutRetryAtomicSelfTest.testPutAsyncStoreEnabled - 0,0% fails in last
100 master runs.
{panel}
[TeamCity Run All
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2209645&buildTypeId=IgniteTests24Java8_RunAll])
> Remove unnecessary @SuppressWarnings annotation
> ---
>
> Key: IGNITE-9312
> URL: https://issues.apache.org/jira/browse/IGNITE-9312
> Project: Ignite
> Issue Type: Bug
>Reporter: Maxim Muzafarov
>Assignee: PetrovMikhail
>Priority: Minor
> Labels: inspections
> Fix For: 2.8
>
>
> New `Code Inspections` profile can be found
> \idea\ignite_inspections.xml.
> We will need to fix all methods with unnecessary {{@SuppressWarnings}}
> annotation regarding this inscpetion profile.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (IGNITE-9312) Remove unnecessary @SuppressWarnings annotation
[
https://issues.apache.org/jira/browse/IGNITE-9312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
PetrovMikhail updated IGNITE-9312:
--
Comment: was deleted
(was: {panel:title=No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity Run All
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2209589&buildTypeId=IgniteTests24Java8_MvccCache_2])
> Remove unnecessary @SuppressWarnings annotation
> ---
>
> Key: IGNITE-9312
> URL: https://issues.apache.org/jira/browse/IGNITE-9312
> Project: Ignite
> Issue Type: Bug
>Reporter: Maxim Muzafarov
>Assignee: PetrovMikhail
>Priority: Minor
> Labels: inspections
> Fix For: 2.8
>
>
> New `Code Inspections` profile can be found
> \idea\ignite_inspections.xml.
> We will need to fix all methods with unnecessary {{@SuppressWarnings}}
> annotation regarding this inscpetion profile.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (IGNITE-9312) Remove unnecessary @SuppressWarnings annotation
[
https://issues.apache.org/jira/browse/IGNITE-9312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
PetrovMikhail updated IGNITE-9312:
--
Comment: was deleted
(was: {panel:title=No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity Run All
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2209589&buildTypeId=IgniteTests24Java8_MvccCache_2])
> Remove unnecessary @SuppressWarnings annotation
> ---
>
> Key: IGNITE-9312
> URL: https://issues.apache.org/jira/browse/IGNITE-9312
> Project: Ignite
> Issue Type: Bug
>Reporter: Maxim Muzafarov
>Assignee: PetrovMikhail
>Priority: Minor
> Labels: inspections
> Fix For: 2.8
>
>
> New `Code Inspections` profile can be found
> \idea\ignite_inspections.xml.
> We will need to fix all methods with unnecessary {{@SuppressWarnings}}
> annotation regarding this inscpetion profile.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9312) Remove unnecessary @SuppressWarnings annotation
[
https://issues.apache.org/jira/browse/IGNITE-9312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689206#comment-16689206
]
PetrovMikhail commented on IGNITE-9312:
---
{panel:title=No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity Run All
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2209589&buildTypeId=IgniteTests24Java8_MvccCache_2]
> Remove unnecessary @SuppressWarnings annotation
> ---
>
> Key: IGNITE-9312
> URL: https://issues.apache.org/jira/browse/IGNITE-9312
> Project: Ignite
> Issue Type: Bug
>Reporter: Maxim Muzafarov
>Assignee: PetrovMikhail
>Priority: Minor
> Labels: inspections
> Fix For: 2.8
>
>
> New `Code Inspections` profile can be found
> \idea\ignite_inspections.xml.
> We will need to fix all methods with unnecessary {{@SuppressWarnings}}
> annotation regarding this inscpetion profile.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (IGNITE-9312) Remove unnecessary @SuppressWarnings annotation
[
https://issues.apache.org/jira/browse/IGNITE-9312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
PetrovMikhail updated IGNITE-9312:
--
Comment: was deleted
(was: {panel:title=No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity Run All
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2209589&buildTypeId=IgniteTests24Java8_MvccCache_2])
> Remove unnecessary @SuppressWarnings annotation
> ---
>
> Key: IGNITE-9312
> URL: https://issues.apache.org/jira/browse/IGNITE-9312
> Project: Ignite
> Issue Type: Bug
>Reporter: Maxim Muzafarov
>Assignee: PetrovMikhail
>Priority: Minor
> Labels: inspections
> Fix For: 2.8
>
>
> New `Code Inspections` profile can be found
> \idea\ignite_inspections.xml.
> We will need to fix all methods with unnecessary {{@SuppressWarnings}}
> annotation regarding this inscpetion profile.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9312) Remove unnecessary @SuppressWarnings annotation
[
https://issues.apache.org/jira/browse/IGNITE-9312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689209#comment-16689209
]
PetrovMikhail commented on IGNITE-9312:
---
{panel:title=No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity Run All
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2209589&buildTypeId=IgniteTests24Java8_MvccCache_2]
> Remove unnecessary @SuppressWarnings annotation
> ---
>
> Key: IGNITE-9312
> URL: https://issues.apache.org/jira/browse/IGNITE-9312
> Project: Ignite
> Issue Type: Bug
>Reporter: Maxim Muzafarov
>Assignee: PetrovMikhail
>Priority: Minor
> Labels: inspections
> Fix For: 2.8
>
>
> New `Code Inspections` profile can be found
> \idea\ignite_inspections.xml.
> We will need to fix all methods with unnecessary {{@SuppressWarnings}}
> annotation regarding this inscpetion profile.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9312) Remove unnecessary @SuppressWarnings annotation
[
https://issues.apache.org/jira/browse/IGNITE-9312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689203#comment-16689203
]
PetrovMikhail commented on IGNITE-9312:
---
{panel:title=No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity Run All
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2209589&buildTypeId=IgniteTests24Java8_MvccCache_2]
> Remove unnecessary @SuppressWarnings annotation
> ---
>
> Key: IGNITE-9312
> URL: https://issues.apache.org/jira/browse/IGNITE-9312
> Project: Ignite
> Issue Type: Bug
>Reporter: Maxim Muzafarov
>Assignee: PetrovMikhail
>Priority: Minor
> Labels: inspections
> Fix For: 2.8
>
>
> New `Code Inspections` profile can be found
> \idea\ignite_inspections.xml.
> We will need to fix all methods with unnecessary {{@SuppressWarnings}}
> annotation regarding this inscpetion profile.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (IGNITE-9312) Remove unnecessary @SuppressWarnings annotation
[
https://issues.apache.org/jira/browse/IGNITE-9312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
PetrovMikhail updated IGNITE-9312:
--
Comment: was deleted
(was: {panel:title=No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity Run All
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2209589&buildTypeId=IgniteTests24Java8_MvccCache_2])
> Remove unnecessary @SuppressWarnings annotation
> ---
>
> Key: IGNITE-9312
> URL: https://issues.apache.org/jira/browse/IGNITE-9312
> Project: Ignite
> Issue Type: Bug
>Reporter: Maxim Muzafarov
>Assignee: PetrovMikhail
>Priority: Minor
> Labels: inspections
> Fix For: 2.8
>
>
> New `Code Inspections` profile can be found
> \idea\ignite_inspections.xml.
> We will need to fix all methods with unnecessary {{@SuppressWarnings}}
> annotation regarding this inscpetion profile.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (IGNITE-9312) Remove unnecessary @SuppressWarnings annotation
[
https://issues.apache.org/jira/browse/IGNITE-9312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
PetrovMikhail updated IGNITE-9312:
--
Comment: was deleted
(was: {panel:title=No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity Run All
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2209589&buildTypeId=IgniteTests24Java8_MvccCache_2])
> Remove unnecessary @SuppressWarnings annotation
> ---
>
> Key: IGNITE-9312
> URL: https://issues.apache.org/jira/browse/IGNITE-9312
> Project: Ignite
> Issue Type: Bug
>Reporter: Maxim Muzafarov
>Assignee: PetrovMikhail
>Priority: Minor
> Labels: inspections
> Fix For: 2.8
>
>
> New `Code Inspections` profile can be found
> \idea\ignite_inspections.xml.
> We will need to fix all methods with unnecessary {{@SuppressWarnings}}
> annotation regarding this inscpetion profile.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9312) Remove unnecessary @SuppressWarnings annotation
[
https://issues.apache.org/jira/browse/IGNITE-9312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689223#comment-16689223
]
PetrovMikhail commented on IGNITE-9312:
---
{panel:title=No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity Run All
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2209589&buildTypeId=IgniteTests24Java8_MvccCache_2]
> Remove unnecessary @SuppressWarnings annotation
> ---
>
> Key: IGNITE-9312
> URL: https://issues.apache.org/jira/browse/IGNITE-9312
> Project: Ignite
> Issue Type: Bug
>Reporter: Maxim Muzafarov
>Assignee: PetrovMikhail
>Priority: Minor
> Labels: inspections
> Fix For: 2.8
>
>
> New `Code Inspections` profile can be found
> \idea\ignite_inspections.xml.
> We will need to fix all methods with unnecessary {{@SuppressWarnings}}
> annotation regarding this inscpetion profile.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-10263) MVCC: Concurrent cache stop can cause vacuum failure.
[ https://issues.apache.org/jira/browse/IGNITE-10263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov reassigned IGNITE-10263: - Assignee: Andrew Mashenkov > MVCC: Concurrent cache stop can cause vacuum failure. > - > > Key: IGNITE-10263 > URL: https://issues.apache.org/jira/browse/IGNITE-10263 > Project: Ignite > Issue Type: Bug > Components: cache, mvcc >Reporter: Andrew Mashenkov >Assignee: Andrew Mashenkov >Priority: Minor > Labels: Hanging > > > Vacuum.cleanup() can fails on cctx.gate().enter() if cache is stopped > concurrently. > ctx.gate().enter() method fails with IllegalStateException and we've got > stacktrace in log for every cache partition. > Replacing enter() with enterIfNotStopped() resolves the issue. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10156) Invalid convertation DynamicCacheDescriptor to StoredCacheData
[ https://issues.apache.org/jira/browse/IGNITE-10156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Govorukhin updated IGNITE-10156: Fix Version/s: 2.8 > Invalid convertation DynamicCacheDescriptor to StoredCacheData > -- > > Key: IGNITE-10156 > URL: https://issues.apache.org/jira/browse/IGNITE-10156 > Project: Ignite > Issue Type: Bug >Reporter: Anton Kalashnikov >Assignee: Anton Kalashnikov >Priority: Major > Fix For: 2.8 > > > Invalid convertation DynamicCacheDescriptor to StoredCacheData in > CacheRegistry#persistCacheConfigurations -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10156) Invalid convertation DynamicCacheDescriptor to StoredCacheData
[ https://issues.apache.org/jira/browse/IGNITE-10156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Govorukhin updated IGNITE-10156: Ignite Flags: (was: Docs Required) > Invalid convertation DynamicCacheDescriptor to StoredCacheData > -- > > Key: IGNITE-10156 > URL: https://issues.apache.org/jira/browse/IGNITE-10156 > Project: Ignite > Issue Type: Bug >Reporter: Anton Kalashnikov >Assignee: Anton Kalashnikov >Priority: Major > Fix For: 2.8 > > > Invalid convertation DynamicCacheDescriptor to StoredCacheData in > CacheRegistry#persistCacheConfigurations -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9622) MVCC Cache API: prohibit non PESSIMISTIC REPEATABLE_READ transactions
[
https://issues.apache.org/jira/browse/IGNITE-9622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689256#comment-16689256
]
Ivan Pavlukhin commented on IGNITE-9622:
[~gvvinblade] If I get your point right it is already works in that way.
{{MvccUtils.currentTx}} throwing new exceptions is not used by SQL components
directly. SQL uses various {{MvccUtils.tx}} methods which translate exceptions
to {{IgniteSQLException}} with corresponding _status code_.
> MVCC Cache API: prohibit non PESSIMISTIC REPEATABLE_READ transactions
> -
>
> Key: IGNITE-9622
> URL: https://issues.apache.org/jira/browse/IGNITE-9622
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Ivan Pavlukhin
>Assignee: Ivan Pavlukhin
>Priority: Major
> Fix For: 2.8
>
>
> For cache with enabled mvcc we should allow running only PESSIMISTIC
> REPEATABLE_READ transactions. For other modes exception should be thrown
> (like is done for SQL API).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10294) SQL: subjectId is lost for SqlFieldsQuery event on local node
Vladimir Ozerov created IGNITE-10294:
Summary: SQL: subjectId is lost for SqlFieldsQuery event on local
node
Key: IGNITE-10294
URL: https://issues.apache.org/jira/browse/IGNITE-10294
Project: Ignite
Issue Type: Task
Components: sql
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
Fix For: 2.8
See {{GridQueryProcessor.sendQueryExecutedEvent}} - we pass {{null}} as subject
ID. Need to fix it to local node ID.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10294) SQL: subjectId is lost for SqlFieldsQuery event on local node
[
https://issues.apache.org/jira/browse/IGNITE-10294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689272#comment-16689272
]
Vladimir Ozerov commented on IGNITE-10294:
--
Fixed. Test run: https://ci.ignite.apache.org/viewQueued.html?itemId=2331885
> SQL: subjectId is lost for SqlFieldsQuery event on local node
> -
>
> Key: IGNITE-10294
> URL: https://issues.apache.org/jira/browse/IGNITE-10294
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Major
> Fix For: 2.8
>
>
> See {{GridQueryProcessor.sendQueryExecutedEvent}} - we pass {{null}} as
> subject ID. Need to fix it to local node ID.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10294) SQL: subjectId is lost for SqlFieldsQuery event on local node
[
https://issues.apache.org/jira/browse/IGNITE-10294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689271#comment-16689271
]
ASF GitHub Bot commented on IGNITE-10294:
-
GitHub user devozerov opened a pull request:
https://github.com/apache/ignite/pull/5408
IGNITE-10294
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10294
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5408.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #5408
commit 97b139ccac96b8e00f2a8ebf70279ff13248d5f5
Author: devozerov
Date: 2018-11-16T10:34:28Z
Fixed.
> SQL: subjectId is lost for SqlFieldsQuery event on local node
> -
>
> Key: IGNITE-10294
> URL: https://issues.apache.org/jira/browse/IGNITE-10294
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Major
> Fix For: 2.8
>
>
> See {{GridQueryProcessor.sendQueryExecutedEvent}} - we pass {{null}} as
> subject ID. Need to fix it to local node ID.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10167) MVCC-compatible IgniteCache.localEntries
[
https://issues.apache.org/jira/browse/IGNITE-10167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689285#comment-16689285
]
Andrew Mashenkov commented on IGNITE-10167:
---
[~Pavlukhin],
I've noticed nternal interface IgniteInternalCache.localPeek() has an
ExpiryPolicy as one of it's argument.
Public IgniteCache interface method doesn't allow to use any ExpiryPolicy and
it looks like we don't use it internally as well (neither in code nor in tests).
Let's drop dead and untested code.
> MVCC-compatible IgniteCache.localEntries
>
>
> Key: IGNITE-10167
> URL: https://issues.apache.org/jira/browse/IGNITE-10167
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Ivan Pavlukhin
>Assignee: Ivan Pavlukhin
>Priority: Major
>
> IgniteCache API method {{localEntries}} should be supported. The idea is to
> provide an entries iterator seeing latest committed versions.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-10279) Control.sh utility unify options naming format
[
https://issues.apache.org/jira/browse/IGNITE-10279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Antonov reassigned IGNITE-10279:
---
Assignee: (was: Sergey Antonov)
> Control.sh utility unify options naming format
> --
>
> Key: IGNITE-10279
> URL: https://issues.apache.org/jira/browse/IGNITE-10279
> Project: Ignite
> Issue Type: Improvement
>Reporter: Sergey Antonov
>Priority: Major
> Fix For: 2.8
>
>
> Now we have options in several styles:
> {noformat}
> --ping-interval
> {noformat}
> {noformat}
> --skipZeros
> {noformat}
> I think, we must unify options naming format and we should use linux like
> format, i.e. {{--word1-word2}}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10272) Inject learning environment into scope of dataset compute task
[ https://issues.apache.org/jira/browse/IGNITE-10272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Babak updated IGNITE-10272: Component/s: ml > Inject learning environment into scope of dataset compute task > -- > > Key: IGNITE-10272 > URL: https://issues.apache.org/jira/browse/IGNITE-10272 > Project: Ignite > Issue Type: Improvement > Components: ml >Reporter: Artem Malykh >Assignee: Artem Malykh >Priority: Major > > We want to have learing environment for each partition during training > process. We need this for several reasons. > The first one is logging training process for each partition. The second > reason is having the possibility of fixing random number generator seed for > tests and debugging(fixing subspace distribution, stable tests, etc...) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10272) Inject learning environment into scope of dataset compute task
[ https://issues.apache.org/jira/browse/IGNITE-10272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Babak updated IGNITE-10272: Description: We want to have learing environment for each partition during training process. We need this for several reasons. The first one is logging training process for each partition. The second reason is having the possibility of fixing random number generator seed for tests and debugging(fixing subspace distribution, stable tests, etc...) > Inject learning environment into scope of dataset compute task > -- > > Key: IGNITE-10272 > URL: https://issues.apache.org/jira/browse/IGNITE-10272 > Project: Ignite > Issue Type: Improvement > Components: ml >Reporter: Artem Malykh >Assignee: Artem Malykh >Priority: Major > > We want to have learing environment for each partition during training > process. We need this for several reasons. > The first one is logging training process for each partition. The second > reason is having the possibility of fixing random number generator seed for > tests and debugging(fixing subspace distribution, stable tests, etc...) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10272) [ML] Inject learning environment into scope of dataset compute task
[ https://issues.apache.org/jira/browse/IGNITE-10272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Babak updated IGNITE-10272: Summary: [ML] Inject learning environment into scope of dataset compute task (was: Inject learning environment into scope of dataset compute task) > [ML] Inject learning environment into scope of dataset compute task > --- > > Key: IGNITE-10272 > URL: https://issues.apache.org/jira/browse/IGNITE-10272 > Project: Ignite > Issue Type: Improvement > Components: ml >Reporter: Artem Malykh >Assignee: Artem Malykh >Priority: Major > > We want to have learing environment for each partition during training > process. We need this for several reasons. > The first one is logging training process for each partition. The second > reason is having the possibility of fixing random number generator seed for > tests and debugging(fixing subspace distribution, stable tests, etc...) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10238) Intermittent Client Nodes suite hang
[
https://issues.apache.org/jira/browse/IGNITE-10238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amelchev Nikita reassigned IGNITE-10238:
Assignee: Amelchev Nikita
> Intermittent Client Nodes suite hang
>
>
> Key: IGNITE-10238
> URL: https://issues.apache.org/jira/browse/IGNITE-10238
> Project: Ignite
> Issue Type: Test
>Reporter: Alexey Goncharuk
>Assignee: Amelchev Nikita
>Priority: Critical
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> There are occasional hangs of Client Nodes suite in master. A quick peek at
> the thread dumps reveals an interesting deadlock (only relevant parts of the
> thread dump are left):
> {code}
> "disco-notifier-worker-#634%internal.IgniteClientReconnectApiExceptionTest0%"
> #791 prio=5 os_prio=0 tid=0x7f990c12d800 nid=0x11b9 waiting on condition
> [0x7f991a0eb000]
>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.processors.cache.binary.CacheObjectBinaryProcessorImpl.metadata(CacheObjectBinaryProcessorImpl.java:656)
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl$1.metadata(CacheObjectBinaryProcessorImpl.java:206)
> at
> org.apache.ignite.internal.binary.BinaryContext.metadata(BinaryContext.java:1293)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.getOrCreateSchema(BinaryReaderExImpl.java:2007)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:286)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:185)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readField(BinaryReaderExImpl.java:1984)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read0(BinaryFieldAccessor.java:703)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor.read(BinaryFieldAccessor.java:188)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:874)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1764)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1716)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readField(BinaryReaderExImpl.java:1984)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read0(BinaryFieldAccessor.java:703)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor.read(BinaryFieldAccessor.java:188)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:874)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1764)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1716)
> at
> org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:313)
> at
> org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal0(BinaryMarshaller.java:101)
> at
> org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:81)
> at
> org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10131)
> at
> org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10160)
> at
> org.apache.ignite.internal.GridEventConsumeHandler.p2pUnmarshal(GridEventConsumeHandler.java:390)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processStartRequest(GridContinuousProcessor.java:1362)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$400(GridContinuousProcessor.java:111)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:203)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:194)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:725)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.lambda$onDiscovery$0(GridDiscoveryManager.java:602)
> - locked <0x0007b62859b8> (a java.lang.Object)
> at
> org.apache.i
[jira] [Commented] (IGNITE-10238) Intermittent Client Nodes suite hang
[
https://issues.apache.org/jira/browse/IGNITE-10238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689315#comment-16689315
]
Amelchev Nikita commented on IGNITE-10238:
--
This issue leads to SPI suite timeout too.
> Intermittent Client Nodes suite hang
>
>
> Key: IGNITE-10238
> URL: https://issues.apache.org/jira/browse/IGNITE-10238
> Project: Ignite
> Issue Type: Test
>Reporter: Alexey Goncharuk
>Assignee: Amelchev Nikita
>Priority: Critical
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> There are occasional hangs of Client Nodes suite in master. A quick peek at
> the thread dumps reveals an interesting deadlock (only relevant parts of the
> thread dump are left):
> {code}
> "disco-notifier-worker-#634%internal.IgniteClientReconnectApiExceptionTest0%"
> #791 prio=5 os_prio=0 tid=0x7f990c12d800 nid=0x11b9 waiting on condition
> [0x7f991a0eb000]
>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.processors.cache.binary.CacheObjectBinaryProcessorImpl.metadata(CacheObjectBinaryProcessorImpl.java:656)
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl$1.metadata(CacheObjectBinaryProcessorImpl.java:206)
> at
> org.apache.ignite.internal.binary.BinaryContext.metadata(BinaryContext.java:1293)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.getOrCreateSchema(BinaryReaderExImpl.java:2007)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:286)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:185)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readField(BinaryReaderExImpl.java:1984)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read0(BinaryFieldAccessor.java:703)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor.read(BinaryFieldAccessor.java:188)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:874)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1764)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1716)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readField(BinaryReaderExImpl.java:1984)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read0(BinaryFieldAccessor.java:703)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor.read(BinaryFieldAccessor.java:188)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:874)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1764)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1716)
> at
> org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:313)
> at
> org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal0(BinaryMarshaller.java:101)
> at
> org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:81)
> at
> org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10131)
> at
> org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10160)
> at
> org.apache.ignite.internal.GridEventConsumeHandler.p2pUnmarshal(GridEventConsumeHandler.java:390)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processStartRequest(GridContinuousProcessor.java:1362)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$400(GridContinuousProcessor.java:111)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:203)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:194)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:725)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.lambda$onDiscovery$0(GridDiscoveryManager.java:602)
> - locked <0x0
[jira] [Commented] (IGNITE-10243) [TC Bot] Support partially cancelled suites in RunAll
[
https://issues.apache.org/jira/browse/IGNITE-10243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689316#comment-16689316
]
Ignite TC Bot commented on IGNITE-10243:
{panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Queries (Binary Objects Simple Mapper){color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=2316244]]
* IgniteBinarySimpleNameMapperCacheQueryTestSuite:
IndexingCachePartitionLossPolicySelfTest.testReadWriteSafeAfterKillTwoNodesWithDelay
- 0,0% fails in last 100 master runs.
{color:#d04437}MVCC Cache{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2316252]]
* IgniteCacheMvccTestSuite:
CacheMvccPartitionedCoordinatorFailoverTest.testAccountsTxScan_Server_Backups1_CoordinatorFails_Persistence
- 1,4% fails in last 100 master runs.
{color:#d04437}SPI{color} [[tests
12|https://ci.ignite.apache.org/viewLog.html?buildId=2316267]]
* IgniteSpiTestSuite: TcpDiscoverySpiSelfTest.testNodeAttributes - 1,0% fails
in last 100 master runs.
* IgniteSpiTestSuite: TcpDiscoverySpiSelfTest.testLocalMetricsUpdate - 1,0%
fails in last 100 master runs.
* IgniteSpiTestSuite:
TcpDiscoverySpiFailureTimeoutSelfTest.testFailureDetectionTimeoutEnabled - 1,0%
fails in last 100 master runs.
* IgniteSpiTestSuite:
TcpDiscoverySpiFailureTimeoutSelfTest.testFailureDetectionOnSocketWrite - 1,0%
fails in last 100 master runs.
* IgniteSpiTestSuite:
TcpDiscoverySpiFailureTimeoutSelfTest.testConnectionCheckMessage - 1,0% fails
in last 100 master runs.
* IgniteSpiTestSuite:
TcpDiscoverySpiFailureTimeoutSelfTest.testFailureDetectionOnSocketOpen - 1,0%
fails in last 100 master runs.
* IgniteSpiTestSuite: TcpDiscoverySpiFailureTimeoutSelfTest.testNodeAttributes
- 1,0% fails in last 100 master runs.
* IgniteSpiTestSuite: TcpDiscoverySpiSelfTest.testDiscovery - 1,0% fails in
last 100 master runs.
* IgniteSpiTestSuite: TcpDiscoverySpiConfigSelfTest.testLocalPortRange - 0,0%
fails in last 100 master runs.
{color:#d04437}Cache (Full API){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2316355]]
* IgniteCacheFullApiSelfTestSuite:
GridCacheLocalWithGroupFullApiSelfTest.testTtlTx - 0,0% fails in last 100
master runs.
{color:#d04437}JDBC Driver{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2316273]]
*
JdbcThinTransactionsServerAutoCommitComplexSelfTest.testRepeatableReadWithConcurrentCacheReplace
(last started)
{panel}
[TeamCity Run All
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2312157&buildTypeId=IgniteTests24Java8_RunAll]
> [TC Bot] Support partially cancelled suites in RunAll
> -
>
> Key: IGNITE-10243
> URL: https://issues.apache.org/jira/browse/IGNITE-10243
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
>
> For case, there is no TC run (RunAll) for the branch with normal status we
> can check if there are any with canceled status.
> If canceled status (unknown) appeared on the latest build in suite's rebuilds
> sequence, we can use the latest build successful.
> If there is only one build in rebuilds sequence and it was canceled => use
> this one as a possible blocker for PR report.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10263) MVCC: Concurrent cache stop can cause vacuum failure.
[ https://issues.apache.org/jira/browse/IGNITE-10263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689331#comment-16689331 ] ASF GitHub Bot commented on IGNITE-10263: - GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/5409 IGNITE-10263: MVCC: Concurrent cache stop can cause vacuum failure. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10263 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5409.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5409 commit eb2033ba67b69565c80edfb26e26ef3ba1825f20 Author: Andrey V. Mashenkov Date: 2018-11-16T10:14:00Z IGNITE-10263: Skip entry belonged to stopped cache. commit 7f671f33a146335a7a77a2f153cd5741fb0eac81 Author: Andrey V. Mashenkov Date: 2018-11-16T10:14:00Z IGNITE-10263: Skip entry belonged to stopped cache. commit 408e9c788fe97e02f1a44bdd68d908fe6423d0b9 Author: Andrey V. Mashenkov Date: 2018-11-16T10:26:19Z Merge remote-tracking branch 'origin/ignite-10263' into ignite-10263 > MVCC: Concurrent cache stop can cause vacuum failure. > - > > Key: IGNITE-10263 > URL: https://issues.apache.org/jira/browse/IGNITE-10263 > Project: Ignite > Issue Type: Bug > Components: cache, mvcc >Reporter: Andrew Mashenkov >Assignee: Andrew Mashenkov >Priority: Minor > Labels: Hanging > > > Vacuum.cleanup() can fails on cctx.gate().enter() if cache is stopped > concurrently. > ctx.gate().enter() method fails with IllegalStateException and we've got > stacktrace in log for every cache partition. > Replacing enter() with enterIfNotStopped() resolves the issue. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10243) [TC Bot] Support partially cancelled suites in RunAll
[
https://issues.apache.org/jira/browse/IGNITE-10243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689335#comment-16689335
]
Ignite TC Bot commented on IGNITE-10243:
{panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Queries (Binary Objects Simple Mapper){color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=2316244]]
* IgniteBinarySimpleNameMapperCacheQueryTestSuite:
IndexingCachePartitionLossPolicySelfTest.testReadWriteSafeAfterKillTwoNodesWithDelay
- 0,0% fails in last 100 master runs.
{color:#d04437}MVCC Cache{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2316252]]
* IgniteCacheMvccTestSuite:
CacheMvccPartitionedCoordinatorFailoverTest.testAccountsTxScan_Server_Backups1_CoordinatorFails_Persistence
- 1,4% fails in last 100 master runs.
{color:#d04437}SPI{color} [[tests
12|https://ci.ignite.apache.org/viewLog.html?buildId=2316267]]
* IgniteSpiTestSuite: TcpDiscoverySpiSelfTest.testNodeAttributes - 1,0% fails
in last 100 master runs.
* IgniteSpiTestSuite: TcpDiscoverySpiSelfTest.testLocalMetricsUpdate - 1,0%
fails in last 100 master runs.
* IgniteSpiTestSuite:
TcpDiscoverySpiFailureTimeoutSelfTest.testFailureDetectionTimeoutEnabled - 1,0%
fails in last 100 master runs.
* IgniteSpiTestSuite:
TcpDiscoverySpiFailureTimeoutSelfTest.testFailureDetectionOnSocketWrite - 1,0%
fails in last 100 master runs.
* IgniteSpiTestSuite:
TcpDiscoverySpiFailureTimeoutSelfTest.testConnectionCheckMessage - 1,0% fails
in last 100 master runs.
* IgniteSpiTestSuite:
TcpDiscoverySpiFailureTimeoutSelfTest.testFailureDetectionOnSocketOpen - 1,0%
fails in last 100 master runs.
* IgniteSpiTestSuite: TcpDiscoverySpiFailureTimeoutSelfTest.testNodeAttributes
- 1,0% fails in last 100 master runs.
* IgniteSpiTestSuite: TcpDiscoverySpiSelfTest.testDiscovery - 1,0% fails in
last 100 master runs.
* IgniteSpiTestSuite: TcpDiscoverySpiConfigSelfTest.testLocalPortRange - 0,0%
fails in last 100 master runs.
{color:#d04437}Cache (Full API){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2316355]]
* IgniteCacheFullApiSelfTestSuite:
GridCacheLocalWithGroupFullApiSelfTest.testTtlTx - 0,0% fails in last 100
master runs.
{color:#d04437}Cache 5{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=2312122]]
{color:#d04437}JDBC Driver{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2316273]]
*
JdbcThinTransactionsServerAutoCommitComplexSelfTest.testRepeatableReadWithConcurrentCacheReplace
(last started)
{panel}
[TeamCity Run All
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2312157&buildTypeId=IgniteTests24Java8_RunAll]
> [TC Bot] Support partially cancelled suites in RunAll
> -
>
> Key: IGNITE-10243
> URL: https://issues.apache.org/jira/browse/IGNITE-10243
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
>
> For case, there is no TC run (RunAll) for the branch with normal status we
> can check if there are any with canceled status.
> If canceled status (unknown) appeared on the latest build in suite's rebuilds
> sequence, we can use the latest build successful.
> If there is only one build in rebuilds sequence and it was canceled => use
> this one as a possible blocker for PR report.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9999) Add verbose logging for node recovery
[
https://issues.apache.org/jira/browse/IGNITE-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689348#comment-16689348
]
Ignite TC Bot commented on IGNITE-:
---
{panel:title=No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity Run All
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2325806&buildTypeId=IgniteTests24Java8_RunAll]
> Add verbose logging for node recovery
> -
>
> Key: IGNITE-
> URL: https://issues.apache.org/jira/browse/IGNITE-
> Project: Ignite
> Issue Type: Task
>Reporter: Alexey Goncharuk
>Assignee: Pavel Kovalenko
>Priority: Major
>
> Sometimes we see some difficulties in understanding which state a node is
> after a binary recovery and what state it has after applying all logical
> records from WAL.
> We need to add more information on the state of partitions (update counter,
> size, maybe more additional info) after the binary recovery (can be validated
> against checkpoint records) and after logical recovery (can help to validate
> the correctness of rebalance).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10226) Partition may restore wrong MOVING state during crash recovery
[
https://issues.apache.org/jira/browse/IGNITE-10226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689347#comment-16689347
]
Ignite TC Bot commented on IGNITE-10226:
{panel:title=No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity Run All
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2325921&buildTypeId=IgniteTests24Java8_RunAll]
> Partition may restore wrong MOVING state during crash recovery
> --
>
> Key: IGNITE-10226
> URL: https://issues.apache.org/jira/browse/IGNITE-10226
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.4
>Reporter: Pavel Kovalenko
>Priority: Major
> Fix For: 2.8
>
>
> The way to get it exists only in versions that don't have IGNITE-9420:
> 1) Start cache, upload some data to partitions, forceCheckpoint
> 2) Start uploading additional data. Kill node. Node should be killed with
> skipping last checkpoint, or during checkpoint mark phase.
> 3) Re-start node. The crash recovery process for partitions started. When we
> create partition during crash recovery (topology().forceCreatePartition()) we
> log it's initial state to WAL. If we have any logical update relates to
> partition we'll log wrong MOVING state to the end of current WAL. This state
> will be considered as last valid when we process PartitionMetaStateRecord
> record's during logical recovery. In "restorePartitionsState" phase this
> state will be chosen as final and the partition will change to MOVING, even
> in page memory it has OWNING or something else.
> To fix this problem in 2.4 - 2.7 versions, additional logging partition state
> change to WAL during crash recovery (logical recovery) should be removed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10273) CPP Thin: Client is unable to get affinity mapping in some cases
[
https://issues.apache.org/jira/browse/IGNITE-10273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689360#comment-16689360
]
Alexey Goncharuk commented on IGNITE-10273:
---
[~isapego], looks good.
> CPP Thin: Client is unable to get affinity mapping in some cases
>
>
> Key: IGNITE-10273
> URL: https://issues.apache.org/jira/browse/IGNITE-10273
> Project: Ignite
> Issue Type: Bug
> Components: thin client
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>Priority: Major
> Labels: cpp
> Fix For: 2.8
>
>
> Reproducer test:
> {code:cpp}
> BOOST_AUTO_TEST_CASE(CacheClientDefaultDynamicCacheThreeNodes)
> {
> StartNode("node1");
> StartNode("node2");
> IgniteClientConfiguration cfg;
> cfg.SetEndPoints("127.0.0.1:0..11120");
> IgniteClient client = IgniteClient::Start(cfg);
> cache::CacheClient cache =
> client.CreateCache("defaultdynamic3");
> cache.RefreshAffinityMapping();
> for (int64_t i = 1; i < 1000; ++i)
> cache.Put(ignite::common::LexicalCast(i * 39916801), i *
> 5039);
> for (int64_t i = 1; i < 1000; ++i)
> {
> int64_t val;
> LocalPeek(cache, ignite::common::LexicalCast(i *
> 39916801), val);
> BOOST_CHECK_EQUAL(val, i * 5039);
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10273) CPP Thin: Client is unable to get affinity mapping in some cases
[
https://issues.apache.org/jira/browse/IGNITE-10273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689363#comment-16689363
]
Igor Sapego commented on IGNITE-10273:
--
Thanks. Tests pass:
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&branch_IgniteTests24Java8=pull%2F5399%2Fhead
Merging to master.
> CPP Thin: Client is unable to get affinity mapping in some cases
>
>
> Key: IGNITE-10273
> URL: https://issues.apache.org/jira/browse/IGNITE-10273
> Project: Ignite
> Issue Type: Bug
> Components: thin client
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>Priority: Major
> Labels: cpp
> Fix For: 2.8
>
>
> Reproducer test:
> {code:cpp}
> BOOST_AUTO_TEST_CASE(CacheClientDefaultDynamicCacheThreeNodes)
> {
> StartNode("node1");
> StartNode("node2");
> IgniteClientConfiguration cfg;
> cfg.SetEndPoints("127.0.0.1:0..11120");
> IgniteClient client = IgniteClient::Start(cfg);
> cache::CacheClient cache =
> client.CreateCache("defaultdynamic3");
> cache.RefreshAffinityMapping();
> for (int64_t i = 1; i < 1000; ++i)
> cache.Put(ignite::common::LexicalCast(i * 39916801), i *
> 5039);
> for (int64_t i = 1; i < 1000; ++i)
> {
> int64_t val;
> LocalPeek(cache, ignite::common::LexicalCast(i *
> 39916801), val);
> BOOST_CHECK_EQUAL(val, i * 5039);
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9999) Add verbose logging for node recovery
[ https://issues.apache.org/jira/browse/IGNITE-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Kovalenko updated IGNITE-: Affects Version/s: 2.8 > Add verbose logging for node recovery > - > > Key: IGNITE- > URL: https://issues.apache.org/jira/browse/IGNITE- > Project: Ignite > Issue Type: Task >Affects Versions: 2.8 >Reporter: Alexey Goncharuk >Assignee: Pavel Kovalenko >Priority: Major > Fix For: 2.8 > > > Sometimes we see some difficulties in understanding which state a node is > after a binary recovery and what state it has after applying all logical > records from WAL. > We need to add more information on the state of partitions (update counter, > size, maybe more additional info) after the binary recovery (can be validated > against checkpoint records) and after logical recovery (can help to validate > the correctness of rebalance). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9999) Add verbose logging for node recovery
[ https://issues.apache.org/jira/browse/IGNITE-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Kovalenko updated IGNITE-: Fix Version/s: 2.8 > Add verbose logging for node recovery > - > > Key: IGNITE- > URL: https://issues.apache.org/jira/browse/IGNITE- > Project: Ignite > Issue Type: Task >Affects Versions: 2.8 >Reporter: Alexey Goncharuk >Assignee: Pavel Kovalenko >Priority: Major > Fix For: 2.8 > > > Sometimes we see some difficulties in understanding which state a node is > after a binary recovery and what state it has after applying all logical > records from WAL. > We need to add more information on the state of partitions (update counter, > size, maybe more additional info) after the binary recovery (can be validated > against checkpoint records) and after logical recovery (can help to validate > the correctness of rebalance). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10273) Thin client is unable to get affinity mapping in some cases
[
https://issues.apache.org/jira/browse/IGNITE-10273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego updated IGNITE-10273:
-
Summary: Thin client is unable to get affinity mapping in some cases (was:
CPP Thin: Client is unable to get affinity mapping in some cases)
> Thin client is unable to get affinity mapping in some cases
> ---
>
> Key: IGNITE-10273
> URL: https://issues.apache.org/jira/browse/IGNITE-10273
> Project: Ignite
> Issue Type: Bug
> Components: thin client
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>Priority: Major
> Labels: cpp
> Fix For: 2.8
>
>
> Reproducer test:
> {code:cpp}
> BOOST_AUTO_TEST_CASE(CacheClientDefaultDynamicCacheThreeNodes)
> {
> StartNode("node1");
> StartNode("node2");
> IgniteClientConfiguration cfg;
> cfg.SetEndPoints("127.0.0.1:0..11120");
> IgniteClient client = IgniteClient::Start(cfg);
> cache::CacheClient cache =
> client.CreateCache("defaultdynamic3");
> cache.RefreshAffinityMapping();
> for (int64_t i = 1; i < 1000; ++i)
> cache.Put(ignite::common::LexicalCast(i * 39916801), i *
> 5039);
> for (int64_t i = 1; i < 1000; ++i)
> {
> int64_t val;
> LocalPeek(cache, ignite::common::LexicalCast(i *
> 39916801), val);
> BOOST_CHECK_EQUAL(val, i * 5039);
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10273) Thin client is unable to get affinity mapping in some cases
[
https://issues.apache.org/jira/browse/IGNITE-10273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego updated IGNITE-10273:
-
Description:
Reproducer test for C++:
{code:cpp}
BOOST_AUTO_TEST_CASE(CacheClientDefaultDynamicCacheThreeNodes)
{
StartNode("node1");
StartNode("node2");
IgniteClientConfiguration cfg;
cfg.SetEndPoints("127.0.0.1:0..11120");
IgniteClient client = IgniteClient::Start(cfg);
cache::CacheClient cache =
client.CreateCache("defaultdynamic3");
cache.RefreshAffinityMapping();
for (int64_t i = 1; i < 1000; ++i)
cache.Put(ignite::common::LexicalCast(i * 39916801), i *
5039);
for (int64_t i = 1; i < 1000; ++i)
{
int64_t val;
LocalPeek(cache, ignite::common::LexicalCast(i *
39916801), val);
BOOST_CHECK_EQUAL(val, i * 5039);
}
}
{code}
was:
Reproducer test:
{code:cpp}
BOOST_AUTO_TEST_CASE(CacheClientDefaultDynamicCacheThreeNodes)
{
StartNode("node1");
StartNode("node2");
IgniteClientConfiguration cfg;
cfg.SetEndPoints("127.0.0.1:0..11120");
IgniteClient client = IgniteClient::Start(cfg);
cache::CacheClient cache =
client.CreateCache("defaultdynamic3");
cache.RefreshAffinityMapping();
for (int64_t i = 1; i < 1000; ++i)
cache.Put(ignite::common::LexicalCast(i * 39916801), i *
5039);
for (int64_t i = 1; i < 1000; ++i)
{
int64_t val;
LocalPeek(cache, ignite::common::LexicalCast(i *
39916801), val);
BOOST_CHECK_EQUAL(val, i * 5039);
}
}
{code}
> Thin client is unable to get affinity mapping in some cases
> ---
>
> Key: IGNITE-10273
> URL: https://issues.apache.org/jira/browse/IGNITE-10273
> Project: Ignite
> Issue Type: Bug
> Components: thin client
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>Priority: Major
> Labels: cpp
> Fix For: 2.8
>
>
> Reproducer test for C++:
> {code:cpp}
> BOOST_AUTO_TEST_CASE(CacheClientDefaultDynamicCacheThreeNodes)
> {
> StartNode("node1");
> StartNode("node2");
> IgniteClientConfiguration cfg;
> cfg.SetEndPoints("127.0.0.1:0..11120");
> IgniteClient client = IgniteClient::Start(cfg);
> cache::CacheClient cache =
> client.CreateCache("defaultdynamic3");
> cache.RefreshAffinityMapping();
> for (int64_t i = 1; i < 1000; ++i)
> cache.Put(ignite::common::LexicalCast(i * 39916801), i *
> 5039);
> for (int64_t i = 1; i < 1000; ++i)
> {
> int64_t val;
> LocalPeek(cache, ignite::common::LexicalCast(i *
> 39916801), val);
> BOOST_CHECK_EQUAL(val, i * 5039);
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-10226) Partition may restore wrong MOVING state during crash recovery
[ https://issues.apache.org/jira/browse/IGNITE-10226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Kovalenko reassigned IGNITE-10226: Assignee: Pavel Kovalenko > Partition may restore wrong MOVING state during crash recovery > -- > > Key: IGNITE-10226 > URL: https://issues.apache.org/jira/browse/IGNITE-10226 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.4 >Reporter: Pavel Kovalenko >Assignee: Pavel Kovalenko >Priority: Major > Fix For: 2.8 > > > The way to get it exists only in versions that don't have IGNITE-9420: > 1) Start cache, upload some data to partitions, forceCheckpoint > 2) Start uploading additional data. Kill node. Node should be killed with > skipping last checkpoint, or during checkpoint mark phase. > 3) Re-start node. The crash recovery process for partitions started. When we > create partition during crash recovery (topology().forceCreatePartition()) we > log it's initial state to WAL. If we have any logical update relates to > partition we'll log wrong MOVING state to the end of current WAL. This state > will be considered as last valid when we process PartitionMetaStateRecord > record's during logical recovery. In "restorePartitionsState" phase this > state will be chosen as final and the partition will change to MOVING, even > in page memory it has OWNING or something else. > To fix this problem in 2.4 - 2.7 versions, additional logging partition state > change to WAL during crash recovery (logical recovery) should be removed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10144) Optimize bagging upstream transformer
[ https://issues.apache.org/jira/browse/IGNITE-10144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Babak updated IGNITE-10144: Fix Version/s: 2.8 > Optimize bagging upstream transformer > - > > Key: IGNITE-10144 > URL: https://issues.apache.org/jira/browse/IGNITE-10144 > Project: Ignite > Issue Type: Improvement > Components: ml >Reporter: Artem Malykh >Priority: Minor > Fix For: 2.8 > > > For now BaggingUpstreamTransformer makes upstream sequential to make > transformation deterministic. Maybe we should do it other way, for example > use mapping of the form (entryIdx, en) -> Stream.generate(() -> en).limit(new > PoissonDistribution(Well19937c(entryIdx + seed), ...).sample()) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10273) Thin client is unable to get affinity mapping in some cases
[
https://issues.apache.org/jira/browse/IGNITE-10273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689377#comment-16689377
]
ASF GitHub Bot commented on IGNITE-10273:
-
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5399
> Thin client is unable to get affinity mapping in some cases
> ---
>
> Key: IGNITE-10273
> URL: https://issues.apache.org/jira/browse/IGNITE-10273
> Project: Ignite
> Issue Type: Bug
> Components: thin client
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>Priority: Major
> Labels: cpp
> Fix For: 2.8
>
>
> Reproducer test for C++:
> {code:cpp}
> BOOST_AUTO_TEST_CASE(CacheClientDefaultDynamicCacheThreeNodes)
> {
> StartNode("node1");
> StartNode("node2");
> IgniteClientConfiguration cfg;
> cfg.SetEndPoints("127.0.0.1:0..11120");
> IgniteClient client = IgniteClient::Start(cfg);
> cache::CacheClient cache =
> client.CreateCache("defaultdynamic3");
> cache.RefreshAffinityMapping();
> for (int64_t i = 1; i < 1000; ++i)
> cache.Put(ignite::common::LexicalCast(i * 39916801), i *
> 5039);
> for (int64_t i = 1; i < 1000; ++i)
> {
> int64_t val;
> LocalPeek(cache, ignite::common::LexicalCast(i *
> 39916801), val);
> BOOST_CHECK_EQUAL(val, i * 5039);
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10272) [ML] Inject learning environment into scope of dataset compute task
[ https://issues.apache.org/jira/browse/IGNITE-10272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Babak updated IGNITE-10272: Fix Version/s: 2.8 > [ML] Inject learning environment into scope of dataset compute task > --- > > Key: IGNITE-10272 > URL: https://issues.apache.org/jira/browse/IGNITE-10272 > Project: Ignite > Issue Type: Improvement > Components: ml >Reporter: Artem Malykh >Assignee: Artem Malykh >Priority: Major > Fix For: 2.8 > > > We want to have learing environment for each partition during training > process. We need this for several reasons. > The first one is logging training process for each partition. The second > reason is having the possibility of fixing random number generator seed for > tests and debugging(fixing subspace distribution, stable tests, etc...) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (IGNITE-9312) Remove unnecessary @SuppressWarnings annotation
[
https://issues.apache.org/jira/browse/IGNITE-9312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
PetrovMikhail updated IGNITE-9312:
--
Comment: was deleted
(was: {panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Queries (Binary Objects Simple Mapper){color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=2209639]]
* IgniteBinarySimpleNameMapperCacheQueryTestSuite:
IgniteClientReconnectCacheQueriesFailoverTest.testReconnectCacheQueries
* IgniteBinarySimpleNameMapperCacheQueryTestSuite:
IgniteErrorOnRebalanceTest.testErrorOnRebalance
{color:#d04437}MVCC Queries{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2209591]]
* IgniteCacheMvccSqlTestSuite:
CacheMvccContinuousWithTransformerReplicatedSelfTest.testContinuousWithTransformerAndRegularListenerKeepBinaryAsync
{color:#d04437}Continuous Query 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2209547]]
* IgniteCacheQuerySelfTestSuite3:
CacheContinuousQueryOrderingEventTest.testAtomicOnheapTwoBackupAsyncFullSync -
0,0% fails in last 100 master runs.
{color:#d04437}SPI{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2331419]]
* IgniteSpiTestSuite:
IgniteClientReconnectMassiveShutdownTest.testMassiveServersShutdown1
{color:#d04437}Binary Objects (Simple Mapper Basic){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2209538]]
* IgniteBinarySimpleNameMapperBasicTestSuite:
GridServiceProcessorBatchDeploySelfTest.testDeployAllTopologyChangeFail
{color:#d04437}Platform .NET{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=2209633]]
* exe: ClientConnectionTest.TestServerConnectionAborted - 3,1% fails in last
100 master runs.
* exe: ServicesTest.TestWithKeepBinaryClient - 0,0% fails in last 100 master
runs.
{color:#d04437}Start Nodes{color} [[tests
16|https://ci.ignite.apache.org/viewLog.html?buildId=2209571]]
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testStopNodesByIds - 3,2% fails in
last 100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testStopNodesFiltered - 3,2% fails in
last 100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testStartThreeNodesAndDoEmptyCall -
3,2% fails in last 100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testStartOneNode - 3,2% fails in last
100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testRestartNodes - 3,2% fails in last
100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testRestartNodesByIds - 3,2% fails in
last 100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testCustomScript - 3,2% fails in last
100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testStartFiveWithTwoSpecs - 3,2% fails
in last 100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testRestartNodesFiltered - 3,2% fails
in last 100 master runs.
{panel}
[TeamCity Run All
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2209645&buildTypeId=IgniteTests24Java8_RunAll])
> Remove unnecessary @SuppressWarnings annotation
> ---
>
> Key: IGNITE-9312
> URL: https://issues.apache.org/jira/browse/IGNITE-9312
> Project: Ignite
> Issue Type: Bug
>Reporter: Maxim Muzafarov
>Assignee: PetrovMikhail
>Priority: Minor
> Labels: inspections
> Fix For: 2.8
>
>
> New `Code Inspections` profile can be found
> \idea\ignite_inspections.xml.
> We will need to fix all methods with unnecessary {{@SuppressWarnings}}
> annotation regarding this inscpetion profile.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9461) Implement random subspace method and provide an option to combine it with bagging
[
https://issues.apache.org/jira/browse/IGNITE-9461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yury Babak updated IGNITE-9461:
---
Fix Version/s: 2.8
> Implement random subspace method and provide an option to combine it with
> bagging
> -
>
> Key: IGNITE-9461
> URL: https://issues.apache.org/jira/browse/IGNITE-9461
> Project: Ignite
> Issue Type: Task
> Components: ml
>Affects Versions: 2.6
>Reporter: Oleg Ignatenko
>Priority: Major
> Fix For: 2.8
>
>
> Implement random subspace method (aka attribute bagging or feature bagging)
> to give ML API users more options to address overfitting. Also provide an
> option to combine this method with bagging.
> References:
> * [Wikipedia article|https://en.wikipedia.org/wiki/Random_subspace_method]
> {quote}Informally, this causes individual learners to not over-focus on
> features that appear highly predictive/descriptive in the training set, but
> fail to be as predictive for points outside that set. For this reason, random
> subspaces are an attractive choice for problems where the number of features
> is much larger than the number of training points, such as learning from fMRI
> data or gene expression data...{quote}
> * [Combining Bagging and Random Subspaces to Create Better
> Ensembles|https://pdfs.semanticscholar.org/d38f/979ad85d59fc93058279010efc73a24a712c.pdf]
> * [Bagging and the Random Subspace Method for Redundant Feature
> Spaces|https://link.springer.com/chapter/10.1007/3-540-48219-9_1]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9999) Add verbose logging for node recovery
[ https://issues.apache.org/jira/browse/IGNITE-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Kovalenko updated IGNITE-: Component/s: cache > Add verbose logging for node recovery > - > > Key: IGNITE- > URL: https://issues.apache.org/jira/browse/IGNITE- > Project: Ignite > Issue Type: Task > Components: cache >Affects Versions: 2.8 >Reporter: Alexey Goncharuk >Assignee: Pavel Kovalenko >Priority: Major > Fix For: 2.8 > > > Sometimes we see some difficulties in understanding which state a node is > after a binary recovery and what state it has after applying all logical > records from WAL. > We need to add more information on the state of partitions (update counter, > size, maybe more additional info) after the binary recovery (can be validated > against checkpoint records) and after logical recovery (can help to validate > the correctness of rebalance). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10287) [ML] Model storage
[ https://issues.apache.org/jira/browse/IGNITE-10287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Babak updated IGNITE-10287: Fix Version/s: 2.8 > [ML] Model storage > -- > > Key: IGNITE-10287 > URL: https://issues.apache.org/jira/browse/IGNITE-10287 > Project: Ignite > Issue Type: New Feature > Components: ml >Reporter: Yury Babak >Priority: Major > Fix For: 2.8 > > > We want to have some storage for any kind of models in Apache Ignite. It > should allow storing > a model from any node after training and evaluation(MB with some meta info > and model metrics) and provide API to get this model to any node. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10288) [ML] Model inference
[ https://issues.apache.org/jira/browse/IGNITE-10288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Babak updated IGNITE-10288: Fix Version/s: 2.8 > [ML] Model inference > > > Key: IGNITE-10288 > URL: https://issues.apache.org/jira/browse/IGNITE-10288 > Project: Ignite > Issue Type: New Feature > Components: ml >Reporter: Yury Babak >Priority: Major > Fix For: 2.8 > > > We need a convenient API for model inference. The current idea is to utilize > Service Grid for this purpose. We should have two options, first is deliver a > model to any node(server or client) and infer this model on that node. The > second approach is to pin a model to a specific server and infer model on > that server, it could be useful in case if we need some specific hardware > which we don't have at any server like a GPU or TPU. > So the first approach is suitable for lightweight models and the second > approach is suitable for some complex models like Neural Networks. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10289) [ML] Import models from XGBoost
[ https://issues.apache.org/jira/browse/IGNITE-10289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Babak updated IGNITE-10289: Fix Version/s: 2.8 > [ML] Import models from XGBoost > --- > > Key: IGNITE-10289 > URL: https://issues.apache.org/jira/browse/IGNITE-10289 > Project: Ignite > Issue Type: New Feature > Components: ml >Reporter: Yury Babak >Assignee: Anton Dmitriev >Priority: Major > Fix For: 2.8 > > > We want to have the ability of import model from 3rd part ml libraries into > Apache Ignite. We could start this process from XGBoost library for trees and > GDB. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9312) Remove unnecessary @SuppressWarnings annotation
[
https://issues.apache.org/jira/browse/IGNITE-9312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689372#comment-16689372
]
PetrovMikhail commented on IGNITE-9312:
---
{panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Queries (Binary Objects Simple Mapper){color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=2209639]]
* IgniteBinarySimpleNameMapperCacheQueryTestSuite:
IgniteClientReconnectCacheQueriesFailoverTest.testReconnectCacheQueries
* IgniteBinarySimpleNameMapperCacheQueryTestSuite:
IgniteErrorOnRebalanceTest.testErrorOnRebalance
{color:#d04437}MVCC Queries{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2209591]]
* IgniteCacheMvccSqlTestSuite:
CacheMvccContinuousWithTransformerReplicatedSelfTest.testContinuousWithTransformerAndRegularListenerKeepBinaryAsync
{color:#d04437}Continuous Query 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2209547]]
* IgniteCacheQuerySelfTestSuite3:
CacheContinuousQueryOrderingEventTest.testAtomicOnheapTwoBackupAsyncFullSync -
0,0% fails in last 100 master runs.
{color:#d04437}SPI{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2331419]]
* IgniteSpiTestSuite:
IgniteClientReconnectMassiveShutdownTest.testMassiveServersShutdown1
{color:#d04437}Binary Objects (Simple Mapper Basic){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2209538]]
* IgniteBinarySimpleNameMapperBasicTestSuite:
GridServiceProcessorBatchDeploySelfTest.testDeployAllTopologyChangeFail
{color:#d04437}Platform .NET{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=2209633]]
* exe: ClientConnectionTest.TestServerConnectionAborted - 3,1% fails in last
100 master runs.
* exe: ServicesTest.TestWithKeepBinaryClient - 0,0% fails in last 100 master
runs.
{color:#d04437}Start Nodes{color} [[tests
16|https://ci.ignite.apache.org/viewLog.html?buildId=2209571]]
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testStopNodesByIds - 3,2% fails in
last 100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testStopNodesFiltered - 3,2% fails in
last 100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testStartThreeNodesAndDoEmptyCall -
3,2% fails in last 100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testStartOneNode - 3,2% fails in last
100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testRestartNodes - 3,2% fails in last
100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testRestartNodesByIds - 3,2% fails in
last 100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testCustomScript - 3,2% fails in last
100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testStartFiveWithTwoSpecs - 3,2% fails
in last 100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testRestartNodesFiltered - 3,2% fails
in last 100 master runs.
{panel}
[TeamCity Run All
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2209645&buildTypeId=IgniteTests24Java8_RunAll]
> Remove unnecessary @SuppressWarnings annotation
> ---
>
> Key: IGNITE-9312
> URL: https://issues.apache.org/jira/browse/IGNITE-9312
> Project: Ignite
> Issue Type: Bug
>Reporter: Maxim Muzafarov
>Assignee: PetrovMikhail
>Priority: Minor
> Labels: inspections
> Fix For: 2.8
>
>
> New `Code Inspections` profile can be found
> \idea\ignite_inspections.xml.
> We will need to fix all methods with unnecessary {{@SuppressWarnings}}
> annotation regarding this inscpetion profile.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9312) Remove unnecessary @SuppressWarnings annotation
[
https://issues.apache.org/jira/browse/IGNITE-9312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689382#comment-16689382
]
PetrovMikhail commented on IGNITE-9312:
---
{panel:title=No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity Run All
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2331413&buildTypeId=IgniteTests24Java8_Queries2]
> Remove unnecessary @SuppressWarnings annotation
> ---
>
> Key: IGNITE-9312
> URL: https://issues.apache.org/jira/browse/IGNITE-9312
> Project: Ignite
> Issue Type: Bug
>Reporter: Maxim Muzafarov
>Assignee: PetrovMikhail
>Priority: Minor
> Labels: inspections
> Fix For: 2.8
>
>
> New `Code Inspections` profile can be found
> \idea\ignite_inspections.xml.
> We will need to fix all methods with unnecessary {{@SuppressWarnings}}
> annotation regarding this inscpetion profile.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10197) unexpected IllegalArgumentException in IgniteDbPutGetAbstractTest#testRandomPutGetRemove
[
https://issues.apache.org/jira/browse/IGNITE-10197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689381#comment-16689381
]
ASF GitHub Bot commented on IGNITE-10197:
-
GitHub user ibessonov opened a pull request:
https://github.com/apache/ignite/pull/5410
IGNITE-10197 unexpected IllegalArgumentException in
IgniteDbPutGetAbstractTest#testRandomPutGetRemove
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10197
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5410.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #5410
commit 5b2aedaf37f0fca7fd3f322bcabb774a7c3e61f4
Author: ibessonov
Date: 2018-11-16T12:52:25Z
IGNITE-10197 "testRandomPutGetRemove" test method was uncommented.
> unexpected IllegalArgumentException in
> IgniteDbPutGetAbstractTest#testRandomPutGetRemove
>
>
> Key: IGNITE-10197
> URL: https://issues.apache.org/jira/browse/IGNITE-10197
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Oleg Ignatenko
>Assignee: Ivan Bessonov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
>
> IgniteDbPutGetAbstractTest#testRandomPutGetRemove (in current codebase muted
> by renaming to {{_testRandomPutGetRemove}}) fails with IAE:
> {noformat}java.lang.IllegalArgumentException: Ouch! Argument is invalid:
> Cache name must not be null or empty.
> at
> org.apache.ignite.internal.util.GridArgumentCheck.ensure(GridArgumentCheck.java:109)
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.validateCacheName(GridCacheUtils.java:1600)
> at org.apache.ignite.internal.IgniteKernal.cache(IgniteKernal.java:2901)
> at
> org.apache.ignite.internal.processors.database.IgniteDbPutGetAbstractTest.cache(IgniteDbPutGetAbstractTest.java:74)
> at
> org.apache.ignite.internal.processors.database.IgniteDbPutGetAbstractTest.testRandomPutGetRemove(IgniteDbPutGetAbstractTest.java:814)
> 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:497)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2208)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:144)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:2124)
> at java.lang.Thread.run(Thread.java:745){noformat}
> Note a while ago this test was muted by adding underscore prefix to its name
> per [commit
> 2e343b6|https://github.com/apache/ignite/commit/4282d802f16188cdea05d6b2d2c0f3c222e343b6]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (IGNITE-9312) Remove unnecessary @SuppressWarnings annotation
[
https://issues.apache.org/jira/browse/IGNITE-9312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
PetrovMikhail updated IGNITE-9312:
--
Comment: was deleted
(was: {panel:title=No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity Run All
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2331413&buildTypeId=IgniteTests24Java8_Queries2])
> Remove unnecessary @SuppressWarnings annotation
> ---
>
> Key: IGNITE-9312
> URL: https://issues.apache.org/jira/browse/IGNITE-9312
> Project: Ignite
> Issue Type: Bug
>Reporter: Maxim Muzafarov
>Assignee: PetrovMikhail
>Priority: Minor
> Labels: inspections
> Fix For: 2.8
>
>
> New `Code Inspections` profile can be found
> \idea\ignite_inspections.xml.
> We will need to fix all methods with unnecessary {{@SuppressWarnings}}
> annotation regarding this inscpetion profile.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10286) [ML] Umbrella: Model serving
[ https://issues.apache.org/jira/browse/IGNITE-10286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Babak updated IGNITE-10286: Fix Version/s: 2.8 > [ML] Umbrella: Model serving > > > Key: IGNITE-10286 > URL: https://issues.apache.org/jira/browse/IGNITE-10286 > Project: Ignite > Issue Type: New Feature > Components: ml >Reporter: Yury Babak >Assignee: Yury Babak >Priority: Major > Fix For: 2.8 > > > We want to have convenient API for model serving. It means that we need a > mechanism for storing models and infer them inside Apache Ignite. > For now, I see 2 important features - distributed storage for any models and > inference. > From my point of view, we could use some built-in(predefined) cache as model > storage. And use service grid for model inference. We could implement some > "ModelService" for access to our storage, receive the list of all suitable > model(including model metrics and some other information about a model), > choose one(or several) and infer it from this service. > Model from TF should also use the same mechanisms for storing and inference. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10285) U.doInParallel may lead to deadlock
[ https://issues.apache.org/jira/browse/IGNITE-10285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689391#comment-16689391 ] Pavel Voronkin commented on IGNITE-10285: - Looks good for me. > U.doInParallel may lead to deadlock > --- > > Key: IGNITE-10285 > URL: https://issues.apache.org/jira/browse/IGNITE-10285 > Project: Ignite > Issue Type: Bug >Reporter: Dmitriy Govorukhin >Assignee: Dmitriy Govorukhin >Priority: Critical > Fix For: 2.8 > > Attachments: dump.rtf > > > There are exist case when we can get a deadlock on the thread pool. > If we try doInParallel in the thread of sys-pool in the number of > hreads==sys-pool.size we lead to deadlock because threads in sys-pool will > try doInParallel through the same sys-pool, and they will wait on future > infinitely because no one thread cannot complete operation doInParallel which > require threads from sys-pool. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10260) MVCC: GetAndPutIfAbsent operation return no result.
[ https://issues.apache.org/jira/browse/IGNITE-10260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-10260: -- Summary: MVCC: GetAndPutIfAbsent operation return no result. (was: MVCC: GetAndPutIfAbsent operation result no result.) > MVCC: GetAndPutIfAbsent operation return no result. > --- > > Key: IGNITE-10260 > URL: https://issues.apache.org/jira/browse/IGNITE-10260 > Project: Ignite > Issue Type: Bug > Components: cache, mvcc >Affects Versions: 2.7 >Reporter: Andrew Mashenkov >Assignee: Andrew Mashenkov >Priority: Major > Fix For: 2.8 > > > Next test (but may be not the only) are failed with Mvcc cache mode: > CachePutIfAbsentTest.testTxConflictGetAndPutIfAbsent() > CacheEnumOperationsSingleNodeTest.testMvccTx() -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10278) The checkpointReadLock must be acquired before calling MvccProcessor.updateState
[
https://issues.apache.org/jira/browse/IGNITE-10278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689392#comment-16689392
]
Andrew Mashenkov commented on IGNITE-10278:
---
Changes looks ok, can be merged.
> The checkpointReadLock must be acquired before calling
> MvccProcessor.updateState
>
>
> Key: IGNITE-10278
> URL: https://issues.apache.org/jira/browse/IGNITE-10278
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Affects Versions: 2.7
>Reporter: Vyacheslav Koptilin
>Assignee: Vyacheslav Koptilin
>Priority: Major
> Fix For: 2.8
>
>
> It looks like acquiring \{{checkpointReadLock}} is missing when we are trying
> to apply mvcc tx records.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8379) Add maven-surefire-plugin support for PDS Compatibility tests
[
https://issues.apache.org/jira/browse/IGNITE-8379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689401#comment-16689401
]
ASF GitHub Bot commented on IGNITE-8379:
GitHub user daradurvs opened a pull request:
https://github.com/apache/ignite/pull/5411
IGNITE-8379 Add maven-surefire-plugin support for PDS Compatibility tests
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/daradurvs/ignite ignite-8379
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5411.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #5411
commit fb00b524aebfe4a48dc39ad98d6fb7aa245cf1c1
Author: Vyacheslav Daradur
Date: 2018-11-16T13:07:55Z
Introduced support precompilled artifacts; refactoring
> Add maven-surefire-plugin support for PDS Compatibility tests
> -
>
> Key: IGNITE-8379
> URL: https://issues.apache.org/jira/browse/IGNITE-8379
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.5
>Reporter: Peter Ivanov
>Assignee: Vyacheslav Daradur
>Priority: Major
> Fix For: 2.8
>
>
> In continuation of the works on PDS Compatibility test suite, it is required
> to add support for {{maven-surefire-plugin}} in Compatibility Framework.
> See IGNITE-8275 for details.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10295) Rework Sending Full Message logging.
Pavel Voronkin created IGNITE-10295: --- Summary: Rework Sending Full Message logging. Key: IGNITE-10295 URL: https://issues.apache.org/jira/browse/IGNITE-10295 Project: Ignite Issue Type: Improvement Reporter: Pavel Voronkin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-3373) Distributed IgniteSet shows size() == 0 for any new node
[ https://issues.apache.org/jira/browse/IGNITE-3373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689410#comment-16689410 ] Dmitriy Govorukhin commented on IGNITE-3373: [~akazlou] Do you have updates? > Distributed IgniteSet shows size() == 0 for any new node > > > Key: IGNITE-3373 > URL: https://issues.apache.org/jira/browse/IGNITE-3373 > Project: Ignite > Issue Type: Bug >Reporter: Andrey Velichko >Assignee: Dmitriy Govorukhin >Priority: Major > Attachments: DistributedSetDemo.java > > > For distributed IgniteSet new node shows incorrect size igniteSet.size() == > 0, but igniteSet.contains(42L) == true -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10295) Rework Sending Full Message logging.
[ https://issues.apache.org/jira/browse/IGNITE-10295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Voronkin reassigned IGNITE-10295: --- Assignee: Pavel Voronkin > Rework Sending Full Message logging. > > > Key: IGNITE-10295 > URL: https://issues.apache.org/jira/browse/IGNITE-10295 > Project: Ignite > Issue Type: Improvement >Reporter: Pavel Voronkin >Assignee: Pavel Voronkin >Priority: Major > > [16:33:34,410][INFO][sys-#122][GridDhtPartitionsExchangeFuture] Sending Full > Message performed in 0 ms. > [16:33:34,410][INFO][sys-#122][GridDhtPartitionsExchangeFuture] Sending Full > Message to all nodes performed in 0 ms. > [16:33:32,993][INFO][exchange-worker-#66][GridDhtPartitionsExchangeFuture] > Sending Single Message performed in 150 ms. > > For varying number of caches, server nodes or number of partitions, reported > single message time change respectively, but reported full message time > always printed as 0 or 1 ms. Seems that it is calculated incorrectly, cause > of async send of message. > The most we spend in this method is actually open connection on send() > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10295) Rework Sending Full Message logging.
[ https://issues.apache.org/jira/browse/IGNITE-10295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Voronkin updated IGNITE-10295: Description: [16:33:34,410][INFO][sys-#122][GridDhtPartitionsExchangeFuture] Sending Full Message performed in 0 ms. [16:33:34,410][INFO][sys-#122][GridDhtPartitionsExchangeFuture] Sending Full Message to all nodes performed in 0 ms. [16:33:32,993][INFO][exchange-worker-#66][GridDhtPartitionsExchangeFuture] Sending Single Message performed in 150 ms. For varying number of caches, server nodes or number of partitions, reported single message time change respectively, but reported full message time always printed as 0 or 1 ms. Seems that it is calculated incorrectly, cause of async send of message. The most we spend in this method is actually open connection on send() > Rework Sending Full Message logging. > > > Key: IGNITE-10295 > URL: https://issues.apache.org/jira/browse/IGNITE-10295 > Project: Ignite > Issue Type: Improvement >Reporter: Pavel Voronkin >Priority: Major > > [16:33:34,410][INFO][sys-#122][GridDhtPartitionsExchangeFuture] Sending Full > Message performed in 0 ms. > [16:33:34,410][INFO][sys-#122][GridDhtPartitionsExchangeFuture] Sending Full > Message to all nodes performed in 0 ms. > [16:33:32,993][INFO][exchange-worker-#66][GridDhtPartitionsExchangeFuture] > Sending Single Message performed in 150 ms. > > For varying number of caches, server nodes or number of partitions, reported > single message time change respectively, but reported full message time > always printed as 0 or 1 ms. Seems that it is calculated incorrectly, cause > of async send of message. > The most we spend in this method is actually open connection on send() > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10243) [TC Bot] Support partially cancelled suites in RunAll
[ https://issues.apache.org/jira/browse/IGNITE-10243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689417#comment-16689417 ] ASF GitHub Bot commented on IGNITE-10243: - asfgit closed pull request #69: IGNITE-10243 Chain analysis entry points are get now from preloaded b… URL: https://github.com/apache/ignite-teamcity-bot/pull/69 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > [TC Bot] Support partially cancelled suites in RunAll > - > > Key: IGNITE-10243 > URL: https://issues.apache.org/jira/browse/IGNITE-10243 > Project: Ignite > Issue Type: Task >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Major > > For case, there is no TC run (RunAll) for the branch with normal status we > can check if there are any with canceled status. > If canceled status (unknown) appeared on the latest build in suite's rebuilds > sequence, we can use the latest build successful. > If there is only one build in rebuilds sequence and it was canceled => use > this one as a possible blocker for PR report. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9355) Document new system views (nodes, node attributes, baseline nodes, node metrics)
[
https://issues.apache.org/jira/browse/IGNITE-9355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689418#comment-16689418
]
Artem Budnikov commented on IGNITE-9355:
[~dmagda]
Agree. I already created the "Management and Monitoring" section and moved the
two pages there.
> Document new system views (nodes, node attributes, baseline nodes, node
> metrics)
>
>
> Key: IGNITE-9355
> URL: https://issues.apache.org/jira/browse/IGNITE-9355
> Project: Ignite
> Issue Type: Task
> Components: documentation, sql
>Reporter: Vladimir Ozerov
>Assignee: Artem Budnikov
>Priority: Major
> Fix For: 2.7
>
>
> We need to document three new SQL system views.
> # Explain users that new system SQL schema appeared, named "IGNITE", where
> all views are stored
> # System view NODES - list of current nodes in topology. Columns: ID,
> CONSISTENT_ID, VERSION, IS_LOCAL, IS_CLIENT, IS_DAEMON, NODE_ORDER,
> ADDRESSES, HOSTNAMES
> # System view NODE_ATTRIBUTES - attributes for all nodes. Columns: NODE_ID,
> NAME, VALUE
> # System view BASELINE_NODES - list of baseline topology nodes. Columns:
> CONSISTENT_ID, ONLINE (whether node is up and running at the moment)
> # System view NODE_METRICS - node metrics. Columns - see
> \{{org.apache.ignite.internal.processors.query.h2.sys.view.SqlSystemViewNodeMetrics}}
> class
> # Explain limitations: views cannot be joined with user tables; it is not
> allowed to create other objects (tables, indexes) in "IGNITE" schema.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10297) Investigate possibility of restricting API of Upstream transformer
Artem Malykh created IGNITE-10297: - Summary: Investigate possibility of restricting API of Upstream transformer Key: IGNITE-10297 URL: https://issues.apache.org/jira/browse/IGNITE-10297 Project: Ignite Issue Type: Improvement Components: ml Reporter: Artem Malykh Assignee: Artem Malykh Signature of 'transform' method of UpstreamTransformer is Stream -> Stream. For now it is used only for bagging and for that purpose, UpstreamEntry -> Stream would suffice (just use 'flatMap' on upstream), maybe we should change signature to this form. From other hand, we'll cut some possibilities like limiting of upstream. This question needs investigation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10177) cleanup Junit 3 from the project
[
https://issues.apache.org/jira/browse/IGNITE-10177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Ignatenko updated IGNITE-10177:
Description:
If needed, refer parent task for more details.
1) remove deprecated API of GridAbstractTest and its subclasses 2) remove
dependencies from Junit 3 in Maven 3) migrate tests that were missed at prior
steps, if there are any 4) remove redundant references to {{JUnit4.class}} if
there are any (like in {{@RunWith(JUnit4.class)}}) 5) in tests suite classes,
change {{extends TestSuite}} to {{@RunWith(AllTests.class)}}
was:
If needed, refer parent task for more details.
1) remove deprecated API of GridAbstractTest and its subclasses 2) remove
dependencies from Junit 3 in Maven 3) migrate tests that were missed at prior
steps, if there are any 4) remove redundant references to {{JUnit4.class}} if
there are any (like in {{\@RunWith(JUnit4.class)}})
> cleanup Junit 3 from the project
>
>
> Key: IGNITE-10177
> URL: https://issues.apache.org/jira/browse/IGNITE-10177
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Oleg Ignatenko
>Priority: Major
>
> If needed, refer parent task for more details.
> 1) remove deprecated API of GridAbstractTest and its subclasses 2) remove
> dependencies from Junit 3 in Maven 3) migrate tests that were missed at prior
> steps, if there are any 4) remove redundant references to {{JUnit4.class}} if
> there are any (like in {{@RunWith(JUnit4.class)}}) 5) in tests suite classes,
> change {{extends TestSuite}} to {{@RunWith(AllTests.class)}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10297) Investigate possibility of restricting API of Upstream transformer
[ https://issues.apache.org/jira/browse/IGNITE-10297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Dmitriev updated IGNITE-10297: Fix Version/s: 2.8 > Investigate possibility of restricting API of Upstream transformer > -- > > Key: IGNITE-10297 > URL: https://issues.apache.org/jira/browse/IGNITE-10297 > Project: Ignite > Issue Type: Improvement > Components: ml >Reporter: Artem Malykh >Assignee: Artem Malykh >Priority: Major > Fix For: 2.8 > > > Signature of 'transform' method of UpstreamTransformer is > Stream -> Stream. For now it is used only for > bagging and for that purpose, UpstreamEntry -> Stream would > suffice (just use 'flatMap' on upstream), maybe we should change signature to > this form. From other hand, we'll cut some possibilities like limiting of > upstream. This question needs investigation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10297) Investigate possibility of restricting API of Upstream transformer
[ https://issues.apache.org/jira/browse/IGNITE-10297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Dmitriev updated IGNITE-10297: Affects Version/s: 2.8 > Investigate possibility of restricting API of Upstream transformer > -- > > Key: IGNITE-10297 > URL: https://issues.apache.org/jira/browse/IGNITE-10297 > Project: Ignite > Issue Type: Improvement > Components: ml >Affects Versions: 2.8 >Reporter: Artem Malykh >Assignee: Artem Malykh >Priority: Major > Fix For: 2.8 > > > Signature of 'transform' method of UpstreamTransformer is > Stream -> Stream. For now it is used only for > bagging and for that purpose, UpstreamEntry -> Stream would > suffice (just use 'flatMap' on upstream), maybe we should change signature to > this form. From other hand, we'll cut some possibilities like limiting of > upstream. This question needs investigation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10297) Investigate possibility of restricting API of Upstream transformer
[ https://issues.apache.org/jira/browse/IGNITE-10297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Dmitriev updated IGNITE-10297: Ignite Flags: (was: Docs Required) > Investigate possibility of restricting API of Upstream transformer > -- > > Key: IGNITE-10297 > URL: https://issues.apache.org/jira/browse/IGNITE-10297 > Project: Ignite > Issue Type: Improvement > Components: ml >Affects Versions: 2.8 >Reporter: Artem Malykh >Assignee: Artem Malykh >Priority: Major > Fix For: 2.8 > > > Signature of 'transform' method of UpstreamTransformer is > Stream -> Stream. For now it is used only for > bagging and for that purpose, UpstreamEntry -> Stream would > suffice (just use 'flatMap' on upstream), maybe we should change signature to > this form. From other hand, we'll cut some possibilities like limiting of > upstream. This question needs investigation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10296) Change API of UpstreamTransformer to make it accept LearningEnvironment.
[ https://issues.apache.org/jira/browse/IGNITE-10296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Dmitriev updated IGNITE-10296: Ignite Flags: (was: Docs Required) > Change API of UpstreamTransformer to make it accept LearningEnvironment. > > > Key: IGNITE-10296 > URL: https://issues.apache.org/jira/browse/IGNITE-10296 > Project: Ignite > Issue Type: Improvement > Components: ml >Affects Versions: 2.8 >Reporter: Artem Malykh >Assignee: Artem Malykh >Priority: Major > Fix For: 2.8 > > > For now UpstreamTransformer uses Random object as parameter to be able to fix > it's behaviour through seeding. This goal should be reached by using random > number generator from learning environment (IGNITE-10272). So, > UpstreamTransformer should be result of work of UpstreamTransformerBuilder > (LearningEnvironment -> UpstreamTransformer) or something like this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10296) Change API of UpstreamTransformer to make it accept LearningEnvironment.
[ https://issues.apache.org/jira/browse/IGNITE-10296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Dmitriev updated IGNITE-10296: Affects Version/s: 2.8 > Change API of UpstreamTransformer to make it accept LearningEnvironment. > > > Key: IGNITE-10296 > URL: https://issues.apache.org/jira/browse/IGNITE-10296 > Project: Ignite > Issue Type: Improvement > Components: ml >Affects Versions: 2.8 >Reporter: Artem Malykh >Assignee: Artem Malykh >Priority: Major > Fix For: 2.8 > > > For now UpstreamTransformer uses Random object as parameter to be able to fix > it's behaviour through seeding. This goal should be reached by using random > number generator from learning environment (IGNITE-10272). So, > UpstreamTransformer should be result of work of UpstreamTransformerBuilder > (LearningEnvironment -> UpstreamTransformer) or something like this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10296) Change API of UpstreamTransformer to make it accept LearningEnvironment.
[ https://issues.apache.org/jira/browse/IGNITE-10296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Dmitriev updated IGNITE-10296: Fix Version/s: 2.8 > Change API of UpstreamTransformer to make it accept LearningEnvironment. > > > Key: IGNITE-10296 > URL: https://issues.apache.org/jira/browse/IGNITE-10296 > Project: Ignite > Issue Type: Improvement > Components: ml >Affects Versions: 2.8 >Reporter: Artem Malykh >Assignee: Artem Malykh >Priority: Major > Fix For: 2.8 > > > For now UpstreamTransformer uses Random object as parameter to be able to fix > it's behaviour through seeding. This goal should be reached by using random > number generator from learning environment (IGNITE-10272). So, > UpstreamTransformer should be result of work of UpstreamTransformerBuilder > (LearningEnvironment -> UpstreamTransformer) or something like this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10260) MVCC: GetAndPutIfAbsent operation return no result.
[ https://issues.apache.org/jira/browse/IGNITE-10260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689479#comment-16689479 ] ASF GitHub Bot commented on IGNITE-10260: - GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/5412 IGNITE-10260: MVCC: GetAndPutIfAbsent operation return no result. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10260 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5412.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5412 commit 4053db079dffe1352b3df93e93020c028eff43be Author: Andrey V. Mashenkov Date: 2018-11-16T14:27:56Z IGNITE-10260: Fix getAndPutIfAbsent. > MVCC: GetAndPutIfAbsent operation return no result. > --- > > Key: IGNITE-10260 > URL: https://issues.apache.org/jira/browse/IGNITE-10260 > Project: Ignite > Issue Type: Bug > Components: cache, mvcc >Affects Versions: 2.7 >Reporter: Andrew Mashenkov >Assignee: Andrew Mashenkov >Priority: Major > Fix For: 2.8 > > > Next test (but may be not the only) are failed with Mvcc cache mode: > CachePutIfAbsentTest.testTxConflictGetAndPutIfAbsent() > CacheEnumOperationsSingleNodeTest.testMvccTx() -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10297) Investigate possibility of restricting API of Upstream transformer
[ https://issues.apache.org/jira/browse/IGNITE-10297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689467#comment-16689467 ] Anton Dmitriev commented on IGNITE-10297: - Could we also consider in this task an ability to avoid using of additional _TransformerChain_ and just use _andThen_ approach? > Investigate possibility of restricting API of Upstream transformer > -- > > Key: IGNITE-10297 > URL: https://issues.apache.org/jira/browse/IGNITE-10297 > Project: Ignite > Issue Type: Improvement > Components: ml >Reporter: Artem Malykh >Assignee: Artem Malykh >Priority: Major > > Signature of 'transform' method of UpstreamTransformer is > Stream -> Stream. For now it is used only for > bagging and for that purpose, UpstreamEntry -> Stream would > suffice (just use 'flatMap' on upstream), maybe we should change signature to > this form. From other hand, we'll cut some possibilities like limiting of > upstream. This question needs investigation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10002) MVCC: Create "Cache 2" test suite for MVCC mode.
[
https://issues.apache.org/jira/browse/IGNITE-10002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689481#comment-16689481
]
Ignite TC Bot commented on IGNITE-10002:
{panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}ZooKeeper (Discovery) 4{color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=2326389]]
* ZookeeperDiscoverySpiTestSuite4:
IgniteCachePutRetryAtomicSelfTest.testPutAsyncStoreEnabled - 0,0% fails in last
100 master runs.
{color:#d04437}Platform .NET{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2326376]]
* exe: PersistenceTest.TestWalDisableEnable - 0,0% fails in last 100 master
runs.
{color:#d04437}PDS (Compatibility)*{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2326366]]
* IgniteCompatibilityBasicTestSuite:
PersistenceBasicCompatibilityTest.testNodeStartByOldVersionPersistenceData_2_3
- 0,0% fails in last 100 master runs.
{panel}
[TeamCity Run All
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2326390&buildTypeId=IgniteTests24Java8_RunAll]
> MVCC: Create "Cache 2" test suite for MVCC mode.
>
>
> Key: IGNITE-10002
> URL: https://issues.apache.org/jira/browse/IGNITE-10002
> Project: Ignite
> Issue Type: Sub-task
> Components: mvcc
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
>Priority: Major
>
> Create MVCC version of IgniteCacheTestSuite2 and add it to TC.
> All non-relevant tests should be marked as ignored.
> Failed tests should be muted and tickets should be created for unknown
> failure reasons.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10243) [TC Bot] Support partially cancelled suites in RunAll
[
https://issues.apache.org/jira/browse/IGNITE-10243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689484#comment-16689484
]
PetrovMikhail commented on IGNITE-10243:
{panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Queries (Binary Objects Simple Mapper){color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=2209639]]
* IgniteBinarySimpleNameMapperCacheQueryTestSuite:
IgniteClientReconnectCacheQueriesFailoverTest.testReconnectCacheQueries
* IgniteBinarySimpleNameMapperCacheQueryTestSuite:
IgniteErrorOnRebalanceTest.testErrorOnRebalance
{color:#d04437}MVCC Queries{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2209591]]
* IgniteCacheMvccSqlTestSuite:
CacheMvccContinuousWithTransformerReplicatedSelfTest.testContinuousWithTransformerAndRegularListenerKeepBinaryAsync
{color:#d04437}Continuous Query 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2209547]]
* IgniteCacheQuerySelfTestSuite3:
CacheContinuousQueryOrderingEventTest.testAtomicOnheapTwoBackupAsyncFullSync -
0,0% fails in last 100 master runs.
{color:#d04437}SPI{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2331419]]
* IgniteSpiTestSuite:
IgniteClientReconnectMassiveShutdownTest.testMassiveServersShutdown1
{color:#d04437}Binary Objects (Simple Mapper Basic){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2209538]]
* IgniteBinarySimpleNameMapperBasicTestSuite:
GridServiceProcessorBatchDeploySelfTest.testDeployAllTopologyChangeFail
{color:#d04437}Start Nodes{color} [[tests
16|https://ci.ignite.apache.org/viewLog.html?buildId=2209571]]
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testStopNodesByIds - 3,2% fails in
last 100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testStopNodesFiltered - 3,2% fails in
last 100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testStartThreeNodesAndDoEmptyCall -
3,2% fails in last 100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testStartOneNode - 3,2% fails in last
100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testRestartNodes - 3,2% fails in last
100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testRestartNodesByIds - 3,2% fails in
last 100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testCustomScript - 3,2% fails in last
100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testStartFiveWithTwoSpecs - 3,2% fails
in last 100 master runs.
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testRestartNodesFiltered - 3,2% fails
in last 100 master runs.
{panel}
[TeamCity Run All
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2209645&buildTypeId=IgniteTests24Java8_RunAll]
> [TC Bot] Support partially cancelled suites in RunAll
> -
>
> Key: IGNITE-10243
> URL: https://issues.apache.org/jira/browse/IGNITE-10243
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
>
> For case, there is no TC run (RunAll) for the branch with normal status we
> can check if there are any with canceled status.
> If canceled status (unknown) appeared on the latest build in suite's rebuilds
> sequence, we can use the latest build successful.
> If there is only one build in rebuilds sequence and it was canceled => use
> this one as a possible blocker for PR report.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10295) Rework Sending Full Message logging.
[ https://issues.apache.org/jira/browse/IGNITE-10295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689482#comment-16689482 ] ASF GitHub Bot commented on IGNITE-10295: - GitHub user voropava opened a pull request: https://github.com/apache/ignite/pull/5413 IGNITE-10295 Added info logging for long connection establish methods… …, removed useless logging of Sending Full Message. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10295 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5413.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5413 commit da856f3883c76276eb034cfbea70a7beb85ea8d8 Author: Pavel Voronkin Date: 2018-11-09T12:00:03Z IGNITE-10295 Added info logging for long connection establish methods, removed useless logging of Sending Full Message. > Rework Sending Full Message logging. > > > Key: IGNITE-10295 > URL: https://issues.apache.org/jira/browse/IGNITE-10295 > Project: Ignite > Issue Type: Improvement >Reporter: Pavel Voronkin >Assignee: Pavel Voronkin >Priority: Major > > [16:33:34,410][INFO][sys-#122][GridDhtPartitionsExchangeFuture] Sending Full > Message performed in 0 ms. > [16:33:34,410][INFO][sys-#122][GridDhtPartitionsExchangeFuture] Sending Full > Message to all nodes performed in 0 ms. > [16:33:32,993][INFO][exchange-worker-#66][GridDhtPartitionsExchangeFuture] > Sending Single Message performed in 150 ms. > > For varying number of caches, server nodes or number of partitions, reported > single message time change respectively, but reported full message time > always printed as 0 or 1 ms. Seems that it is calculated incorrectly, cause > of async send of message. > The most we spend in this method is actually open connection on send() > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-3373) Distributed IgniteSet shows size() == 0 for any new node
[ https://issues.apache.org/jira/browse/IGNITE-3373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689494#comment-16689494 ] Aliaksandr Kazlou commented on IGNITE-3373: --- Hi, [~DmitriyGovorukhin]. Sorry for the delay. I do remember about the request, and have this in my TODO list. Right now we prepare for the major event for the product we build, it will be done next Wednesday, then would have more free time to look into further and share the details with you. > Distributed IgniteSet shows size() == 0 for any new node > > > Key: IGNITE-3373 > URL: https://issues.apache.org/jira/browse/IGNITE-3373 > Project: Ignite > Issue Type: Bug >Reporter: Andrey Velichko >Assignee: Dmitriy Govorukhin >Priority: Major > Attachments: DistributedSetDemo.java > > > For distributed IgniteSet new node shows incorrect size igniteSet.size() == > 0, but igniteSet.contains(42L) == true -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10299) SQL: Extract SELECT and DML plan caches into single class
Vladimir Ozerov created IGNITE-10299: Summary: SQL: Extract SELECT and DML plan caches into single class Key: IGNITE-10299 URL: https://issues.apache.org/jira/browse/IGNITE-10299 Project: Ignite Issue Type: Task Components: sql Reporter: Vladimir Ozerov Assignee: Vladimir Ozerov Fix For: 2.8 In future we will need to merge plans for both DML and SELECTs (both local and distributed) into a single entity. This ticket is the first part of this effort - let's just extract both plan caches into a single class. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10299) SQL: Extract SELECT and DML plan caches into single class
[ https://issues.apache.org/jira/browse/IGNITE-10299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689491#comment-16689491 ] ASF GitHub Bot commented on IGNITE-10299: - GitHub user devozerov opened a pull request: https://github.com/apache/ignite/pull/5414 IGNITE-10299 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10299 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5414.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5414 commit 68145c6eb0de4e4254a5804deb1b84f9a0a3be41 Author: devozerov Date: 2018-11-16T14:16:11Z DML. commit 0ab81dd184922eabb362a19c80757f67ea7763c3 Author: devozerov Date: 2018-11-16T14:24:54Z SQL. commit 02fe236eb1005ab9b7e0164bff9570c6b8612990 Author: devozerov Date: 2018-11-16T14:28:53Z Renames. commit 5f0dac97ca315aade75171bdd4d60932208106ca Author: devozerov Date: 2018-11-16T14:31:46Z WIP. commit b3ea9113de81a6d97d2a5acdf8881c966d186f3c Author: devozerov Date: 2018-11-16T14:35:48Z Minors. > SQL: Extract SELECT and DML plan caches into single class > - > > Key: IGNITE-10299 > URL: https://issues.apache.org/jira/browse/IGNITE-10299 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Major > Fix For: 2.8 > > > In future we will need to merge plans for both DML and SELECTs (both local > and distributed) into a single entity. This ticket is the first part of this > effort - let's just extract both plan caches into a single class. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10300) control.sh: incorrect error message after three tries on unsuccessful authorization
Pavel Voronkin created IGNITE-10300:
---
Summary: control.sh: incorrect error message after three tries on
unsuccessful authorization
Key: IGNITE-10300
URL: https://issues.apache.org/jira/browse/IGNITE-10300
Project: Ignite
Issue Type: Bug
Reporter: Pavel Voronkin
1. start grid with securirty enabled
2. try to issue control.sh --cache
authentication credentials asked
3. enter incorrect credentials three times
expected: Authentication error printed and logged
actual: Latest topology update failed error printed
{noformat}
IGNITE_HOME=`pwd` bin/control.sh --cache list .
Control utility [ver. 2.5.1-p160#20181113-sha1:5f845ca7]
2018 Copyright(C) Apache Software Foundation
User: mshonichev
Authentication error, try connection again.
user:
password:
Authentication error, try connection again.
user:
password:
Authentication error, try connection again.
user:
password:
Authentication error.
Error: Latest topology update failed.
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10243) [TC Bot] Support partially cancelled suites in RunAll
[
https://issues.apache.org/jira/browse/IGNITE-10243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689488#comment-16689488
]
PetrovMikhail commented on IGNITE-10243:
{panel:title=No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity Run All
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2331413&buildTypeId=IgniteTests24Java8_Queries2]
> [TC Bot] Support partially cancelled suites in RunAll
> -
>
> Key: IGNITE-10243
> URL: https://issues.apache.org/jira/browse/IGNITE-10243
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
>
> For case, there is no TC run (RunAll) for the branch with normal status we
> can check if there are any with canceled status.
> If canceled status (unknown) appeared on the latest build in suite's rebuilds
> sequence, we can use the latest build successful.
> If there is only one build in rebuilds sequence and it was canceled => use
> this one as a possible blocker for PR report.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10298) Possible deadlock between restore partition states and checkpoint begin
Pavel Kovalenko created IGNITE-10298:
Summary: Possible deadlock between restore partition states and
checkpoint begin
Key: IGNITE-10298
URL: https://issues.apache.org/jira/browse/IGNITE-10298
Project: Ignite
Issue Type: Bug
Components: cache
Affects Versions: 2.4
Reporter: Pavel Kovalenko
Fix For: 2.8
There is possible deadlock between "restorePartitionStates" phase during caches
starting and currently running checkpointer:
{noformat}
"db-checkpoint-thread-#50" #89 prio=5 os_prio=0 tid=0x1ad57800
nid=0x2b58 waiting on condition [0x7e42e000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0xddabfcc8> (a
java.util.concurrent.CountDownLatch$Sync)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:997)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1304)
at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:231)
at
org.apache.ignite.internal.util.IgniteUtils.await(IgniteUtils.java:7515)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.init0(GridCacheOffheapManager.java:1331)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.fullSize(GridCacheOffheapManager.java:1459)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.markCheckpointBegin(GridCacheDatabaseSharedManager.java:3397)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.doCheckpoint(GridCacheDatabaseSharedManager.java:3009)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.body(GridCacheDatabaseSharedManager.java:2934)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:748)
"exchange-worker-#42" #69 prio=5 os_prio=0 tid=0x1c1cd800 nid=0x259c
waiting on condition [0x249ae000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0x80b634a0> (a
java.util.concurrent.locks.ReentrantReadWriteLock$NonfairSync)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireShared(AbstractQueuedSynchronizer.java:967)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireShared(AbstractQueuedSynchronizer.java:1283)
at
java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock.lock(ReentrantReadWriteLock.java:727)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.checkpointReadLock(GridCacheDatabaseSharedManager.java:1328)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.init0(GridCacheOffheapManager.java:1212)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.initialUpdateCounter(GridCacheOffheapManager.java:1537)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager.onPartitionInitialCounterUpdated(GridCacheOffheapManager.java:633)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.restorePartitionStates(GridCacheDatabaseSharedManager.java:2365)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.beforeExchange(GridCacheDatabaseSharedManager.java:1174)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchangeFuture.java:1119)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:703)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2364)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:748)
{noformat}
Possible solution is performing resto
[jira] [Commented] (IGNITE-10299) SQL: Extract SELECT and DML plan caches into single class
[ https://issues.apache.org/jira/browse/IGNITE-10299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689501#comment-16689501 ] Vladimir Ozerov commented on IGNITE-10299: -- Test run: https://ci.ignite.apache.org/viewQueued.html?itemId=2333920 > SQL: Extract SELECT and DML plan caches into single class > - > > Key: IGNITE-10299 > URL: https://issues.apache.org/jira/browse/IGNITE-10299 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Major > Fix For: 2.8 > > > In future we will need to merge plans for both DML and SELECTs (both local > and distributed) into a single entity. This ticket is the first part of this > effort - let's just extract both plan caches into a single class. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10300) control.sh: incorrect error message after three tries on unsuccessful authorization.
[
https://issues.apache.org/jira/browse/IGNITE-10300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Voronkin updated IGNITE-10300:
Summary: control.sh: incorrect error message after three tries on
unsuccessful authorization. (was: control.sh: incorrect error message after
three tries on unsuccessful authorization)
> control.sh: incorrect error message after three tries on unsuccessful
> authorization.
>
>
> Key: IGNITE-10300
> URL: https://issues.apache.org/jira/browse/IGNITE-10300
> Project: Ignite
> Issue Type: Bug
>Reporter: Pavel Voronkin
>Assignee: Pavel Voronkin
>Priority: Major
>
> 1. start grid with securirty enabled
> 2. try to issue control.sh --cache
> authentication credentials asked
> 3. enter incorrect credentials three times
> expected: Authentication error printed and logged
> actual: Latest topology update failed error printed
> {noformat}
> IGNITE_HOME=`pwd` bin/control.sh --cache list .
> Control utility [ver. 2.5.1-p160#20181113-sha1:5f845ca7]
> 2018 Copyright(C) Apache Software Foundation
> User: mshonichev
>
> Authentication error, try connection again.
> user:
> password:
> Authentication error, try connection again.
> user:
> password:
> Authentication error, try connection again.
> user:
> password:
> Authentication error.
> Error: Latest topology update failed.
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-10300) control.sh: incorrect error message after three tries on unsuccessful authorization
[
https://issues.apache.org/jira/browse/IGNITE-10300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Voronkin reassigned IGNITE-10300:
---
Assignee: Pavel Voronkin
> control.sh: incorrect error message after three tries on unsuccessful
> authorization
> ---
>
> Key: IGNITE-10300
> URL: https://issues.apache.org/jira/browse/IGNITE-10300
> Project: Ignite
> Issue Type: Bug
>Reporter: Pavel Voronkin
>Assignee: Pavel Voronkin
>Priority: Major
>
> 1. start grid with securirty enabled
> 2. try to issue control.sh --cache
> authentication credentials asked
> 3. enter incorrect credentials three times
> expected: Authentication error printed and logged
> actual: Latest topology update failed error printed
> {noformat}
> IGNITE_HOME=`pwd` bin/control.sh --cache list .
> Control utility [ver. 2.5.1-p160#20181113-sha1:5f845ca7]
> 2018 Copyright(C) Apache Software Foundation
> User: mshonichev
>
> Authentication error, try connection again.
> user:
> password:
> Authentication error, try connection again.
> user:
> password:
> Authentication error, try connection again.
> user:
> password:
> Authentication error.
> Error: Latest topology update failed.
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10301) GridToStringBuilder is broken for classes with inheritance
Alexey Goncharuk created IGNITE-10301:
-
Summary: GridToStringBuilder is broken for classes with inheritance
Key: IGNITE-10301
URL: https://issues.apache.org/jira/browse/IGNITE-10301
Project: Ignite
Issue Type: Bug
Affects Versions: 2.7
Reporter: Alexey Goncharuk
Fix For: 2.7
Given the following class hierarchy
{code}
/** */
private static class Parent {
/** */
private int a;
/** {@inheritDoc} */
@Override public String toString() {
return S.toString(Parent.class, this);
}
}
/** */
private static class Child extends Parent {
/** */
private int b;
/** {@inheritDoc} */
@Override public String toString() {
return S.toString(Child.class, this, super.toString());
}
}
private static class Wrapper {
/** */
@GridToStringInclude
Parent p = new Child();
/** {@inheritDoc} */
@Override public String toString() {
return S.toString(Wrapper.class, this);
}
}
{code}
the next test fails:
{code}
/**
*/
public void testHierarchy() {
Wrapper w = new Wrapper();
Parent p = w.p;
String wS = w.toString();
String pS = p.toString();
// Expect wS to be "Wrapper [p=" + pS + ']'.
assertEquals("Wrapper [p=" + pS + ']', wS);
}
{code}
{code}
Expected :Wrapper [p=Child [b=0, super=Parent [a=0]]]
Actual :Wrapper [p=Parent [a=0]Child [b=0, super=]]
{code}
This is a regression from IGNITE-602. We need to fix this in 2.7 or revert
IGNITE-602.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
