[jira] [Commented] (IGNITE-14771) Deadlock in org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager.GridCacheDataStore#init0
[
https://issues.apache.org/jira/browse/IGNITE-14771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17350866#comment-17350866
]
Ignite TC Bot commented on IGNITE-14771:
{panel:title=Branch: [pull/9121/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9121/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6020680&buildTypeId=IgniteTests24Java8_RunAll]
> Deadlock in
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager.GridCacheDataStore#init0
>
>
> Key: IGNITE-14771
> URL: https://issues.apache.org/jira/browse/IGNITE-14771
> Project: Ignite
> Issue Type: Bug
>Reporter: Ivan Bessonov
>Assignee: Ivan Bessonov
>Priority: Major
> Fix For: 2.11
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {code:java}
> Thread [name="sys-#145", id=178, state=RUNNABLE, blockCnt=47, waitCnt=135]
> at sun.management.ThreadImpl.dumpThreads0(Native Method)
> at sun.management.ThreadImpl.dumpAllThreads(ThreadImpl.java:454)
> at o.a.i.i.util.IgniteUtils.dumpThreads(IgniteUtils.java:1482)
> at
> o.a.i.i.processors.failure.FailureProcessor.process(FailureProcessor.java:187)
> - locked o.a.i.i.processors.failure.FailureProcessor@7ff7120d
> at
> o.a.i.i.processors.failure.FailureProcessor.process(FailureProcessor.java:150)
> at
> o.a.i.i.processors.cache.persistence.checkpoint.CheckpointTimeoutLock.failCheckpointReadLock(CheckpointTimeoutLock.java:216)
> at
> o.a.i.i.processors.cache.persistence.checkpoint.CheckpointTimeoutLock.checkpointReadLock(CheckpointTimeoutLock.java:113)
> at
> o.a.i.i.processors.cache.persistence.GridCacheDatabaseSharedManager.checkpointReadLock(GridCacheDatabaseSharedManager.java:1586)
> at
> o.a.i.i.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.init0(GridCacheOffheapManager.java:2177)
> at
> o.a.i.i.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.tombstonesCount(GridCacheOffheapManager.java:3284)
> at
> o.a.i.i.processors.cache.IgniteCacheOffheapManagerImpl.tombstonesCount(IgniteCacheOffheapManagerImpl.java:366)
> at
> o.a.i.i.processors.cache.persistence.GridCacheOffheapManager.fillQueue(GridCacheOffheapManager.java:1353)
> at
> o.a.i.i.processors.cache.distributed.dht.topology.PartitionsEvictManager.fillEvictQueue(PartitionsEvictManager.java:378)
> at
> o.a.i.i.processors.cache.distributed.dht.topology.PartitionsEvictManager.access$200(PartitionsEvictManager.java:76)
> at
> o.a.i.i.processors.cache.distributed.dht.topology.PartitionsEvictManager$1.run(PartitionsEvictManager.java:327)
> at o.a.i.i.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:7237)
> at
> o.a.i.i.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:826)
> at o.a.i.i.util.worker.GridWorker.run(GridWorker.java:119)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> {code:java}
>
> Thread [name="db-checkpoint-thread-#175", id=214, state=WAITING, blockCnt=4,
> waitCnt=1108] Lock
> [object=java.util.concurrent.locks.ReentrantReadWriteLock$NonfairSync@23108bcf,
> ownerName=null, ownerId=-1] at sun.misc.Unsafe.park(Native Method) at
> java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:870)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1199)
> at
> java.util.concurrent.locks.ReentrantReadWriteLock$WriteLock.lock(ReentrantReadWriteLock.java:943)
> at
> o.a.i.i.processors.cache.persistence.checkpoint.CheckpointReadWriteLock.writeLock(CheckpointReadWriteLock.java:138)
> at
> o.a.i.i.processors.cache.persistence.checkpoint.CheckpointWorkflow.markCheckpointBegin(CheckpointWorkflow.java:271)
> at
> o.a.i.i.processors.cache.persistence.checkpoint.Checkpointer.doCheckpoint(Checkpointer.java:414)
> at
> o.a.i.i.processors.cache.persistence.checkpoint.Checkpointer.body(Checkpointer.java:272)
> at o.a.i.i.util.worker.GridWorker.run(GridWorker.java
[jira] [Commented] (IGNITE-14667) Optimise WatchAggregator key criterion inference
[ https://issues.apache.org/jira/browse/IGNITE-14667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17350868#comment-17350868 ] Alexander Lapin commented on IGNITE-14667: -- [~kgusakov] LGTM > Optimise WatchAggregator key criterion inference > > > Key: IGNITE-14667 > URL: https://issues.apache.org/jira/browse/IGNITE-14667 > Project: Ignite > Issue Type: Task >Reporter: Kirill Gusakov >Assignee: Kirill Gusakov >Priority: Major > Time Spent: 2h > Remaining Estimate: 0h > > Now, MetaStorageManager is listening to the whole range of keys inferred from > component watches key criteria. But in practice, it can be a rough strategy > and if we have no prefix or range watches - we can infer the watch for > collection of keys. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14667) Optimise WatchAggregator key criterion inference
[ https://issues.apache.org/jira/browse/IGNITE-14667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin updated IGNITE-14667: - Reviewer: Alexander Lapin > Optimise WatchAggregator key criterion inference > > > Key: IGNITE-14667 > URL: https://issues.apache.org/jira/browse/IGNITE-14667 > Project: Ignite > Issue Type: Task >Reporter: Kirill Gusakov >Assignee: Kirill Gusakov >Priority: Major > Time Spent: 2h > Remaining Estimate: 0h > > Now, MetaStorageManager is listening to the whole range of keys inferred from > component watches key criteria. But in practice, it can be a rough strategy > and if we have no prefix or range watches - we can infer the watch for > collection of keys. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14771) Deadlock in org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager.GridCacheDataStore#init0
[
https://issues.apache.org/jira/browse/IGNITE-14771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17350880#comment-17350880
]
Sergey Chugunov commented on IGNITE-14771:
--
[~ibessonov],
Change looks good to me, please merge it to master. Thank you for the fix!
> Deadlock in
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager.GridCacheDataStore#init0
>
>
> Key: IGNITE-14771
> URL: https://issues.apache.org/jira/browse/IGNITE-14771
> Project: Ignite
> Issue Type: Bug
>Reporter: Ivan Bessonov
>Assignee: Ivan Bessonov
>Priority: Major
> Fix For: 2.11
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {code:java}
> Thread [name="sys-#145", id=178, state=RUNNABLE, blockCnt=47, waitCnt=135]
> at sun.management.ThreadImpl.dumpThreads0(Native Method)
> at sun.management.ThreadImpl.dumpAllThreads(ThreadImpl.java:454)
> at o.a.i.i.util.IgniteUtils.dumpThreads(IgniteUtils.java:1482)
> at
> o.a.i.i.processors.failure.FailureProcessor.process(FailureProcessor.java:187)
> - locked o.a.i.i.processors.failure.FailureProcessor@7ff7120d
> at
> o.a.i.i.processors.failure.FailureProcessor.process(FailureProcessor.java:150)
> at
> o.a.i.i.processors.cache.persistence.checkpoint.CheckpointTimeoutLock.failCheckpointReadLock(CheckpointTimeoutLock.java:216)
> at
> o.a.i.i.processors.cache.persistence.checkpoint.CheckpointTimeoutLock.checkpointReadLock(CheckpointTimeoutLock.java:113)
> at
> o.a.i.i.processors.cache.persistence.GridCacheDatabaseSharedManager.checkpointReadLock(GridCacheDatabaseSharedManager.java:1586)
> at
> o.a.i.i.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.init0(GridCacheOffheapManager.java:2177)
> at
> o.a.i.i.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.tombstonesCount(GridCacheOffheapManager.java:3284)
> at
> o.a.i.i.processors.cache.IgniteCacheOffheapManagerImpl.tombstonesCount(IgniteCacheOffheapManagerImpl.java:366)
> at
> o.a.i.i.processors.cache.persistence.GridCacheOffheapManager.fillQueue(GridCacheOffheapManager.java:1353)
> at
> o.a.i.i.processors.cache.distributed.dht.topology.PartitionsEvictManager.fillEvictQueue(PartitionsEvictManager.java:378)
> at
> o.a.i.i.processors.cache.distributed.dht.topology.PartitionsEvictManager.access$200(PartitionsEvictManager.java:76)
> at
> o.a.i.i.processors.cache.distributed.dht.topology.PartitionsEvictManager$1.run(PartitionsEvictManager.java:327)
> at o.a.i.i.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:7237)
> at
> o.a.i.i.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:826)
> at o.a.i.i.util.worker.GridWorker.run(GridWorker.java:119)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> {code:java}
>
> Thread [name="db-checkpoint-thread-#175", id=214, state=WAITING, blockCnt=4,
> waitCnt=1108] Lock
> [object=java.util.concurrent.locks.ReentrantReadWriteLock$NonfairSync@23108bcf,
> ownerName=null, ownerId=-1] at sun.misc.Unsafe.park(Native Method) at
> java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:870)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1199)
> at
> java.util.concurrent.locks.ReentrantReadWriteLock$WriteLock.lock(ReentrantReadWriteLock.java:943)
> at
> o.a.i.i.processors.cache.persistence.checkpoint.CheckpointReadWriteLock.writeLock(CheckpointReadWriteLock.java:138)
> at
> o.a.i.i.processors.cache.persistence.checkpoint.CheckpointWorkflow.markCheckpointBegin(CheckpointWorkflow.java:271)
> at
> o.a.i.i.processors.cache.persistence.checkpoint.Checkpointer.doCheckpoint(Checkpointer.java:414)
> at
> o.a.i.i.processors.cache.persistence.checkpoint.Checkpointer.body(Checkpointer.java:272)
> at o.a.i.i.util.worker.GridWorker.run(GridWorker.java:119) at
> java.lang.Thread.run(Thread.java:748)
> {code}
> {code:java}
>
> Thread [name="sys-#152", id=185, state=WAITING, blockCnt=47, waitCnt=115]
> Lock [object=java.util.concurrent.CountDownLatch$Sync@1b1a9e5a,
> ownerName=null, ownerId=-1] at sun.misc.Unsafe.park(Native Method) at
> java.util.concurrent.loc
[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
]
Sergey Chugunov updated IGNITE-12911:
-
Ignite Flags: Release Notes Required (was: Docs Required,Release Notes
Required)
> 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
>Assignee: Sergey Chugunov
>Priority: Blocker
> 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
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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.int
[jira] [Commented] (IGNITE-14725) Cluster crashes when the client has a higher byte code version than server
[
https://issues.apache.org/jira/browse/IGNITE-14725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17350886#comment-17350886
]
Ignite TC Bot commented on IGNITE-14725:
{panel:title=Branch: [pull/9124/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9124/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6021023&buildTypeId=IgniteTests24Java8_RunAll]
> Cluster crashes when the client has a higher byte code version than server
> --
>
> Key: IGNITE-14725
> URL: https://issues.apache.org/jira/browse/IGNITE-14725
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.10
>Reporter: Surkov Aleksandr
>Assignee: Sergei Ryzhov
>Priority: Major
> Attachments: different-java.zip
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When the Java version on the server does not support the byte code that the
> client node sends to server, then some operations(Scan Queries) can lead to
> the fall of the cluster.
> Steps to reproduce the situation:
> 1. Start the server using Java 8(org.apache.ignite.SimpleServer#main)
> 2. Start the client using Java 11(target byte code version 11), which will
> run ScanQuery(org.apache.ignite.ThickClient#main)
> Reproducer is attached. Logs from the server and client are located in the
> errors folder.
> {code:java}
> SEVERE: Failed to process message
> [senderId=53c4266d-8b74-480b-bbf5-670bd94c4192, msg=GridCacheQueryRequest
> [id=13, cacheName=cache_scan, type=SCAN, fields=false, clause=null, limit=0,
> clsName=null, keyValFilter=null, rdc=null, trans=null, pageSize=1024,
> incBackups=false, cancel=false, incMeta=false, all=false, keepBinary=false,
> subjId=53c4266d-8b74-480b-bbf5-670bd94c4192, taskHash=0, part=-1,
> topVer=AffinityTopologyVersion [topVer=2, minorTopVer=1], mvccSnapshot=null,
> flags=0, super=GridCacheIdMessage [cacheId=29045018, super=GridCacheMessage
> [msgId=14, depInfo=GridDeploymentInfoBean
> [clsLdrId=74845d87971-53c4266d-8b74-480b-bbf5-670bd94c4192, depMode=SHARED,
> userVer=0, locDepOwner=false, participants=null],
> lastAffChangedTopVer=AffinityTopologyVersion [topVer=2, minorTopVer=1],
> err=null, skipPrepare=false
> java.lang.UnsupportedClassVersionError: org/apache/ignite/ThickClient has
> been compiled by a more recent version of the Java Runtime (class file
> version 55.0), this version of the Java Runtime only recognizes class file
> versions up to 52.0
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:756)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:635)
> at
> org.apache.ignite.internal.managers.deployment.GridDeploymentClassLoader.findClass(GridDeploymentClassLoader.java:543)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
> at
> org.apache.ignite.internal.managers.deployment.GridDeploymentClassLoader.loadClass(GridDeploymentClassLoader.java:461)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at
> org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:9014)
> at
> org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:8945)
> at
> org.apache.ignite.internal.managers.deployment.GridDeployment.deployedClass(GridDeployment.java:460)
> at
> org.apache.ignite.internal.managers.deployment.GridDeploymentPerVersionStore.getDeployment(GridDeploymentPerVersionStore.java:441)
> at
> org.apache.ignite.internal.managers.deployment.GridDeploymentManager.getGlobalDeployment(GridDeploymentManager.java:517)
> at
> org.apache.ignite.internal.processors.cache.GridCacheDeploymentManager$CacheClassLoader.tryToloadClassFromCacheDep(GridCacheDeploymentManager.java:816)
> at
> org.apache.ignite.internal.processors.cache.GridCacheDeploymentManager$CacheClassLoader.findClass(GridCacheDeploymentManager.java:783)
> at
> org.apache.ignite.internal.processors.cache.GridCacheDeploymentManager$CacheClassLoader.loadClass(GridCacheDeploymentManager.java:760)
> at
> org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:9012)
> at
> org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:8957)
> at
> org.apache.ignite.internal.MarshallerContextImpl.getClass(MarshallerContextImpl.java:376)
> at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:693)
> at
> org.apache.ignite.internal.binary.BinaryUtils.doReadClass
[jira] [Commented] (IGNITE-11970) Excessive use of memory in continuous queries
[ https://issues.apache.org/jira/browse/IGNITE-11970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17350892#comment-17350892 ] Igor Belyakov commented on IGNITE-11970: [~mmuzaf], could you please review the changes? > Excessive use of memory in continuous queries > - > > Key: IGNITE-11970 > URL: https://issues.apache.org/jira/browse/IGNITE-11970 > Project: Ignite > Issue Type: Bug >Reporter: Igor Belyakov >Assignee: Igor Belyakov >Priority: Critical > Time Spent: 2h > Remaining Estimate: 0h > > When we prepare to send an entry into the continuous query's filter and > listener, we store it in an instance of CacheContinuousQueryEventBuffer.Batch. > The batch is an array of entries of size > IGNITE_CONTINUOUS_QUERY_SERVER_BUFFER_SIZE (default is 1000) that stores the > currently received entries (we need it for the case of concurrent updates to > make sure that we preserve the order of update counters). > The issue is that when we process a part of the array we keep the links to > the processed entries until we exhaust the array (after when we finally clear > it). Because of that we may store up to 999 garbage objects which can be a > lot if the entries are big. > Need to clear the entries right after we've processed them. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14567) Implement a snapshot abstraction for RAFT server.
[ https://issues.apache.org/jira/browse/IGNITE-14567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17350911#comment-17350911 ] Alexey Scherbakov commented on IGNITE-14567: 1. Implemented the API extension for snapshot support, improved the documentation on listener's contract [1]. 2. Additional refactoring required for incoming jraft merging. Overlall, no functional changes in the patch, only API improvements and refactoring. [1] org.apache.ignite.raft.client.service.RaftGroupListener > Implement a snapshot abstraction for RAFT server. > - > > Key: IGNITE-14567 > URL: https://issues.apache.org/jira/browse/IGNITE-14567 > Project: Ignite > Issue Type: Task >Reporter: Alexey Scherbakov >Assignee: Alexey Scherbakov >Priority: Major > Labels: iep-61, ignite-3 > Fix For: 3.0.0-alpha2 > > Time Spent: 10m > Remaining Estimate: 0h > > In addition to command processing [1] we need a snapshot abstraction allowing > for dumping/restoring state machine state. > [1] org.apache.ignite.raft.client.service.RaftGroupCommandListener -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14775) Prevent invoke responses to be delivered to message handlers
[ https://issues.apache.org/jira/browse/IGNITE-14775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Scherbakov updated IGNITE-14775: --- Description: Need to efficiently avoid calling [1] for invoke [2] responses, because they never are subject for any additional processing except returning responses for invoke, so it make no sense to deliver it to handlers. [1] org.apache.ignite.network.NetworkMessageHandler#onReceived [2] org.apache.ignite.network.MessagingService#invoke was: Need to efficiently avoid calling [1] for invoke [2] responses. [1] org.apache.ignite.network.NetworkMessageHandler#onReceived [2] org.apache.ignite.network.MessagingService#invoke > Prevent invoke responses to be delivered to message handlers > > > Key: IGNITE-14775 > URL: https://issues.apache.org/jira/browse/IGNITE-14775 > Project: Ignite > Issue Type: Bug > Components: networking >Reporter: Alexey Scherbakov >Priority: Major > Labels: ignite-3 > > Need to efficiently avoid calling [1] for invoke [2] responses, because they > never are subject for any additional processing except returning responses > for invoke, so it make no sense to deliver it to handlers. > [1] org.apache.ignite.network.NetworkMessageHandler#onReceived > [2] org.apache.ignite.network.MessagingService#invoke > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14649) Create an annotation processor for generating message serializers and de-serializers
[
https://issues.apache.org/jira/browse/IGNITE-14649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Chugunov updated IGNITE-14649:
-
Fix Version/s: (was: 3.0.0-alpha2)
3.0.0-alpha3
> Create an annotation processor for generating message serializers and
> de-serializers
>
>
> Key: IGNITE-14649
> URL: https://issues.apache.org/jira/browse/IGNITE-14649
> Project: Ignite
> Issue Type: Sub-task
> Components: networking
>Reporter: Semyon Danilov
>Assignee: Aleksandr Polovtcev
>Priority: Major
> Fix For: 3.0.0-alpha3
>
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> {{NetworkMessage}} instances can be (de-)serialized using instances of
> {{MessageSerializer}} and {{MessageDeserializer}} interfaces. These
> interfaces have to be implemented for every message type which is very
> tedious and can be automated. It is proposed to use annotation processing to
> generate the corresponding implementations for every network message.
> Current serialization procedure looks like the following:
> # Message header is written.
> # Message fields are sorted alphanumerically. This is done for historical
> reasons and not needed at the moment, but it was decided to keep this logic.
> # Message fields are dumped into the provided stateful {{MessageWriter}}.
> De-serialization procedure performs the same actions in reverse order.
> h3. Requirements
> # Create an annotation processor for generating instances of the following
> interfaces:
> ## {{MessageDeserializer}}
> ## {{MessageSerializer}}
> ## {{MessageSerializationFactory}}
> # Introduce the {{@AutoSerializable}} annotation that will be used to mark
> {{NetworkMessage}} implementations which will be considered as candidates for
> code generation by the annotation processor.
> # It should be possible to implement custom (de-)serializers for some
> messages. In this case it is proposed to simply omit the
> {{@AutoSerializable}} annotation on such messages.
> # Auto-generated {{MessageSerializationFactory}} instances should be
> automatically registered in a {{MessageSerializationRegistry}}. It is
> proposed to create a helper class that will add the generated factories to
> the provided registry.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-14226) Ducktape tests of rebalance
[
https://issues.apache.org/jira/browse/IGNITE-14226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergei Ryzhov reassigned IGNITE-14226:
--
Assignee: Sergei Ryzhov (was: Dmitriy Sorokin)
> Ducktape tests of rebalance
> ---
>
> Key: IGNITE-14226
> URL: https://issues.apache.org/jira/browse/IGNITE-14226
> Project: Ignite
> Issue Type: Test
>Reporter: Dmitriy Sorokin
>Assignee: Sergei Ryzhov
>Priority: Major
>
> There should be tests of rebalance for both in-memory caches and persistent
> caches.
> In case of persistent caches, the tests also should check both modes of
> rebalance: full and historical (asserts is needed that the proper mode of
> rebalance was worked).
> Basic scenario:
> Testing of rebalance triggered by two event types: node join and node left
> the topology (baseline change in persistent mode).
> Extended scenario:
> Node join or left during rebalance process.
> Test parameters:
> # Initial node count (derived from test context);
> # Cache count - the count of caches to create and data preload;
> # Cache entry count - the count of entries per cache to preload;
> # Cache entry size - the size of each cache entry in bytes;
> # Rebalance thread pool size - the value for
> {{IgniteConfiguration#rebalanceThreadPoolSize}} property (see [configuring
> rebalance thread pool
> title|https://ignite.apache.org/docs/latest/data-rebalancing#configuring-rebalance-thread-pool]),
> expected that greater value makes rebalance faster.
> # Rebalance batch size - the value for
> {{IgniteConfiguration#rebalanceBatchSize}} property (see [other rebalance
> properties|https://ignite.apache.org/docs/latest/data-rebalancing#other-properties]),
> expected that greater value makes rebalance faster on large data or
> [throttling|https://ignite.apache.org/docs/latest/data-rebalancing#throttling]
> enabled (rebalanceThrottling > 0).
> # Rebalance throttle - the value for
> {{IgniteConfiguration#rebalanceThrottle}} property (see [rebalance message
> throttling|https://ignite.apache.org/docs/latest/data-rebalancing#throttling],
> [other rebalance
> properties|https://ignite.apache.org/docs/latest/data-rebalancing#other-properties]),
> 0 - throttling disabled, greater value makes rebalance slower.
> Test result: time taken to rebalance process.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12692) Calcite integration. DML. Skip reducer optimization.
[ https://issues.apache.org/jira/browse/IGNITE-12692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17351019#comment-17351019 ] Atri Sharma commented on IGNITE-12692: -- I will be actively working on this ticket. > Calcite integration. DML. Skip reducer optimization. > > > Key: IGNITE-12692 > URL: https://issues.apache.org/jira/browse/IGNITE-12692 > Project: Ignite > Issue Type: Improvement >Reporter: Igor Seliverstov >Assignee: Atri Sharma >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > Having plan tree we easily can check whether a final modification may be > executed on data nodes directly or not. We should implement such kind of > optimization. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-12692) Calcite integration. DML. Skip reducer optimization.
[ https://issues.apache.org/jira/browse/IGNITE-12692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Atri Sharma reassigned IGNITE-12692: Assignee: Atri Sharma > Calcite integration. DML. Skip reducer optimization. > > > Key: IGNITE-12692 > URL: https://issues.apache.org/jira/browse/IGNITE-12692 > Project: Ignite > Issue Type: Improvement >Reporter: Igor Seliverstov >Assignee: Atri Sharma >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > Having plan tree we easily can check whether a final modification may be > executed on data nodes directly or not. We should implement such kind of > optimization. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14689) Get rid of addListeners and removeListeners from ConfigurationStorage interface
[ https://issues.apache.org/jira/browse/IGNITE-14689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17351036#comment-17351036 ] Ivan Bessonov commented on IGNITE-14689: [~maliev] looks good, thank you for the contribution! > Get rid of addListeners and removeListeners from ConfigurationStorage > interface > --- > > Key: IGNITE-14689 > URL: https://issues.apache.org/jira/browse/IGNITE-14689 > Project: Ignite > Issue Type: Task >Reporter: Mirza Aliev >Assignee: Mirza Aliev >Priority: Major > Labels: ignite-3 > Time Spent: 10m > Remaining Estimate: 0h > > Seems that it is needed only one listener for updating configuration, so > addListeners and removeListeners methods are redundant -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14689) Get rid of addListeners and removeListeners from ConfigurationStorage interface
[ https://issues.apache.org/jira/browse/IGNITE-14689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Bessonov updated IGNITE-14689: --- Ignite Flags: (was: Docs Required,Release Notes Required) > Get rid of addListeners and removeListeners from ConfigurationStorage > interface > --- > > Key: IGNITE-14689 > URL: https://issues.apache.org/jira/browse/IGNITE-14689 > Project: Ignite > Issue Type: Task >Reporter: Mirza Aliev >Assignee: Mirza Aliev >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha2 > > Time Spent: 20m > Remaining Estimate: 0h > > Seems that it is needed only one listener for updating configuration, so > addListeners and removeListeners methods are redundant -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14689) Get rid of addListeners and removeListeners from ConfigurationStorage interface
[ https://issues.apache.org/jira/browse/IGNITE-14689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mirza Aliev updated IGNITE-14689: - Labels: 3.0.0-alpha2 ignite-3 (was: ignite-3) > Get rid of addListeners and removeListeners from ConfigurationStorage > interface > --- > > Key: IGNITE-14689 > URL: https://issues.apache.org/jira/browse/IGNITE-14689 > Project: Ignite > Issue Type: Task >Reporter: Mirza Aliev >Assignee: Mirza Aliev >Priority: Major > Labels: 3.0.0-alpha2, ignite-3 > Fix For: 3.0.0-alpha2 > > Time Spent: 20m > Remaining Estimate: 0h > > Seems that it is needed only one listener for updating configuration, so > addListeners and removeListeners methods are redundant -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14709) Make ConfigurationStorage#readAll async
[
https://issues.apache.org/jira/browse/IGNITE-14709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mirza Aliev updated IGNITE-14709:
-
Description:
Currently, we faced with a problem when a node starts it is hanged on phase
when we register {{DistributedConfigurationStorage}}. It happens because when
{{ConfigurationChanger#register}} is run it requires
{{ConfigurationStorage#readAll}}, this, in turn, calls
{{MetaStorageServiceImpl#range}}, but the range is waiting on future until
cluster init happens, so all process of starting node is hanged.
Could be reproduced in
{{IgnitionTest#testNodeStartWithoutBootstrapConfiguration}}
was:
Currently, we faced with a problem when a node starts it is hanged on phase
when we register {{DistributedConfigurationStorage}}. It happens because when
{{ConfigurationChanger#register}} is run it requires
{{ConfigurationStorage#readAll}}, this, in turn, calls
{{MetaStorageServiceImpl#range}}, but the range is waiting on future until
cluster init happens, so all process of starting node is hanged.
Could be reproduced in IgnitionTest#testNodeStartWithoutBootstrapConfiguration
> Make ConfigurationStorage#readAll async
> ---
>
> Key: IGNITE-14709
> URL: https://issues.apache.org/jira/browse/IGNITE-14709
> Project: Ignite
> Issue Type: Improvement
>Reporter: Mirza Aliev
>Priority: Major
> Labels: ignite-3
>
> Currently, we faced with a problem when a node starts it is hanged on phase
> when we register {{DistributedConfigurationStorage}}. It happens because when
> {{ConfigurationChanger#register}} is run it requires
> {{ConfigurationStorage#readAll}}, this, in turn, calls
> {{MetaStorageServiceImpl#range}}, but the range is waiting on future until
> cluster init happens, so all process of starting node is hanged.
> Could be reproduced in
> {{IgnitionTest#testNodeStartWithoutBootstrapConfiguration}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14017) Willing to add s390x support to the docker image.
[ https://issues.apache.org/jira/browse/IGNITE-14017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17351044#comment-17351044 ] Vibhuti Sawant commented on IGNITE-14017: - Hi [~vveider], Any updates? > Willing to add s390x support to the docker image. > - > > Key: IGNITE-14017 > URL: https://issues.apache.org/jira/browse/IGNITE-14017 > Project: Ignite > Issue Type: New Feature >Reporter: Prajakta Chaudhari >Assignee: Peter Ivanov >Priority: Major > Fix For: 2.11 > > Time Spent: 10m > Remaining Estimate: 0h > > We are willing to add s390x support to the docker image. Dockerfile provided > on Apache Ignite GitHub repository > (https://github.com/apache/ignite/tree/master/docker/apache-ignite) is > working fine on s390x architecture. However we could not get any information > about how does the docker image build and release process work. Can you > please give some pointers to go ahead with the task? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14709) Make ConfigurationStorage#readAll async
[
https://issues.apache.org/jira/browse/IGNITE-14709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mirza Aliev updated IGNITE-14709:
-
Description:
Currently, we faced with a problem when a node starts it is hanged on phase
when we register {{DistributedConfigurationStorage}}. It happens because when
{{ConfigurationChanger#register}} is run it requires
{{ConfigurationStorage#readAll}}, this, in turn, calls
{{MetaStorageServiceImpl#range}}, but the range is waiting on future until
cluster init happens, so all process of starting node is hanged.
Could be reproduced in IgnitionTest#testNodeStartWithoutBootstrapConfiguration
was:
Currently, we faced with a problem when a node starts it is hanged on phase
when we register {{DistributedConfigurationStorage}}. It happens because when
{{ConfigurationChanger#register}} is run it requires
{{ConfigurationStorage#readAll}}, this, in turn, calls
{{MetaStorageServiceImpl#range}}, but the range is waiting on future until
cluster init happens, so all process of starting node is hanged.
> Make ConfigurationStorage#readAll async
> ---
>
> Key: IGNITE-14709
> URL: https://issues.apache.org/jira/browse/IGNITE-14709
> Project: Ignite
> Issue Type: Improvement
>Reporter: Mirza Aliev
>Priority: Major
> Labels: ignite-3
>
> Currently, we faced with a problem when a node starts it is hanged on phase
> when we register {{DistributedConfigurationStorage}}. It happens because when
> {{ConfigurationChanger#register}} is run it requires
> {{ConfigurationStorage#readAll}}, this, in turn, calls
> {{MetaStorageServiceImpl#range}}, but the range is waiting on future until
> cluster init happens, so all process of starting node is hanged.
> Could be reproduced in IgnitionTest#testNodeStartWithoutBootstrapConfiguration
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14352) Add the ability to check the consistency of individual cache groups in a snapshot.
[ https://issues.apache.org/jira/browse/IGNITE-14352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17351051#comment-17351051 ] Pavel Pereslegin commented on IGNITE-14352: --- [~mmuzaf], the changes look good to me, thanks for adding this feature. > Add the ability to check the consistency of individual cache groups in a > snapshot. > -- > > Key: IGNITE-14352 > URL: https://issues.apache.org/jira/browse/IGNITE-14352 > Project: Ignite > Issue Type: Improvement >Reporter: Pavel Pereslegin >Assignee: Maxim Muzafarov >Priority: Major > Fix For: 2.11 > > Time Spent: 40m > Remaining Estimate: 0h > > IGNITE-13725 introduces a snapshot check command to check the whole snapshot > consistency. > But sometimes it's necessary only to check the consistency of individual > cache groups in the snapshot. For example, IGNITE-13805 requires this feature > to restore the cache group). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14017) Willing to add s390x support to the docker image.
[
https://issues.apache.org/jira/browse/IGNITE-14017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17351053#comment-17351053
]
Peter Ivanov commented on IGNITE-14017:
---
Concerning proposed hierarchy, I would move ordinary Docker build files to
{{deliveries/docker/apache-ignite/x64}} instead
{{deliveries/docker/apache-ignite}}.
Other comments are in PR — if some of them are not clear, I can propose patch
with changes.
Also, I am no committer and would not be able to merge PR anyway ¯\_(ツ)_/¯.
> Willing to add s390x support to the docker image.
> -
>
> Key: IGNITE-14017
> URL: https://issues.apache.org/jira/browse/IGNITE-14017
> Project: Ignite
> Issue Type: New Feature
>Reporter: Prajakta Chaudhari
>Assignee: Peter Ivanov
>Priority: Major
> Fix For: 2.11
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> We are willing to add s390x support to the docker image. Dockerfile provided
> on Apache Ignite GitHub repository
> (https://github.com/apache/ignite/tree/master/docker/apache-ignite) is
> working fine on s390x architecture. However we could not get any information
> about how does the docker image build and release process work. Can you
> please give some pointers to go ahead with the task?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14777) row_number() with window functions unsupported.
Stanilovsky Evgeny created IGNITE-14777:
---
Summary: row_number() with window functions unsupported.
Key: IGNITE-14777
URL: https://issues.apache.org/jira/browse/IGNITE-14777
Project: Ignite
Issue Type: Improvement
Components: sql
Reporter: Stanilovsky Evgeny
subclass of window queries with _row_number_ functionality are not supported
for now.
examples:
{noformat}
SELECT i, j, row_number() OVER (PARTITION BY i ORDER BY j NULLS FIRST) FROM
test ORDER BY i NULLS FIRST, j NULLS FIRST;
---
SELECT i, (SELECT row_number() OVER (ORDER BY i) FROM integers WHERE i1.i=i)
FROM integers i1 ORDER BY i;
{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14778) Calcite integration. Expression executor
Konstantin Orlov created IGNITE-14778: - Summary: Calcite integration. Expression executor Key: IGNITE-14778 URL: https://issues.apache.org/jira/browse/IGNITE-14778 Project: Ignite Issue Type: Task Components: sql Reporter: Konstantin Orlov Assignee: Konstantin Orlov Implement a minimal expression executor -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14638) Calcite engine. Support for INTERSECT operator
[
https://issues.apache.org/jira/browse/IGNITE-14638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17351074#comment-17351074
]
Taras Ledkov commented on IGNITE-14638:
---
[~alex_pl], the patch is OK with me.
Minor comments:
- Please file the ticket to implement sort set operations in future.
- Why you don't use the {{AbstractPlannerTest#checkSplitAndSerialization}} at
the new planner test? I agree that plan mapping & serialization is checked by
integration test. But usually the planner tests covers more different plans
than integration tests.
> Calcite engine. Support for INTERSECT operator
> --
>
> Key: IGNITE-14638
> URL: https://issues.apache.org/jira/browse/IGNITE-14638
> Project: Ignite
> Issue Type: Improvement
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, INTERSECT operator is not supported
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14779) Unblock NULLS FIRST|LAST functionality checks calling from script runner tests.
Stanilovsky Evgeny created IGNITE-14779: --- Summary: Unblock NULLS FIRST|LAST functionality checks calling from script runner tests. Key: IGNITE-14779 URL: https://issues.apache.org/jira/browse/IGNITE-14779 Project: Ignite Issue Type: Improvement Components: sql Reporter: Stanilovsky Evgeny Assignee: Stanilovsky Evgeny We have numerous tests under _order/test_nulls_first.test_ but they seems to be failed due to *#pragma* specific parameters which are not take into account while calcite tests are running. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14779) Calcite. Unblock NULLS FIRST|LAST functionality checks calling from script runner tests.
[ https://issues.apache.org/jira/browse/IGNITE-14779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stanilovsky Evgeny updated IGNITE-14779: Summary: Calcite. Unblock NULLS FIRST|LAST functionality checks calling from script runner tests. (was: Unblock NULLS FIRST|LAST functionality checks calling from script runner tests.) > Calcite. Unblock NULLS FIRST|LAST functionality checks calling from script > runner tests. > > > Key: IGNITE-14779 > URL: https://issues.apache.org/jira/browse/IGNITE-14779 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Stanilovsky Evgeny >Assignee: Stanilovsky Evgeny >Priority: Major > Labels: calcite > > We have numerous tests under _order/test_nulls_first.test_ but they seems to > be failed due to *#pragma* specific parameters which are not take into > account while calcite tests are running. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14779) Calcite. Unblock NULLS FIRST|LAST functionality checks calling from script runner tests.
[ https://issues.apache.org/jira/browse/IGNITE-14779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17351106#comment-17351106 ] Stanilovsky Evgeny commented on IGNITE-14779: - [~korlov] can u review it plz ? > Calcite. Unblock NULLS FIRST|LAST functionality checks calling from script > runner tests. > > > Key: IGNITE-14779 > URL: https://issues.apache.org/jira/browse/IGNITE-14779 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Stanilovsky Evgeny >Assignee: Stanilovsky Evgeny >Priority: Major > Labels: calcite > Time Spent: 10m > Remaining Estimate: 0h > > We have numerous tests under _order/test_nulls_first.test_ but they seems to > be failed due to *#pragma* specific parameters which are not take into > account while calcite tests are running. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14649) Create an annotation processor for generating message serializers and de-serializers
[
https://issues.apache.org/jira/browse/IGNITE-14649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17351110#comment-17351110
]
Ivan Bessonov commented on IGNITE-14649:
[~apolovtcev] looks good to me, thank you!
> Create an annotation processor for generating message serializers and
> de-serializers
>
>
> Key: IGNITE-14649
> URL: https://issues.apache.org/jira/browse/IGNITE-14649
> Project: Ignite
> Issue Type: Sub-task
> Components: networking
>Reporter: Semyon Danilov
>Assignee: Aleksandr Polovtcev
>Priority: Major
> Fix For: 3.0.0-alpha3
>
> Time Spent: 5h
> Remaining Estimate: 0h
>
> {{NetworkMessage}} instances can be (de-)serialized using instances of
> {{MessageSerializer}} and {{MessageDeserializer}} interfaces. These
> interfaces have to be implemented for every message type which is very
> tedious and can be automated. It is proposed to use annotation processing to
> generate the corresponding implementations for every network message.
> Current serialization procedure looks like the following:
> # Message header is written.
> # Message fields are sorted alphanumerically. This is done for historical
> reasons and not needed at the moment, but it was decided to keep this logic.
> # Message fields are dumped into the provided stateful {{MessageWriter}}.
> De-serialization procedure performs the same actions in reverse order.
> h3. Requirements
> # Create an annotation processor for generating instances of the following
> interfaces:
> ## {{MessageDeserializer}}
> ## {{MessageSerializer}}
> ## {{MessageSerializationFactory}}
> # Introduce the {{@AutoSerializable}} annotation that will be used to mark
> {{NetworkMessage}} implementations which will be considered as candidates for
> code generation by the annotation processor.
> # It should be possible to implement custom (de-)serializers for some
> messages. In this case it is proposed to simply omit the
> {{@AutoSerializable}} annotation on such messages.
> # Auto-generated {{MessageSerializationFactory}} instances should be
> automatically registered in a {{MessageSerializationRegistry}}. It is
> proposed to create a helper class that will add the generated factories to
> the provided registry.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[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&focusedCommentId=17351125#comment-17351125
]
Ilya Kasnacheev commented on IGNITE-12911:
--
Looks OK if you are going to mark the subKey case as known issue. Just move the
test to a different site.
> 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
>Assignee: Sergey Chugunov
>Priority: Blocker
> 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
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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.finis
[jira] [Updated] (IGNITE-14649) Create an annotation processor for generating message serializers and de-serializers
[
https://issues.apache.org/jira/browse/IGNITE-14649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Bessonov updated IGNITE-14649:
---
Fix Version/s: (was: 3.0.0-alpha3)
3.0.0-alpha2
> Create an annotation processor for generating message serializers and
> de-serializers
>
>
> Key: IGNITE-14649
> URL: https://issues.apache.org/jira/browse/IGNITE-14649
> Project: Ignite
> Issue Type: Sub-task
> Components: networking
>Reporter: Semyon Danilov
>Assignee: Aleksandr Polovtcev
>Priority: Major
> Fix For: 3.0.0-alpha2
>
> Time Spent: 5h 20m
> Remaining Estimate: 0h
>
> {{NetworkMessage}} instances can be (de-)serialized using instances of
> {{MessageSerializer}} and {{MessageDeserializer}} interfaces. These
> interfaces have to be implemented for every message type which is very
> tedious and can be automated. It is proposed to use annotation processing to
> generate the corresponding implementations for every network message.
> Current serialization procedure looks like the following:
> # Message header is written.
> # Message fields are sorted alphanumerically. This is done for historical
> reasons and not needed at the moment, but it was decided to keep this logic.
> # Message fields are dumped into the provided stateful {{MessageWriter}}.
> De-serialization procedure performs the same actions in reverse order.
> h3. Requirements
> # Create an annotation processor for generating instances of the following
> interfaces:
> ## {{MessageDeserializer}}
> ## {{MessageSerializer}}
> ## {{MessageSerializationFactory}}
> # Introduce the {{@AutoSerializable}} annotation that will be used to mark
> {{NetworkMessage}} implementations which will be considered as candidates for
> code generation by the annotation processor.
> # It should be possible to implement custom (de-)serializers for some
> messages. In this case it is proposed to simply omit the
> {{@AutoSerializable}} annotation on such messages.
> # Auto-generated {{MessageSerializationFactory}} instances should be
> automatically registered in a {{MessageSerializationRegistry}}. It is
> proposed to create a helper class that will add the generated factories to
> the provided registry.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14649) Create an annotation processor for generating message serializers and de-serializers
[
https://issues.apache.org/jira/browse/IGNITE-14649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Bessonov updated IGNITE-14649:
---
Ignite Flags: (was: Docs Required,Release Notes Required)
> Create an annotation processor for generating message serializers and
> de-serializers
>
>
> Key: IGNITE-14649
> URL: https://issues.apache.org/jira/browse/IGNITE-14649
> Project: Ignite
> Issue Type: Sub-task
> Components: networking
>Reporter: Semyon Danilov
>Assignee: Aleksandr Polovtcev
>Priority: Major
> Fix For: 3.0.0-alpha3
>
> Time Spent: 5h 20m
> Remaining Estimate: 0h
>
> {{NetworkMessage}} instances can be (de-)serialized using instances of
> {{MessageSerializer}} and {{MessageDeserializer}} interfaces. These
> interfaces have to be implemented for every message type which is very
> tedious and can be automated. It is proposed to use annotation processing to
> generate the corresponding implementations for every network message.
> Current serialization procedure looks like the following:
> # Message header is written.
> # Message fields are sorted alphanumerically. This is done for historical
> reasons and not needed at the moment, but it was decided to keep this logic.
> # Message fields are dumped into the provided stateful {{MessageWriter}}.
> De-serialization procedure performs the same actions in reverse order.
> h3. Requirements
> # Create an annotation processor for generating instances of the following
> interfaces:
> ## {{MessageDeserializer}}
> ## {{MessageSerializer}}
> ## {{MessageSerializationFactory}}
> # Introduce the {{@AutoSerializable}} annotation that will be used to mark
> {{NetworkMessage}} implementations which will be considered as candidates for
> code generation by the annotation processor.
> # It should be possible to implement custom (de-)serializers for some
> messages. In this case it is proposed to simply omit the
> {{@AutoSerializable}} annotation on such messages.
> # Auto-generated {{MessageSerializationFactory}} instances should be
> automatically registered in a {{MessageSerializationRegistry}}. It is
> proposed to create a helper class that will add the generated factories to
> the provided registry.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14780) We should have posibility to override LATEST version param for forks
Mikhail Filatov created IGNITE-14780: Summary: We should have posibility to override LATEST version param for forks Key: IGNITE-14780 URL: https://issues.apache.org/jira/browse/IGNITE-14780 Project: Ignite Issue Type: Task Reporter: Mikhail Filatov Assignee: Mikhail Filatov -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14781) Ignite examples from binary package fail to build due to ClientKubernetesPutGetExample
Ilya Kasnacheev created IGNITE-14781:
Summary: Ignite examples from binary package fail to build due to
ClientKubernetesPutGetExample
Key: IGNITE-14781
URL: https://issues.apache.org/jira/browse/IGNITE-14781
Project: Ignite
Issue Type: Bug
Components: examples
Affects Versions: 2.10
Reporter: Ilya Kasnacheev
Fix For: 2.11
{code}
~/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples% mvn clean install
[INFO]
[INFO] -< org.apache.ignite:ignite-examples >--
[INFO] Building ignite-examples 2.11.0-SNAPSHOT
[INFO] [ jar ]-
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ ignite-examples ---
[INFO]
[INFO] --- build-helper-maven-plugin:3.2.0:add-source (add-sources) @
ignite-examples ---
[INFO] Source directory:
/home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java
added.
[INFO] Source directory:
/home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java
added.
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @
ignite-examples ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] Copying 14 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @
ignite-examples ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 266 source files to
/home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/target/classes
[INFO] -
[WARNING] COMPILATION WARNING :
[INFO] -
[WARNING]
/home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/datagrid/CacheAsyncApiExample.java:
Some input files use or override a deprecated API.
[WARNING]
/home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/datagrid/CacheAsyncApiExample.java:
Recompile with -Xlint:deprecation for details.
[WARNING]
/home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/datagrid/store/CacheLoadOnlyStoreExample.java:
Some input files use unchecked or unsafe operations.
[WARNING]
/home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/datagrid/store/CacheLoadOnlyStoreExample.java:
Recompile with -Xlint:unchecked for details.
[INFO] 4 warnings
[INFO] -
[INFO] -
[ERROR] COMPILATION ERROR :
[INFO] -
[ERROR]
/home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/client/ClientKubernetesPutGetExample.java:[23,32]
cannot find symbol
symbol: class ThinClientKubernetesAddressFinder
location: package org.apache.ignite.client
[ERROR]
/home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/client/ClientKubernetesPutGetExample.java:[26,50]
package org.apache.ignite.kubernetes.configuration does not exist
[ERROR]
/home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/client/ClientKubernetesPutGetExample.java:[42,9]
cannot find symbol
symbol: class KubernetesConnectionConfiguration
location: class
org.apache.ignite.examples.client.ClientKubernetesPutGetExample
[ERROR]
/home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/client/ClientKubernetesPutGetExample.java:[42,54]
cannot find symbol
symbol: class KubernetesConnectionConfiguration
location: class
org.apache.ignite.examples.client.ClientKubernetesPutGetExample
[ERROR]
/home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/client/ClientKubernetesPutGetExample.java:[46,36]
cannot find symbol
symbol: class ThinClientKubernetesAddressFinder
location: class
org.apache.ignite.examples.client.ClientKubernetesPutGetExample
[INFO] 5 errors
[INFO] -
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 4.852 s
[INFO] Finished at: 2021-05-25T18:57:12+03:00
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on
[jira] [Commented] (IGNITE-14781) Ignite examples from binary package fail to build due to ClientKubernetesPutGetExample
[
https://issues.apache.org/jira/browse/IGNITE-14781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17351167#comment-17351167
]
Ilya Kasnacheev commented on IGNITE-14781:
--
This is because IGNITE-13796 has added this class but did not add its
dependencies into pom-standalone file.
> Ignite examples from binary package fail to build due to
> ClientKubernetesPutGetExample
> --
>
> Key: IGNITE-14781
> URL: https://issues.apache.org/jira/browse/IGNITE-14781
> Project: Ignite
> Issue Type: Bug
> Components: examples
>Affects Versions: 2.10
>Reporter: Ilya Kasnacheev
>Priority: Blocker
> Fix For: 2.11
>
>
> {code}
> ~/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples% mvn clean install
> [INFO]
> [INFO] -< org.apache.ignite:ignite-examples
> >--
> [INFO] Building ignite-examples 2.11.0-SNAPSHOT
> [INFO] [ jar
> ]-
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ ignite-examples ---
> [INFO]
> [INFO] --- build-helper-maven-plugin:3.2.0:add-source (add-sources) @
> ignite-examples ---
> [INFO] Source directory:
> /home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java
> added.
> [INFO] Source directory:
> /home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java
> added.
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @
> ignite-examples ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 2 resources
> [INFO] Copying 14 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @
> ignite-examples ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 266 source files to
> /home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/target/classes
> [INFO] -
> [WARNING] COMPILATION WARNING :
> [INFO] -
> [WARNING]
> /home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/datagrid/CacheAsyncApiExample.java:
> Some input files use or override a deprecated API.
> [WARNING]
> /home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/datagrid/CacheAsyncApiExample.java:
> Recompile with -Xlint:deprecation for details.
> [WARNING]
> /home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/datagrid/store/CacheLoadOnlyStoreExample.java:
> Some input files use unchecked or unsafe operations.
> [WARNING]
> /home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/datagrid/store/CacheLoadOnlyStoreExample.java:
> Recompile with -Xlint:unchecked for details.
> [INFO] 4 warnings
> [INFO] -
> [INFO] -
> [ERROR] COMPILATION ERROR :
> [INFO] -
> [ERROR]
> /home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/client/ClientKubernetesPutGetExample.java:[23,32]
> cannot find symbol
> symbol: class ThinClientKubernetesAddressFinder
> location: package org.apache.ignite.client
> [ERROR]
> /home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/client/ClientKubernetesPutGetExample.java:[26,50]
> package org.apache.ignite.kubernetes.configuration does not exist
> [ERROR]
> /home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/client/ClientKubernetesPutGetExample.java:[42,9]
> cannot find symbol
> symbol: class KubernetesConnectionConfiguration
> location: class
> org.apache.ignite.examples.client.ClientKubernetesPutGetExample
> [ERROR]
> /home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/client/ClientKubernetesPutGetExample.java:[42,54]
> cannot find symbol
> symbol: class KubernetesConnectionConfiguration
> location: class
> org.apache.ignite.examples.client.ClientKubernetesPutGetExample
> [ERROR]
> /home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/client/ClientKubernetesPutGetExample.java:[46,36]
> cannot find symbol
> symbol: class ThinClientKubernetesAddressFinder
> location: class
> org.apache.ignite.examples.clien
[jira] [Commented] (IGNITE-14352) Add the ability to check the consistency of individual cache groups in a snapshot.
[
https://issues.apache.org/jira/browse/IGNITE-14352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17351216#comment-17351216
]
Ignite TC Bot commented on IGNITE-14352:
{panel:title=Branch: [pull/9105/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9105/head] Base: [master] : New Tests
(3)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Basic 3{color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=6021982]]
* {color:#013220}IgniteBasicWithPersistenceTestSuite:
IgniteClusterSnapshotCheckTest.testClusterSnapshotCheckWithTwoCachesCheckNotCorrupted
- PASSED{color}
* {color:#013220}IgniteBasicWithPersistenceTestSuite:
IgniteClusterSnapshotCheckTest.testClusterSnapshotCheckWithTwoCachesCheckTwoCaches
- PASSED{color}
* {color:#013220}IgniteBasicWithPersistenceTestSuite:
IgniteClusterSnapshotCheckTest.testClusterSnapshotCheckWithTwoCachesCheckNullInput
- PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6022043&buildTypeId=IgniteTests24Java8_RunAll]
> Add the ability to check the consistency of individual cache groups in a
> snapshot.
> --
>
> Key: IGNITE-14352
> URL: https://issues.apache.org/jira/browse/IGNITE-14352
> Project: Ignite
> Issue Type: Improvement
>Reporter: Pavel Pereslegin
>Assignee: Maxim Muzafarov
>Priority: Major
> Fix For: 2.11
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> IGNITE-13725 introduces a snapshot check command to check the whole snapshot
> consistency.
> But sometimes it's necessary only to check the consistency of individual
> cache groups in the snapshot. For example, IGNITE-13805 requires this feature
> to restore the cache group).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14352) Add the ability to check the consistency of individual cache groups in a snapshot.
[ https://issues.apache.org/jira/browse/IGNITE-14352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17351219#comment-17351219 ] Maxim Muzafarov commented on IGNITE-14352: -- Merged to the master branch. [~xtern] Thank you for the review. > Add the ability to check the consistency of individual cache groups in a > snapshot. > -- > > Key: IGNITE-14352 > URL: https://issues.apache.org/jira/browse/IGNITE-14352 > Project: Ignite > Issue Type: Improvement >Reporter: Pavel Pereslegin >Assignee: Maxim Muzafarov >Priority: Major > Fix For: 2.11 > > Time Spent: 50m > Remaining Estimate: 0h > > IGNITE-13725 introduces a snapshot check command to check the whole snapshot > consistency. > But sometimes it's necessary only to check the consistency of individual > cache groups in the snapshot. For example, IGNITE-13805 requires this feature > to restore the cache group). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14782) .net Thin Client: If bash not installed on pod, ignite fails to start
Robert May created IGNITE-14782:
---
Summary: .net Thin Client: If bash not installed on pod, ignite
fails to start
Key: IGNITE-14782
URL: https://issues.apache.org/jira/browse/IGNITE-14782
Project: Ignite
Issue Type: Bug
Components: clients, platforms
Affects Versions: 2.10
Reporter: Robert May
If bash is not installed, you get the following exception on startup:
{code:c#}
System.TypeInitializationException: The type initializer for
'Apache.Ignite.Core.Impl.Unmanaged.Jni.JvmDll' threw an exception.
---> System.TypeInitializationException: The type initializer for
'Apache.Ignite.Core.Impl.Unmanaged.Os' threw an exception.
---> System.ComponentModel.Win32Exception (2): No such file or directory
at System.Diagnostics.Process.ForkAndExecProcess(String filename, String[]
argv, String[] envp, String cwd, Boolean redirectStdin, Boolean redirectStdout,
Boolean redirectStderr, Boolean setCredentials, UInt32 userId, UInt32 groupId,
UInt32[] groups, Int32& stdinFd, Int32& stdoutFd, Int32& stderrFd, Boolean
usesTerminal, Boolean throwOnNoExec)
at System.Diagnostics.Process.StartCore(ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start()
at Apache.Ignite.Core.Impl.Shell.Execute(String file, String args)
at Apache.Ignite.Core.Impl.Shell.BashExecute(String args)
at Apache.Ignite.Core.Impl.Unmanaged.Os..cctor()
--- End of inner exception stack trace ---
at Apache.Ignite.Core.Impl.Unmanaged.Os.get_IsWindows()
at Apache.Ignite.Core.Impl.Unmanaged.Jni.JvmDll..cctor()
--- End of inner exception stack trace ---
at Apache.Ignite.Core.Impl.Unmanaged.Jni.JvmDll.Load(String
configJvmDllPath, ILogger log)
at Apache.Ignite.Core.Ignition.Start(IgniteConfiguration cfg)
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14783) Fix tests fail: IgniteCacheTestSuite9:SystemViewComputeJobTest, IoStatisticsSelfTest
Sergei Ryzhov created IGNITE-14783: -- Summary: Fix tests fail: IgniteCacheTestSuite9:SystemViewComputeJobTest, IoStatisticsSelfTest Key: IGNITE-14783 URL: https://issues.apache.org/jira/browse/IGNITE-14783 Project: Ignite Issue Type: Test Reporter: Sergei Ryzhov Assignee: Sergei Ryzhov Fix tests fail: IgniteCacheTestSuite9: - SystemViewComputeJobTest.testCancelComputeTask - IoStatisticsSelfTest.testPersistentIOGlobalStat -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-14781) Ignite examples from binary package fail to build due to ClientKubernetesPutGetExample
[
https://issues.apache.org/jira/browse/IGNITE-14781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maksim Timonin reassigned IGNITE-14781:
---
Assignee: Maksim Timonin
> Ignite examples from binary package fail to build due to
> ClientKubernetesPutGetExample
> --
>
> Key: IGNITE-14781
> URL: https://issues.apache.org/jira/browse/IGNITE-14781
> Project: Ignite
> Issue Type: Bug
> Components: examples
>Affects Versions: 2.10
>Reporter: Ilya Kasnacheev
>Assignee: Maksim Timonin
>Priority: Blocker
> Fix For: 2.11
>
>
> {code}
> ~/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples% mvn clean install
> [INFO]
> [INFO] -< org.apache.ignite:ignite-examples
> >--
> [INFO] Building ignite-examples 2.11.0-SNAPSHOT
> [INFO] [ jar
> ]-
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ ignite-examples ---
> [INFO]
> [INFO] --- build-helper-maven-plugin:3.2.0:add-source (add-sources) @
> ignite-examples ---
> [INFO] Source directory:
> /home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java
> added.
> [INFO] Source directory:
> /home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java
> added.
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @
> ignite-examples ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 2 resources
> [INFO] Copying 14 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @
> ignite-examples ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 266 source files to
> /home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/target/classes
> [INFO] -
> [WARNING] COMPILATION WARNING :
> [INFO] -
> [WARNING]
> /home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/datagrid/CacheAsyncApiExample.java:
> Some input files use or override a deprecated API.
> [WARNING]
> /home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/datagrid/CacheAsyncApiExample.java:
> Recompile with -Xlint:deprecation for details.
> [WARNING]
> /home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/datagrid/store/CacheLoadOnlyStoreExample.java:
> Some input files use unchecked or unsafe operations.
> [WARNING]
> /home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/datagrid/store/CacheLoadOnlyStoreExample.java:
> Recompile with -Xlint:unchecked for details.
> [INFO] 4 warnings
> [INFO] -
> [INFO] -
> [ERROR] COMPILATION ERROR :
> [INFO] -
> [ERROR]
> /home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/client/ClientKubernetesPutGetExample.java:[23,32]
> cannot find symbol
> symbol: class ThinClientKubernetesAddressFinder
> location: package org.apache.ignite.client
> [ERROR]
> /home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/client/ClientKubernetesPutGetExample.java:[26,50]
> package org.apache.ignite.kubernetes.configuration does not exist
> [ERROR]
> /home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/client/ClientKubernetesPutGetExample.java:[42,9]
> cannot find symbol
> symbol: class KubernetesConnectionConfiguration
> location: class
> org.apache.ignite.examples.client.ClientKubernetesPutGetExample
> [ERROR]
> /home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/client/ClientKubernetesPutGetExample.java:[42,54]
> cannot find symbol
> symbol: class KubernetesConnectionConfiguration
> location: class
> org.apache.ignite.examples.client.ClientKubernetesPutGetExample
> [ERROR]
> /home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/client/ClientKubernetesPutGetExample.java:[46,36]
> cannot find symbol
> symbol: class ThinClientKubernetesAddressFinder
> location: class
> org.apache.ignite.examples.client.ClientKubernetesPutGetExample
> [INFO] 5 errors
> [INFO]
