[jira] [Created] (IGNITE-11255) Fix test failure after IGNITE-7648
Pavel Voronkin created IGNITE-11255: --- Summary: Fix test failure after IGNITE-7648 Key: IGNITE-11255 URL: https://issues.apache.org/jira/browse/IGNITE-11255 Project: Ignite Issue Type: Bug Reporter: Pavel Voronkin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11255) Fix test failure after IGNITE-7648
[ https://issues.apache.org/jira/browse/IGNITE-11255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763398#comment-16763398 ] Dmitriy Pavlov commented on IGNITE-11255: - Please fill ticket description, you may provide a reference to TC runs with failures, stack traces, any other details, which will help to find or fix the issue. > Fix test failure after IGNITE-7648 > -- > > Key: IGNITE-11255 > URL: https://issues.apache.org/jira/browse/IGNITE-11255 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Voronkin >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11255) Fix test failure after IGNITE-7648
[ https://issues.apache.org/jira/browse/IGNITE-11255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-11255: Ignite Flags: (was: Docs Required) > Fix test failure after IGNITE-7648 > -- > > Key: IGNITE-11255 > URL: https://issues.apache.org/jira/browse/IGNITE-11255 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Voronkin >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10602) Failure parsing INLINE_SIZE if CREATE INDEX is one of multiple statements
[
https://issues.apache.org/jira/browse/IGNITE-10602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763394#comment-16763394
]
Vladimir Ozerov commented on IGNITE-10602:
--
Only "Queries 1" failure was caused by changes from the patch. Fixed it. Merged
to master.
> Failure parsing INLINE_SIZE if CREATE INDEX is one of multiple statements
> -
>
> Key: IGNITE-10602
> URL: https://issues.apache.org/jira/browse/IGNITE-10602
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.7
>Reporter: Ilya Kasnacheev
>Assignee: Pavel Kuznetsov
>Priority: Minor
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> On an empty cluster issue the following statements (shown using sqlline):
> {code}
> 0: jdbc:ignite:thin://localhost> CREATE TABLE public.transactions (pk INT, id
> INT, k
> . . . . . . . . . . . . . . . .> VARCHAR, v VARCHAR, PRIMARY KEY (pk, id));
> CREATE INDEX transactions_id_k_v ON public.transactions (id, k, v)
> INLINE_SIZE 150; CREATE INDEX transactions_k_v_id ON
> . . . . . . . . . . . . . . . .> public.transactions (k, v, id) INLINE_SIZE
> 150; CREATE INDEX transactions_pk_id ON public.transactions
> . . . . . . . . . . . . . . . .> (pk, id) INLINE_SIZE 20;
> {code}
> Expected: Table is created, three indexes are created.
> Actual: table is created, indexes are NOT created, error is printed:
> {{Error: Failed to parse query. Синтаксическая ошибка в выражении SQL "CREATE
> INDEX TRANSACTIONS_ID_K_V ON PUBLIC.TRANSACTIONS (ID, K, V) INLINE_SIZE[*]
> 150; CREATE INDEX TRANSACTIONS_K_V_ID ON}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11256) Implement read-only mode for grid
Alexei Scherbakov created IGNITE-11256: -- Summary: Implement read-only mode for grid Key: IGNITE-11256 URL: https://issues.apache.org/jira/browse/IGNITE-11256 Project: Ignite Issue Type: Improvement Reporter: Alexei Scherbakov Fix For: 2.8 Should be triggered from control.sh utility. Useful for maintenance work, for example checking partition consistency (idle_verify) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11193) MVCC TX: the query with specified explicit patririons fails
[
https://issues.apache.org/jira/browse/IGNITE-11193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763421#comment-16763421
]
Taras Ledkov commented on IGNITE-11193:
---
[~gvvinblade], the new tests are OK with me.
> MVCC TX: the query with specified explicit patririons fails
> ---
>
> Key: IGNITE-11193
> URL: https://issues.apache.org/jira/browse/IGNITE-11193
> Project: Ignite
> Issue Type: Bug
> Components: mvcc, sql
>Affects Versions: 2.7
>Reporter: Taras Ledkov
>Assignee: Igor Seliverstov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> If the explicit partitions specified by {{SqlFieldsQuery#setPartitions}} are
> placed on the several nodes the query fails at the partition reservation
> ({{GridDhtTxQueryEnlistFuture.checkPartitions}}) with error: "{{Cannot run
> update query. Node must own all the necessary partitions.}}"
> *Root cause*: MVCC DML doesn't map the requests
> {{GridNearTxQueryEnlistRequest}}. Each node received the messages with all
> explicit partitions.
> *Proposal fix*: use the partitions/node mapping similar to SELECT queries.
> See more:
> - {{GridH2QueryRequest#partitions}}
> - {{ReducePartitionsSpecializer#ReducePartitionsSpecializer}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11171) Assertion on tx preparing
[
https://issues.apache.org/jira/browse/IGNITE-11171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763430#comment-16763430
]
Ignite TC Bot commented on IGNITE-11171:
{panel:title=--> Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}ZooKeeper (Discovery) 1{color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=3035674]]
* ZookeeperDiscoverySpiTestSuite1:
ZookeeperDiscoveryClientDisconnectTest.testReconnectServersRestart_3 - 2,8%
fails in last 283 master runs.
* ZookeeperDiscoverySpiTestSuite1:
ZookeeperDiscoveryCommunicationFailureTest.testDefaultCommunicationFailureResolver4
- 0,0% fails in last 283 master runs.
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3029470&buildTypeId=IgniteTests24Java8_RunAll]
> Assertion on tx preparing
> -
>
> Key: IGNITE-11171
> URL: https://issues.apache.org/jira/browse/IGNITE-11171
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexei Scherbakov
>Assignee: Alexei Scherbakov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {noformat}
> 2019-01-22
> 14:00:01.203[ERROR][sys-stripe-15-#16%DPL_GRID%DplGridNodeName%][org.apache.ignite.Ignite]
> Critical system error detected. Will be handled accordingly to configured
> handler [hnd=class o.a.i.failure.StopNodeOrHaltFailureHandle
> r, failureCtx=FailureContext [type=CRITICAL_ERROR,
> err=java.lang.AssertionError: Got entry removed exception while holding
> transactional lock on entry
> [e=o.a.i.i.processors.cache.GridCacheEntryRemovedException,
> cached=GridDhtCacheEntry
> [rdrs=ReaderId[] [], part=7042, super=GridDistributedCacheEntry
> [super=GridCacheMapEntry [key=KeyCacheObjectImpl [part=7042,
> val=SCHEDULED_CHECK_STOP_PAYMENTS_TASK_DPL_defaultSection, hasValBytes=true],
> val=null, startVer=1548154332959,
> ver=GridCacheVersion [topVer=159054171, order=1548061479047, nodeOrder=20],
> hash=1755381247, extras=GridCacheObsoleteEntryExtras
> [obsoleteVer=GridCacheVersion [topVer=2147483647, order=0, nodeOrder=0]],
> flags=2]]
> java.lang.AssertionError: Got entry removed exception while holding
> transactional lock on entry
> [e=org.apache.ignite.internal.processors.cache.GridCacheEntryRemovedException,
> cached=GridDhtCacheEntry [rdrs=ReaderId[] [], part=7042, supe
> r=GridDistributedCacheEntry [super=GridCacheMapEntry [key=KeyCacheObjectImpl
> [part=7042, val=SCHEDULED_CHECK_STOP_PAYMENTS_TASK_DPL_defaultSection,
> hasValBytes=true], val=null, startVer=1548154332959, ver=GridCacheVersion
> [topVer=159054
> 171, order=1548061479047, nodeOrder=20], hash=1755381247,
> extras=GridCacheObsoleteEntryExtras [obsoleteVer=GridCacheVersion
> [topVer=2147483647, order=0, nodeOrder=0]], flags=2
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.onEntriesLocked(GridDhtTxPrepareFuture.java:512)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.prepare0(GridDhtTxPrepareFuture.java:1231)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.mapIfLocked(GridDhtTxPrepareFuture.java:671)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.prepare(GridDhtTxPrepareFuture.java:1048)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.prepareAsync(GridDhtTxLocal.java:397)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.prepareNearTx(IgniteTxHandler.java:520)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processNearTxPrepareRequest0(IgniteTxHandler.java:161)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processNearTxPrepareRequest(IgniteTxHandler.java:139)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.access$000(IgniteTxHandler.java:101)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$1.apply(IgniteTxHandler.java:181)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$1.apply(IgniteTxHandler.java:179)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1058)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:583)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:382)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:308)
[jira] [Created] (IGNITE-11257) JDBC: update handshake protocol so that the node returns its UUID.
Alexander Lapin created IGNITE-11257: Summary: JDBC: update handshake protocol so that the node returns its UUID. Key: IGNITE-11257 URL: https://issues.apache.org/jira/browse/IGNITE-11257 Project: Ignite Issue Type: Task Components: sql Reporter: Alexander Lapin Fix For: 2.8 Add node UUID to successful handshake response. For more information see [IEP-23: Best Effort Affinity|https://cwiki.apache.org/confluence/display/IGNITE/IEP-23%3A+Best+Effort+Affinity+for+thin+clients] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11171) Assertion on tx preparing
[
https://issues.apache.org/jira/browse/IGNITE-11171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763434#comment-16763434
]
Alexei Scherbakov commented on IGNITE-11171:
Failing tests seem not related to fix because they even do not start
transactions.
[~agoncharuk] please review.
> Assertion on tx preparing
> -
>
> Key: IGNITE-11171
> URL: https://issues.apache.org/jira/browse/IGNITE-11171
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexei Scherbakov
>Assignee: Alexei Scherbakov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {noformat}
> 2019-01-22
> 14:00:01.203[ERROR][sys-stripe-15-#16%DPL_GRID%DplGridNodeName%][org.apache.ignite.Ignite]
> Critical system error detected. Will be handled accordingly to configured
> handler [hnd=class o.a.i.failure.StopNodeOrHaltFailureHandle
> r, failureCtx=FailureContext [type=CRITICAL_ERROR,
> err=java.lang.AssertionError: Got entry removed exception while holding
> transactional lock on entry
> [e=o.a.i.i.processors.cache.GridCacheEntryRemovedException,
> cached=GridDhtCacheEntry
> [rdrs=ReaderId[] [], part=7042, super=GridDistributedCacheEntry
> [super=GridCacheMapEntry [key=KeyCacheObjectImpl [part=7042,
> val=SCHEDULED_CHECK_STOP_PAYMENTS_TASK_DPL_defaultSection, hasValBytes=true],
> val=null, startVer=1548154332959,
> ver=GridCacheVersion [topVer=159054171, order=1548061479047, nodeOrder=20],
> hash=1755381247, extras=GridCacheObsoleteEntryExtras
> [obsoleteVer=GridCacheVersion [topVer=2147483647, order=0, nodeOrder=0]],
> flags=2]]
> java.lang.AssertionError: Got entry removed exception while holding
> transactional lock on entry
> [e=org.apache.ignite.internal.processors.cache.GridCacheEntryRemovedException,
> cached=GridDhtCacheEntry [rdrs=ReaderId[] [], part=7042, supe
> r=GridDistributedCacheEntry [super=GridCacheMapEntry [key=KeyCacheObjectImpl
> [part=7042, val=SCHEDULED_CHECK_STOP_PAYMENTS_TASK_DPL_defaultSection,
> hasValBytes=true], val=null, startVer=1548154332959, ver=GridCacheVersion
> [topVer=159054
> 171, order=1548061479047, nodeOrder=20], hash=1755381247,
> extras=GridCacheObsoleteEntryExtras [obsoleteVer=GridCacheVersion
> [topVer=2147483647, order=0, nodeOrder=0]], flags=2
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.onEntriesLocked(GridDhtTxPrepareFuture.java:512)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.prepare0(GridDhtTxPrepareFuture.java:1231)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.mapIfLocked(GridDhtTxPrepareFuture.java:671)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.prepare(GridDhtTxPrepareFuture.java:1048)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.prepareAsync(GridDhtTxLocal.java:397)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.prepareNearTx(IgniteTxHandler.java:520)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processNearTxPrepareRequest0(IgniteTxHandler.java:161)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processNearTxPrepareRequest(IgniteTxHandler.java:139)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.access$000(IgniteTxHandler.java:101)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$1.apply(IgniteTxHandler.java:181)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$1.apply(IgniteTxHandler.java:179)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1058)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:583)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:382)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:308)
> 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:297)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1184)
> at
> org.apache.ignite.internal.managers.commun
[jira] [Comment Edited] (IGNITE-11182) Web console: Actualize grid configurator
[ https://issues.apache.org/jira/browse/IGNITE-11182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16760680#comment-16760680 ] Vasiliy Sisko edited comment on IGNITE-11182 at 2/8/19 9:18 AM: Actualised configuration of IGFS secondary file system. Test updated. Actualised SslContextFactory configuration. Actualised CacheConfiguration. [~pkonstantinov] Please test fields from description. was (Author: vsisko): Actualised configuration of IGFS secondary file system. Test updated. > Web console: Actualize grid configurator > > > Key: IGNITE-11182 > URL: https://issues.apache.org/jira/browse/IGNITE-11182 > Project: Ignite > Issue Type: Improvement >Reporter: Vasiliy Sisko >Assignee: Vasiliy Sisko >Priority: Major > > WebConsoleConfigurationSelfTest has found the next difference: > Result for class: org.apache.ignite.hadoop.fs.CachingHadoopFileSystemFactory > Missed > userNameMapper > Result for class: org.apache.ignite.ssl.SslContextFactory > Missed > cipherSuites > protocols > Result for class: org.apache.ignite.configuration.CacheConfiguration > Missed > cacheWriterFactory > expiryPolicyFactory > types > storeConcurrentLoadAllThreshold > sqlIndexMaxInlineSize > sqlOnheapCacheEnabled > interceptor > invalidate > diskPageCompression > storeByValue > sqlOnheapCacheMaxSize > eagerTtl > evictionPolicyFactory > encryptionEnabled > eventsDisabled > cacheLoaderFactory > keyConfiguration > cacheStoreSessionListenerFactories > diskPageCompressionLevel > maxQueryIteratorsCount > affinity > Deprecated > rebalanceThreadPoolSize > transactionManagerLookupClassName > Removed > isInvalidate -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11258) JDBC: update connection setup logic.
Alexander Lapin created IGNITE-11258: Summary: JDBC: update connection setup logic. Key: IGNITE-11258 URL: https://issues.apache.org/jira/browse/IGNITE-11258 Project: Ignite Issue Type: Task Components: sql Reporter: Alexander Lapin # On thin client startup it connects to *all* *nodes* provided by user by client configuration. # Upon handshake server returns its UUID to client. # By the end of the startup procedure, client have open connections to all available server nodes and the following mapping (*nodeMap*): [UUID => Connection]. Connection to all nodes helps to identify available nodes, but can lead to significant delay, when thin client is used on a large cluster with a long IP list provided by user. To lower this delay, asynchronous establishment of connections can be used. For more information see [IEP-23: Best Effort Affinity|https://cwiki.apache.org/confluence/display/IGNITE/IEP-23%3A+Best+Effort+Affinity+for+thin+clients] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11182) Web console: Actualize grid configurator
[ https://issues.apache.org/jira/browse/IGNITE-11182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko updated IGNITE-11182: --- Description: WebConsoleConfigurationSelfTest has found the next difference: Result for class: org.apache.ignite.hadoop.fs.CachingHadoopFileSystemFactory Missed userNameMapper Result for class: org.apache.ignite.ssl.SslContextFactory Missed cipherSuites protocols Result for class: org.apache.ignite.configuration.CacheConfiguration Missed cacheWriterFactory expiryPolicyFactory storeConcurrentLoadAllThreshold sqlIndexMaxInlineSize sqlOnheapCacheEnabled interceptor invalidate diskPageCompression storeByValue sqlOnheapCacheMaxSize eagerTtl evictionPolicyFactory encryptionEnabled eventsDisabled cacheLoaderFactory keyConfiguration cacheStoreSessionListenerFactories diskPageCompressionLevel maxQueryIteratorsCount affinity Deprecated rebalanceThreadPoolSize transactionManagerLookupClassName Removed isInvalidate was: WebConsoleConfigurationSelfTest has found the next difference: Result for class: org.apache.ignite.hadoop.fs.CachingHadoopFileSystemFactory Missed userNameMapper Result for class: org.apache.ignite.ssl.SslContextFactory Missed cipherSuites protocols Result for class: org.apache.ignite.configuration.CacheConfiguration Missed cacheWriterFactory expiryPolicyFactory types storeConcurrentLoadAllThreshold sqlIndexMaxInlineSize sqlOnheapCacheEnabled interceptor invalidate diskPageCompression storeByValue sqlOnheapCacheMaxSize eagerTtl evictionPolicyFactory encryptionEnabled eventsDisabled cacheLoaderFactory keyConfiguration cacheStoreSessionListenerFactories diskPageCompressionLevel maxQueryIteratorsCount affinity Deprecated rebalanceThreadPoolSize transactionManagerLookupClassName Removed isInvalidate > Web console: Actualize grid configurator > > > Key: IGNITE-11182 > URL: https://issues.apache.org/jira/browse/IGNITE-11182 > Project: Ignite > Issue Type: Improvement >Reporter: Vasiliy Sisko >Assignee: Pavel Konstantinov >Priority: Major > > WebConsoleConfigurationSelfTest has found the next difference: > Result for class: org.apache.ignite.hadoop.fs.CachingHadoopFileSystemFactory > Missed > userNameMapper > Result for class: org.apache.ignite.ssl.SslContextFactory > Missed > cipherSuites > protocols > Result for class: org.apache.ignite.configuration.CacheConfiguration > Missed > cacheWriterFactory > expiryPolicyFactory > storeConcurrentLoadAllThreshold > sqlIndexMaxInlineSize > sqlOnheapCacheEnabled > interceptor > invalidate > diskPageCompression > storeByValue > sqlOnheapCacheMaxSize > eagerTtl > evictionPolicyFactory > encryptionEnabled > eventsDisabled > cacheLoaderFactory > keyConfiguration > cacheStoreSessionListenerFactories > diskPageCompressionLevel > maxQueryIteratorsCount > affinity > Deprecated > rebalanceThreadPoolSize > transactionManagerLookupClassName > Removed > isInvalidate -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11182) Web console: Actualize grid configurator
[ https://issues.apache.org/jira/browse/IGNITE-11182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-11182: -- Assignee: Pavel Konstantinov (was: Vasiliy Sisko) > Web console: Actualize grid configurator > > > Key: IGNITE-11182 > URL: https://issues.apache.org/jira/browse/IGNITE-11182 > Project: Ignite > Issue Type: Improvement >Reporter: Vasiliy Sisko >Assignee: Pavel Konstantinov >Priority: Major > > WebConsoleConfigurationSelfTest has found the next difference: > Result for class: org.apache.ignite.hadoop.fs.CachingHadoopFileSystemFactory > Missed > userNameMapper > Result for class: org.apache.ignite.ssl.SslContextFactory > Missed > cipherSuites > protocols > Result for class: org.apache.ignite.configuration.CacheConfiguration > Missed > cacheWriterFactory > expiryPolicyFactory > types > storeConcurrentLoadAllThreshold > sqlIndexMaxInlineSize > sqlOnheapCacheEnabled > interceptor > invalidate > diskPageCompression > storeByValue > sqlOnheapCacheMaxSize > eagerTtl > evictionPolicyFactory > encryptionEnabled > eventsDisabled > cacheLoaderFactory > keyConfiguration > cacheStoreSessionListenerFactories > diskPageCompressionLevel > maxQueryIteratorsCount > affinity > Deprecated > rebalanceThreadPoolSize > transactionManagerLookupClassName > Removed > isInvalidate -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11257) JDBC: update handshake protocol so that the node returns its UUID.
[ https://issues.apache.org/jira/browse/IGNITE-11257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin reassigned IGNITE-11257: Assignee: Alexander Lapin > JDBC: update handshake protocol so that the node returns its UUID. > -- > > Key: IGNITE-11257 > URL: https://issues.apache.org/jira/browse/IGNITE-11257 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Alexander Lapin >Assignee: Alexander Lapin >Priority: Major > Labels: iep-23 > Fix For: 2.8 > > > Add node UUID to successful handshake response. > For more information see [IEP-23: Best Effort > Affinity|https://cwiki.apache.org/confluence/display/IGNITE/IEP-23%3A+Best+Effort+Affinity+for+thin+clients] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10602) Failure parsing INLINE_SIZE if CREATE INDEX is one of multiple statements
[
https://issues.apache.org/jira/browse/IGNITE-10602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763442#comment-16763442
]
Pavel Kuznetsov commented on IGNITE-10602:
--
Thank you!
> Failure parsing INLINE_SIZE if CREATE INDEX is one of multiple statements
> -
>
> Key: IGNITE-10602
> URL: https://issues.apache.org/jira/browse/IGNITE-10602
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.7
>Reporter: Ilya Kasnacheev
>Assignee: Pavel Kuznetsov
>Priority: Minor
> Fix For: 2.8
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> On an empty cluster issue the following statements (shown using sqlline):
> {code}
> 0: jdbc:ignite:thin://localhost> CREATE TABLE public.transactions (pk INT, id
> INT, k
> . . . . . . . . . . . . . . . .> VARCHAR, v VARCHAR, PRIMARY KEY (pk, id));
> CREATE INDEX transactions_id_k_v ON public.transactions (id, k, v)
> INLINE_SIZE 150; CREATE INDEX transactions_k_v_id ON
> . . . . . . . . . . . . . . . .> public.transactions (k, v, id) INLINE_SIZE
> 150; CREATE INDEX transactions_pk_id ON public.transactions
> . . . . . . . . . . . . . . . .> (pk, id) INLINE_SIZE 20;
> {code}
> Expected: Table is created, three indexes are created.
> Actual: table is created, indexes are NOT created, error is printed:
> {{Error: Failed to parse query. Синтаксическая ошибка в выражении SQL "CREATE
> INDEX TRANSACTIONS_ID_K_V ON PUBLIC.TRANSACTIONS (ID, K, V) INLINE_SIZE[*]
> 150; CREATE INDEX TRANSACTIONS_K_V_ID ON}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10347) Expose system SQL view for running queries
[ https://issues.apache.org/jira/browse/IGNITE-10347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763443#comment-16763443 ] Vladimir Ozerov commented on IGNITE-10347: -- Merged to master. > Expose system SQL view for running queries > -- > > Key: IGNITE-10347 > URL: https://issues.apache.org/jira/browse/IGNITE-10347 > Project: Ignite > Issue Type: Task >Reporter: Yury Gerzhedovich >Assignee: Yury Gerzhedovich >Priority: Major > Labels: iep-29, sql > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > Need to expose system SQL view to provide list of running queries. Proposed > name is *running_queries* with following columns: query_id, node_id, sql, > schema_name, duration. > Where, > query_id - cluster unique id of query > sql - sql command > cancelable - is is possible to cancel the query. > schema_name - SQL schema name > duration - time in ms from start of execution of query > > The view should contains all kind of running queries from RunningQueryManager > on local node -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11259) Web console: Actualize grid configurator BinaryTypeConfiguration
Vasiliy Sisko created IGNITE-11259: -- Summary: Web console: Actualize grid configurator BinaryTypeConfiguration Key: IGNITE-11259 URL: https://issues.apache.org/jira/browse/IGNITE-11259 Project: Ignite Issue Type: Improvement Components: wizards Reporter: Vasiliy Sisko Assignee: Vasiliy Sisko Result for class: org.apache.ignite.binary.BinaryTypeConfiguration Missed enumValues -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10347) Expose system SQL view for running queries
[ https://issues.apache.org/jira/browse/IGNITE-10347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-10347: - Component/s: sql > Expose system SQL view for running queries > -- > > Key: IGNITE-10347 > URL: https://issues.apache.org/jira/browse/IGNITE-10347 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Yury Gerzhedovich >Assignee: Yury Gerzhedovich >Priority: Major > Labels: iep-29, sql > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > Need to expose system SQL view to provide list of running queries. Proposed > name is *running_queries* with following columns: query_id, node_id, sql, > schema_name, duration. > Where, > query_id - cluster unique id of query > sql - sql command > cancelable - is is possible to cancel the query. > schema_name - SQL schema name > duration - time in ms from start of execution of query > > The view should contains all kind of running queries from RunningQueryManager > on local node -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10347) Expose system SQL view for running queries
[ https://issues.apache.org/jira/browse/IGNITE-10347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-10347: - Labels: iep-29 (was: iep-29 sql) > Expose system SQL view for running queries > -- > > Key: IGNITE-10347 > URL: https://issues.apache.org/jira/browse/IGNITE-10347 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Yury Gerzhedovich >Assignee: Yury Gerzhedovich >Priority: Major > Labels: iep-29 > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > Need to expose system SQL view to provide list of running queries. Proposed > name is *running_queries* with following columns: query_id, node_id, sql, > schema_name, duration. > Where, > query_id - cluster unique id of query > sql - sql command > cancelable - is is possible to cancel the query. > schema_name - SQL schema name > duration - time in ms from start of execution of query > > The view should contains all kind of running queries from RunningQueryManager > on local node -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11260) Document new system view for running queries
Yury Gerzhedovich created IGNITE-11260: -- Summary: Document new system view for running queries Key: IGNITE-11260 URL: https://issues.apache.org/jira/browse/IGNITE-11260 Project: Ignite Issue Type: Task Components: documentation, sql Reporter: Yury Gerzhedovich Assignee: Artem Budnikov Fix For: 2.8 We need to document new SQL system views with running queries - LOCAL_SQL_RUNNING_QUERIES. see org.apache.ignite.internal.processors.query.h2.sys.view.SqlSystemViewRunningQueries -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11260) Document new system view for running queries
[ https://issues.apache.org/jira/browse/IGNITE-11260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-11260: - Ignite Flags: (was: Docs Required) > Document new system view for running queries > > > Key: IGNITE-11260 > URL: https://issues.apache.org/jira/browse/IGNITE-11260 > Project: Ignite > Issue Type: Task > Components: documentation, sql >Reporter: Yury Gerzhedovich >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.8 > > > We need to document new SQL system views with running queries - > LOCAL_SQL_RUNNING_QUERIES. > see > org.apache.ignite.internal.processors.query.h2.sys.view.SqlSystemViewRunningQueries -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11147) Dynamic cache start during rebalance leads to start rebalance for all cache groups in case of IGNITE_DISABLE_WAL_DURING_REBALANCING = true
[ https://issues.apache.org/jira/browse/IGNITE-11147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Daschinskiy reassigned IGNITE-11147: - Assignee: Ivan Daschinskiy > Dynamic cache start during rebalance leads to start rebalance for all cache > groups in case of IGNITE_DISABLE_WAL_DURING_REBALANCING = true > -- > > Key: IGNITE-11147 > URL: https://issues.apache.org/jira/browse/IGNITE-11147 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.7 >Reporter: Sergey Antonov >Assignee: Ivan Daschinskiy >Priority: Blocker > Fix For: 2.8 > > > Scenario: > 1) Start cluster with PDS and option (IGNITE_DISABLE_WAL_DURING_REBALANCING = > true). Activate cluster and start few dinymic caches. > 2) Stop one node and clean its PDS. > 3) Start the node again. It's come back to the cluster. Rebalance started. > 4) During rebalance start some caches (part of them should be already started > on nodes). > Expected: > Rebalance will be started only for new caches. For other nodes rebalance > willn't canceled. > Actual: > Rebalance wiil be canceled and starts again for all cache groups (including > rebalanced yet) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11209) SQL: Merge DmlStatementsProcessor into IgniteH2Indexing
[
https://issues.apache.org/jira/browse/IGNITE-11209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763461#comment-16763461
]
Ignite TC Bot commented on IGNITE-11209:
{panel:title=--> Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache (Restarts) 1{color} [[tests
12|https://ci.ignite.apache.org/viewLog.html?buildId=3018997]]
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithPutTwoNodesOneBackup -
0,0% fails in last 382 master runs.
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithPutFourNodesNoBackups -
0,0% fails in last 382 master runs.
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithTxFourNodesOneBackups -
0,0% fails in last 382 master runs.
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithPutTwoNodesNoBackups -
0,0% fails in last 382 master runs.
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithTxTwoNodesOneBackup -
0,0% fails in last 382 master runs.
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3019052&buildTypeId=IgniteTests24Java8_RunAll]
> SQL: Merge DmlStatementsProcessor into IgniteH2Indexing
> ---
>
> Key: IGNITE-11209
> URL: https://issues.apache.org/jira/browse/IGNITE-11209
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Major
> Fix For: 2.8
>
>
> Reasoning:
> # Too complex method interaction
> # Code duplication
> # Dead code
> # Will allow for further more intellectual refactoring in IGNITE-11227
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11255) Fix test failure after IGNITE-7648
[ https://issues.apache.org/jira/browse/IGNITE-11255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Voronkin updated IGNITE-11255: Labels: MakeTeamcityGreenAgain (was: ) > Fix test failure after IGNITE-7648 > -- > > Key: IGNITE-11255 > URL: https://issues.apache.org/jira/browse/IGNITE-11255 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Voronkin >Priority: Major > Labels: MakeTeamcityGreenAgain > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11233) Ignite Build for Java 11 does not reuse ignite-tools from Build Apache Ignite for some configurations, Compilation error
[
https://issues.apache.org/jira/browse/IGNITE-11233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Ivanov reassigned IGNITE-11233:
-
Assignee: Peter Ivanov
> Ignite Build for Java 11 does not reuse ignite-tools from Build Apache Ignite
> for some configurations, Compilation error
>
>
> Key: IGNITE-11233
> URL: https://issues.apache.org/jira/browse/IGNITE-11233
> Project: Ignite
> Issue Type: Bug
>Reporter: Dmitriy Pavlov
>Assignee: Peter Ivanov
>Priority: Critical
>
> _Javadoc_ [ tests 0 Exit Code , Compilation Error ]
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Javadoc&branch=ignite-11213&tab=buildTypeStatusDiv
> SPI (URI Deploy) [ tests 0 Exit Code , Compilation Error ]
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_SpiUriDeploy&branch=ignite-11213&tab=buildTypeStatusDiv
> RDD* [ tests 0 Exit Code , Compilation Error ]
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Rdd&branch=ignite-11213&tab=buildTypeStatusDiv
> JCache TCK 1.1 [ tests 0 Exit Code , Compilation Error ]
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_JCacheTck11&branch=ignite-11213&tab=buildTypeStatusDiv
> Platform .NET (NuGet)* [ tests 0 Exit Code ]
> https://ci.ignite.apache.org/viewLog.html?tab=buildLog&logTab=tree&filter=debug&expand=all&buildId=3007897&_focus=904
> {noformat}
> [21:28:31][Step 1/1] [INFO] Compiling 9 source files to
> /data/teamcity/work/9198da4c51c3e112/modules/tools/target/classes
> [21:28:32][Step 1/1] [INFO]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:
>
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java
> uses or overrides a deprecated API that is marked for removal.
> [21:28:32][Step 1/1] [INFO]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:
> Recompile with -Xlint:removal for details.
> [21:28:32][Step 1/1] [INFO]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/classgen/ClassesGenerator.java:
>
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/classgen/ClassesGenerator.java
> uses unchecked or unsafe operations.
> [21:28:32][Step 1/1] [INFO]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/classgen/ClassesGenerator.java:
> Recompile with -Xlint:unchecked for details.
> [21:28:32][Step 1/1] [INFO]
> -
> [21:28:32][Step 1/1] [ERROR] COMPILATION ERROR :
> [21:28:32][Step 1/1] [INFO]
> -
> [21:28:32][Step 1/1] [ERROR]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:[21,29]
> package com.sun.tools.doclets does not exist
> [21:28:32][Step 1/1] [ERROR]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:[30,42]
> cannot find symbol
> [21:28:32][Step 1/1] symbol: class Taglet
> [21:28:32][Step 1/1] [ERROR]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:[37,5]
> method does not override or implement a method from a supertype
> [21:28:32][Step 1/1] [ERROR]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:[44,5]
> method does not override or implement a method from a supertype
> [21:28:32][Step 1/1] [ERROR]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:[51,5]
> method does not override or implement a method from a supertype
> [21:28:32][Step 1/1] [ERROR]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:[58,5]
> method does not override or implement a method from a supertype
> [21:28:32][Step 1/1] [ERROR]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:[65,5]
> method does not override or implement a method from a supertype
> [21:28:32][Step 1/1] [ERROR]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:[72,5]
> method does not override or implement a method from a supertype
> [21:28:32][Step 1/1] [ERROR]
> /data/teamcity/work/9198da4c51c3e112/modu
[jira] [Commented] (IGNITE-11209) SQL: Merge DmlStatementsProcessor into IgniteH2Indexing
[ https://issues.apache.org/jira/browse/IGNITE-11209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763465#comment-16763465 ] Vladimir Ozerov commented on IGNITE-11209: -- Failures are unrelated. > SQL: Merge DmlStatementsProcessor into IgniteH2Indexing > --- > > Key: IGNITE-11209 > URL: https://issues.apache.org/jira/browse/IGNITE-11209 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > Reasoning: > # Too complex method interaction > # Code duplication > # Dead code > # Will allow for further more intellectual refactoring in IGNITE-11227 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11255) Fix test failure after IGNITE-7648
[ https://issues.apache.org/jira/browse/IGNITE-11255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763481#comment-16763481 ] Dmitriy Pavlov commented on IGNITE-11255: - [~voropava], Please fill ticket description, you may provide a reference to TC runs with failures, stack traces, any other details, which will help to find or fix the issue. > Fix test failure after IGNITE-7648 > -- > > Key: IGNITE-11255 > URL: https://issues.apache.org/jira/browse/IGNITE-11255 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Voronkin >Priority: Major > Labels: MakeTeamcityGreenAgain > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11233) Ignite Build for Java 11 does not reuse ignite-tools from Build Apache Ignite for some configurations, Compilation error
[
https://issues.apache.org/jira/browse/IGNITE-11233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763490#comment-16763490
]
Peter Ivanov commented on IGNITE-11233:
---
#
_[Javadoc|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Javadoc&branch_IgniteTests24Java8=ignite-11213]_
(/) This task requires full compilation: forced JDK 8
(https://ci.ignite.apache.org/viewLog.html?buildId=3036542).
# _[SPI (URI
Deploy)|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_SpiUriDeploy&branch_IgniteTests24Java8=ignite-11213]_
(/) Some strange build step with "precompilation" existed: turned off
(https://ci.ignite.apache.org/viewLog.html?buildId=3036506)
#
_[RDD|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Rdd&branch_IgniteTests24Java8=ignite-11213]_
(x) This suite was setup to run {{test}} instead of {{surefire:test}} goal:
reconfigured.
ERROR: [java.lang.NoClassDefFoundError:
scala/Product$class|https://www.google.com/search?client=safari&rls=en&q=java.lang.NoClassDefFoundError:+scala/Product$class&ie=UTF-8&oe=UTF-8]
# _[JCache TCK
1.1|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_JCacheTck11&branch_IgniteTests24Java8=ignite-11213]_
(/) This suite was setup to run {{test}} instead of {{surefire:test}} goal:
reconfigured (https://ci.ignite.apache.org/viewLog.html?buildId=3036528)
# _[Platform .NET
(NuGet)*|https://ci.ignite.apache.org/admin/editProject.html?init=1&projectId=IgniteTests24Java8&branch_IgniteTests24Java8=ignite-11213]_
(!) One of build's step requires project compilation. [~ptupitsyn] advise is
needed on how to run {{build.ps1}} script to omit rebuild of project's java
part.
> Ignite Build for Java 11 does not reuse ignite-tools from Build Apache Ignite
> for some configurations, Compilation error
>
>
> Key: IGNITE-11233
> URL: https://issues.apache.org/jira/browse/IGNITE-11233
> Project: Ignite
> Issue Type: Bug
>Reporter: Dmitriy Pavlov
>Assignee: Peter Ivanov
>Priority: Critical
>
> _Javadoc_ [ tests 0 Exit Code , Compilation Error ]
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Javadoc&branch=ignite-11213&tab=buildTypeStatusDiv
> SPI (URI Deploy) [ tests 0 Exit Code , Compilation Error ]
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_SpiUriDeploy&branch=ignite-11213&tab=buildTypeStatusDiv
> RDD* [ tests 0 Exit Code , Compilation Error ]
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Rdd&branch=ignite-11213&tab=buildTypeStatusDiv
> JCache TCK 1.1 [ tests 0 Exit Code , Compilation Error ]
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_JCacheTck11&branch=ignite-11213&tab=buildTypeStatusDiv
> Platform .NET (NuGet)* [ tests 0 Exit Code ]
> https://ci.ignite.apache.org/viewLog.html?tab=buildLog&logTab=tree&filter=debug&expand=all&buildId=3007897&_focus=904
> {noformat}
> [21:28:31][Step 1/1] [INFO] Compiling 9 source files to
> /data/teamcity/work/9198da4c51c3e112/modules/tools/target/classes
> [21:28:32][Step 1/1] [INFO]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:
>
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java
> uses or overrides a deprecated API that is marked for removal.
> [21:28:32][Step 1/1] [INFO]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:
> Recompile with -Xlint:removal for details.
> [21:28:32][Step 1/1] [INFO]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/classgen/ClassesGenerator.java:
>
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/classgen/ClassesGenerator.java
> uses unchecked or unsafe operations.
> [21:28:32][Step 1/1] [INFO]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/classgen/ClassesGenerator.java:
> Recompile with -Xlint:unchecked for details.
> [21:28:32][Step 1/1] [INFO]
> -
> [21:28:32][Step 1/1] [ERROR] COMPILATION ERROR :
> [21:28:32][Step 1/1] [INFO]
> -
> [21:28:32][Step 1/1] [ERROR]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:[21,29]
> package com.sun.tools.doclets does not exist
> [21:28:32][Step 1/1] [ERROR]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/m
[jira] [Created] (IGNITE-11261) [ML] Flaky test(testNaiveBaggingLogRegression)
Yury Babak created IGNITE-11261: --- Summary: [ML] Flaky test(testNaiveBaggingLogRegression) Key: IGNITE-11261 URL: https://issues.apache.org/jira/browse/IGNITE-11261 Project: Ignite Issue Type: Bug Components: ml Reporter: Yury Babak Assignee: Artem Malykh -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-11233) Ignite Build for Java 11 does not reuse ignite-tools from Build Apache Ignite for some configurations, Compilation error
[
https://issues.apache.org/jira/browse/IGNITE-11233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763490#comment-16763490
]
Peter Ivanov edited comment on IGNITE-11233 at 2/8/19 10:51 AM:
#
_[Javadoc|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Javadoc&branch_IgniteTests24Java8=ignite-11213]_
(/) This task requires full compilation: forced JDK 8
([https://ci.ignite.apache.org/viewLog.html?buildId=3036542]).
# _[SPI (URI
Deploy)|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_SpiUriDeploy&branch_IgniteTests24Java8=ignite-11213]_
(/) Some strange build step with "precompilation" existed: turned off
([https://ci.ignite.apache.org/viewLog.html?buildId=3036506])
#
_[RDD|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Rdd&branch_IgniteTests24Java8=ignite-11213]_
(x) This suite was setup to run {{test}} instead of {{surefire:test}} goal:
reconfigured.
ERROR: [java.lang.NoClassDefFoundError:
scala/Product$class|https://www.google.com/search?client=safari&rls=en&q=java.lang.NoClassDefFoundError:+scala/Product$class&ie=UTF-8&oe=UTF-8]
# _[JCache TCK
1.1|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_JCacheTck11&branch_IgniteTests24Java8=ignite-11213]_
(/) This suite was setup to run {{test}} instead of {{surefire:test}} goal:
reconfigured ([https://ci.ignite.apache.org/viewLog.html?buildId=3036528])
# _[Platform .NET
(NuGet)*|https://ci.ignite.apache.org/admin/editProject.html?init=1&projectId=IgniteTests24Java8&branch_IgniteTests24Java8=ignite-11213]_
(!) One of build's step requires project compilation. [~ptupitsyn] advice is
needed on how to run {{build.ps1}} script to omit rebuild of project's java
part.
was (Author: vveider):
#
_[Javadoc|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Javadoc&branch_IgniteTests24Java8=ignite-11213]_
(/) This task requires full compilation: forced JDK 8
(https://ci.ignite.apache.org/viewLog.html?buildId=3036542).
# _[SPI (URI
Deploy)|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_SpiUriDeploy&branch_IgniteTests24Java8=ignite-11213]_
(/) Some strange build step with "precompilation" existed: turned off
(https://ci.ignite.apache.org/viewLog.html?buildId=3036506)
#
_[RDD|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Rdd&branch_IgniteTests24Java8=ignite-11213]_
(x) This suite was setup to run {{test}} instead of {{surefire:test}} goal:
reconfigured.
ERROR: [java.lang.NoClassDefFoundError:
scala/Product$class|https://www.google.com/search?client=safari&rls=en&q=java.lang.NoClassDefFoundError:+scala/Product$class&ie=UTF-8&oe=UTF-8]
# _[JCache TCK
1.1|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_JCacheTck11&branch_IgniteTests24Java8=ignite-11213]_
(/) This suite was setup to run {{test}} instead of {{surefire:test}} goal:
reconfigured (https://ci.ignite.apache.org/viewLog.html?buildId=3036528)
# _[Platform .NET
(NuGet)*|https://ci.ignite.apache.org/admin/editProject.html?init=1&projectId=IgniteTests24Java8&branch_IgniteTests24Java8=ignite-11213]_
(!) One of build's step requires project compilation. [~ptupitsyn] advise is
needed on how to run {{build.ps1}} script to omit rebuild of project's java
part.
> Ignite Build for Java 11 does not reuse ignite-tools from Build Apache Ignite
> for some configurations, Compilation error
>
>
> Key: IGNITE-11233
> URL: https://issues.apache.org/jira/browse/IGNITE-11233
> Project: Ignite
> Issue Type: Bug
>Reporter: Dmitriy Pavlov
>Assignee: Peter Ivanov
>Priority: Critical
>
> _Javadoc_ [ tests 0 Exit Code , Compilation Error ]
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Javadoc&branch=ignite-11213&tab=buildTypeStatusDiv
> SPI (URI Deploy) [ tests 0 Exit Code , Compilation Error ]
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_SpiUriDeploy&branch=ignite-11213&tab=buildTypeStatusDiv
> RDD* [ tests 0 Exit Code , Compilation Error ]
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Rdd&branch=ignite-11213&tab=buildTypeStatusDiv
> JCache TCK 1.1 [ tests 0 Exit Code , Compilation Error ]
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_JCacheTck11&branch=ignite-11213&tab=buildTypeStatusDiv
> Platform .NET (NuGet)* [ tests 0 Exit Code ]
> https://ci.ignite.apache.org/viewLog.html?tab=buildLog&logTab=tree&filter=debug&expand=all&buildId=3007897&_focus=904
> {noformat}
> [21:28:31][Step 1/1] [INFO] Compiling 9 source files to
> /data/teamcity/work/9198da4c51
[jira] [Assigned] (IGNITE-11239) SPI and JDBC driver tests failed because of SSL connection timeout for Java 11
[ https://issues.apache.org/jira/browse/IGNITE-11239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov reassigned IGNITE-11239: - Assignee: Peter Ivanov > SPI and JDBC driver tests failed because of SSL connection timeout for Java 11 > -- > > Key: IGNITE-11239 > URL: https://issues.apache.org/jira/browse/IGNITE-11239 > Project: Ignite > Issue Type: Task >Reporter: Dmitriy Pavlov >Assignee: Peter Ivanov >Priority: Major > > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Spi&branch=ignite-11155&tab=buildTypeStatusDiv > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_JdbcDriver&branch=ignite-11155&tab=buildTypeStatusDiv > Probably we should update Java versions installed on TC agents to avoid some > EA-Java-related bugs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11253) When a node that is not part of the base topology joins the cluster, it may lead to a node failure.
[
https://issues.apache.org/jira/browse/IGNITE-11253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763502#comment-16763502
]
Ignite TC Bot commented on IGNITE-11253:
{panel:title=--> Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 7{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=3036071]]
* IgniteCacheTestSuite7:
TxRollbackAsyncWithPersistenceTest.testSynchronousRollback - 0,0% fails in last
397 master runs.
{color:#d04437}Data Structures{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=3036077]]
* IgniteCacheDataStructuresSelfTestSuite:
IgniteCacheAtomicReplicatedNodeRestartSelfTest.testRestartWithPutSixNodesTwoBackups
- 0,0% fails in last 404 master runs.
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3036117&buildTypeId=IgniteTests24Java8_RunAll]
> When a node that is not part of the base topology joins the cluster, it may
> lead to a node failure.
> ---
>
> Key: IGNITE-11253
> URL: https://issues.apache.org/jira/browse/IGNITE-11253
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Vyacheslav Koptilin
>Assignee: Vyacheslav Koptilin
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> * In case of eager TTL is configured, a starting node creates and starts
> {{cleanupWorker}} (see {{GridCacheTtlManager.start0()}})
> * {{GridCacheSharedTtlCleanupManager.CleanupWorker}}, in its turn, has to
> wait for {{discovery().localJoin()}} future that is completed by discovery
> thread.
> * On the other hand, the exchange thread stops cache contexts and,
> therefore, it stops the {{cleanupWorker}} as well.
>
> {code:java}
> org.apache.ignite.internal.processors.cache.GridCacheSharedTtlCleanupManager.stopCleanupWorker(GridCacheSharedTtlCleanupManager.java:109)
> org.apache.ignite.internal.processors.cache.GridCacheSharedTtlCleanupManager.unregister(GridCacheSharedTtlCleanupManager.java:82)
> org.apache.ignite.internal.processors.cache.GridCacheTtlManager.onKernalStop0(GridCacheTtlManager.java:110)
> org.apache.ignite.internal.processors.cache.GridCacheManagerAdapter.onKernalStop(GridCacheManagerAdapter.java:111)
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStop(GridCacheProcessor.java:1495)
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStopCaches(GridCacheProcessor.java:1182)
> org.apache.ignite.internal.processors.cache.GridCacheProcessor$CacheRecoveryLifecycle.onBaselineChange(GridCacheProcessor.java:5637)
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.initCachesOnLocalJoin(GridDhtPartitionsExchangeFuture.java:910)
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:792)
> {code}
> So, exchange thread may try to stop the {{cleanupWorker}} before the
> {{localJoin}} future is completed by discovery thread. Unfortunately,
> `cleanupWorker` incorrectly handles this situation, and this fact can lead to
> a node failure:
> {code:java}
> Critical system error detected. Will be handled accordingly to configured
> handler [hnd=StopNodeFailureHandler [super=AbstractFailureHandler
> [ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED,
> SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext
> [type=SYSTEM_WORKER_TERMINATION, err=class o.a.i.IgniteException: Got
> interrupted while waiting for future to complete.]]
> class org.apache.ignite.IgniteException: Got interrupted while waiting for
> future to complete.
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.localJoin(GridDiscoveryManager.java:2217)
> at
> org.apache.ignite.internal.processors.cache.GridCacheSharedTtlCleanupManager$CleanupWorker.body(GridCacheSharedTtlCleanupManager.java:136)
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class
> org.apache.ignite.internal.IgniteInterruptedCheckedException: Got interrupted
> while waiting for future to complete.
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:186)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:141)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.localJoin(GridDiscoveryManager.java:2214)
> ... 3 more
> {code}
> The obvious fix is changing the catch block
> {code:java}
> catch (Throwable t) {
> if (!(t instanceof IgniteInterruptedCheckedE
[jira] [Updated] (IGNITE-11255) Fix test failure after IGNITE-7648
[ https://issues.apache.org/jira/browse/IGNITE-11255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Voronkin updated IGNITE-11255: Description: We need to fix: * CacheQueriesRestartServerTest.Test_ScanQueryAfterClientReconnect_ReturnsResults(False) * ZookeeperDiscoveryClientDisconnectTest.testReconnectServersRestart_3 * IgniteTwoRegionsRebuildIndexTest.testRebuildIndexes > Fix test failure after IGNITE-7648 > -- > > Key: IGNITE-11255 > URL: https://issues.apache.org/jira/browse/IGNITE-11255 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Voronkin >Priority: Major > Labels: MakeTeamcityGreenAgain > Time Spent: 10m > Remaining Estimate: 0h > > We need to fix: > > * > CacheQueriesRestartServerTest.Test_ScanQueryAfterClientReconnect_ReturnsResults(False) > * ZookeeperDiscoveryClientDisconnectTest.testReconnectServersRestart_3 > * IgniteTwoRegionsRebuildIndexTest.testRebuildIndexes > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11255) Fix test failure after IGNITE-7648
[ https://issues.apache.org/jira/browse/IGNITE-11255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Voronkin reassigned IGNITE-11255: --- Assignee: Pavel Voronkin > Fix test failure after IGNITE-7648 > -- > > Key: IGNITE-11255 > URL: https://issues.apache.org/jira/browse/IGNITE-11255 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Voronkin >Assignee: Pavel Voronkin >Priority: Major > Labels: MakeTeamcityGreenAgain > Time Spent: 10m > Remaining Estimate: 0h > > We need to fix: > > * > CacheQueriesRestartServerTest.Test_ScanQueryAfterClientReconnect_ReturnsResults(False) > * ZookeeperDiscoveryClientDisconnectTest.testReconnectServersRestart_3 > * IgniteTwoRegionsRebuildIndexTest.testRebuildIndexes > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11255) Fix test failure after IGNITE-7648.
[ https://issues.apache.org/jira/browse/IGNITE-11255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Voronkin updated IGNITE-11255: Summary: Fix test failure after IGNITE-7648. (was: Fix test failure after IGNITE-7648) > Fix test failure after IGNITE-7648. > --- > > Key: IGNITE-11255 > URL: https://issues.apache.org/jira/browse/IGNITE-11255 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Voronkin >Assignee: Pavel Voronkin >Priority: Major > Labels: MakeTeamcityGreenAgain > Time Spent: 10m > Remaining Estimate: 0h > > We need to fix: > > * > CacheQueriesRestartServerTest.Test_ScanQueryAfterClientReconnect_ReturnsResults(False) > * ZookeeperDiscoveryClientDisconnectTest.testReconnectServersRestart_3 > * IgniteTwoRegionsRebuildIndexTest.testRebuildIndexes > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11255) Fix test failures after IGNITE-7648.
[ https://issues.apache.org/jira/browse/IGNITE-11255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Voronkin updated IGNITE-11255: Summary: Fix test failures after IGNITE-7648. (was: Fix test failure after IGNITE-7648.) > Fix test failures after IGNITE-7648. > > > Key: IGNITE-11255 > URL: https://issues.apache.org/jira/browse/IGNITE-11255 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Voronkin >Assignee: Pavel Voronkin >Priority: Major > Labels: MakeTeamcityGreenAgain > Time Spent: 10m > Remaining Estimate: 0h > > We need to fix: > > * > CacheQueriesRestartServerTest.Test_ScanQueryAfterClientReconnect_ReturnsResults(False) > * ZookeeperDiscoveryClientDisconnectTest.testReconnectServersRestart_3 > * IgniteTwoRegionsRebuildIndexTest.testRebuildIndexes > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11262) Compression on Discovery data bag
Vladislav Pyatkov created IGNITE-11262:
--
Summary: Compression on Discovery data bag
Key: IGNITE-11262
URL: https://issues.apache.org/jira/browse/IGNITE-11262
Project: Ignite
Issue Type: Improvement
Reporter: Vladislav Pyatkov
Size of GridComponetns data may increase significantly in large deployment.
Examples:
1) In case of more then 3K caches with QueryEntry configured - size of
{{DiscoveryDataBag}}{{GridCacheProcessor}} data bag consume more then 20 Mb
2) If cluster contain more then 13K objects -
{{GridMarshallerMappingProcessor}} size more then 1 Mb
3) Cluster with more then 3К types in binary format -
{{CacheObjectBinaryProcessorImpl}} size can grow to 10Mb
The data in most cases contain duplicated structure and simple zip compression
can led to seriously reduce size.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-11262) Compression on Discovery data bag
[
https://issues.apache.org/jira/browse/IGNITE-11262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladislav Pyatkov reassigned IGNITE-11262:
--
Assignee: Vladislav Pyatkov
> Compression on Discovery data bag
> -
>
> Key: IGNITE-11262
> URL: https://issues.apache.org/jira/browse/IGNITE-11262
> Project: Ignite
> Issue Type: Improvement
>Reporter: Vladislav Pyatkov
>Assignee: Vladislav Pyatkov
>Priority: Major
>
> Size of GridComponetns data may increase significantly in large deployment.
> Examples:
> 1) In case of more then 3K caches with QueryEntry configured - size of
> {{DiscoveryDataBag}}{{GridCacheProcessor}} data bag consume more then 20 Mb
> 2) If cluster contain more then 13K objects -
> {{GridMarshallerMappingProcessor}} size more then 1 Mb
> 3) Cluster with more then 3К types in binary format -
> {{CacheObjectBinaryProcessorImpl}} size can grow to 10Mb
> The data in most cases contain duplicated structure and simple zip
> compression can led to seriously reduce size.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11263) If host in TcpDiscoveryVmIpFinder is unreachable - server hang on start
ARomantsov created IGNITE-11263:
---
Summary: If host in TcpDiscoveryVmIpFinder is unreachable - server
hang on start
Key: IGNITE-11263
URL: https://issues.apache.org/jira/browse/IGNITE-11263
Project: Ignite
Issue Type: Bug
Affects Versions: 2.5
Reporter: ARomantsov
Fix For: 2.8
If one of servers in discovery ipFinder is unreachable - server hang on start
repeat locally with commands
sudo iptables -A INPUT DROP
sudo iptables -A OUTPUT DROP
{code:java}
{code}
Server logs end with
{code:java}
[14:39:44,668][INFO][main][GridCacheDatabaseSharedManager] Read checkpoint
status [startMarker=null, endMarker=null]
[14:39:44,669][INFO][main][GridCacheDatabaseSharedManager] Applying lost cache
updates since last checkpoint record [lastMarked=FileWALPointer [idx=0,
fileOff=0, len=0], lastCheckpointId=----]
[14:39:44,700][INFO][main][GridCacheDatabaseSharedManager] Finished applying
WAL changes [updatesApplied=0, time=30 ms]
[14:39:44,700][INFO][main][GridCacheDatabaseSharedManager] Restoring partition
state for local groups.
[14:39:44,705][INFO][main][GridCacheDatabaseSharedManager] Finished restoring
partition state for local groups [groupsProcessed11partitionsProcessed=0,
time=10ms]
[14:39:45,252][INFO][main][TcpDiscoverySpi] Successfully bound to TCP port
[port=47500, localHost=0.0.0.0/0.0.0.0,
locNodeId=6621cfd7-26a8-4bc0-a80a-88c6281aa118]
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-10455) MVCC: Tx timeout can cause update counters inconsistency.
[
https://issues.apache.org/jira/browse/IGNITE-10455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16759710#comment-16759710
]
Ivan Pavlukhin edited comment on IGNITE-10455 at 2/8/19 11:54 AM:
--
After fixing the problem with active txs leak (linked ticket 8841) the test
reproduces an issue with inconsistent partition sizes when some MOVING
partitions are processed. Should be double checked after fixing broken sizes
(linked ticket 10082).
was (Author: pavlukhin):
After fixing the problem with active txs leak (linked ticket 8841) the test
reproduces an issue with inconsistent partition sizes when some MOVING
partitions are processed. Should be double checked after fixing broken sizes
(linked ticket 10082).
> MVCC: Tx timeout can cause update counters inconsistency.
> --
>
> Key: IGNITE-10455
> URL: https://issues.apache.org/jira/browse/IGNITE-10455
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Priority: Major
> Labels: mvcc_stabilization_stage_1, transactions
> Fix For: 2.8
>
>
> When transaction is rolled back on backup on prepare step, it could lead to
> update counters inconsistency between primary and backup. We need to fix
> backup counters update.
> Reproducer: {{TxWithSmallTimeoutAndContentionOneKeyTest#test}} with enabled
> MVCC.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-11263) If host in TcpDiscoveryVmIpFinder is unreachable - server hang on start
[
https://issues.apache.org/jira/browse/IGNITE-11263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ARomantsov resolved IGNITE-11263.
-
Resolution: Invalid
> If host in TcpDiscoveryVmIpFinder is unreachable - server hang on start
> ---
>
> Key: IGNITE-11263
> URL: https://issues.apache.org/jira/browse/IGNITE-11263
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: ARomantsov
>Priority: Major
> Fix For: 2.8
>
>
> If one of servers in discovery ipFinder is unreachable - server hang on start
> repeat locally with commands
> sudo iptables -A INPUT DROP
> sudo iptables -A OUTPUT DROP
> {code:java}
>
>
>
>
>
>
>
>
>
>
> class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
>
>
> {code}
> Server logs end with
> {code:java}
> [14:39:44,668][INFO][main][GridCacheDatabaseSharedManager] Read checkpoint
> status [startMarker=null, endMarker=null]
> [14:39:44,669][INFO][main][GridCacheDatabaseSharedManager] Applying lost
> cache updates since last checkpoint record [lastMarked=FileWALPointer [idx=0,
> fileOff=0, len=0], lastCheckpointId=----]
> [14:39:44,700][INFO][main][GridCacheDatabaseSharedManager] Finished applying
> WAL changes [updatesApplied=0, time=30 ms]
> [14:39:44,700][INFO][main][GridCacheDatabaseSharedManager] Restoring
> partition state for local groups.
> [14:39:44,705][INFO][main][GridCacheDatabaseSharedManager] Finished restoring
> partition state for local groups [groupsProcessed11partitionsProcessed=0,
> time=10ms]
> [14:39:45,252][INFO][main][TcpDiscoverySpi] Successfully bound to TCP port
> [port=47500, localHost=0.0.0.0/0.0.0.0,
> locNodeId=6621cfd7-26a8-4bc0-a80a-88c6281aa118]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11263) If host in TcpDiscoveryVmIpFinder is unreachable - server hang on start
[
https://issues.apache.org/jira/browse/IGNITE-11263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763524#comment-16763524
]
ARomantsov commented on IGNITE-11263:
-
Finally it start
[14:39:45,252][INFO][main][TcpDiscoverySpi] Successfully bound to TCP port
[port=47500, localHost=0.0.0.0/0.0.0.0,
locNodeId=6621cfd7-26a8-4bc0-a80a-88c6281aa118]
[14:50:45,910][WARNING][snapshot-scheduler-restats-#67][SnapshotScheduleProcessor]
Snapshot schedule processor awaits for cluster activation.
> If host in TcpDiscoveryVmIpFinder is unreachable - server hang on start
> ---
>
> Key: IGNITE-11263
> URL: https://issues.apache.org/jira/browse/IGNITE-11263
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: ARomantsov
>Priority: Major
> Fix For: 2.8
>
>
> If one of servers in discovery ipFinder is unreachable - server hang on start
> repeat locally with commands
> sudo iptables -A INPUT DROP
> sudo iptables -A OUTPUT DROP
> {code:java}
>
>
>
>
>
>
>
>
>
>
> class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
>
>
> {code}
> Server logs end with
> {code:java}
> [14:39:44,668][INFO][main][GridCacheDatabaseSharedManager] Read checkpoint
> status [startMarker=null, endMarker=null]
> [14:39:44,669][INFO][main][GridCacheDatabaseSharedManager] Applying lost
> cache updates since last checkpoint record [lastMarked=FileWALPointer [idx=0,
> fileOff=0, len=0], lastCheckpointId=----]
> [14:39:44,700][INFO][main][GridCacheDatabaseSharedManager] Finished applying
> WAL changes [updatesApplied=0, time=30 ms]
> [14:39:44,700][INFO][main][GridCacheDatabaseSharedManager] Restoring
> partition state for local groups.
> [14:39:44,705][INFO][main][GridCacheDatabaseSharedManager] Finished restoring
> partition state for local groups [groupsProcessed11partitionsProcessed=0,
> time=10ms]
> [14:39:45,252][INFO][main][TcpDiscoverySpi] Successfully bound to TCP port
> [port=47500, localHost=0.0.0.0/0.0.0.0,
> locNodeId=6621cfd7-26a8-4bc0-a80a-88c6281aa118]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11264) JVM crash in OffheapReadWriteLock#tryWriteLock
[ https://issues.apache.org/jira/browse/IGNITE-11264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Bessonov updated IGNITE-11264: --- Attachment: test_output.txt > JVM crash in OffheapReadWriteLock#tryWriteLock > -- > > Key: IGNITE-11264 > URL: https://issues.apache.org/jira/browse/IGNITE-11264 > Project: Ignite > Issue Type: Bug >Reporter: Ivan Bessonov >Assignee: Eduard Shangareev >Priority: Major > Attachments: hs_err_pid19407.log, test_output.txt > > > JVM crash in the end of > IgniteClusterActivateDeactivateTest#testClientReconnectClusterActivateInProgress. > Test was invoked using "Until Failure" mode in IDEA. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11264) JVM crash in OffheapReadWriteLock#tryWriteLock
Ivan Bessonov created IGNITE-11264: -- Summary: JVM crash in OffheapReadWriteLock#tryWriteLock Key: IGNITE-11264 URL: https://issues.apache.org/jira/browse/IGNITE-11264 Project: Ignite Issue Type: Bug Reporter: Ivan Bessonov Assignee: Eduard Shangareev Attachments: hs_err_pid19407.log JVM crash in the end of IgniteClusterActivateDeactivateTest#testClientReconnectClusterActivateInProgress. Test was invoked using "Until Failure" mode in IDEA. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11264) JVM crash in OffheapReadWriteLock#tryWriteLock
[ https://issues.apache.org/jira/browse/IGNITE-11264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Bessonov updated IGNITE-11264: --- Attachment: hs_err_pid19407.log > JVM crash in OffheapReadWriteLock#tryWriteLock > -- > > Key: IGNITE-11264 > URL: https://issues.apache.org/jira/browse/IGNITE-11264 > Project: Ignite > Issue Type: Bug >Reporter: Ivan Bessonov >Assignee: Eduard Shangareev >Priority: Major > Attachments: hs_err_pid19407.log > > > JVM crash in the end of > IgniteClusterActivateDeactivateTest#testClientReconnectClusterActivateInProgress. > Test was invoked using "Until Failure" mode in IDEA. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11265) JVM Crash is often on TeamCity for Java 11 runs
Dmitriy Pavlov created IGNITE-11265: --- Summary: JVM Crash is often on TeamCity for Java 11 runs Key: IGNITE-11265 URL: https://issues.apache.org/jira/browse/IGNITE-11265 Project: Ignite Issue Type: Bug Reporter: Dmitriy Pavlov All crash dumps complain about the same method org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.writeLock Data Structures (https://ci.ignite.apache.org/viewLog.html?buildId=3007882) https://ci.ignite.apache.org/repository/download/IgniteTests24Java8_DataStructures/3007882:id/hs_err_pid2674225.log Other recent examples Queries 1 https://ci.ignite.apache.org/repository/download/IgniteTests24Java8_Queries1/3027655:id/hs_err_pid2458635.log Client Nodes https://ci.ignite.apache.org/repository/download/IgniteTests24Java8_ClientNodes/3027569:id/hs_err_pid2431080.log Zookeeper Discovery https://ci.ignite.apache.org/repository/download/IgniteTests24Java8_ZooKeeperDiscovery1/3027601:id/hs_err_pid3473289.log -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11247) MVCC: Tests has been forgotten to unmute.
[ https://issues.apache.org/jira/browse/IGNITE-11247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-11247: -- Description: There are muted\ignored tests that are not being run on TC, but tickets for fixing them looks already resolved. Let's recheck those tests and either unmute them or create a new tickets to fix lately if needed. IgniteBasicWithPersistenceTestSuite * testIoomErrorMvccPdsHandling - IGNITE-10185 IgniteCacheMvccSqlTestSuite * testSqlReadInsideTxInProgressCoordinatorFails - IGNITE-8841 * testSqlReadInsideTxInProgressCoordinatorFails_ReadDelay - IGNITE-8841 * testPutAllGetAll_ClientServer_Backups1_SinglePartition_RestartRandomSrv_SqlDml - IGNITE-10752 * testAccountsTxSql_SingleNode_CoordinatorFails_Persistence - IGNITE-10753 was: There are muted\ignored tests that are not being run on TC, but tickets for fixing them looks already resolved. Let's recheck those tests and either unmute them or create a new tickets to fix lately if needed. IgniteCacheMvccSqlTestSuite * testSqlReadInsideTxInProgressCoordinatorFails - IGNITE-8841 * testSqlReadInsideTxInProgressCoordinatorFails_ReadDelay - IGNITE-8841 IgniteBasicWithPersistenceTestSuite * testIoomErrorMvccPdsHandling - IGNITE-10185 IgniteCacheMvccSqlTestSuite * testPutAllGetAll_ClientServer_Backups1_SinglePartition_RestartRandomSrv_SqlDml - IGNITE-10752 * testAccountsTxSql_SingleNode_CoordinatorFails_Persistence - IGNITE-10753 > MVCC: Tests has been forgotten to unmute. > - > > Key: IGNITE-11247 > URL: https://issues.apache.org/jira/browse/IGNITE-11247 > Project: Ignite > Issue Type: Bug > Components: mvcc >Reporter: Andrew Mashenkov >Assignee: Andrew Mashenkov >Priority: Major > Labels: MakeTeamcityGreenAgain, mvcc_stabilization_stage_1 > Time Spent: 10m > Remaining Estimate: 0h > > There are muted\ignored tests that are not being run on TC, but tickets for > fixing them looks already resolved. > Let's recheck those tests and either unmute them or create a new tickets to > fix lately if needed. > IgniteBasicWithPersistenceTestSuite > * testIoomErrorMvccPdsHandling - IGNITE-10185 > IgniteCacheMvccSqlTestSuite > * testSqlReadInsideTxInProgressCoordinatorFails - IGNITE-8841 > * testSqlReadInsideTxInProgressCoordinatorFails_ReadDelay - IGNITE-8841 > * > testPutAllGetAll_ClientServer_Backups1_SinglePartition_RestartRandomSrv_SqlDml > - IGNITE-10752 > * testAccountsTxSql_SingleNode_CoordinatorFails_Persistence - IGNITE-10753 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11216) Ignite.sh fails on Mac OS and Linux - Java 11
[
https://issues.apache.org/jira/browse/IGNITE-11216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11216:
Ignite Flags: (was: Docs Required)
> Ignite.sh fails on Mac OS and Linux - Java 11
> -
>
> Key: IGNITE-11216
> URL: https://issues.apache.org/jira/browse/IGNITE-11216
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.7
>Reporter: Denis Magda
>Assignee: Peter Ivanov
>Priority: Blocker
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Ignite.sh fails on Mac OS Mojave with the following JDK version:
> java version "11.0.2" 2019-01-15 LTS
> Java(TM) SE Runtime Environment 18.9 (build 11.0.2+9-LTS)
> Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.2+9-LTS, mixed mode)
> The same issue is reproduced on Linux and the workaround is discussed here:
> https://issues.apache.org/jira/browse/IGNITE-3
> The exception is as follows:
> {noformat}
> /Users/dmagda/Downloads/apache-ignite-2.7.0-bin/bin/include/functions.sh:
> line 40: [: -eq: unary operator expected
> ./ignite.sh: line 152: [: -eq: unary operator expected
> ./ignite.sh: line 157: [: -gt: unary operator expected
> ./ignite.sh: line 170: [: -eq: unary operator expected
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by
> org.apache.ignite.internal.util.GridUnsafe$2
> (file:/Users/dmagda/Downloads/apache-ignite-2.7.0-bin/libs/ignite-core-2.7.0.jar)
> to field java.nio.Buffer.address
> WARNING: Please consider reporting this to the maintainers of
> org.apache.ignite.internal.util.GridUnsafe$2
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> Exception in thread "main" java.lang.ExceptionInInitializerError
> at
> org.apache.ignite.internal.util.IgniteUtils.(IgniteUtils.java:795)
> at
> org.apache.ignite.lang.IgniteProductVersion.fromString(IgniteProductVersion.java:305)
> at
> org.apache.ignite.internal.IgniteVersionUtils.(IgniteVersionUtils.java:71)
> at
> org.apache.ignite.startup.cmdline.CommandLineStartup.(CommandLineStartup.java:99)
> Caused by: java.lang.RuntimeException: jdk.internal.misc.JavaNioAccess class
> is unavailable.
> at
> org.apache.ignite.internal.util.GridUnsafe.javaNioAccessObject(GridUnsafe.java:1453)
> at
> org.apache.ignite.internal.util.GridUnsafe.(GridUnsafe.java:112)
> ... 4 more
> Caused by: java.lang.IllegalAccessException: class
> org.apache.ignite.internal.util.GridUnsafe cannot access class
> jdk.internal.misc.SharedSecrets (in module java.base) because module
> java.base does not export jdk.internal.misc to unnamed module @4f83df68
> at
> java.base/jdk.internal.reflect.Reflection.newIllegalAccessException(Reflection.java:361)
> at
> java.base/java.lang.reflect.AccessibleObject.checkAccess(AccessibleObject.java:591)
> at java.base/java.lang.reflect.Method.invoke(Method.java:558)
> at
> org.apache.ignite.internal.util.GridUnsafe.javaNioAccessObject(GridUnsafe.java:1450)
> ... 5 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11216) Ignite.sh fails on Mac OS and Linux - Java 11
[
https://issues.apache.org/jira/browse/IGNITE-11216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763554#comment-16763554
]
Dmitriy Pavlov commented on IGNITE-11216:
-
I don't understand how the fix works, so [~ustas], could you please review this
fix?
> Ignite.sh fails on Mac OS and Linux - Java 11
> -
>
> Key: IGNITE-11216
> URL: https://issues.apache.org/jira/browse/IGNITE-11216
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.7
>Reporter: Denis Magda
>Assignee: Peter Ivanov
>Priority: Blocker
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Ignite.sh fails on Mac OS Mojave with the following JDK version:
> java version "11.0.2" 2019-01-15 LTS
> Java(TM) SE Runtime Environment 18.9 (build 11.0.2+9-LTS)
> Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.2+9-LTS, mixed mode)
> The same issue is reproduced on Linux and the workaround is discussed here:
> https://issues.apache.org/jira/browse/IGNITE-3
> The exception is as follows:
> {noformat}
> /Users/dmagda/Downloads/apache-ignite-2.7.0-bin/bin/include/functions.sh:
> line 40: [: -eq: unary operator expected
> ./ignite.sh: line 152: [: -eq: unary operator expected
> ./ignite.sh: line 157: [: -gt: unary operator expected
> ./ignite.sh: line 170: [: -eq: unary operator expected
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by
> org.apache.ignite.internal.util.GridUnsafe$2
> (file:/Users/dmagda/Downloads/apache-ignite-2.7.0-bin/libs/ignite-core-2.7.0.jar)
> to field java.nio.Buffer.address
> WARNING: Please consider reporting this to the maintainers of
> org.apache.ignite.internal.util.GridUnsafe$2
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> Exception in thread "main" java.lang.ExceptionInInitializerError
> at
> org.apache.ignite.internal.util.IgniteUtils.(IgniteUtils.java:795)
> at
> org.apache.ignite.lang.IgniteProductVersion.fromString(IgniteProductVersion.java:305)
> at
> org.apache.ignite.internal.IgniteVersionUtils.(IgniteVersionUtils.java:71)
> at
> org.apache.ignite.startup.cmdline.CommandLineStartup.(CommandLineStartup.java:99)
> Caused by: java.lang.RuntimeException: jdk.internal.misc.JavaNioAccess class
> is unavailable.
> at
> org.apache.ignite.internal.util.GridUnsafe.javaNioAccessObject(GridUnsafe.java:1453)
> at
> org.apache.ignite.internal.util.GridUnsafe.(GridUnsafe.java:112)
> ... 4 more
> Caused by: java.lang.IllegalAccessException: class
> org.apache.ignite.internal.util.GridUnsafe cannot access class
> jdk.internal.misc.SharedSecrets (in module java.base) because module
> java.base does not export jdk.internal.misc to unnamed module @4f83df68
> at
> java.base/jdk.internal.reflect.Reflection.newIllegalAccessException(Reflection.java:361)
> at
> java.base/java.lang.reflect.AccessibleObject.checkAccess(AccessibleObject.java:591)
> at java.base/java.lang.reflect.Method.invoke(Method.java:558)
> at
> org.apache.ignite.internal.util.GridUnsafe.javaNioAccessObject(GridUnsafe.java:1450)
> ... 5 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7648) Fix IGNITE_ENABLE_FORCIBLE_NODE_KILL system property.
[ https://issues.apache.org/jira/browse/IGNITE-7648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763556#comment-16763556 ] Pavel Voronkin commented on IGNITE-7648: We changed behaviour of ENABLED_FORCIBLE_NODE_KILL=true in this ticket. Only server node can kill client node in case if property is enabled. client can't kill server, server can't kill server. Timeout logic changed in case of failure detection enabled scenario We start connect and hanshake from timeout 500ms. If failed we increase timeout using exponential backoff strategy timeout = Math.min(Math.min(timeout * 2, maxTimeout), remainingTiimeTillFailureDetection) > Fix IGNITE_ENABLE_FORCIBLE_NODE_KILL system property. > - > > Key: IGNITE-7648 > URL: https://issues.apache.org/jira/browse/IGNITE-7648 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.3 >Reporter: Alexei Scherbakov >Assignee: Pavel Voronkin >Priority: Major > Fix For: 2.8 > > > IGNITE_ENABLE_FORCIBLE_NODE_KILL system property was introduced in > IGNITE-5718 as a way to prevent unnecessary node drops in case of short > network problems. > I suppose it's wrong decision to fix it in such way. > We had faced some issues in our production due to lack of automatic kicking > of ill-behaving nodes (on example, hanging due to long GC pauses) until we > realised the necessity of changing default behavior via property. > Right solution is to kick nodes only if failure threshold is reached. Such > behavior should be always enabled. > UPDATE: During a discussion it was decided what the property will remain > disabled by default. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11266) Platform .NET test failed with Java 11 warning
Dmitriy Pavlov created IGNITE-11266:
---
Summary: Platform .NET test failed with Java 11 warning
Key: IGNITE-11266
URL: https://issues.apache.org/jira/browse/IGNITE-11266
Project: Ignite
Issue Type: Bug
Reporter: Dmitriy Pavlov
Following warning is unavoidable, because Java always warns about illegal
reflective access (at least for the first time). Probably we can change some
settings to avoid "The active test run was aborted. Reason".
{noformat}
[17:32:56][test] The active test run was aborted. Reason: WARNING: An illegal
reflective access operation has occurred
[17:32:56][test] WARNING: Illegal reflective access by
org.apache.ignite.internal.util.GridUnsafe$2
(file:/data/teamcity/work/9198da4c51c3e112/modules/core/target/classes/) to
field java.nio.Buffer.address
[17:32:56][test] WARNING: Please consider reporting this to the maintainers of
org.apache.ignite.internal.util.GridUnsafe$2
[17:32:56][test] WARNING: Use --illegal-access=warn to enable warnings of
further illegal reflective access operations
[17:32:56][test] WARNING: All illegal access operations will be denied in a
future release
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7648) Fix IGNITE_ENABLE_FORCIBLE_NODE_KILL system property.
[ https://issues.apache.org/jira/browse/IGNITE-7648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763557#comment-16763557 ] Pavel Voronkin commented on IGNITE-7648: We changed behaviour of ENABLED_FORCIBLE_NODE_KILL=true in this ticket. Only server node can kill client node in case if property is enabled. client can't kill server, server can't kill server. Timeout logic changed in case of failure detection enabled scenario We start connect and hanshake from timeout 500ms. If failed we increase timeout using exponential backoff strategy timeout = Math.min(Math.min(timeout * 2, maxTimeout), remainingTiimeTillFailureDetection) > Fix IGNITE_ENABLE_FORCIBLE_NODE_KILL system property. > - > > Key: IGNITE-7648 > URL: https://issues.apache.org/jira/browse/IGNITE-7648 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.3 >Reporter: Alexei Scherbakov >Assignee: Pavel Voronkin >Priority: Major > Fix For: 2.8 > > > IGNITE_ENABLE_FORCIBLE_NODE_KILL system property was introduced in > IGNITE-5718 as a way to prevent unnecessary node drops in case of short > network problems. > I suppose it's wrong decision to fix it in such way. > We had faced some issues in our production due to lack of automatic kicking > of ill-behaving nodes (on example, hanging due to long GC pauses) until we > realised the necessity of changing default behavior via property. > Right solution is to kick nodes only if failure threshold is reached. Such > behavior should be always enabled. > UPDATE: During a discussion it was decided what the property will remain > disabled by default. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-7648) Fix IGNITE_ENABLE_FORCIBLE_NODE_KILL system property.
[ https://issues.apache.org/jira/browse/IGNITE-7648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763556#comment-16763556 ] Pavel Voronkin edited comment on IGNITE-7648 at 2/8/19 12:48 PM: - We changed behaviour of ENABLED_FORCIBLE_NODE_KILL=true in this ticket. Only server node can kill client node in case if property is enabled. client can't kill server, server can't kill server. Timeout logic changed in case of failure detection enabled scenario We start connect and hanshake from timeout 500ms. If failed we increase timeout using exponential backoff strategy timeout = Math.min(Math.min(timeout * 2, maxTimeout), remainingTiimeTillFailureDetection) was (Author: voropava): We changed behaviour of ENABLED_FORCIBLE_NODE_KILL=true in this ticket. Only server node can kill client node in case if property is enabled. client can't kill server, server can't kill server. Timeout logic changed in case of failure detection enabled scenario We start connect and hanshake from timeout 500ms. If failed we increase timeout using exponential backoff strategy timeout = Math.min(Math.min(timeout * 2, maxTimeout), remainingTiimeTillFailureDetection) > Fix IGNITE_ENABLE_FORCIBLE_NODE_KILL system property. > - > > Key: IGNITE-7648 > URL: https://issues.apache.org/jira/browse/IGNITE-7648 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.3 >Reporter: Alexei Scherbakov >Assignee: Pavel Voronkin >Priority: Major > Fix For: 2.8 > > > IGNITE_ENABLE_FORCIBLE_NODE_KILL system property was introduced in > IGNITE-5718 as a way to prevent unnecessary node drops in case of short > network problems. > I suppose it's wrong decision to fix it in such way. > We had faced some issues in our production due to lack of automatic kicking > of ill-behaving nodes (on example, hanging due to long GC pauses) until we > realised the necessity of changing default behavior via property. > Right solution is to kick nodes only if failure threshold is reached. Such > behavior should be always enabled. > UPDATE: During a discussion it was decided what the property will remain > disabled by default. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (IGNITE-7648) Fix IGNITE_ENABLE_FORCIBLE_NODE_KILL system property.
[ https://issues.apache.org/jira/browse/IGNITE-7648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Voronkin updated IGNITE-7648: --- Comment: was deleted (was: We changed behaviour of ENABLED_FORCIBLE_NODE_KILL=true in this ticket. Only server node can kill client node in case if property is enabled. client can't kill server, server can't kill server. Timeout logic changed in case of failure detection enabled scenario We start connect and hanshake from timeout 500ms. If failed we increase timeout using exponential backoff strategy timeout = Math.min(Math.min(timeout * 2, maxTimeout), remainingTiimeTillFailureDetection) ) > Fix IGNITE_ENABLE_FORCIBLE_NODE_KILL system property. > - > > Key: IGNITE-7648 > URL: https://issues.apache.org/jira/browse/IGNITE-7648 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.3 >Reporter: Alexei Scherbakov >Assignee: Pavel Voronkin >Priority: Major > Fix For: 2.8 > > > IGNITE_ENABLE_FORCIBLE_NODE_KILL system property was introduced in > IGNITE-5718 as a way to prevent unnecessary node drops in case of short > network problems. > I suppose it's wrong decision to fix it in such way. > We had faced some issues in our production due to lack of automatic kicking > of ill-behaving nodes (on example, hanging due to long GC pauses) until we > realised the necessity of changing default behavior via property. > Right solution is to kick nodes only if failure threshold is reached. Such > behavior should be always enabled. > UPDATE: During a discussion it was decided what the property will remain > disabled by default. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7648) Fix IGNITE_ENABLE_FORCIBLE_NODE_KILL system property.
[ https://issues.apache.org/jira/browse/IGNITE-7648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Voronkin updated IGNITE-7648: --- Description: IGNITE_ENABLE_FORCIBLE_NODE_KILL system property was introduced in IGNITE-5718 as a way to prevent unnecessary node drops in case of short network problems. I suppose it's wrong decision to fix it in such way. We had faced some issues in our production due to lack of automatic kicking of ill-behaving nodes (on example, hanging due to long GC pauses) until we realised the necessity of changing default behavior via property. Right solution is to kick nodes only if failure threshold is reached. Such behavior should be always enabled. UPDATE: During a discussion it was decided what the property will remain disabled by default. We decided to change timeout logic in case of failure detection enabled. We start performing connect and handshake from 500ms increasing using exponential backoff strategy. was: IGNITE_ENABLE_FORCIBLE_NODE_KILL system property was introduced in IGNITE-5718 as a way to prevent unnecessary node drops in case of short network problems. I suppose it's wrong decision to fix it in such way. We had faced some issues in our production due to lack of automatic kicking of ill-behaving nodes (on example, hanging due to long GC pauses) until we realised the necessity of changing default behavior via property. Right solution is to kick nodes only if failure threshold is reached. Such behavior should be always enabled. UPDATE: During a discussion it was decided what the property will remain disabled by default. > Fix IGNITE_ENABLE_FORCIBLE_NODE_KILL system property. > - > > Key: IGNITE-7648 > URL: https://issues.apache.org/jira/browse/IGNITE-7648 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.3 >Reporter: Alexei Scherbakov >Assignee: Pavel Voronkin >Priority: Major > Fix For: 2.8 > > > IGNITE_ENABLE_FORCIBLE_NODE_KILL system property was introduced in > IGNITE-5718 as a way to prevent unnecessary node drops in case of short > network problems. > I suppose it's wrong decision to fix it in such way. > We had faced some issues in our production due to lack of automatic kicking > of ill-behaving nodes (on example, hanging due to long GC pauses) until we > realised the necessity of changing default behavior via property. > Right solution is to kick nodes only if failure threshold is reached. Such > behavior should be always enabled. > UPDATE: During a discussion it was decided what the property will remain > disabled by default. > We decided to change timeout logic in case of failure detection enabled. We > start performing connect and handshake from 500ms increasing using > exponential backoff strategy. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11266) Platform .NET test failed with Java 11 warning
[
https://issues.apache.org/jira/browse/IGNITE-11266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11266:
Description:
Following warning is unavoidable, because Java always warns about illegal
reflective access (at least for the first time). Probably we can change some
settings to avoid "The active test run was aborted. Reason".
https://ci.ignite.apache.org/viewLog.html?buildId=3027650
{noformat}
[17:32:56][test] The active test run was aborted. Reason: WARNING: An illegal
reflective access operation has occurred
[17:32:56][test] WARNING: Illegal reflective access by
org.apache.ignite.internal.util.GridUnsafe$2
(file:/data/teamcity/work/9198da4c51c3e112/modules/core/target/classes/) to
field java.nio.Buffer.address
[17:32:56][test] WARNING: Please consider reporting this to the maintainers of
org.apache.ignite.internal.util.GridUnsafe$2
[17:32:56][test] WARNING: Use --illegal-access=warn to enable warnings of
further illegal reflective access operations
[17:32:56][test] WARNING: All illegal access operations will be denied in a
future release
{noformat}
was:
Following warning is unavoidable, because Java always warns about illegal
reflective access (at least for the first time). Probably we can change some
settings to avoid "The active test run was aborted. Reason".
{noformat}
[17:32:56][test] The active test run was aborted. Reason: WARNING: An illegal
reflective access operation has occurred
[17:32:56][test] WARNING: Illegal reflective access by
org.apache.ignite.internal.util.GridUnsafe$2
(file:/data/teamcity/work/9198da4c51c3e112/modules/core/target/classes/) to
field java.nio.Buffer.address
[17:32:56][test] WARNING: Please consider reporting this to the maintainers of
org.apache.ignite.internal.util.GridUnsafe$2
[17:32:56][test] WARNING: Use --illegal-access=warn to enable warnings of
further illegal reflective access operations
[17:32:56][test] WARNING: All illegal access operations will be denied in a
future release
{noformat}
> Platform .NET test failed with Java 11 warning
> --
>
> Key: IGNITE-11266
> URL: https://issues.apache.org/jira/browse/IGNITE-11266
> Project: Ignite
> Issue Type: Bug
>Reporter: Dmitriy Pavlov
>Priority: Major
>
> Following warning is unavoidable, because Java always warns about illegal
> reflective access (at least for the first time). Probably we can change some
> settings to avoid "The active test run was aborted. Reason".
> https://ci.ignite.apache.org/viewLog.html?buildId=3027650
> {noformat}
> [17:32:56][test] The active test run was aborted. Reason: WARNING: An illegal
> reflective access operation has occurred
> [17:32:56][test] WARNING: Illegal reflective access by
> org.apache.ignite.internal.util.GridUnsafe$2
> (file:/data/teamcity/work/9198da4c51c3e112/modules/core/target/classes/) to
> field java.nio.Buffer.address
> [17:32:56][test] WARNING: Please consider reporting this to the maintainers
> of org.apache.ignite.internal.util.GridUnsafe$2
> [17:32:56][test] WARNING: Use --illegal-access=warn to enable warnings of
> further illegal reflective access operations
> [17:32:56][test] WARNING: All illegal access operations will be denied in a
> future release
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11265) JVM Crash is often on TeamCity for Java 11 runs
[ https://issues.apache.org/jira/browse/IGNITE-11265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763559#comment-16763559 ] Dmitriy Pavlov commented on IGNITE-11265: - [~agoncharuk] could you please take a look at the failure? I suppose we have a bug in our code, and Java 11 just a reproducer for it. > JVM Crash is often on TeamCity for Java 11 runs > --- > > Key: IGNITE-11265 > URL: https://issues.apache.org/jira/browse/IGNITE-11265 > Project: Ignite > Issue Type: Bug >Reporter: Dmitriy Pavlov >Priority: Major > Attachments: hs_err_pid2431080.log.txt, hs_err_pid2458635.log.txt, > hs_err_pid2674225.log.txt, hs_err_pid3473289.log.txt > > > All crash dumps complain about the same method > org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.writeLock > Data Structures (https://ci.ignite.apache.org/viewLog.html?buildId=3007882) > https://ci.ignite.apache.org/repository/download/IgniteTests24Java8_DataStructures/3007882:id/hs_err_pid2674225.log > Other recent examples > Queries 1 > https://ci.ignite.apache.org/repository/download/IgniteTests24Java8_Queries1/3027655:id/hs_err_pid2458635.log > Client Nodes > https://ci.ignite.apache.org/repository/download/IgniteTests24Java8_ClientNodes/3027569:id/hs_err_pid2431080.log > Zookeeper Discovery > https://ci.ignite.apache.org/repository/download/IgniteTests24Java8_ZooKeeperDiscovery1/3027601:id/hs_err_pid3473289.log -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11266) Platform .NET test failed with Java 11 warning
[
https://issues.apache.org/jira/browse/IGNITE-11266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763558#comment-16763558
]
Dmitriy Pavlov commented on IGNITE-11266:
-
[~ptupitsyn], could you please take a look at this failure? How can we
reconfigure the tests to ignore the warning (If the warning is the only reason
for the failure)?
> Platform .NET test failed with Java 11 warning
> --
>
> Key: IGNITE-11266
> URL: https://issues.apache.org/jira/browse/IGNITE-11266
> Project: Ignite
> Issue Type: Bug
>Reporter: Dmitriy Pavlov
>Priority: Major
>
> Following warning is unavoidable, because Java always warns about illegal
> reflective access (at least for the first time). Probably we can change some
> settings to avoid "The active test run was aborted. Reason".
> https://ci.ignite.apache.org/viewLog.html?buildId=3027650
> {noformat}
> [17:32:56][test] The active test run was aborted. Reason: WARNING: An illegal
> reflective access operation has occurred
> [17:32:56][test] WARNING: Illegal reflective access by
> org.apache.ignite.internal.util.GridUnsafe$2
> (file:/data/teamcity/work/9198da4c51c3e112/modules/core/target/classes/) to
> field java.nio.Buffer.address
> [17:32:56][test] WARNING: Please consider reporting this to the maintainers
> of org.apache.ignite.internal.util.GridUnsafe$2
> [17:32:56][test] WARNING: Use --illegal-access=warn to enable warnings of
> further illegal reflective access operations
> [17:32:56][test] WARNING: All illegal access operations will be denied in a
> future release
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11265) JVM Crash is often on TeamCity for Java 11 runs
[ https://issues.apache.org/jira/browse/IGNITE-11265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-11265: Attachment: hs_err_pid2458635.log.txt hs_err_pid2431080.log.txt hs_err_pid3473289.log.txt hs_err_pid2674225.log.txt > JVM Crash is often on TeamCity for Java 11 runs > --- > > Key: IGNITE-11265 > URL: https://issues.apache.org/jira/browse/IGNITE-11265 > Project: Ignite > Issue Type: Bug >Reporter: Dmitriy Pavlov >Priority: Major > Attachments: hs_err_pid2431080.log.txt, hs_err_pid2458635.log.txt, > hs_err_pid2674225.log.txt, hs_err_pid3473289.log.txt > > > All crash dumps complain about the same method > org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.writeLock > Data Structures (https://ci.ignite.apache.org/viewLog.html?buildId=3007882) > https://ci.ignite.apache.org/repository/download/IgniteTests24Java8_DataStructures/3007882:id/hs_err_pid2674225.log > Other recent examples > Queries 1 > https://ci.ignite.apache.org/repository/download/IgniteTests24Java8_Queries1/3027655:id/hs_err_pid2458635.log > Client Nodes > https://ci.ignite.apache.org/repository/download/IgniteTests24Java8_ClientNodes/3027569:id/hs_err_pid2431080.log > Zookeeper Discovery > https://ci.ignite.apache.org/repository/download/IgniteTests24Java8_ZooKeeperDiscovery1/3027601:id/hs_err_pid3473289.log -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11253) When a node that is not part of the base topology joins the cluster, it may lead to a node failure.
[
https://issues.apache.org/jira/browse/IGNITE-11253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763562#comment-16763562
]
Vyacheslav Koptilin commented on IGNITE-11253:
--
I just checked and it seems that this test should not be affected by the fix.
Anyway, I will re-run the team city in order to confirm that.
> When a node that is not part of the base topology joins the cluster, it may
> lead to a node failure.
> ---
>
> Key: IGNITE-11253
> URL: https://issues.apache.org/jira/browse/IGNITE-11253
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Vyacheslav Koptilin
>Assignee: Vyacheslav Koptilin
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> * In case of eager TTL is configured, a starting node creates and starts
> {{cleanupWorker}} (see {{GridCacheTtlManager.start0()}})
> * {{GridCacheSharedTtlCleanupManager.CleanupWorker}}, in its turn, has to
> wait for {{discovery().localJoin()}} future that is completed by discovery
> thread.
> * On the other hand, the exchange thread stops cache contexts and,
> therefore, it stops the {{cleanupWorker}} as well.
>
> {code:java}
> org.apache.ignite.internal.processors.cache.GridCacheSharedTtlCleanupManager.stopCleanupWorker(GridCacheSharedTtlCleanupManager.java:109)
> org.apache.ignite.internal.processors.cache.GridCacheSharedTtlCleanupManager.unregister(GridCacheSharedTtlCleanupManager.java:82)
> org.apache.ignite.internal.processors.cache.GridCacheTtlManager.onKernalStop0(GridCacheTtlManager.java:110)
> org.apache.ignite.internal.processors.cache.GridCacheManagerAdapter.onKernalStop(GridCacheManagerAdapter.java:111)
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStop(GridCacheProcessor.java:1495)
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStopCaches(GridCacheProcessor.java:1182)
> org.apache.ignite.internal.processors.cache.GridCacheProcessor$CacheRecoveryLifecycle.onBaselineChange(GridCacheProcessor.java:5637)
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.initCachesOnLocalJoin(GridDhtPartitionsExchangeFuture.java:910)
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:792)
> {code}
> So, exchange thread may try to stop the {{cleanupWorker}} before the
> {{localJoin}} future is completed by discovery thread. Unfortunately,
> `cleanupWorker` incorrectly handles this situation, and this fact can lead to
> a node failure:
> {code:java}
> Critical system error detected. Will be handled accordingly to configured
> handler [hnd=StopNodeFailureHandler [super=AbstractFailureHandler
> [ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED,
> SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext
> [type=SYSTEM_WORKER_TERMINATION, err=class o.a.i.IgniteException: Got
> interrupted while waiting for future to complete.]]
> class org.apache.ignite.IgniteException: Got interrupted while waiting for
> future to complete.
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.localJoin(GridDiscoveryManager.java:2217)
> at
> org.apache.ignite.internal.processors.cache.GridCacheSharedTtlCleanupManager$CleanupWorker.body(GridCacheSharedTtlCleanupManager.java:136)
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class
> org.apache.ignite.internal.IgniteInterruptedCheckedException: Got interrupted
> while waiting for future to complete.
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:186)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:141)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.localJoin(GridDiscoveryManager.java:2214)
> ... 3 more
> {code}
> The obvious fix is changing the catch block
> {code:java}
> catch (Throwable t) {
> if (!(t instanceof IgniteInterruptedCheckedException))
> err = t;
> throw t;
> }
> {code}
> to the following:
> {code:java}
> catch (Throwable t) {
> if (!(X.hasCause(t, IgniteInterruptedCheckedException.class)))
> err = t;
> throw t;
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11253) When a node that is not part of the baseline topology joins the cluster, it may lead to a node failure.
[
https://issues.apache.org/jira/browse/IGNITE-11253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-11253:
-
Summary: When a node that is not part of the baseline topology joins the
cluster, it may lead to a node failure. (was: When a node that is not part of
the base topology joins the cluster, it may lead to a node failure.)
> When a node that is not part of the baseline topology joins the cluster, it
> may lead to a node failure.
> ---
>
> Key: IGNITE-11253
> URL: https://issues.apache.org/jira/browse/IGNITE-11253
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Vyacheslav Koptilin
>Assignee: Vyacheslav Koptilin
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> * In case of eager TTL is configured, a starting node creates and starts
> {{cleanupWorker}} (see {{GridCacheTtlManager.start0()}})
> * {{GridCacheSharedTtlCleanupManager.CleanupWorker}}, in its turn, has to
> wait for {{discovery().localJoin()}} future that is completed by discovery
> thread.
> * On the other hand, the exchange thread stops cache contexts and,
> therefore, it stops the {{cleanupWorker}} as well.
>
> {code:java}
> org.apache.ignite.internal.processors.cache.GridCacheSharedTtlCleanupManager.stopCleanupWorker(GridCacheSharedTtlCleanupManager.java:109)
> org.apache.ignite.internal.processors.cache.GridCacheSharedTtlCleanupManager.unregister(GridCacheSharedTtlCleanupManager.java:82)
> org.apache.ignite.internal.processors.cache.GridCacheTtlManager.onKernalStop0(GridCacheTtlManager.java:110)
> org.apache.ignite.internal.processors.cache.GridCacheManagerAdapter.onKernalStop(GridCacheManagerAdapter.java:111)
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStop(GridCacheProcessor.java:1495)
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStopCaches(GridCacheProcessor.java:1182)
> org.apache.ignite.internal.processors.cache.GridCacheProcessor$CacheRecoveryLifecycle.onBaselineChange(GridCacheProcessor.java:5637)
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.initCachesOnLocalJoin(GridDhtPartitionsExchangeFuture.java:910)
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:792)
> {code}
> So, exchange thread may try to stop the {{cleanupWorker}} before the
> {{localJoin}} future is completed by discovery thread. Unfortunately,
> `cleanupWorker` incorrectly handles this situation, and this fact can lead to
> a node failure:
> {code:java}
> Critical system error detected. Will be handled accordingly to configured
> handler [hnd=StopNodeFailureHandler [super=AbstractFailureHandler
> [ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED,
> SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext
> [type=SYSTEM_WORKER_TERMINATION, err=class o.a.i.IgniteException: Got
> interrupted while waiting for future to complete.]]
> class org.apache.ignite.IgniteException: Got interrupted while waiting for
> future to complete.
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.localJoin(GridDiscoveryManager.java:2217)
> at
> org.apache.ignite.internal.processors.cache.GridCacheSharedTtlCleanupManager$CleanupWorker.body(GridCacheSharedTtlCleanupManager.java:136)
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class
> org.apache.ignite.internal.IgniteInterruptedCheckedException: Got interrupted
> while waiting for future to complete.
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:186)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:141)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.localJoin(GridDiscoveryManager.java:2214)
> ... 3 more
> {code}
> The obvious fix is changing the catch block
> {code:java}
> catch (Throwable t) {
> if (!(t instanceof IgniteInterruptedCheckedException))
> err = t;
> throw t;
> }
> {code}
> to the following:
> {code:java}
> catch (Throwable t) {
> if (!(X.hasCause(t, IgniteInterruptedCheckedException.class)))
> err = t;
> throw t;
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10161) Be able to cancel any query by query id
[
https://issues.apache.org/jira/browse/IGNITE-10161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763572#comment-16763572
]
Yury Gerzhedovich commented on IGNITE-10161:
[~vozerov], Patch is ready to review.
> Be able to cancel any query by query id
> ---
>
> Key: IGNITE-10161
> URL: https://issues.apache.org/jira/browse/IGNITE-10161
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Yury Gerzhedovich
>Assignee: Yury Gerzhedovich
>Priority: Major
> Labels: iep-29
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> User should be able to cancel any query by query id through SQL command.
> SQL syntax: *KILL QUERY '<_query_id>' \{ASYNC}_*
> _ASYNC_ is optional parameter which return control immediately without
> waiting real cancellation will be done.
> By default, without ASYNC parameter, the request is blocking untill
> cancellation is not done.
> Query should be canceled together with its parts on all nodes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10926) ZookeeperDiscoverySpi: client does not survive after several cluster restarts
[
https://issues.apache.org/jira/browse/IGNITE-10926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763589#comment-16763589
]
Sergey Chugunov commented on IGNITE-10926:
--
[~NSAmelchev],
I reviewed patch one more time, it looks good to me as client node now fires
RECONNECT event only after a successful join.
I suggest to remove {{Ignore}} annotation from tests
{{testReconnectServersRestart_1}} and {{testReconnectServersRestart_2}} as they
should be fixed by this change. If so we may even close related ticket
IGNITE-8178.
Thank you for your contribution!
> ZookeeperDiscoverySpi: client does not survive after several cluster restarts
> -
>
> Key: IGNITE-10926
> URL: https://issues.apache.org/jira/browse/IGNITE-10926
> Project: Ignite
> Issue Type: Bug
> Components: zookeeper
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{ZookeeperDiscoveryImpl#cleanupPreviousClusterData}} can delete alive node
> of a client in case of low internal order.
> Steps to reproduce:
> 1. Start server and client.
> 2. Stop the server and wait for the client disconnected.
> 3. Start and stop the server. The server hasn't time to process client join
> request.
> 4. Start server. It will delete alive client node because the client has low
> internal order. The client will never connect.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10926) ZookeeperDiscoverySpi: client does not survive after several cluster restarts
[
https://issues.apache.org/jira/browse/IGNITE-10926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763594#comment-16763594
]
Amelchev Nikita commented on IGNITE-10926:
--
[~sergey-chugunov], Thank you for review.
I looked at these tests and they fail not only by this reason if run several
times. After this fix, I'll back to this related ticket.
> ZookeeperDiscoverySpi: client does not survive after several cluster restarts
> -
>
> Key: IGNITE-10926
> URL: https://issues.apache.org/jira/browse/IGNITE-10926
> Project: Ignite
> Issue Type: Bug
> Components: zookeeper
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{ZookeeperDiscoveryImpl#cleanupPreviousClusterData}} can delete alive node
> of a client in case of low internal order.
> Steps to reproduce:
> 1. Start server and client.
> 2. Stop the server and wait for the client disconnected.
> 3. Start and stop the server. The server hasn't time to process client join
> request.
> 4. Start server. It will delete alive client node because the client has low
> internal order. The client will never connect.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11177) IGNITE.NODE_METRICS view fails with "Cannot parse "TIME" constant" > 24h
[
https://issues.apache.org/jira/browse/IGNITE-11177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763592#comment-16763592
]
Pavel Kuznetsov commented on IGNITE-11177:
--
[~vozerov] Done! But note, the hack actually is a bit more complicated than
just set a field.
> IGNITE.NODE_METRICS view fails with "Cannot parse "TIME" constant" > 24h
>
>
> Key: IGNITE-11177
> URL: https://issues.apache.org/jira/browse/IGNITE-11177
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.7
>Reporter: Ilya Kasnacheev
>Assignee: Pavel Kuznetsov
>Priority: Major
> Labels: metrics
> Fix For: 2.8
>
>
> This is because we are using TIME type for several additive measurements:
> {quote}SqlSystemViewNodeMetrics.class:
>
> valueTimeFromMillis(metrics.getTotalJobsExecutionTime()),
> valueTimeFromMillis(metrics.getTotalBusyTime()),
>
> valueTimeFromMillis(metrics.getTotalIdleTime()),{quote}
> which will be hundreds of hours on long-running cluster, but {{TIME}} type is
> limited to 24 hours and will fail to be converted otherwise, as in:
> {quote}0: jdbc:ignite:thin://localhost> SELECT CAST('40:52:26.548' AS TIME);
> Error: Failed to parse query. Невозможно преобразование строки "40:52:26.548"
> в тип "TIME"
> Cannot parse "TIME" constant "40:52:26.548"; SQL statement:
> SELECT CAST('40:52:26.548' AS TIME) [22007-197] (state=42000,code=1001){quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11155) Add JVM options analysis to Ignition.start() or handle and comment exceptions
[
https://issues.apache.org/jira/browse/IGNITE-11155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763598#comment-16763598
]
Ignite TC Bot commented on IGNITE-11155:
{panel:title=--> Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET (Long Running){color} [[tests 10 TIMEOUT
|https://ci.ignite.apache.org/viewLog.html?buildId=3027653]]
* exe: ClientConnectionTest.TestClientDisposeWhileOperationsAreInProgress -
21,1% fails in last 365 master runs.
* exe: CacheTest.TestGetMultithreadedMultiClient - 15,1% fails in last 365
master runs.
* exe: CacheTest.TestGetMultithreadedSingleClient - 0,8% fails in last 365
master runs.
* exe: CacheTest.TestPutGetAsyncMultithreaded - 0,0% fails in last 365 master
runs.
* exe: SslConfigurationTest.TestClientServer - 0,0% fails in last 362 master
runs.
* exe: CacheTest.TestGetMultithreadedSingleClient - 0,0% fails in last 365
master runs.
* exe: CacheTest.TestPutGetAsyncMultithreaded - 0,0% fails in last 365 master
runs.
* exe: CacheTest.TestGetMultithreadedSingleClient - 0,0% fails in last 365
master runs.
* exe: CacheTest.TestPutGetAsyncMultithreaded - 0,0% fails in last 365 master
runs.
* exe: ExecutableTest.TestInvalidCmdArgs - 0,0% fails in last 363 master runs.
{color:#d04437}ZooKeeper (Discovery) 1{color} [[tests 0 JVM CRASH , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3027601]]
* ZookeeperDiscoveryTopologyChangeAndReconnectTest.testDuplicatedNodeId (last
started)
{color:#d04437}Client Nodes{color} [[tests 0 JVM CRASH , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3027569]]
* IgniteClientReconnectCacheTest.testReconnectClusterRestartMultinode (last
started)
{color:#d04437}SPI{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3036820]]
{color:#d04437}Platform .NET (Core Linux){color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3027650]]
{color:#d04437}Queries 1{color} [[tests 0 JVM CRASH , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3027655]]
* IgniteCacheAtomicNearEnabledFieldsQuerySelfTest.testSingleResultUsesFindOne
(last started)
{color:#d04437}ZooKeeper (Discovery) 3{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3027659]]
* GridEventConsumeSelfTest.testRemoteProjection (last started)
{color:#d04437}Platform C++ (Linux){color} [[tests 0 Exit Code , Failure on
metric |https://ci.ignite.apache.org/viewLog.html?buildId=3027603]]
{color:#d04437}Platform C++ (Linux Clang){color} [[tests 0 Exit Code , Failure
on metric |https://ci.ignite.apache.org/viewLog.html?buildId=3027609]]
{color:#d04437}Cache (Failover SSL){color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3027618]]
{color:#d04437}SPI (URI Deploy){color} [[tests 0 Exit Code , Compilation Error
|https://ci.ignite.apache.org/viewLog.html?buildId=3027595]]
{color:#d04437}_Javadoc_{color} [[tests 0 Exit Code , Compilation Error
|https://ci.ignite.apache.org/viewLog.html?buildId=3027614]]
{color:#d04437}RDD*{color} [[tests 0 Exit Code , Compilation Error
|https://ci.ignite.apache.org/viewLog.html?buildId=3027588]]
{color:#d04437}Platform .NET (NuGet)*{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3027654]]
{color:#d04437}JCache TCK 1.1{color} [[tests 0 Exit Code , Compilation Error
|https://ci.ignite.apache.org/viewLog.html?buildId=3027608]]
{color:#d04437}Queries 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=3027589]]
* IgniteBinaryCacheQueryTestSuite2:
CacheQueryEntityWithDateTimeApiFieldsTest.testUpdateAllFields - 0,0% fails in
last 404 master runs.
{color:#d04437}Cache 1{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=3027627]]
* IgniteBinaryCacheTestSuite:
IgniteCommunicationSslBalanceTest.testRandomBalance - 0,0% fails in last 406
master runs.
* IgniteBinaryCacheTestSuite: IgniteCommunicationSslBalanceTest.testBalance2 -
0,0% fails in last 406 master runs.
{color:#d04437}Java Client{color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=3027582]]
* IgniteClientTestSuite:
ClientTcpSslAuthenticationSelfTest.testClientAuthenticated - 0,0% fails in last
402 master runs.
* IgniteClientTestSuite:
ClientTcpSslAuthenticationSelfTest.testServerAuthenticated - 0,0% fails in last
402 master runs.
* IgniteClientTestSuite: ClientTcpSslSelfTest.testExecute - 0,0% fails in last
402 master runs.
{color:#d04437}JDBC Driver{color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=3036956]]
* IgniteJdbcDriverTestSuite:
JdbcThinConnectionSSLTest.testUnsupportedSslProtocol - 0,0% fails in last 406
master runs.
* IgniteJdbcDriverTestSuite: JdbcThinConnectionSSLTest.testInvalidKeyStoreType
- 0,0% fails in last 406 master runs.
* Ign
[jira] [Commented] (IGNITE-11233) Ignite Build for Java 11 does not reuse ignite-tools from Build Apache Ignite for some configurations, Compilation error
[
https://issues.apache.org/jira/browse/IGNITE-11233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763606#comment-16763606
]
Dmitriy Pavlov commented on IGNITE-11233:
-
Ok, let's move RDD and Platform .NET to standalone issues. I've retriggered
builds for my branch. If it passes now, let's resolve this one.
> Ignite Build for Java 11 does not reuse ignite-tools from Build Apache Ignite
> for some configurations, Compilation error
>
>
> Key: IGNITE-11233
> URL: https://issues.apache.org/jira/browse/IGNITE-11233
> Project: Ignite
> Issue Type: Bug
>Reporter: Dmitriy Pavlov
>Assignee: Peter Ivanov
>Priority: Critical
>
> _Javadoc_ [ tests 0 Exit Code , Compilation Error ]
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Javadoc&branch=ignite-11213&tab=buildTypeStatusDiv
> SPI (URI Deploy) [ tests 0 Exit Code , Compilation Error ]
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_SpiUriDeploy&branch=ignite-11213&tab=buildTypeStatusDiv
> RDD* [ tests 0 Exit Code , Compilation Error ]
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Rdd&branch=ignite-11213&tab=buildTypeStatusDiv
> JCache TCK 1.1 [ tests 0 Exit Code , Compilation Error ]
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_JCacheTck11&branch=ignite-11213&tab=buildTypeStatusDiv
> Platform .NET (NuGet)* [ tests 0 Exit Code ]
> https://ci.ignite.apache.org/viewLog.html?tab=buildLog&logTab=tree&filter=debug&expand=all&buildId=3007897&_focus=904
> {noformat}
> [21:28:31][Step 1/1] [INFO] Compiling 9 source files to
> /data/teamcity/work/9198da4c51c3e112/modules/tools/target/classes
> [21:28:32][Step 1/1] [INFO]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:
>
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java
> uses or overrides a deprecated API that is marked for removal.
> [21:28:32][Step 1/1] [INFO]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:
> Recompile with -Xlint:removal for details.
> [21:28:32][Step 1/1] [INFO]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/classgen/ClassesGenerator.java:
>
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/classgen/ClassesGenerator.java
> uses unchecked or unsafe operations.
> [21:28:32][Step 1/1] [INFO]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/classgen/ClassesGenerator.java:
> Recompile with -Xlint:unchecked for details.
> [21:28:32][Step 1/1] [INFO]
> -
> [21:28:32][Step 1/1] [ERROR] COMPILATION ERROR :
> [21:28:32][Step 1/1] [INFO]
> -
> [21:28:32][Step 1/1] [ERROR]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:[21,29]
> package com.sun.tools.doclets does not exist
> [21:28:32][Step 1/1] [ERROR]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:[30,42]
> cannot find symbol
> [21:28:32][Step 1/1] symbol: class Taglet
> [21:28:32][Step 1/1] [ERROR]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:[37,5]
> method does not override or implement a method from a supertype
> [21:28:32][Step 1/1] [ERROR]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:[44,5]
> method does not override or implement a method from a supertype
> [21:28:32][Step 1/1] [ERROR]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:[51,5]
> method does not override or implement a method from a supertype
> [21:28:32][Step 1/1] [ERROR]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:[58,5]
> method does not override or implement a method from a supertype
> [21:28:32][Step 1/1] [ERROR]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:[65,5]
> method does not override or implement a method from a supertype
> [21:28:32][Step 1/1] [ERROR]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/Ig
[jira] [Commented] (IGNITE-11059) Print information about pending locks queue in case of dht local tx timeout.
[ https://issues.apache.org/jira/browse/IGNITE-11059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763609#comment-16763609 ] Alexei Scherbakov commented on IGNITE-11059: [~ivandasch] Changes look good to me. But probably it's worth adding newly introduced debug info directly to toString implementation (both for DhtPrepare and DhtLock futures) and resort to already existing code for printing long running operations. [~agoncharuk] what do you think ? > Print information about pending locks queue in case of dht local tx timeout. > > > Key: IGNITE-11059 > URL: https://issues.apache.org/jira/browse/IGNITE-11059 > Project: Ignite > Issue Type: Improvement >Reporter: Alexei Scherbakov >Assignee: Ivan Daschinskiy >Priority: Major > Labels: newbie > Fix For: 2.8 > > Time Spent: 1h > Remaining Estimate: 0h > > Currently in case of dht local tx timeout it's hard to understand which keys > was not locked. > Addtional information should be printed in log on timeout containing > information about pending keys: > key, tx info holding a lock (xid, label if present) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11218) COUNT(*) may return wrong value with PDS
[
https://issues.apache.org/jira/browse/IGNITE-11218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763610#comment-16763610
]
Vladimir Ozerov commented on IGNITE-11218:
--
[~skozlov], as discussed, this is expected behavior for PRIMARY_SYNC.
> COUNT(*) may return wrong value with PDS
>
>
> Key: IGNITE-11218
> URL: https://issues.apache.org/jira/browse/IGNITE-11218
> Project: Ignite
> Issue Type: Bug
> Components: persistence, sql
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Priority: Major
> Attachments: count.zip
>
>
> 1. Unzip attached file into {{examples}} directory
> 2. Open {{ignite-examples}} project in IDEA.
> 3. Start at least 3 nodes {{bin/ignite.sh examples/config/count.xml -v}}
> 4. Run {{SqlJdbcCountExample}} which creates tables by template _Replicated,
> TX, PRIMARY_SYNC, readFromBackup=false_, inserts 500 rows and executes
> _SELECT COUNT(*)_
> {noformat}
> [23:54:44] Ignite node started OK (id=97f4654e)
> [23:54:44] >>> Ignite cluster is not active (limited functionality
> available). Use control.(sh|bat) script or IgniteCluster interface to
> activate.
> [23:54:44] Topology snapshot [ver=4, locNode=97f4654e, servers=3, clients=1,
> state=INACTIVE, CPUs=4, offheap=0.66GB, heap=8.3GB]
> [23:54:45] Ignite node stopped OK [uptime=00:00:01.238]
> >>> Connected to server.
> >>> Attempt 1
> >>> ERROR! Expected 500 entries for table t1 but got 498 entries
> >>> Attempt 2
> >>> ERROR! Expected 500 entries for table t2 but got 476 entries
> >>> Attempt 3
> >>> ERROR! Expected 500 entries for table t3 but got 477 entries
> >>> Attempt 4
> >>> ERROR! Expected 500 entries for table t4 but got 430 entries
> >>> Attempt 5
> >>> Attempt 6
> >>> ERROR! Expected 500 entries for table t6 but got 486 entries
> >>> Attempt 7
> >>> Attempt 8
> >>> ERROR! Expected 500 entries for table t8 but got 463 entries
> >>> Attempt 9
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11218) COUNT(*) may return wrong value with PDS
[
https://issues.apache.org/jira/browse/IGNITE-11218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-11218:
-
Component/s: (was: sql)
(was: persistence)
documentation
> COUNT(*) may return wrong value with PDS
>
>
> Key: IGNITE-11218
> URL: https://issues.apache.org/jira/browse/IGNITE-11218
> Project: Ignite
> Issue Type: Bug
> Components: documentation
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Priority: Major
> Attachments: count.zip
>
>
> 1. Unzip attached file into {{examples}} directory
> 2. Open {{ignite-examples}} project in IDEA.
> 3. Start at least 3 nodes {{bin/ignite.sh examples/config/count.xml -v}}
> 4. Run {{SqlJdbcCountExample}} which creates tables by template _Replicated,
> TX, PRIMARY_SYNC, readFromBackup=false_, inserts 500 rows and executes
> _SELECT COUNT(*)_
> {noformat}
> [23:54:44] Ignite node started OK (id=97f4654e)
> [23:54:44] >>> Ignite cluster is not active (limited functionality
> available). Use control.(sh|bat) script or IgniteCluster interface to
> activate.
> [23:54:44] Topology snapshot [ver=4, locNode=97f4654e, servers=3, clients=1,
> state=INACTIVE, CPUs=4, offheap=0.66GB, heap=8.3GB]
> [23:54:45] Ignite node stopped OK [uptime=00:00:01.238]
> >>> Connected to server.
> >>> Attempt 1
> >>> ERROR! Expected 500 entries for table t1 but got 498 entries
> >>> Attempt 2
> >>> ERROR! Expected 500 entries for table t2 but got 476 entries
> >>> Attempt 3
> >>> ERROR! Expected 500 entries for table t3 but got 477 entries
> >>> Attempt 4
> >>> ERROR! Expected 500 entries for table t4 but got 430 entries
> >>> Attempt 5
> >>> Attempt 6
> >>> ERROR! Expected 500 entries for table t6 but got 486 entries
> >>> Attempt 7
> >>> Attempt 8
> >>> ERROR! Expected 500 entries for table t8 but got 463 entries
> >>> Attempt 9
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-11218) COUNT(*) may return wrong value with PDS
[
https://issues.apache.org/jira/browse/IGNITE-11218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763610#comment-16763610
]
Vladimir Ozerov edited comment on IGNITE-11218 at 2/8/19 1:53 PM:
--
[~skozlov], as discussed, this is expected behavior for PRIMARY_SYNC. What we
need is to document it properly.
was (Author: vozerov):
[~skozlov], as discussed, this is expected behavior for PRIMARY_SYNC.
> COUNT(*) may return wrong value with PDS
>
>
> Key: IGNITE-11218
> URL: https://issues.apache.org/jira/browse/IGNITE-11218
> Project: Ignite
> Issue Type: Bug
> Components: documentation
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Priority: Major
> Attachments: count.zip
>
>
> 1. Unzip attached file into {{examples}} directory
> 2. Open {{ignite-examples}} project in IDEA.
> 3. Start at least 3 nodes {{bin/ignite.sh examples/config/count.xml -v}}
> 4. Run {{SqlJdbcCountExample}} which creates tables by template _Replicated,
> TX, PRIMARY_SYNC, readFromBackup=false_, inserts 500 rows and executes
> _SELECT COUNT(*)_
> {noformat}
> [23:54:44] Ignite node started OK (id=97f4654e)
> [23:54:44] >>> Ignite cluster is not active (limited functionality
> available). Use control.(sh|bat) script or IgniteCluster interface to
> activate.
> [23:54:44] Topology snapshot [ver=4, locNode=97f4654e, servers=3, clients=1,
> state=INACTIVE, CPUs=4, offheap=0.66GB, heap=8.3GB]
> [23:54:45] Ignite node stopped OK [uptime=00:00:01.238]
> >>> Connected to server.
> >>> Attempt 1
> >>> ERROR! Expected 500 entries for table t1 but got 498 entries
> >>> Attempt 2
> >>> ERROR! Expected 500 entries for table t2 but got 476 entries
> >>> Attempt 3
> >>> ERROR! Expected 500 entries for table t3 but got 477 entries
> >>> Attempt 4
> >>> ERROR! Expected 500 entries for table t4 but got 430 entries
> >>> Attempt 5
> >>> Attempt 6
> >>> ERROR! Expected 500 entries for table t6 but got 486 entries
> >>> Attempt 7
> >>> Attempt 8
> >>> ERROR! Expected 500 entries for table t8 but got 463 entries
> >>> Attempt 9
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11218) COUNT(*) may return wrong value with PDS
[
https://issues.apache.org/jira/browse/IGNITE-11218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-11218:
-
Issue Type: Task (was: Bug)
> COUNT(*) may return wrong value with PDS
>
>
> Key: IGNITE-11218
> URL: https://issues.apache.org/jira/browse/IGNITE-11218
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Priority: Major
> Attachments: count.zip
>
>
> 1. Unzip attached file into {{examples}} directory
> 2. Open {{ignite-examples}} project in IDEA.
> 3. Start at least 3 nodes {{bin/ignite.sh examples/config/count.xml -v}}
> 4. Run {{SqlJdbcCountExample}} which creates tables by template _Replicated,
> TX, PRIMARY_SYNC, readFromBackup=false_, inserts 500 rows and executes
> _SELECT COUNT(*)_
> {noformat}
> [23:54:44] Ignite node started OK (id=97f4654e)
> [23:54:44] >>> Ignite cluster is not active (limited functionality
> available). Use control.(sh|bat) script or IgniteCluster interface to
> activate.
> [23:54:44] Topology snapshot [ver=4, locNode=97f4654e, servers=3, clients=1,
> state=INACTIVE, CPUs=4, offheap=0.66GB, heap=8.3GB]
> [23:54:45] Ignite node stopped OK [uptime=00:00:01.238]
> >>> Connected to server.
> >>> Attempt 1
> >>> ERROR! Expected 500 entries for table t1 but got 498 entries
> >>> Attempt 2
> >>> ERROR! Expected 500 entries for table t2 but got 476 entries
> >>> Attempt 3
> >>> ERROR! Expected 500 entries for table t3 but got 477 entries
> >>> Attempt 4
> >>> ERROR! Expected 500 entries for table t4 but got 430 entries
> >>> Attempt 5
> >>> Attempt 6
> >>> ERROR! Expected 500 entries for table t6 but got 486 entries
> >>> Attempt 7
> >>> Attempt 8
> >>> ERROR! Expected 500 entries for table t8 but got 463 entries
> >>> Attempt 9
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-10206) Allow specifying query parallelism in CREATE TABLE's WITH "" clause
[
https://issues.apache.org/jira/browse/IGNITE-10206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Kuznetsov reassigned IGNITE-10206:
Assignee: Pavel Kuznetsov
> Allow specifying query parallelism in CREATE TABLE's WITH "" clause
> ---
>
> Key: IGNITE-10206
> URL: https://issues.apache.org/jira/browse/IGNITE-10206
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Affects Versions: 2.6
>Reporter: Ilya Kasnacheev
>Assignee: Pavel Kuznetsov
>Priority: Minor
>
> As in
> {code}
> CREATE TABLE foo (id long primary key, val varchar) WITH "backups=1,
> query_parallelism=4";
> {code}
> Currently it is possible to specify e.g. backups but not query_parallelism.
> This leads to necessity to specify cache template for such tables, which is
> cumbersome.
> Moreover, people may ignore this option outright and get worse performance.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11239) SPI and JDBC driver tests failed because of SSL connection timeout for Java 11
[ https://issues.apache.org/jira/browse/IGNITE-11239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763614#comment-16763614 ] Peter Ivanov commented on IGNITE-11239: --- # _[SPI|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Spi&branch_IgniteTests24Java8=ignite-11155]_ (x) [Run on JDK 11.0.2|https://ci.ignite.apache.org/viewLog.html?buildId=3036820]: timeout # _[JDBC Driver|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_JdbcDriver&branch_IgniteTests24Java8=ignite-11155]_ (!) Run on JDK 11.0.2: no timeouts for [3 runs|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_JdbcDriver&tab=buildTypeHistoryList&branch_IgniteTests24Java8=ignite-11155] > SPI and JDBC driver tests failed because of SSL connection timeout for Java 11 > -- > > Key: IGNITE-11239 > URL: https://issues.apache.org/jira/browse/IGNITE-11239 > Project: Ignite > Issue Type: Task >Reporter: Dmitriy Pavlov >Assignee: Peter Ivanov >Priority: Major > > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Spi&branch=ignite-11155&tab=buildTypeStatusDiv > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_JdbcDriver&branch=ignite-11155&tab=buildTypeStatusDiv > Probably we should update Java versions installed on TC agents to avoid some > EA-Java-related bugs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11267) Print warning when keystore password arguments are used in control.sh (bat)
[ https://issues.apache.org/jira/browse/IGNITE-11267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Kuznetsov updated IGNITE-11267: -- Priority: Minor (was: Major) > Print warning when keystore password arguments are used in control.sh (bat) > --- > > Key: IGNITE-11267 > URL: https://issues.apache.org/jira/browse/IGNITE-11267 > Project: Ignite > Issue Type: Task >Reporter: Andrey Kuznetsov >Priority: Minor > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11267) Print warning when keystore password arguments are used in control.sh (bat)
[ https://issues.apache.org/jira/browse/IGNITE-11267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Kuznetsov updated IGNITE-11267: -- Summary: Print warning when keystore password arguments are used in control.sh (bat) (was: Print Warn user when keystore password arguments) > Print warning when keystore password arguments are used in control.sh (bat) > --- > > Key: IGNITE-11267 > URL: https://issues.apache.org/jira/browse/IGNITE-11267 > Project: Ignite > Issue Type: Bug >Reporter: Andrey Kuznetsov >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11267) Print warning when keystore password arguments are used in control.sh (bat)
[ https://issues.apache.org/jira/browse/IGNITE-11267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Kuznetsov updated IGNITE-11267: -- Issue Type: Task (was: Bug) > Print warning when keystore password arguments are used in control.sh (bat) > --- > > Key: IGNITE-11267 > URL: https://issues.apache.org/jira/browse/IGNITE-11267 > Project: Ignite > Issue Type: Task >Reporter: Andrey Kuznetsov >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11242) Update counters mismatch after loading data via DataStreamer into MVCC-enabled caches
[
https://issues.apache.org/jira/browse/IGNITE-11242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Pavlukhin reassigned IGNITE-11242:
---
Assignee: Ivan Pavlukhin
> Update counters mismatch after loading data via DataStreamer into
> MVCC-enabled caches
> -
>
> Key: IGNITE-11242
> URL: https://issues.apache.org/jira/browse/IGNITE-11242
> Project: Ignite
> Issue Type: Bug
> Components: mvcc, streaming
>Affects Versions: 2.7
>Reporter: Ivan Artukhov
>Assignee: Ivan Pavlukhin
>Priority: Critical
>
> *Steps:*
> Start 1000 caches in 100 cache groups. Caches configuration:
> {code:xml}
> value="TRANSACTIONAL_SNAPSHOT"/>
>
>
> value="FULL_SYNC"/>
> value="READ_WRITE_SAFE"/>
> {code}
> Preload 1 keys into each cache using DataStreamer
> Run *VerifyBackupPartitionsTaskV2* to check partition inconsistencies between
> hashes or update counters
> *Expected:*
> There are no differences between primary and backup partitions
> *Actual:*
> Two or three *backup* partitions in each cache group have update counters
> which differ from corresponding primary partitions. E.g.:
> {code}
> [2019-02-07 11:04:23,286][INFO ][Task-threadNum-0] Conflict partition:
> PartitionKeyV2 [grpId=-1093321804, grpName=cache_group_100, partId=261]
> [2019-02-07 11:04:23,286][INFO ][Task-threadNum-0] Partition instances:
> [PartitionHashRecordV2 [isPrimary=true, consistentId=id-0, updateCntr=100,
> size=100, partHash=665729765], PartitionHashRecordV2 [isPrimary=false,
> consistentId=id-1, updateCntr=91, size=100, partHash=665729765],
> PartitionHashRecordV2 [isPrimary=false, consistentId=id-2, updateCntr=100,
> size=100, partHash=665729765]]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11267) Print warning when keystore password arguments are used in control.sh (bat)
[ https://issues.apache.org/jira/browse/IGNITE-11267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Kuznetsov updated IGNITE-11267: -- Affects Version/s: 2.7 > Print warning when keystore password arguments are used in control.sh (bat) > --- > > Key: IGNITE-11267 > URL: https://issues.apache.org/jira/browse/IGNITE-11267 > Project: Ignite > Issue Type: Task >Affects Versions: 2.7 >Reporter: Andrey Kuznetsov >Assignee: Andrey Kuznetsov >Priority: Minor > > Control utility gets keystore/truststore password either as command line > argument or as console input. Former way is insecure, and user should be > warned. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11267) Print warning when keystore password arguments are used in control.sh (bat)
[ https://issues.apache.org/jira/browse/IGNITE-11267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Kuznetsov updated IGNITE-11267: -- Ignite Flags: (was: Docs Required) > Print warning when keystore password arguments are used in control.sh (bat) > --- > > Key: IGNITE-11267 > URL: https://issues.apache.org/jira/browse/IGNITE-11267 > Project: Ignite > Issue Type: Task >Affects Versions: 2.7 >Reporter: Andrey Kuznetsov >Assignee: Andrey Kuznetsov >Priority: Minor > > Control utility gets keystore/truststore password either as command line > argument or as console input. Former way is insecure, and user should be > warned. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10920) Optimize HistoryAffinityAssignment heap usage.
[ https://issues.apache.org/jira/browse/IGNITE-10920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763616#comment-16763616 ] Alexey Goncharuk commented on IGNITE-10920: --- Looks good to me. > Optimize HistoryAffinityAssignment heap usage. > -- > > Key: IGNITE-10920 > URL: https://issues.apache.org/jira/browse/IGNITE-10920 > Project: Ignite > Issue Type: Improvement >Reporter: Alexei Scherbakov >Assignee: Konstantin Bolyandra >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > With large topology and large amount of caches/partitions many server > discovery events may quickly produce large affinity history, eating gigabytes > of heap. > Solution: implement some kind of a compression for affinity cache map. > On example, affinity history could be stored as delta to some previous > version. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11267) Print Warn user when keystore password arguments
Andrey Kuznetsov created IGNITE-11267: - Summary: Print Warn user when keystore password arguments Key: IGNITE-11267 URL: https://issues.apache.org/jira/browse/IGNITE-11267 Project: Ignite Issue Type: Bug Reporter: Andrey Kuznetsov -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11267) Print warning when keystore password arguments are used in control.sh (bat)
[ https://issues.apache.org/jira/browse/IGNITE-11267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Kuznetsov updated IGNITE-11267: -- Description: Control utility gets keystore/truststore password either as command line argument or as console input. Former way is insecure, and user should be warned. > Print warning when keystore password arguments are used in control.sh (bat) > --- > > Key: IGNITE-11267 > URL: https://issues.apache.org/jira/browse/IGNITE-11267 > Project: Ignite > Issue Type: Task >Reporter: Andrey Kuznetsov >Priority: Minor > > Control utility gets keystore/truststore password either as command line > argument or as console input. Former way is insecure, and user should be > warned. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11242) Update counters mismatch after loading data via DataStreamer into MVCC-enabled caches
[
https://issues.apache.org/jira/browse/IGNITE-11242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763619#comment-16763619
]
Ivan Pavlukhin commented on IGNITE-11242:
-
[~Artukhov] could you please clarify how many nodes is in cluster? How exactly
data streamer is used, how many threads stream data, from which nodes? Is there
any nodes entering to the cluster during streaming?
> Update counters mismatch after loading data via DataStreamer into
> MVCC-enabled caches
> -
>
> Key: IGNITE-11242
> URL: https://issues.apache.org/jira/browse/IGNITE-11242
> Project: Ignite
> Issue Type: Bug
> Components: mvcc, streaming
>Affects Versions: 2.7
>Reporter: Ivan Artukhov
>Assignee: Ivan Pavlukhin
>Priority: Critical
>
> *Steps:*
> Start 1000 caches in 100 cache groups. Caches configuration:
> {code:xml}
> value="TRANSACTIONAL_SNAPSHOT"/>
>
>
> value="FULL_SYNC"/>
> value="READ_WRITE_SAFE"/>
> {code}
> Preload 1 keys into each cache using DataStreamer
> Run *VerifyBackupPartitionsTaskV2* to check partition inconsistencies between
> hashes or update counters
> *Expected:*
> There are no differences between primary and backup partitions
> *Actual:*
> Two or three *backup* partitions in each cache group have update counters
> which differ from corresponding primary partitions. E.g.:
> {code}
> [2019-02-07 11:04:23,286][INFO ][Task-threadNum-0] Conflict partition:
> PartitionKeyV2 [grpId=-1093321804, grpName=cache_group_100, partId=261]
> [2019-02-07 11:04:23,286][INFO ][Task-threadNum-0] Partition instances:
> [PartitionHashRecordV2 [isPrimary=true, consistentId=id-0, updateCntr=100,
> size=100, partHash=665729765], PartitionHashRecordV2 [isPrimary=false,
> consistentId=id-1, updateCntr=91, size=100, partHash=665729765],
> PartitionHashRecordV2 [isPrimary=false, consistentId=id-2, updateCntr=100,
> size=100, partHash=665729765]]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-11267) Print warning when keystore password arguments are used in control.sh (bat)
[ https://issues.apache.org/jira/browse/IGNITE-11267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Kuznetsov reassigned IGNITE-11267: - Assignee: Andrey Kuznetsov > Print warning when keystore password arguments are used in control.sh (bat) > --- > > Key: IGNITE-11267 > URL: https://issues.apache.org/jira/browse/IGNITE-11267 > Project: Ignite > Issue Type: Task >Reporter: Andrey Kuznetsov >Assignee: Andrey Kuznetsov >Priority: Minor > > Control utility gets keystore/truststore password either as command line > argument or as console input. Former way is insecure, and user should be > warned. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11268) Unable to run control.bat or ignite.bat from Ignite source tree with compiled classes
Andrey Kuznetsov created IGNITE-11268:
-
Summary: Unable to run control.bat or ignite.bat from Ignite
source tree with compiled classes
Key: IGNITE-11268
URL: https://issues.apache.org/jira/browse/IGNITE-11268
Project: Ignite
Issue Type: Bug
Reporter: Andrey Kuznetsov
Under Windows, {{control}} and {{ignite}} scripts collect Java classpath value
from {{%IGNITE_HOME%\modules\*\target}} directories into a variable. Batch
script variable length is limited to 8k characters, and this leads to error
when there are many compiled/packaged modules in a source tree.
Possible (yet imperfect) solutions:
- Limit modules list to some minimal required sublist.
- Create Class-Path-header-only jar "on the fly".
- (Java 9+ only) Generate command-line arguments file, see [1].
[1]
https://docs.oracle.com/javase/9/tools/java.htm#JSWOR-GUID-4856361B-8BFD-4964-AE84-121F5F6CF111
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11253) When a node that is not part of the baseline topology joins the cluster, it may lead to a node failure.
[
https://issues.apache.org/jira/browse/IGNITE-11253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763636#comment-16763636
]
Ignite TC Bot commented on IGNITE-11253:
{panel:title=--> Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Service Grid (legacy mode){color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3038050]]
{color:#d04437}Cache (Restarts) 1{color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=3038010]]
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithPutFourNodesNoBackups -
0,0% fails in last 384 master runs.
{color:#d04437}ZooKeeper (Discovery) 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=3037987]]
* ZookeeperDiscoverySpiTestSuite1:
ZookeeperDiscoveryClientDisconnectTest.testReconnectServersRestart_3 - 3,8%
fails in last 286 master runs.
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3038065&buildTypeId=IgniteTests24Java8_RunAll]
> When a node that is not part of the baseline topology joins the cluster, it
> may lead to a node failure.
> ---
>
> Key: IGNITE-11253
> URL: https://issues.apache.org/jira/browse/IGNITE-11253
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Vyacheslav Koptilin
>Assignee: Vyacheslav Koptilin
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> * In case of eager TTL is configured, a starting node creates and starts
> {{cleanupWorker}} (see {{GridCacheTtlManager.start0()}})
> * {{GridCacheSharedTtlCleanupManager.CleanupWorker}}, in its turn, has to
> wait for {{discovery().localJoin()}} future that is completed by discovery
> thread.
> * On the other hand, the exchange thread stops cache contexts and,
> therefore, it stops the {{cleanupWorker}} as well.
>
> {code:java}
> org.apache.ignite.internal.processors.cache.GridCacheSharedTtlCleanupManager.stopCleanupWorker(GridCacheSharedTtlCleanupManager.java:109)
> org.apache.ignite.internal.processors.cache.GridCacheSharedTtlCleanupManager.unregister(GridCacheSharedTtlCleanupManager.java:82)
> org.apache.ignite.internal.processors.cache.GridCacheTtlManager.onKernalStop0(GridCacheTtlManager.java:110)
> org.apache.ignite.internal.processors.cache.GridCacheManagerAdapter.onKernalStop(GridCacheManagerAdapter.java:111)
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStop(GridCacheProcessor.java:1495)
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStopCaches(GridCacheProcessor.java:1182)
> org.apache.ignite.internal.processors.cache.GridCacheProcessor$CacheRecoveryLifecycle.onBaselineChange(GridCacheProcessor.java:5637)
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.initCachesOnLocalJoin(GridDhtPartitionsExchangeFuture.java:910)
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:792)
> {code}
> So, exchange thread may try to stop the {{cleanupWorker}} before the
> {{localJoin}} future is completed by discovery thread. Unfortunately,
> `cleanupWorker` incorrectly handles this situation, and this fact can lead to
> a node failure:
> {code:java}
> Critical system error detected. Will be handled accordingly to configured
> handler [hnd=StopNodeFailureHandler [super=AbstractFailureHandler
> [ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED,
> SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext
> [type=SYSTEM_WORKER_TERMINATION, err=class o.a.i.IgniteException: Got
> interrupted while waiting for future to complete.]]
> class org.apache.ignite.IgniteException: Got interrupted while waiting for
> future to complete.
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.localJoin(GridDiscoveryManager.java:2217)
> at
> org.apache.ignite.internal.processors.cache.GridCacheSharedTtlCleanupManager$CleanupWorker.body(GridCacheSharedTtlCleanupManager.java:136)
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class
> org.apache.ignite.internal.IgniteInterruptedCheckedException: Got interrupted
> while waiting for future to complete.
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:186)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:141)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.localJoin(GridDiscoveryManage
[jira] [Created] (IGNITE-11270) Batch join to topology
Vladislav Pyatkov created IGNITE-11270: -- Summary: Batch join to topology Key: IGNITE-11270 URL: https://issues.apache.org/jira/browse/IGNITE-11270 Project: Ignite Issue Type: Improvement Reporter: Vladislav Pyatkov In first cluster start many nodes will trying to join. This case leed to many time consuming join process (TcpDiscoveryJoinRequestMessage -> TcpDiscoveryNodeAddedMessage -> TcpDiscoveryNodeAddFinishedMessage). Finally, collect of topology required to much time. We can to merge some of TcpDiscoveryJoinRequestMessage and join to topology as one batch. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11269) Optimize node join to topology
Vladislav Pyatkov created IGNITE-11269: -- Summary: Optimize node join to topology Key: IGNITE-11269 URL: https://issues.apache.org/jira/browse/IGNITE-11269 Project: Ignite Issue Type: Improvement Reporter: Vladislav Pyatkov When coordinator recived TcpDiscoveryJoinRequestMessage appropriate TcpDiscoveryNodeAddedMessage had been sent in should not to process new recived TcpDiscoveryJoinRequestMessage until first joined node does not complitly joined (TcpDiscoveryNodeAddFinishedMessage was sented). This solution allow to faster join node to topology without blocking ring of huge TcpDiscoveryNodeAddedMessage's. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11255) Fix test failure after IGNITE-7648.
[ https://issues.apache.org/jira/browse/IGNITE-11255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Voronkin updated IGNITE-11255: Summary: Fix test failure after IGNITE-7648. (was: Fix test failures after IGNITE-7648.) > Fix test failure after IGNITE-7648. > --- > > Key: IGNITE-11255 > URL: https://issues.apache.org/jira/browse/IGNITE-11255 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Voronkin >Assignee: Pavel Voronkin >Priority: Major > Labels: MakeTeamcityGreenAgain > Time Spent: 10m > Remaining Estimate: 0h > > We need to fix: > > * > CacheQueriesRestartServerTest.Test_ScanQueryAfterClientReconnect_ReturnsResults(False) > * ZookeeperDiscoveryClientDisconnectTest.testReconnectServersRestart_3 > * IgniteTwoRegionsRebuildIndexTest.testRebuildIndexes > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11242) Update counters mismatch after loading data via DataStreamer into MVCC-enabled caches
[
https://issues.apache.org/jira/browse/IGNITE-11242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763709#comment-16763709
]
Ivan Artukhov commented on IGNITE-11242:
[~Pavlukhin] There was 3 server nodes and 3 client "DataStreamer" nodes each
using 8 threads to load data. Cluster topology was stable.
> Update counters mismatch after loading data via DataStreamer into
> MVCC-enabled caches
> -
>
> Key: IGNITE-11242
> URL: https://issues.apache.org/jira/browse/IGNITE-11242
> Project: Ignite
> Issue Type: Bug
> Components: mvcc, streaming
>Affects Versions: 2.7
>Reporter: Ivan Artukhov
>Assignee: Ivan Pavlukhin
>Priority: Critical
>
> *Steps:*
> Start 1000 caches in 100 cache groups. Caches configuration:
> {code:xml}
> value="TRANSACTIONAL_SNAPSHOT"/>
>
>
> value="FULL_SYNC"/>
> value="READ_WRITE_SAFE"/>
> {code}
> Preload 1 keys into each cache using DataStreamer
> Run *VerifyBackupPartitionsTaskV2* to check partition inconsistencies between
> hashes or update counters
> *Expected:*
> There are no differences between primary and backup partitions
> *Actual:*
> Two or three *backup* partitions in each cache group have update counters
> which differ from corresponding primary partitions. E.g.:
> {code}
> [2019-02-07 11:04:23,286][INFO ][Task-threadNum-0] Conflict partition:
> PartitionKeyV2 [grpId=-1093321804, grpName=cache_group_100, partId=261]
> [2019-02-07 11:04:23,286][INFO ][Task-threadNum-0] Partition instances:
> [PartitionHashRecordV2 [isPrimary=true, consistentId=id-0, updateCntr=100,
> size=100, partHash=665729765], PartitionHashRecordV2 [isPrimary=false,
> consistentId=id-1, updateCntr=91, size=100, partHash=665729765],
> PartitionHashRecordV2 [isPrimary=false, consistentId=id-2, updateCntr=100,
> size=100, partHash=665729765]]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11177) IGNITE.NODE_METRICS view fails with "Cannot parse "TIME" constant" > 24h
[
https://issues.apache.org/jira/browse/IGNITE-11177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763731#comment-16763731
]
Ignite TC Bot commented on IGNITE-11177:
{panel:title=--> Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache (Restarts) 1{color} [[tests
15|https://ci.ignite.apache.org/viewLog.html?buildId=3038288]]
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithPutFourNodesNoBackups -
0,0% fails in last 384 master runs.
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithTxFourNodesOneBackups -
0,0% fails in last 384 master runs.
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithPutTwoNodesNoBackups -
0,0% fails in last 384 master runs.
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithTxTwoNodesOneBackup -
0,0% fails in last 384 master runs.
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithPutTwoNodesOneBackup -
0,0% fails in last 384 master runs.
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithTxFourNodesOneBackupsOffheapEvict
- 0,0% fails in last 384 master runs.
* IgniteCacheRestartTestSuite:
GridCacheReplicatedNodeRestartSelfTest.testRestart - 0,0% fails in last 384
master runs.
{color:#d04437}Queries 1{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=3038319]]
* IgniteBinaryCacheQueryTestSuite:
IgniteDynamicSqlRestoreTest.testIndexCreationWhenNodeStopped - 0,0% fails in
last 399 master runs.
{color:#d04437}Spring{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3038254]]
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3038343&buildTypeId=IgniteTests24Java8_RunAll]
> IGNITE.NODE_METRICS view fails with "Cannot parse "TIME" constant" > 24h
>
>
> Key: IGNITE-11177
> URL: https://issues.apache.org/jira/browse/IGNITE-11177
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.7
>Reporter: Ilya Kasnacheev
>Assignee: Pavel Kuznetsov
>Priority: Major
> Labels: metrics
> Fix For: 2.8
>
>
> This is because we are using TIME type for several additive measurements:
> {quote}SqlSystemViewNodeMetrics.class:
>
> valueTimeFromMillis(metrics.getTotalJobsExecutionTime()),
> valueTimeFromMillis(metrics.getTotalBusyTime()),
>
> valueTimeFromMillis(metrics.getTotalIdleTime()),{quote}
> which will be hundreds of hours on long-running cluster, but {{TIME}} type is
> limited to 24 hours and will fail to be converted otherwise, as in:
> {quote}0: jdbc:ignite:thin://localhost> SELECT CAST('40:52:26.548' AS TIME);
> Error: Failed to parse query. Невозможно преобразование строки "40:52:26.548"
> в тип "TIME"
> Cannot parse "TIME" constant "40:52:26.548"; SQL statement:
> SELECT CAST('40:52:26.548' AS TIME) [22007-197] (state=42000,code=1001){quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11271) Investigate setting discardCustomMsgId to null in prepareNodeAddedMessage
Alexey Goncharuk created IGNITE-11271: - Summary: Investigate setting discardCustomMsgId to null in prepareNodeAddedMessage Key: IGNITE-11271 URL: https://issues.apache.org/jira/browse/IGNITE-11271 Project: Ignite Issue Type: Improvement Reporter: Alexey Goncharuk >From debugging IGNITE-10935 it was discovered that NodeAddedMessage contains >wrong state: pending messages are already filtered out by discard ID, but at >the same time discardId and customDiscardId are set to non-null values. This >resulted in a broken pending messages iterator on a newly added node: >SkipIterator was skipping all pending messages until a valid discardId was >received. The fix made in IGNITE-10935 was incomplete because we should have set both discardId and customDiscardId to null. However, after running TC tests it turned out that setting discardCustomMsgId to null resulted in duplicate custom events (the particular failed test is AuthenticationProcessorNodeRestartTest#testConcurrentAddUpdateRemoveNodeRestartServer) The reason behind the failed test is that some of the fired custom events are delivered multiple times. This should be investigated. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11271) Investigate setting discardCustomMsgId to null in prepareNodeAddedMessage
[ https://issues.apache.org/jira/browse/IGNITE-11271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-11271: -- Fix Version/s: 2.8 > Investigate setting discardCustomMsgId to null in prepareNodeAddedMessage > - > > Key: IGNITE-11271 > URL: https://issues.apache.org/jira/browse/IGNITE-11271 > Project: Ignite > Issue Type: Improvement >Reporter: Alexey Goncharuk >Priority: Major > Fix For: 2.8 > > > From debugging IGNITE-10935 it was discovered that NodeAddedMessage contains > wrong state: pending messages are already filtered out by discard ID, but at > the same time discardId and customDiscardId are set to non-null values. This > resulted in a broken pending messages iterator on a newly added node: > SkipIterator was skipping all pending messages until a valid discardId was > received. > The fix made in IGNITE-10935 was incomplete because we should have set both > discardId and customDiscardId to null. However, after running TC tests it > turned out that setting discardCustomMsgId to null resulted in duplicate > custom events (the particular failed test is > AuthenticationProcessorNodeRestartTest#testConcurrentAddUpdateRemoveNodeRestartServer) > The reason behind the failed test is that some of the fired custom events are > delivered multiple times. This should be investigated. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11272) Investigate race between local node promotion to the first node in topology and NodeAddedMessage
Alexey Goncharuk created IGNITE-11272:
-
Summary: Investigate race between local node promotion to the
first node in topology and NodeAddedMessage
Key: IGNITE-11272
URL: https://issues.apache.org/jira/browse/IGNITE-11272
Project: Ignite
Issue Type: Improvement
Reporter: Alexey Goncharuk
The following race is possible - a node sends join request, succeeds, but does
not receive {{NodeAddFinishedMessage}} on time, after that due to a short-time
connection break it fails to send join request and decides to promote itself to
a first node in the topology. At the same time, the network may be restored and
{{NodeAddedMessage}} may be received by the local node. The behavior is
currently undefined.
This should be tested and fixed if needed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11247) MVCC: Tests has been forgotten to unmute.
[
https://issues.apache.org/jira/browse/IGNITE-11247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763789#comment-16763789
]
Ignite TC Bot commented on IGNITE-11247:
{panel:title=--> Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}ZooKeeper (Discovery) 1{color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=3039183]]
* ZookeeperDiscoverySpiTestSuite1:
ZookeeperDiscoveryClientDisconnectTest.testReconnectServersRestart_3 - 3,8%
fails in last 286 master runs.
{color:#d04437}MVCC Queries{color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=3037754]]
* IgniteCacheMvccSqlTestSuite:
CacheMvccPartitionedSqlCoordinatorFailoverTest.testAccountsTxSql_SingleNode_CoordinatorFails_Persistence
- 0,0% fails in last 0 master runs.
* IgniteCacheMvccSqlTestSuite:
CacheMvccReplicatedSqlCoordinatorFailoverTest.testAccountsTxSql_SingleNode_CoordinatorFails_Persistence
- 0,0% fails in last 0 master runs.
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3037821&buildTypeId=IgniteTests24Java8_RunAll]
> MVCC: Tests has been forgotten to unmute.
> -
>
> Key: IGNITE-11247
> URL: https://issues.apache.org/jira/browse/IGNITE-11247
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
>Priority: Major
> Labels: MakeTeamcityGreenAgain, mvcc_stabilization_stage_1
> Time Spent: 10m
> Remaining Estimate: 0h
>
> There are muted\ignored tests that are not being run on TC, but tickets for
> fixing them looks already resolved.
> Let's recheck those tests and either unmute them or create a new tickets to
> fix lately if needed.
> IgniteBasicWithPersistenceTestSuite
> * testIoomErrorMvccPdsHandling - IGNITE-10185
> IgniteCacheMvccSqlTestSuite
> * testSqlReadInsideTxInProgressCoordinatorFails - IGNITE-8841
> * testSqlReadInsideTxInProgressCoordinatorFails_ReadDelay - IGNITE-8841
> *
> testPutAllGetAll_ClientServer_Backups1_SinglePartition_RestartRandomSrv_SqlDml
> - IGNITE-10752
> * testAccountsTxSql_SingleNode_CoordinatorFails_Persistence - IGNITE-10753
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11273) IgniteCassandraStoreTestSuite failed under Java 11
Dmitriy Pavlov created IGNITE-11273:
---
Summary: IgniteCassandraStoreTestSuite failed under Java 11
Key: IGNITE-11273
URL: https://issues.apache.org/jira/browse/IGNITE-11273
Project: Ignite
Issue Type: Bug
Reporter: Dmitriy Pavlov
https://ci.ignite.apache.org/viewLog.html?buildId=3027678&buildTypeId=IgniteTests24Java8_CassandraStore
store.IgniteCassandraStoreTestSuite
{noformat}
java.lang.RuntimeException: Failed to start embedded Cassandra instance
at
org.apache.ignite.testsuites.cassandra.store.IgniteCassandraStoreTestSuite.setUpClass(IgniteCassandraStoreTestSuite.java:59)
Caused by: java.lang.ExceptionInInitializerError
at
org.apache.ignite.testsuites.cassandra.store.IgniteCassandraStoreTestSuite.setUpClass(IgniteCassandraStoreTestSuite.java:56)
Caused by: java.lang.StringIndexOutOfBoundsException: begin 0, end -1, length 5
at
org.apache.ignite.testsuites.cassandra.store.IgniteCassandraStoreTestSuite.setUpClass(IgniteCassandraStoreTestSuite.java:56)
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-11100) AssertionError LocalJoinCachesContext occurs in sequential cluster restart
[
https://issues.apache.org/jira/browse/IGNITE-11100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk resolved IGNITE-11100.
---
Resolution: Duplicate
> AssertionError LocalJoinCachesContext occurs in sequential cluster restart
> --
>
> Key: IGNITE-11100
> URL: https://issues.apache.org/jira/browse/IGNITE-11100
> Project: Ignite
> Issue Type: Bug
>Reporter: Dmitry Sherstobitov
>Assignee: Alexey Goncharuk
>Priority: Critical
>
> Same scenario as in https://issues.apache.org/jira/browse/IGNITE-10878
> {code}
> [2019-01-26T03:32:22,226][ERROR][tcp-disco-msg-worker-#2][TcpDiscoverySpi]
> TcpDiscoverSpi's message worker thread failed abnormally. Stopping the node
> in order to prevent cluster wide instability.
> java.lang.AssertionError: LocalJoinCachesContext
> [locJoinStartCaches=[IgniteBiTuple [val1=DynamicCacheDescriptor
> [deploymentId=bc3e0978861-fb98885f-92a5-47d2-9475-00173fab8ee1,
> staticCfg=true, sql=false, cacheType=UTILITY, template=false,
> updatesAllowed=true, cacheId=-2100569601,
> rcvdFrom=f97e4743-6cf2-488e-a7fc-14707e9a8eb0, objCtx=null,
> rcvdOnDiscovery=false, startTopVer=null, rcvdFromVer=null,
> clientCacheStartVer=null, schema=QuerySchema [], grpDesc=CacheGroupDescriptor
> [grpId=-2100569601, grpName=null, startTopVer=null,
> rcvdFrom=f97e4743-6cf2-488e-a7fc-14707e9a8eb0,
> deploymentId=bc3e0978861-fb98885f-92a5-47d2-9475-00173fab8ee1,
> caches={ignite-sys-cache=-2100569601}, rcvdFromVer=null,
> persistenceEnabled=false, walEnabled=false, cacheName=ignite-sys-cache],
> cacheName=ignite-sys-cache], val2=null], IgniteBiTuple
> [val1=DynamicCacheDescriptor
> [deploymentId=60771978861-398164df-6240-4d19-ad0b-308768d2a095,
> staticCfg=false, sql=false, cacheType=USER, template=false,
> updatesAllowed=true, cacheId=-1901084566,
> rcvdFrom=f00ec506-fc6c-45c5-b550-9308d17a39cf, objCtx=null,
> rcvdOnDiscovery=true, startTopVer=null, rcvdFromVer=null,
> clientCacheStartVer=null, schema=QuerySchema [], grpDesc=CacheGroupDescriptor
> [grpId=-1901084566, grpName=null, startTopVer=AffinityTopologyVersion
> [topVer=13, minorTopVer=20], rcvdFrom=f00ec506-fc6c-45c5-b550-9308d17a39cf,
> deploymentId=60771978861-398164df-6240-4d19-ad0b-308768d2a095,
> caches={config_third_copy=-1901084566}, rcvdFromVer=null,
> persistenceEnabled=false, walEnabled=false, cacheName=config_third_copy],
> cacheName=config_third_copy], val2=null], IgniteBiTuple
> [val1=DynamicCacheDescriptor
> [deploymentId=01771978861-398164df-6240-4d19-ad0b-308768d2a095,
> staticCfg=false, sql=false, cacheType=USER, template=false,
> updatesAllowed=true, cacheId=-1858528402,
> rcvdFrom=f00ec506-fc6c-45c5-b550-9308d17a39cf, objCtx=null,
> rcvdOnDiscovery=true, startTopVer=null, rcvdFromVer=null,
> clientCacheStartVer=null, schema=QuerySchema [], grpDesc=CacheGroupDescriptor
> [grpId=-1858528402, grpName=null, startTopVer=AffinityTopologyVersion
> [topVer=13, minorTopVer=22], rcvdFrom=f00ec506-fc6c-45c5-b550-9308d17a39cf,
> deploymentId=01771978861-398164df-6240-4d19-ad0b-308768d2a095,
> caches={trans_forth_copy=-1858528402}, rcvdFromVer=null,
> persistenceEnabled=false, walEnabled=false, cacheName=trans_forth_copy],
> cacheName=trans_forth_copy], val2=null], IgniteBiTuple
> [val1=DynamicCacheDescriptor
> [deploymentId=51771978861-398164df-6240-4d19-ad0b-308768d2a095,
> staticCfg=false, sql=false, cacheType=USER, template=false,
> updatesAllowed=true, cacheId=-1502999781,
> rcvdFrom=f00ec506-fc6c-45c5-b550-9308d17a39cf, objCtx=null,
> rcvdOnDiscovery=true, startTopVer=null, rcvdFromVer=null,
> clientCacheStartVer=null, schema=QuerySchema [], grpDesc=CacheGroupDescriptor
> [grpId=-1502999781, grpName=null, startTopVer=AffinityTopologyVersion
> [topVer=13, minorTopVer=23], rcvdFrom=f00ec506-fc6c-45c5-b550-9308d17a39cf,
> deploymentId=51771978861-398164df-6240-4d19-ad0b-308768d2a095,
> caches={id_forth_copy=-1502999781}, rcvdFromVer=null,
> persistenceEnabled=false, walEnabled=false, cacheName=id_forth_copy],
> cacheName=id_forth_copy], val2=null], IgniteBiTuple
> [val1=DynamicCacheDescriptor
> [deploymentId=8a671978861-398164df-6240-4d19-ad0b-308768d2a095,
> staticCfg=false, sql=false, cacheType=USER, template=false,
> updatesAllowed=true, cacheId=-1354792126,
> rcvdFrom=f00ec506-fc6c-45c5-b550-9308d17a39cf, objCtx=null,
> rcvdOnDiscovery=true, startTopVer=null, rcvdFromVer=null,
> clientCacheStartVer=null, schema=QuerySchema [], grpDesc=CacheGroupDescriptor
> [grpId=-1354792126, grpName=null, startTopVer=AffinityTopologyVersion
> [topVer=13, minorTopVer=5], rcvdFrom=f00ec506-fc6c-45c5-b550-9308d17a39cf,
> deploymentId=8a671978861-398164df-6240-4d19-ad0b-308768d2a095,
> caches={config=-1354792126}, rcvdFromVer=null, persistenceEnabled=fals
[jira] [Updated] (IGNITE-11100) AssertionError LocalJoinCachesContext occurs in sequential cluster restart
[
https://issues.apache.org/jira/browse/IGNITE-11100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-11100:
--
Ignite Flags: (was: Docs Required)
> AssertionError LocalJoinCachesContext occurs in sequential cluster restart
> --
>
> Key: IGNITE-11100
> URL: https://issues.apache.org/jira/browse/IGNITE-11100
> Project: Ignite
> Issue Type: Bug
>Reporter: Dmitry Sherstobitov
>Assignee: Alexey Goncharuk
>Priority: Critical
>
> Same scenario as in https://issues.apache.org/jira/browse/IGNITE-10878
> {code}
> [2019-01-26T03:32:22,226][ERROR][tcp-disco-msg-worker-#2][TcpDiscoverySpi]
> TcpDiscoverSpi's message worker thread failed abnormally. Stopping the node
> in order to prevent cluster wide instability.
> java.lang.AssertionError: LocalJoinCachesContext
> [locJoinStartCaches=[IgniteBiTuple [val1=DynamicCacheDescriptor
> [deploymentId=bc3e0978861-fb98885f-92a5-47d2-9475-00173fab8ee1,
> staticCfg=true, sql=false, cacheType=UTILITY, template=false,
> updatesAllowed=true, cacheId=-2100569601,
> rcvdFrom=f97e4743-6cf2-488e-a7fc-14707e9a8eb0, objCtx=null,
> rcvdOnDiscovery=false, startTopVer=null, rcvdFromVer=null,
> clientCacheStartVer=null, schema=QuerySchema [], grpDesc=CacheGroupDescriptor
> [grpId=-2100569601, grpName=null, startTopVer=null,
> rcvdFrom=f97e4743-6cf2-488e-a7fc-14707e9a8eb0,
> deploymentId=bc3e0978861-fb98885f-92a5-47d2-9475-00173fab8ee1,
> caches={ignite-sys-cache=-2100569601}, rcvdFromVer=null,
> persistenceEnabled=false, walEnabled=false, cacheName=ignite-sys-cache],
> cacheName=ignite-sys-cache], val2=null], IgniteBiTuple
> [val1=DynamicCacheDescriptor
> [deploymentId=60771978861-398164df-6240-4d19-ad0b-308768d2a095,
> staticCfg=false, sql=false, cacheType=USER, template=false,
> updatesAllowed=true, cacheId=-1901084566,
> rcvdFrom=f00ec506-fc6c-45c5-b550-9308d17a39cf, objCtx=null,
> rcvdOnDiscovery=true, startTopVer=null, rcvdFromVer=null,
> clientCacheStartVer=null, schema=QuerySchema [], grpDesc=CacheGroupDescriptor
> [grpId=-1901084566, grpName=null, startTopVer=AffinityTopologyVersion
> [topVer=13, minorTopVer=20], rcvdFrom=f00ec506-fc6c-45c5-b550-9308d17a39cf,
> deploymentId=60771978861-398164df-6240-4d19-ad0b-308768d2a095,
> caches={config_third_copy=-1901084566}, rcvdFromVer=null,
> persistenceEnabled=false, walEnabled=false, cacheName=config_third_copy],
> cacheName=config_third_copy], val2=null], IgniteBiTuple
> [val1=DynamicCacheDescriptor
> [deploymentId=01771978861-398164df-6240-4d19-ad0b-308768d2a095,
> staticCfg=false, sql=false, cacheType=USER, template=false,
> updatesAllowed=true, cacheId=-1858528402,
> rcvdFrom=f00ec506-fc6c-45c5-b550-9308d17a39cf, objCtx=null,
> rcvdOnDiscovery=true, startTopVer=null, rcvdFromVer=null,
> clientCacheStartVer=null, schema=QuerySchema [], grpDesc=CacheGroupDescriptor
> [grpId=-1858528402, grpName=null, startTopVer=AffinityTopologyVersion
> [topVer=13, minorTopVer=22], rcvdFrom=f00ec506-fc6c-45c5-b550-9308d17a39cf,
> deploymentId=01771978861-398164df-6240-4d19-ad0b-308768d2a095,
> caches={trans_forth_copy=-1858528402}, rcvdFromVer=null,
> persistenceEnabled=false, walEnabled=false, cacheName=trans_forth_copy],
> cacheName=trans_forth_copy], val2=null], IgniteBiTuple
> [val1=DynamicCacheDescriptor
> [deploymentId=51771978861-398164df-6240-4d19-ad0b-308768d2a095,
> staticCfg=false, sql=false, cacheType=USER, template=false,
> updatesAllowed=true, cacheId=-1502999781,
> rcvdFrom=f00ec506-fc6c-45c5-b550-9308d17a39cf, objCtx=null,
> rcvdOnDiscovery=true, startTopVer=null, rcvdFromVer=null,
> clientCacheStartVer=null, schema=QuerySchema [], grpDesc=CacheGroupDescriptor
> [grpId=-1502999781, grpName=null, startTopVer=AffinityTopologyVersion
> [topVer=13, minorTopVer=23], rcvdFrom=f00ec506-fc6c-45c5-b550-9308d17a39cf,
> deploymentId=51771978861-398164df-6240-4d19-ad0b-308768d2a095,
> caches={id_forth_copy=-1502999781}, rcvdFromVer=null,
> persistenceEnabled=false, walEnabled=false, cacheName=id_forth_copy],
> cacheName=id_forth_copy], val2=null], IgniteBiTuple
> [val1=DynamicCacheDescriptor
> [deploymentId=8a671978861-398164df-6240-4d19-ad0b-308768d2a095,
> staticCfg=false, sql=false, cacheType=USER, template=false,
> updatesAllowed=true, cacheId=-1354792126,
> rcvdFrom=f00ec506-fc6c-45c5-b550-9308d17a39cf, objCtx=null,
> rcvdOnDiscovery=true, startTopVer=null, rcvdFromVer=null,
> clientCacheStartVer=null, schema=QuerySchema [], grpDesc=CacheGroupDescriptor
> [grpId=-1354792126, grpName=null, startTopVer=AffinityTopologyVersion
> [topVer=13, minorTopVer=5], rcvdFrom=f00ec506-fc6c-45c5-b550-9308d17a39cf,
> deploymentId=8a671978861-398164df-6240-4d19-ad0b-308768d2a095,
> caches={config=-1354792126}, rcvdFromVer=null, persistenc
[jira] [Assigned] (IGNITE-11100) AssertionError LocalJoinCachesContext occurs in sequential cluster restart
[
https://issues.apache.org/jira/browse/IGNITE-11100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk reassigned IGNITE-11100:
-
Assignee: Alexey Goncharuk
> AssertionError LocalJoinCachesContext occurs in sequential cluster restart
> --
>
> Key: IGNITE-11100
> URL: https://issues.apache.org/jira/browse/IGNITE-11100
> Project: Ignite
> Issue Type: Bug
>Reporter: Dmitry Sherstobitov
>Assignee: Alexey Goncharuk
>Priority: Critical
>
> Same scenario as in https://issues.apache.org/jira/browse/IGNITE-10878
> {code}
> [2019-01-26T03:32:22,226][ERROR][tcp-disco-msg-worker-#2][TcpDiscoverySpi]
> TcpDiscoverSpi's message worker thread failed abnormally. Stopping the node
> in order to prevent cluster wide instability.
> java.lang.AssertionError: LocalJoinCachesContext
> [locJoinStartCaches=[IgniteBiTuple [val1=DynamicCacheDescriptor
> [deploymentId=bc3e0978861-fb98885f-92a5-47d2-9475-00173fab8ee1,
> staticCfg=true, sql=false, cacheType=UTILITY, template=false,
> updatesAllowed=true, cacheId=-2100569601,
> rcvdFrom=f97e4743-6cf2-488e-a7fc-14707e9a8eb0, objCtx=null,
> rcvdOnDiscovery=false, startTopVer=null, rcvdFromVer=null,
> clientCacheStartVer=null, schema=QuerySchema [], grpDesc=CacheGroupDescriptor
> [grpId=-2100569601, grpName=null, startTopVer=null,
> rcvdFrom=f97e4743-6cf2-488e-a7fc-14707e9a8eb0,
> deploymentId=bc3e0978861-fb98885f-92a5-47d2-9475-00173fab8ee1,
> caches={ignite-sys-cache=-2100569601}, rcvdFromVer=null,
> persistenceEnabled=false, walEnabled=false, cacheName=ignite-sys-cache],
> cacheName=ignite-sys-cache], val2=null], IgniteBiTuple
> [val1=DynamicCacheDescriptor
> [deploymentId=60771978861-398164df-6240-4d19-ad0b-308768d2a095,
> staticCfg=false, sql=false, cacheType=USER, template=false,
> updatesAllowed=true, cacheId=-1901084566,
> rcvdFrom=f00ec506-fc6c-45c5-b550-9308d17a39cf, objCtx=null,
> rcvdOnDiscovery=true, startTopVer=null, rcvdFromVer=null,
> clientCacheStartVer=null, schema=QuerySchema [], grpDesc=CacheGroupDescriptor
> [grpId=-1901084566, grpName=null, startTopVer=AffinityTopologyVersion
> [topVer=13, minorTopVer=20], rcvdFrom=f00ec506-fc6c-45c5-b550-9308d17a39cf,
> deploymentId=60771978861-398164df-6240-4d19-ad0b-308768d2a095,
> caches={config_third_copy=-1901084566}, rcvdFromVer=null,
> persistenceEnabled=false, walEnabled=false, cacheName=config_third_copy],
> cacheName=config_third_copy], val2=null], IgniteBiTuple
> [val1=DynamicCacheDescriptor
> [deploymentId=01771978861-398164df-6240-4d19-ad0b-308768d2a095,
> staticCfg=false, sql=false, cacheType=USER, template=false,
> updatesAllowed=true, cacheId=-1858528402,
> rcvdFrom=f00ec506-fc6c-45c5-b550-9308d17a39cf, objCtx=null,
> rcvdOnDiscovery=true, startTopVer=null, rcvdFromVer=null,
> clientCacheStartVer=null, schema=QuerySchema [], grpDesc=CacheGroupDescriptor
> [grpId=-1858528402, grpName=null, startTopVer=AffinityTopologyVersion
> [topVer=13, minorTopVer=22], rcvdFrom=f00ec506-fc6c-45c5-b550-9308d17a39cf,
> deploymentId=01771978861-398164df-6240-4d19-ad0b-308768d2a095,
> caches={trans_forth_copy=-1858528402}, rcvdFromVer=null,
> persistenceEnabled=false, walEnabled=false, cacheName=trans_forth_copy],
> cacheName=trans_forth_copy], val2=null], IgniteBiTuple
> [val1=DynamicCacheDescriptor
> [deploymentId=51771978861-398164df-6240-4d19-ad0b-308768d2a095,
> staticCfg=false, sql=false, cacheType=USER, template=false,
> updatesAllowed=true, cacheId=-1502999781,
> rcvdFrom=f00ec506-fc6c-45c5-b550-9308d17a39cf, objCtx=null,
> rcvdOnDiscovery=true, startTopVer=null, rcvdFromVer=null,
> clientCacheStartVer=null, schema=QuerySchema [], grpDesc=CacheGroupDescriptor
> [grpId=-1502999781, grpName=null, startTopVer=AffinityTopologyVersion
> [topVer=13, minorTopVer=23], rcvdFrom=f00ec506-fc6c-45c5-b550-9308d17a39cf,
> deploymentId=51771978861-398164df-6240-4d19-ad0b-308768d2a095,
> caches={id_forth_copy=-1502999781}, rcvdFromVer=null,
> persistenceEnabled=false, walEnabled=false, cacheName=id_forth_copy],
> cacheName=id_forth_copy], val2=null], IgniteBiTuple
> [val1=DynamicCacheDescriptor
> [deploymentId=8a671978861-398164df-6240-4d19-ad0b-308768d2a095,
> staticCfg=false, sql=false, cacheType=USER, template=false,
> updatesAllowed=true, cacheId=-1354792126,
> rcvdFrom=f00ec506-fc6c-45c5-b550-9308d17a39cf, objCtx=null,
> rcvdOnDiscovery=true, startTopVer=null, rcvdFromVer=null,
> clientCacheStartVer=null, schema=QuerySchema [], grpDesc=CacheGroupDescriptor
> [grpId=-1354792126, grpName=null, startTopVer=AffinityTopologyVersion
> [topVer=13, minorTopVer=5], rcvdFrom=f00ec506-fc6c-45c5-b550-9308d17a39cf,
> deploymentId=8a671978861-398164df-6240-4d19-ad0b-308768d2a095,
> caches={config=-1354792126}, rcvdFromVer=null, persistenceEn
