[jira] [Created] (IGNITE-9907) Wrong index field name makes the whole cluster to fail
Mikhail Cherkasov created IGNITE-9907: - Summary: Wrong index field name makes the whole cluster to fail Key: IGNITE-9907 URL: https://issues.apache.org/jira/browse/IGNITE-9907 Project: Ignite Issue Type: Bug Reporter: Mikhail Cherkasov Assignee: Mikhail Cherkasov Attachments: WrongFields.java Wrong index field name makes the whole cluster to fail and there's now reliable way to restore from this state, exchange fails with the exception: 2018-10-16 14:42:56,842][ERROR][exchange-worker-#42%server_0%][GridCachePartitionExchangeManager] Failed to wait for completion of partition map exchange (preloading will not start): GridDhtPartitionsExchangeFuture [firstDiscoEvt=DiscoveryCustomEvent [customMsg=null, affTopVer=AffinityTopologyVersion [topVer=2, minorTopVer=1], super=DiscoveryEvent [evtNode=TcpDiscoveryNode [id=6859ef9c-cceb-4d8a-8d5b-c1cd2cd192b7, addrs=[0:0:0:0:0:0:0:1%lo0, 127.0.0.1, 192.168.75.84], sockAddrs=[/192.168.75.84:0, /0:0:0:0:0:0:0:1%lo0:0, /127.0.0.1:0], discPort=0, order=2, intOrder=2, lastExchangeTime=1539726176458, loc=false, ver=2.4.3#19691231-sha1:, isClient=true], topVer=2, nodeId8=0d8b289d, msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1539726176684]], crd=TcpDiscoveryNode [id=0d8b289d-32aa-402e-8e71-137977559979, addrs=[0:0:0:0:0:0:0:1%lo0, 127.0.0.1, 192.168.75.84], sockAddrs=[/192.168.75.84:47500, /0:0:0:0:0:0:0:1%lo0:47500, /127.0.0.1:47500], discPort=47500, order=1, intOrder=1, lastExchangeTime=1539726176493, loc=true, ver=2.4.3#19691231-sha1:, isClient=false], exchId=GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=2, minorTopVer=1], discoEvt=DiscoveryCustomEvent [customMsg=null, affTopVer=AffinityTopologyVersion [topVer=2, minorTopVer=1], super=DiscoveryEvent [evtNode=TcpDiscoveryNode [id=6859ef9c-cceb-4d8a-8d5b-c1cd2cd192b7, addrs=[0:0:0:0:0:0:0:1%lo0, 127.0.0.1, 192.168.75.84], sockAddrs=[/192.168.75.84:0, /0:0:0:0:0:0:0:1%lo0:0, /127.0.0.1:0], discPort=0, order=2, intOrder=2, lastExchangeTime=1539726176458, loc=false, ver=2.4.3#19691231-sha1:, isClient=true], topVer=2, nodeId8=0d8b289d, msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1539726176684]], nodeId=6859ef9c, evt=DISCOVERY_CUSTOM_EVT], added=true, initFut=GridFutureAdapter [ignoreInterrupts=false, state=DONE, res=false, hash=1240595188], init=false, lastVer=null, partReleaseFut=PartitionReleaseFuture [topVer=AffinityTopologyVersion [topVer=2, minorTopVer=1], futures=[ExplicitLockReleaseFuture [topVer=AffinityTopologyVersion [topVer=2, minorTopVer=1], futures=[]], TxReleaseFuture [topVer=AffinityTopologyVersion [topVer=2, minorTopVer=1], futures=[]], AtomicUpdateReleaseFuture [topVer=AffinityTopologyVersion [topVer=2, minorTopVer=1], futures=[]], DataStreamerReleaseFuture [topVer=AffinityTopologyVersion [topVer=2, minorTopVer=1], futures=[, exchActions=null, affChangeMsg=null, initTs=1539726176695, centralizedAff=false, forceAffReassignment=false, changeGlobalStateE=null, done=true, state=CRD, evtLatch=0, remaining=[], super=GridFutureAdapter [ignoreInterrupts=false, state=DONE, res=java.lang.IndexOutOfBoundsException: Index: 0, Size: 0, hash=1559339235]] class org.apache.ignite.IgniteCheckedException: Index: 0, Size: 0 at org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7332) at org.apache.ignite.internal.util.future.GridFutureAdapter.resolve(GridFutureAdapter.java:259) at org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:207) at org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:159) at org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2374) at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110) at java.lang.Thread.run(Thread.java:748) Caused by: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at java.util.ArrayList.rangeCheck(ArrayList.java:657) at java.util.ArrayList.get(ArrayList.java:433) at org.apache.ignite.internal.processors.cache.CacheGroupContext.singleCacheContext(CacheGroupContext.java:374) at org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition.(GridDhtLocalPartition.java:194) at org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.getOrCreatePartition(GridDhtPartitionTopologyImpl.java:816) at org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.initPartitions(GridDhtPartitionTopologyImpl.java:381) at org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.beforeExchange(GridDhtPartitionTopologyImpl.java:554) at
[jira] [Comment Edited] (IGNITE-9893) add hibernate-5.2 module
[ https://issues.apache.org/jira/browse/IGNITE-9893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16652901#comment-16652901 ] Scott Feldstein edited comment on IGNITE-9893 at 10/17/18 4:17 AM: --- No, the SPI spec in hibernate-5.2 changed a little bit so they are not compatible. My changes use 5.1 as a baseline and I simply reworked the code and got all the tests to pass. I'm not sure I would remove the hibernate-5.1 module since that may still be something that is desired. pull request -> https://github.com/apache/ignite/pull/5008 was (Author: scottmf): No, the SPI spec in hibernate-5.2 changed a little bit so they are not compatible. My changes use 5.1 as a baseline and I simply reworked the code and got all the tests to pass. I'm not sure I would remove the hibernate-5.1 module since that may still be something that is desired. I'll work on getting the code committed when I get some time - hopefully soon. > add hibernate-5.2 module > > > Key: IGNITE-9893 > URL: https://issues.apache.org/jira/browse/IGNITE-9893 > Project: Ignite > Issue Type: New Feature > Components: hibernate >Reporter: Scott Feldstein >Priority: Major > > hi, > I have ported hibernate-5.2 to ignite 2.7.0-SNAPSHOT HEAD. > commit: > [https://github.com/scottmf/ignite/commit/4f2caafb8c433e3f840d14f91c2d83da1052afd9] > All tests pass except > CacheHibernateBlobStoreSelfTest.testSimpleMultithreading which is carryover > from the hibernate-5.1 implementation. There is a bug already associated with > the failure: > https://issues.apache.org/jira/browse/IGNITE-1757 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-1757) [Failed test] CacheHibernateBlobStoreSelfTest.testSimpleMultithreading fails on TC sometimes
[
https://issues.apache.org/jira/browse/IGNITE-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16652923#comment-16652923
]
ASF GitHub Bot commented on IGNITE-1757:
GitHub user scottmf opened a pull request:
https://github.com/apache/ignite/pull/5008
adding hibernate-5.2 module
all tests pass except
CacheHibernateBlobStoreSelfTest.testSimpleMultithreading which
is carryover from the hibernate-5.1 implementation. There is a bug already
associated
with the failure: https://issues.apache.org/jira/browse/IGNITE-1757
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/scottmf/ignite-1 master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5008.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #5008
commit d24953a70cd752547d85d4fa40d58bade9d18da1
Author: scottmf
Date: 2018-10-15T18:55:00Z
adding hibernate-5.2 module
all tests pass except
CacheHibernateBlobStoreSelfTest.testSimpleMultithreading which
is carryover from the hibernate-5.1 implementation. There is a bug already
associated
with the failure: https://issues.apache.org/jira/browse/IGNITE-1757
> [Failed test] CacheHibernateBlobStoreSelfTest.testSimpleMultithreading fails
> on TC sometimes
>
>
> Key: IGNITE-1757
> URL: https://issues.apache.org/jira/browse/IGNITE-1757
> Project: Ignite
> Issue Type: Test
>Reporter: Artem Shutak
>Priority: Critical
> Labels: Muted_test
>
> CacheHibernateBlobStoreSelfTest.testSimpleMultithreading fails on TC
> sometimes.
> {noformat}
> java.lang.NullPointerException: null
> at
> org.apache.maven.surefire.shade.org.apache.commons.io.output.DeferredFileOutputStream.thresholdReached(DeferredFileOutputStream.java:179)
> at
> org.apache.maven.surefire.shade.org.apache.commons.io.output.ThresholdingOutputStream.checkThreshold(ThresholdingOutputStream.java:224)
> at
> org.apache.maven.surefire.shade.org.apache.commons.io.output.ThresholdingOutputStream.write(ThresholdingOutputStream.java:128)
> at
> org.apache.maven.plugin.surefire.report.Utf8RecodingDeferredFileOutputStream.write(Utf8RecodingDeferredFileOutputStream.java:59)
> at
> org.apache.maven.plugin.surefire.report.TestSetRunListener.writeTestOutput(TestSetRunListener.java:98)
> at
> org.apache.maven.surefire.report.ConsoleOutputCapture$ForwardingPrintStream.println(ConsoleOutputCapture.java:91)
> at
> org.hibernate.engine.jdbc.spi.SqlStatementLogger.logStatement(SqlStatementLogger.java:106)
> at
> org.hibernate.engine.jdbc.spi.SqlStatementLogger.logStatement(SqlStatementLogger.java:95)
> at
> org.hibernate.engine.jdbc.internal.StatementPreparerImpl$StatementPreparationTemplate.prepareStatement(StatementPreparerImpl.java:180)
> at
> org.hibernate.engine.jdbc.internal.StatementPreparerImpl.prepareStatement(StatementPreparerImpl.java:85)
> at
> org.hibernate.persister.entity.AbstractEntityPersister.getDatabaseSnapshot(AbstractEntityPersister.java:1513)
> at
> org.hibernate.engine.internal.StatefulPersistenceContext.getDatabaseSnapshot(StatefulPersistenceContext.java:316)
> at
> org.hibernate.engine.internal.ForeignKeys.isTransient(ForeignKeys.java:217)
> at
> org.hibernate.event.internal.AbstractSaveEventListener.getEntityState(AbstractSaveEventListener.java:497)
> at
> org.hibernate.event.internal.DefaultSaveOrUpdateEventListener.performSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:100)
> at
> org.hibernate.event.internal.DefaultSaveOrUpdateEventListener.onSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:90)
> at
> org.hibernate.internal.SessionImpl.fireSaveOrUpdate(SessionImpl.java:735)
> at org.hibernate.internal.SessionImpl.saveOrUpdate(SessionImpl.java:727)
> at org.hibernate.internal.SessionImpl.saveOrUpdate(SessionImpl.java:723)
> at
> org.apache.ignite.cache.store.hibernate.CacheHibernateBlobStore.write(CacheHibernateBlobStore.java:190)
> at
> org.apache.ignite.testframework.junits.cache.GridAbstractCacheStoreSelfTest$1.call(GridAbstractCacheStoreSelfTest.java:396)
> at
> org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
> --- Stderr: ---
> [21:04:18,410][WARN
> ][hibernate.CacheHibernateBlobStoreSelfTest-1][CacheHibernateBlobStore] No
> Hibernate configuration has been provided for store (will use default).
> [21:04:18,495][WARN
> ][hibernate.CacheHibernateBlobStoreSelfTest-1][DriverManagerConnectionProviderImpl]
> HHH000148: No JDBC Driver class was specified by property
>
[jira] [Commented] (IGNITE-9893) add hibernate-5.2 module
[ https://issues.apache.org/jira/browse/IGNITE-9893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16652901#comment-16652901 ] Scott Feldstein commented on IGNITE-9893: - No, the SPI spec in hibernate-5.2 changed a little bit so they are not compatible. My changes use 5.1 as a baseline and I simply reworked the code and got all the tests to pass. I'm not sure I would remove the hibernate-5.1 module since that may still be something that is desired. I'll work on getting the code committed when I get some time - hopefully soon. > add hibernate-5.2 module > > > Key: IGNITE-9893 > URL: https://issues.apache.org/jira/browse/IGNITE-9893 > Project: Ignite > Issue Type: New Feature > Components: hibernate >Reporter: Scott Feldstein >Priority: Major > > hi, > I have ported hibernate-5.2 to ignite 2.7.0-SNAPSHOT HEAD. > commit: > [https://github.com/scottmf/ignite/commit/4f2caafb8c433e3f840d14f91c2d83da1052afd9] > All tests pass except > CacheHibernateBlobStoreSelfTest.testSimpleMultithreading which is carryover > from the hibernate-5.1 implementation. There is a bug already associated with > the failure: > https://issues.apache.org/jira/browse/IGNITE-1757 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9207) Update Web Console dependencies
[ https://issues.apache.org/jira/browse/IGNITE-9207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov reassigned IGNITE-9207: Assignee: Alexander Kalinin (was: Alexey Kuznetsov) [~alexdel], could you take a look at tests? Unit tests passed, but E2E failed. > Update Web Console dependencies > --- > > Key: IGNITE-9207 > URL: https://issues.apache.org/jira/browse/IGNITE-9207 > Project: Ignite > Issue Type: Task > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Alexander Kalinin >Priority: Major > Fix For: 2.8 > > Original Estimate: 2h > Time Spent: 4h > Remaining Estimate: 0h > > Update package.json to latest versions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9881) Management events for webconsole and visor
[
https://issues.apache.org/jira/browse/IGNITE-9881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16652605#comment-16652605
]
Ignite TC Bot commented on IGNITE-9881:
---
{panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET (Core Linux){color} [[tests
7|https://ci.ignite.apache.org/viewLog.html?buildId=2100893]]
* dll: ServicesTestAsync.TestGetServiceProxy(False) - 0,0% fails in last 100
master runs.
{color:#d04437}Binary Objects (Simple Mapper Basic){color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=2100844]]
* IgniteBinarySimpleNameMapperBasicTestSuite: SystemCacheNotConfiguredTest.test
- 2,0% fails in last 100 master runs.
* IgniteBinarySimpleNameMapperBasicTestSuite:
IgniteFutureImplTest.testChainAsync - 0,0% fails in last 100 master runs.
{color:#d04437}_Javadoc_{color} [[tests 0 Exit Code , BuildFailureOnMessage
|https://ci.ignite.apache.org/viewLog.html?buildId=2100911]]
{panel}
[TeamCity Run
All|http://ci.ignite.apache.org/viewLog.html?buildId=2099292buildTypeId=IgniteTests24Java8_RunAll]
> Management events for webconsole and visor
> --
>
> Key: IGNITE-9881
> URL: https://issues.apache.org/jira/browse/IGNITE-9881
> Project: Ignite
> Issue Type: New Feature
>Affects Versions: 2.6
>Reporter: Andrey Aleksandrov
>Assignee: Andrey Aleksandrov
>Priority: Major
> Fix For: 2.8
>
>
> New events for the handling of the tasks that were started on web console or
> visor could be helpful for tracking the user activities.
> At the moment all events will be handled as data node events. So it could be
> difficult to understand why they were fired in case if it was done on web
> console or visor.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-9600) SQL update fails if the sql updates more than one field
[
https://issues.apache.org/jira/browse/IGNITE-9600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Cherkasov resolved IGNITE-9600.
---
Resolution: Won't Fix
> SQL update fails if the sql updates more than one field
> ---
>
> Key: IGNITE-9600
> URL: https://issues.apache.org/jira/browse/IGNITE-9600
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.6
>Reporter: Mikhail Cherkasov
>Assignee: Mikhail Cherkasov
>Priority: Minor
> Attachments: TwoFieldUpdate.java
>
>
> SQL update fails if the sql updates more than one field:
> {noformat}
> Exception in thread "main" javax.cache.CacheException: Failed to execute map
> query on remote node [nodeId=9c46dc49-30d2-46ca-a2ec-8b1be7f19c91,
> errMsg=Failed to execute SQL query. Data conversion error converting
> "Entity2"; SQL statement:
> SELECT
> __Z0._KEY __C0_0,
> __Z0._VAL __C0_1,
> ((?1 AND (__Z0.ENTITY_NAME2 = ?2)) AND (__Z0.CONTINENT = ?3)) __C0_2
> FROM PUBLIC.ENTITY_TABLE __Z0
> WHERE __Z0.ENTITY_ID = ?4 [22018-195]]
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.fail(GridReduceQueryExecutor.java:288)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onFail(GridReduceQueryExecutor.java:278)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onMessage(GridReduceQueryExecutor.java:257)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$2.onMessage(GridReduceQueryExecutor.java:202)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$ArrayListener.onMessage(GridIoManager.java:2349)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1569)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1197)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:127)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1093)
> 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){noformat}
> Looks like ignite or underlying h2 engine generates query incorrectly:
> ((?1 AND (__Z0.ENTITY_NAME2 = ?2)) AND (__Z0.CONTINENT = ?3)) __C0_2
> the name for first field is missed.
>
> The reproducer is attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-9600) SQL update fails if the sql updates more than one field
[
https://issues.apache.org/jira/browse/IGNITE-9600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Cherkasov reassigned IGNITE-9600:
-
Assignee: Mikhail Cherkasov
> SQL update fails if the sql updates more than one field
> ---
>
> Key: IGNITE-9600
> URL: https://issues.apache.org/jira/browse/IGNITE-9600
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.6
>Reporter: Mikhail Cherkasov
>Assignee: Mikhail Cherkasov
>Priority: Minor
> Attachments: TwoFieldUpdate.java
>
>
> SQL update fails if the sql updates more than one field:
> {noformat}
> Exception in thread "main" javax.cache.CacheException: Failed to execute map
> query on remote node [nodeId=9c46dc49-30d2-46ca-a2ec-8b1be7f19c91,
> errMsg=Failed to execute SQL query. Data conversion error converting
> "Entity2"; SQL statement:
> SELECT
> __Z0._KEY __C0_0,
> __Z0._VAL __C0_1,
> ((?1 AND (__Z0.ENTITY_NAME2 = ?2)) AND (__Z0.CONTINENT = ?3)) __C0_2
> FROM PUBLIC.ENTITY_TABLE __Z0
> WHERE __Z0.ENTITY_ID = ?4 [22018-195]]
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.fail(GridReduceQueryExecutor.java:288)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onFail(GridReduceQueryExecutor.java:278)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onMessage(GridReduceQueryExecutor.java:257)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$2.onMessage(GridReduceQueryExecutor.java:202)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$ArrayListener.onMessage(GridIoManager.java:2349)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1569)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1197)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:127)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1093)
> 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){noformat}
> Looks like ignite or underlying h2 engine generates query incorrectly:
> ((?1 AND (__Z0.ENTITY_NAME2 = ?2)) AND (__Z0.CONTINENT = ?3)) __C0_2
> the name for first field is missed.
>
> The reproducer is attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9906) Added new method to get or wait for cache
Mikhail Cherkasov created IGNITE-9906: - Summary: Added new method to get or wait for cache Key: IGNITE-9906 URL: https://issues.apache.org/jira/browse/IGNITE-9906 Project: Ignite Issue Type: Improvement Reporter: Mikhail Cherkasov Assignee: Mikhail Cherkasov Attachments: Client.java, Server.java Due async nature of Ignite, ignite client might get cache creation event later then the rest of cluster and if server node created cache and pass it name to client, client might fail to get this cache, client.cache(name) will return null: # server creates cache server.getOrCreateCache() and return from getOrCreateCache method # server sends the cache name to client # client does client.cache(cacheName) and get null. It can be workaround by adding retirees, but it's a boilerplate code that we can add to our API. we can overload existing method ignite.cache() and add timeout for waiting. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9830) o.a.i.i.b.BinaryReaderExImpl#getOrCreateSchema sometimes misses latest metadata version resulting in failed tx commit because of absent schema.
[
https://issues.apache.org/jira/browse/IGNITE-9830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16652155#comment-16652155
]
Ignite TC Bot commented on IGNITE-9830:
---
{panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Hadoop{color} [[tests 0 Out Of Memory Error , Exit Code ,
[Artifacts publishing failed]
|https://ci.ignite.apache.org/viewLog.html?buildId=2095759]]
* IgniteHadoopFileSystemClientBasedOpenTest.testFsOpenMultithreadedSkipInProc
(last started)
{color:#d04437}_Javadoc_{color} [[tests 0 Exit Code , BuildFailureOnMessage
|https://ci.ignite.apache.org/viewLog.html?buildId=2095873]]
{color:#d04437}Spring{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2096466]]
* SpringEncryptedCacheRestartTest.testEncryptionKeysEqualsOnThirdNodeJoin (last
started)
{panel}
[TeamCity Run
All|http://ci.ignite.apache.org/viewLog.html?buildId=2092002buildTypeId=IgniteTests24Java8_RunAll]
> o.a.i.i.b.BinaryReaderExImpl#getOrCreateSchema sometimes misses latest
> metadata version resulting in failed tx commit because of absent schema.
> ---
>
> Key: IGNITE-9830
> URL: https://issues.apache.org/jira/browse/IGNITE-9830
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexei Scherbakov
>Assignee: Alexei Scherbakov
>Priority: Major
> Fix For: 2.8
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9868) Refactor [GridCachePartitionExchangeManager] Sending Full Message/Full Message creating
[
https://issues.apache.org/jira/browse/IGNITE-9868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16652104#comment-16652104
]
Ignite TC Bot commented on IGNITE-9868:
---
{panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Hadoop{color} [[tests 0 TIMEOUT , Out Of Memory Error , Exit
Code , [Artifacts publishing failed]
|https://ci.ignite.apache.org/viewLog.html?buildId=2098855]]
* HadoopMapReduceErrorResilienceTest.testRecoveryAfterAnError0_Error (last
started)
{color:#d04437}_Javadoc_{color} [[tests 0 Exit Code , BuildFailureOnMessage
|https://ci.ignite.apache.org/viewLog.html?buildId=2098859]]
{panel}
[TeamCity Run
All|http://ci.ignite.apache.org/viewLog.html?buildId=2097055buildTypeId=IgniteTests24Java8_RunAll]
> Refactor [GridCachePartitionExchangeManager] Sending Full Message/Full
> Message creating
> ---
>
> Key: IGNITE-9868
> URL: https://issues.apache.org/jira/browse/IGNITE-9868
> Project: Ignite
> Issue Type: Improvement
>Reporter: Sergey Antonov
>Assignee: Sergey Antonov
>Priority: Major
> Fix For: 2.7
>
>
> Made messages more informative and, maybe, reduce number of messages in log
> file
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9868) Refactor [GridCachePartitionExchangeManager] Sending Full Message/Full Message creating
[ https://issues.apache.org/jira/browse/IGNITE-9868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Antonov updated IGNITE-9868: --- Fix Version/s: 2.7 > Refactor [GridCachePartitionExchangeManager] Sending Full Message/Full > Message creating > --- > > Key: IGNITE-9868 > URL: https://issues.apache.org/jira/browse/IGNITE-9868 > Project: Ignite > Issue Type: Improvement >Reporter: Sergey Antonov >Assignee: Sergey Antonov >Priority: Major > Fix For: 2.7 > > > Made messages more informative and, maybe, reduce number of messages in log > file -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9905) After transaction load cluster inconsistent
[
https://issues.apache.org/jira/browse/IGNITE-9905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ARomantsov updated IGNITE-9905:
---
Description:
Loaded data into the cluster using transactions consisting of two get / two put
Test env: one server, two server node, one client
{code:java}
idle_verify check has finished, found 60 conflict partitions:
[counterConflicts=45, hashConflicts=15]
Update counter conflicts:
Conflict partition: PartitionKeyV2 [grpId=-1903385190,
grpName=CACHEGROUP_PARTICLE_1, partId=98]
Partition instances: [PartitionHashRecordV2 [isPrimary=true,
consistentId=node2, updateCntr=1519, size=596, partHash=-1167688484],
PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=1520,
size=596, partHash=-1167688484]]
Conflict partition: PartitionKeyV2 [grpId=-1903385190,
grpName=CACHEGROUP_PARTICLE_1, partId=34]
Partition instances: [PartitionHashRecordV2 [isPrimary=false,
consistentId=node2, updateCntr=1539, size=596, partHash=-99631005],
PartitionHashRecordV2 [isPrimary=true, consistentId=node1, updateCntr=1537,
size=596, partHash=-1284437377]]
Conflict partition: PartitionKeyV2 [grpId=770187303,
grpName=CACHEGROUP_PARTICLE_1, partId=31]
Partition instances: [PartitionHashRecordV2 [isPrimary=true,
consistentId=node2, updateCntr=15, size=4, partHash=-1125172674],
PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=16,
size=4, partHash=-1125172674]]
Conflict partition: PartitionKeyV2 [grpId=-1903385190,
grpName=CACHEGROUP_PARTICLE_1, partId=39]
Partition instances: [PartitionHashRecordV2 [isPrimary=true,
consistentId=node2, updateCntr=1555, size=596, partHash=-40303136],
PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=1556,
size=596, partHash=-40303136]]
Conflict partition: PartitionKeyV2 [grpId=-1903385190,
grpName=CACHEGROUP_PARTICLE_1, partId=90]
Partition instances: [PartitionHashRecordV2 [isPrimary=false,
consistentId=node2, updateCntr=1557, size=596, partHash=-1295145299],
PartitionHashRecordV2 [isPrimary=true, consistentId=node1, updateCntr=1556,
size=596, partHash=-1221175703]]
...
{code}
was:
{code:java}
idle_verify check has finished, found 60 conflict partitions:
[counterConflicts=45, hashConflicts=15]
Update counter conflicts:
Conflict partition: PartitionKeyV2 [grpId=-1903385190,
grpName=CACHEGROUP_PARTICLE_1, partId=98]
Partition instances: [PartitionHashRecordV2 [isPrimary=true,
consistentId=node2, updateCntr=1519, size=596, partHash=-1167688484],
PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=1520,
size=596, partHash=-1167688484]]
Conflict partition: PartitionKeyV2 [grpId=-1903385190,
grpName=CACHEGROUP_PARTICLE_1, partId=34]
Partition instances: [PartitionHashRecordV2 [isPrimary=false,
consistentId=node2, updateCntr=1539, size=596, partHash=-99631005],
PartitionHashRecordV2 [isPrimary=true, consistentId=node1, updateCntr=1537,
size=596, partHash=-1284437377]]
Conflict partition: PartitionKeyV2 [grpId=770187303,
grpName=CACHEGROUP_PARTICLE_1, partId=31]
Partition instances: [PartitionHashRecordV2 [isPrimary=true,
consistentId=node2, updateCntr=15, size=4, partHash=-1125172674],
PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=16,
size=4, partHash=-1125172674]]
Conflict partition: PartitionKeyV2 [grpId=-1903385190,
grpName=CACHEGROUP_PARTICLE_1, partId=39]
Partition instances: [PartitionHashRecordV2 [isPrimary=true,
consistentId=node2, updateCntr=1555, size=596, partHash=-40303136],
PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=1556,
size=596, partHash=-40303136]]
Conflict partition: PartitionKeyV2 [grpId=-1903385190,
grpName=CACHEGROUP_PARTICLE_1, partId=90]
Partition instances: [PartitionHashRecordV2 [isPrimary=false,
consistentId=node2, updateCntr=1557, size=596, partHash=-1295145299],
PartitionHashRecordV2 [isPrimary=true, consistentId=node1, updateCntr=1556,
size=596, partHash=-1221175703]]
...
{code}
> After transaction load cluster inconsistent
> ---
>
> Key: IGNITE-9905
> URL: https://issues.apache.org/jira/browse/IGNITE-9905
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Affects Versions: 2.7
>Reporter: ARomantsov
>Priority: Critical
> Fix For: 2.7
>
>
> Loaded data into the cluster using transactions consisting of two get / two
> put
> Test env: one server, two server node, one client
> {code:java}
> idle_verify check has finished, found 60 conflict partitions:
> [counterConflicts=45, hashConflicts=15]
> Update counter conflicts:
> Conflict partition: PartitionKeyV2 [grpId=-1903385190,
> grpName=CACHEGROUP_PARTICLE_1, partId=98]
> Partition instances: [PartitionHashRecordV2 [isPrimary=true,
> consistentId=node2, updateCntr=1519, size=596, partHash=-1167688484],
>
[jira] [Updated] (IGNITE-9905) After transaction load cluster inconsistent
[
https://issues.apache.org/jira/browse/IGNITE-9905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ARomantsov updated IGNITE-9905:
---
Description:
{code:java}
idle_verify check has finished, found 60 conflict partitions:
[counterConflicts=45, hashConflicts=15]
Update counter conflicts:
Conflict partition: PartitionKeyV2 [grpId=-1903385190,
grpName=CACHEGROUP_PARTICLE_1, partId=98]
Partition instances: [PartitionHashRecordV2 [isPrimary=true,
consistentId=node2, updateCntr=1519, size=596, partHash=-1167688484],
PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=1520,
size=596, partHash=-1167688484]]
Conflict partition: PartitionKeyV2 [grpId=-1903385190,
grpName=CACHEGROUP_PARTICLE_1, partId=34]
Partition instances: [PartitionHashRecordV2 [isPrimary=false,
consistentId=node2, updateCntr=1539, size=596, partHash=-99631005],
PartitionHashRecordV2 [isPrimary=true, consistentId=node1, updateCntr=1537,
size=596, partHash=-1284437377]]
Conflict partition: PartitionKeyV2 [grpId=770187303,
grpName=CACHEGROUP_PARTICLE_1, partId=31]
Partition instances: [PartitionHashRecordV2 [isPrimary=true,
consistentId=node2, updateCntr=15, size=4, partHash=-1125172674],
PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=16,
size=4, partHash=-1125172674]]
Conflict partition: PartitionKeyV2 [grpId=-1903385190,
grpName=CACHEGROUP_PARTICLE_1, partId=39]
Partition instances: [PartitionHashRecordV2 [isPrimary=true,
consistentId=node2, updateCntr=1555, size=596, partHash=-40303136],
PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=1556,
size=596, partHash=-40303136]]
Conflict partition: PartitionKeyV2 [grpId=-1903385190,
grpName=CACHEGROUP_PARTICLE_1, partId=90]
Partition instances: [PartitionHashRecordV2 [isPrimary=false,
consistentId=node2, updateCntr=1557, size=596, partHash=-1295145299],
PartitionHashRecordV2 [isPrimary=true, consistentId=node1, updateCntr=1556,
size=596, partHash=-1221175703]]
...
{code}
was:
{code:java}
idle_verify check has finished, found 60 conflict partitions:
[counterConflicts=45, hashConflicts=15]
Update counter conflicts:
Conflict partition: PartitionKeyV2 [grpId=-1903385190,
grpName=CACHEGROUP_PARTICLE_1, partId=98]
Partition instances: [PartitionHashRecordV2 [isPrimary=true,
consistentId=node2, updateCntr=1519, size=596, partHash=-1167688484],
PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=1520,
size=596, partHash=-1167688484]]
Conflict partition: PartitionKeyV2 [grpId=-1903385190,
grpName=CACHEGROUP_PARTICLE_1, partId=34]
Partition instances: [PartitionHashRecordV2 [isPrimary=false,
consistentId=node2, updateCntr=1539, size=596, partHash=-99631005],
PartitionHashRecordV2 [isPrimary=true, consistentId=node1, updateCntr=1537,
size=596, partHash=-1284437377]]
Conflict partition: PartitionKeyV2 [grpId=770187303,
grpName=CACHEGROUP_PARTICLE_1, partId=31]
Partition instances: [PartitionHashRecordV2 [isPrimary=true,
consistentId=node2, updateCntr=15, size=4, partHash=-1125172674],
PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=16,
size=4, partHash=-1125172674]]
Conflict partition: PartitionKeyV2 [grpId=-1903385190,
grpName=CACHEGROUP_PARTICLE_1, partId=39]
Partition instances: [PartitionHashRecordV2 [isPrimary=true,
consistentId=node2, updateCntr=1555, size=596, partHash=-40303136],
PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=1556,
size=596, partHash=-40303136]]
Conflict partition: PartitionKeyV2 [grpId=-1903385190,
grpName=CACHEGROUP_PARTICLE_1, partId=90]
Partition instances: [PartitionHashRecordV2 [isPrimary=false,
consistentId=node2, updateCntr=1557, size=596, partHash=-1295145299],
PartitionHashRecordV2 [isPrimary=true, consistentId=node1, updateCntr=1556,
size=596, partHash=-1221175703]]
...
{code}
> After transaction load cluster inconsistent
> ---
>
> Key: IGNITE-9905
> URL: https://issues.apache.org/jira/browse/IGNITE-9905
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Affects Versions: 2.7
>Reporter: ARomantsov
>Priority: Critical
> Fix For: 2.7
>
>
> {code:java}
> idle_verify check has finished, found 60 conflict partitions:
> [counterConflicts=45, hashConflicts=15]
> Update counter conflicts:
> Conflict partition: PartitionKeyV2 [grpId=-1903385190,
> grpName=CACHEGROUP_PARTICLE_1, partId=98]
> Partition instances: [PartitionHashRecordV2 [isPrimary=true,
> consistentId=node2, updateCntr=1519, size=596, partHash=-1167688484],
> PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=1520,
> size=596, partHash=-1167688484]]
> Conflict partition: PartitionKeyV2 [grpId=-1903385190,
> grpName=CACHEGROUP_PARTICLE_1, partId=34]
> Partition instances: [PartitionHashRecordV2
[jira] [Updated] (IGNITE-9905) After transaction load cluster inconsistent
[
https://issues.apache.org/jira/browse/IGNITE-9905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ARomantsov updated IGNITE-9905:
---
Description:
{code:java}
idle_verify check has finished, found 60 conflict partitions:
[counterConflicts=45, hashConflicts=15]
Update counter conflicts:
Conflict partition: PartitionKeyV2 [grpId=-1903385190,
grpName=CACHEGROUP_PARTICLE_1, partId=98]
Partition instances: [PartitionHashRecordV2 [isPrimary=true,
consistentId=node2, updateCntr=1519, size=596, partHash=-1167688484],
PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=1520,
size=596, partHash=-1167688484]]
Conflict partition: PartitionKeyV2 [grpId=-1903385190,
grpName=CACHEGROUP_PARTICLE_1, partId=34]
Partition instances: [PartitionHashRecordV2 [isPrimary=false,
consistentId=node2, updateCntr=1539, size=596, partHash=-99631005],
PartitionHashRecordV2 [isPrimary=true, consistentId=node1, updateCntr=1537,
size=596, partHash=-1284437377]]
Conflict partition: PartitionKeyV2 [grpId=770187303,
grpName=CACHEGROUP_PARTICLE_1, partId=31]
Partition instances: [PartitionHashRecordV2 [isPrimary=true,
consistentId=node2, updateCntr=15, size=4, partHash=-1125172674],
PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=16,
size=4, partHash=-1125172674]]
Conflict partition: PartitionKeyV2 [grpId=-1903385190,
grpName=CACHEGROUP_PARTICLE_1, partId=39]
Partition instances: [PartitionHashRecordV2 [isPrimary=true,
consistentId=node2, updateCntr=1555, size=596, partHash=-40303136],
PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=1556,
size=596, partHash=-40303136]]
Conflict partition: PartitionKeyV2 [grpId=-1903385190,
grpName=CACHEGROUP_PARTICLE_1, partId=90]
Partition instances: [PartitionHashRecordV2 [isPrimary=false,
consistentId=node2, updateCntr=1557, size=596, partHash=-1295145299],
PartitionHashRecordV2 [isPrimary=true, consistentId=node1, updateCntr=1556,
size=596, partHash=-1221175703]]
...
{code}
was:
{code:java}
idle_verify check has finished, found 60 conflict partitions:
[counterConflicts=45, hashConflicts=15]
Update counter conflicts:
Conflict partition: PartitionKeyV2 [grpId=-1903385190,
grpName=CACHEGROUP_PARTICLE_1, partId=98]
Partition instances: [PartitionHashRecordV2 [isPrimary=true,
consistentId=node2, updateCntr=1519, size=596, partHash=-1167688484],
PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=1520,
size=596, partHash=-1167688484]]
Conflict partition: PartitionKeyV2 [grpId=-1903385190,
grpName=CACHEGROUP_PARTICLE_1, partId=34]
Partition instances: [PartitionHashRecordV2 [isPrimary=false,
consistentId=node2, updateCntr=1539, size=596, partHash=-99631005],
PartitionHashRecordV2 [isPrimary=true, consistentId=node1, updateCntr=1537,
size=596, partHash=-1284437377]]
Conflict partition: PartitionKeyV2 [grpId=770187303,
grpName=CACHEGROUP_PARTICLE_1, partId=31]
Partition instances: [PartitionHashRecordV2 [isPrimary=true,
consistentId=node2, updateCntr=15, size=4, partHash=-1125172674],
PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=16,
size=4, partHash=-1125172674]]
Conflict partition: PartitionKeyV2 [grpId=-1903385190,
grpName=CACHEGROUP_PARTICLE_1, partId=39]
Partition instances: [PartitionHashRecordV2 [isPrimary=true,
consistentId=node2, updateCntr=1555, size=596, partHash=-40303136],
PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=1556,
size=596, partHash=-40303136]]
Conflict partition: PartitionKeyV2 [grpId=-1903385190,
grpName=CACHEGROUP_PARTICLE_1, partId=90]
Partition instances: [PartitionHashRecordV2 [isPrimary=false,
consistentId=node2, updateCntr=1557, size=596, partHash=-1295145299],
PartitionHashRecordV2 [isPrimary=true, consistentId=node1, updateCntr=1556,
size=596, partHash=-1221175703]]
{code}
> After transaction load cluster inconsistent
> ---
>
> Key: IGNITE-9905
> URL: https://issues.apache.org/jira/browse/IGNITE-9905
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Affects Versions: 2.7
>Reporter: ARomantsov
>Priority: Critical
> Fix For: 2.7
>
>
> {code:java}
> idle_verify check has finished, found 60 conflict partitions:
> [counterConflicts=45, hashConflicts=15]
> Update counter conflicts:
> Conflict partition: PartitionKeyV2 [grpId=-1903385190,
> grpName=CACHEGROUP_PARTICLE_1, partId=98]
> Partition instances: [PartitionHashRecordV2 [isPrimary=true,
> consistentId=node2, updateCntr=1519, size=596, partHash=-1167688484],
> PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=1520,
> size=596, partHash=-1167688484]]
> Conflict partition: PartitionKeyV2 [grpId=-1903385190,
> grpName=CACHEGROUP_PARTICLE_1, partId=34]
> Partition instances: [PartitionHashRecordV2
[jira] [Updated] (IGNITE-9905) After transaction load cluster inconsistent
[
https://issues.apache.org/jira/browse/IGNITE-9905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ARomantsov updated IGNITE-9905:
---
Description:
{code:java}
idle_verify check has finished, found 60 conflict partitions:
[counterConflicts=45, hashConflicts=15]
Update counter conflicts:
Conflict partition: PartitionKeyV2 [grpId=-1903385190,
grpName=CACHEGROUP_PARTICLE_1, partId=98]
Partition instances: [PartitionHashRecordV2 [isPrimary=true,
consistentId=node2, updateCntr=1519, size=596, partHash=-1167688484],
PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=1520,
size=596, partHash=-1167688484]]
Conflict partition: PartitionKeyV2 [grpId=-1903385190,
grpName=CACHEGROUP_PARTICLE_1, partId=34]
Partition instances: [PartitionHashRecordV2 [isPrimary=false,
consistentId=node2, updateCntr=1539, size=596, partHash=-99631005],
PartitionHashRecordV2 [isPrimary=true, consistentId=node1, updateCntr=1537,
size=596, partHash=-1284437377]]
Conflict partition: PartitionKeyV2 [grpId=770187303,
grpName=CACHEGROUP_PARTICLE_1, partId=31]
Partition instances: [PartitionHashRecordV2 [isPrimary=true,
consistentId=node2, updateCntr=15, size=4, partHash=-1125172674],
PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=16,
size=4, partHash=-1125172674]]
Conflict partition: PartitionKeyV2 [grpId=-1903385190,
grpName=CACHEGROUP_PARTICLE_1, partId=39]
Partition instances: [PartitionHashRecordV2 [isPrimary=true,
consistentId=node2, updateCntr=1555, size=596, partHash=-40303136],
PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=1556,
size=596, partHash=-40303136]]
Conflict partition: PartitionKeyV2 [grpId=-1903385190,
grpName=CACHEGROUP_PARTICLE_1, partId=90]
Partition instances: [PartitionHashRecordV2 [isPrimary=false,
consistentId=node2, updateCntr=1557, size=596, partHash=-1295145299],
PartitionHashRecordV2 [isPrimary=true, consistentId=node1, updateCntr=1556,
size=596, partHash=-1221175703]]
{code}
was:
One server, two nodes per server, one client
Loaded data into the cluster using transactions consisting of two get / two put
{code:java}
idle_verify check has finished, found 60 conflict partitions:
[counterConflicts=45, hashConflicts=15]
Update counter conflicts:
Conflict partition: PartitionKeyV2 [grpId=-1903385190,
grpName=CACHEGROUP_PARTICLE_union-module_com.sbt.bm.ucp.common.dpl.model.dictionary.DServiceZone,
partId=98]
Partition instances: [PartitionHashRecordV2 [isPrimary=true,
consistentId=node2, updateCntr=1519, size=596, partHash=-1167688484],
PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=1520,
size=596, partHash=-1167688484]]
Conflict partition: PartitionKeyV2 [grpId=-1903385190,
grpName=CACHEGROUP_PARTICLE_union-module_com.sbt.bm.ucp.common.dpl.model.dictionary.DServiceZone,
partId=34]
Partition instances: [PartitionHashRecordV2 [isPrimary=false,
consistentId=node2, updateCntr=1539, size=596, partHash=-99631005],
PartitionHashRecordV2 [isPrimary=true, consistentId=node1, updateCntr=1537,
size=596, partHash=-1284437377]]
Conflict partition: PartitionKeyV2 [grpId=770187303,
grpName=CACHEGROUP_PARTICLE_currency-rates_com.sbt.cdm.api.model.dictionary.RKOKCostLevels,
partId=31]
Partition instances: [PartitionHashRecordV2 [isPrimary=true,
consistentId=node2, updateCntr=15, size=4, partHash=-1125172674],
PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=16,
size=4, partHash=-1125172674]]
Conflict partition: PartitionKeyV2 [grpId=-1903385190,
grpName=CACHEGROUP_PARTICLE_union-module_com.sbt.bm.ucp.common.dpl.model.dictionary.DServiceZone,
partId=39]
Partition instances: [PartitionHashRecordV2 [isPrimary=true,
consistentId=node2, updateCntr=1555, size=596, partHash=-40303136],
PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=1556,
size=596, partHash=-40303136]]
Conflict partition: PartitionKeyV2 [grpId=-1903385190,
grpName=CACHEGROUP_PARTICLE_union-module_com.sbt.bm.ucp.common.dpl.model.dictionary.DServiceZone,
partId=90]
Partition instances: [PartitionHashRecordV2 [isPrimary=false,
consistentId=node2, updateCntr=1557, size=596, partHash=-1295145299],
PartitionHashRecordV2 [isPrimary=true, consistentId=node1, updateCntr=1556,
size=596, partHash=-1221175703]]
Conflict partition: PartitionKeyV2 [grpId=-1903385190,
grpName=CACHEGROUP_PARTICLE_union-module_com.sbt.bm.ucp.common.dpl.model.dictionary.DServiceZone,
partId=28]
Partition instances: [PartitionHashRecordV2 [isPrimary=true,
consistentId=node2, updateCntr=1480, size=596, partHash=840625505],
PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=1481,
size=596, partHash=840625505]]
Conflict partition: PartitionKeyV2 [grpId=-1903385190,
grpName=CACHEGROUP_PARTICLE_union-module_com.sbt.bm.ucp.common.dpl.model.dictionary.DServiceZone,
partId=29]
Partition instances: [PartitionHashRecordV2 [isPrimary=true,
[jira] [Updated] (IGNITE-9905) After transaction load cluster inconsistent
[
https://issues.apache.org/jira/browse/IGNITE-9905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ARomantsov updated IGNITE-9905:
---
Description:
One server, two nodes per server, one client
Loaded data into the cluster using transactions consisting of two get / two put
{code:java}
idle_verify check has finished, found 60 conflict partitions:
[counterConflicts=45, hashConflicts=15]
Update counter conflicts:
Conflict partition: PartitionKeyV2 [grpId=-1903385190,
grpName=CACHEGROUP_PARTICLE_union-module_com.sbt.bm.ucp.common.dpl.model.dictionary.DServiceZone,
partId=98]
Partition instances: [PartitionHashRecordV2 [isPrimary=true,
consistentId=node2, updateCntr=1519, size=596, partHash=-1167688484],
PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=1520,
size=596, partHash=-1167688484]]
Conflict partition: PartitionKeyV2 [grpId=-1903385190,
grpName=CACHEGROUP_PARTICLE_union-module_com.sbt.bm.ucp.common.dpl.model.dictionary.DServiceZone,
partId=34]
Partition instances: [PartitionHashRecordV2 [isPrimary=false,
consistentId=node2, updateCntr=1539, size=596, partHash=-99631005],
PartitionHashRecordV2 [isPrimary=true, consistentId=node1, updateCntr=1537,
size=596, partHash=-1284437377]]
Conflict partition: PartitionKeyV2 [grpId=770187303,
grpName=CACHEGROUP_PARTICLE_currency-rates_com.sbt.cdm.api.model.dictionary.RKOKCostLevels,
partId=31]
Partition instances: [PartitionHashRecordV2 [isPrimary=true,
consistentId=node2, updateCntr=15, size=4, partHash=-1125172674],
PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=16,
size=4, partHash=-1125172674]]
Conflict partition: PartitionKeyV2 [grpId=-1903385190,
grpName=CACHEGROUP_PARTICLE_union-module_com.sbt.bm.ucp.common.dpl.model.dictionary.DServiceZone,
partId=39]
Partition instances: [PartitionHashRecordV2 [isPrimary=true,
consistentId=node2, updateCntr=1555, size=596, partHash=-40303136],
PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=1556,
size=596, partHash=-40303136]]
Conflict partition: PartitionKeyV2 [grpId=-1903385190,
grpName=CACHEGROUP_PARTICLE_union-module_com.sbt.bm.ucp.common.dpl.model.dictionary.DServiceZone,
partId=90]
Partition instances: [PartitionHashRecordV2 [isPrimary=false,
consistentId=node2, updateCntr=1557, size=596, partHash=-1295145299],
PartitionHashRecordV2 [isPrimary=true, consistentId=node1, updateCntr=1556,
size=596, partHash=-1221175703]]
Conflict partition: PartitionKeyV2 [grpId=-1903385190,
grpName=CACHEGROUP_PARTICLE_union-module_com.sbt.bm.ucp.common.dpl.model.dictionary.DServiceZone,
partId=28]
Partition instances: [PartitionHashRecordV2 [isPrimary=true,
consistentId=node2, updateCntr=1480, size=596, partHash=840625505],
PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=1481,
size=596, partHash=840625505]]
Conflict partition: PartitionKeyV2 [grpId=-1903385190,
grpName=CACHEGROUP_PARTICLE_union-module_com.sbt.bm.ucp.common.dpl.model.dictionary.DServiceZone,
partId=29]
Partition instances: [PartitionHashRecordV2 [isPrimary=true,
consistentId=node2, updateCntr=1518, size=596, partHash=-65201475],
PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=1519,
size=596, partHash=-446824253]]
Conflict partition: PartitionKeyV2 [grpId=-1903385190,
grpName=CACHEGROUP_PARTICLE_union-module_com.sbt.bm.ucp.common.dpl.model.dictionary.DServiceZone,
partId=94]
Partition instances: [PartitionHashRecordV2 [isPrimary=true,
consistentId=node2, updateCntr=1556, size=596, partHash=-1459651056],
PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=1558,
size=596, partHash=-1459651056]]
Conflict partition: PartitionKeyV2 [grpId=-1903385190,
grpName=CACHEGROUP_PARTICLE_union-module_com.sbt.bm.ucp.common.dpl.model.dictionary.DServiceZone,
partId=30]
Partition instances: [PartitionHashRecordV2 [isPrimary=true,
consistentId=node2, updateCntr=1518, size=596, partHash=170987026],
PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=1519,
size=596, partHash=170987026]]
Conflict partition: PartitionKeyV2 [grpId=-1903385190,
grpName=CACHEGROUP_PARTICLE_union-module_com.sbt.bm.ucp.common.dpl.model.dictionary.DServiceZone,
partId=97]
Partition instances: [PartitionHashRecordV2 [isPrimary=false,
consistentId=node2, updateCntr=1475, size=596, partHash=-587015760],
PartitionHashRecordV2 [isPrimary=true, consistentId=node1, updateCntr=1474,
size=596, partHash=-587015760]]
Conflict partition: PartitionKeyV2 [grpId=321390040,
grpName=CACHEGROUP_DICTIONARY, partId=47]
Partition instances: [PartitionHashRecordV2 [isPrimary=true,
consistentId=node2, updateCntr=1871, size=1403, partHash=984736761],
PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=1872,
size=1403, partHash=984736761]]
Conflict partition: PartitionKeyV2 [grpId=321390040,
grpName=CACHEGROUP_DICTIONARY, partId=38]
Partition instances:
[jira] [Updated] (IGNITE-9905) After transaction load cluster inconsistent
[
https://issues.apache.org/jira/browse/IGNITE-9905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ARomantsov updated IGNITE-9905:
---
Description:
Loaded data into the cluster using transactions consisting of two get / two put
{code:java}
idle_verify check has finished, found 60 conflict partitions:
[counterConflicts=45, hashConflicts=15]
Update counter conflicts:
Conflict partition: PartitionKeyV2 [grpId=-1903385190,
grpName=CACHEGROUP_PARTICLE_union-module_com.sbt.bm.ucp.common.dpl.model.dictionary.DServiceZone,
partId=98]
Partition instances: [PartitionHashRecordV2 [isPrimary=true,
consistentId=node2, updateCntr=1519, size=596, partHash=-1167688484],
PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=1520,
size=596, partHash=-1167688484]]
Conflict partition: PartitionKeyV2 [grpId=-1903385190,
grpName=CACHEGROUP_PARTICLE_union-module_com.sbt.bm.ucp.common.dpl.model.dictionary.DServiceZone,
partId=34]
Partition instances: [PartitionHashRecordV2 [isPrimary=false,
consistentId=node2, updateCntr=1539, size=596, partHash=-99631005],
PartitionHashRecordV2 [isPrimary=true, consistentId=node1, updateCntr=1537,
size=596, partHash=-1284437377]]
Conflict partition: PartitionKeyV2 [grpId=770187303,
grpName=CACHEGROUP_PARTICLE_currency-rates_com.sbt.cdm.api.model.dictionary.RKOKCostLevels,
partId=31]
Partition instances: [PartitionHashRecordV2 [isPrimary=true,
consistentId=node2, updateCntr=15, size=4, partHash=-1125172674],
PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=16,
size=4, partHash=-1125172674]]
Conflict partition: PartitionKeyV2 [grpId=-1903385190,
grpName=CACHEGROUP_PARTICLE_union-module_com.sbt.bm.ucp.common.dpl.model.dictionary.DServiceZone,
partId=39]
Partition instances: [PartitionHashRecordV2 [isPrimary=true,
consistentId=node2, updateCntr=1555, size=596, partHash=-40303136],
PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=1556,
size=596, partHash=-40303136]]
Conflict partition: PartitionKeyV2 [grpId=-1903385190,
grpName=CACHEGROUP_PARTICLE_union-module_com.sbt.bm.ucp.common.dpl.model.dictionary.DServiceZone,
partId=90]
Partition instances: [PartitionHashRecordV2 [isPrimary=false,
consistentId=node2, updateCntr=1557, size=596, partHash=-1295145299],
PartitionHashRecordV2 [isPrimary=true, consistentId=node1, updateCntr=1556,
size=596, partHash=-1221175703]]
Conflict partition: PartitionKeyV2 [grpId=-1903385190,
grpName=CACHEGROUP_PARTICLE_union-module_com.sbt.bm.ucp.common.dpl.model.dictionary.DServiceZone,
partId=28]
Partition instances: [PartitionHashRecordV2 [isPrimary=true,
consistentId=node2, updateCntr=1480, size=596, partHash=840625505],
PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=1481,
size=596, partHash=840625505]]
Conflict partition: PartitionKeyV2 [grpId=-1903385190,
grpName=CACHEGROUP_PARTICLE_union-module_com.sbt.bm.ucp.common.dpl.model.dictionary.DServiceZone,
partId=29]
Partition instances: [PartitionHashRecordV2 [isPrimary=true,
consistentId=node2, updateCntr=1518, size=596, partHash=-65201475],
PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=1519,
size=596, partHash=-446824253]]
Conflict partition: PartitionKeyV2 [grpId=-1903385190,
grpName=CACHEGROUP_PARTICLE_union-module_com.sbt.bm.ucp.common.dpl.model.dictionary.DServiceZone,
partId=94]
Partition instances: [PartitionHashRecordV2 [isPrimary=true,
consistentId=node2, updateCntr=1556, size=596, partHash=-1459651056],
PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=1558,
size=596, partHash=-1459651056]]
Conflict partition: PartitionKeyV2 [grpId=-1903385190,
grpName=CACHEGROUP_PARTICLE_union-module_com.sbt.bm.ucp.common.dpl.model.dictionary.DServiceZone,
partId=30]
Partition instances: [PartitionHashRecordV2 [isPrimary=true,
consistentId=node2, updateCntr=1518, size=596, partHash=170987026],
PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=1519,
size=596, partHash=170987026]]
Conflict partition: PartitionKeyV2 [grpId=-1903385190,
grpName=CACHEGROUP_PARTICLE_union-module_com.sbt.bm.ucp.common.dpl.model.dictionary.DServiceZone,
partId=97]
Partition instances: [PartitionHashRecordV2 [isPrimary=false,
consistentId=node2, updateCntr=1475, size=596, partHash=-587015760],
PartitionHashRecordV2 [isPrimary=true, consistentId=node1, updateCntr=1474,
size=596, partHash=-587015760]]
Conflict partition: PartitionKeyV2 [grpId=321390040,
grpName=CACHEGROUP_DICTIONARY, partId=47]
Partition instances: [PartitionHashRecordV2 [isPrimary=true,
consistentId=node2, updateCntr=1871, size=1403, partHash=984736761],
PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=1872,
size=1403, partHash=984736761]]
Conflict partition: PartitionKeyV2 [grpId=321390040,
grpName=CACHEGROUP_DICTIONARY, partId=38]
Partition instances: [PartitionHashRecordV2 [isPrimary=true,
[jira] [Updated] (IGNITE-9905) After transaction load cluster inconsistent
[
https://issues.apache.org/jira/browse/IGNITE-9905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ARomantsov updated IGNITE-9905:
---
Security: (was: Private)
> After transaction load cluster inconsistent
> ---
>
> Key: IGNITE-9905
> URL: https://issues.apache.org/jira/browse/IGNITE-9905
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Affects Versions: 2.7
>Reporter: ARomantsov
>Priority: Critical
> Fix For: 2.7
>
>
> {code:java}
> idle_verify check has finished, found 60 conflict partitions:
> [counterConflicts=45, hashConflicts=15]
> Update counter conflicts:
> Conflict partition: PartitionKeyV2 [grpId=-1903385190,
> grpName=CACHEGROUP_PARTICLE_union-module_com.sbt.bm.ucp.common.dpl.model.dictionary.DServiceZone,
> partId=98]
> Partition instances: [PartitionHashRecordV2 [isPrimary=true,
> consistentId=node2, updateCntr=1519, size=596, partHash=-1167688484],
> PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=1520,
> size=596, partHash=-1167688484]]
> Conflict partition: PartitionKeyV2 [grpId=-1903385190,
> grpName=CACHEGROUP_PARTICLE_union-module_com.sbt.bm.ucp.common.dpl.model.dictionary.DServiceZone,
> partId=34]
> Partition instances: [PartitionHashRecordV2 [isPrimary=false,
> consistentId=node2, updateCntr=1539, size=596, partHash=-99631005],
> PartitionHashRecordV2 [isPrimary=true, consistentId=node1, updateCntr=1537,
> size=596, partHash=-1284437377]]
> Conflict partition: PartitionKeyV2 [grpId=770187303,
> grpName=CACHEGROUP_PARTICLE_currency-rates_com.sbt.cdm.api.model.dictionary.RKOKCostLevels,
> partId=31]
> Partition instances: [PartitionHashRecordV2 [isPrimary=true,
> consistentId=node2, updateCntr=15, size=4, partHash=-1125172674],
> PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=16,
> size=4, partHash=-1125172674]]
> Conflict partition: PartitionKeyV2 [grpId=-1903385190,
> grpName=CACHEGROUP_PARTICLE_union-module_com.sbt.bm.ucp.common.dpl.model.dictionary.DServiceZone,
> partId=39]
> Partition instances: [PartitionHashRecordV2 [isPrimary=true,
> consistentId=node2, updateCntr=1555, size=596, partHash=-40303136],
> PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=1556,
> size=596, partHash=-40303136]]
> Conflict partition: PartitionKeyV2 [grpId=-1903385190,
> grpName=CACHEGROUP_PARTICLE_union-module_com.sbt.bm.ucp.common.dpl.model.dictionary.DServiceZone,
> partId=90]
> Partition instances: [PartitionHashRecordV2 [isPrimary=false,
> consistentId=node2, updateCntr=1557, size=596, partHash=-1295145299],
> PartitionHashRecordV2 [isPrimary=true, consistentId=node1, updateCntr=1556,
> size=596, partHash=-1221175703]]
> Conflict partition: PartitionKeyV2 [grpId=-1903385190,
> grpName=CACHEGROUP_PARTICLE_union-module_com.sbt.bm.ucp.common.dpl.model.dictionary.DServiceZone,
> partId=28]
> Partition instances: [PartitionHashRecordV2 [isPrimary=true,
> consistentId=node2, updateCntr=1480, size=596, partHash=840625505],
> PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=1481,
> size=596, partHash=840625505]]
> Conflict partition: PartitionKeyV2 [grpId=-1903385190,
> grpName=CACHEGROUP_PARTICLE_union-module_com.sbt.bm.ucp.common.dpl.model.dictionary.DServiceZone,
> partId=29]
> Partition instances: [PartitionHashRecordV2 [isPrimary=true,
> consistentId=node2, updateCntr=1518, size=596, partHash=-65201475],
> PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=1519,
> size=596, partHash=-446824253]]
> Conflict partition: PartitionKeyV2 [grpId=-1903385190,
> grpName=CACHEGROUP_PARTICLE_union-module_com.sbt.bm.ucp.common.dpl.model.dictionary.DServiceZone,
> partId=94]
> Partition instances: [PartitionHashRecordV2 [isPrimary=true,
> consistentId=node2, updateCntr=1556, size=596, partHash=-1459651056],
> PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=1558,
> size=596, partHash=-1459651056]]
> Conflict partition: PartitionKeyV2 [grpId=-1903385190,
> grpName=CACHEGROUP_PARTICLE_union-module_com.sbt.bm.ucp.common.dpl.model.dictionary.DServiceZone,
> partId=30]
> Partition instances: [PartitionHashRecordV2 [isPrimary=true,
> consistentId=node2, updateCntr=1518, size=596, partHash=170987026],
> PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=1519,
> size=596, partHash=170987026]]
> Conflict partition: PartitionKeyV2 [grpId=-1903385190,
> grpName=CACHEGROUP_PARTICLE_union-module_com.sbt.bm.ucp.common.dpl.model.dictionary.DServiceZone,
> partId=97]
> Partition instances: [PartitionHashRecordV2 [isPrimary=false,
> consistentId=node2, updateCntr=1475, size=596, partHash=-587015760],
> PartitionHashRecordV2 [isPrimary=true, consistentId=node1, updateCntr=1474,
> size=596,
[jira] [Commented] (IGNITE-9739) Critical exception in transaction processing in case we have nodes out of baseline and non-persisted cache
[
https://issues.apache.org/jira/browse/IGNITE-9739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16652035#comment-16652035
]
Ignite TC Bot commented on IGNITE-9739:
---
{panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Hadoop{color} [[tests 0 TIMEOUT , Out Of Memory Error , Exit
Code |https://ci.ignite.apache.org/viewLog.html?buildId=2089514]]
* HadoopMapReduceErrorResilienceTest.testRecoveryAfterAnError7_Runtime (last
started)
{color:#d04437}_Javadoc_{color} [[tests 0 Exit Code , BuildFailureOnMessage
|https://ci.ignite.apache.org/viewLog.html?buildId=2089563]]
{panel}
[TeamCity Run
All|http://ci.ignite.apache.org/viewLog.html?buildId=2089597buildTypeId=IgniteTests24Java8_RunAll]
> Critical exception in transaction processing in case we have nodes out of
> baseline and non-persisted cache
> --
>
> Key: IGNITE-9739
> URL: https://issues.apache.org/jira/browse/IGNITE-9739
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Reporter: Sergey Kosarev
>Assignee: Sergey Kosarev
>Priority: Major
>
> Activation finished
> {code:java}
> 2018-09-20 20:47:05.169 [INFO
> ][sys-#307%DPL_GRID%DplGridNodeName%][o.g.g.i.p.c.d.GridSnapshotAwareClusterStateProcessorImpl]
> Successfully performed final activation steps
> [nodeId=382437eb-fd8a-4f92-acd5-d9ea562c8557, client=false,
> topVer=AffinityTopologyVersion [topVer=160, minorTopVer=1]]
> {code}
> but we have nodes not in base line
> {code:java}
> 2018-09-20 20:45:36.116 [INFO
> ][sys-#305%DPL_GRID%DplGridNodeName%][o.g.g.i.p.c.d.GridSnapshotAwareClusterStateProcessorImpl]
> Local node is not included in Baseline Topology and will not be used for
> persistent data storage. Use control.(sh|bat) script or IgniteCluster
> interface to include the node to Baseline Topology.
> {code}
> And we have cache (869481129) in the data region with persistanceEnabled=false
> {code:java}
> 2018-09-20 20:49:01.825 [INFO
> ][exchange-worker-#154%DPL_GRID%DplGridNodeName%][o.a.i.i.p.cache.GridCacheProcessor]
> Started cache [name=DPL_PUBLISHED_CACHES_REGISTRY$, *id=869481129*, group=SY
> STEM_CACHEGROUP_PUBLISHED_REGISTRY, memoryPolicyName=not-persisted,
> mode=PARTITIONED, atomicity=TRANSACTIONAL, backups=3]
> {code}
> Transaction on this cache(869481129)
> {code:java}
> 869481129{code}
> leads to critical error causing nodes by faulure handler:
> {code:java}
> 2018-09-20 20:50:24.275
> [ERROR][sys-stripe-41-#42%DPL_GRID%DplGridNodeName%][o.a.i.i.p.cache.GridCacheIoManager]
> Failed processing message [senderId=62e986f0-62b5-4ec8-8cc7-27b74d345235,
> msg=GridDhtTxPrepareRequest [nearNodeId=814af7c4-2de5-4511-b1ea-065b91eaa774,
> futId=520e308f561-255fdea5-a996-4102-a120-afa380c54570, miniId=1,
> topVer=AffinityTopologyVersion [topVer=160, minorTopVer=2],
> invalidateNearEntries={}, nearWrites=null, owned=null,
> nearXidVer=GridCacheVersion [topVer=148944365, order=1537511036821,
> nodeOrder=132], subjId=814af7c4-2de5-4511-b1ea-065b91eaa774, taskNameHash=0,
> preloadKeys=null, skipCompletedVers=false,
> super=GridDistributedTxPrepareRequest [threadId=58, concurrency=PESSIMISTIC,
> isolation=READ_COMMITTED, writeVer=GridCacheVersion [topVer=148944365,
> order=1537511036824, nodeOrder=7], timeout=299970, reads=null,
> writes=ArrayList [
> IgniteTxEntry [key=KeyCacheObjectImpl [part=27254,
> val=com.sbt.api.entities.out.IPublishedDocType, hasValBytes=true],
> *cacheId=869481129*,
> txKey=IgniteTxKey [key=KeyCacheObjectImpl [part=27254,
> val=com.sbt.api.entities.out.IPublishedDocType, hasValBytes=true],
> *cacheId=869481129*], val=[op=CREATE,
> val=com.sbt.dpl.gridgain.PublishedRegistry$PublishedCacheTuple
> [idHash=811765531, hash=1522508040,
> cacheName=com.sbt.gbk.entities.DocType_DPL_union-module,indexes=ArrayList
> {com.sbt.dpl.gridgain.newModel.base.indexes.PublishedIndexType
> [idHash=1583970836, hash=363194492, isSoftReference=false,
> unselectiveBuckets=4096, fieldNames=ArrayList
> \{isDeleted},moduleName=union-module
> , cachedUnselectives=1, selectors=ArrayList {isDeleted},
> exceptUnselectives=false, primitiveCollection=false, isVersioned=false,
> isComposite=false, isSystemTypeBelongs=false,
> name=com.sbt.gbk.entities.DocType_DPL_isDeleted, isIndexedCollection=false,
> isGlobal=false, maxSelective=1000],
> com.sbt.dpl.gridgain.newModel.base.indexes.PublishedIndexType
> [idHash=2060926101, hash=1983794578, isSoftReference=false,
> unselectiveBuckets=4096, fieldNames=ArrayList ,moduleName=union-module,
> cachedUnselectives=1, selectors=ArrayList, exceptUnselectives=false,
> primitiveCollection=false, isVersioned=false, isComposite=false,
> isSystemTypeBelongs=false,
[jira] [Updated] (IGNITE-9904) CPP Thin: Implement atomic part of Cache API for C++ thin client
[
https://issues.apache.org/jira/browse/IGNITE-9904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego updated IGNITE-9904:
Description:
Need to implement atomic part of cache API:
# {{ReplaceIfEquals}}
# {{RemoveIfEquals}}
# {{GetAndPut}}
# {{GetAndRemove}}
# {{GetAndReplace}}
# {{PutIfAbsent}}
# {{GetAndPutIfAbsent}}
was:
Need to implement atomic part of cache API:
# replaceIfEquals
# removeIfEquals
# getAndPut
# getAndRemove
# getAndReplace
# putIfAbsent
# getAndPutIfAbsent
> CPP Thin: Implement atomic part of Cache API for C++ thin client
>
>
> Key: IGNITE-9904
> URL: https://issues.apache.org/jira/browse/IGNITE-9904
> Project: Ignite
> Issue Type: New Feature
> Components: thin client
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>Priority: Major
> Labels: cpp
> Fix For: 2.8
>
>
> Need to implement atomic part of cache API:
> # {{ReplaceIfEquals}}
> # {{RemoveIfEquals}}
> # {{GetAndPut}}
> # {{GetAndRemove}}
> # {{GetAndReplace}}
> # {{PutIfAbsent}}
> # {{GetAndPutIfAbsent}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9904) CPP Thin: Implement atomic part of Cache API for C++ thin client
[ https://issues.apache.org/jira/browse/IGNITE-9904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-9904: Description: Need to implement atomic part of cache API: # replaceIfEquals # removeIfEquals # getAndPut # getAndRemove # getAndReplace # putIfAbsent # getAndPutIfAbsent was:Need to implement atomic part of cache API: replaceIfEquals, removeIfEquals, getAndPut, getAndRemove, getAndReplace, putIfAbsent, getAndPutIfAbsent > CPP Thin: Implement atomic part of Cache API for C++ thin client > > > Key: IGNITE-9904 > URL: https://issues.apache.org/jira/browse/IGNITE-9904 > Project: Ignite > Issue Type: New Feature > Components: thin client >Reporter: Igor Sapego >Assignee: Igor Sapego >Priority: Major > Labels: cpp > Fix For: 2.8 > > > Need to implement atomic part of cache API: > # replaceIfEquals > # removeIfEquals > # getAndPut > # getAndRemove > # getAndReplace > # putIfAbsent > # getAndPutIfAbsent -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9904) CPP Thin: Implement atomic part of Cache API for C++ thin client
[ https://issues.apache.org/jira/browse/IGNITE-9904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-9904: Description: Need to implement atomic part of cache API: replaceIfEquals, removeIfEquals, getAndPut, getAndRemove, getAndReplace, putIfAbsent, getAndPutIfAbsent > CPP Thin: Implement atomic part of Cache API for C++ thin client > > > Key: IGNITE-9904 > URL: https://issues.apache.org/jira/browse/IGNITE-9904 > Project: Ignite > Issue Type: New Feature > Components: thin client >Reporter: Igor Sapego >Assignee: Igor Sapego >Priority: Major > Labels: cpp > Fix For: 2.8 > > > Need to implement atomic part of cache API: replaceIfEquals, removeIfEquals, > getAndPut, getAndRemove, getAndReplace, putIfAbsent, getAndPutIfAbsent -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9904) CPP Thin: Implement atomic part of Cache API for C++ thin client
[ https://issues.apache.org/jira/browse/IGNITE-9904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-9904: Labels: cpp (was: ) > CPP Thin: Implement atomic part of Cache API for C++ thin client > > > Key: IGNITE-9904 > URL: https://issues.apache.org/jira/browse/IGNITE-9904 > Project: Ignite > Issue Type: New Feature > Components: thin client >Reporter: Igor Sapego >Assignee: Igor Sapego >Priority: Major > Labels: cpp > Fix For: 2.8 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9904) CPP Thin: Implement atomic part of Cache API for C++ thin client
[ https://issues.apache.org/jira/browse/IGNITE-9904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego reassigned IGNITE-9904: --- Assignee: Igor Sapego > CPP Thin: Implement atomic part of Cache API for C++ thin client > > > Key: IGNITE-9904 > URL: https://issues.apache.org/jira/browse/IGNITE-9904 > Project: Ignite > Issue Type: New Feature > Components: thin client >Reporter: Igor Sapego >Assignee: Igor Sapego >Priority: Major > Fix For: 2.8 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9904) CPP Thin: Implement atomic part of Cache API for C++ thin client
Igor Sapego created IGNITE-9904: --- Summary: CPP Thin: Implement atomic part of Cache API for C++ thin client Key: IGNITE-9904 URL: https://issues.apache.org/jira/browse/IGNITE-9904 Project: Ignite Issue Type: New Feature Components: thin client Reporter: Igor Sapego Fix For: 2.8 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9891) ODBC: SQLTables does not work with list of table types
[
https://issues.apache.org/jira/browse/IGNITE-9891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16652004#comment-16652004
]
Igor Sapego commented on IGNITE-9891:
-
[~vozerov] thank you
> ODBC: SQLTables does not work with list of table types
> --
>
> Key: IGNITE-9891
> URL: https://issues.apache.org/jira/browse/IGNITE-9891
> Project: Ignite
> Issue Type: Bug
> Components: odbc
>Affects Versions: 2.6
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>Priority: Major
> Labels: odbc
> Fix For: 2.7
>
>
> {{SQLTables}} do not work with list of table types as stated in
> https://docs.microsoft.com/en-us/sql/odbc/reference/syntax/sqltables-function?view=sql-server-2017
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7196) Exchange can stuck and wait while new node restoring state from disk and starting caches
[
https://issues.apache.org/jira/browse/IGNITE-7196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16652000#comment-16652000
]
Pavel Kovalenko commented on IGNITE-7196:
-
[~Mmuzaf] [~DmitriyGovorukhin] Changes look good to me. Ready to merge.
> Exchange can stuck and wait while new node restoring state from disk and
> starting caches
>
>
> Key: IGNITE-7196
> URL: https://issues.apache.org/jira/browse/IGNITE-7196
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.3
>Reporter: Mikhail Cherkasov
>Assignee: Maxim Muzafarov
>Priority: Critical
> Fix For: 2.8
>
>
> Exchange can stuck and wait while new node restoring state from disk and
> starting caches, there's a log snippet from a just joined new node that shows
> the issue:
> {noformat}
> [21:36:13,023][INFO][exchange-worker-#62%statement_grid%][time] Started
> exchange init [topVer=AffinityTopologyVersion [topVer=57, minorTopVer=0],
> crd=false, evt=NODE_JOINED, evtNode=3ac1160e-0de4-41bc-a366-59292c9f03c1,
> customEvt=null, allowMerge=true]
> [21:36:13,023][INFO][exchange-worker-#62%statement_grid%][FilePageStoreManager]
> Resolved page store work directory:
> /mnt/store/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463
> [21:36:13,024][INFO][exchange-worker-#62%statement_grid%][FileWriteAheadLogManager]
> Resolved write ahead log work directory:
> /mnt/wal/WAL/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463
> [21:36:13,024][INFO][exchange-worker-#62%statement_grid%][FileWriteAheadLogManager]
> Resolved write ahead log archive directory:
> /mnt/wal/WAL_archive/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463
> [21:36:13,046][INFO][exchange-worker-#62%statement_grid%][FileWriteAheadLogManager]
> Started write-ahead log manager [mode=DEFAULT]
> [21:36:13,065][INFO][exchange-worker-#62%statement_grid%][PageMemoryImpl]
> Started page memory [memoryAllocated=100.0 MiB, pages=6352, tableSize=373.4
> KiB, checkpointBuffer=100.0 MiB]
> [21:36:13,105][INFO][exchange-worker-#62%statement_grid%][PageMemoryImpl]
> Started page memory [memoryAllocated=32.0 GiB, pages=2083376, tableSize=119.6
> MiB, checkpointBuffer=896.0 MiB]
> [21:36:13,428][INFO][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager]
> Read checkpoint status
> [startMarker=/mnt/store/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463/cp/1512930965253-306c0895-1f5f-4237-bebf-8bf2b49682af-START.bin,
>
> endMarker=/mnt/store/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463/cp/1512930869357-1c24b6dc-d64c-4b83-8166-11edf1bfdad3-END.bin]
> [21:36:13,429][INFO][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager]
> Checking memory state [lastValidPos=FileWALPointer [idx=3582,
> fileOffset=59186076, len=9229, forceFlush=false], lastMarked=FileWALPointer
> [idx=3629, fileOffset=50829700, len=9229, forceFlush=false],
> lastCheckpointId=306c0895-1f5f-4237-bebf-8bf2b49682af]
> [21:36:13,429][WARNING][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager]
> Ignite node stopped in the middle of checkpoint. Will restore memory state
> and finish checkpoint on node start.
> [21:36:18,312][INFO][grid-nio-worker-tcp-comm-0-#41%statement_grid%][TcpCommunicationSpi]
> Accepted incoming communication connection [locAddr=/172.31.20.209:48100,
> rmtAddr=/172.31.17.115:57148]
> [21:36:21,619][INFO][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager]
> Found last checkpoint marker [cpId=306c0895-1f5f-4237-bebf-8bf2b49682af,
> pos=FileWALPointer [idx=3629, fileOffset=50829700, len=9229,
> forceFlush=false]]
> [21:36:21,620][INFO][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager]
> Finished applying memory changes [changesApplied=165103, time=8189ms]
> [21:36:22,403][INFO][grid-nio-worker-tcp-comm-1-#42%statement_grid%][TcpCommunicationSpi]
> Accepted incoming communication connection [locAddr=/172.31.20.209:48100,
> rmtAddr=/172.31.28.10:47964]
> [21:36:23,414][INFO][grid-nio-worker-tcp-comm-2-#43%statement_grid%][TcpCommunicationSpi]
> Accepted incoming communication connection [locAddr=/172.31.20.209:48100,
> rmtAddr=/172.31.27.101:46000]
> [21:36:33,019][WARNING][main][GridCachePartitionExchangeManager] Failed to
> wait for initial partition map exchange. Possible reasons are:
> ^-- Transactions in deadlock.
> ^-- Long running transactions (ignore if this is the case).
> ^-- Unreleased explicit locks.
> [21:36:53,021][WARNING][main][GridCachePartitionExchangeManager] Still
> waiting for initial partition map exchange
> [fut=GridDhtPartitionsExchangeFuture [firstDiscoEvt=DiscoveryEvent
> [evtNode=TcpDiscoveryNode [id=3ac1160e-0de4-41bc-a366-59292c9f03c1,
> addrs=[0:0:0:0:0:0:0:1%lo, 127.0.0.1, 172.31.20.209],
>
[jira] [Commented] (IGNITE-9882) OOME in Hadoop suite
[
https://issues.apache.org/jira/browse/IGNITE-9882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16651970#comment-16651970
]
Taras Ledkov commented on IGNITE-9882:
--
[~vozerov], I fixed the hadoop suite run (please take a look at the [tests
results|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Hadoop_IgniteTests24Java8=pull%2F5003%2Fhead=buildTypeStatusDiv]),
but the fix isn't in scope H2 lazy patch.
I guess the root cause is:
{{HadoopClassLoader}} implementation & hadoop helper produce memory leaks (e.g.
{{GridKernalContext}}). And H2 lazy patch add the last critical allocates for
one instance of {{GridKernalContext}} because connection pool was changed etc.
The patch for this problem doesn't solve all leaks in the hadoop module but
reduce them.
Please review the draft of the patch. I'll fix cosmetics if you agree in
general.
> OOME in Hadoop suite
>
>
> Key: IGNITE-9882
> URL: https://issues.apache.org/jira/browse/IGNITE-9882
> Project: Ignite
> Issue Type: Bug
> Components: hadoop, sql
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
>Priority: Blocker
> Fix For: 2.7
>
>
> Hadoop suite starts failing with OOME after several commits were merged. I
> suspect that it may be related to IGNITE-9171 merge or IGNITE-9561. See two
> runs:
> Failure:
> https://ci.ignite.apache.org/viewLog.html?buildId=2063682=buildResultsDiv=IgniteTests24Java8_Hadoop
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9853) control.sh show more information about cache configuration
[
https://issues.apache.org/jira/browse/IGNITE-9853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16651956#comment-16651956
]
Sergey Antonov commented on IGNITE-9853:
{{[~kuaw26] I reused --cache list command. Could you review my changes again?}}
> control.sh show more information about cache configuration
> --
>
> Key: IGNITE-9853
> URL: https://issues.apache.org/jira/browse/IGNITE-9853
> Project: Ignite
> Issue Type: Improvement
>Reporter: Sergey Antonov
>Assignee: Sergey Antonov
>Priority: Major
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9903) Copy only actual amount of data during archiving of WAL segment
Andrey Gura created IGNITE-9903:
---
Summary: Copy only actual amount of data during archiving of WAL
segment
Key: IGNITE-9903
URL: https://issues.apache.org/jira/browse/IGNITE-9903
Project: Ignite
Issue Type: Improvement
Reporter: Andrey Gura
Assignee: Andrey Gura
Fix For: 2.8
Current WAL archiver implementation copies full WAL segment to the archive
while actual size of the segment can be significantly less then
{{maxWalSegmentSize}} (segment files are preallocated for max possible segment
size).
In order to reduce disk space consuming we need copy only actual data of
segment using {{SWITCH_SEGMENT_RECORD}} as marker. It will require some kind of
WAL iterator implementation that will just copy WAL records using information
about record size without records deserialization.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9710) Ignite watchdog service handles longrunning cache creation
[
https://issues.apache.org/jira/browse/IGNITE-9710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16651936#comment-16651936
]
Andrey Kuznetsov commented on IGNITE-9710:
--
[~agoncharuk], [~agura], thanks for your comments. I've made all required
changes. I had to update progress marker for exchanger worker from threads
other than exchanger thread. Are you ok with this?
TeamCity (re)tests are in progress right now.
> Ignite watchdog service handles longrunning cache creation
> --
>
> Key: IGNITE-9710
> URL: https://issues.apache.org/jira/browse/IGNITE-9710
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.6
>Reporter: Vyacheslav Daradur
>Assignee: Andrey Kuznetsov
>Priority: Major
> Fix For: 2.7
>
> Attachments: LongRunningCacheCreationTest.java
>
>
> Ignite watchdog service introduced by IGNITE-6587 handles long running cache
> creation.
> Action in {{GridDhtPartitionsExchangeFuture#init}} may take significant time
> and possibly should be covered by blocking section of warchdog service.
> Reproducer was attached: [^LongRunningCacheCreationTest.java].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (IGNITE-9165) FindBugs: Methods may fail to close stream in core module
[
https://issues.apache.org/jira/browse/IGNITE-9165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
PetrovMikhail updated IGNITE-9165:
--
Comment: was deleted
(was: {panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Hadoop{color} [[tests 0 TIMEOUT , Out Of Memory Error , Exit
Code , [Artifacts publishing failed]
|https://ci.ignite.apache.org/viewLog.html?buildId=2088269]]
* HadoopMapReduceErrorResilienceTest.testRecoveryAfterAnError0_Error (last
started)
{color:#d04437}_Javadoc_{color} [[tests 0 Exit Code , BuildFailureOnMessage
|https://ci.ignite.apache.org/viewLog.html?buildId=2088296]]
{color:#d04437}MVCC Queries{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2067909]]
* IgniteCacheMvccSqlTestSuite:
CacheMvccPartitionedSqlCoordinatorFailoverTest.testReadInProgressCoordinatorFailsSimple_FromClient
- 0,0% fails in last 100 master runs.
{color:#d04437}SPI{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=2067844]]
* IgniteSpiTestSuite: TcpDiscoverySslSelfTest.testFailedNodes3 - 3,1% fails in
last 100 master runs.
{color:#d04437}Platform .NET (Long Running){color} [[tests
5|https://ci.ignite.apache.org/viewLog.html?buildId=2067859]]
* exe: CacheQueriesTest.TestSqlFieldsQueryTimeout - 0,0% fails in last 100
master runs.
* exe: CacheQueriesTest.TestSqlQueryTimeout - 0,0% fails in last 100 master
runs.
* exe: CacheQueriesTest.TestSqlFieldsQueryTimeout - 0,0% fails in last 100
master runs.
* exe: CacheQueriesTest.TestSqlQueryTimeout - 0,0% fails in last 100 master
runs.
{color:#d04437}Platform .NET (Core Linux){color} [[tests
9|https://ci.ignite.apache.org/viewLog.html?buildId=2067858]]
* dll: CacheQueriesTest.TestSqlFieldsQueryTimeout - 0,0% fails in last 100
master runs.
* dll: CacheQueriesTest.TestSqlQueryTimeout - 0,0% fails in last 100 master
runs.
* dll: CacheQueriesTestSimpleName.TestSqlFieldsQueryTimeout - 0,0% fails in
last 100 master runs.
* dll: CacheQueriesTestSimpleName.TestSqlQueryTimeout - 0,0% fails in last 100
master runs.
{color:#d04437}Streamers{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2067842]]
* IgniteKafkaStreamerSelfTestSuite:
IgniteSinkConnectorTest.testSinkPutsWithoutTransformation - 3,3% fails in last
100 master runs.
{color:#d04437}Binary Objects{color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=2067808]]
* IgniteBinaryObjectsTestSuite:
BinaryMetadataUpdatesFlowTest.testFlowNoConflictsWithClients - 3,2% fails in
last 100 master runs.
* IgniteBinaryObjectsTestSuite:
GridCacheClientNodeBinaryObjectMetadataMultinodeTest.testClientMetadataInitialization
- 3,2% fails in last 100 master runs.
* IgniteBinaryObjectsTestSuite:
GridCacheClientNodeBinaryObjectMetadataMultinodeTest.testClientStartsFirst -
3,2% fails in last 100 master runs.
{color:#d04437}Cache 8{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2067900]]
* IgniteCacheTestSuite8:
GridCacheRebalancingAsyncSelfTest.testSimpleRebalancing - 0,0% fails in last
100 master runs.
{color:#d04437}Cache (Full API Config Variations / Basic){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2067898]]
* IgniteCacheBasicConfigVariationsFullApiTestSuite:
IgniteCacheConfigVariationsFullApiTest.testTtlNoTxOldEntry - 0,0% fails in last
100 master runs.
{panel}
[TeamCity Run
All|http://ci.ignite.apache.org/viewLog.html?buildId=2067910buildTypeId=IgniteTests24Java8_RunAll])
> FindBugs: Methods may fail to close stream in core module
> -
>
> Key: IGNITE-9165
> URL: https://issues.apache.org/jira/browse/IGNITE-9165
> Project: Ignite
> Issue Type: Bug
> Components: binary
>Affects Versions: 2.6
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
> Labels: newbie
> Fix For: 2.8
>
> Attachments:
> findbugs-result-apache-ignite[ignite-core]_2018_08_02_12_38_02.html
>
>
> The method creates an IO stream object, does not assign it to any fields,
> pass it to other methods that might close it, or return it, and does not
> appear to close the stream on all paths out of the method. This may result
> in a file descriptor leak.
> Example:
>
> {code:java}
> // GridCacheAbstractLoadTest#GridCacheAbstractLoadTest()
> try {
> props.load(new FileReader(GridTestUtils.resolveIgnitePath(
> "modules/tests/config/cache-load.properties")));
> }
> catch (IOException e) {
> throw new RuntimeException(e);
> }{code}
>
> One of possible solutions:
> {code:java}
> try (Reader reader = new FileReader(GridTestUtils.resolveIgnitePath(
> "modules/tests/config/cache-load.properties"))) {
> props.load(reader);
> }
> catch (IOException e) {
> throw new RuntimeException(e);
>
[jira] [Commented] (IGNITE-9430) Add ability to override all caches's "rebalanceThrottle" option via JVM node option
[ https://issues.apache.org/jira/browse/IGNITE-9430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16651925#comment-16651925 ] ASF GitHub Bot commented on IGNITE-9430: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4944 > Add ability to override all caches's "rebalanceThrottle" option via JVM node > option > > > Key: IGNITE-9430 > URL: https://issues.apache.org/jira/browse/IGNITE-9430 > Project: Ignite > Issue Type: Improvement > Components: general >Affects Versions: 2.5 >Reporter: ARomantsov >Assignee: Sergey Kosarev >Priority: Major > Fix For: 2.8 > > > I found ability to set rebalanceThrottle option for any cache , but can we > have JVM key for override that parameter for all caches at once -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9165) FindBugs: Methods may fail to close stream in core module
[
https://issues.apache.org/jira/browse/IGNITE-9165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16651924#comment-16651924
]
PetrovMikhail commented on IGNITE-9165:
---
{panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Hadoop{color} [[tests 0 TIMEOUT , Out Of Memory Error , Exit
Code , [Artifacts publishing failed]
|https://ci.ignite.apache.org/viewLog.html?buildId=2088269]]
* HadoopMapReduceErrorResilienceTest.testRecoveryAfterAnError0_Error (last
started)
{color:#d04437}_Javadoc_{color} [[tests 0 Exit Code , BuildFailureOnMessage
|https://ci.ignite.apache.org/viewLog.html?buildId=2088296]]
{color:#d04437}MVCC Queries{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2067909]]
* IgniteCacheMvccSqlTestSuite:
CacheMvccPartitionedSqlCoordinatorFailoverTest.testReadInProgressCoordinatorFailsSimple_FromClient
- 0,0% fails in last 100 master runs.
{color:#d04437}SPI{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=2067844]]
* IgniteSpiTestSuite: TcpDiscoverySslSelfTest.testFailedNodes3 - 3,1% fails in
last 100 master runs.
{color:#d04437}Platform .NET (Long Running){color} [[tests
5|https://ci.ignite.apache.org/viewLog.html?buildId=2067859]]
* exe: CacheQueriesTest.TestSqlFieldsQueryTimeout - 0,0% fails in last 100
master runs.
* exe: CacheQueriesTest.TestSqlQueryTimeout - 0,0% fails in last 100 master
runs.
* exe: CacheQueriesTest.TestSqlFieldsQueryTimeout - 0,0% fails in last 100
master runs.
* exe: CacheQueriesTest.TestSqlQueryTimeout - 0,0% fails in last 100 master
runs.
{color:#d04437}Platform .NET (Core Linux){color} [[tests
9|https://ci.ignite.apache.org/viewLog.html?buildId=2067858]]
* dll: CacheQueriesTest.TestSqlFieldsQueryTimeout - 0,0% fails in last 100
master runs.
* dll: CacheQueriesTest.TestSqlQueryTimeout - 0,0% fails in last 100 master
runs.
* dll: CacheQueriesTestSimpleName.TestSqlFieldsQueryTimeout - 0,0% fails in
last 100 master runs.
* dll: CacheQueriesTestSimpleName.TestSqlQueryTimeout - 0,0% fails in last 100
master runs.
{color:#d04437}Streamers{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2067842]]
* IgniteKafkaStreamerSelfTestSuite:
IgniteSinkConnectorTest.testSinkPutsWithoutTransformation - 3,3% fails in last
100 master runs.
{color:#d04437}Binary Objects{color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=2067808]]
* IgniteBinaryObjectsTestSuite:
BinaryMetadataUpdatesFlowTest.testFlowNoConflictsWithClients - 3,2% fails in
last 100 master runs.
* IgniteBinaryObjectsTestSuite:
GridCacheClientNodeBinaryObjectMetadataMultinodeTest.testClientMetadataInitialization
- 3,2% fails in last 100 master runs.
* IgniteBinaryObjectsTestSuite:
GridCacheClientNodeBinaryObjectMetadataMultinodeTest.testClientStartsFirst -
3,2% fails in last 100 master runs.
{color:#d04437}Cache 8{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2067900]]
* IgniteCacheTestSuite8:
GridCacheRebalancingAsyncSelfTest.testSimpleRebalancing - 0,0% fails in last
100 master runs.
{color:#d04437}Cache (Full API Config Variations / Basic){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2067898]]
* IgniteCacheBasicConfigVariationsFullApiTestSuite:
IgniteCacheConfigVariationsFullApiTest.testTtlNoTxOldEntry - 0,0% fails in last
100 master runs.
{panel}
[TeamCity Run
All|http://ci.ignite.apache.org/viewLog.html?buildId=2067910buildTypeId=IgniteTests24Java8_RunAll]
> FindBugs: Methods may fail to close stream in core module
> -
>
> Key: IGNITE-9165
> URL: https://issues.apache.org/jira/browse/IGNITE-9165
> Project: Ignite
> Issue Type: Bug
> Components: binary
>Affects Versions: 2.6
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
> Labels: newbie
> Fix For: 2.8
>
> Attachments:
> findbugs-result-apache-ignite[ignite-core]_2018_08_02_12_38_02.html
>
>
> The method creates an IO stream object, does not assign it to any fields,
> pass it to other methods that might close it, or return it, and does not
> appear to close the stream on all paths out of the method. This may result
> in a file descriptor leak.
> Example:
>
> {code:java}
> // GridCacheAbstractLoadTest#GridCacheAbstractLoadTest()
> try {
> props.load(new FileReader(GridTestUtils.resolveIgnitePath(
> "modules/tests/config/cache-load.properties")));
> }
> catch (IOException e) {
> throw new RuntimeException(e);
> }{code}
>
> One of possible solutions:
> {code:java}
> try (Reader reader = new FileReader(GridTestUtils.resolveIgnitePath(
> "modules/tests/config/cache-load.properties"))) {
> props.load(reader);
> }
> catch (IOException e) {
> throw new
[jira] [Updated] (IGNITE-9856) Update documentation for control.sh --cache list
[
https://issues.apache.org/jira/browse/IGNITE-9856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Antonov updated IGNITE-9856:
---
Description:
{{Documentation for option --cache list in control.sh}} must be updated.
As reference could be used help message:
{noformat}
--cache subcommand allows to do the following operations:
Show information about caches, groups or sequences that match a regex:
control.sh [--host HOST_OR_IP] [--port PORT] [--user USER] [--password
PASSWORD] [--ping-interval PING_INTERVAL] [--ping-timeout PING_TIMEOUT] --cache
list regexPattern [groups|seq] [nodeId] [--output-format multi-line]
If [nodeId] is not specified, list with no defined [groups|seq], contention and
validate_indexes commands will be broadcasted to all server nodes.
{noformat}
And output example:
{noformat}
Control utility [ver. 2.7.0-SNAPSHOT#19700101-sha1:DEV]
2018 Copyright(C) Apache Software Foundation
User: santonov
ignite-sys-cache: {Name=ignite-sys-cache, Group=null, Dynamic Deployment
ID=fb381836661-93ea1b62-7e2c-449d-82f4-ede849a03e22, System=true,
Mode=REPLICATED, Atomicity Mode=TRANSACTIONAL, Statistic Enabled=false,
Management Enabled=false, On-heap cache enabled=false, Partition Loss
Policy=IGNORE, Query Parallelism=1, Copy On Read=false, Listener
Configurations=null, Load Previous Value=false, Memory Policy Name=sysMemPlc,
Node Filter=o.a.i.configuration.CacheConfiguration$IgniteAllNodesPredicate,
Read From Backup=true, Topology Validator=null, Time To Live Eager Flag=true,
Write Synchronization Mode=FULL_SYNC, Invalidate=false, Affinity
Function=o.a.i.cache.affinity.rendezvous.RendezvousAffinityFunction, Affinity
Backups=2147483647, Affinity Partitions=100, Affinity Exclude Neighbors=false,
Affinity Mapper=o.a.i.i.processors.cache.GridCacheDefaultAffinityKeyMapper,
Rebalance Mode=SYNC, Rebalance Batch Size=524288, Rebalance Timeout=1,
Rebalance Delay=0, Time Between Rebalance Messages=0, Rebalance Batches
Count=2, Rebalance Cache Order=-2, Eviction Policy Enabled=false, Eviction
Policy Factory=null, Eviction Policy Max Size=null, Eviction Filter=null, Near
Cache Enabled=false, Near Start Size=0, Near Eviction Policy Factory=null, Near
Eviction Policy Max Size=null, Default Lock Timeout=0, Query Entities=[], Cache
Interceptor=null, Store Enabled=false, Store Class=null, Store Factory
Class=null, Store Keep Binary=false, Store Read Through=false, Store Write
Through=false, Store Write Coalescing=true, Write-Behind Enabled=false,
Write-Behind Flush Size=10240, Write-Behind Frequency=5000, Write-Behind Flush
Threads Count=1, Write-Behind Batch Size=512, Concurrent Asynchronous
Operations Number=500, Loader Factory Class Name=null, Writer Factory Class
Name=null, Expiry Policy Factory Class
Name=javax.cache.configuration.FactoryBuilder$SingletonFactory, Query Execution
Time Threshold=3000, Query Escaped Names=false, Query SQL Schema=null, Query
SQL functions=null, Query Indexed Types=null, Maximum payload size for offheap
indexes=-1, Query Metrics History Size=0}
test-default: {Name=test-default, Group=null, Dynamic Deployment
ID=fb381836661-93ea1b62-7e2c-449d-82f4-ede849a03e22, System=false,
Mode=PARTITIONED, Atomicity Mode=ATOMIC, Statistic Enabled=false, Management
Enabled=false, On-heap cache enabled=false, Partition Loss Policy=IGNORE, Query
Parallelism=1, Copy On Read=true, Listener Configurations=null, Load Previous
Value=false, Memory Policy Name=null, Node
Filter=o.a.i.configuration.CacheConfiguration$IgniteAllNodesPredicate, Read
From Backup=true, Topology Validator=null, Time To Live Eager Flag=true, Write
Synchronization Mode=PRIMARY_SYNC, Invalidate=false, Affinity
Function=o.a.i.cache.affinity.rendezvous.RendezvousAffinityFunction, Affinity
Backups=0, Affinity Partitions=1024, Affinity Exclude Neighbors=false, Affinity
Mapper=o.a.i.i.processors.cache.CacheDefaultBinaryAffinityKeyMapper, Rebalance
Mode=ASYNC, Rebalance Batch Size=524288, Rebalance Timeout=1, Rebalance
Delay=0, Time Between Rebalance Messages=0, Rebalance Batches Count=2,
Rebalance Cache Order=0, Eviction Policy Enabled=false, Eviction Policy
Factory=null, Eviction Policy Max Size=null, Eviction Filter=null, Near Cache
Enabled=false, Near Start Size=0, Near Eviction Policy Factory=null, Near
Eviction Policy Max Size=null, Default Lock Timeout=0, Query Entities=[], Cache
Interceptor=null, Store Enabled=false, Store Class=null, Store Factory
Class=null, Store Keep Binary=false, Store Read Through=false, Store Write
Through=false, Store Write Coalescing=true, Write-Behind Enabled=false,
Write-Behind Flush Size=10240, Write-Behind Frequency=5000, Write-Behind Flush
Threads Count=1, Write-Behind Batch Size=512, Concurrent Asynchronous
Operations Number=500, Loader Factory Class Name=null, Writer Factory Class
[jira] [Updated] (IGNITE-9856) Update documentation for control.sh --cache list
[
https://issues.apache.org/jira/browse/IGNITE-9856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Antonov updated IGNITE-9856:
---
Description:
{{Documentation for option --cache list }}in {{control.sh}} must be updated.
As reference could be used help message:
{noformat}
--cache subcommand allows to do the following operations:
Show information about caches, groups or sequences that match a regex:
control.sh [--host HOST_OR_IP] [--port PORT] [--user USER] [--password
PASSWORD] [--ping-interval PING_INTERVAL] [--ping-timeout PING_TIMEOUT] --cache
list regexPattern [groups|seq] [nodeId] [--output-format multi-line]
If [nodeId] is not specified, list with no defined [groups|seq], contention and
validate_indexes commands will be broadcasted to all server nodes.
{noformat}
And output example:
{noformat}
Control utility [ver. 2.7.0-SNAPSHOT#19700101-sha1:DEV]
2018 Copyright(C) Apache Software Foundation
User: santonov
ignite-sys-cache: {Name=ignite-sys-cache, Group=null, Dynamic Deployment
ID=fb381836661-93ea1b62-7e2c-449d-82f4-ede849a03e22, System=true,
Mode=REPLICATED, Atomicity Mode=TRANSACTIONAL, Statistic Enabled=false,
Management Enabled=false, On-heap cache enabled=false, Partition Loss
Policy=IGNORE, Query Parallelism=1, Copy On Read=false, Listener
Configurations=null, Load Previous Value=false, Memory Policy Name=sysMemPlc,
Node Filter=o.a.i.configuration.CacheConfiguration$IgniteAllNodesPredicate,
Read From Backup=true, Topology Validator=null, Time To Live Eager Flag=true,
Write Synchronization Mode=FULL_SYNC, Invalidate=false, Affinity
Function=o.a.i.cache.affinity.rendezvous.RendezvousAffinityFunction, Affinity
Backups=2147483647, Affinity Partitions=100, Affinity Exclude Neighbors=false,
Affinity Mapper=o.a.i.i.processors.cache.GridCacheDefaultAffinityKeyMapper,
Rebalance Mode=SYNC, Rebalance Batch Size=524288, Rebalance Timeout=1,
Rebalance Delay=0, Time Between Rebalance Messages=0, Rebalance Batches
Count=2, Rebalance Cache Order=-2, Eviction Policy Enabled=false, Eviction
Policy Factory=null, Eviction Policy Max Size=null, Eviction Filter=null, Near
Cache Enabled=false, Near Start Size=0, Near Eviction Policy Factory=null, Near
Eviction Policy Max Size=null, Default Lock Timeout=0, Query Entities=[], Cache
Interceptor=null, Store Enabled=false, Store Class=null, Store Factory
Class=null, Store Keep Binary=false, Store Read Through=false, Store Write
Through=false, Store Write Coalescing=true, Write-Behind Enabled=false,
Write-Behind Flush Size=10240, Write-Behind Frequency=5000, Write-Behind Flush
Threads Count=1, Write-Behind Batch Size=512, Concurrent Asynchronous
Operations Number=500, Loader Factory Class Name=null, Writer Factory Class
Name=null, Expiry Policy Factory Class
Name=javax.cache.configuration.FactoryBuilder$SingletonFactory, Query Execution
Time Threshold=3000, Query Escaped Names=false, Query SQL Schema=null, Query
SQL functions=null, Query Indexed Types=null, Maximum payload size for offheap
indexes=-1, Query Metrics History Size=0}
test-default: {Name=test-default, Group=null, Dynamic Deployment
ID=fb381836661-93ea1b62-7e2c-449d-82f4-ede849a03e22, System=false,
Mode=PARTITIONED, Atomicity Mode=ATOMIC, Statistic Enabled=false, Management
Enabled=false, On-heap cache enabled=false, Partition Loss Policy=IGNORE, Query
Parallelism=1, Copy On Read=true, Listener Configurations=null, Load Previous
Value=false, Memory Policy Name=null, Node
Filter=o.a.i.configuration.CacheConfiguration$IgniteAllNodesPredicate, Read
From Backup=true, Topology Validator=null, Time To Live Eager Flag=true, Write
Synchronization Mode=PRIMARY_SYNC, Invalidate=false, Affinity
Function=o.a.i.cache.affinity.rendezvous.RendezvousAffinityFunction, Affinity
Backups=0, Affinity Partitions=1024, Affinity Exclude Neighbors=false, Affinity
Mapper=o.a.i.i.processors.cache.CacheDefaultBinaryAffinityKeyMapper, Rebalance
Mode=ASYNC, Rebalance Batch Size=524288, Rebalance Timeout=1, Rebalance
Delay=0, Time Between Rebalance Messages=0, Rebalance Batches Count=2,
Rebalance Cache Order=0, Eviction Policy Enabled=false, Eviction Policy
Factory=null, Eviction Policy Max Size=null, Eviction Filter=null, Near Cache
Enabled=false, Near Start Size=0, Near Eviction Policy Factory=null, Near
Eviction Policy Max Size=null, Default Lock Timeout=0, Query Entities=[], Cache
Interceptor=null, Store Enabled=false, Store Class=null, Store Factory
Class=null, Store Keep Binary=false, Store Read Through=false, Store Write
Through=false, Store Write Coalescing=true, Write-Behind Enabled=false,
Write-Behind Flush Size=10240, Write-Behind Frequency=5000, Write-Behind Flush
Threads Count=1, Write-Behind Batch Size=512, Concurrent Asynchronous
Operations Number=500, Loader Factory Class Name=null, Writer Factory Class
[jira] [Commented] (IGNITE-9830) o.a.i.i.b.BinaryReaderExImpl#getOrCreateSchema sometimes misses latest metadata version resulting in failed tx commit because of absent schema.
[ https://issues.apache.org/jira/browse/IGNITE-9830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16651853#comment-16651853 ] Alexei Scherbakov commented on IGNITE-9830: --- Root cause of a problem is too early metadata update completion in case of multiple concurrent updates for the same schema. > o.a.i.i.b.BinaryReaderExImpl#getOrCreateSchema sometimes misses latest > metadata version resulting in failed tx commit because of absent schema. > --- > > Key: IGNITE-9830 > URL: https://issues.apache.org/jira/browse/IGNITE-9830 > Project: Ignite > Issue Type: Improvement >Reporter: Alexei Scherbakov >Assignee: Alexei Scherbakov >Priority: Major > Fix For: 2.8 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-9895) DiscoveryMessageNotifierWorker must be an instance of IgniteDiscoveryThread
[
https://issues.apache.org/jira/browse/IGNITE-9895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk resolved IGNITE-9895.
--
Resolution: Fixed
> DiscoveryMessageNotifierWorker must be an instance of IgniteDiscoveryThread
> ---
>
> Key: IGNITE-9895
> URL: https://issues.apache.org/jira/browse/IGNITE-9895
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
>Priority: Critical
> Fix For: 2.7
>
>
> This is a regression from IGNITE-9398. The newly added thread must implement
> the marker interface, otherwise it is possible for a blocking future get
> inside of discovery worker, which leads to a cluster-wide deadlock:
> {code}
> "disco-notyfier-worker-#625%internal.IgniteClientReconnectApiExceptionTest0%"
> #770 prio=5 os_prio=0 tid=0x7f479c263800 nid=0x209b waiting on condition
> [0x7f49287ec000]
>java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:177)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:140)
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.metadata(CacheObjectBinaryProcessorImpl.java:579)
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl$2.metadata(CacheObjectBinaryProcessorImpl.java:197)
> at
> org.apache.ignite.internal.binary.BinaryContext.metadata(BinaryContext.java:1283)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.getOrCreateSchema(BinaryReaderExImpl.java:2007)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:286)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:185)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readField(BinaryReaderExImpl.java:1984)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read0(BinaryFieldAccessor.java:698)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor.read(BinaryFieldAccessor.java:183)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:870)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1764)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1716)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readField(BinaryReaderExImpl.java:1984)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read0(BinaryFieldAccessor.java:698)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor.read(BinaryFieldAccessor.java:183)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:870)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1764)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1716)
> at
> org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:310)
> at
> org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal0(BinaryMarshaller.java:99)
> at
> org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:82)
> at
> org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10014)
> at
> org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10043)
> at
> org.apache.ignite.internal.GridMessageListenHandler.p2pUnmarshal(GridMessageListenHandler.java:194)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processStartRequest(GridContinuousProcessor.java:1331)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$400(GridContinuousProcessor.java:108)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:200)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:191)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:721)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.lambda$onDiscovery$0(GridDiscoveryManager.java:600)
> - locked <0x0007860b5c70> (a java.lang.Object)
> at
[jira] [Commented] (IGNITE-9895) DiscoveryMessageNotifierWorker must be an instance of IgniteDiscoveryThread
[
https://issues.apache.org/jira/browse/IGNITE-9895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16651848#comment-16651848
]
ASF GitHub Bot commented on IGNITE-9895:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5000
> DiscoveryMessageNotifierWorker must be an instance of IgniteDiscoveryThread
> ---
>
> Key: IGNITE-9895
> URL: https://issues.apache.org/jira/browse/IGNITE-9895
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
>Priority: Critical
> Fix For: 2.7
>
>
> This is a regression from IGNITE-9398. The newly added thread must implement
> the marker interface, otherwise it is possible for a blocking future get
> inside of discovery worker, which leads to a cluster-wide deadlock:
> {code}
> "disco-notyfier-worker-#625%internal.IgniteClientReconnectApiExceptionTest0%"
> #770 prio=5 os_prio=0 tid=0x7f479c263800 nid=0x209b waiting on condition
> [0x7f49287ec000]
>java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:177)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:140)
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.metadata(CacheObjectBinaryProcessorImpl.java:579)
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl$2.metadata(CacheObjectBinaryProcessorImpl.java:197)
> at
> org.apache.ignite.internal.binary.BinaryContext.metadata(BinaryContext.java:1283)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.getOrCreateSchema(BinaryReaderExImpl.java:2007)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:286)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:185)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readField(BinaryReaderExImpl.java:1984)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read0(BinaryFieldAccessor.java:698)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor.read(BinaryFieldAccessor.java:183)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:870)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1764)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1716)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readField(BinaryReaderExImpl.java:1984)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read0(BinaryFieldAccessor.java:698)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor.read(BinaryFieldAccessor.java:183)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:870)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1764)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1716)
> at
> org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:310)
> at
> org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal0(BinaryMarshaller.java:99)
> at
> org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:82)
> at
> org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10014)
> at
> org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10043)
> at
> org.apache.ignite.internal.GridMessageListenHandler.p2pUnmarshal(GridMessageListenHandler.java:194)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processStartRequest(GridContinuousProcessor.java:1331)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$400(GridContinuousProcessor.java:108)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:200)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:191)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:721)
> at
>
[jira] [Commented] (IGNITE-9557) Assert exception on explain of DELETE query.
[
https://issues.apache.org/jira/browse/IGNITE-9557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16651843#comment-16651843
]
Pavel Kuznetsov commented on IGNITE-9557:
-
Thank you!
Also moved test to another package and added to IgniteCacheQuerySelfTestSuite2
Test run : https://ci.ignite.apache.org/viewQueued.html?itemId=2098497
> Assert exception on explain of DELETE query.
>
>
> Key: IGNITE-9557
> URL: https://issues.apache.org/jira/browse/IGNITE-9557
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Vasiliy Sisko
>Assignee: Pavel Kuznetsov
>Priority: Major
>
> On execution of an query:
> {code:java}
> explain delete from "schema".type {code}
> received exception:
> {code:java}
> java.lang.AssertionError
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.parseAndSplit(IgniteH2Indexing.java:2309)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.querySqlFields(IgniteH2Indexing.java:2105)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2139)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2134)
> at
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2711)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2148)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2083)
> at
> org.apache.ignite.internal.visor.query.VisorQueryTask$VisorQueryJob.run(VisorQueryTask.java:94)
> at
> org.apache.ignite.internal.visor.query.VisorQueryTask$VisorQueryJob.run(VisorQueryTask.java:59)
> at org.apache.ignite.internal.visor.VisorJob.execute(VisorJob.java:69)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:568)
> at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6765)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:562)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:491)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at
> org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1125)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.sendRequest(GridTaskWorker.java:1420)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.processMappedJobs(GridTaskWorker.java:666)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.body(GridTaskWorker.java:538)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at
> org.apache.ignite.internal.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:764)
> at
> org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:509)
> at
> org.apache.ignite.internal.IgniteComputeImpl.executeAsync0(IgniteComputeImpl.java:488)
> at
> org.apache.ignite.internal.IgniteComputeImpl.executeAsync(IgniteComputeImpl.java:468)
> at
> org.apache.ignite.internal.visor.compute.VisorGatewayTask$VisorGatewayJob.execute(VisorGatewayTask.java:462)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:568)
> at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6765)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:562)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:491)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at
> org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1125)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.sendRequest(GridTaskWorker.java:1420)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.processMappedJobs(GridTaskWorker.java:666)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.body(GridTaskWorker.java:538)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at
> org.apache.ignite.internal.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:764)
> at
> org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:509)
> at
>
[jira] [Commented] (IGNITE-9891) ODBC: SQLTables does not work with list of table types
[
https://issues.apache.org/jira/browse/IGNITE-9891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16651826#comment-16651826
]
ASF GitHub Bot commented on IGNITE-9891:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4995
> ODBC: SQLTables does not work with list of table types
> --
>
> Key: IGNITE-9891
> URL: https://issues.apache.org/jira/browse/IGNITE-9891
> Project: Ignite
> Issue Type: Bug
> Components: odbc
>Affects Versions: 2.6
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>Priority: Major
> Labels: odbc
> Fix For: 2.7
>
>
> {{SQLTables}} do not work with list of table types as stated in
> https://docs.microsoft.com/en-us/sql/odbc/reference/syntax/sqltables-function?view=sql-server-2017
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9895) DiscoveryMessageNotifierWorker must be an instance of IgniteDiscoveryThread
[
https://issues.apache.org/jira/browse/IGNITE-9895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16651823#comment-16651823
]
Alexey Goncharuk commented on IGNITE-9895:
--
Javadoc failure is related to the changes in the suite that will be soon
reverted. Hadoop suite is failing in master with the same issue as well.
> DiscoveryMessageNotifierWorker must be an instance of IgniteDiscoveryThread
> ---
>
> Key: IGNITE-9895
> URL: https://issues.apache.org/jira/browse/IGNITE-9895
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
>Priority: Critical
> Fix For: 2.7
>
>
> This is a regression from IGNITE-9398. The newly added thread must implement
> the marker interface, otherwise it is possible for a blocking future get
> inside of discovery worker, which leads to a cluster-wide deadlock:
> {code}
> "disco-notyfier-worker-#625%internal.IgniteClientReconnectApiExceptionTest0%"
> #770 prio=5 os_prio=0 tid=0x7f479c263800 nid=0x209b waiting on condition
> [0x7f49287ec000]
>java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:177)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:140)
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.metadata(CacheObjectBinaryProcessorImpl.java:579)
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl$2.metadata(CacheObjectBinaryProcessorImpl.java:197)
> at
> org.apache.ignite.internal.binary.BinaryContext.metadata(BinaryContext.java:1283)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.getOrCreateSchema(BinaryReaderExImpl.java:2007)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:286)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:185)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readField(BinaryReaderExImpl.java:1984)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read0(BinaryFieldAccessor.java:698)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor.read(BinaryFieldAccessor.java:183)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:870)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1764)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1716)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readField(BinaryReaderExImpl.java:1984)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read0(BinaryFieldAccessor.java:698)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor.read(BinaryFieldAccessor.java:183)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:870)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1764)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1716)
> at
> org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:310)
> at
> org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal0(BinaryMarshaller.java:99)
> at
> org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:82)
> at
> org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10014)
> at
> org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10043)
> at
> org.apache.ignite.internal.GridMessageListenHandler.p2pUnmarshal(GridMessageListenHandler.java:194)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processStartRequest(GridContinuousProcessor.java:1331)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$400(GridContinuousProcessor.java:108)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:200)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:191)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:721)
> at
>
[jira] [Commented] (IGNITE-9895) DiscoveryMessageNotifierWorker must be an instance of IgniteDiscoveryThread
[
https://issues.apache.org/jira/browse/IGNITE-9895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16651821#comment-16651821
]
Ignite TC Bot commented on IGNITE-9895:
---
{panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Hadoop{color} [[tests 0 TIMEOUT , Out Of Memory Error , Exit
Code , [Artifacts publishing failed]
|https://ci.ignite.apache.org/viewLog.html?buildId=2097892]]
* HadoopMapReduceErrorResilienceTest.testRecoveryAfterAnError0_Error (last
started)
{color:#d04437}_Javadoc_{color} [[tests 0 Exit Code , BuildFailureOnMessage
|https://ci.ignite.apache.org/viewLog.html?buildId=2096204]]
{panel}
[TeamCity Run
All|http://ci.ignite.apache.org/viewLog.html?buildId=2096238buildTypeId=IgniteTests24Java8_RunAll]
> DiscoveryMessageNotifierWorker must be an instance of IgniteDiscoveryThread
> ---
>
> Key: IGNITE-9895
> URL: https://issues.apache.org/jira/browse/IGNITE-9895
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
>Priority: Critical
> Fix For: 2.7
>
>
> This is a regression from IGNITE-9398. The newly added thread must implement
> the marker interface, otherwise it is possible for a blocking future get
> inside of discovery worker, which leads to a cluster-wide deadlock:
> {code}
> "disco-notyfier-worker-#625%internal.IgniteClientReconnectApiExceptionTest0%"
> #770 prio=5 os_prio=0 tid=0x7f479c263800 nid=0x209b waiting on condition
> [0x7f49287ec000]
>java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:177)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:140)
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.metadata(CacheObjectBinaryProcessorImpl.java:579)
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl$2.metadata(CacheObjectBinaryProcessorImpl.java:197)
> at
> org.apache.ignite.internal.binary.BinaryContext.metadata(BinaryContext.java:1283)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.getOrCreateSchema(BinaryReaderExImpl.java:2007)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:286)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:185)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readField(BinaryReaderExImpl.java:1984)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read0(BinaryFieldAccessor.java:698)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor.read(BinaryFieldAccessor.java:183)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:870)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1764)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1716)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readField(BinaryReaderExImpl.java:1984)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read0(BinaryFieldAccessor.java:698)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor.read(BinaryFieldAccessor.java:183)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:870)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1764)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1716)
> at
> org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:310)
> at
> org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal0(BinaryMarshaller.java:99)
> at
> org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:82)
> at
> org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10014)
> at
> org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10043)
> at
> org.apache.ignite.internal.GridMessageListenHandler.p2pUnmarshal(GridMessageListenHandler.java:194)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processStartRequest(GridContinuousProcessor.java:1331)
> at
>
[jira] [Updated] (IGNITE-9659) NonCollocatedRetryMessageSelfTest is flaky
[ https://issues.apache.org/jira/browse/IGNITE-9659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-9659: Fix Version/s: 2.8 > NonCollocatedRetryMessageSelfTest is flaky > -- > > Key: IGNITE-9659 > URL: https://issues.apache.org/jira/browse/IGNITE-9659 > Project: Ignite > Issue Type: Test >Reporter: Alexey Goncharuk >Assignee: Amelchev Nikita >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.8 > > > https://ci.ignite.apache.org/viewLog.html?buildId=1881869=buildResultsDiv=IgniteTests24Java8_Queries2#testNameId-2853122976880171731 > A few concerns on the test code: > 1) What is the point of setting an anonymous discovery SPI? The overridden > method is identical to super(), but the new discovery SPI looses test VM IP > finder which is set by default > 2) Looks like there is a race in test communication SPI code - there is an if > - assign block for a volatile variable > 3) The test fails with "Node left during query execution" - since the node is > stopped, this should be either an allowed exception, or the test > communication SPI should be crafted more carefully. > (FYI: Locally I have this test failing with No CacheException emitted. > Collection size=10) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9659) NonCollocatedRetryMessageSelfTest is flaky
[ https://issues.apache.org/jira/browse/IGNITE-9659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16651816#comment-16651816 ] ASF GitHub Bot commented on IGNITE-9659: GitHub user NSAmelchev opened a pull request: https://github.com/apache/ignite/pull/5005 IGNITE-9659 Fix the _NonCollocatedRetryMessageSelfTest.testNonCollocatedRetryMessage_ test. You can merge this pull request into a Git repository by running: $ git pull https://github.com/NSAmelchev/ignite ignite-9659 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5005.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5005 commit dc5a776ea3d1634533bcae3f09931d0beb23cfab Author: NSAmelchev Date: 2018-10-16T13:54:06Z Fix the testNonCollocatedRetryMessage test. commit dfa7d661d14899d3a31f71fd70c589bc9d254272 Author: NSAmelchev Date: 2018-10-16T14:34:16Z Code style fix. > NonCollocatedRetryMessageSelfTest is flaky > -- > > Key: IGNITE-9659 > URL: https://issues.apache.org/jira/browse/IGNITE-9659 > Project: Ignite > Issue Type: Test >Reporter: Alexey Goncharuk >Assignee: Amelchev Nikita >Priority: Major > Labels: MakeTeamcityGreenAgain > > https://ci.ignite.apache.org/viewLog.html?buildId=1881869=buildResultsDiv=IgniteTests24Java8_Queries2#testNameId-2853122976880171731 > A few concerns on the test code: > 1) What is the point of setting an anonymous discovery SPI? The overridden > method is identical to super(), but the new discovery SPI looses test VM IP > finder which is set by default > 2) Looks like there is a race in test communication SPI code - there is an if > - assign block for a volatile variable > 3) The test fails with "Node left during query execution" - since the node is > stopped, this should be either an allowed exception, or the test > communication SPI should be crafted more carefully. > (FYI: Locally I have this test failing with No CacheException emitted. > Collection size=10) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9902) ScanQuery doesn't take lost partitions into account
[ https://issues.apache.org/jira/browse/IGNITE-9902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16651803#comment-16651803 ] Stanislav Lukyanov commented on IGNITE-9902: Actually, no, it's not even like IGNITE-9841 - scan queries currently just ignore lost partitions. > ScanQuery doesn't take lost partitions into account > --- > > Key: IGNITE-9902 > URL: https://issues.apache.org/jira/browse/IGNITE-9902 > Project: Ignite > Issue Type: Bug >Reporter: Stanislav Lukyanov >Priority: Major > > Same as IGNITE-9841, but about scan queries. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9902) ScanQuery doesn't take lost partitions into account
[ https://issues.apache.org/jira/browse/IGNITE-9902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stanislav Lukyanov updated IGNITE-9902: --- Summary: ScanQuery doesn't take lost partitions into account (was: ScanQuery doesn't take lost partitions into account when persistence is enabled) > ScanQuery doesn't take lost partitions into account > --- > > Key: IGNITE-9902 > URL: https://issues.apache.org/jira/browse/IGNITE-9902 > Project: Ignite > Issue Type: Bug >Reporter: Stanislav Lukyanov >Priority: Major > > Same as IGNITE-9841, but about scan queries. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9738) Client node can suddenly fail on start
[
https://issues.apache.org/jira/browse/IGNITE-9738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16651796#comment-16651796
]
Ignite TC Bot commented on IGNITE-9738:
---
{panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}_Javadoc_{color} [[tests 0 Exit Code , BuildFailureOnMessage
|https://ci.ignite.apache.org/viewLog.html?buildId=2066820]]
{color:#d04437}PDS (Indexing){color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2066812]]
* WalRolloverRecordLoggingFsyncTest.testAvoidInfinityWaitingOnRolloverOfSegment
(last started)
{color:#d04437}ZooKeeper (Discovery) 2{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2066796]]
* GridCacheReplicatedNodeRestartSelfTest.testRestartWithTxSixNodesTwoBackups
(last started)
{color:#d04437}_Licenses Headers_{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2066821]]
{color:#d04437}Cache 2{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=2066832]]
* IgniteCacheTestSuite2:
CacheTxLoadingConcurrentGridStartSelfTestAllowOverwrite.testLoadCacheWithDataStreamerSequentialClientWithConfig
- 1,0% fails in last 100 master runs.
{color:#d04437}Cache 3{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2066833]]
* IgniteBinaryObjectsCacheTestSuite3:
IgniteCacheGroupsTest.testNoKeyIntersectTx - 1,0% fails in last 100 master runs.
{panel}
[TeamCity Run
All|http://ci.ignite.apache.org/viewLog.html?buildId=2066854buildTypeId=IgniteTests24Java8_RunAll]
> Client node can suddenly fail on start
> --
>
> Key: IGNITE-9738
> URL: https://issues.apache.org/jira/browse/IGNITE-9738
> Project: Ignite
> Issue Type: Bug
>Reporter: Vladislav Pyatkov
>Assignee: Vladislav Pyatkov
>Priority: Major
>
> If client joining to large topology it can to spend some time on waiting
> {{TcpDiscoveryNodeAddFinishedMessage}}, but in that time it can not to send
> {{TcpDiscoveryClientMetricsUpdateMessage.}} By that reason server can to
> reset client from topology.
> {noformat}
> Client node considered as unreachable and will be dropped from cluster,
> because no metrics update messages received in interval:
> TcpDiscoverySpi.clientFailureDetectionTimeout() ms. It may be caused by
> network problems or long GC pause on client node, try to increase this
> parameter. [nodeId=a3493895-7c13-403c-bf0d-94eab011,
> clientFailureDetectionTimeout=3];
> {noformat}
> We should to sent {{TcpDiscoveryClientMetricsUpdateMessage as soon as
> possible}} without, waiting finish of join procedure.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9830) o.a.i.i.b.BinaryReaderExImpl#getOrCreateSchema sometimes misses latest metadata version resulting in failed tx commit because of absent schema.
[ https://issues.apache.org/jira/browse/IGNITE-9830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-9830: - Ignite Flags: (was: Docs Required) > o.a.i.i.b.BinaryReaderExImpl#getOrCreateSchema sometimes misses latest > metadata version resulting in failed tx commit because of absent schema. > --- > > Key: IGNITE-9830 > URL: https://issues.apache.org/jira/browse/IGNITE-9830 > Project: Ignite > Issue Type: Improvement >Reporter: Alexei Scherbakov >Assignee: Alexei Scherbakov >Priority: Major > Fix For: 2.8 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-4111) Communication fails to send message if target node did not finish join process
[ https://issues.apache.org/jira/browse/IGNITE-4111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16651756#comment-16651756 ] Nikolay Izhikov commented on IGNITE-4111: - LGTM > Communication fails to send message if target node did not finish join process > -- > > Key: IGNITE-4111 > URL: https://issues.apache.org/jira/browse/IGNITE-4111 > Project: Ignite > Issue Type: Bug > Components: general >Reporter: Semen Boikov >Assignee: Amelchev Nikita >Priority: Minor > Fix For: 2.8 > > Attachments: test onFirstMessage hang.log > > > Currently this scenario is possible: > - joining node sent join request and waits for > TcpDiscoveryNodeAddFinishedMessage inside ServerImpl.joinTopology > - others nodes already see this node and can send messages to it (for example > try to run compute job on this node) > - joining node can not receive message: TcpCommunicationSpi will hang inside > 'onFirstMessage' on 'getSpiContext' call, so sending node will get error > trying to establish connection > Possible fix: if in onFirstMessage() spi context is not available, then > TcpCommunicationSpi should send special response which indicates that this > node is not ready yet, and sender should retry after some time. > Also need check internal code for places where message can be unnecessarily > sent to node: one such place is > GridCachePartitionExchangeManager.refreshPartitions - message is sent to all > known nodes, but here we can filter by node order / finished exchage version. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9872) [Test falied] IgniteSinkConnectorTest.testSinkPutsWithoutTransformation
[
https://issues.apache.org/jira/browse/IGNITE-9872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-9872:
-
Ignite Flags: (was: Docs Required)
> [Test falied] IgniteSinkConnectorTest.testSinkPutsWithoutTransformation
> ---
>
> Key: IGNITE-9872
> URL: https://issues.apache.org/jira/browse/IGNITE-9872
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Maxim Pudov
>Assignee: Maxim Pudov
>Priority: Major
> Fix For: 2.8
>
>
> Test started failing after updating kafka
> https://issues.apache.org/jira/browse/IGNITE-9126
> There is an issue with classloading in kafka
> https://issues.apache.org/jira/browse/KAFKA-6914, which was fixed but wasn't
> included to any public releases yet.
> It can be fixed in our test by replacing system class loader in
> org.apache.ignite.stream.kafka.connect.IgniteSinkConnectorTest#beforeTest:
> Field scl = ClassLoader.class.getDeclaredField("scl"); // Get system class
> loader
> scl.setAccessible(true); // Set accessible
> scl.set(null, getClass().getClassLoader());
> However, it might be better to wait for kafka 1.1.2 and just update its
> version.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9738) Client node can suddenly fail on start
[
https://issues.apache.org/jira/browse/IGNITE-9738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16651729#comment-16651729
]
Ivan Daschinskiy commented on IGNITE-9738:
--
[~v.pyatkov] generally, it looks good for me, but there are some strange
failures in TC. Could you please rerun failed suites again?
> Client node can suddenly fail on start
> --
>
> Key: IGNITE-9738
> URL: https://issues.apache.org/jira/browse/IGNITE-9738
> Project: Ignite
> Issue Type: Bug
>Reporter: Vladislav Pyatkov
>Assignee: Vladislav Pyatkov
>Priority: Major
>
> If client joining to large topology it can to spend some time on waiting
> {{TcpDiscoveryNodeAddFinishedMessage}}, but in that time it can not to send
> {{TcpDiscoveryClientMetricsUpdateMessage.}} By that reason server can to
> reset client from topology.
> {noformat}
> Client node considered as unreachable and will be dropped from cluster,
> because no metrics update messages received in interval:
> TcpDiscoverySpi.clientFailureDetectionTimeout() ms. It may be caused by
> network problems or long GC pause on client node, try to increase this
> parameter. [nodeId=a3493895-7c13-403c-bf0d-94eab011,
> clientFailureDetectionTimeout=3];
> {noformat}
> We should to sent {{TcpDiscoveryClientMetricsUpdateMessage as soon as
> possible}} without, waiting finish of join procedure.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9272) PureJavaCrc32 vs j.u.zip.CRC32 benchmark and probably replace.
[
https://issues.apache.org/jira/browse/IGNITE-9272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16651704#comment-16651704
]
Nikolay Izhikov commented on IGNITE-9272:
-
Latest Run All - https://ci.ignite.apache.org/viewQueued.html?itemId=2098115
> PureJavaCrc32 vs j.u.zip.CRC32 benchmark and probably replace.
> --
>
> Key: IGNITE-9272
> URL: https://issues.apache.org/jira/browse/IGNITE-9272
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Affects Versions: 2.6
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
> Fix For: 2.8
>
> Attachments: BenchmarkCRC.java
>
>
> I see that Ignite has its own crc32 realization called: PureJavaCrc32 and
> from desc it seems to be : _The current version is ~10x to 1.8x as fast as
> Sun's native java.util.zip.CRC32 in Java 1.6_ But my jmh tests show opposite
> results.
> + If it really so, looks like backward compatibility would be easy, all that
> need is just to take lower part of long form zip.crc32 realization.
> {noformat}
> jmh results (less - better):
> Benchmark Mode CntScoreError Units
> BenchmarkCRC.crc32 avgt5 1521060.716 ± 44083.424 ns/op
> BenchmarkCRC.pureJavaCrc32 avgt5 4657756.671 ± 177243.254 ns/op
> {noformat}
> JMH version: 1.21
> VM version: JDK 1.8.0_131, Java HotSpot(TM) 64-Bit Server VM, 25.131-b11
> VM invoker: /usr/lib/jvm/java-8-oracle/jre/bin/java
> op system : ubuntu 16.10
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8570) Create lighter version of GridStringLogger
[
https://issues.apache.org/jira/browse/IGNITE-8570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16651703#comment-16651703
]
Ivan Bessonov commented on IGNITE-8570:
---
Hi [~xtern],
I added a few comments in upsource, please take a look at them. Thank you!
> Create lighter version of GridStringLogger
> --
>
> Key: IGNITE-8570
> URL: https://issues.apache.org/jira/browse/IGNITE-8570
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.4
>Reporter: Andrey Kuznetsov
>Assignee: Pavel Pereslegin
>Priority: Major
> Fix For: 2.8
>
>
> _+Problem with current GridStringLogger implementation+_:
> Most usages of {{GridStringLogger}} in test assumes the following scenario.
> First, it is set as a logger for some Ignite node.
> Then, after some activity on that node, log content is searched for some
> predefined strings.
> {{GridStringLogger}} uses {{StringBuilder}} of bounded size internally to
> store log contents, older contents gets dropped on exaustion.
> Thus, changes that add more logging may damage some independent tests that
> use {{GridStringLogger}}.
>
> +_The suggestion for new implementation:_+
> The suggestion is to implement and use another test logger conforming to
> these requirements:
> * It does not accumulate any logs(actually, it will print no logs to
> anywhere)
> * It allows to set the listener that fires when log message matches certain
> condition,
> _+Proposed design+_, pseudocode:
> {code:java}
> public class ListeningTestLogger implements IgniteLogger {
> public void registerListener(Consumer lsnr);
> public void unregisterListener(Consumer lsnr);
>
> public void clearListeners();
> }
> {code}
> In 99.9% cases at some point we should validate listener precondition. For
> example, default precondition for {{substring listener}} - "_Is there any
> message in the log with such substring?_". So, listener should support
> validation.
> {code:java}
> interface LogListener extends Consumer {
> void check() throws AssertionError;
> }
> {code}
> To simplify creation of common case listeners (substring, regular expression
> and predicate) special listener builder should be introduced.
> +_Sample logger usage_+:
> {code:java}
> ListeningTestLogger log = new ListeningTestLogger(false, super.log);
> // Create listener that should match "hello" (2 times) and "Ignite" (case
> insensitive, once at least)
> LogListener lsnr =
> LogListener.matches("hello").times(2).andMatches(Pattern.compile(""(?i)ignite")).build();
> log.registerListener(lsnr);
> // ...
> // ...
> // ...
> lsnr.check(); // throws AssertionError if precodition is not met.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9756) [Test Failed] IgniteCacheIncrementTxTest.testIncrementTxTopologyChange2 fails sometimes in master.
[
https://issues.apache.org/jira/browse/IGNITE-9756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16651671#comment-16651671
]
Alexey Goncharuk commented on IGNITE-9756:
--
[~xtern], if I remember correctly, we added deduplication of the eviction
requests to avoid very large queue sizes because we attempt to clear partition
after each transaction commit. I think we can add a correct synchronization
here - add the task to the queue and the set under the mutex, and remove the
task from the set before executing the task under the same mutex. This should
keep the deduplication logic and fix the logic you described.
> [Test Failed] IgniteCacheIncrementTxTest.testIncrementTxTopologyChange2 fails
> sometimes in master.
> --
>
> Key: IGNITE-9756
> URL: https://issues.apache.org/jira/browse/IGNITE-9756
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> IgniteCacheIncrementTxTest.testIncrementTxTopologyChange2 fails sometimes in
> master with timeout.
> Example of such failure:
> [https://ci.ignite.apache.org/viewLog.html?buildId=1977579=buildResultsDiv=IgniteTests24Java8_Cache2#testNameId-613377372188362920]
> Typical log output:
>
> {noformat}
> [2018-10-03 19:40:32,654][INFO
> ][sys-#438%cache.IgniteCacheIncrementTxTest1%][GridDhtPartitionDemander]
> Started rebalance routine [default,
> supplier=67fdbd60-24fe-4810-a6a6-41a949b3, topic=0, fullPartitions=[28,
> 31, 33, 40, 43, 56, 61, 63, 70, 86, 93, 107, 115, 129, 149, 153, 167, 187,
> 207, 215, 218, 224, 247, 279, 284, 290, 329, 332, 342, 373, 377, 383,
> 385-386, 423, 435, 469, 478, 494, 515, 525, 528, 537, 565, 603, 607, 610,
> 624, 654, 686, 707, 718, 738, 741, 746, 766, 775, 777, 797, 807, 809, 814,
> 822, 849, 856, 872, 876, 909, 911, 914, 925, 940, 943, 962, 983, 991, 1005,
> 1014], histPartitions=[]]
> [2018-10-03 19:40:32,654][INFO
> ][sys-#175%cache.IgniteCacheIncrementTxTest0%][GridDhtPartitionSupplier]
> Finished supplying rebalancing [grp=default,
> demander=688062dd-508d-4ebc-9458-a48e1ba2, topVer=AffinityTopologyVersion
> [topVer=45, minorTopVer=0], topic=0]
> [2018-10-03 19:40:32,654][INFO
> ][sys-#185%cache.IgniteCacheIncrementTxTest3%][GridDhtPartitionSupplier]
> Finished supplying rebalancing [grp=default,
> demander=3f09a855-390b-40ce-b3e0-8b411db1, topVer=AffinityTopologyVersion
> [topVer=45, minorTopVer=0], topic=0]
> [2018-10-03 19:40:32,654][INFO
> ][sys-#179%cache.IgniteCacheIncrementTxTest0%][GridDhtPartitionSupplier]
> Finished supplying rebalancing [grp=default,
> demander=67fdbd60-24fe-4810-a6a6-41a949b3, topVer=AffinityTopologyVersion
> [topVer=45, minorTopVer=0], topic=0]
> [2018-10-03 19:40:32,654][INFO
> ][sys-#234%cache.IgniteCacheIncrementTxTest1%][GridDhtPartitionDemander]
> Completed rebalancing [grp=default,
> supplier=67fdbd60-24fe-4810-a6a6-41a949b3, topVer=AffinityTopologyVersion
> [topVer=45, minorTopVer=0], progress=1/2, time=0 ms]
> [2018-10-03 19:40:32,654][INFO
> ][sys-#237%cache.IgniteCacheIncrementTxTest3%][GridDhtPartitionDemander]
> Completed (final) rebalancing [grp=default,
> supplier=4b3e5c6e-cec4-4fb6-b1b2-47fd7190, topVer=AffinityTopologyVersion
> [topVer=45, minorTopVer=0], progress=2/2, time=0 ms]
> [2018-10-03 19:40:32,654][INFO
> ][sys-#237%cache.IgniteCacheIncrementTxTest3%][GridDhtPartitionDemander]
> Completed rebalance future: RebalanceFuture [grp=CacheGroupContext
> [grp=default], topVer=AffinityTopologyVersion [topVer=45, minorTopVer=0],
> rebalanceId=96, routines=2]
> [2018-10-03 19:40:32,655][INFO
> ][sys-#162%cache.IgniteCacheIncrementTxTest2%][GridDhtPartitionDemander]
> Completed (final) rebalancing [grp=default,
> supplier=4b3e5c6e-cec4-4fb6-b1b2-47fd7190, topVer=AffinityTopologyVersion
> [topVer=45, minorTopVer=0], progress=2/2, time=0 ms]
> [2018-10-03 19:40:32,655][INFO
> ][sys-#162%cache.IgniteCacheIncrementTxTest2%][GridDhtPartitionDemander]
> Completed rebalance future: RebalanceFuture [grp=CacheGroupContext
> [grp=default], topVer=AffinityTopologyVersion [topVer=45, minorTopVer=0],
> rebalanceId=96, routines=2]
> [2018-10-03 19:40:33,260][INFO
> ][exchange-worker-#38%cache.IgniteCacheIncrementTxTest0%][GridCachePartitionExchangeManager]
> Skipping rebalancing (nothing scheduled) [top=AffinityTopologyVersion
> [topVer=45, minorTopVer=0], force=true, evt=NODE_LEFT,
> node=f675cf49-5db3-45b3-83fb-7a778849]
> [2018-10-03 19:40:33,261][INFO
> ][exchange-worker-#151%cache.IgniteCacheIncrementTxTest1%][GridDhtPartitionDemander]
> Cancelled rebalancing from all nodes [grp=default,
>
[jira] [Commented] (IGNITE-9841) SQL doesn't take lost partitions into account when persistence is enabled
[ https://issues.apache.org/jira/browse/IGNITE-9841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16651664#comment-16651664 ] Stanislav Lukyanov commented on IGNITE-9841: [~novicr], thanks! At first I thought it would be the same fix, but it definitely a different one. Filed IGNITE-9902. > SQL doesn't take lost partitions into account when persistence is enabled > - > > Key: IGNITE-9841 > URL: https://issues.apache.org/jira/browse/IGNITE-9841 > Project: Ignite > Issue Type: Bug > Components: sql >Reporter: Stanislav Lukyanov >Priority: Major > Attachments: IgniteSqlQueryWithLostPartitionsTest.java > > > IGNITE-8927 changed SQL queries to honor lost partitions. However, it doesn't > work if persistence is enabled. E.g. if there are lost partitions then > `select * from T` fails for in-memory caches (good) and silently ignores the > lost partitions for persistent caches (bad). > See attached reproducer. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9902) ScanQuery doesn't take lost partitions into account when persistence is enabled
Stanislav Lukyanov created IGNITE-9902: -- Summary: ScanQuery doesn't take lost partitions into account when persistence is enabled Key: IGNITE-9902 URL: https://issues.apache.org/jira/browse/IGNITE-9902 Project: Ignite Issue Type: Bug Reporter: Stanislav Lukyanov Same as IGNITE-9841, but about scan queries. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9776) FsyncModeFileWriteAheadLogManager can block forever in log() call
[
https://issues.apache.org/jira/browse/IGNITE-9776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16651647#comment-16651647
]
Alexey Goncharuk commented on IGNITE-9776:
--
[~astelmak], the tests commented in {{WalRolloverTypesTest}} are still hanging
after your fix, please take a look.
> FsyncModeFileWriteAheadLogManager can block forever in log() call
> -
>
> Key: IGNITE-9776
> URL: https://issues.apache.org/jira/browse/IGNITE-9776
> Project: Ignite
> Issue Type: Bug
>Reporter: Andrey Kuznetsov
>Assignee: Alexey Stelmak
>Priority: Major
> Fix For: 2.7
>
> Attachments: FsyncWalRolloverDoesNotBlockTest.java
>
>
> If WAL archiver is disabled and WALRecord being logged has {{rollOver() ==
> true}}, then {{log()}} call blocks forever in {{FileArchiver}}'s (!) method:
> {noformat}
> nextAbsoluteSegmentIndex:1707, FsyncModeFileWriteAheadLogManager$FileArchiver
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> access$3200:1437, FsyncModeFileWriteAheadLogManager$FileArchiver
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> pollNextFile:1384, FsyncModeFileWriteAheadLogManager
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> initNextWriteHandle:1243, FsyncModeFileWriteAheadLogManager
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> rollOver:1130, FsyncModeFileWriteAheadLogManager
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> log:712, FsyncModeFileWriteAheadLogManager
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> {noformat}
> Reproducer is attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9841) SQL doesn't take lost partitions into account when persistence is enabled
[ https://issues.apache.org/jira/browse/IGNITE-9841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stanislav Lukyanov updated IGNITE-9841: --- Summary: SQL doesn't take lost partitions into account when persistence is enabled (was: SQL take lost partitions into account when persistence is enabled) > SQL doesn't take lost partitions into account when persistence is enabled > - > > Key: IGNITE-9841 > URL: https://issues.apache.org/jira/browse/IGNITE-9841 > Project: Ignite > Issue Type: Bug > Components: sql >Reporter: Stanislav Lukyanov >Priority: Major > Attachments: IgniteSqlQueryWithLostPartitionsTest.java > > > IGNITE-8927 changed SQL queries to honor lost partitions. However, it doesn't > work if persistence is enabled. E.g. if there are lost partitions then > `select * from T` fails for in-memory caches (good) and silently ignores the > lost partitions for persistent caches (bad). > See attached reproducer. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9900) Upgrade annotations.jar to a new version
[ https://issues.apache.org/jira/browse/IGNITE-9900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16651623#comment-16651623 ] ASF GitHub Bot commented on IGNITE-9900: GitHub user slukyano opened a pull request: https://github.com/apache/ignite/pull/5004 IGNITE-9900: Upgrade annotations.jar to a new version. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9900 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5004.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5004 commit 2e9e6a3a21a117ca9a9ef2864f9e7e1541746388 Author: Stanislav Lukyanov Date: 2018-10-16T12:29:38Z IGNITE-9900: Upgrade annotations.jar to a new version. > Upgrade annotations.jar to a new version > > > Key: IGNITE-9900 > URL: https://issues.apache.org/jira/browse/IGNITE-9900 > Project: Ignite > Issue Type: Improvement >Reporter: Stanislav Lukyanov >Assignee: Stanislav Lukyanov >Priority: Major > > OWASP Dependency Check reports that annotations.jar of version 13.0 is > affected by vulnerability CVE-2017-8316, > while it obviously isn't (the CVE is about XXE attack, and annotations.jar > is, well, annotations). > The issue is that NVD database only says that "intellij_idea" is affected, > and OWASP doesn't know better than to map annotations.jar to the > intellij_idea product. > While the problem could be (and perhaps will be, see > https://youtrack.jetbrains.com/issue/IDEA-200601) sorted out on the level of > OWASP and NVD, the easiest way to workaround this is to upgrade > annotations.jar to a new version (currently 16.0.3). It will help Ignite > users to avoid annoying false-positive warnings from OWASP. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9893) add hibernate-5.2 module
[ https://issues.apache.org/jira/browse/IGNITE-9893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16651612#comment-16651612 ] Ilya Kasnacheev commented on IGNITE-9893: - Please create a pull request to apache/ignite, master branch. This way it will be possible to commend on your commit. Is it possible to do some changes to hibernate-5.1 implementation to make it compatible with hibernate-5.2 too? If the answer is no, I suggest removing hibernate-5.1 altogether in favor of 5.2. > add hibernate-5.2 module > > > Key: IGNITE-9893 > URL: https://issues.apache.org/jira/browse/IGNITE-9893 > Project: Ignite > Issue Type: New Feature > Components: hibernate >Reporter: Scott Feldstein >Priority: Major > > hi, > I have ported hibernate-5.2 to ignite 2.7.0-SNAPSHOT HEAD. > commit: > [https://github.com/scottmf/ignite/commit/4f2caafb8c433e3f840d14f91c2d83da1052afd9] > All tests pass except > CacheHibernateBlobStoreSelfTest.testSimpleMultithreading which is carryover > from the hibernate-5.1 implementation. There is a bug already associated with > the failure: > https://issues.apache.org/jira/browse/IGNITE-1757 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9798) Add TensorFlow Integration Page to Ignite website
[ https://issues.apache.org/jira/browse/IGNITE-9798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akmal Chaudhri updated IGNITE-9798: --- Description: We need to create a dedicated page for Ignite and TensorFlow integration. Please put it under Machine Learning item of the Features menu. [~abchaudhri], will provide a reference to the readme.io page with in-depth integration description. [~dmagda], I have discussed this with [~chief]. He will create a separate section with new pages for TensorFlow Integration. was: We need to create a dedicated page for Ignite and TensorFlow integration. Please put it under Machine Learning item of the Features menu. [~abchaudhri], will provide a reference to the readme.io page with in-depth integration description. > Add TensorFlow Integration Page to Ignite website > - > > Key: IGNITE-9798 > URL: https://issues.apache.org/jira/browse/IGNITE-9798 > Project: Ignite > Issue Type: Task > Components: documentation, site >Reporter: Denis Magda >Assignee: Prachi Garg >Priority: Major > Fix For: 2.7 > > > We need to create a dedicated page for Ignite and TensorFlow integration. > Please put it under Machine Learning item of the Features menu. > [~abchaudhri], will provide a reference to the readme.io page with in-depth > integration description. > [~dmagda], I have discussed this with [~chief]. He will create a separate > section with new pages for TensorFlow Integration. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9901) [TC Bot] Exclude losses of visa requests while TC Bot server reloading
PetrovMikhail created IGNITE-9901: - Summary: [TC Bot] Exclude losses of visa requests while TC Bot server reloading Key: IGNITE-9901 URL: https://issues.apache.org/jira/browse/IGNITE-9901 Project: Ignite Issue Type: Task Reporter: PetrovMikhail Assignee: PetrovMikhail Exclude losses of visa requests while TC Bot server reloading -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-9234) Wrong javadocs about null value for cache name.
[ https://issues.apache.org/jira/browse/IGNITE-9234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Ostanin closed IGNITE-9234. > Wrong javadocs about null value for cache name. > --- > > Key: IGNITE-9234 > URL: https://issues.apache.org/jira/browse/IGNITE-9234 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.6 >Reporter: Alexey Kuznetsov >Assignee: Oleg Ostanin >Priority: Minor > Labels: newbie > Fix For: 2.8 > > > Since Ignite 2.0 cache name can not be null (see IGNITE-3488). > javadocs for the following methods are not correct: > org.apache.ignite.configuration.CacheConfiguration#getName > org.apache.ignite.Ignite#cacheNames > They should be fixed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9739) Critical exception in transaction processing in case we have nodes out of baseline and non-persisted cache
[
https://issues.apache.org/jira/browse/IGNITE-9739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-9739:
-
Ignite Flags: (was: Docs Required)
> Critical exception in transaction processing in case we have nodes out of
> baseline and non-persisted cache
> --
>
> Key: IGNITE-9739
> URL: https://issues.apache.org/jira/browse/IGNITE-9739
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Reporter: Sergey Kosarev
>Assignee: Sergey Kosarev
>Priority: Major
>
> Activation finished
> {code:java}
> 2018-09-20 20:47:05.169 [INFO
> ][sys-#307%DPL_GRID%DplGridNodeName%][o.g.g.i.p.c.d.GridSnapshotAwareClusterStateProcessorImpl]
> Successfully performed final activation steps
> [nodeId=382437eb-fd8a-4f92-acd5-d9ea562c8557, client=false,
> topVer=AffinityTopologyVersion [topVer=160, minorTopVer=1]]
> {code}
> but we have nodes not in base line
> {code:java}
> 2018-09-20 20:45:36.116 [INFO
> ][sys-#305%DPL_GRID%DplGridNodeName%][o.g.g.i.p.c.d.GridSnapshotAwareClusterStateProcessorImpl]
> Local node is not included in Baseline Topology and will not be used for
> persistent data storage. Use control.(sh|bat) script or IgniteCluster
> interface to include the node to Baseline Topology.
> {code}
> And we have cache (869481129) in the data region with persistanceEnabled=false
> {code:java}
> 2018-09-20 20:49:01.825 [INFO
> ][exchange-worker-#154%DPL_GRID%DplGridNodeName%][o.a.i.i.p.cache.GridCacheProcessor]
> Started cache [name=DPL_PUBLISHED_CACHES_REGISTRY$, *id=869481129*, group=SY
> STEM_CACHEGROUP_PUBLISHED_REGISTRY, memoryPolicyName=not-persisted,
> mode=PARTITIONED, atomicity=TRANSACTIONAL, backups=3]
> {code}
> Transaction on this cache(869481129)
> {code:java}
> 869481129{code}
> leads to critical error causing nodes by faulure handler:
> {code:java}
> 2018-09-20 20:50:24.275
> [ERROR][sys-stripe-41-#42%DPL_GRID%DplGridNodeName%][o.a.i.i.p.cache.GridCacheIoManager]
> Failed processing message [senderId=62e986f0-62b5-4ec8-8cc7-27b74d345235,
> msg=GridDhtTxPrepareRequest [nearNodeId=814af7c4-2de5-4511-b1ea-065b91eaa774,
> futId=520e308f561-255fdea5-a996-4102-a120-afa380c54570, miniId=1,
> topVer=AffinityTopologyVersion [topVer=160, minorTopVer=2],
> invalidateNearEntries={}, nearWrites=null, owned=null,
> nearXidVer=GridCacheVersion [topVer=148944365, order=1537511036821,
> nodeOrder=132], subjId=814af7c4-2de5-4511-b1ea-065b91eaa774, taskNameHash=0,
> preloadKeys=null, skipCompletedVers=false,
> super=GridDistributedTxPrepareRequest [threadId=58, concurrency=PESSIMISTIC,
> isolation=READ_COMMITTED, writeVer=GridCacheVersion [topVer=148944365,
> order=1537511036824, nodeOrder=7], timeout=299970, reads=null,
> writes=ArrayList [
> IgniteTxEntry [key=KeyCacheObjectImpl [part=27254,
> val=com.sbt.api.entities.out.IPublishedDocType, hasValBytes=true],
> *cacheId=869481129*,
> txKey=IgniteTxKey [key=KeyCacheObjectImpl [part=27254,
> val=com.sbt.api.entities.out.IPublishedDocType, hasValBytes=true],
> *cacheId=869481129*], val=[op=CREATE,
> val=com.sbt.dpl.gridgain.PublishedRegistry$PublishedCacheTuple
> [idHash=811765531, hash=1522508040,
> cacheName=com.sbt.gbk.entities.DocType_DPL_union-module,indexes=ArrayList
> {com.sbt.dpl.gridgain.newModel.base.indexes.PublishedIndexType
> [idHash=1583970836, hash=363194492, isSoftReference=false,
> unselectiveBuckets=4096, fieldNames=ArrayList
> \{isDeleted},moduleName=union-module
> , cachedUnselectives=1, selectors=ArrayList {isDeleted},
> exceptUnselectives=false, primitiveCollection=false, isVersioned=false,
> isComposite=false, isSystemTypeBelongs=false,
> name=com.sbt.gbk.entities.DocType_DPL_isDeleted, isIndexedCollection=false,
> isGlobal=false, maxSelective=1000],
> com.sbt.dpl.gridgain.newModel.base.indexes.PublishedIndexType
> [idHash=2060926101, hash=1983794578, isSoftReference=false,
> unselectiveBuckets=4096, fieldNames=ArrayList ,moduleName=union-module,
> cachedUnselectives=1, selectors=ArrayList, exceptUnselectives=false,
> primitiveCollection=false, isVersioned=false, isComposite=false,
> isSystemTypeBelongs=false, name=com.sbt.gbk.entities.DocType_DPL_code,
> isIndexedCollection=false, isGlobal=true, maxSelective=1000]
> , com.sbt.dpl.gridgain.newModel.base.indexes.PublishedIndexType
> [idHash=1821682714, hash=-1245813786, isSoftReference=false,
> unselectiveBuckets=4096, fieldNames=ArrayList {globalId},
> moduleName=union-module, cachedUnselectives=1, selectors=ArrayList
> {globalId}, exceptUnselectives=false, primitiveCollection=false,
> isVersioned=false, isComposite=false, isSystemTypeBelongs=false,
> name=com.sbt.gbk.entities.DocType_DPL_globalId, isIndexedCollection=false,
>
[jira] [Commented] (IGNITE-9234) Wrong javadocs about null value for cache name.
[ https://issues.apache.org/jira/browse/IGNITE-9234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16651590#comment-16651590 ] ASF GitHub Bot commented on IGNITE-9234: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4548 > Wrong javadocs about null value for cache name. > --- > > Key: IGNITE-9234 > URL: https://issues.apache.org/jira/browse/IGNITE-9234 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.6 >Reporter: Alexey Kuznetsov >Assignee: Oleg Ostanin >Priority: Minor > Labels: newbie > Fix For: 2.8 > > > Since Ignite 2.0 cache name can not be null (see IGNITE-3488). > javadocs for the following methods are not correct: > org.apache.ignite.configuration.CacheConfiguration#getName > org.apache.ignite.Ignite#cacheNames > They should be fixed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-9234) Wrong javadocs about null value for cache name.
[ https://issues.apache.org/jira/browse/IGNITE-9234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov resolved IGNITE-9234. -- Resolution: Fixed Merged to master. > Wrong javadocs about null value for cache name. > --- > > Key: IGNITE-9234 > URL: https://issues.apache.org/jira/browse/IGNITE-9234 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.6 >Reporter: Alexey Kuznetsov >Assignee: Oleg Ostanin >Priority: Minor > Labels: newbie > Fix For: 2.8 > > > Since Ignite 2.0 cache name can not be null (see IGNITE-3488). > javadocs for the following methods are not correct: > org.apache.ignite.configuration.CacheConfiguration#getName > org.apache.ignite.Ignite#cacheNames > They should be fixed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9234) Wrong javadocs about null value for cache name.
[ https://issues.apache.org/jira/browse/IGNITE-9234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-9234: - Fix Version/s: 2.8 > Wrong javadocs about null value for cache name. > --- > > Key: IGNITE-9234 > URL: https://issues.apache.org/jira/browse/IGNITE-9234 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.6 >Reporter: Alexey Kuznetsov >Assignee: Oleg Ostanin >Priority: Minor > Labels: newbie > Fix For: 2.8 > > > Since Ignite 2.0 cache name can not be null (see IGNITE-3488). > javadocs for the following methods are not correct: > org.apache.ignite.configuration.CacheConfiguration#getName > org.apache.ignite.Ignite#cacheNames > They should be fixed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9292) MVCC SQL: Unexpected state exception when updating backup
[
https://issues.apache.org/jira/browse/IGNITE-9292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16651585#comment-16651585
]
ASF GitHub Bot commented on IGNITE-9292:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4984
> MVCC SQL: Unexpected state exception when updating backup
> -
>
> Key: IGNITE-9292
> URL: https://issues.apache.org/jira/browse/IGNITE-9292
> Project: Ignite
> Issue Type: Bug
> Components: mvcc, sql
>Reporter: Ivan Pavlukhin
>Assignee: Igor Seliverstov
>Priority: Major
> Fix For: 2.7
>
> Attachments: MvccInsertUpdateConcurrent.java
>
>
> Unexpected state exception is observed during concurrent execution insert and
> fast update for same key.
> One of observed with concurrent update and insert for the same key from the
> same node serializes as follows:
> 1. insert on primary
> 2. insert on backup
> 3. update on primary waits on lock
> 4. insert is prepared on backup
> 5. insert is prepared on primary
> 6. insert is committed on primary (before committing on backup)
> 7. update waiting on lock wakes up
> 8. update is executed on primary
> 9. update fails on backup because sees inserted row in prepared state
> It is one possible erroneous scenario. There might be others. TX log update
> procedure should be thoroughly reviewed.
> {noformat}
> [2018-08-16
> 16:32:25,452][ERROR][ForkJoinPool.commonPool-worker-2][DmlStatementsProcessor]
> Error during update [localNodeId=6709af72-2fe9-4eab-9ee5-be83eab0]
> class org.apache.ignite.IgniteCheckedException: Failed to update backup node:
> [localNodeId=6709af72-2fe9-4eab-9ee5-be83eab0,
> remoteNodeId=4ca5b185-c5d1-4756-8977-e57aec31]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.onResult(GridDhtTxAbstractEnlistFuture.java:931)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.processDhtTxQueryEnlistResponse(GridDhtTransactionalCacheAdapter.java:2245)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.access$1000(GridDhtTransactionalCacheAdapter.java:106)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$16.apply(GridDhtTransactionalCacheAdapter.java:237)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$16.apply(GridDhtTransactionalCacheAdapter.java:235)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1056)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:581)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:380)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:306)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:101)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:295)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1569)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1197)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:127)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1093)
> at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:496)
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.IgniteCheckedException: Runtime failure on
> bounds: [lower=MvccMaxSearchRow [], upper=MvccMinSearchRow []]
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.visit(BPlusTree.java:1047)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.mvccUpdate(IgniteCacheOffheapManagerImpl.java:1887)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.mvccUpdate(IgniteCacheOffheapManagerImpl.java:523)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.mvccSet(GridCacheMapEntry.java:1080)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxRemote.mvccEnlistBatch(GridDhtTxRemote.java:451)
> at
>
[jira] [Updated] (IGNITE-9882) OOME in Hadoop suite
[ https://issues.apache.org/jira/browse/IGNITE-9882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-9882: Component/s: sql > OOME in Hadoop suite > > > Key: IGNITE-9882 > URL: https://issues.apache.org/jira/browse/IGNITE-9882 > Project: Ignite > Issue Type: Bug > Components: hadoop, sql >Reporter: Vladimir Ozerov >Assignee: Taras Ledkov >Priority: Blocker > Fix For: 2.7 > > > Hadoop suite starts failing with OOME after several commits were merged. I > suspect that it may be related to IGNITE-9171 merge or IGNITE-9561. See two > runs: > Failure: > https://ci.ignite.apache.org/viewLog.html?buildId=2063682=buildResultsDiv=IgniteTests24Java8_Hadoop -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9292) MVCC SQL: Unexpected state exception when updating backup
[
https://issues.apache.org/jira/browse/IGNITE-9292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-9292:
Ignite Flags: (was: Docs Required)
> MVCC SQL: Unexpected state exception when updating backup
> -
>
> Key: IGNITE-9292
> URL: https://issues.apache.org/jira/browse/IGNITE-9292
> Project: Ignite
> Issue Type: Bug
> Components: mvcc, sql
>Reporter: Ivan Pavlukhin
>Assignee: Igor Seliverstov
>Priority: Major
> Fix For: 2.7
>
> Attachments: MvccInsertUpdateConcurrent.java
>
>
> Unexpected state exception is observed during concurrent execution insert and
> fast update for same key.
> One of observed with concurrent update and insert for the same key from the
> same node serializes as follows:
> 1. insert on primary
> 2. insert on backup
> 3. update on primary waits on lock
> 4. insert is prepared on backup
> 5. insert is prepared on primary
> 6. insert is committed on primary (before committing on backup)
> 7. update waiting on lock wakes up
> 8. update is executed on primary
> 9. update fails on backup because sees inserted row in prepared state
> It is one possible erroneous scenario. There might be others. TX log update
> procedure should be thoroughly reviewed.
> {noformat}
> [2018-08-16
> 16:32:25,452][ERROR][ForkJoinPool.commonPool-worker-2][DmlStatementsProcessor]
> Error during update [localNodeId=6709af72-2fe9-4eab-9ee5-be83eab0]
> class org.apache.ignite.IgniteCheckedException: Failed to update backup node:
> [localNodeId=6709af72-2fe9-4eab-9ee5-be83eab0,
> remoteNodeId=4ca5b185-c5d1-4756-8977-e57aec31]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.onResult(GridDhtTxAbstractEnlistFuture.java:931)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.processDhtTxQueryEnlistResponse(GridDhtTransactionalCacheAdapter.java:2245)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.access$1000(GridDhtTransactionalCacheAdapter.java:106)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$16.apply(GridDhtTransactionalCacheAdapter.java:237)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$16.apply(GridDhtTransactionalCacheAdapter.java:235)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1056)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:581)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:380)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:306)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:101)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:295)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1569)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1197)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:127)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1093)
> at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:496)
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.IgniteCheckedException: Runtime failure on
> bounds: [lower=MvccMaxSearchRow [], upper=MvccMinSearchRow []]
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.visit(BPlusTree.java:1047)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.mvccUpdate(IgniteCacheOffheapManagerImpl.java:1887)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.mvccUpdate(IgniteCacheOffheapManagerImpl.java:523)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.mvccSet(GridCacheMapEntry.java:1080)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxRemote.mvccEnlistBatch(GridDhtTxRemote.java:451)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.processDhtTxQueryEnlistRequest(GridDhtTransactionalCacheAdapter.java:2209)
> at
>
[jira] [Commented] (IGNITE-9891) ODBC: SQLTables does not work with list of table types
[
https://issues.apache.org/jira/browse/IGNITE-9891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16651580#comment-16651580
]
Vladimir Ozerov commented on IGNITE-9891:
-
[~isapego], [~gvvinblade], Igniters,
What is the impact of this bug, that we decided to include it into AI 2.7?
> ODBC: SQLTables does not work with list of table types
> --
>
> Key: IGNITE-9891
> URL: https://issues.apache.org/jira/browse/IGNITE-9891
> Project: Ignite
> Issue Type: Bug
> Components: odbc
>Affects Versions: 2.6
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>Priority: Major
> Labels: odbc
> Fix For: 2.7
>
>
> {{SQLTables}} do not work with list of table types as stated in
> https://docs.microsoft.com/en-us/sql/odbc/reference/syntax/sqltables-function?view=sql-server-2017
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9891) ODBC: SQLTables does not work with list of table types
[
https://issues.apache.org/jira/browse/IGNITE-9891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego updated IGNITE-9891:
Fix Version/s: 2.7
> ODBC: SQLTables does not work with list of table types
> --
>
> Key: IGNITE-9891
> URL: https://issues.apache.org/jira/browse/IGNITE-9891
> Project: Ignite
> Issue Type: Bug
> Components: odbc
>Affects Versions: 2.6
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>Priority: Major
> Labels: odbc
> Fix For: 2.7
>
>
> {{SQLTables}} do not work with list of table types as stated in
> https://docs.microsoft.com/en-us/sql/odbc/reference/syntax/sqltables-function?view=sql-server-2017
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9900) Upgrade annotations.jar to a new version
Stanislav Lukyanov created IGNITE-9900: -- Summary: Upgrade annotations.jar to a new version Key: IGNITE-9900 URL: https://issues.apache.org/jira/browse/IGNITE-9900 Project: Ignite Issue Type: Improvement Reporter: Stanislav Lukyanov Assignee: Stanislav Lukyanov OWASP Dependency Check reports that annotations.jar of version 13.0 is affected by vulnerability CVE-2017-8316, while it obviously isn't (the CVE is about XXE attack, and annotations.jar is, well, annotations). The issue is that NVD database only says that "intellij_idea" is affected, and OWASP doesn't know better than to map annotations.jar to the intellij_idea product. While the problem could be (and perhaps will be, see https://youtrack.jetbrains.com/issue/IDEA-200601) sorted out on the level of OWASP and NVD, the easiest way to workaround this is to upgrade annotations.jar to a new version (currently 16.0.3). It will help Ignite users to avoid annoying false-positive warnings from OWASP. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9804) SSL: Expired certificates are not refused
[ https://issues.apache.org/jira/browse/IGNITE-9804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16651566#comment-16651566 ] Ilya Kasnacheev commented on IGNITE-9804: - [~andmed] perhaps close it with cannot reproduce then? > SSL: Expired certificates are not refused > - > > Key: IGNITE-9804 > URL: https://issues.apache.org/jira/browse/IGNITE-9804 > Project: Ignite > Issue Type: Bug >Reporter: Andrew Medvedev >Priority: Major > Attachments: SslTests.java > > > Expired certificate scenarios are not covered by current tests > # Set date to 2038: sudo date --set='@2147483647' > # Run org.apache.ignite.client.SecurityTest#testEncryption > Connection is accepted although certificate expires in 2032. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9864) CacheQueriesTest test fails in .NET
[ https://issues.apache.org/jira/browse/IGNITE-9864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16651563#comment-16651563 ] ASF GitHub Bot commented on IGNITE-9864: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4973 > CacheQueriesTest test fails in .NET > --- > > Key: IGNITE-9864 > URL: https://issues.apache.org/jira/browse/IGNITE-9864 > Project: Ignite > Issue Type: Bug > Components: platforms, sql >Reporter: Vladimir Ozerov >Assignee: Taras Ledkov >Priority: Major > Fix For: 2.7 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9882) OOME in Hadoop suite
[ https://issues.apache.org/jira/browse/IGNITE-9882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16651554#comment-16651554 ] ASF GitHub Bot commented on IGNITE-9882: GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/5003 IGNITE-9882: investigation progress 1 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9882 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5003.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5003 commit bf50cc64b535dd79b2c0c1754aa6d82cde49f8b9 Author: tledkov-gridgain Date: 2018-10-16T11:46:28Z IGNITE-9882: investigation progress 1 > OOME in Hadoop suite > > > Key: IGNITE-9882 > URL: https://issues.apache.org/jira/browse/IGNITE-9882 > Project: Ignite > Issue Type: Bug > Components: hadoop >Reporter: Vladimir Ozerov >Assignee: Taras Ledkov >Priority: Blocker > Fix For: 2.7 > > > Hadoop suite starts failing with OOME after several commits were merged. I > suspect that it may be related to IGNITE-9171 merge or IGNITE-9561. See two > runs: > Failure: > https://ci.ignite.apache.org/viewLog.html?buildId=2063682=buildResultsDiv=IgniteTests24Java8_Hadoop -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9887) A lot of exceptions on cluster deactivation.
[
https://issues.apache.org/jira/browse/IGNITE-9887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16651543#comment-16651543
]
ASF GitHub Bot commented on IGNITE-9887:
Github user devozerov closed the pull request at:
https://github.com/apache/ignite/pull/4999
> A lot of exceptions on cluster deactivation.
>
>
> Key: IGNITE-9887
> URL: https://issues.apache.org/jira/browse/IGNITE-9887
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Alexey Kuznetsov
>Assignee: Vladimir Ozerov
>Priority: Blocker
> Fix For: 2.7
>
>
> Start node with caches configured via config.
> Activate cluster.
> Deactivate cluster - got following exception for almost for all caches.
> {code}
> [2018-10-15
> 10:31:56,715][ERROR][exchange-worker-#44%tester%][IgniteH2Indexing] Failed to
> drop schema on cache stop (will ignore): c_partitioned
> class org.apache.ignite.internal.processors.query.IgniteSQLException: Failed
> to execute statement: DROP SCHEMA IF EXISTS "c_partitioned"
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSystemStatement(IgniteH2Indexing.java:763)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.dropSchema(IgniteH2Indexing.java:715)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.unregisterCache(IgniteH2Indexing.java:3577)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStop0(GridQueryProcessor.java:1693)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStop(GridQueryProcessor.java:885)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.stopCache(GridCacheProcessor.java:1375)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStop(GridCacheProcessor.java:2336)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.processCacheStopRequestOnExchangeDone(GridCacheProcessor.java:2488)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onExchangeDone(GridCacheProcessor.java:2557)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:1921)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.finishExchangeOnCoordinator(GridDhtPartitionsExchangeFuture.java:3265)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onAllReceived(GridDhtPartitionsExchangeFuture.java:2973)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchangeFuture.java:1321)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:789)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2657)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2529)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.h2.jdbc.JdbcSQLException: Невозможно удалить "c_partitioned",
> пока существует зависимый объект "SLEEP, SQUARE, UPPERCASE, _LENGTH_, _CUBE_"
> Cannot drop "c_partitioned" because "SLEEP, SQUARE, UPPERCASE, _LENGTH_,
> _CUBE_" depends on it; SQL statement:
> DROP SCHEMA IF EXISTS "c_partitioned" [90107-197]
> at org.h2.message.DbException.getJdbcSQLException(DbException.java:357)
> at org.h2.message.DbException.get(DbException.java:179)
> at org.h2.command.ddl.DropSchema.update(DropSchema.java:59)
> at org.h2.command.CommandContainer.update(CommandContainer.java:102)
> at org.h2.command.Command.executeUpdate(Command.java:261)
> at
> org.h2.jdbc.JdbcStatement.executeUpdateInternal(JdbcStatement.java:169)
> at org.h2.jdbc.JdbcStatement.executeUpdate(JdbcStatement.java:126)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSystemStatement(IgniteH2Indexing.java:758)
> ... 17 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9887) A lot of exceptions on cluster deactivation.
[
https://issues.apache.org/jira/browse/IGNITE-9887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-9887:
Ignite Flags: (was: Docs Required)
> A lot of exceptions on cluster deactivation.
>
>
> Key: IGNITE-9887
> URL: https://issues.apache.org/jira/browse/IGNITE-9887
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Alexey Kuznetsov
>Assignee: Vladimir Ozerov
>Priority: Blocker
> Fix For: 2.7
>
>
> Start node with caches configured via config.
> Activate cluster.
> Deactivate cluster - got following exception for almost for all caches.
> {code}
> [2018-10-15
> 10:31:56,715][ERROR][exchange-worker-#44%tester%][IgniteH2Indexing] Failed to
> drop schema on cache stop (will ignore): c_partitioned
> class org.apache.ignite.internal.processors.query.IgniteSQLException: Failed
> to execute statement: DROP SCHEMA IF EXISTS "c_partitioned"
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSystemStatement(IgniteH2Indexing.java:763)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.dropSchema(IgniteH2Indexing.java:715)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.unregisterCache(IgniteH2Indexing.java:3577)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStop0(GridQueryProcessor.java:1693)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStop(GridQueryProcessor.java:885)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.stopCache(GridCacheProcessor.java:1375)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStop(GridCacheProcessor.java:2336)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.processCacheStopRequestOnExchangeDone(GridCacheProcessor.java:2488)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onExchangeDone(GridCacheProcessor.java:2557)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:1921)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.finishExchangeOnCoordinator(GridDhtPartitionsExchangeFuture.java:3265)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onAllReceived(GridDhtPartitionsExchangeFuture.java:2973)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchangeFuture.java:1321)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:789)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2657)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2529)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.h2.jdbc.JdbcSQLException: Невозможно удалить "c_partitioned",
> пока существует зависимый объект "SLEEP, SQUARE, UPPERCASE, _LENGTH_, _CUBE_"
> Cannot drop "c_partitioned" because "SLEEP, SQUARE, UPPERCASE, _LENGTH_,
> _CUBE_" depends on it; SQL statement:
> DROP SCHEMA IF EXISTS "c_partitioned" [90107-197]
> at org.h2.message.DbException.getJdbcSQLException(DbException.java:357)
> at org.h2.message.DbException.get(DbException.java:179)
> at org.h2.command.ddl.DropSchema.update(DropSchema.java:59)
> at org.h2.command.CommandContainer.update(CommandContainer.java:102)
> at org.h2.command.Command.executeUpdate(Command.java:261)
> at
> org.h2.jdbc.JdbcStatement.executeUpdateInternal(JdbcStatement.java:169)
> at org.h2.jdbc.JdbcStatement.executeUpdate(JdbcStatement.java:126)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSystemStatement(IgniteH2Indexing.java:758)
> ... 17 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9574) Document Gradient boosting
[ https://issues.apache.org/jira/browse/IGNITE-9574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akmal Chaudhri updated IGNITE-9574: --- Attachment: Gradient Boosting.docx > Document Gradient boosting > -- > > Key: IGNITE-9574 > URL: https://issues.apache.org/jira/browse/IGNITE-9574 > Project: Ignite > Issue Type: Task > Components: documentation, ml >Reporter: Aleksey Zinoviev >Assignee: Akmal Chaudhri >Priority: Major > Fix For: 2.7 > > Attachments: Gradient Boosting.docx > > > The documentation for the new page with name "Gradient Boosting" > https://docs.google.com/document/d/1Twztetmpu9hH9ueomhAOUZSLUCukk8AvY9ibuicDCXI/edit -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9574) Document Gradient boosting
[ https://issues.apache.org/jira/browse/IGNITE-9574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16651536#comment-16651536 ] Akmal Chaudhri commented on IGNITE-9574: [~zaleslaw], edited documentation attached. Please double-check. > Document Gradient boosting > -- > > Key: IGNITE-9574 > URL: https://issues.apache.org/jira/browse/IGNITE-9574 > Project: Ignite > Issue Type: Task > Components: documentation, ml >Reporter: Aleksey Zinoviev >Assignee: Akmal Chaudhri >Priority: Major > Fix For: 2.7 > > Attachments: Gradient Boosting.docx > > > The documentation for the new page with name "Gradient Boosting" > https://docs.google.com/document/d/1Twztetmpu9hH9ueomhAOUZSLUCukk8AvY9ibuicDCXI/edit -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9576) Document Multi-Class Logistic Regression
[ https://issues.apache.org/jira/browse/IGNITE-9576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akmal Chaudhri updated IGNITE-9576: --- Attachment: Multi-class Logisitc Regression.docx > Document Multi-Class Logistic Regression > > > Key: IGNITE-9576 > URL: https://issues.apache.org/jira/browse/IGNITE-9576 > Project: Ignite > Issue Type: Task > Components: documentation, ml >Reporter: Aleksey Zinoviev >Assignee: Akmal Chaudhri >Priority: Major > Fix For: 2.7 > > Attachments: Multi-class Logisitc Regression.docx > > > Added documentation for "Multi-class Logisitic Regression" > [https://docs.google.com/document/d/1L2NIZ0K3fn74VswT8k7Qk0Tezqyc_hAJETQGN–TZb4/edit?usp=sharing|https://docs.google.com/document/d/1L2NIZ0K3fn74VswT8k7Qk0Tezqyc_hAJETQGN--TZb4/edit?usp=sharing] > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9576) Document Multi-Class Logistic Regression
[ https://issues.apache.org/jira/browse/IGNITE-9576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16651521#comment-16651521 ] Akmal Chaudhri commented on IGNITE-9576: [~zaleslaw], edited documentation attached. Please double-check. > Document Multi-Class Logistic Regression > > > Key: IGNITE-9576 > URL: https://issues.apache.org/jira/browse/IGNITE-9576 > Project: Ignite > Issue Type: Task > Components: documentation, ml >Reporter: Aleksey Zinoviev >Assignee: Akmal Chaudhri >Priority: Major > Fix For: 2.7 > > > Added documentation for "Multi-class Logisitic Regression" > [https://docs.google.com/document/d/1L2NIZ0K3fn74VswT8k7Qk0Tezqyc_hAJETQGN–TZb4/edit?usp=sharing|https://docs.google.com/document/d/1L2NIZ0K3fn74VswT8k7Qk0Tezqyc_hAJETQGN--TZb4/edit?usp=sharing] > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9856) Add documentation for control.sh --cache config
[
https://issues.apache.org/jira/browse/IGNITE-9856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Antonov reassigned IGNITE-9856:
--
Assignee: Artem Budnikov
> Add documentation for control.sh --cache config
> ---
>
> Key: IGNITE-9856
> URL: https://issues.apache.org/jira/browse/IGNITE-9856
> Project: Ignite
> Issue Type: Improvement
> Components: documentation
>Reporter: Sergey Antonov
>Assignee: Artem Budnikov
>Priority: Major
>
> Option {{--cache config}} in {{control.sh}} must be documented.
> As reference could be used help message:
> {noformat}
> List caches configuration:
> control.sh [--host HOST_OR_IP] [--port PORT] [--user USER] [--password
> PASSWORD] [--ping-interval PING_INTERVAL] [--ping-timeout PING_TIMEOUT]
> --cache config cacheNameRegexPattern [--human-readable]
> {noformat}
> And output example:
> {noformat}
> Control utility [ver. 2.7.0-SNAPSHOT#19700101-sha1:DEV]
> 2018 Copyright(C) Apache Software Foundation
> User: santonov
>
> ignite-sys-cache: {Name=ignite-sys-cache, Group=null, Dynamic Deployment
> ID=fb381836661-93ea1b62-7e2c-449d-82f4-ede849a03e22, System=true,
> Mode=REPLICATED, Atomicity Mode=TRANSACTIONAL, Statistic Enabled=false,
> Management Enabled=false, On-heap cache enabled=false, Partition Loss
> Policy=IGNORE, Query Parallelism=1, Copy On Read=false, Listener
> Configurations=null, Load Previous Value=false, Memory Policy Name=sysMemPlc,
> Node Filter=o.a.i.configuration.CacheConfiguration$IgniteAllNodesPredicate,
> Read From Backup=true, Topology Validator=null, Time To Live Eager Flag=true,
> Write Synchronization Mode=FULL_SYNC, Invalidate=false, Affinity
> Function=o.a.i.cache.affinity.rendezvous.RendezvousAffinityFunction, Affinity
> Backups=2147483647, Affinity Partitions=100, Affinity Exclude
> Neighbors=false, Affinity
> Mapper=o.a.i.i.processors.cache.GridCacheDefaultAffinityKeyMapper, Rebalance
> Mode=SYNC, Rebalance Batch Size=524288, Rebalance Timeout=1, Rebalance
> Delay=0, Time Between Rebalance Messages=0, Rebalance Batches Count=2,
> Rebalance Cache Order=-2, Eviction Policy Enabled=false, Eviction Policy
> Factory=null, Eviction Policy Max Size=null, Eviction Filter=null, Near Cache
> Enabled=false, Near Start Size=0, Near Eviction Policy Factory=null, Near
> Eviction Policy Max Size=null, Default Lock Timeout=0, Query Entities=[],
> Cache Interceptor=null, Store Enabled=false, Store Class=null, Store Factory
> Class=null, Store Keep Binary=false, Store Read Through=false, Store Write
> Through=false, Store Write Coalescing=true, Write-Behind Enabled=false,
> Write-Behind Flush Size=10240, Write-Behind Frequency=5000, Write-Behind
> Flush Threads Count=1, Write-Behind Batch Size=512, Concurrent Asynchronous
> Operations Number=500, Loader Factory Class Name=null, Writer Factory Class
> Name=null, Expiry Policy Factory Class
> Name=javax.cache.configuration.FactoryBuilder$SingletonFactory, Query
> Execution Time Threshold=3000, Query Escaped Names=false, Query SQL
> Schema=null, Query SQL functions=null, Query Indexed Types=null, Maximum
> payload size for offheap indexes=-1, Query Metrics History Size=0}
> test-default: {Name=test-default, Group=null, Dynamic Deployment
> ID=fb381836661-93ea1b62-7e2c-449d-82f4-ede849a03e22, System=false,
> Mode=PARTITIONED, Atomicity Mode=ATOMIC, Statistic Enabled=false, Management
> Enabled=false, On-heap cache enabled=false, Partition Loss Policy=IGNORE,
> Query Parallelism=1, Copy On Read=true, Listener Configurations=null, Load
> Previous Value=false, Memory Policy Name=null, Node
> Filter=o.a.i.configuration.CacheConfiguration$IgniteAllNodesPredicate, Read
> From Backup=true, Topology Validator=null, Time To Live Eager Flag=true,
> Write Synchronization Mode=PRIMARY_SYNC, Invalidate=false, Affinity
> Function=o.a.i.cache.affinity.rendezvous.RendezvousAffinityFunction, Affinity
> Backups=0, Affinity Partitions=1024, Affinity Exclude Neighbors=false,
> Affinity Mapper=o.a.i.i.processors.cache.CacheDefaultBinaryAffinityKeyMapper,
> Rebalance Mode=ASYNC, Rebalance Batch Size=524288, Rebalance Timeout=1,
> Rebalance Delay=0, Time Between Rebalance Messages=0, Rebalance Batches
> Count=2, Rebalance Cache Order=0, Eviction Policy Enabled=false, Eviction
> Policy Factory=null, Eviction Policy Max Size=null, Eviction Filter=null,
> Near Cache Enabled=false, Near Start Size=0, Near Eviction Policy
> Factory=null, Near Eviction Policy Max Size=null, Default Lock Timeout=0,
> Query Entities=[], Cache Interceptor=null, Store Enabled=false, Store
> Class=null, Store Factory Class=null, Store Keep Binary=false, Store Read
> Through=false, Store Write Through=false,
[jira] [Commented] (IGNITE-9575) Document Binary Logistic Regression
[ https://issues.apache.org/jira/browse/IGNITE-9575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16651507#comment-16651507 ] Akmal Chaudhri commented on IGNITE-9575: [~zaleslaw], edited documentation attached. Please double-check. [^Binary Logistic Regression.docx] > Document Binary Logistic Regression > --- > > Key: IGNITE-9575 > URL: https://issues.apache.org/jira/browse/IGNITE-9575 > Project: Ignite > Issue Type: Task > Components: documentation, ml >Reporter: Aleksey Zinoviev >Assignee: Akmal Chaudhri >Priority: Major > Fix For: 2.7 > > Attachments: Binary Logistic Regression.docx > > > The docs for the page "Binary Logistic Regression" > [https://docs.google.com/document/d/1UjcyxHdcRDffbhcFEGkaPvxcG9Xn1SuTy-gmeHWaWFg/edit?usp=sharing] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9575) Document Binary Logistic Regression
[ https://issues.apache.org/jira/browse/IGNITE-9575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akmal Chaudhri updated IGNITE-9575: --- Attachment: Binary Logistic Regression.docx > Document Binary Logistic Regression > --- > > Key: IGNITE-9575 > URL: https://issues.apache.org/jira/browse/IGNITE-9575 > Project: Ignite > Issue Type: Task > Components: documentation, ml >Reporter: Aleksey Zinoviev >Assignee: Akmal Chaudhri >Priority: Major > Fix For: 2.7 > > Attachments: Binary Logistic Regression.docx > > > The docs for the page "Binary Logistic Regression" > [https://docs.google.com/document/d/1UjcyxHdcRDffbhcFEGkaPvxcG9Xn1SuTy-gmeHWaWFg/edit?usp=sharing] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9577) Document Preprocessing
[ https://issues.apache.org/jira/browse/IGNITE-9577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akmal Chaudhri updated IGNITE-9577: --- Attachment: Preprocessing.docx > Document Preprocessing > -- > > Key: IGNITE-9577 > URL: https://issues.apache.org/jira/browse/IGNITE-9577 > Project: Ignite > Issue Type: Task > Components: documentation, ml >Reporter: Aleksey Zinoviev >Assignee: Akmal Chaudhri >Priority: Major > Fix For: 2.7 > > Attachments: Preprocessing.docx > > > The link for the updating > [https://apacheignite.readme.io/docs/ml-preprocessing] > > is here > [https://docs.google.com/document/d/1_KAZd5rVTlgWI3ZI9Q5gPVo06SuNZN4Sc6XD7KOX-Xw/edit?usp=sharing] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9577) Document Preprocessing
[ https://issues.apache.org/jira/browse/IGNITE-9577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16651493#comment-16651493 ] Akmal Chaudhri commented on IGNITE-9577: [~zaleslaw], edited documentation attached. Please double-check. [^Preprocessing.docx] > Document Preprocessing > -- > > Key: IGNITE-9577 > URL: https://issues.apache.org/jira/browse/IGNITE-9577 > Project: Ignite > Issue Type: Task > Components: documentation, ml >Reporter: Aleksey Zinoviev >Assignee: Akmal Chaudhri >Priority: Major > Fix For: 2.7 > > Attachments: Preprocessing.docx > > > The link for the updating > [https://apacheignite.readme.io/docs/ml-preprocessing] > > is here > [https://docs.google.com/document/d/1_KAZd5rVTlgWI3ZI9Q5gPVo06SuNZN4Sc6XD7KOX-Xw/edit?usp=sharing] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9819) SQL: document recomendation to use TIMESTAMP instead of DATE
[ https://issues.apache.org/jira/browse/IGNITE-9819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov reassigned IGNITE-9819: -- Assignee: Prachi Garg (was: Artem Budnikov) > SQL: document recomendation to use TIMESTAMP instead of DATE > > > Key: IGNITE-9819 > URL: https://issues.apache.org/jira/browse/IGNITE-9819 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Vladimir Ozerov >Assignee: Prachi Garg >Priority: Major > Fix For: 2.7 > > > We support both DATE (date only) and TIMESTAMP (date + time) data types. > Unfortunately, DATE data type is serialized/deserialized very inefficiently, > what leads to performance degradation. > We need to warn users in documentation, that it is better to use TIMESTAMP > than DATE. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9819) SQL: document recomendation to use TIMESTAMP instead of DATE
[ https://issues.apache.org/jira/browse/IGNITE-9819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16651486#comment-16651486 ] Artem Budnikov commented on IGNITE-9819: Added a note about TIMESTAMPs and DATEs: https://apacheignite-sql.readme.io/v2.6/docs/performance-and-debugging-27 [~pgarg] please review. > SQL: document recomendation to use TIMESTAMP instead of DATE > > > Key: IGNITE-9819 > URL: https://issues.apache.org/jira/browse/IGNITE-9819 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Vladimir Ozerov >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.7 > > > We support both DATE (date only) and TIMESTAMP (date + time) data types. > Unfortunately, DATE data type is serialized/deserialized very inefficiently, > what leads to performance degradation. > We need to warn users in documentation, that it is better to use TIMESTAMP > than DATE. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9790) Assertion error on full messages merge after coordinator failover
[ https://issues.apache.org/jira/browse/IGNITE-9790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk reassigned IGNITE-9790: Assignee: (was: Alexey Goncharuk) > Assertion error on full messages merge after coordinator failover > - > > Key: IGNITE-9790 > URL: https://issues.apache.org/jira/browse/IGNITE-9790 > Project: Ignite > Issue Type: Bug >Reporter: Alexey Goncharuk >Priority: Critical > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9895) DiscoveryMessageNotifierWorker must be an instance of IgniteDiscoveryThread
[
https://issues.apache.org/jira/browse/IGNITE-9895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-9895:
-
Summary: DiscoveryMessageNotifierWorker must be an instance of
IgniteDiscoveryThread (was: DiscoveryMessageNotifierWorker must be instanceof
IgniteDiscoveryThread)
> DiscoveryMessageNotifierWorker must be an instance of IgniteDiscoveryThread
> ---
>
> Key: IGNITE-9895
> URL: https://issues.apache.org/jira/browse/IGNITE-9895
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
>Priority: Critical
> Fix For: 2.7
>
>
> This is a regression from IGNITE-9398. The newly added thread must implement
> the marker interface, otherwise it is possible for a blocking future get
> inside of discovery worker, which leads to a cluster-wide deadlock:
> {code}
> "disco-notyfier-worker-#625%internal.IgniteClientReconnectApiExceptionTest0%"
> #770 prio=5 os_prio=0 tid=0x7f479c263800 nid=0x209b waiting on condition
> [0x7f49287ec000]
>java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:177)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:140)
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.metadata(CacheObjectBinaryProcessorImpl.java:579)
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl$2.metadata(CacheObjectBinaryProcessorImpl.java:197)
> at
> org.apache.ignite.internal.binary.BinaryContext.metadata(BinaryContext.java:1283)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.getOrCreateSchema(BinaryReaderExImpl.java:2007)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:286)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:185)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readField(BinaryReaderExImpl.java:1984)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read0(BinaryFieldAccessor.java:698)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor.read(BinaryFieldAccessor.java:183)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:870)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1764)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1716)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readField(BinaryReaderExImpl.java:1984)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read0(BinaryFieldAccessor.java:698)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor.read(BinaryFieldAccessor.java:183)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:870)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1764)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1716)
> at
> org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:310)
> at
> org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal0(BinaryMarshaller.java:99)
> at
> org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:82)
> at
> org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10014)
> at
> org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10043)
> at
> org.apache.ignite.internal.GridMessageListenHandler.p2pUnmarshal(GridMessageListenHandler.java:194)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processStartRequest(GridContinuousProcessor.java:1331)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$400(GridContinuousProcessor.java:108)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:200)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:191)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:721)
> at
>
[jira] [Assigned] (IGNITE-9406) Improve SQL "Performance and Debugging" page
[ https://issues.apache.org/jira/browse/IGNITE-9406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov reassigned IGNITE-9406: -- Assignee: Vladimir Ozerov (was: Artem Budnikov) > Improve SQL "Performance and Debugging" page > > > Key: IGNITE-9406 > URL: https://issues.apache.org/jira/browse/IGNITE-9406 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Major > Fix For: 2.7 > > Attachments: ignite_sql_perf.txt > > > I prepared a document for one of Ignite clients with some advanced > information about how various performance optimizations work in Ignite SQL. > Let's compare this document with our "Performance and Debugging" page [1], > and enhance the latter with missing info (if any). > P.S.: Document is attached. Russian language. > [1] > https://apacheignite-sql.readme.io/docs/performance-and-debugging#query-execution-flow-optimizations -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9406) Improve SQL "Performance and Debugging" page
[ https://issues.apache.org/jira/browse/IGNITE-9406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16651483#comment-16651483 ] Artem Budnikov commented on IGNITE-9406: I added points 2) and 5) from the file to the page: [https://apacheignite-sql.readme.io/v2.6/docs/performance-and-debugging-27] Other points are already described. [~vozerov] please review sections "Querying Collocated Data" and "Increasing Index Inline Size". > Improve SQL "Performance and Debugging" page > > > Key: IGNITE-9406 > URL: https://issues.apache.org/jira/browse/IGNITE-9406 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Vladimir Ozerov >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.7 > > Attachments: ignite_sql_perf.txt > > > I prepared a document for one of Ignite clients with some advanced > information about how various performance optimizations work in Ignite SQL. > Let's compare this document with our "Performance and Debugging" page [1], > and enhance the latter with missing info (if any). > P.S.: Document is attached. Russian language. > [1] > https://apacheignite-sql.readme.io/docs/performance-and-debugging#query-execution-flow-optimizations -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9737) Ignite WatchDog service should be configurable
[
https://issues.apache.org/jira/browse/IGNITE-9737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16651470#comment-16651470
]
Alexey Goncharuk commented on IGNITE-9737:
--
[~andrey-kuznetsov] [~agura], now {{checkpointReadLock}} logic looks good to me.
> Ignite WatchDog service should be configurable
> --
>
> Key: IGNITE-9737
> URL: https://issues.apache.org/jira/browse/IGNITE-9737
> Project: Ignite
> Issue Type: Bug
>Reporter: Nikolay Izhikov
>Assignee: Andrey Kuznetsov
>Priority: Blocker
> Fix For: 2.7
>
>
> At the moment, there is no way to disable Ignite WatchDog service from config
> or JVM option.
> In any corner case or bug in that feature Ignite can become fully unusable
> due to unpredictable shutdown.
> We should provide a way to enable/disable this feature from config or from
> JVM option.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9234) Wrong javadocs about null value for cache name.
[ https://issues.apache.org/jira/browse/IGNITE-9234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16651460#comment-16651460 ] Igor Seliverstov commented on IGNITE-9234: -- [~oleg-ostanin], [~kuaw26], looks good to me. > Wrong javadocs about null value for cache name. > --- > > Key: IGNITE-9234 > URL: https://issues.apache.org/jira/browse/IGNITE-9234 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.6 >Reporter: Alexey Kuznetsov >Assignee: Oleg Ostanin >Priority: Minor > Labels: newbie > > Since Ignite 2.0 cache name can not be null (see IGNITE-3488). > javadocs for the following methods are not correct: > org.apache.ignite.configuration.CacheConfiguration#getName > org.apache.ignite.Ignite#cacheNames > They should be fixed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-9899) Continuous query handlers are not called on backups when one-phase commit is used
[ https://issues.apache.org/jira/browse/IGNITE-9899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16651455#comment-16651455 ] Denis Mekhanikov edited comment on IGNITE-9899 at 10/16/18 10:28 AM: - This issue has the same cache configuration and symptoms: IGNITE-4015 was (Author: dmekhanikov): This issue has the same cache configuration and symptoms. > Continuous query handlers are not called on backups when one-phase commit is > used > - > > Key: IGNITE-9899 > URL: https://issues.apache.org/jira/browse/IGNITE-9899 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.6 >Reporter: Denis Mekhanikov >Assignee: Denis Mekhanikov >Priority: Major > Attachments: CacheContinuousQueryTxBackupTest.java > > > Consider the following cache configuration: > * Atomicity mode: Transactional > * Cache mode: Partitioned > * Backups: 1 > If a continuous query is registered for such cache, then it's not processed > on backup copies. It results in remote filters not being called on backups > and lost events on changing topology. > Test case is attached: [^CacheContinuousQueryTxBackupTest.java] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9899) Continuous query handlers are not called on backups when one-phase commit is used
[ https://issues.apache.org/jira/browse/IGNITE-9899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16651455#comment-16651455 ] Denis Mekhanikov commented on IGNITE-9899: -- This issue has the same cache configuration and symptoms. > Continuous query handlers are not called on backups when one-phase commit is > used > - > > Key: IGNITE-9899 > URL: https://issues.apache.org/jira/browse/IGNITE-9899 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.6 >Reporter: Denis Mekhanikov >Assignee: Denis Mekhanikov >Priority: Major > Attachments: CacheContinuousQueryTxBackupTest.java > > > Consider the following cache configuration: > * Atomicity mode: Transactional > * Cache mode: Partitioned > * Backups: 1 > If a continuous query is registered for such cache, then it's not processed > on backup copies. It results in remote filters not being called on backups > and lost events on changing topology. > Test case is attached: [^CacheContinuousQueryTxBackupTest.java] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9898) Checkpoint thread hangs on await async task completion
[
https://issues.apache.org/jira/browse/IGNITE-9898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Govorukhin updated IGNITE-9898:
---
Component/s: persistence
> Checkpoint thread hangs on await async task completion
> --
>
> Key: IGNITE-9898
> URL: https://issues.apache.org/jira/browse/IGNITE-9898
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Reporter: Dmitriy Govorukhin
>Assignee: Dmitriy Govorukhin
>Priority: Blocker
> Fix For: 2.7
>
>
> In some cases, we can reset (IgniteTaskTrackingThreadPoolExecutor#reset)
> counters for checkpoint thread pool during execution async task, and then we
> can get hangs on await
> {code}
> [19:36:01] : [Step 4/5] [2018-10-15 16:36:01,435][INFO
> ][db-checkpoint-thread-#21691%db.IgnitePdsPageEvictionDuringPartitionClearTest0%][GridCacheDatabaseSharedManager]
> Await checkpoint pool tasks comleted, pendingTaskCnt=2, completedTaskCnt=3,
> initialized=true, err=null, activeCnt=0
> [19:36:03] : [Step 4/5] [2018-10-15 16:36:03,435][INFO
> ][db-checkpoint-thread-#21691%db.IgnitePdsPageEvictionDuringPartitionClearTest0%][GridCacheDatabaseSharedManager]
> Await checkpoint pool tasks comleted, pendingTaskCnt=2, completedTaskCnt=3,
> initialized=true, err=null, activeCnt=0
> [19:36:05] : [Step 4/5] [2018-10-15 16:36:05,436][INFO
> ][db-checkpoint-thread-#21691%db.IgnitePdsPageEvictionDuringPartitionClearTest0%][GridCacheDatabaseSharedManager]
> Await checkpoint pool tasks comleted, pendingTaskCnt=2, completedTaskCnt=3,
> initialized=true, err=null, activeCnt=0
> [19:36:07] : [Step 4/5] [2018-10-15 16:36:07,436][INFO
> ][db-checkpoint-thread-#21691%db.IgnitePdsPageEvictionDuringPartitionClearTest0%][GridCacheDatabaseSharedManager]
> Await checkpoint pool tasks comleted, pendingTaskCnt=2, completedTaskCnt=3,
> initialized=true, err=null, activeCnt=0
> [19:36:09] : [Step 4/5] [2018-10-15 16:36:09,437][INFO
> ][db-checkpoint-thread-#21691%db.IgnitePdsPageEvictionDuringPartitionClearTest0%][GridCacheDatabaseSharedManager]
> Await checkpoint pool tasks comleted, pendingTaskCnt=2, completedTaskCnt=3,
> initialized=true, err=null, activeCnt=0
> [19:36:11] : [Step 4/5] [2018-10-15 16:36:11,437][INFO
> ][db-checkpoint-thread-#21691%db.IgnitePdsPageEvictionDuringPartitionClearTest0%][GridCacheDatabaseSharedManager]
> Await checkpoint pool tasks comleted, pendingTaskCnt=2, completedTaskCnt=3,
> initialized=true, err=null, activeCnt=0
> [19:36:13] : [Step 4/5] [2018-10-15 16:36:13,438][INFO
> ][db-checkpoint-thread-#21691%db.IgnitePdsPageEvictionDuringPartitionClearTest0%][GridCacheDatabaseSharedManager]
> Await checkpoint pool tasks comleted, pendingTaskCnt=2, completedTaskCnt=3,
> initialized=true, err=null, activeCnt=0
> [19:36:15] : [Step 4/5] [2018-10-15 16:36:15,439][INFO
> ][db-checkpoint-thread-#21691%db.IgnitePdsPageEvictionDuringPartitionClearTest0%][GridCacheDatabaseSharedManager]
> Await checkpoint pool tasks comleted, pendingTaskCnt=2, completedTaskCnt=3,
> initialized=true, err=null, activeCnt=0
> [19:36:17] : [Step 4/5] [2018-10-15 16:36:17,440][INFO
> ][db-checkpoint-thread-#21691%db.IgnitePdsPageEvictionDuringPartitionClearTest0%][GridCacheDatabaseSharedManager]
> Await checkpoint pool tasks comleted, pendingTaskCnt=2, completedTaskCnt=3,
> initialized=true, err=null, activeCnt=0
> [19:36:19] : [Step 4/5] [2018-10-15 16:36:19,441][INFO
> ][db-checkpoint-thread-#21691%db.IgnitePdsPageEvictionDuringPartitionClearTest0%][GridCacheDatabaseSharedManager]
> Await checkpoint pool tasks comleted, pendingTaskCnt=2, completedTaskCnt=3,
> initialized=true, err=null, activeCnt=0
> [19:36:21] : [Step 4/5] [2018-10-15 16:36:21,442][INFO
> ][db-checkpoint-thread-#21691%db.IgnitePdsPageEvictionDuringPartitionClearTest0%][GridCacheDatabaseSharedManager]
> Await checkpoint pool tasks comleted, pendingTaskCnt=2, completedTaskCnt=3,
> initialized=true, err=null, activeCnt=0
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
