[jira] [Commented] (IGNITE-12926) [ignite-extensions] build failed
[
https://issues.apache.org/jira/browse/IGNITE-12926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17089180#comment-17089180
]
Saikat Maitra commented on IGNITE-12926:
[~nizhikov]
I have reviewed the PR and the changes looks good.
Thank you,
Saikat
> [ignite-extensions] build failed
>
>
> Key: IGNITE-12926
> URL: https://issues.apache.org/jira/browse/IGNITE-12926
> Project: Ignite
> Issue Type: Test
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Blocker
>
> The current master in ignite-extension can't be built.
> The reason in parent pom.xml which contains
> org.apache.ignite:ignite-tools:1.0-SNAPSHOT dependency for Javadoc plugin.
> The version has taken from the project version.
> {noformat}
>
> org.apache.maven.plugins
> maven-javadoc-plugin
> ${maven.javadoc.plugin.version}
>
>
>
>
> org.apache.ignite.tools.javadoc.IgniteLinkTaglet
>
> org.apache.ignite
> ignite-tools
> ${project.version}
>
>
>
> Ignite ${project.version}
> Ignite ${project.version}
> true
> true
> protected
> true
> false
> false
> ${javadoc.opts}
> {noformat}
> {noformat}
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] ignite-flink-ext 1.0.0-SNAPSHOT FAILURE [ 5.227
> s]
> [INFO] ignite-flume-ext 1.0.0-SNAPSHOT SKIPPED
> [INFO] ignite-pub-sub 2.9.0-SNAPSHOT .. SKIPPED
> [INFO] ignite-spring-boot-autoconfigure 1.0.0-SNAPSHOT SKIPPED
> [INFO] ignite-client-spring-boot-autoconfigure 1.0.0-SNAPSHOT SKIPPED
> [INFO] ignite-zeromq-ext 1.0.0-SNAPSHOT ... SKIPPED
> [INFO] apache-ignite-extensions 1.0.0-SNAPSHOT SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 5.812 s
> [INFO] Finished at: 2020-04-21T13:56:20+03:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-javadoc-plugin:2.10.4:jar (module-javadoc) on
> project ignite-flink-ext: MavenReportException: Error while generating
> Javadoc: Unable to find artifact:groupId = 'org.apache.ignite'
> [ERROR] artifactId = 'ignite-tools'
> [ERROR] version = '1.0.0-SNAPSHOT': Failure to find
> org.apache.ignite:ignite-tools:pom:1.0.0-SNAPSHOT in
> https://h2database.com/m2-repo was cached in the local repository, resolution
> will not be reattempted until the update interval of h2database.com has
> elapsed or updates are forced
> [ERROR]
> [ERROR] org.apache.ignite:ignite-tools:pom:1.0.0-SNAPSHOT
> [ERROR]
> [ERROR] from the specified remote repositories:
> [ERROR] h2database.com (https://h2database.com/m2-repo, releases=false,
> snapshots=true),
> [ERROR] apache.snapshots (http://repository.apache.org/snapshots,
> releases=false, snapshots=true),
> [ERROR] central (https://repo.maven.apache.org/maven2, releases=true,
> snapshots=false)
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12930) DistributedProcess fails node if unable to send single message to coordinator
Maxim Muzafarov created IGNITE-12930:
Summary: DistributedProcess fails node if unable to send single
message to coordinator
Key: IGNITE-12930
URL: https://issues.apache.org/jira/browse/IGNITE-12930
Project: Ignite
Issue Type: Task
Reporter: Maxim Muzafarov
The
[DistributedProcess|https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/util/distributed/DistributedProcess.java]
fails the local node ({{FailureHandler}} CRITICAL_ERROR thrown) if unable to
send a message to the coordinator (e.g. the coordinator fails right before the
single message is sent).
{code:java}
try {
ctx.io().sendToGridTopic(p.crdId,
GridTopic.TOPIC_DISTRIBUTED_PROCESS, singleMsg, SYSTEM_POOL);
}
catch (IgniteCheckedException e) {
log.error("Unable to send message to coordinator.", e);
ctx.failure().process(new FailureContext(CRITICAL_ERROR,
new Exception("Unable to send message to coordinator.",
e)));
}
{code}
h4. Expected behaviour
If the {{ClusterTopologyCheckedException}} occurs need to wait for the
NODE_LEFT event of the coordinator node and re-init the distributed process
future.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12930) DistributedProcess fails node if unable to send single message to coordinator
[
https://issues.apache.org/jira/browse/IGNITE-12930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-12930:
-
Ignite Flags: (was: Docs Required,Release Notes Required)
> DistributedProcess fails node if unable to send single message to coordinator
> -
>
> Key: IGNITE-12930
> URL: https://issues.apache.org/jira/browse/IGNITE-12930
> Project: Ignite
> Issue Type: Task
>Reporter: Maxim Muzafarov
>Priority: Major
>
> The
> [DistributedProcess|https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/util/distributed/DistributedProcess.java]
> fails the local node ({{FailureHandler}} CRITICAL_ERROR thrown) if unable to
> send a message to the coordinator (e.g. the coordinator fails right before
> the single message is sent).
> {code:java}
> try {
> ctx.io().sendToGridTopic(p.crdId,
> GridTopic.TOPIC_DISTRIBUTED_PROCESS, singleMsg, SYSTEM_POOL);
> }
> catch (IgniteCheckedException e) {
> log.error("Unable to send message to coordinator.", e);
> ctx.failure().process(new FailureContext(CRITICAL_ERROR,
> new Exception("Unable to send message to coordinator.",
> e)));
> }
> {code}
> h4. Expected behaviour
> If the {{ClusterTopologyCheckedException}} occurs need to wait for the
> NODE_LEFT event of the coordinator node and re-init the distributed process
> future.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12929) Incorrect setClientMode calls instead of startClientGrid
[
https://issues.apache.org/jira/browse/IGNITE-12929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-12929:
-
Ignite Flags: (was: Docs Required,Release Notes Required)
> Incorrect setClientMode calls instead of startClientGrid
>
>
> Key: IGNITE-12929
> URL: https://issues.apache.org/jira/browse/IGNITE-12929
> Project: Ignite
> Issue Type: Task
>Reporter: Maxim Muzafarov
>Priority: Major
>
> There were some places left after IGNITE-12493 merge where {{setClientMode}}
> instead of {{startClientGrid}}.
> Need to be fixed.
> Examples:
> https://github.com/apache/ignite/blob/master/modules/core/src/test/java/org/apache/ignite/internal/processors/database/IgniteDbAbstractTest.java#L168
> https://github.com/apache/ignite/blob/master/modules/indexing/src/test/java/org/apache/ignite/internal/processors/cache/SqlCacheStartStopTest.java#L81
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12929) Incorrect setClientMode calls instead of startClientGrid
Maxim Muzafarov created IGNITE-12929:
Summary: Incorrect setClientMode calls instead of startClientGrid
Key: IGNITE-12929
URL: https://issues.apache.org/jira/browse/IGNITE-12929
Project: Ignite
Issue Type: Task
Reporter: Maxim Muzafarov
There were some places left after IGNITE-12493 merge where {{setClientMode}}
instead of {{startClientGrid}}.
Need to be fixed.
Examples:
https://github.com/apache/ignite/blob/master/modules/core/src/test/java/org/apache/ignite/internal/processors/database/IgniteDbAbstractTest.java#L168
https://github.com/apache/ignite/blob/master/modules/indexing/src/test/java/org/apache/ignite/internal/processors/cache/SqlCacheStartStopTest.java#L81
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12911) B+Tree Corrupted exception when using a key extracted from a BinaryObject value object --- and SQL enabled.
[
https://issues.apache.org/jira/browse/IGNITE-12911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Korenshteyn updated IGNITE-12911:
---
Attachment: image-2020-04-21-17-16-29-107.png
> B+Tree Corrupted exception when using a key extracted from a BinaryObject
> value object --- and SQL enabled.
> ---
>
> Key: IGNITE-12911
> URL: https://issues.apache.org/jira/browse/IGNITE-12911
> Project: Ignite
> Issue Type: Bug
> Components: cache, sql
>Reporter: Alexander Korenshteyn
>Priority: Blocker
> Fix For: 2.9
>
> Attachments: Employee.java, EmployeeId.java, ServerNode.java,
> image-2020-04-21-17-10-55-797.png, image-2020-04-21-17-11-31-242.png,
> image-2020-04-21-17-16-10-703.png, image-2020-04-21-17-16-29-107.png,
> image-2020-04-21-17-16-46-381.png
>
>
> If a key is part of the value like so:
> class key \{ ... }
> class value
> { private Key key getKey() }
> cache = ignite.cache()*.withKeepBinary()*
> the following scenario yields a B+ Tree exception:
> 1. *Enable SQL via annotations or QueryEntities.*
> key1= new Key()
> value1 = new Value(key1)
> cache.put(key1, value1)
> BinaryObject val2 = cache.get(key1)
> BinaryObject key2 = val2.field("key")
>
> *cache2.put(key2.toBuilder().build(), emp1); // OK!*
>
> *cache.put(key2, emp1); // CRASH!!! CorruptedTreeException: B+Tree
> iscorrupted ...*
> user list:
>
> [http://apache-ignite-users.70518.x6.nabble.com/Ignite-crashes-with-CorruptedTreeException-quot-B-Tree-is-corrupted-quot-on-a-composite-BinaryObjecto-tc32032.html]
> *Reproducer – attached*
>
> his happens because:
> CacheRowAdapter.readFullRow() reads the length
> *int len = PageUtils.getInt(addr,off)*
> *it returns 0 when val2.field("key") is used*
>
> *the data is written correctly in DataPageIO.writeDataPageIO():*
> !image-2020-04-21-17-10-55-797.png!
>
> *but read incorrectly in CacheRowAdapter.readFullRow()*
>
> !image-2020-04-21-17-11-31-242.png!
>
> Exception:
> [2020-04-17 11:24:33,475][ERROR][main][root] Critical system error detected.
> Will be handled accordingly to configured handler
> [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
> super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet
> [SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]],
> failureCtx=FailureContext [type=CRITICAL_ERROR, err=class
> o.a.i.i.processors.cache.persistence.tree.CorruptedTreeException: B+Tree is
> corrupted [pages(groupId, pageId)=[IgniteBiTuple [val1=1258113742,
> val2=844420635164673]], cacheId=1976096430, cacheName=EMPLOYEE,
> indexName=_key_PK, msg=Runtime failure on row: Row@2233cac0[ key:
> model.EmployeeId [idHash=1744523301, hash=674030145, employeeNumber=65348765,
> departmentNumber=123], val: model.Employee [idHash=382762227,
> hash=1627745429, firstName=John, lastName=Smith, id=model.EmployeeId
> [idHash=2021540695, hash=674030145, employeeNumber=65348765,
> departmentNumber=123]] ][ John, Smith
> class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> B+Tree is corrupted [pages(groupId, pageId)=[IgniteBiTuple [val1=1258113742,
> val2=844420635164673]], cacheId=1976096430, cacheName=EMPLOYEE,
> indexName=_key_PK, msg=Runtime failure on row: Row@2233cac0[ key:
> model.EmployeeId [idHash=1744523301, hash=674030145, employeeNumber=65348765,
> departmentNumber=123], val: model.Employee [idHash=382762227,
> hash=1627745429, firstName=John, lastName=Smith, id=model.EmployeeId
> [idHash=2021540695, hash=674030145, employeeNumber=65348765,
> departmentNumber=123]] ][ John, Smith ]]
> at
> org.apache.ignite.internal.processors.query.h2.database.H2Tree.corruptedTreeException(H2Tree.java:836)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doPut(BPlusTree.java:2447)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.putx(BPlusTree.java:2394)
> at
> org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.putx(H2TreeIndex.java:437)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.update(GridH2Table.java:756)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.store(IgniteH2Indexing.java:363)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.store(GridQueryProcessor.java:2016)
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.store(GridCacheQueryManager.java:401)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.finishUpdate(IgniteCacheOffheapManagerImpl.java:2555)
> at
>
[jira] [Updated] (IGNITE-12911) B+Tree Corrupted exception when using a key extracted from a BinaryObject value object --- and SQL enabled.
[
https://issues.apache.org/jira/browse/IGNITE-12911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Korenshteyn updated IGNITE-12911:
---
Description:
If a key is part of the value like so:
class key \{ ... }
class value
{ private Key key getKey() }
cache = ignite.cache()*.withKeepBinary()*
the following scenario yields a B+ Tree exception:
1. *Enable SQL via annotations or QueryEntities.*
key1= new Key()
value1 = new Value(key1)
cache.put(key1, value1)
BinaryObject val2 = cache.get(key1)
BinaryObject key2 = val2.field("key")
*cache2.put(key2.toBuilder().build(), emp1); // OK!*
*cache.put(key2, emp1); // CRASH!!! CorruptedTreeException: B+Tree iscorrupted
...*
user list:
[http://apache-ignite-users.70518.x6.nabble.com/Ignite-crashes-with-CorruptedTreeException-quot-B-Tree-is-corrupted-quot-on-a-composite-BinaryObjecto-tc32032.html]
*Reproducer – attached*
his happens because:
CacheRowAdapter.readFullRow() reads the length
*int len = PageUtils.getInt(addr,off)*
*it returns 0 when val2.field("key") is used*
*the data is written correctly in DataPageIO.writeDataPageIO():*
!image-2020-04-21-17-16-46-381.png!
*but read incorrectly in CacheRowAdapter.readFullRow()*
!image-2020-04-21-17-16-29-107.png!
Exception:
[2020-04-17 11:24:33,475][ERROR][main][root] Critical system error detected.
Will be handled accordingly to configured handler
[hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet
[SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]],
failureCtx=FailureContext [type=CRITICAL_ERROR, err=class
o.a.i.i.processors.cache.persistence.tree.CorruptedTreeException: B+Tree is
corrupted [pages(groupId, pageId)=[IgniteBiTuple [val1=1258113742,
val2=844420635164673]], cacheId=1976096430, cacheName=EMPLOYEE,
indexName=_key_PK, msg=Runtime failure on row: Row@2233cac0[ key:
model.EmployeeId [idHash=1744523301, hash=674030145, employeeNumber=65348765,
departmentNumber=123], val: model.Employee [idHash=382762227, hash=1627745429,
firstName=John, lastName=Smith, id=model.EmployeeId [idHash=2021540695,
hash=674030145, employeeNumber=65348765, departmentNumber=123]] ][ John, Smith
class
org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
B+Tree is corrupted [pages(groupId, pageId)=[IgniteBiTuple [val1=1258113742,
val2=844420635164673]], cacheId=1976096430, cacheName=EMPLOYEE,
indexName=_key_PK, msg=Runtime failure on row: Row@2233cac0[ key:
model.EmployeeId [idHash=1744523301, hash=674030145, employeeNumber=65348765,
departmentNumber=123], val: model.Employee [idHash=382762227, hash=1627745429,
firstName=John, lastName=Smith, id=model.EmployeeId [idHash=2021540695,
hash=674030145, employeeNumber=65348765, departmentNumber=123]] ][ John, Smith
]]
at
org.apache.ignite.internal.processors.query.h2.database.H2Tree.corruptedTreeException(H2Tree.java:836)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doPut(BPlusTree.java:2447)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.putx(BPlusTree.java:2394)
at
org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.putx(H2TreeIndex.java:437)
at
org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.update(GridH2Table.java:756)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.store(IgniteH2Indexing.java:363)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.store(GridQueryProcessor.java:2016)
at
org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.store(GridCacheQueryManager.java:401)
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.finishUpdate(IgniteCacheOffheapManagerImpl.java:2555)
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke0(IgniteCacheOffheapManagerImpl.java:1664)
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:1639)
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.invoke(IgniteCacheOffheapManagerImpl.java:436)
at
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerUpdate(GridCacheMapEntry.java:2311)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateSingle(GridDhtAtomicCache.java:2593)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update(GridDhtAtomicCache.java:2053)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1871)
at
[jira] [Updated] (IGNITE-12911) B+Tree Corrupted exception when using a key extracted from a BinaryObject value object --- and SQL enabled.
[
https://issues.apache.org/jira/browse/IGNITE-12911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Korenshteyn updated IGNITE-12911:
---
Attachment: image-2020-04-21-17-16-10-703.png
> B+Tree Corrupted exception when using a key extracted from a BinaryObject
> value object --- and SQL enabled.
> ---
>
> Key: IGNITE-12911
> URL: https://issues.apache.org/jira/browse/IGNITE-12911
> Project: Ignite
> Issue Type: Bug
> Components: cache, sql
>Reporter: Alexander Korenshteyn
>Priority: Blocker
> Fix For: 2.9
>
> Attachments: Employee.java, EmployeeId.java, ServerNode.java,
> image-2020-04-21-17-10-55-797.png, image-2020-04-21-17-11-31-242.png,
> image-2020-04-21-17-16-10-703.png, image-2020-04-21-17-16-29-107.png,
> image-2020-04-21-17-16-46-381.png
>
>
> If a key is part of the value like so:
> class key \{ ... }
> class value
> { private Key key getKey() }
> cache = ignite.cache()*.withKeepBinary()*
> the following scenario yields a B+ Tree exception:
> 1. *Enable SQL via annotations or QueryEntities.*
> key1= new Key()
> value1 = new Value(key1)
> cache.put(key1, value1)
> BinaryObject val2 = cache.get(key1)
> BinaryObject key2 = val2.field("key")
>
> *cache2.put(key2.toBuilder().build(), emp1); // OK!*
>
> *cache.put(key2, emp1); // CRASH!!! CorruptedTreeException: B+Tree
> iscorrupted ...*
> user list:
>
> [http://apache-ignite-users.70518.x6.nabble.com/Ignite-crashes-with-CorruptedTreeException-quot-B-Tree-is-corrupted-quot-on-a-composite-BinaryObjecto-tc32032.html]
> *Reproducer – attached*
>
> his happens because:
> CacheRowAdapter.readFullRow() reads the length
> *int len = PageUtils.getInt(addr,off)*
> *it returns 0 when val2.field("key") is used*
>
> *the data is written correctly in DataPageIO.writeDataPageIO():*
> !image-2020-04-21-17-10-55-797.png!
>
> *but read incorrectly in CacheRowAdapter.readFullRow()*
>
> !image-2020-04-21-17-11-31-242.png!
>
> Exception:
> [2020-04-17 11:24:33,475][ERROR][main][root] Critical system error detected.
> Will be handled accordingly to configured handler
> [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
> super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet
> [SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]],
> failureCtx=FailureContext [type=CRITICAL_ERROR, err=class
> o.a.i.i.processors.cache.persistence.tree.CorruptedTreeException: B+Tree is
> corrupted [pages(groupId, pageId)=[IgniteBiTuple [val1=1258113742,
> val2=844420635164673]], cacheId=1976096430, cacheName=EMPLOYEE,
> indexName=_key_PK, msg=Runtime failure on row: Row@2233cac0[ key:
> model.EmployeeId [idHash=1744523301, hash=674030145, employeeNumber=65348765,
> departmentNumber=123], val: model.Employee [idHash=382762227,
> hash=1627745429, firstName=John, lastName=Smith, id=model.EmployeeId
> [idHash=2021540695, hash=674030145, employeeNumber=65348765,
> departmentNumber=123]] ][ John, Smith
> class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> B+Tree is corrupted [pages(groupId, pageId)=[IgniteBiTuple [val1=1258113742,
> val2=844420635164673]], cacheId=1976096430, cacheName=EMPLOYEE,
> indexName=_key_PK, msg=Runtime failure on row: Row@2233cac0[ key:
> model.EmployeeId [idHash=1744523301, hash=674030145, employeeNumber=65348765,
> departmentNumber=123], val: model.Employee [idHash=382762227,
> hash=1627745429, firstName=John, lastName=Smith, id=model.EmployeeId
> [idHash=2021540695, hash=674030145, employeeNumber=65348765,
> departmentNumber=123]] ][ John, Smith ]]
> at
> org.apache.ignite.internal.processors.query.h2.database.H2Tree.corruptedTreeException(H2Tree.java:836)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doPut(BPlusTree.java:2447)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.putx(BPlusTree.java:2394)
> at
> org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.putx(H2TreeIndex.java:437)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.update(GridH2Table.java:756)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.store(IgniteH2Indexing.java:363)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.store(GridQueryProcessor.java:2016)
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.store(GridCacheQueryManager.java:401)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.finishUpdate(IgniteCacheOffheapManagerImpl.java:2555)
> at
>
[jira] [Updated] (IGNITE-12911) B+Tree Corrupted exception when using a key extracted from a BinaryObject value object --- and SQL enabled.
[
https://issues.apache.org/jira/browse/IGNITE-12911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Korenshteyn updated IGNITE-12911:
---
Attachment: image-2020-04-21-17-16-46-381.png
> B+Tree Corrupted exception when using a key extracted from a BinaryObject
> value object --- and SQL enabled.
> ---
>
> Key: IGNITE-12911
> URL: https://issues.apache.org/jira/browse/IGNITE-12911
> Project: Ignite
> Issue Type: Bug
> Components: cache, sql
>Reporter: Alexander Korenshteyn
>Priority: Blocker
> Fix For: 2.9
>
> Attachments: Employee.java, EmployeeId.java, ServerNode.java,
> image-2020-04-21-17-10-55-797.png, image-2020-04-21-17-11-31-242.png,
> image-2020-04-21-17-16-10-703.png, image-2020-04-21-17-16-29-107.png,
> image-2020-04-21-17-16-46-381.png
>
>
> If a key is part of the value like so:
> class key \{ ... }
> class value
> { private Key key getKey() }
> cache = ignite.cache()*.withKeepBinary()*
> the following scenario yields a B+ Tree exception:
> 1. *Enable SQL via annotations or QueryEntities.*
> key1= new Key()
> value1 = new Value(key1)
> cache.put(key1, value1)
> BinaryObject val2 = cache.get(key1)
> BinaryObject key2 = val2.field("key")
>
> *cache2.put(key2.toBuilder().build(), emp1); // OK!*
>
> *cache.put(key2, emp1); // CRASH!!! CorruptedTreeException: B+Tree
> iscorrupted ...*
> user list:
>
> [http://apache-ignite-users.70518.x6.nabble.com/Ignite-crashes-with-CorruptedTreeException-quot-B-Tree-is-corrupted-quot-on-a-composite-BinaryObjecto-tc32032.html]
> *Reproducer – attached*
>
> his happens because:
> CacheRowAdapter.readFullRow() reads the length
> *int len = PageUtils.getInt(addr,off)*
> *it returns 0 when val2.field("key") is used*
>
> *the data is written correctly in DataPageIO.writeDataPageIO():*
> !image-2020-04-21-17-10-55-797.png!
>
> *but read incorrectly in CacheRowAdapter.readFullRow()*
>
> !image-2020-04-21-17-11-31-242.png!
>
> Exception:
> [2020-04-17 11:24:33,475][ERROR][main][root] Critical system error detected.
> Will be handled accordingly to configured handler
> [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
> super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet
> [SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]],
> failureCtx=FailureContext [type=CRITICAL_ERROR, err=class
> o.a.i.i.processors.cache.persistence.tree.CorruptedTreeException: B+Tree is
> corrupted [pages(groupId, pageId)=[IgniteBiTuple [val1=1258113742,
> val2=844420635164673]], cacheId=1976096430, cacheName=EMPLOYEE,
> indexName=_key_PK, msg=Runtime failure on row: Row@2233cac0[ key:
> model.EmployeeId [idHash=1744523301, hash=674030145, employeeNumber=65348765,
> departmentNumber=123], val: model.Employee [idHash=382762227,
> hash=1627745429, firstName=John, lastName=Smith, id=model.EmployeeId
> [idHash=2021540695, hash=674030145, employeeNumber=65348765,
> departmentNumber=123]] ][ John, Smith
> class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> B+Tree is corrupted [pages(groupId, pageId)=[IgniteBiTuple [val1=1258113742,
> val2=844420635164673]], cacheId=1976096430, cacheName=EMPLOYEE,
> indexName=_key_PK, msg=Runtime failure on row: Row@2233cac0[ key:
> model.EmployeeId [idHash=1744523301, hash=674030145, employeeNumber=65348765,
> departmentNumber=123], val: model.Employee [idHash=382762227,
> hash=1627745429, firstName=John, lastName=Smith, id=model.EmployeeId
> [idHash=2021540695, hash=674030145, employeeNumber=65348765,
> departmentNumber=123]] ][ John, Smith ]]
> at
> org.apache.ignite.internal.processors.query.h2.database.H2Tree.corruptedTreeException(H2Tree.java:836)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doPut(BPlusTree.java:2447)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.putx(BPlusTree.java:2394)
> at
> org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.putx(H2TreeIndex.java:437)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.update(GridH2Table.java:756)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.store(IgniteH2Indexing.java:363)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.store(GridQueryProcessor.java:2016)
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.store(GridCacheQueryManager.java:401)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.finishUpdate(IgniteCacheOffheapManagerImpl.java:2555)
> at
>
[jira] [Commented] (IGNITE-12911) B+Tree Corrupted exception when using a key extracted from a BinaryObject value object --- and SQL enabled.
[
https://issues.apache.org/jira/browse/IGNITE-12911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17089076#comment-17089076
]
Alexander Korenshteyn commented on IGNITE-12911:
updated details – this happens when the key is retrieved from a BinaryObject —
it is correctly written into memory – but then
when the CacheRowAdapter reads the key back – the length field is corrupted –
reads 0 hence the error.
looking to see how to fix this.
> B+Tree Corrupted exception when using a key extracted from a BinaryObject
> value object --- and SQL enabled.
> ---
>
> Key: IGNITE-12911
> URL: https://issues.apache.org/jira/browse/IGNITE-12911
> Project: Ignite
> Issue Type: Bug
> Components: cache, sql
>Reporter: Alexander Korenshteyn
>Priority: Blocker
> Fix For: 2.9
>
> Attachments: Employee.java, EmployeeId.java, ServerNode.java,
> image-2020-04-21-17-10-55-797.png, image-2020-04-21-17-11-31-242.png
>
>
> If a key is part of the value like so:
> class key \{ ... }
> class value
> { private Key key getKey() }
> cache = ignite.cache()*.withKeepBinary()*
> the following scenario yields a B+ Tree exception:
> 1. *Enable SQL via annotations or QueryEntities.*
> key1= new Key()
> value1 = new Value(key1)
> cache.put(key1, value1)
> BinaryObject val2 = cache.get(key1)
> BinaryObject key2 = val2.field("key")
>
> *cache2.put(key2.toBuilder().build(), emp1); // OK!*
>
> *cache.put(key2, emp1); // CRASH!!! CorruptedTreeException: B+Tree
> iscorrupted ...*
> user list:
>
> [http://apache-ignite-users.70518.x6.nabble.com/Ignite-crashes-with-CorruptedTreeException-quot-B-Tree-is-corrupted-quot-on-a-composite-BinaryObjecto-tc32032.html]
> *Reproducer – attached*
>
> his happens because:
> CacheRowAdapter.readFullRow() reads the length
> *int len = PageUtils.getInt(addr,off)*
> *it returns 0 when val2.field("key") is used*
>
> *the data is written correctly in DataPageIO.writeDataPageIO():*
> !image-2020-04-21-17-10-55-797.png!
>
> *but read incorrectly in CacheRowAdapter.readFullRow()*
>
> !image-2020-04-21-17-11-31-242.png!
>
> Exception:
> [2020-04-17 11:24:33,475][ERROR][main][root] Critical system error detected.
> Will be handled accordingly to configured handler
> [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
> super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet
> [SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]],
> failureCtx=FailureContext [type=CRITICAL_ERROR, err=class
> o.a.i.i.processors.cache.persistence.tree.CorruptedTreeException: B+Tree is
> corrupted [pages(groupId, pageId)=[IgniteBiTuple [val1=1258113742,
> val2=844420635164673]], cacheId=1976096430, cacheName=EMPLOYEE,
> indexName=_key_PK, msg=Runtime failure on row: Row@2233cac0[ key:
> model.EmployeeId [idHash=1744523301, hash=674030145, employeeNumber=65348765,
> departmentNumber=123], val: model.Employee [idHash=382762227,
> hash=1627745429, firstName=John, lastName=Smith, id=model.EmployeeId
> [idHash=2021540695, hash=674030145, employeeNumber=65348765,
> departmentNumber=123]] ][ John, Smith
> class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> B+Tree is corrupted [pages(groupId, pageId)=[IgniteBiTuple [val1=1258113742,
> val2=844420635164673]], cacheId=1976096430, cacheName=EMPLOYEE,
> indexName=_key_PK, msg=Runtime failure on row: Row@2233cac0[ key:
> model.EmployeeId [idHash=1744523301, hash=674030145, employeeNumber=65348765,
> departmentNumber=123], val: model.Employee [idHash=382762227,
> hash=1627745429, firstName=John, lastName=Smith, id=model.EmployeeId
> [idHash=2021540695, hash=674030145, employeeNumber=65348765,
> departmentNumber=123]] ][ John, Smith ]]
> at
> org.apache.ignite.internal.processors.query.h2.database.H2Tree.corruptedTreeException(H2Tree.java:836)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doPut(BPlusTree.java:2447)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.putx(BPlusTree.java:2394)
> at
> org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.putx(H2TreeIndex.java:437)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.update(GridH2Table.java:756)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.store(IgniteH2Indexing.java:363)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.store(GridQueryProcessor.java:2016)
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.store(GridCacheQueryManager.java:401)
> at
>
[jira] [Updated] (IGNITE-12911) B+Tree Corrupted exception when using a key extracted from a BinaryObject value object --- and SQL enabled.
[
https://issues.apache.org/jira/browse/IGNITE-12911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Korenshteyn updated IGNITE-12911:
---
Description:
If a key is part of the value like so:
class key \{ ... }
class value
{ private Key key getKey() }
cache = ignite.cache()*.withKeepBinary()*
the following scenario yields a B+ Tree exception:
1. *Enable SQL via annotations or QueryEntities.*
key1= new Key()
value1 = new Value(key1)
cache.put(key1, value1)
BinaryObject val2 = cache.get(key1)
BinaryObject key2 = val2.field("key")
*cache2.put(key2.toBuilder().build(), emp1); // OK!*
*cache.put(key2, emp1); // CRASH!!! CorruptedTreeException: B+Tree iscorrupted
...*
user list:
[http://apache-ignite-users.70518.x6.nabble.com/Ignite-crashes-with-CorruptedTreeException-quot-B-Tree-is-corrupted-quot-on-a-composite-BinaryObjecto-tc32032.html]
*Reproducer – attached*
his happens because:
CacheRowAdapter.readFullRow() reads the length
*int len = PageUtils.getInt(addr,off)*
*it returns 0 when val2.field("key") is used*
*the data is written correctly in DataPageIO.writeDataPageIO():*
!image-2020-04-21-17-10-55-797.png!
*but read incorrectly in CacheRowAdapter.readFullRow()*
!image-2020-04-21-17-11-31-242.png!
Exception:
[2020-04-17 11:24:33,475][ERROR][main][root] Critical system error detected.
Will be handled accordingly to configured handler
[hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet
[SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]],
failureCtx=FailureContext [type=CRITICAL_ERROR, err=class
o.a.i.i.processors.cache.persistence.tree.CorruptedTreeException: B+Tree is
corrupted [pages(groupId, pageId)=[IgniteBiTuple [val1=1258113742,
val2=844420635164673]], cacheId=1976096430, cacheName=EMPLOYEE,
indexName=_key_PK, msg=Runtime failure on row: Row@2233cac0[ key:
model.EmployeeId [idHash=1744523301, hash=674030145, employeeNumber=65348765,
departmentNumber=123], val: model.Employee [idHash=382762227, hash=1627745429,
firstName=John, lastName=Smith, id=model.EmployeeId [idHash=2021540695,
hash=674030145, employeeNumber=65348765, departmentNumber=123]] ][ John, Smith
class
org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
B+Tree is corrupted [pages(groupId, pageId)=[IgniteBiTuple [val1=1258113742,
val2=844420635164673]], cacheId=1976096430, cacheName=EMPLOYEE,
indexName=_key_PK, msg=Runtime failure on row: Row@2233cac0[ key:
model.EmployeeId [idHash=1744523301, hash=674030145, employeeNumber=65348765,
departmentNumber=123], val: model.Employee [idHash=382762227, hash=1627745429,
firstName=John, lastName=Smith, id=model.EmployeeId [idHash=2021540695,
hash=674030145, employeeNumber=65348765, departmentNumber=123]] ][ John, Smith
]]
at
org.apache.ignite.internal.processors.query.h2.database.H2Tree.corruptedTreeException(H2Tree.java:836)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doPut(BPlusTree.java:2447)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.putx(BPlusTree.java:2394)
at
org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.putx(H2TreeIndex.java:437)
at
org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.update(GridH2Table.java:756)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.store(IgniteH2Indexing.java:363)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.store(GridQueryProcessor.java:2016)
at
org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.store(GridCacheQueryManager.java:401)
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.finishUpdate(IgniteCacheOffheapManagerImpl.java:2555)
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke0(IgniteCacheOffheapManagerImpl.java:1664)
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:1639)
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.invoke(IgniteCacheOffheapManagerImpl.java:436)
at
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerUpdate(GridCacheMapEntry.java:2311)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateSingle(GridDhtAtomicCache.java:2593)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update(GridDhtAtomicCache.java:2053)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1871)
at
[jira] [Updated] (IGNITE-12911) B+Tree Corrupted exception when using a key extracted from a BinaryObject value object --- and SQL enabled.
[
https://issues.apache.org/jira/browse/IGNITE-12911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Korenshteyn updated IGNITE-12911:
---
Attachment: image-2020-04-21-17-11-31-242.png
> B+Tree Corrupted exception when using a key extracted from a BinaryObject
> value object --- and SQL enabled.
> ---
>
> Key: IGNITE-12911
> URL: https://issues.apache.org/jira/browse/IGNITE-12911
> Project: Ignite
> Issue Type: Bug
> Components: cache, sql
>Reporter: Alexander Korenshteyn
>Priority: Blocker
> Fix For: 2.9
>
> Attachments: Employee.java, EmployeeId.java, ServerNode.java,
> image-2020-04-21-17-10-55-797.png, image-2020-04-21-17-11-31-242.png
>
>
> If a key is part of the value like so:
> class key \{ ... }
> class value {
> private Key key
> getKey()
> }
> cache = ignite.cache()*.withKeepBinary()*
> the following scenario yields a B+ Tree exception:
> 1. *Enable SQL via annotations or QueryEntities.*
> key1= new Key()
> value1 = new Value(key1)
> cache.put(key1, value1)
> BinaryObject val2 = cache.get(key1)
> BinaryObject key2 = val2.field("key")
> *cache.put(key2, emp1); // CRASH!!! CorruptedTreeException: B+Tree
> iscorrupted ...*
> user list:
> [http://apache-ignite-users.70518.x6.nabble.com/Ignite-crashes-with-CorruptedTreeException-quot-B-Tree-is-corrupted-quot-on-a-composite-BinaryObjecto-tc32032.html]
> *Reproducer – attached*
>
> Exception:
> [2020-04-17 11:24:33,475][ERROR][main][root] Critical system error detected.
> Will be handled accordingly to configured handler
> [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
> super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet
> [SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]],
> failureCtx=FailureContext [type=CRITICAL_ERROR, err=class
> o.a.i.i.processors.cache.persistence.tree.CorruptedTreeException: B+Tree is
> corrupted [pages(groupId, pageId)=[IgniteBiTuple [val1=1258113742,
> val2=844420635164673]], cacheId=1976096430, cacheName=EMPLOYEE,
> indexName=_key_PK, msg=Runtime failure on row: Row@2233cac0[ key:
> model.EmployeeId [idHash=1744523301, hash=674030145, employeeNumber=65348765,
> departmentNumber=123], val: model.Employee [idHash=382762227,
> hash=1627745429, firstName=John, lastName=Smith, id=model.EmployeeId
> [idHash=2021540695, hash=674030145, employeeNumber=65348765,
> departmentNumber=123]] ][ John, Smith
> class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> B+Tree is corrupted [pages(groupId, pageId)=[IgniteBiTuple [val1=1258113742,
> val2=844420635164673]], cacheId=1976096430, cacheName=EMPLOYEE,
> indexName=_key_PK, msg=Runtime failure on row: Row@2233cac0[ key:
> model.EmployeeId [idHash=1744523301, hash=674030145, employeeNumber=65348765,
> departmentNumber=123], val: model.Employee [idHash=382762227,
> hash=1627745429, firstName=John, lastName=Smith, id=model.EmployeeId
> [idHash=2021540695, hash=674030145, employeeNumber=65348765,
> departmentNumber=123]] ][ John, Smith ]]
> at
> org.apache.ignite.internal.processors.query.h2.database.H2Tree.corruptedTreeException(H2Tree.java:836)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doPut(BPlusTree.java:2447)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.putx(BPlusTree.java:2394)
> at
> org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.putx(H2TreeIndex.java:437)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.update(GridH2Table.java:756)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.store(IgniteH2Indexing.java:363)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.store(GridQueryProcessor.java:2016)
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.store(GridCacheQueryManager.java:401)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.finishUpdate(IgniteCacheOffheapManagerImpl.java:2555)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke0(IgniteCacheOffheapManagerImpl.java:1664)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:1639)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.invoke(IgniteCacheOffheapManagerImpl.java:436)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerUpdate(GridCacheMapEntry.java:2311)
> at
>
[jira] [Updated] (IGNITE-12911) B+Tree Corrupted exception when using a key extracted from a BinaryObject value object --- and SQL enabled.
[
https://issues.apache.org/jira/browse/IGNITE-12911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Korenshteyn updated IGNITE-12911:
---
Attachment: image-2020-04-21-17-10-55-797.png
> B+Tree Corrupted exception when using a key extracted from a BinaryObject
> value object --- and SQL enabled.
> ---
>
> Key: IGNITE-12911
> URL: https://issues.apache.org/jira/browse/IGNITE-12911
> Project: Ignite
> Issue Type: Bug
> Components: cache, sql
>Reporter: Alexander Korenshteyn
>Priority: Blocker
> Fix For: 2.9
>
> Attachments: Employee.java, EmployeeId.java, ServerNode.java,
> image-2020-04-21-17-10-55-797.png
>
>
> If a key is part of the value like so:
> class key \{ ... }
> class value {
> private Key key
> getKey()
> }
> cache = ignite.cache()*.withKeepBinary()*
> the following scenario yields a B+ Tree exception:
> 1. *Enable SQL via annotations or QueryEntities.*
> key1= new Key()
> value1 = new Value(key1)
> cache.put(key1, value1)
> BinaryObject val2 = cache.get(key1)
> BinaryObject key2 = val2.field("key")
> *cache.put(key2, emp1); // CRASH!!! CorruptedTreeException: B+Tree
> iscorrupted ...*
> user list:
> [http://apache-ignite-users.70518.x6.nabble.com/Ignite-crashes-with-CorruptedTreeException-quot-B-Tree-is-corrupted-quot-on-a-composite-BinaryObjecto-tc32032.html]
> *Reproducer – attached*
>
> Exception:
> [2020-04-17 11:24:33,475][ERROR][main][root] Critical system error detected.
> Will be handled accordingly to configured handler
> [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
> super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet
> [SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]],
> failureCtx=FailureContext [type=CRITICAL_ERROR, err=class
> o.a.i.i.processors.cache.persistence.tree.CorruptedTreeException: B+Tree is
> corrupted [pages(groupId, pageId)=[IgniteBiTuple [val1=1258113742,
> val2=844420635164673]], cacheId=1976096430, cacheName=EMPLOYEE,
> indexName=_key_PK, msg=Runtime failure on row: Row@2233cac0[ key:
> model.EmployeeId [idHash=1744523301, hash=674030145, employeeNumber=65348765,
> departmentNumber=123], val: model.Employee [idHash=382762227,
> hash=1627745429, firstName=John, lastName=Smith, id=model.EmployeeId
> [idHash=2021540695, hash=674030145, employeeNumber=65348765,
> departmentNumber=123]] ][ John, Smith
> class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> B+Tree is corrupted [pages(groupId, pageId)=[IgniteBiTuple [val1=1258113742,
> val2=844420635164673]], cacheId=1976096430, cacheName=EMPLOYEE,
> indexName=_key_PK, msg=Runtime failure on row: Row@2233cac0[ key:
> model.EmployeeId [idHash=1744523301, hash=674030145, employeeNumber=65348765,
> departmentNumber=123], val: model.Employee [idHash=382762227,
> hash=1627745429, firstName=John, lastName=Smith, id=model.EmployeeId
> [idHash=2021540695, hash=674030145, employeeNumber=65348765,
> departmentNumber=123]] ][ John, Smith ]]
> at
> org.apache.ignite.internal.processors.query.h2.database.H2Tree.corruptedTreeException(H2Tree.java:836)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doPut(BPlusTree.java:2447)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.putx(BPlusTree.java:2394)
> at
> org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.putx(H2TreeIndex.java:437)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.update(GridH2Table.java:756)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.store(IgniteH2Indexing.java:363)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.store(GridQueryProcessor.java:2016)
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.store(GridCacheQueryManager.java:401)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.finishUpdate(IgniteCacheOffheapManagerImpl.java:2555)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke0(IgniteCacheOffheapManagerImpl.java:1664)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:1639)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.invoke(IgniteCacheOffheapManagerImpl.java:436)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerUpdate(GridCacheMapEntry.java:2311)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateSingle(GridDhtAtomicCache.java:2593)
> at
>
[jira] [Updated] (IGNITE-12911) B+Tree Corrupted exception when using a key extracted from a BinaryObject value object --- and SQL enabled.
[
https://issues.apache.org/jira/browse/IGNITE-12911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Korenshteyn updated IGNITE-12911:
---
Summary: B+Tree Corrupted exception when using a key extracted from a
BinaryObject value object --- and SQL enabled. (was: B+Tree Corrupted
exception when using a key extracted from a value object --- and SQL enabled.)
> B+Tree Corrupted exception when using a key extracted from a BinaryObject
> value object --- and SQL enabled.
> ---
>
> Key: IGNITE-12911
> URL: https://issues.apache.org/jira/browse/IGNITE-12911
> Project: Ignite
> Issue Type: Bug
> Components: cache, sql
>Reporter: Alexander Korenshteyn
>Priority: Blocker
> Fix For: 2.9
>
> Attachments: Employee.java, EmployeeId.java, ServerNode.java
>
>
> If a key is part of the value like so:
> class key \{ ... }
> class value {
> private Key key
> getKey()
> }
> cache = ignite.cache()*.withKeepBinary()*
> the following scenario yields a B+ Tree exception:
> 1. *Enable SQL via annotations or QueryEntities.*
> key1= new Key()
> value1 = new Value(key1)
> cache.put(key1, value1)
> BinaryObject val2 = cache.get(key1)
> BinaryObject key2 = val2.field("key")
> *cache.put(key2, emp1); // CRASH!!! CorruptedTreeException: B+Tree
> iscorrupted ...*
> user list:
> [http://apache-ignite-users.70518.x6.nabble.com/Ignite-crashes-with-CorruptedTreeException-quot-B-Tree-is-corrupted-quot-on-a-composite-BinaryObjecto-tc32032.html]
> *Reproducer – attached*
>
> Exception:
> [2020-04-17 11:24:33,475][ERROR][main][root] Critical system error detected.
> Will be handled accordingly to configured handler
> [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
> super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet
> [SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]],
> failureCtx=FailureContext [type=CRITICAL_ERROR, err=class
> o.a.i.i.processors.cache.persistence.tree.CorruptedTreeException: B+Tree is
> corrupted [pages(groupId, pageId)=[IgniteBiTuple [val1=1258113742,
> val2=844420635164673]], cacheId=1976096430, cacheName=EMPLOYEE,
> indexName=_key_PK, msg=Runtime failure on row: Row@2233cac0[ key:
> model.EmployeeId [idHash=1744523301, hash=674030145, employeeNumber=65348765,
> departmentNumber=123], val: model.Employee [idHash=382762227,
> hash=1627745429, firstName=John, lastName=Smith, id=model.EmployeeId
> [idHash=2021540695, hash=674030145, employeeNumber=65348765,
> departmentNumber=123]] ][ John, Smith
> class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> B+Tree is corrupted [pages(groupId, pageId)=[IgniteBiTuple [val1=1258113742,
> val2=844420635164673]], cacheId=1976096430, cacheName=EMPLOYEE,
> indexName=_key_PK, msg=Runtime failure on row: Row@2233cac0[ key:
> model.EmployeeId [idHash=1744523301, hash=674030145, employeeNumber=65348765,
> departmentNumber=123], val: model.Employee [idHash=382762227,
> hash=1627745429, firstName=John, lastName=Smith, id=model.EmployeeId
> [idHash=2021540695, hash=674030145, employeeNumber=65348765,
> departmentNumber=123]] ][ John, Smith ]]
> at
> org.apache.ignite.internal.processors.query.h2.database.H2Tree.corruptedTreeException(H2Tree.java:836)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doPut(BPlusTree.java:2447)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.putx(BPlusTree.java:2394)
> at
> org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.putx(H2TreeIndex.java:437)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.update(GridH2Table.java:756)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.store(IgniteH2Indexing.java:363)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.store(GridQueryProcessor.java:2016)
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.store(GridCacheQueryManager.java:401)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.finishUpdate(IgniteCacheOffheapManagerImpl.java:2555)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke0(IgniteCacheOffheapManagerImpl.java:1664)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:1639)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.invoke(IgniteCacheOffheapManagerImpl.java:436)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerUpdate(GridCacheMapEntry.java:2311)
> at
>
[jira] [Commented] (IGNITE-12918) .NET: Add Travis job
[ https://issues.apache.org/jira/browse/IGNITE-12918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17089064#comment-17089064 ] Maxim Muzafarov commented on IGNITE-12918: -- [~ptupitsyn] Actually I'm not an expert with Travis configuration :-) Let's revert changes from the master branch and test a new configuration locally without the rush? Tests can be done locally with docker: https://stackoverflow.com/questions/21053657/how-to-run-travis-ci-locally or I've configured Travis for my own Ignite fork. I can help you to fix the configuration to run dotnet a bit later. > .NET: Add Travis job > > > Key: IGNITE-12918 > URL: https://issues.apache.org/jira/browse/IGNITE-12918 > Project: Ignite > Issue Type: Improvement > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Add .NET build to .travis.yml -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12918) .NET: Add Travis job
[ https://issues.apache.org/jira/browse/IGNITE-12918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17089004#comment-17089004 ] Pavel Tupitsyn commented on IGNITE-12918: - [~mmuzaf] please check, is this ok? https://github.com/apache/ignite/pull/7710 P.S.: I've pushed 1 commit, in 1 PR, but there are 2 builds. Can we fix this? > .NET: Add Travis job > > > Key: IGNITE-12918 > URL: https://issues.apache.org/jira/browse/IGNITE-12918 > Project: Ignite > Issue Type: Improvement > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Add .NET build to .travis.yml -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12928) CacheMetricsMXBean does not provide proper descriptions for rebalancing attributes
[ https://issues.apache.org/jira/browse/IGNITE-12928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Makedonskaya updated IGNITE-12928: Ignite Flags: (was: Docs Required,Release Notes Required) > CacheMetricsMXBean does not provide proper descriptions for rebalancing > attributes > -- > > Key: IGNITE-12928 > URL: https://issues.apache.org/jira/browse/IGNITE-12928 > Project: Ignite > Issue Type: Bug >Reporter: Maria Makedonskaya >Assignee: Maria Makedonskaya >Priority: Minor > > When querying MBean info via JMX one expects to get meaningful descriptions > for all attributes. > However, for bean CacheMetricsMXBean, no descriptions provided for following > attributes, default value 'Attribute exposed for management' returned instead: > * EstimatedRebalancingFinishTime > * KeysToRebalanceLeft > * RebalancingBytesRate > * RebalancingKeysRate > * RebalancingPartitionsCount > * RebalancingStartTime > * TotalPartitionsCount -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12928) CacheMetricsMXBean does not provide proper descriptions for rebalancing attributes
Maria Makedonskaya created IGNITE-12928: --- Summary: CacheMetricsMXBean does not provide proper descriptions for rebalancing attributes Key: IGNITE-12928 URL: https://issues.apache.org/jira/browse/IGNITE-12928 Project: Ignite Issue Type: Bug Reporter: Maria Makedonskaya Assignee: Maria Makedonskaya When querying MBean info via JMX one expects to get meaningful descriptions for all attributes. However, for bean CacheMetricsMXBean, no descriptions provided for following attributes, default value 'Attribute exposed for management' returned instead: * EstimatedRebalancingFinishTime * KeysToRebalanceLeft * RebalancingBytesRate * RebalancingKeysRate * RebalancingPartitionsCount * RebalancingStartTime * TotalPartitionsCount -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12918) .NET: Add Travis job
[ https://issues.apache.org/jira/browse/IGNITE-12918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17088893#comment-17088893 ] Pavel Tupitsyn commented on IGNITE-12918: - [~mmuzaf] good catch, I'll have a look > .NET: Add Travis job > > > Key: IGNITE-12918 > URL: https://issues.apache.org/jira/browse/IGNITE-12918 > Project: Ignite > Issue Type: Improvement > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Add .NET build to .travis.yml -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-12450) Transaction operations metrics
[ https://issues.apache.org/jira/browse/IGNITE-12450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov resolved IGNITE-12450. -- Resolution: Fixed Cherry-picked to 2.8.1 > Transaction operations metrics > -- > > Key: IGNITE-12450 > URL: https://issues.apache.org/jira/browse/IGNITE-12450 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.7.6 >Reporter: Nikolay Izhikov >Assignee: Amelchev Nikita >Priority: Blocker > Labels: IEP-35 > Fix For: 2.8.1 > > Time Spent: 10m > Remaining Estimate: 0h > > We should add histogram metrics that measure tx.commit and tx.rollback time. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12745) Compute job system view
[ https://issues.apache.org/jira/browse/IGNITE-12745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17088842#comment-17088842 ] Nikolay Izhikov commented on IGNITE-12745: -- Cherry-picked to 2.8.1 > Compute job system view > --- > > Key: IGNITE-12745 > URL: https://issues.apache.org/jira/browse/IGNITE-12745 > Project: Ignite > Issue Type: Sub-task >Affects Versions: 2.7.6 >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: IEP-35 > Fix For: 2.9, 2.8.1 > > Time Spent: 3h 40m > Remaining Estimate: 0h > > ComputeTaskView shows compute tasks that was started(initiated) on the local > node. > We need to introduce another view that will show compute jobs - jobs that > executing on the local node but was initiated on some remote node. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12676) .NET: Add partition-based AffinityCall and AffinityRun overloads
[ https://issues.apache.org/jira/browse/IGNITE-12676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17088830#comment-17088830 ] Pavel Tupitsyn commented on IGNITE-12676: - Merged to master: 2f64b7a96b5ff3cc2e18fdb850f9a6f65a962d1f > .NET: Add partition-based AffinityCall and AffinityRun overloads > > > Key: IGNITE-12676 > URL: https://issues.apache.org/jira/browse/IGNITE-12676 > Project: Ignite > Issue Type: Improvement > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: .NET > Time Spent: 10m > Remaining Estimate: 0h > > Add partition-based AffinityCall and AffinityRun overloads to ICompute.See > corresponding methods in Java (IgniteCompute). > Additionally, current affinity methods work through PlatformAbstractTask, > which does not lock partitions. We should refactor existing AffinityCall and > AffinityRun overloads to call corresponding IgniteCompute APIs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12927) The CacheGroupsMetricsRebalanceTest.testRebalancingLastCancelledTime is flacky
[
https://issues.apache.org/jira/browse/IGNITE-12927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amelchev Nikita updated IGNITE-12927:
-
Description:
The {{CacheGroupsMetricsRebalanceTest.testRebalancingLastCancelledTime}} is
flacky.
[TC
history.|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-448222889376376497=%3Cdefault%3E=testDetails]
{noformat}
java.lang.IllegalStateException: Duplicate key 1472820775 (attempted merging
values 1472820775 and 1472820775)
at
java.base/java.util.stream.Collectors.duplicateKeyException(Collectors.java:133)
at
java.base/java.util.stream.Collectors.lambda$uniqKeysMapAccumulator$1(Collectors.java:180)
at
java.base/java.util.stream.ReduceOps$3ReducingSink.accept(ReduceOps.java:169)
at
java.base/java.util.stream.IntPipeline$1$1.accept(IntPipeline.java:180)
at
java.base/java.util.Random$RandomIntsSpliterator.forEachRemaining(Random.java:1044)
at
java.base/java.util.Spliterator$OfInt.forEachRemaining(Spliterator.java:699)
at
java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)
at
java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)
at
java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:913)
at
java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
at
java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:578)
at
org.apache.ignite.internal.processors.cache.CacheGroupsMetricsRebalanceTest.testRebalancingLastCancelledTime(CacheGroupsMetricsRebalanceTest.java:315)
{noformat}
The reason is that randomly generated keys can be duplicated and cant be
collected from stream .
was:
The {{CacheGroupsMetricsRebalanceTest.testRebalancingLastCancelledTime}} is
flacky.
[TC
history.|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-448222889376376497=%3Cdefault%3E=testDetails]
{noformat}
java.lang.IllegalStateException: Duplicate key 1472820775 (attempted merging
values 1472820775 and 1472820775)
at
java.base/java.util.stream.Collectors.duplicateKeyException(Collectors.java:133)
at
java.base/java.util.stream.Collectors.lambda$uniqKeysMapAccumulator$1(Collectors.java:180)
at
java.base/java.util.stream.ReduceOps$3ReducingSink.accept(ReduceOps.java:169)
at
java.base/java.util.stream.IntPipeline$1$1.accept(IntPipeline.java:180)
at
java.base/java.util.Random$RandomIntsSpliterator.forEachRemaining(Random.java:1044)
at
java.base/java.util.Spliterator$OfInt.forEachRemaining(Spliterator.java:699)
at
java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)
at
java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)
at
java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:913)
at
java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
at
java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:578)
at
org.apache.ignite.internal.processors.cache.CacheGroupsMetricsRebalanceTest.testRebalancingLastCancelledTime(CacheGroupsMetricsRebalanceTest.java:315)
{noformat}
The reason is that random generated keys can be duplicated and cant be
collected from stream .
> The CacheGroupsMetricsRebalanceTest.testRebalancingLastCancelledTime is flacky
> --
>
> Key: IGNITE-12927
> URL: https://issues.apache.org/jira/browse/IGNITE-12927
> Project: Ignite
> Issue Type: Bug
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
>Priority: Minor
>
> The {{CacheGroupsMetricsRebalanceTest.testRebalancingLastCancelledTime}} is
> flacky.
> [TC
> history.|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-448222889376376497=%3Cdefault%3E=testDetails]
> {noformat}
> java.lang.IllegalStateException: Duplicate key 1472820775 (attempted merging
> values 1472820775 and 1472820775)
> at
> java.base/java.util.stream.Collectors.duplicateKeyException(Collectors.java:133)
> at
> java.base/java.util.stream.Collectors.lambda$uniqKeysMapAccumulator$1(Collectors.java:180)
> at
> java.base/java.util.stream.ReduceOps$3ReducingSink.accept(ReduceOps.java:169)
> at
> java.base/java.util.stream.IntPipeline$1$1.accept(IntPipeline.java:180)
> at
> java.base/java.util.Random$RandomIntsSpliterator.forEachRemaining(Random.java:1044)
> at
> java.base/java.util.Spliterator$OfInt.forEachRemaining(Spliterator.java:699)
> at
> java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)
> at
>
[jira] [Created] (IGNITE-12927) The CacheGroupsMetricsRebalanceTest.testRebalancingLastCancelledTime is flacky
Amelchev Nikita created IGNITE-12927:
Summary: The
CacheGroupsMetricsRebalanceTest.testRebalancingLastCancelledTime is flacky
Key: IGNITE-12927
URL: https://issues.apache.org/jira/browse/IGNITE-12927
Project: Ignite
Issue Type: Bug
Reporter: Amelchev Nikita
Assignee: Amelchev Nikita
The {{CacheGroupsMetricsRebalanceTest.testRebalancingLastCancelledTime}} is
flacky.
[TC
history.|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-448222889376376497=%3Cdefault%3E=testDetails]
{noformat}
java.lang.IllegalStateException: Duplicate key 1472820775 (attempted merging
values 1472820775 and 1472820775)
at
java.base/java.util.stream.Collectors.duplicateKeyException(Collectors.java:133)
at
java.base/java.util.stream.Collectors.lambda$uniqKeysMapAccumulator$1(Collectors.java:180)
at
java.base/java.util.stream.ReduceOps$3ReducingSink.accept(ReduceOps.java:169)
at
java.base/java.util.stream.IntPipeline$1$1.accept(IntPipeline.java:180)
at
java.base/java.util.Random$RandomIntsSpliterator.forEachRemaining(Random.java:1044)
at
java.base/java.util.Spliterator$OfInt.forEachRemaining(Spliterator.java:699)
at
java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)
at
java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)
at
java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:913)
at
java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
at
java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:578)
at
org.apache.ignite.internal.processors.cache.CacheGroupsMetricsRebalanceTest.testRebalancingLastCancelledTime(CacheGroupsMetricsRebalanceTest.java:315)
{noformat}
The reason is that random generated keys can be duplicated and cant be
collected from stream .
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-7369) .NET: Thin client: Transactions
[ https://issues.apache.org/jira/browse/IGNITE-7369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17088763#comment-17088763 ] Sergey Stronchinskiy commented on IGNITE-7369: -- [~ptupitsyn], I think i will need around 3 weeks more. > .NET: Thin client: Transactions > --- > > Key: IGNITE-7369 > URL: https://issues.apache.org/jira/browse/IGNITE-7369 > Project: Ignite > Issue Type: Improvement > Components: platforms, thin client >Affects Versions: 2.4 >Reporter: Pavel Tupitsyn >Assignee: Sergey Stronchinskiy >Priority: Major > Labels: .NET, iep-34 > Fix For: 2.9 > > > Implement transactions in thin client protocol and .NET thin client. > Main issue: Ignite transactions are tied to a specific thread. > See how JDBC works around this by starting a dedicated thread. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12919) Not all GridUuid renamed to IgniteUuid
[
https://issues.apache.org/jira/browse/IGNITE-12919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17088690#comment-17088690
]
Maxim Muzafarov commented on IGNITE-12919:
--
[~NSAmelchev]
LGTM, merged to the master brach.
> Not all GridUuid renamed to IgniteUuid
> --
>
> Key: IGNITE-12919
> URL: https://issues.apache.org/jira/browse/IGNITE-12919
> Project: Ignite
> Issue Type: Bug
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
>Priority: Minor
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> There are several places in javadocs and serialization mechanisms where
> GridUuid is not renamed. For example:
> {noformat}
> /**
> * Constructs {@code GridUuid} from a global and local identifiers.
> ...
> */
> public IgniteUuid(UUID gid, long locId) { ... }
> /**
> * Reads {@link org.apache.ignite.lang.IgniteUuid} from input stream.
> ...
> */
> @Nullable public static IgniteUuid readGridUuid(DataInput in) throws
> IOException {...}
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12902) Concurrent modification in time to iterate by events
[
https://issues.apache.org/jira/browse/IGNITE-12902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17088675#comment-17088675
]
Kirill Tkalenko commented on IGNITE-12902:
--
Build of new suite:
[https://ci.ignite.apache.org/viewLog.html?buildId=5244369=queuedBuildOverviewTab]
> Concurrent modification in time to iterate by events
>
>
> Key: IGNITE-12902
> URL: https://issues.apache.org/jira/browse/IGNITE-12902
> Project: Ignite
> Issue Type: Improvement
>Reporter: Kirill Tkalenko
>Assignee: Kirill Tkalenko
>Priority: Major
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {code:java}
> [10:20:37]W: [org.apache.ignite:ignite-core] [2020-02-20
> 10:20:37,324][ERROR][main][CacheExchangeMergeTest9] Failed to pre-stop
> processor: GridProcessorAdapter []
> [10:20:37]W: [org.apache.ignite:ignite-core]
> java.util.ConcurrentModificationException
> [10:20:37]W: [org.apache.ignite:ignite-core] at
> java.util.ArrayList$Itr.checkForComodification(ArrayList.java:909)
> [10:20:37]W: [org.apache.ignite:ignite-core] at
> java.util.ArrayList$Itr.next(ArrayList.java:859)
> [10:20:37]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:2302)
> [10:20:37]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:142)
> [10:20:37]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:464)
> [10:20:37]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.onKernalStop0(GridCachePartitionExchangeManager.java:821)
> [10:20:37]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.processors.cache.GridCacheSharedManagerAdapter.onKernalStop(GridCacheSharedManagerAdapter.java:120)
> [10:20:37]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStop(GridCacheProcessor.java:972){code}
> In that place we are going over event’s collection, looking for server
> leave’s event:
> {code:java}
> for (DiscoveryEvent evt : evts.events()) {
> if (serverLeftEvent(evt)) {
> for (CacheGroupContext grp : cctx.cache().cacheGroups())
> grp.affinityFunction().removeNode(evt.eventNode().id());
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12918) .NET: Add Travis job
[ https://issues.apache.org/jira/browse/IGNITE-12918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17088662#comment-17088662 ] Maxim Muzafarov commented on IGNITE-12918: -- [~ptupitsyn] It seems openjdk11 is skipped with this configuration. > .NET: Add Travis job > > > Key: IGNITE-12918 > URL: https://issues.apache.org/jira/browse/IGNITE-12918 > Project: Ignite > Issue Type: Improvement > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Add .NET build to .travis.yml -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12080) Add extended logging for rebalance
[ https://issues.apache.org/jira/browse/IGNITE-12080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Tkalenko updated IGNITE-12080: - Description: We should log information about finished rebalance on demander node. I'd have in log: h3. Total information: # Rebalance duration, rebalance start time/rebalance finish time # How many nodes were suppliers in rebalance (nodeId, number of supplied paritions, number of supplied entries, number of bytes, duraton of getting and processing partitions from supplier) h3. Information per cache group: # Rebalance duration, rebalance start time/rebalance finish time # How many nodes were suppliers in rebalance (nodeId, number of supplied paritions, list of partition ids with PRIMARY/BACKUP flag, number of supplied entries, number of bytes, duraton of getting and processing partitions from supplier) # Information about each partition distribution (list of nodeIds with primary/backup flag and marked supplier nodeId) h3. Information per supplier node: # How many paritions were requested: ** Total number ** Primary/backup distribution (number of primary partitions, number of backup partitions) ** Total number of entries ** Total size partitions in bytes # How many paritions were requested per cache group: ** Number of requested partitions ** Number of entries in partitions ** Total size of partitions in bytes ** List of requested partitions with size in bytes, count entries, primary or backup partition flag was: We should log all information about finished rebalance on demander node. I'd have in log: h3. Total information: # Rebalance duration, rebalance start time/rebalance finish time # How many partitions were processed in each topic (number of paritions, number of entries, number of bytes) # How many nodes were suppliers in rebalance (nodeId, number of supplied paritions, number of supplied entries, number of bytes, duraton of getting and processing partitions from supplier) h3. Information per cache group: # Rebalance duration, rebalance start time/rebalance finish time # How many partitions were processed in each topic (number of paritions, number of entries, number of bytes) # How many nodes were suppliers in rebalance (nodeId, number of supplied paritions, list of partition ids with PRIMARY/BACKUP flag, number of supplied entries, number of bytes, duraton of getting and processing partitions from supplier) # Information about each partition distribution (list of nodeIds with primary/backup flag and marked supplier nodeId) h3. Information per supplier node: # How many paritions were requested: #* Total number #* Primary/backup distribution (number of primary partitions, number of backup partitions) #* Total number of entries #* Total size partitions in bytes # How many paritions were requested per cache group: #* Number of requested partitions #* Number of entries in partitions #* Total size of partitions in bytes #* List of requested partitions with size in bytes, count entries, primary or backup partition flag > Add extended logging for rebalance > -- > > Key: IGNITE-12080 > URL: https://issues.apache.org/jira/browse/IGNITE-12080 > Project: Ignite > Issue Type: Improvement >Reporter: Kirill Tkalenko >Assignee: Kirill Tkalenko >Priority: Major > Time Spent: 1h 40m > Remaining Estimate: 0h > > We should log information about finished rebalance on demander node. > I'd have in log: > h3. Total information: > # Rebalance duration, rebalance start time/rebalance finish time > # How many nodes were suppliers in rebalance (nodeId, number of supplied > paritions, number of supplied entries, number of bytes, duraton of getting > and processing partitions from supplier) > h3. Information per cache group: > # Rebalance duration, rebalance start time/rebalance finish time > # How many nodes were suppliers in rebalance (nodeId, number of supplied > paritions, list of partition ids with PRIMARY/BACKUP flag, number of supplied > entries, number of bytes, duraton of getting and processing partitions from > supplier) > # Information about each partition distribution (list of nodeIds with > primary/backup flag and marked supplier nodeId) > h3. Information per supplier node: > # How many paritions were requested: > ** Total number > ** Primary/backup distribution (number of primary partitions, number of > backup partitions) > ** Total number of entries > ** Total size partitions in bytes > # How many paritions were requested per cache group: > ** Number of requested partitions > ** Number of entries in partitions > ** Total size of partitions in bytes > ** List of requested partitions with size in bytes, count entries, primary > or backup partition flag -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12905) QueryKeyValueIterable missing custom spliterator() implementation
[
https://issues.apache.org/jira/browse/IGNITE-12905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17088598#comment-17088598
]
Johnny Galatikitis commented on IGNITE-12905:
-
[~cyberdemon],
just done it and waiting for TC to finish. I removed old PR link and will
append the new one, if it does not happen automagically :)
> QueryKeyValueIterable missing custom spliterator() implementation
> -
>
> Key: IGNITE-12905
> URL: https://issues.apache.org/jira/browse/IGNITE-12905
> Project: Ignite
> Issue Type: Bug
> Components: cache, general
>Affects Versions: 2.8
> Environment: Windows 10
> JDK 1.8.0_172
> ignite-core 2.8.0
> reactor-core 3.3.3
>Reporter: Johnny Galatikitis
>Priority: Critical
> Fix For: 2.8.1
>
> Attachments:
> IGNITE-12905_-_add_QueryKeyValueSpliterator_and_corresponding_test.patch
>
> Time Spent: 3h 40m
> Remaining Estimate: 0h
>
> We are using apache ignite with reactor-core and since reactors upgrade from
> 3.2.12 to 3.3.3 {code:java}
> org.apache.ignite.internal.processors.query.QueryKeyValueIterable.iterator
> {code}
> is called multiple times. It starts with:
> 1. calling iterable.spliterator().hasCharacteristics(Spliterator.SIZED),
> where iterable is instanceof QueryKeyValueIterable
> 2. calls default implementation
> Spliterators.spliteratorUnknownSize(iterator(), 0)
> 3. which in turn calls ignite's QueryKeyValueIterable.iterator() call and
> that "uses it up" for subsequent calls, i.e. throw IgniteException "Iterator
> is already fetched or query was cancelled."
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12926) [ignite-extensions] build failed
[
https://issues.apache.org/jira/browse/IGNITE-12926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17088585#comment-17088585
]
Nikolay Izhikov commented on IGNITE-12926:
--
Hello [~samaitra]
I'm preparing the release of the spring-boot-autoconfigurer and found that
javadoc can't be built for the current master.
I fixed this in PR - https://github.com/apache/ignite-extensions/pull/11/files
As we want to perform releases of some extensions I also propose the following
changes:
* Have separate parent pom.xml - "ignite-extensions-parent".
* Have a single version of Ignite in dependency for now(if in the future we
will want to release extension for the different version of Ignite, we can fix
dependency for a specific module)
* Clear from parent pom unused plugins and other wrong parts(developer
information, old jdk link, etc.)
Can you, please, take a look at my changes?
> [ignite-extensions] build failed
>
>
> Key: IGNITE-12926
> URL: https://issues.apache.org/jira/browse/IGNITE-12926
> Project: Ignite
> Issue Type: Test
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Blocker
>
> The current master in ignite-extension can't be built.
> The reason in parent pom.xml which contains
> org.apache.ignite:ignite-tools:1.0-SNAPSHOT dependency for Javadoc plugin.
> The version has taken from the project version.
> {noformat}
>
> org.apache.maven.plugins
> maven-javadoc-plugin
> ${maven.javadoc.plugin.version}
>
>
>
>
> org.apache.ignite.tools.javadoc.IgniteLinkTaglet
>
> org.apache.ignite
> ignite-tools
> ${project.version}
>
>
>
> Ignite ${project.version}
> Ignite ${project.version}
> true
> true
> protected
> true
> false
> false
> ${javadoc.opts}
> {noformat}
> {noformat}
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] ignite-flink-ext 1.0.0-SNAPSHOT FAILURE [ 5.227
> s]
> [INFO] ignite-flume-ext 1.0.0-SNAPSHOT SKIPPED
> [INFO] ignite-pub-sub 2.9.0-SNAPSHOT .. SKIPPED
> [INFO] ignite-spring-boot-autoconfigure 1.0.0-SNAPSHOT SKIPPED
> [INFO] ignite-client-spring-boot-autoconfigure 1.0.0-SNAPSHOT SKIPPED
> [INFO] ignite-zeromq-ext 1.0.0-SNAPSHOT ... SKIPPED
> [INFO] apache-ignite-extensions 1.0.0-SNAPSHOT SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 5.812 s
> [INFO] Finished at: 2020-04-21T13:56:20+03:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-javadoc-plugin:2.10.4:jar (module-javadoc) on
> project ignite-flink-ext: MavenReportException: Error while generating
> Javadoc: Unable to find artifact:groupId = 'org.apache.ignite'
> [ERROR] artifactId = 'ignite-tools'
> [ERROR] version = '1.0.0-SNAPSHOT': Failure to find
> org.apache.ignite:ignite-tools:pom:1.0.0-SNAPSHOT in
> https://h2database.com/m2-repo was cached in the local repository, resolution
> will not be reattempted until the update interval of h2database.com has
> elapsed or updates are forced
> [ERROR]
> [ERROR] org.apache.ignite:ignite-tools:pom:1.0.0-SNAPSHOT
> [ERROR]
> [ERROR] from the specified remote repositories:
> [ERROR] h2database.com (https://h2database.com/m2-repo, releases=false,
> snapshots=true),
> [ERROR] apache.snapshots (http://repository.apache.org/snapshots,
> releases=false, snapshots=true),
> [ERROR] central (https://repo.maven.apache.org/maven2, releases=true,
> snapshots=false)
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> {noformat}
--
This message was
[jira] [Created] (IGNITE-12926) [ignite-extensions] build failed
Nikolay Izhikov created IGNITE-12926:
Summary: [ignite-extensions] build failed
Key: IGNITE-12926
URL: https://issues.apache.org/jira/browse/IGNITE-12926
Project: Ignite
Issue Type: Test
Reporter: Nikolay Izhikov
Assignee: Nikolay Izhikov
The current master in ignite-extension can't be built.
The reason in parent pom.xml which contains
org.apache.ignite:ignite-tools:1.0-SNAPSHOT dependency for Javadoc plugin.
The version has taken from the project version.
{noformat}
org.apache.maven.plugins
maven-javadoc-plugin
${maven.javadoc.plugin.version}
org.apache.ignite.tools.javadoc.IgniteLinkTaglet
org.apache.ignite
ignite-tools
${project.version}
Ignite ${project.version}
Ignite ${project.version}
true
true
protected
true
false
false
${javadoc.opts}
{noformat}
{noformat}
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] ignite-flink-ext 1.0.0-SNAPSHOT FAILURE [ 5.227 s]
[INFO] ignite-flume-ext 1.0.0-SNAPSHOT SKIPPED
[INFO] ignite-pub-sub 2.9.0-SNAPSHOT .. SKIPPED
[INFO] ignite-spring-boot-autoconfigure 1.0.0-SNAPSHOT SKIPPED
[INFO] ignite-client-spring-boot-autoconfigure 1.0.0-SNAPSHOT SKIPPED
[INFO] ignite-zeromq-ext 1.0.0-SNAPSHOT ... SKIPPED
[INFO] apache-ignite-extensions 1.0.0-SNAPSHOT SKIPPED
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 5.812 s
[INFO] Finished at: 2020-04-21T13:56:20+03:00
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-javadoc-plugin:2.10.4:jar (module-javadoc) on
project ignite-flink-ext: MavenReportException: Error while generating Javadoc:
Unable to find artifact:groupId = 'org.apache.ignite'
[ERROR] artifactId = 'ignite-tools'
[ERROR] version = '1.0.0-SNAPSHOT': Failure to find
org.apache.ignite:ignite-tools:pom:1.0.0-SNAPSHOT in
https://h2database.com/m2-repo was cached in the local repository, resolution
will not be reattempted until the update interval of h2database.com has elapsed
or updates are forced
[ERROR]
[ERROR] org.apache.ignite:ignite-tools:pom:1.0.0-SNAPSHOT
[ERROR]
[ERROR] from the specified remote repositories:
[ERROR] h2database.com (https://h2database.com/m2-repo, releases=false,
snapshots=true),
[ERROR] apache.snapshots (http://repository.apache.org/snapshots,
releases=false, snapshots=true),
[ERROR] central (https://repo.maven.apache.org/maven2, releases=true,
snapshots=false)
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-12852) Comma in field is not supported by COPY command
[ https://issues.apache.org/jira/browse/IGNITE-12852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov reassigned IGNITE-12852: Assignee: YuJue Li (was: Nikolay Izhikov) > Comma in field is not supported by COPY command > --- > > Key: IGNITE-12852 > URL: https://issues.apache.org/jira/browse/IGNITE-12852 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.8 >Reporter: YuJue Li >Assignee: YuJue Li >Priority: Critical > Fix For: 2.8.1 > > Time Spent: 10m > Remaining Estimate: 0h > > CREATE TABLE test(a int,b varchar(100),c int,PRIMARY key(a)); > > a.csv: > 1,"a,b",2 > > COPY FROM '/data/a.csv' INTO test (a,b,c) FORMAT CSV; > > The copy command fails because there is a comma in the second field,but this > is a fully legal and compliant CSV format -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-12852) Comma in field is not supported by COPY command
[ https://issues.apache.org/jira/browse/IGNITE-12852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov reassigned IGNITE-12852: Assignee: Nikolay Izhikov (was: YuJue Li) > Comma in field is not supported by COPY command > --- > > Key: IGNITE-12852 > URL: https://issues.apache.org/jira/browse/IGNITE-12852 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.8 >Reporter: YuJue Li >Assignee: Nikolay Izhikov >Priority: Critical > Fix For: 2.8.1 > > Time Spent: 10m > Remaining Estimate: 0h > > CREATE TABLE test(a int,b varchar(100),c int,PRIMARY key(a)); > > a.csv: > 1,"a,b",2 > > COPY FROM '/data/a.csv' INTO test (a,b,c) FORMAT CSV; > > The copy command fails because there is a comma in the second field,but this > is a fully legal and compliant CSV format -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12905) QueryKeyValueIterable missing custom spliterator() implementation
[
https://issues.apache.org/jira/browse/IGNITE-12905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17088548#comment-17088548
]
Dmitriy Sorokin commented on IGNITE-12905:
--
[~bleedah],
You have to make the new PR to master branch instead ignite-2.8.1, based on
newest upstream/master, and get an approval from TC Bot for that.
> QueryKeyValueIterable missing custom spliterator() implementation
> -
>
> Key: IGNITE-12905
> URL: https://issues.apache.org/jira/browse/IGNITE-12905
> Project: Ignite
> Issue Type: Bug
> Components: cache, general
>Affects Versions: 2.8
> Environment: Windows 10
> JDK 1.8.0_172
> ignite-core 2.8.0
> reactor-core 3.3.3
>Reporter: Johnny Galatikitis
>Priority: Critical
> Fix For: 2.8.1
>
> Attachments:
> IGNITE-12905_-_add_QueryKeyValueSpliterator_and_corresponding_test.patch
>
> Time Spent: 3h
> Remaining Estimate: 0h
>
> We are using apache ignite with reactor-core and since reactors upgrade from
> 3.2.12 to 3.3.3 {code:java}
> org.apache.ignite.internal.processors.query.QueryKeyValueIterable.iterator
> {code}
> is called multiple times. It starts with:
> 1. calling iterable.spliterator().hasCharacteristics(Spliterator.SIZED),
> where iterable is instanceof QueryKeyValueIterable
> 2. calls default implementation
> Spliterators.spliteratorUnknownSize(iterator(), 0)
> 3. which in turn calls ignite's QueryKeyValueIterable.iterator() call and
> that "uses it up" for subsequent calls, i.e. throw IgniteException "Iterator
> is already fetched or query was cancelled."
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12676) .NET: Add partition-based AffinityCall and AffinityRun overloads
[
https://issues.apache.org/jira/browse/IGNITE-12676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17088545#comment-17088545
]
Ignite TC Bot commented on IGNITE-12676:
{panel:title=Branch: [pull/7701/head] Base: [master] : Possible Blockers
(8)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}PDS (Indexing){color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5243583]]
{color:#d04437}ZooKeeper (Discovery) 3{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5243597]]
* ZookeeperDiscoverySpiTestSuite3:
CacheContinuousQueryOperationP2PTest.testTxReplicated - Test has low fail rate
in base branch 0,0% and is not flaky
{color:#d04437}Basic 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5243547]]
* IgniteBasicTestSuite:
GridIoManagerFileTransmissionSelfTest.tesFileHandlerReconnectTimeouted - Test
has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Queries 1{color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=5243595]]
* IgniteBinaryCacheQueryTestSuite: IgniteSqlQueryMinMaxTest.testGroupMinMax -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteBinaryCacheQueryTestSuite:
IgniteSqlQueryMinMaxTest.testMinMaxQueryPlanOnFields - Test has low fail rate
in base branch 0,0% and is not flaky
* IgniteBinaryCacheQueryTestSuite:
IgniteSqlQueryMinMaxTest.testMinMaxQueryPlanOnKey - Test has low fail rate in
base branch 0,0% and is not flaky
* IgniteBinaryCacheQueryTestSuite:
IgniteSqlQueryMinMaxTest.testGroupHavingMinMax - Test has low fail rate in base
branch 0,0% and is not flaky
{color:#d04437}Platform .NET (Core Linux){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5243590]]
* dll: DataStreamerTest.TestMultithreaded - New test duration 70s is more that
1 minute
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5243619buildTypeId=IgniteTests24Java8_RunAll]
> .NET: Add partition-based AffinityCall and AffinityRun overloads
>
>
> Key: IGNITE-12676
> URL: https://issues.apache.org/jira/browse/IGNITE-12676
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Add partition-based AffinityCall and AffinityRun overloads to ICompute.See
> corresponding methods in Java (IgniteCompute).
> Additionally, current affinity methods work through PlatformAbstractTask,
> which does not lock partitions. We should refactor existing AffinityCall and
> AffinityRun overloads to call corresponding IgniteCompute APIs.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12732) SQL: KILL QUERY command hangs on query when query cursor is held by user or leak
[ https://issues.apache.org/jira/browse/IGNITE-12732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17088539#comment-17088539 ] Nikolay Izhikov commented on IGNITE-12732: -- I mean, can you, please, create a pull request to ignite-2.8.1 branch that will contain this fix. > SQL: KILL QUERY command hangs on query when query cursor is held by user or > leak > > > Key: IGNITE-12732 > URL: https://issues.apache.org/jira/browse/IGNITE-12732 > Project: Ignite > Issue Type: Bug > Components: sql >Reporter: Roman Kondakov >Assignee: Roman Kondakov >Priority: Major > Fix For: 2.9, 2.8.1 > > Time Spent: 20m > Remaining Estimate: 0h > > Scenario to reproduce: > 1. Execute a query > 2. Don't close the query cursor, don't iterate to the end of results. > 3. Run "KILL QUERY" command. The command hangs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12676) .NET: Add partition-based AffinityCall and AffinityRun overloads
[ https://issues.apache.org/jira/browse/IGNITE-12676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17088533#comment-17088533 ] Alexandr Shapkin commented on IGNITE-12676: --- [~ptupitsyn] Looks good to me, thanks! > .NET: Add partition-based AffinityCall and AffinityRun overloads > > > Key: IGNITE-12676 > URL: https://issues.apache.org/jira/browse/IGNITE-12676 > Project: Ignite > Issue Type: Improvement > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: .NET > Time Spent: 10m > Remaining Estimate: 0h > > Add partition-based AffinityCall and AffinityRun overloads to ICompute.See > corresponding methods in Java (IgniteCompute). > Additionally, current affinity methods work through PlatformAbstractTask, > which does not lock partitions. We should refactor existing AffinityCall and > AffinityRun overloads to call corresponding IgniteCompute APIs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12732) SQL: KILL QUERY command hangs on query when query cursor is held by user or leak
[ https://issues.apache.org/jira/browse/IGNITE-12732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17088513#comment-17088513 ] Roman Kondakov commented on IGNITE-12732: - [~nizhikov], I'm not a committer, so I don't have rights for this. > SQL: KILL QUERY command hangs on query when query cursor is held by user or > leak > > > Key: IGNITE-12732 > URL: https://issues.apache.org/jira/browse/IGNITE-12732 > Project: Ignite > Issue Type: Bug > Components: sql >Reporter: Roman Kondakov >Assignee: Roman Kondakov >Priority: Major > Fix For: 2.9, 2.8.1 > > Time Spent: 20m > Remaining Estimate: 0h > > Scenario to reproduce: > 1. Execute a query > 2. Don't close the query cursor, don't iterate to the end of results. > 3. Run "KILL QUERY" command. The command hangs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12732) SQL: KILL QUERY command hangs on query when query cursor is held by user or leak
[ https://issues.apache.org/jira/browse/IGNITE-12732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov updated IGNITE-12732: -- Fix Version/s: 2.9 > SQL: KILL QUERY command hangs on query when query cursor is held by user or > leak > > > Key: IGNITE-12732 > URL: https://issues.apache.org/jira/browse/IGNITE-12732 > Project: Ignite > Issue Type: Bug > Components: sql >Reporter: Roman Kondakov >Assignee: Roman Kondakov >Priority: Major > Fix For: 2.9, 2.8.1 > > Time Spent: 20m > Remaining Estimate: 0h > > Scenario to reproduce: > 1. Execute a query > 2. Don't close the query cursor, don't iterate to the end of results. > 3. Run "KILL QUERY" command. The command hangs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12732) SQL: KILL QUERY command hangs on query when query cursor is held by user or leak
[ https://issues.apache.org/jira/browse/IGNITE-12732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17088490#comment-17088490 ] Nikolay Izhikov commented on IGNITE-12732: -- Hello, [~rkondakov] Can you, please, cherry-pick your fix to ignite-2.8.1 branch? > SQL: KILL QUERY command hangs on query when query cursor is held by user or > leak > > > Key: IGNITE-12732 > URL: https://issues.apache.org/jira/browse/IGNITE-12732 > Project: Ignite > Issue Type: Bug > Components: sql >Reporter: Roman Kondakov >Assignee: Roman Kondakov >Priority: Major > Fix For: 2.8.1 > > Time Spent: 20m > Remaining Estimate: 0h > > Scenario to reproduce: > 1. Execute a query > 2. Don't close the query cursor, don't iterate to the end of results. > 3. Run "KILL QUERY" command. The command hangs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12609) SQL: GridReduceQueryExecutor refactoring.
[ https://issues.apache.org/jira/browse/IGNITE-12609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov updated IGNITE-12609: -- Fix Version/s: 2.8.1 > SQL: GridReduceQueryExecutor refactoring. > - > > Key: IGNITE-12609 > URL: https://issues.apache.org/jira/browse/IGNITE-12609 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Andrey Mashenkov >Assignee: Andrey Mashenkov >Priority: Major > Labels: refactoring > Fix For: 2.9, 2.8.1 > > Time Spent: 20m > Remaining Estimate: 0h > > For now we have few issues that can be resolved. > 1. We create fake H2 tables\indices for reduce stage even if there is no need > to do so (skipMergeTable=true. > Let's decouple reduce logic from H2Index adapter code. > 2. Partition mapping code look to complicated and non-optimal. > Let's use cached affinity mapping and avoid collections copying when possible. > 3. Also there is no sense to pass RequestID to mapping code just for logging. > We'll never be able to match any request as no query really exists at a time > when error with RequestID is logged. > 4. Replicated only flag value semantic (calculation and usage) is not clear. > 5. GridReduceQueryExecutor.reduce() method is too long (over 400 lines). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12444) SQL: Query reduce can fail with NPE on retry.
[
https://issues.apache.org/jira/browse/IGNITE-12444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-12444:
--
Fix Version/s: (was: 2.8)
2.8.1
2.9
> SQL: Query reduce can fail with NPE on retry.
> -
>
> Key: IGNITE-12444
> URL: https://issues.apache.org/jira/browse/IGNITE-12444
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.7.6
>Reporter: Andrey Mashenkov
>Assignee: Andrey Mashenkov
>Priority: Major
> Fix For: 2.9, 2.8.1
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> GridReduceQueryExecutor can fail with NPE on retry if it couldn't map during
> retry timeout.
> So, 'lastRun' can be null here
> {code:java}
>if (attempt > 0 && retryTimeout > 0 && (U.currentTimeMillis() - startTime
> > retryTimeout)) {
> UUID retryNodeId = lastRun.retryNodeId();
> String retryCause = lastRun.retryCause();
> assert !F.isEmpty(retryCause);
> {code}
> Also assertion above is not correct.
> It is possible, we failed to send request, then retried with success to remap.
> So, 'lastRun' would be not null, but cause is empty.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12732) SQL: KILL QUERY command hangs on query when query cursor is held by user or leak
[ https://issues.apache.org/jira/browse/IGNITE-12732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-12732: - Fix Version/s: 2.8.1 > SQL: KILL QUERY command hangs on query when query cursor is held by user or > leak > > > Key: IGNITE-12732 > URL: https://issues.apache.org/jira/browse/IGNITE-12732 > Project: Ignite > Issue Type: Bug > Components: sql >Reporter: Roman Kondakov >Assignee: Roman Kondakov >Priority: Major > Fix For: 2.8.1 > > Time Spent: 20m > Remaining Estimate: 0h > > Scenario to reproduce: > 1. Execute a query > 2. Don't close the query cursor, don't iterate to the end of results. > 3. Run "KILL QUERY" command. The command hangs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12925) Flaky test SystemViewSelfTest.testContinuousQuery.
Mikhail Petrov created IGNITE-12925: --- Summary: Flaky test SystemViewSelfTest.testContinuousQuery. Key: IGNITE-12925 URL: https://issues.apache.org/jira/browse/IGNITE-12925 Project: Ignite Issue Type: Test Reporter: Mikhail Petrov It is needed to fix SystemViewSelfTest.testContinuousQuery test, which is flaky – [TC history|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=2075278944640125900=testDetails_IgniteTests24Java8=pull%2F7696%2Fhead]. It seems that QueryCursor#close method gives no guarantees that CQ routine will be cleared from all nodes before its returning. This behavior is due to StopRoutineDiscoveryMessage is immutable and so StopRoutineAckDiscoveryMessage can be received (QueryCoursor#close method returns) before GridContinuousProcessor#processStopRequest completion on all nodes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-12924) [ignite-extensions] Unused import breaks checkstyle
[
https://issues.apache.org/jira/browse/IGNITE-12924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolay Izhikov reassigned IGNITE-12924:
Assignee: Nikolay Izhikov
> [ignite-extensions] Unused import breaks checkstyle
>
>
> Key: IGNITE-12924
> URL: https://issues.apache.org/jira/browse/IGNITE-12924
> Project: Ignite
> Issue Type: Test
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
>
> {noformat}
> [INFO] --- maven-checkstyle-plugin:3.0.0:check (style) @ ignite-flume-ext ---
> [INFO] Starting audit...
> [ERROR]
> /Users/sbt-izhikov-nv/src/ignite-extensions/modules/flume-ext/src/main/java/org/apache/ignite/stream/flume/IgniteSink.java:32:8:
> Unused import - org.apache.ignite.IgniteIllegalStateException.
> [UnusedImports]
> Audit done.
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] ignite-flink-ext 1.0.0-SNAPSHOT SUCCESS [ 7.202
> s]
> [INFO] ignite-flume-ext 1.0.0-SNAPSHOT FAILURE [ 0.390
> s]
> [INFO] ignite-pub-sub 2.9.0-SNAPSHOT .. SKIPPED
> [INFO] ignite-spring-boot-autoconfigure 1.0.0-SNAPSHOT SKIPPED
> [INFO] ignite-client-spring-boot-autoconfigure 1.0.0-SNAPSHOT SKIPPED
> [INFO] ignite-zeromq-ext 1.0.0-SNAPSHOT ... SKIPPED
> [INFO] apache-ignite-extensions 1.0.0-SNAPSHOT SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 8.169 s
> [INFO] Finished at: 2020-04-21T11:47:45+03:00
> [INFO]
>
> [WARNING] The requested profile "lgpl" could not be activated because it does
> not exist.
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-checkstyle-plugin:3.0.0:check (style) on
> project ignite-flume-ext: Failed during checkstyle execution: There is 1
> error reported by Checkstyle 8.19 with ../checkstyle/checkstyle.xml ruleset.
> -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR] mvn -rf :ignite-flume-ext
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12924) [ignite-extensions] Unused import breaks checkstyle
Nikolay Izhikov created IGNITE-12924:
Summary: [ignite-extensions] Unused import breaks checkstyle
Key: IGNITE-12924
URL: https://issues.apache.org/jira/browse/IGNITE-12924
Project: Ignite
Issue Type: Test
Reporter: Nikolay Izhikov
{noformat}
[INFO] --- maven-checkstyle-plugin:3.0.0:check (style) @ ignite-flume-ext ---
[INFO] Starting audit...
[ERROR]
/Users/sbt-izhikov-nv/src/ignite-extensions/modules/flume-ext/src/main/java/org/apache/ignite/stream/flume/IgniteSink.java:32:8:
Unused import - org.apache.ignite.IgniteIllegalStateException. [UnusedImports]
Audit done.
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] ignite-flink-ext 1.0.0-SNAPSHOT SUCCESS [ 7.202 s]
[INFO] ignite-flume-ext 1.0.0-SNAPSHOT FAILURE [ 0.390 s]
[INFO] ignite-pub-sub 2.9.0-SNAPSHOT .. SKIPPED
[INFO] ignite-spring-boot-autoconfigure 1.0.0-SNAPSHOT SKIPPED
[INFO] ignite-client-spring-boot-autoconfigure 1.0.0-SNAPSHOT SKIPPED
[INFO] ignite-zeromq-ext 1.0.0-SNAPSHOT ... SKIPPED
[INFO] apache-ignite-extensions 1.0.0-SNAPSHOT SKIPPED
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 8.169 s
[INFO] Finished at: 2020-04-21T11:47:45+03:00
[INFO]
[WARNING] The requested profile "lgpl" could not be activated because it does
not exist.
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-checkstyle-plugin:3.0.0:check (style) on project
ignite-flume-ext: Failed during checkstyle execution: There is 1 error reported
by Checkstyle 8.19 with ../checkstyle/checkstyle.xml ruleset. -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn -rf :ignite-flume-ext
{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12804) SQL: ConnectionManager refactoring
[ https://issues.apache.org/jira/browse/IGNITE-12804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov updated IGNITE-12804: -- Fix Version/s: 2.8.1 > SQL: ConnectionManager refactoring > -- > > Key: IGNITE-12804 > URL: https://issues.apache.org/jira/browse/IGNITE-12804 > Project: Ignite > Issue Type: Task > Components: sql >Affects Versions: 2.8 >Reporter: Taras Ledkov >Assignee: Taras Ledkov >Priority: Major > Fix For: 2.9, 2.8.1 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > As of now ConnectionManager is a mess, really hard to understand. We should > refactor it. > Also ThreadLocal connection is a root cause of complicated behavior of local > queries & map queries. > I guess we have to use simple connection pool. > For better performance connection pools will be striped by Thread ID. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12880) IllegalArgumentException on activation of LogExporterSpi
[
https://issues.apache.org/jira/browse/IGNITE-12880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17088428#comment-17088428
]
Nikolay Izhikov commented on IGNITE-12880:
--
cherry-picked to 2.8.1
> IllegalArgumentException on activation of LogExporterSpi
>
>
> Key: IGNITE-12880
> URL: https://issues.apache.org/jira/browse/IGNITE-12880
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.8
>Reporter: Denis A. Magda
>Assignee: Mikhail Petrov
>Priority: Major
> Fix For: 2.8.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I tried to enable `LogExporterSpi` and getting an error below. Running on
> jdk1.8.0_77.jdk and macOS Catalina. See a source file attached.
> {noformat}
> Apr 08, 2020 1:07:00 PM org.apache.ignite.logger.java.JavaLogger error
> SEVERE: Got exception while starting (will rollback startup routine).
> java.lang.IllegalArgumentException
> at
> java.util.concurrent.ScheduledThreadPoolExecutor.scheduleWithFixedDelay(ScheduledThreadPoolExecutor.java:589)
> at
> org.apache.ignite.internal.processors.metric.PushMetricsExporterAdapter.spiStart(PushMetricsExporterAdapter.java:56)
> at
> org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:297)
> at
> org.apache.ignite.internal.processors.metric.GridMetricManager.start(GridMetricManager.java:277)
> at
> org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1960)
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1171)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2038)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1703)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1117)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:637)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:563)
> at org.apache.ignite.Ignition.start(Ignition.java:321)
> at ServerNodeStartup.main(ServerNodeStartup.java:43)
> Apr 08, 2020 1:07:00 PM org.apache.ignite.logger.java.JavaLogger error
> SEVERE: Failed to stop component (ignoring): GridManagerAdapter
> [enabled=true, name=o.a.i.i.processors.metric.GridMetricManager]
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.metric.PushMetricsExporterAdapter.spiStop(PushMetricsExporterAdapter.java:71)
> at
> org.apache.ignite.internal.managers.GridManagerAdapter.stopSpi(GridManagerAdapter.java:330)
> at
> org.apache.ignite.internal.processors.metric.GridMetricManager.stop(GridMetricManager.java:314)
> at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2627)
> at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2499)
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1395)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2038)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1703)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1117)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:637)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:563)
> at org.apache.ignite.Ignition.start(Ignition.java:321)
> at ServerNodeStartup.main(ServerNodeStartup.java:43)
> [13:07:00] Ignite node stopped wih ERRORS [uptime=00:00:01.303]
> Exception in thread "main" class org.apache.ignite.IgniteException: null
> at
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:1067)
> at org.apache.ignite.Ignition.start(Ignition.java:324)
> at ServerNodeStartup.main(ServerNodeStartup.java:43)
> Caused by: class org.apache.ignite.IgniteCheckedException: null
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1402)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2038)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1703)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1117)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:637)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:563)
> at org.apache.ignite.Ignition.start(Ignition.java:321)
> ... 1 more
> Caused by: java.lang.IllegalArgumentException
> at
> java.util.concurrent.ScheduledThreadPoolExecutor.scheduleWithFixedDelay(ScheduledThreadPoolExecutor.java:589)
> at
>
[jira] [Commented] (IGNITE-12908) Confusing check for presence of SqlViewExporterSpi class in classpath during initialization
[
https://issues.apache.org/jira/browse/IGNITE-12908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17088427#comment-17088427
]
Nikolay Izhikov commented on IGNITE-12908:
--
cherry-picked to 2.8.1
> Confusing check for presence of SqlViewExporterSpi class in classpath during
> initialization
> ---
>
> Key: IGNITE-12908
> URL: https://issues.apache.org/jira/browse/IGNITE-12908
> Project: Ignite
> Issue Type: Improvement
>Reporter: Andrey N. Gura
>Assignee: Mikhail Petrov
>Priority: Minor
> Labels: IEP-35
> Fix For: 2.8.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{IgnitionEx.initializeDefaultSpi()}} method checks for presence of
> {{SqlViewExporterSpi}} class in classpath whilst actual intention is to check
> for presence of indexing in classpath. It could be done just using
> {{IgniteComponentType.INDEXING.inClassPath()}} method.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12910) SqlViewExporterSpi uses log method which must not be used in production code
[
https://issues.apache.org/jira/browse/IGNITE-12910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17088429#comment-17088429
]
Nikolay Izhikov commented on IGNITE-12910:
--
cherry-picked to 2.8.1
> SqlViewExporterSpi uses log method which must not be used in production code
>
>
> Key: IGNITE-12910
> URL: https://issues.apache.org/jira/browse/IGNITE-12910
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.8
>Reporter: Andrey N. Gura
>Assignee: Mikhail Petrov
>Priority: Minor
> Labels: IEP-35
> Fix For: 2.8.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{SqlViewExporterSpi.register()}} method uses IgniteUtils.debug() method that
> log on INFO level instead of DEBUG because it needs only for debug purposes.
> Should be replaced by explicit log.debug() invocation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12801) Possible extra page release when throttling and checkpoint thread store its concurrently
[
https://issues.apache.org/jira/browse/IGNITE-12801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17088409#comment-17088409
]
Nikolay Izhikov commented on IGNITE-12801:
--
Hello, [~agoncharuk]
Can you, please, cherry pick this fix to 2.8.1 branch?
> Possible extra page release when throttling and checkpoint thread store its
> concurrently
>
>
> Key: IGNITE-12801
> URL: https://issues.apache.org/jira/browse/IGNITE-12801
> Project: Ignite
> Issue Type: Bug
>Reporter: Anton Kalashnikov
>Assignee: Anton Kalashnikov
>Priority: Major
> Fix For: 2.8.1
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> * User thread acquire page on write release
> * Checkpoint thread sees that page was acquired
> * Throttling thread sees that page was acquired
> * Checkpoint thread saves page to disk and releases the page
> * Throttling thread understand that the page was already saved but
> nonetheless release this page again. - this is not ok.
> {noformat}
> java.lang.AssertionError: null
> at
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.copyPageForCheckpoint(PageMemoryImpl.java:1181)
> at
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.checkpointWritePage(PageMemoryImpl.java:1160)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$WriteCheckpointPages.writePages(GridCacheDatabaseSharedManager.java:4868)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$WriteCheckpointPages.run(GridCacheDatabaseSharedManager.java:4792)
> ... 3 common frames omitted
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12910) SqlViewExporterSpi uses log method which must not be used in production code
[
https://issues.apache.org/jira/browse/IGNITE-12910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17088408#comment-17088408
]
Ignite TC Bot commented on IGNITE-12910:
{panel:title=Branch: [pull/7696/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5240717buildTypeId=IgniteTests24Java8_RunAll]
> SqlViewExporterSpi uses log method which must not be used in production code
>
>
> Key: IGNITE-12910
> URL: https://issues.apache.org/jira/browse/IGNITE-12910
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.8
>Reporter: Andrey N. Gura
>Assignee: Mikhail Petrov
>Priority: Minor
> Labels: IEP-35
> Fix For: 2.8.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{SqlViewExporterSpi.register()}} method uses IgniteUtils.debug() method that
> log on INFO level instead of DEBUG because it needs only for debug purposes.
> Should be replaced by explicit log.debug() invocation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12735) Metric exporter implementation could lead to NullPointerException from gauge which invoke communication
[
https://issues.apache.org/jira/browse/IGNITE-12735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolay Izhikov updated IGNITE-12735:
-
Fix Version/s: 2.8.1
> Metric exporter implementation could lead to NullPointerException from gauge
> which invoke communication
> ---
>
> Key: IGNITE-12735
> URL: https://issues.apache.org/jira/browse/IGNITE-12735
> Project: Ignite
> Issue Type: Improvement
>Reporter: Andrey N. Gura
>Assignee: Andrey N. Gura
>Priority: Major
> Labels: IEP-35
> Fix For: 2.9, 2.8.1
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> {{ReadMetricsOnNodeStartupTest#testReadMetricsOnNodeStartup}} test fails
> sometimes. The reason is try to export gauge metric value while
> {{TcpCommunicationMetricsListener}} isn't initialized.
> **Proposed solution:**
> Register metrics after export SPIs are already started.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-12880) IllegalArgumentException on activation of LogExporterSpi
[
https://issues.apache.org/jira/browse/IGNITE-12880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Petrov reassigned IGNITE-12880:
---
Assignee: Mikhail Petrov (was: Nikolay Izhikov)
> IllegalArgumentException on activation of LogExporterSpi
>
>
> Key: IGNITE-12880
> URL: https://issues.apache.org/jira/browse/IGNITE-12880
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.8
>Reporter: Denis A. Magda
>Assignee: Mikhail Petrov
>Priority: Major
> Fix For: 2.8.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I tried to enable `LogExporterSpi` and getting an error below. Running on
> jdk1.8.0_77.jdk and macOS Catalina. See a source file attached.
> {noformat}
> Apr 08, 2020 1:07:00 PM org.apache.ignite.logger.java.JavaLogger error
> SEVERE: Got exception while starting (will rollback startup routine).
> java.lang.IllegalArgumentException
> at
> java.util.concurrent.ScheduledThreadPoolExecutor.scheduleWithFixedDelay(ScheduledThreadPoolExecutor.java:589)
> at
> org.apache.ignite.internal.processors.metric.PushMetricsExporterAdapter.spiStart(PushMetricsExporterAdapter.java:56)
> at
> org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:297)
> at
> org.apache.ignite.internal.processors.metric.GridMetricManager.start(GridMetricManager.java:277)
> at
> org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1960)
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1171)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2038)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1703)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1117)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:637)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:563)
> at org.apache.ignite.Ignition.start(Ignition.java:321)
> at ServerNodeStartup.main(ServerNodeStartup.java:43)
> Apr 08, 2020 1:07:00 PM org.apache.ignite.logger.java.JavaLogger error
> SEVERE: Failed to stop component (ignoring): GridManagerAdapter
> [enabled=true, name=o.a.i.i.processors.metric.GridMetricManager]
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.metric.PushMetricsExporterAdapter.spiStop(PushMetricsExporterAdapter.java:71)
> at
> org.apache.ignite.internal.managers.GridManagerAdapter.stopSpi(GridManagerAdapter.java:330)
> at
> org.apache.ignite.internal.processors.metric.GridMetricManager.stop(GridMetricManager.java:314)
> at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2627)
> at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2499)
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1395)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2038)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1703)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1117)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:637)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:563)
> at org.apache.ignite.Ignition.start(Ignition.java:321)
> at ServerNodeStartup.main(ServerNodeStartup.java:43)
> [13:07:00] Ignite node stopped wih ERRORS [uptime=00:00:01.303]
> Exception in thread "main" class org.apache.ignite.IgniteException: null
> at
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:1067)
> at org.apache.ignite.Ignition.start(Ignition.java:324)
> at ServerNodeStartup.main(ServerNodeStartup.java:43)
> Caused by: class org.apache.ignite.IgniteCheckedException: null
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1402)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2038)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1703)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1117)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:637)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:563)
> at org.apache.ignite.Ignition.start(Ignition.java:321)
> ... 1 more
> Caused by: java.lang.IllegalArgumentException
> at
> java.util.concurrent.ScheduledThreadPoolExecutor.scheduleWithFixedDelay(ScheduledThreadPoolExecutor.java:589)
> at
>
[jira] [Commented] (IGNITE-12908) Confusing check for presence of SqlViewExporterSpi class in classpath during initialization
[
https://issues.apache.org/jira/browse/IGNITE-12908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17088368#comment-17088368
]
Ignite TC Bot commented on IGNITE-12908:
{panel:title=Branch: [pull/7695/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5240833buildTypeId=IgniteTests24Java8_RunAll]
> Confusing check for presence of SqlViewExporterSpi class in classpath during
> initialization
> ---
>
> Key: IGNITE-12908
> URL: https://issues.apache.org/jira/browse/IGNITE-12908
> Project: Ignite
> Issue Type: Improvement
>Reporter: Andrey N. Gura
>Assignee: Mikhail Petrov
>Priority: Minor
> Labels: IEP-35
> Fix For: 2.8.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{IgnitionEx.initializeDefaultSpi()}} method checks for presence of
> {{SqlViewExporterSpi}} class in classpath whilst actual intention is to check
> for presence of indexing in classpath. It could be done just using
> {{IgniteComponentType.INDEXING.inClassPath()}} method.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12880) IllegalArgumentException on activation of LogExporterSpi
[
https://issues.apache.org/jira/browse/IGNITE-12880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17088369#comment-17088369
]
Ignite TC Bot commented on IGNITE-12880:
{panel:title=Branch: [pull/7700/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5241480buildTypeId=IgniteTests24Java8_RunAll]
> IllegalArgumentException on activation of LogExporterSpi
>
>
> Key: IGNITE-12880
> URL: https://issues.apache.org/jira/browse/IGNITE-12880
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.8
>Reporter: Denis A. Magda
>Assignee: Nikolay Izhikov
>Priority: Major
> Fix For: 2.8.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I tried to enable `LogExporterSpi` and getting an error below. Running on
> jdk1.8.0_77.jdk and macOS Catalina. See a source file attached.
> {noformat}
> Apr 08, 2020 1:07:00 PM org.apache.ignite.logger.java.JavaLogger error
> SEVERE: Got exception while starting (will rollback startup routine).
> java.lang.IllegalArgumentException
> at
> java.util.concurrent.ScheduledThreadPoolExecutor.scheduleWithFixedDelay(ScheduledThreadPoolExecutor.java:589)
> at
> org.apache.ignite.internal.processors.metric.PushMetricsExporterAdapter.spiStart(PushMetricsExporterAdapter.java:56)
> at
> org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:297)
> at
> org.apache.ignite.internal.processors.metric.GridMetricManager.start(GridMetricManager.java:277)
> at
> org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1960)
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1171)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2038)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1703)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1117)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:637)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:563)
> at org.apache.ignite.Ignition.start(Ignition.java:321)
> at ServerNodeStartup.main(ServerNodeStartup.java:43)
> Apr 08, 2020 1:07:00 PM org.apache.ignite.logger.java.JavaLogger error
> SEVERE: Failed to stop component (ignoring): GridManagerAdapter
> [enabled=true, name=o.a.i.i.processors.metric.GridMetricManager]
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.metric.PushMetricsExporterAdapter.spiStop(PushMetricsExporterAdapter.java:71)
> at
> org.apache.ignite.internal.managers.GridManagerAdapter.stopSpi(GridManagerAdapter.java:330)
> at
> org.apache.ignite.internal.processors.metric.GridMetricManager.stop(GridMetricManager.java:314)
> at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2627)
> at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2499)
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1395)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2038)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1703)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1117)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:637)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:563)
> at org.apache.ignite.Ignition.start(Ignition.java:321)
> at ServerNodeStartup.main(ServerNodeStartup.java:43)
> [13:07:00] Ignite node stopped wih ERRORS [uptime=00:00:01.303]
> Exception in thread "main" class org.apache.ignite.IgniteException: null
> at
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:1067)
> at org.apache.ignite.Ignition.start(Ignition.java:324)
> at ServerNodeStartup.main(ServerNodeStartup.java:43)
> Caused by: class org.apache.ignite.IgniteCheckedException: null
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1402)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2038)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1703)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1117)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:637)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:563)
> at org.apache.ignite.Ignition.start(Ignition.java:321)
> ... 1 more
> Caused by:
[jira] [Updated] (IGNITE-12080) Add extended logging for rebalance
[ https://issues.apache.org/jira/browse/IGNITE-12080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Tkalenko updated IGNITE-12080: - Reviewer: Ivan Rakov (was: Eduard Shangareev) > Add extended logging for rebalance > -- > > Key: IGNITE-12080 > URL: https://issues.apache.org/jira/browse/IGNITE-12080 > Project: Ignite > Issue Type: Improvement >Reporter: Kirill Tkalenko >Assignee: Kirill Tkalenko >Priority: Major > Time Spent: 1.5h > Remaining Estimate: 0h > > We should log all information about finished rebalance on demander node. > I'd have in log: > h3. Total information: > # Rebalance duration, rebalance start time/rebalance finish time > # How many partitions were processed in each topic (number of paritions, > number of entries, number of bytes) > # How many nodes were suppliers in rebalance (nodeId, number of supplied > paritions, number of supplied entries, number of bytes, duraton of getting > and processing partitions from supplier) > h3. Information per cache group: > # Rebalance duration, rebalance start time/rebalance finish time > # How many partitions were processed in each topic (number of paritions, > number of entries, number of bytes) > # How many nodes were suppliers in rebalance (nodeId, number of supplied > paritions, list of partition ids with PRIMARY/BACKUP flag, number of supplied > entries, number of bytes, duraton of getting and processing partitions from > supplier) > # Information about each partition distribution (list of nodeIds with > primary/backup flag and marked supplier nodeId) > h3. Information per supplier node: > # How many paritions were requested: > #* Total number > #* Primary/backup distribution (number of primary partitions, number of > backup partitions) > #* Total number of entries > #* Total size partitions in bytes > # How many paritions were requested per cache group: > #* Number of requested partitions > #* Number of entries in partitions > #* Total size of partitions in bytes > #* List of requested partitions with size in bytes, count entries, primary or > backup partition flag -- This message was sent by Atlassian Jira (v8.3.4#803005)
