[jira] [Commented] (IGNITE-8789) Add a call to the FailureHandler for an error with meta-data.
[
https://issues.apache.org/jira/browse/IGNITE-8789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16515716#comment-16515716
]
Andrey Gura commented on IGNITE-8789:
-
Fixed. TC run^
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8_IgniteTests24Java8=pull%2F4204%2Fhead
> Add a call to the FailureHandler for an error with meta-data.
> -
>
> Key: IGNITE-8789
> URL: https://issues.apache.org/jira/browse/IGNITE-8789
> Project: Ignite
> Issue Type: Improvement
>Reporter: Dmitriy Gladkikh
>Assignee: Andrey Gura
>Priority: Critical
> Fix For: 2.6
>
>
> This is a critical situation, corresponding exception should be propagated to
> handler to make necessary actions.
> Need to add a call to the FailureHandler if the specified error occurs.
> When processing a message in the GridCacheIoManager#onMessage0 method, an
> exception was thrown: Failed to process message
> [senderId=f815a46c-8973-4cda-ac77-51325e731cda, messageType=class
> o.a.i.i.processors.cache.distributed.near.GridNearTxFinishRequest]
> An error occurred during the error logging associated with the meta-data:
> Cannot find schema for object with compact footer [typeId=1599442645,
> schemaId=-1705721149]
> The original exception was lost.
> {code:java}
> 2018-06-13
> 09:04:01.593[ERROR][sys-stripe-22-#23%DPL_GRID%DplGridNodeName%][o.a.i.i.p.cache.GridCacheIoManager]
> Failed to process message [senderId=f815a46c-8973-4cda-ac77-51325e731cda,
> messageType=class
> o.a.i.i.processors.cache.distributed.near.GridNearTxFinishRequest]
> org.apache.ignite.IgniteException: Failed to create string representation of
> binary object.
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1028)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:826)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:783)
> at
> org.apache.ignite.internal.processors.cache.distributed.GridDistributedTxFinishRequest.toString(GridDistributedTxFinishRequest.java:561)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxFinishRequest.toString(GridNearTxFinishRequest.java:221)
> at java.lang.String.valueOf(String.java:2994)
> at java.lang.StringBuilder.append(StringBuilder.java:131)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1060)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:579)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:378)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:304)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:99)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:293)
> 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.communication.GridIoManager.access$4200(GridIoManager.java:125)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1091)
> at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.run(StripedExecutor.java:511)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.apache.ignite.IgniteException: Failed to create string
> representation of binary object.
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1028)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:826)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:783)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxStateImpl.toString(IgniteTxStateImpl.java:466)
> at java.lang.String.valueOf(String.java:2994)
> at
> org.apache.ignite.internal.util.GridStringBuilder.a(GridStringBuilder.java:101)
> at
> org.apache.ignite.internal.util.tostring.SBLimitedLength.a(SBLimitedLength.java:88)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:939)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1005)
> ... 18 common frames omitted
> Caused by: org.apache.ignite.IgniteException: Failed to create string
> representation
[jira] [Commented] (IGNITE-8749) Exception for "no space left" situation should be propagated to FailureHandler
[ https://issues.apache.org/jira/browse/IGNITE-8749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16515578#comment-16515578 ] Andrey Gura commented on IGNITE-8749: - [~cyberdemon] LGTM. Merged to master branch. Thanks for contribution! > Exception for "no space left" situation should be propagated to FailureHandler > -- > > Key: IGNITE-8749 > URL: https://issues.apache.org/jira/browse/IGNITE-8749 > Project: Ignite > Issue Type: Improvement > Components: persistence >Reporter: Sergey Chugunov >Assignee: Dmitriy Sorokin >Priority: Major > Fix For: 2.6 > > > For now if "no space left" situation is detected in > FileWriteAheadLogManager#formatFile method and corresponding exception is > thrown the exception doesn't get propagated to FailureHandler and node > continues working. > As "no space left" is a critical situation, corresponding exception should be > propagated to handler to make necessary actions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-4210) CacheLoadingConcurrentGridStartSelfTest.testLoadCacheFromStore() test lose data.
[ https://issues.apache.org/jira/browse/IGNITE-4210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16515567#comment-16515567 ] Andrey Gura commented on IGNITE-4210: - [~Alexey Kuznetsov] I think we should cancel cache store loading in mentioned cases. > CacheLoadingConcurrentGridStartSelfTest.testLoadCacheFromStore() test lose > data. > > > Key: IGNITE-4210 > URL: https://issues.apache.org/jira/browse/IGNITE-4210 > Project: Ignite > Issue Type: Bug >Reporter: Anton Vinogradov >Assignee: Alexey Kuznetsov >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.6 > > > org.apache.ignite.internal.processors.cache.distributed.CacheLoadingConcurrentGridStartSelfTest#testLoadCacheFromStore > sometimes have failures. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8562) Turn system-critical Ignite threads into GridWorkers
[
https://issues.apache.org/jira/browse/IGNITE-8562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16515551#comment-16515551
]
Andrey Gura commented on IGNITE-8562:
-
[~andrey-kuznetsov] LGTM. Merged to master branch. Thanks for contribution!
> Turn system-critical Ignite threads into GridWorkers
>
>
> Key: IGNITE-8562
> URL: https://issues.apache.org/jira/browse/IGNITE-8562
> Project: Ignite
> Issue Type: Improvement
>Reporter: Andrey Kuznetsov
>Assignee: Andrey Kuznetsov
>Priority: Major
> Fix For: 2.6
>
>
> The goal of the change is to make system-critical threads (in terms of
> IEP-14, [1]) available to {{WorkersControlMXBean}}.
> [1]
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-14+Ignite+failures+handling
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8763) java.nio.file.AccessDeniedException is not handled with default failure handler
[
https://issues.apache.org/jira/browse/IGNITE-8763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16512820#comment-16512820
]
Andrey Gura commented on IGNITE-8763:
-
[~alex_pl] LGTM! Merged to master branch. Thanks for contribution!
> java.nio.file.AccessDeniedException is not handled with default failure
> handler
> ---
>
> Key: IGNITE-8763
> URL: https://issues.apache.org/jira/browse/IGNITE-8763
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Andrey Gura
>Assignee: Aleksey Plekhanov
>Priority: Major
> Fix For: 2.6
>
>
> java.nio.file.AccessDeniedException is not handled with default failure
> handler
> 1. Start cluster(4 nodes).
> 2. Upload some data.
> 3. Make files in metastore read only.
> 4. Deactivate grid.
> 5. Activate grid.
> On this step I see java.nio.file.AccessDeniedException:
> {noformat}
> [17:55:40,035][INFO][exchange-worker-#62][GridCacheDatabaseSharedManager]
> Read checkpoint status
> [startMarker=/storage/ssd/avolkov/tiden/iep_14-180517-175425/test_iep_14/ignite.server.1/work/db/node1/cp/1526568907638-46128a87-562a-45fc-8d73-75ccb1490d63-START.bin,
>
> endMarker=/storage/ssd/avolkov/tiden/iep_14-180517-175425/test_iep_14/ignite.server.1/work/db/node1/cp/1526568907638-46128a87-562a-45fc-8d73-75ccb1490d63-END.bin]
> [17:55:40,037][SEVERE][exchange-worker-#62][GridDhtPartitionsExchangeFuture]
> Failed to activate node components
> [nodeId=bd7115d5-1f95-4673-9f40-47056b0b1a58, client=false,
> topVer=AffinityTopologyVersion [topVer=4, minorTopVer=5]]
> class org.apache.ignite.IgniteCheckedException: Error while creating file
> page store
> [file=/storage/ssd/avolkov/tiden/iep_14-180517-175425/test_iep_14/ignite.server.1/work/db/node1/metastorage/part-0.bin]:
> at
> org.apache.ignite.internal.processors.cache.persistence.file.FileVersionCheckingFactory.createPageStore(FileVersionCheckingFactory.java:98)
> at
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.initDir(FilePageStoreManager.java:463)
> at
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.initializeForMetastorage(FilePageStoreManager.java:234)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.readCheckpointAndRestoreMemory(GridCacheDatabaseSharedManager.java:743)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onClusterStateChangeRequest(GridDhtPartitionsExchangeFuture.java:896)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:643)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2419)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2299)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.nio.file.AccessDeniedException:
> /storage/ssd/avolkov/tiden/iep_14-180517-175425/test_iep_14/ignite.server.1/work/db/node1/metastorage/part-0.bin
> at
> sun.nio.fs.UnixException.translateToIOException(UnixException.java:84)
> at
> sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
> at
> sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
> at
> sun.nio.fs.UnixFileSystemProvider.newAsynchronousFileChannel(UnixFileSystemProvider.java:196)
> at
> java.nio.channels.AsynchronousFileChannel.open(AsynchronousFileChannel.java:248)
> at
> java.nio.channels.AsynchronousFileChannel.open(AsynchronousFileChannel.java:301)
> at
> org.apache.ignite.internal.processors.cache.persistence.file.AsyncFileIO.(AsyncFileIO.java:57)
> at
> org.apache.ignite.internal.processors.cache.persistence.file.AsyncFileIOFactory.create(AsyncFileIOFactory.java:53)
> at
> org.apache.ignite.internal.processors.cache.persistence.file.AsyncFileIOFactory.create(AsyncFileIOFactory.java:41)
> at
> org.apache.ignite.internal.processors.cache.persistence.file.FileVersionCheckingFactory.createPageStore(FileVersionCheckingFactory.java:78)
> ... 9 more
> {noformat}
> Situation led to NPE exception after AccessDeniedException looks like this:
> 1. AccessDeniedException was thrown in ExchangeFuture right before affinity
> initialization so affinity was never initialized.
> 2. After that node receives PartitionSingleMessage and tries to
[jira] [Assigned] (IGNITE-8789) Add a call to the FailureHandler for an error with meta-data.
[
https://issues.apache.org/jira/browse/IGNITE-8789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura reassigned IGNITE-8789:
---
Assignee: Andrey Gura
> Add a call to the FailureHandler for an error with meta-data.
> -
>
> Key: IGNITE-8789
> URL: https://issues.apache.org/jira/browse/IGNITE-8789
> Project: Ignite
> Issue Type: Improvement
>Reporter: Dmitriy Gladkikh
>Assignee: Andrey Gura
>Priority: Critical
> Fix For: 2.6
>
>
> This is a critical situation, corresponding exception should be propagated to
> handler to make necessary actions.
> Need to add a call to the FailureHandler if the specified error occurs.
> When processing a message in the GridCacheIoManager#onMessage0 method, an
> exception was thrown: Failed to process message
> [senderId=f815a46c-8973-4cda-ac77-51325e731cda, messageType=class
> o.a.i.i.processors.cache.distributed.near.GridNearTxFinishRequest]
> An error occurred during the error logging associated with the meta-data:
> Cannot find schema for object with compact footer [typeId=1599442645,
> schemaId=-1705721149]
> The original exception was lost.
> {code:java}
> 2018-06-13
> 09:04:01.593[ERROR][sys-stripe-22-#23%DPL_GRID%DplGridNodeName%][o.a.i.i.p.cache.GridCacheIoManager]
> Failed to process message [senderId=f815a46c-8973-4cda-ac77-51325e731cda,
> messageType=class
> o.a.i.i.processors.cache.distributed.near.GridNearTxFinishRequest]
> org.apache.ignite.IgniteException: Failed to create string representation of
> binary object.
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1028)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:826)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:783)
> at
> org.apache.ignite.internal.processors.cache.distributed.GridDistributedTxFinishRequest.toString(GridDistributedTxFinishRequest.java:561)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxFinishRequest.toString(GridNearTxFinishRequest.java:221)
> at java.lang.String.valueOf(String.java:2994)
> at java.lang.StringBuilder.append(StringBuilder.java:131)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1060)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:579)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:378)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:304)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:99)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:293)
> 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.communication.GridIoManager.access$4200(GridIoManager.java:125)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1091)
> at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.run(StripedExecutor.java:511)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.apache.ignite.IgniteException: Failed to create string
> representation of binary object.
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1028)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:826)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:783)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxStateImpl.toString(IgniteTxStateImpl.java:466)
> at java.lang.String.valueOf(String.java:2994)
> at
> org.apache.ignite.internal.util.GridStringBuilder.a(GridStringBuilder.java:101)
> at
> org.apache.ignite.internal.util.tostring.SBLimitedLength.a(SBLimitedLength.java:88)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:939)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1005)
> ... 18 common frames omitted
> Caused by: org.apache.ignite.IgniteException: Failed to create string
> representation of binary object.
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1028)
[jira] [Reopened] (IGNITE-8789) Add a call to the FailureHandler for an error with meta-data.
[
https://issues.apache.org/jira/browse/IGNITE-8789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura reopened IGNITE-8789:
-
> Add a call to the FailureHandler for an error with meta-data.
> -
>
> Key: IGNITE-8789
> URL: https://issues.apache.org/jira/browse/IGNITE-8789
> Project: Ignite
> Issue Type: Improvement
>Reporter: Dmitriy Gladkikh
>Priority: Critical
> Fix For: 2.6
>
>
> This is a critical situation, corresponding exception should be propagated to
> handler to make necessary actions.
> Need to add a call to the FailureHandler if the specified error occurs.
> When processing a message in the GridCacheIoManager#onMessage0 method, an
> exception was thrown: Failed to process message
> [senderId=f815a46c-8973-4cda-ac77-51325e731cda, messageType=class
> o.a.i.i.processors.cache.distributed.near.GridNearTxFinishRequest]
> An error occurred during the error logging associated with the meta-data:
> Cannot find schema for object with compact footer [typeId=1599442645,
> schemaId=-1705721149]
> The original exception was lost.
> {code:java}
> 2018-06-13
> 09:04:01.593[ERROR][sys-stripe-22-#23%DPL_GRID%DplGridNodeName%][o.a.i.i.p.cache.GridCacheIoManager]
> Failed to process message [senderId=f815a46c-8973-4cda-ac77-51325e731cda,
> messageType=class
> o.a.i.i.processors.cache.distributed.near.GridNearTxFinishRequest]
> org.apache.ignite.IgniteException: Failed to create string representation of
> binary object.
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1028)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:826)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:783)
> at
> org.apache.ignite.internal.processors.cache.distributed.GridDistributedTxFinishRequest.toString(GridDistributedTxFinishRequest.java:561)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxFinishRequest.toString(GridNearTxFinishRequest.java:221)
> at java.lang.String.valueOf(String.java:2994)
> at java.lang.StringBuilder.append(StringBuilder.java:131)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1060)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:579)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:378)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:304)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:99)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:293)
> 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.communication.GridIoManager.access$4200(GridIoManager.java:125)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1091)
> at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.run(StripedExecutor.java:511)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.apache.ignite.IgniteException: Failed to create string
> representation of binary object.
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1028)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:826)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:783)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxStateImpl.toString(IgniteTxStateImpl.java:466)
> at java.lang.String.valueOf(String.java:2994)
> at
> org.apache.ignite.internal.util.GridStringBuilder.a(GridStringBuilder.java:101)
> at
> org.apache.ignite.internal.util.tostring.SBLimitedLength.a(SBLimitedLength.java:88)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:939)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1005)
> ... 18 common frames omitted
> Caused by: org.apache.ignite.IgniteException: Failed to create string
> representation of binary object.
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1028)
> at
>
[jira] [Resolved] (IGNITE-8787) Striped Executor thread failure is not processed by IgniteFailureProcessor
[ https://issues.apache.org/jira/browse/IGNITE-8787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura resolved IGNITE-8787. - Resolution: Won't Fix > Striped Executor thread failure is not processed by IgniteFailureProcessor > -- > > Key: IGNITE-8787 > URL: https://issues.apache.org/jira/browse/IGNITE-8787 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.5 >Reporter: Andrew Medvedev >Priority: Major > Fix For: 2.6 > > Attachments: after.jstack, before.jstack > > > org.apache.ignite.internal.util.StripedExecutor.Stripe#run currently does not > invoke IgniteFailureProcessor upon thread death. This can lead to dying all > striped threads on a running node. see jstacks attached taken before and > after killing all striped threads (via JMX). > > If striped executor threads are considered critical, they should be processed > by IgniteFailureProcessor as well -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (IGNITE-8789) Add a call to the FailureHandler for an error with meta-data.
[
https://issues.apache.org/jira/browse/IGNITE-8789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura updated IGNITE-8789:
Comment: was deleted
(was: Will be fixed as result of
https://issues.apache.org/jira/browse/IGNITE-8562)
> Add a call to the FailureHandler for an error with meta-data.
> -
>
> Key: IGNITE-8789
> URL: https://issues.apache.org/jira/browse/IGNITE-8789
> Project: Ignite
> Issue Type: Improvement
>Reporter: Dmitriy Gladkikh
>Priority: Critical
> Fix For: 2.6
>
>
> This is a critical situation, corresponding exception should be propagated to
> handler to make necessary actions.
> Need to add a call to the FailureHandler if the specified error occurs.
> When processing a message in the GridCacheIoManager#onMessage0 method, an
> exception was thrown: Failed to process message
> [senderId=f815a46c-8973-4cda-ac77-51325e731cda, messageType=class
> o.a.i.i.processors.cache.distributed.near.GridNearTxFinishRequest]
> An error occurred during the error logging associated with the meta-data:
> Cannot find schema for object with compact footer [typeId=1599442645,
> schemaId=-1705721149]
> The original exception was lost.
> {code:java}
> 2018-06-13
> 09:04:01.593[ERROR][sys-stripe-22-#23%DPL_GRID%DplGridNodeName%][o.a.i.i.p.cache.GridCacheIoManager]
> Failed to process message [senderId=f815a46c-8973-4cda-ac77-51325e731cda,
> messageType=class
> o.a.i.i.processors.cache.distributed.near.GridNearTxFinishRequest]
> org.apache.ignite.IgniteException: Failed to create string representation of
> binary object.
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1028)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:826)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:783)
> at
> org.apache.ignite.internal.processors.cache.distributed.GridDistributedTxFinishRequest.toString(GridDistributedTxFinishRequest.java:561)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxFinishRequest.toString(GridNearTxFinishRequest.java:221)
> at java.lang.String.valueOf(String.java:2994)
> at java.lang.StringBuilder.append(StringBuilder.java:131)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1060)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:579)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:378)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:304)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:99)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:293)
> 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.communication.GridIoManager.access$4200(GridIoManager.java:125)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1091)
> at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.run(StripedExecutor.java:511)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.apache.ignite.IgniteException: Failed to create string
> representation of binary object.
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1028)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:826)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:783)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxStateImpl.toString(IgniteTxStateImpl.java:466)
> at java.lang.String.valueOf(String.java:2994)
> at
> org.apache.ignite.internal.util.GridStringBuilder.a(GridStringBuilder.java:101)
> at
> org.apache.ignite.internal.util.tostring.SBLimitedLength.a(SBLimitedLength.java:88)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:939)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1005)
> ... 18 common frames omitted
> Caused by: org.apache.ignite.IgniteException: Failed to create string
> representation of binary object.
> at
>
[jira] [Commented] (IGNITE-8787) Striped Executor thread failure is not processed by IgniteFailureProcessor
[ https://issues.apache.org/jira/browse/IGNITE-8787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16512326#comment-16512326 ] Andrey Gura commented on IGNITE-8787: - Will be fixed as result of https://issues.apache.org/jira/browse/IGNITE-8562 > Striped Executor thread failure is not processed by IgniteFailureProcessor > -- > > Key: IGNITE-8787 > URL: https://issues.apache.org/jira/browse/IGNITE-8787 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.5 >Reporter: Andrew Medvedev >Priority: Major > Fix For: 2.6 > > Attachments: after.jstack, before.jstack > > > org.apache.ignite.internal.util.StripedExecutor.Stripe#run currently does not > invoke IgniteFailureProcessor upon thread death. This can lead to dying all > striped threads on a running node. see jstacks attached taken before and > after killing all striped threads (via JMX). > > If striped executor threads are considered critical, they should be processed > by IgniteFailureProcessor as well -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-8789) Add a call to the FailureHandler for an error with meta-data.
[
https://issues.apache.org/jira/browse/IGNITE-8789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura resolved IGNITE-8789.
-
Resolution: Won't Fix
Will be fixed as result of https://issues.apache.org/jira/browse/IGNITE-8562
> Add a call to the FailureHandler for an error with meta-data.
> -
>
> Key: IGNITE-8789
> URL: https://issues.apache.org/jira/browse/IGNITE-8789
> Project: Ignite
> Issue Type: Improvement
>Reporter: Dmitriy Gladkikh
>Priority: Critical
> Fix For: 2.6
>
>
> This is a critical situation, corresponding exception should be propagated to
> handler to make necessary actions.
> Need to add a call to the FailureHandler if the specified error occurs.
> When processing a message in the GridCacheIoManager#onMessage0 method, an
> exception was thrown: Failed to process message
> [senderId=f815a46c-8973-4cda-ac77-51325e731cda, messageType=class
> o.a.i.i.processors.cache.distributed.near.GridNearTxFinishRequest]
> An error occurred during the error logging associated with the meta-data:
> Cannot find schema for object with compact footer [typeId=1599442645,
> schemaId=-1705721149]
> The original exception was lost.
> {code:java}
> 2018-06-13
> 09:04:01.593[ERROR][sys-stripe-22-#23%DPL_GRID%DplGridNodeName%][o.a.i.i.p.cache.GridCacheIoManager]
> Failed to process message [senderId=f815a46c-8973-4cda-ac77-51325e731cda,
> messageType=class
> o.a.i.i.processors.cache.distributed.near.GridNearTxFinishRequest]
> org.apache.ignite.IgniteException: Failed to create string representation of
> binary object.
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1028)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:826)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:783)
> at
> org.apache.ignite.internal.processors.cache.distributed.GridDistributedTxFinishRequest.toString(GridDistributedTxFinishRequest.java:561)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxFinishRequest.toString(GridNearTxFinishRequest.java:221)
> at java.lang.String.valueOf(String.java:2994)
> at java.lang.StringBuilder.append(StringBuilder.java:131)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1060)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:579)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:378)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:304)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:99)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:293)
> 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.communication.GridIoManager.access$4200(GridIoManager.java:125)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1091)
> at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.run(StripedExecutor.java:511)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.apache.ignite.IgniteException: Failed to create string
> representation of binary object.
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1028)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:826)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:783)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxStateImpl.toString(IgniteTxStateImpl.java:466)
> at java.lang.String.valueOf(String.java:2994)
> at
> org.apache.ignite.internal.util.GridStringBuilder.a(GridStringBuilder.java:101)
> at
> org.apache.ignite.internal.util.tostring.SBLimitedLength.a(SBLimitedLength.java:88)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:939)
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1005)
> ... 18 common frames omitted
> Caused by: org.apache.ignite.IgniteException: Failed to create string
> representation of binary object.
> at
>
[jira] [Commented] (IGNITE-8322) Yardstick benchmark preloading option
[ https://issues.apache.org/jira/browse/IGNITE-8322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16511521#comment-16511521 ] Andrey Gura commented on IGNITE-8322: - [~oleg-ostanin] LGTM. Merged to master branch. Thanks for contribution! > Yardstick benchmark preloading option > - > > Key: IGNITE-8322 > URL: https://issues.apache.org/jira/browse/IGNITE-8322 > Project: Ignite > Issue Type: Improvement >Reporter: Oleg Ostanin >Assignee: Oleg Ostanin >Priority: Major > Fix For: 2.6 > > > Yardstick has no benchmarks with eviction on the disk (PDS). For that puspose > we need following: > 1. Make new configuration and put every cache into a separate date region: > atomic,tx,atomic-index,query,compute > 2. Add a new preload option for a benchmark: preload up to a size passed from > that option. There two options: > * total size of preload data (bytes) > * the size of data in memory against total size (percent) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-602) [Test] GridToStringBuilder is vulnerable for StackOverflowError caused by infinite recursion
[ https://issues.apache.org/jira/browse/IGNITE-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16511300#comment-16511300 ] Andrey Gura commented on IGNITE-602: [~SomeFire] Could you please move ticket to "Patch available" status? > [Test] GridToStringBuilder is vulnerable for StackOverflowError caused by > infinite recursion > > > Key: IGNITE-602 > URL: https://issues.apache.org/jira/browse/IGNITE-602 > Project: Ignite > Issue Type: Bug > Components: general >Reporter: Artem Shutak >Assignee: Ryabov Dmitrii >Priority: Major > Labels: MakeTeamcityGreenAgain, Muted_test > Fix For: 2.6 > > > See test > org.gridgain.grid.util.tostring.GridToStringBuilderSelfTest#_testToStringCheckAdvancedRecursionPrevention > and related TODO in same source file. > Also take a look at > http://stackoverflow.com/questions/11300203/most-efficient-way-to-prevent-an-infinite-recursion-in-tostring > Test should be unmuted on TC after fix. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-602) [Test] GridToStringBuilder is vulnerable for StackOverflowError caused by infinite recursion
[ https://issues.apache.org/jira/browse/IGNITE-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16511297#comment-16511297 ] Andrey Gura commented on IGNITE-602: [~SomeFire] Seems ok. But it would be better to review somebody else. [~agoncharuk] Could you please take a look? (Actual PR: https://github.com/apache/ignite/pull/1558) > [Test] GridToStringBuilder is vulnerable for StackOverflowError caused by > infinite recursion > > > Key: IGNITE-602 > URL: https://issues.apache.org/jira/browse/IGNITE-602 > Project: Ignite > Issue Type: Bug > Components: general >Reporter: Artem Shutak >Assignee: Ryabov Dmitrii >Priority: Major > Labels: MakeTeamcityGreenAgain, Muted_test > Fix For: 2.6 > > > See test > org.gridgain.grid.util.tostring.GridToStringBuilderSelfTest#_testToStringCheckAdvancedRecursionPrevention > and related TODO in same source file. > Also take a look at > http://stackoverflow.com/questions/11300203/most-efficient-way-to-prevent-an-infinite-recursion-in-tostring > Test should be unmuted on TC after fix. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8781) nio-acceptor threads are indistinguishable in GridNioServer
Andrey Gura created IGNITE-8781:
---
Summary: nio-acceptor threads are indistinguishable in
GridNioServer
Key: IGNITE-8781
URL: https://issues.apache.org/jira/browse/IGNITE-8781
Project: Ignite
Issue Type: Improvement
Reporter: Andrey Gura
Assignee: Andrey Gura
Fix For: 2.6
nio-acceptor threads are indistinguishable in {{GridNioServer}}. All threads
have exactly same name.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-8293) BinaryUtils#isCustomJavaSerialization fails when only readObject is declared in a class
[
https://issues.apache.org/jira/browse/IGNITE-8293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16511026#comment-16511026
]
Andrey Gura edited comment on IGNITE-8293 at 6/13/18 12:13 PM:
---
[~MihkelJ] Unfortunately, TC run has failed tests due to your change. At least
following tests are failed:
{noformat}
org.apache.ignite.testsuites.IgniteBinaryObjectsTestSuite:
org.apache.ignite.internal.binary (12)
BinaryEnumsSelfTest.testDeclaredBodyEnumNotRegistered
BinaryEnumsSelfTest.testDeclaredBodyEnumRegistered
BinaryEnumsSelfTest.testNestedBuilderNotRegistered
BinaryEnumsSelfTest.testNestedNotRegistered
BinaryEnumsSelfTest.testSimpleArrayNotRegistered
BinaryEnumsSelfTest.testSimpleArrayRegistered
BinaryEnumsSelfTest.testSimpleNotRegistered
BinaryEnumsSelfTest.testSimpleRegistered
BinaryMarshallerSelfTest.testWriteReplaceInheritable
BinaryObjectBuilderAdditionalSelfTest.testEnum
BinaryObjectBuilderAdditionalSelfTest.testMetadataChanging
BinaryObjectBuilderAdditionalSelfTest.testSimpleTypeFieldOverride
org.apache.ignite.testsuites.IgniteBinaryObjectsTestSuite:
org.apache.ignite.internal.binary.noncompact (4)
BinaryMarshallerNonCompactSelfTest.testWriteReplaceInheritable
BinaryObjectBuilderAdditionalNonCompactSelfTest.testEnum
BinaryObjectBuilderAdditionalNonCompactSelfTest.testMetadataChanging
BinaryObjectBuilderAdditionalNonCompactSelfTest.testSimpleTypeFieldOverride
{noformat}
was (Author: agura):
[~MihkelJ] Unfortunately, TC run has failed tests due to your change. At least
following changes are failed:
{noformat}
org.apache.ignite.testsuites.IgniteBinaryObjectsTestSuite:
org.apache.ignite.internal.binary (12)
BinaryEnumsSelfTest.testDeclaredBodyEnumNotRegistered
BinaryEnumsSelfTest.testDeclaredBodyEnumRegistered
BinaryEnumsSelfTest.testNestedBuilderNotRegistered
BinaryEnumsSelfTest.testNestedNotRegistered
BinaryEnumsSelfTest.testSimpleArrayNotRegistered
BinaryEnumsSelfTest.testSimpleArrayRegistered
BinaryEnumsSelfTest.testSimpleNotRegistered
BinaryEnumsSelfTest.testSimpleRegistered
BinaryMarshallerSelfTest.testWriteReplaceInheritable
BinaryObjectBuilderAdditionalSelfTest.testEnum
BinaryObjectBuilderAdditionalSelfTest.testMetadataChanging
BinaryObjectBuilderAdditionalSelfTest.testSimpleTypeFieldOverride
org.apache.ignite.testsuites.IgniteBinaryObjectsTestSuite:
org.apache.ignite.internal.binary.noncompact (4)
BinaryMarshallerNonCompactSelfTest.testWriteReplaceInheritable
BinaryObjectBuilderAdditionalNonCompactSelfTest.testEnum
BinaryObjectBuilderAdditionalNonCompactSelfTest.testMetadataChanging
BinaryObjectBuilderAdditionalNonCompactSelfTest.testSimpleTypeFieldOverride
{noformat}
> BinaryUtils#isCustomJavaSerialization fails when only readObject is declared
> in a class
> ---
>
> Key: IGNITE-8293
> URL: https://issues.apache.org/jira/browse/IGNITE-8293
> Project: Ignite
> Issue Type: Bug
> Components: binary
>Affects Versions: 2.4
>Reporter: MihkelJ
>Assignee: MihkelJ
>Priority: Minor
> Fix For: 2.6
>
>
> Consider this class:
>
> {code:java}
> public class Test implements Serializable {
> private transient AtomicBoolean dirty = new AtomicBoolean(false);
> private void readObject(java.io.ObjectInputStream in) throws IOException,
> ClassNotFoundException {
> dirty = new AtomicBoolean(false);
> }
> //methods to check and mark class as dirty
> }{code}
> {{isCustomJavaSerialization}} will get a {{NoSuchMethodException}} when
> trying to grab the {{writeObject}} method and falsely conclude that Test
> doesn't use custom serialization.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8293) BinaryUtils#isCustomJavaSerialization fails when only readObject is declared in a class
[
https://issues.apache.org/jira/browse/IGNITE-8293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16511026#comment-16511026
]
Andrey Gura commented on IGNITE-8293:
-
[~MihkelJ] Unfortunately, TC run has failed tests due to your change. At least
following changes are failed:
{noformat}
org.apache.ignite.testsuites.IgniteBinaryObjectsTestSuite:
org.apache.ignite.internal.binary (12)
BinaryEnumsSelfTest.testDeclaredBodyEnumNotRegistered
BinaryEnumsSelfTest.testDeclaredBodyEnumRegistered
BinaryEnumsSelfTest.testNestedBuilderNotRegistered
BinaryEnumsSelfTest.testNestedNotRegistered
BinaryEnumsSelfTest.testSimpleArrayNotRegistered
BinaryEnumsSelfTest.testSimpleArrayRegistered
BinaryEnumsSelfTest.testSimpleNotRegistered
BinaryEnumsSelfTest.testSimpleRegistered
BinaryMarshallerSelfTest.testWriteReplaceInheritable
BinaryObjectBuilderAdditionalSelfTest.testEnum
BinaryObjectBuilderAdditionalSelfTest.testMetadataChanging
BinaryObjectBuilderAdditionalSelfTest.testSimpleTypeFieldOverride
org.apache.ignite.testsuites.IgniteBinaryObjectsTestSuite:
org.apache.ignite.internal.binary.noncompact (4)
BinaryMarshallerNonCompactSelfTest.testWriteReplaceInheritable
BinaryObjectBuilderAdditionalNonCompactSelfTest.testEnum
BinaryObjectBuilderAdditionalNonCompactSelfTest.testMetadataChanging
BinaryObjectBuilderAdditionalNonCompactSelfTest.testSimpleTypeFieldOverride
{noformat}
> BinaryUtils#isCustomJavaSerialization fails when only readObject is declared
> in a class
> ---
>
> Key: IGNITE-8293
> URL: https://issues.apache.org/jira/browse/IGNITE-8293
> Project: Ignite
> Issue Type: Bug
> Components: binary
>Affects Versions: 2.4
>Reporter: MihkelJ
>Assignee: MihkelJ
>Priority: Minor
> Fix For: 2.6
>
>
> Consider this class:
>
> {code:java}
> public class Test implements Serializable {
> private transient AtomicBoolean dirty = new AtomicBoolean(false);
> private void readObject(java.io.ObjectInputStream in) throws IOException,
> ClassNotFoundException {
> dirty = new AtomicBoolean(false);
> }
> //methods to check and mark class as dirty
> }{code}
> {{isCustomJavaSerialization}} will get a {{NoSuchMethodException}} when
> trying to grab the {{writeObject}} method and falsely conclude that Test
> doesn't use custom serialization.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8751) Possible race on node segmentation.
[ https://issues.apache.org/jira/browse/IGNITE-8751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16510928#comment-16510928 ] Andrey Gura commented on IGNITE-8751: - TC looks good: https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8_IgniteTests24Java8=pull%2F4171%2Fhead Please review. > Possible race on node segmentation. > --- > > Key: IGNITE-8751 > URL: https://issues.apache.org/jira/browse/IGNITE-8751 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.5 >Reporter: Andrew Mashenkov >Assignee: Andrey Gura >Priority: Major > Fix For: 2.6 > > > Segmentation policy may be ignored, probably, due to a race. > See [1] for details. > [1] > [http://apache-ignite-users.70518.x6.nabble.com/Node-pause-for-no-obvious-reason-td21923.html] > Logs from segmented node. > [08:42:42,290][INFO][tcp-disco-sock-reader-#15][TcpDiscoverySpi] Finished > serving remote node connection [rmtAddr=/10.29.42.45:38712, rmtPort=38712 > [08:42:42,290][WARNING][disco-event-worker-#161][GridDiscoveryManager] Local > node SEGMENTED: TcpDiscoveryNode [id=8333aa56-8bf4-4558-a387-809b1d2e2e5b, > addrs=[10.29.42.44, 127.0.0.1], sockAddrs=[sap-datanode1/10.29.42.44:49500, > /127.0.0.1:49500], discPort=49500, order=1, intOrder=1, > lastExchangeTime=1528447362286, loc=true, ver=2.5.0#20180523-sha1:86e110c7, > isClient=false] > [08:42:42,294][SEVERE][tcp-disco-srvr-#2][] Critical system error detected. > Will be handled accordingly to configured handler [hnd=class > o.a.i.failure.StopNodeOrHaltFailureHandler, failureCtx=FailureContext > [type=SYSTEM_WORKER_TERMINATION, err=java.lang.IllegalStateException: Thread > tcp-disco-srvr-#2 is terminated unexpectedly.]] > java.lang.IllegalStateException: Thread tcp-disco-srvr-#2 is terminated > unexpectedly. > at > org.apache.ignite.spi.discovery.tcp.ServerImpl$TcpServer.body(ServerImpl.java:5686) > > at > org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62) > [08:42:42,294][SEVERE][tcp-disco-srvr-#2][] JVM will be halted immediately > due to the failure: [failureCtx=FailureContext > [type=SYSTEM_WORKER_TERMINATION, err=java.lang.IllegalStateException: Thread > tcp-disco-srvr-#2 is terminated unexpectedly.]] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-4210) CacheLoadingConcurrentGridStartSelfTest.testLoadCacheFromStore() test lose data.
[ https://issues.apache.org/jira/browse/IGNITE-4210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16510877#comment-16510877 ] Andrey Gura edited comment on IGNITE-4210 at 6/13/18 9:47 AM: -- [~Alexey Kuznetsov] From my point of view it's a not good solution because it will block partition map exchange until loadCache finish data loading and then will lead to massive data rebalancing. Better way, I believe, it's passing exception to user code in case of topology changes and then user will have possibility to manage initial data loading from cache store (e.g. user can split whole data set on blocks and retry loading of block on which topology is changed). was (Author: agura): [~Alexey Kuznetsov] From my point of view it's a not good solution because it will block partition map exchange until loadCache finish data loading and then will lead to massive data rebalancing. Better way, I believe, it's passing exception to user code in case of topology changes and then user will have possibility to manage initial data loading (e.g. user can split whole data set on blocks and retry loading of block on which topology is changed). > CacheLoadingConcurrentGridStartSelfTest.testLoadCacheFromStore() test lose > data. > > > Key: IGNITE-4210 > URL: https://issues.apache.org/jira/browse/IGNITE-4210 > Project: Ignite > Issue Type: Bug >Reporter: Anton Vinogradov >Assignee: Alexey Kuznetsov >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.6 > > > org.apache.ignite.internal.processors.cache.distributed.CacheLoadingConcurrentGridStartSelfTest#testLoadCacheFromStore > sometimes have failures. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-4210) CacheLoadingConcurrentGridStartSelfTest.testLoadCacheFromStore() test lose data.
[ https://issues.apache.org/jira/browse/IGNITE-4210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16510877#comment-16510877 ] Andrey Gura commented on IGNITE-4210: - [~Alexey Kuznetsov] From my point of view it's a not good solution because it will block partition map exchange until loadCache finish data loading and then will lead to massive data rebalancing. Better way, I believe, it's passing exception to user code in case of topology changes and then user will have possibility to manage initial data loading (e.g. user can split whole data set on blocks and retry loading of block on which topology is changed). > CacheLoadingConcurrentGridStartSelfTest.testLoadCacheFromStore() test lose > data. > > > Key: IGNITE-4210 > URL: https://issues.apache.org/jira/browse/IGNITE-4210 > Project: Ignite > Issue Type: Bug >Reporter: Anton Vinogradov >Assignee: Alexey Kuznetsov >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.6 > > > org.apache.ignite.internal.processors.cache.distributed.CacheLoadingConcurrentGridStartSelfTest#testLoadCacheFromStore > sometimes have failures. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8763) java.nio.file.AccessDeniedException is not handled with default failure handler
Andrey Gura created IGNITE-8763:
---
Summary: java.nio.file.AccessDeniedException is not handled with
default failure handler
Key: IGNITE-8763
URL: https://issues.apache.org/jira/browse/IGNITE-8763
Project: Ignite
Issue Type: Improvement
Affects Versions: 2.5
Reporter: Andrey Gura
Fix For: 2.6
java.nio.file.AccessDeniedException is not handled with default failure handler
1. Start cluster(4 nodes).
2. Upload some data.
3. Make files in metastore read only.
4. Deactivate grid.
5. Activate grid.
On this step I see java.nio.file.AccessDeniedException:
{noformat}
[17:55:40,035][INFO][exchange-worker-#62][GridCacheDatabaseSharedManager] Read
checkpoint status
[startMarker=/storage/ssd/avolkov/tiden/iep_14-180517-175425/test_iep_14/ignite.server.1/work/db/node1/cp/1526568907638-46128a87-562a-45fc-8d73-75ccb1490d63-START.bin,
endMarker=/storage/ssd/avolkov/tiden/iep_14-180517-175425/test_iep_14/ignite.server.1/work/db/node1/cp/1526568907638-46128a87-562a-45fc-8d73-75ccb1490d63-END.bin]
[17:55:40,037][SEVERE][exchange-worker-#62][GridDhtPartitionsExchangeFuture]
Failed to activate node components
[nodeId=bd7115d5-1f95-4673-9f40-47056b0b1a58, client=false,
topVer=AffinityTopologyVersion [topVer=4, minorTopVer=5]]
class org.apache.ignite.IgniteCheckedException: Error while creating file page
store
[file=/storage/ssd/avolkov/tiden/iep_14-180517-175425/test_iep_14/ignite.server.1/work/db/node1/metastorage/part-0.bin]:
at
org.apache.ignite.internal.processors.cache.persistence.file.FileVersionCheckingFactory.createPageStore(FileVersionCheckingFactory.java:98)
at
org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.initDir(FilePageStoreManager.java:463)
at
org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.initializeForMetastorage(FilePageStoreManager.java:234)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.readCheckpointAndRestoreMemory(GridCacheDatabaseSharedManager.java:743)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onClusterStateChangeRequest(GridDhtPartitionsExchangeFuture.java:896)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:643)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2419)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2299)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.nio.file.AccessDeniedException:
/storage/ssd/avolkov/tiden/iep_14-180517-175425/test_iep_14/ignite.server.1/work/db/node1/metastorage/part-0.bin
at
sun.nio.fs.UnixException.translateToIOException(UnixException.java:84)
at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
at
sun.nio.fs.UnixFileSystemProvider.newAsynchronousFileChannel(UnixFileSystemProvider.java:196)
at
java.nio.channels.AsynchronousFileChannel.open(AsynchronousFileChannel.java:248)
at
java.nio.channels.AsynchronousFileChannel.open(AsynchronousFileChannel.java:301)
at
org.apache.ignite.internal.processors.cache.persistence.file.AsyncFileIO.(AsyncFileIO.java:57)
at
org.apache.ignite.internal.processors.cache.persistence.file.AsyncFileIOFactory.create(AsyncFileIOFactory.java:53)
at
org.apache.ignite.internal.processors.cache.persistence.file.AsyncFileIOFactory.create(AsyncFileIOFactory.java:41)
at
org.apache.ignite.internal.processors.cache.persistence.file.FileVersionCheckingFactory.createPageStore(FileVersionCheckingFactory.java:78)
... 9 more
{noformat}
Situation led to NPE exception after AccessDeniedException looks like this:
1. AccessDeniedException was thrown in ExchangeFuture right before affinity
initialization so affinity was never initialized.
2. After that node receives PartitionSingleMessage and tries to access
affinity information. Null is returned because of exception in step #1.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8763) java.nio.file.AccessDeniedException is not handled with default failure handler
[
https://issues.apache.org/jira/browse/IGNITE-8763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura updated IGNITE-8763:
Issue Type: Bug (was: Improvement)
> java.nio.file.AccessDeniedException is not handled with default failure
> handler
> ---
>
> Key: IGNITE-8763
> URL: https://issues.apache.org/jira/browse/IGNITE-8763
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Andrey Gura
>Priority: Major
> Fix For: 2.6
>
>
> java.nio.file.AccessDeniedException is not handled with default failure
> handler
> 1. Start cluster(4 nodes).
> 2. Upload some data.
> 3. Make files in metastore read only.
> 4. Deactivate grid.
> 5. Activate grid.
> On this step I see java.nio.file.AccessDeniedException:
> {noformat}
> [17:55:40,035][INFO][exchange-worker-#62][GridCacheDatabaseSharedManager]
> Read checkpoint status
> [startMarker=/storage/ssd/avolkov/tiden/iep_14-180517-175425/test_iep_14/ignite.server.1/work/db/node1/cp/1526568907638-46128a87-562a-45fc-8d73-75ccb1490d63-START.bin,
>
> endMarker=/storage/ssd/avolkov/tiden/iep_14-180517-175425/test_iep_14/ignite.server.1/work/db/node1/cp/1526568907638-46128a87-562a-45fc-8d73-75ccb1490d63-END.bin]
> [17:55:40,037][SEVERE][exchange-worker-#62][GridDhtPartitionsExchangeFuture]
> Failed to activate node components
> [nodeId=bd7115d5-1f95-4673-9f40-47056b0b1a58, client=false,
> topVer=AffinityTopologyVersion [topVer=4, minorTopVer=5]]
> class org.apache.ignite.IgniteCheckedException: Error while creating file
> page store
> [file=/storage/ssd/avolkov/tiden/iep_14-180517-175425/test_iep_14/ignite.server.1/work/db/node1/metastorage/part-0.bin]:
> at
> org.apache.ignite.internal.processors.cache.persistence.file.FileVersionCheckingFactory.createPageStore(FileVersionCheckingFactory.java:98)
> at
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.initDir(FilePageStoreManager.java:463)
> at
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.initializeForMetastorage(FilePageStoreManager.java:234)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.readCheckpointAndRestoreMemory(GridCacheDatabaseSharedManager.java:743)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onClusterStateChangeRequest(GridDhtPartitionsExchangeFuture.java:896)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:643)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2419)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2299)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.nio.file.AccessDeniedException:
> /storage/ssd/avolkov/tiden/iep_14-180517-175425/test_iep_14/ignite.server.1/work/db/node1/metastorage/part-0.bin
> at
> sun.nio.fs.UnixException.translateToIOException(UnixException.java:84)
> at
> sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
> at
> sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
> at
> sun.nio.fs.UnixFileSystemProvider.newAsynchronousFileChannel(UnixFileSystemProvider.java:196)
> at
> java.nio.channels.AsynchronousFileChannel.open(AsynchronousFileChannel.java:248)
> at
> java.nio.channels.AsynchronousFileChannel.open(AsynchronousFileChannel.java:301)
> at
> org.apache.ignite.internal.processors.cache.persistence.file.AsyncFileIO.(AsyncFileIO.java:57)
> at
> org.apache.ignite.internal.processors.cache.persistence.file.AsyncFileIOFactory.create(AsyncFileIOFactory.java:53)
> at
> org.apache.ignite.internal.processors.cache.persistence.file.AsyncFileIOFactory.create(AsyncFileIOFactory.java:41)
> at
> org.apache.ignite.internal.processors.cache.persistence.file.FileVersionCheckingFactory.createPageStore(FileVersionCheckingFactory.java:78)
> ... 9 more
> {noformat}
> Situation led to NPE exception after AccessDeniedException looks like this:
> 1. AccessDeniedException was thrown in ExchangeFuture right before affinity
> initialization so affinity was never initialized.
> 2. After that node receives PartitionSingleMessage and tries to access
> affinity information. Null is returned because of exception in step #1.
--
This message was sent by
[jira] [Comment Edited] (IGNITE-8751) Possible race on node segmentation.
[
https://issues.apache.org/jira/browse/IGNITE-8751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16506083#comment-16506083
]
Andrey Gura edited comment on IGNITE-8751 at 6/8/18 2:43 PM:
-
It isn't race. {{tcp-disco-srvr}} and {{tcp-disco-msg-worker}} are interrupted
earlier than segmentation policy handles segmentation. See
{{org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.DiscoveryWorker#onSegmentation}}
where we first disconnect SPI and then handle segmentation.
It seems could be fixed by adding check on SPI state in exception handler of
{{tcp-disco-srvr}} and {{tcp-disco-msg-worker}}.
was (Author: agura):
It isn't race. {{tcp-disco-srvr}} is interrupted earlier than segmentation
policy handles segmentation. See
{{org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.DiscoveryWorker#onSegmentation}}
where we first disconnect SPI and then handle segmentation.
It seems could be fixed by adding check on SPI state in exception handler of
{{tcp-disco-srvr}}.
> Possible race on node segmentation.
> ---
>
> Key: IGNITE-8751
> URL: https://issues.apache.org/jira/browse/IGNITE-8751
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Andrew Mashenkov
>Assignee: Andrey Gura
>Priority: Major
> Fix For: 2.6
>
>
> Segmentation policy may be ignored, probably, due to a race.
> See [1] for details.
> [1]
> [http://apache-ignite-users.70518.x6.nabble.com/Node-pause-for-no-obvious-reason-td21923.html]
> Logs from segmented node.
> [08:42:42,290][INFO][tcp-disco-sock-reader-#15][TcpDiscoverySpi] Finished
> serving remote node connection [rmtAddr=/10.29.42.45:38712, rmtPort=38712
> [08:42:42,290][WARNING][disco-event-worker-#161][GridDiscoveryManager] Local
> node SEGMENTED: TcpDiscoveryNode [id=8333aa56-8bf4-4558-a387-809b1d2e2e5b,
> addrs=[10.29.42.44, 127.0.0.1], sockAddrs=[sap-datanode1/10.29.42.44:49500,
> /127.0.0.1:49500], discPort=49500, order=1, intOrder=1,
> lastExchangeTime=1528447362286, loc=true, ver=2.5.0#20180523-sha1:86e110c7,
> isClient=false]
> [08:42:42,294][SEVERE][tcp-disco-srvr-#2][] Critical system error detected.
> Will be handled accordingly to configured handler [hnd=class
> o.a.i.failure.StopNodeOrHaltFailureHandler, failureCtx=FailureContext
> [type=SYSTEM_WORKER_TERMINATION, err=java.lang.IllegalStateException: Thread
> tcp-disco-srvr-#2 is terminated unexpectedly.]]
> java.lang.IllegalStateException: Thread tcp-disco-srvr-#2 is terminated
> unexpectedly.
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$TcpServer.body(ServerImpl.java:5686)
>
> at
> org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> [08:42:42,294][SEVERE][tcp-disco-srvr-#2][] JVM will be halted immediately
> due to the failure: [failureCtx=FailureContext
> [type=SYSTEM_WORKER_TERMINATION, err=java.lang.IllegalStateException: Thread
> tcp-disco-srvr-#2 is terminated unexpectedly.]]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8751) Possible race on node segmentation.
[
https://issues.apache.org/jira/browse/IGNITE-8751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16506083#comment-16506083
]
Andrey Gura commented on IGNITE-8751:
-
It isn't race. {{tcp-disco-srvr}} is interrupted earlier than segmentation
policy handles segmentation. See
{{org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.DiscoveryWorker#onSegmentation}}
where we first disconnect SPI and then handle segmentation.
It seems could be fixed by adding check on SPI state in exception handler of
{{tcp-disco-srvr}}.
> Possible race on node segmentation.
> ---
>
> Key: IGNITE-8751
> URL: https://issues.apache.org/jira/browse/IGNITE-8751
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Andrew Mashenkov
>Assignee: Andrey Gura
>Priority: Major
> Fix For: 2.6
>
>
> Segmentation policy may be ignored, probably, due to a race.
> See [1] for details.
> [1]
> [http://apache-ignite-users.70518.x6.nabble.com/Node-pause-for-no-obvious-reason-td21923.html]
> Logs from segmented node.
> [08:42:42,290][INFO][tcp-disco-sock-reader-#15][TcpDiscoverySpi] Finished
> serving remote node connection [rmtAddr=/10.29.42.45:38712, rmtPort=38712
> [08:42:42,290][WARNING][disco-event-worker-#161][GridDiscoveryManager] Local
> node SEGMENTED: TcpDiscoveryNode [id=8333aa56-8bf4-4558-a387-809b1d2e2e5b,
> addrs=[10.29.42.44, 127.0.0.1], sockAddrs=[sap-datanode1/10.29.42.44:49500,
> /127.0.0.1:49500], discPort=49500, order=1, intOrder=1,
> lastExchangeTime=1528447362286, loc=true, ver=2.5.0#20180523-sha1:86e110c7,
> isClient=false]
> [08:42:42,294][SEVERE][tcp-disco-srvr-#2][] Critical system error detected.
> Will be handled accordingly to configured handler [hnd=class
> o.a.i.failure.StopNodeOrHaltFailureHandler, failureCtx=FailureContext
> [type=SYSTEM_WORKER_TERMINATION, err=java.lang.IllegalStateException: Thread
> tcp-disco-srvr-#2 is terminated unexpectedly.]]
> java.lang.IllegalStateException: Thread tcp-disco-srvr-#2 is terminated
> unexpectedly.
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$TcpServer.body(ServerImpl.java:5686)
>
> at
> org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> [08:42:42,294][SEVERE][tcp-disco-srvr-#2][] JVM will be halted immediately
> due to the failure: [failureCtx=FailureContext
> [type=SYSTEM_WORKER_TERMINATION, err=java.lang.IllegalStateException: Thread
> tcp-disco-srvr-#2 is terminated unexpectedly.]]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8751) Possible race on node segmentation.
[ https://issues.apache.org/jira/browse/IGNITE-8751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-8751: Fix Version/s: 2.6 > Possible race on node segmentation. > --- > > Key: IGNITE-8751 > URL: https://issues.apache.org/jira/browse/IGNITE-8751 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.5 >Reporter: Andrew Mashenkov >Assignee: Andrey Gura >Priority: Major > Fix For: 2.6 > > > Segmentation policy may be ignored, probably, due to a race. > See [1] for details. > [1] > [http://apache-ignite-users.70518.x6.nabble.com/Node-pause-for-no-obvious-reason-td21923.html] > Logs from segmented node. > [08:42:42,290][INFO][tcp-disco-sock-reader-#15][TcpDiscoverySpi] Finished > serving remote node connection [rmtAddr=/10.29.42.45:38712, rmtPort=38712 > [08:42:42,290][WARNING][disco-event-worker-#161][GridDiscoveryManager] Local > node SEGMENTED: TcpDiscoveryNode [id=8333aa56-8bf4-4558-a387-809b1d2e2e5b, > addrs=[10.29.42.44, 127.0.0.1], sockAddrs=[sap-datanode1/10.29.42.44:49500, > /127.0.0.1:49500], discPort=49500, order=1, intOrder=1, > lastExchangeTime=1528447362286, loc=true, ver=2.5.0#20180523-sha1:86e110c7, > isClient=false] > [08:42:42,294][SEVERE][tcp-disco-srvr-#2][] Critical system error detected. > Will be handled accordingly to configured handler [hnd=class > o.a.i.failure.StopNodeOrHaltFailureHandler, failureCtx=FailureContext > [type=SYSTEM_WORKER_TERMINATION, err=java.lang.IllegalStateException: Thread > tcp-disco-srvr-#2 is terminated unexpectedly.]] > java.lang.IllegalStateException: Thread tcp-disco-srvr-#2 is terminated > unexpectedly. > at > org.apache.ignite.spi.discovery.tcp.ServerImpl$TcpServer.body(ServerImpl.java:5686) > > at > org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62) > [08:42:42,294][SEVERE][tcp-disco-srvr-#2][] JVM will be halted immediately > due to the failure: [failureCtx=FailureContext > [type=SYSTEM_WORKER_TERMINATION, err=java.lang.IllegalStateException: Thread > tcp-disco-srvr-#2 is terminated unexpectedly.]] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-8749) Exception for "no space left" situation should be propagated to FailureHandler
[ https://issues.apache.org/jira/browse/IGNITE-8749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura reassigned IGNITE-8749: --- Assignee: Andrey Gura > Exception for "no space left" situation should be propagated to FailureHandler > -- > > Key: IGNITE-8749 > URL: https://issues.apache.org/jira/browse/IGNITE-8749 > Project: Ignite > Issue Type: Improvement > Components: persistence >Reporter: Sergey Chugunov >Assignee: Andrey Gura >Priority: Major > Fix For: 2.6 > > > For now if "no space left" situation is detected in > FileWriteAheadLogManager#formatFile method and corresponding exception is > thrown the exception doesn't get propagated to FailureHandler and node > continues working. > As "no space left" is a critical situation, corresponding exception should be > propagated to handler to make necessary actions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-8751) Possible race on node segmentation.
[ https://issues.apache.org/jira/browse/IGNITE-8751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura reassigned IGNITE-8751: --- Assignee: Andrey Gura > Possible race on node segmentation. > --- > > Key: IGNITE-8751 > URL: https://issues.apache.org/jira/browse/IGNITE-8751 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.5 >Reporter: Andrew Mashenkov >Assignee: Andrey Gura >Priority: Major > > Segmentation policy may be ignored, probably, due to a race. > See [1] for details. > [1] > [http://apache-ignite-users.70518.x6.nabble.com/Node-pause-for-no-obvious-reason-td21923.html] > Logs from segmented node. > [08:42:42,290][INFO][tcp-disco-sock-reader-#15][TcpDiscoverySpi] Finished > serving remote node connection [rmtAddr=/10.29.42.45:38712, rmtPort=38712 > [08:42:42,290][WARNING][disco-event-worker-#161][GridDiscoveryManager] Local > node SEGMENTED: TcpDiscoveryNode [id=8333aa56-8bf4-4558-a387-809b1d2e2e5b, > addrs=[10.29.42.44, 127.0.0.1], sockAddrs=[sap-datanode1/10.29.42.44:49500, > /127.0.0.1:49500], discPort=49500, order=1, intOrder=1, > lastExchangeTime=1528447362286, loc=true, ver=2.5.0#20180523-sha1:86e110c7, > isClient=false] > [08:42:42,294][SEVERE][tcp-disco-srvr-#2][] Critical system error detected. > Will be handled accordingly to configured handler [hnd=class > o.a.i.failure.StopNodeOrHaltFailureHandler, failureCtx=FailureContext > [type=SYSTEM_WORKER_TERMINATION, err=java.lang.IllegalStateException: Thread > tcp-disco-srvr-#2 is terminated unexpectedly.]] > java.lang.IllegalStateException: Thread tcp-disco-srvr-#2 is terminated > unexpectedly. > at > org.apache.ignite.spi.discovery.tcp.ServerImpl$TcpServer.body(ServerImpl.java:5686) > > at > org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62) > [08:42:42,294][SEVERE][tcp-disco-srvr-#2][] JVM will be halted immediately > due to the failure: [failureCtx=FailureContext > [type=SYSTEM_WORKER_TERMINATION, err=java.lang.IllegalStateException: Thread > tcp-disco-srvr-#2 is terminated unexpectedly.]] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-7319) Memory leak during creating/destroying local cache
[
https://issues.apache.org/jira/browse/IGNITE-7319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16505967#comment-16505967
]
Andrey Gura edited comment on IGNITE-7319 at 6/8/18 12:25 PM:
--
[~aealeksandrov] Please, don't use Java asserts in test assertions. Use JUnit
assertXxx() methods instead.
was (Author: agura):
[~aealeksandrov] Please, don't use Java asserts in test assertion. Use
assertXxx() methods.
> Memory leak during creating/destroying local cache
> --
>
> Key: IGNITE-7319
> URL: https://issues.apache.org/jira/browse/IGNITE-7319
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.3
>Reporter: Mikhail Cherkasov
>Assignee: Andrey Aleksandrov
>Priority: Major
> Fix For: 2.6
>
> Attachments: Demo.java
>
>
> The following code creates local caches:
> {code}
> private IgniteCache createLocalCache(String name) {
> CacheConfiguration cCfg = new
> CacheConfiguration<>();
> cCfg.setName(name);
> cCfg.setGroupName("localCaches"); // without group leak is much
> bigger!
> cCfg.setStoreKeepBinary(true);
> cCfg.setCacheMode(CacheMode.LOCAL);
> cCfg.setOnheapCacheEnabled(false);
> cCfg.setCopyOnRead(false);
> cCfg.setBackups(0);
> cCfg.setWriteBehindEnabled(false);
> cCfg.setReadThrough(false);
> cCfg.setReadFromBackup(false);
> cCfg.setQueryEntities();
> return ignite.createCache(cCfg).withKeepBinary();
> }
> {code}
> The caches are placed in the queue and are picked up by the worker thread
> which just destroys them after removing from the queue.
> This setup seems to generate a memory leak of about 1GB per day.
> When looking at heap dump, I see all space is occupied by instances of
> java.util.concurrent.ConcurrentSkipListMap$Node.
> User list:
> http://apache-ignite-users.70518.x6.nabble.com/Memory-leak-in-GridCachePartitionExchangeManager-tt18995.html
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7319) Memory leak during creating/destroying local cache
[
https://issues.apache.org/jira/browse/IGNITE-7319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16505967#comment-16505967
]
Andrey Gura commented on IGNITE-7319:
-
[~aealeksandrov] Please, don't use Java asserts in test assertion. Use
assertXxx() methods.
> Memory leak during creating/destroying local cache
> --
>
> Key: IGNITE-7319
> URL: https://issues.apache.org/jira/browse/IGNITE-7319
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.3
>Reporter: Mikhail Cherkasov
>Assignee: Andrey Aleksandrov
>Priority: Major
> Fix For: 2.6
>
> Attachments: Demo.java
>
>
> The following code creates local caches:
> {code}
> private IgniteCache createLocalCache(String name) {
> CacheConfiguration cCfg = new
> CacheConfiguration<>();
> cCfg.setName(name);
> cCfg.setGroupName("localCaches"); // without group leak is much
> bigger!
> cCfg.setStoreKeepBinary(true);
> cCfg.setCacheMode(CacheMode.LOCAL);
> cCfg.setOnheapCacheEnabled(false);
> cCfg.setCopyOnRead(false);
> cCfg.setBackups(0);
> cCfg.setWriteBehindEnabled(false);
> cCfg.setReadThrough(false);
> cCfg.setReadFromBackup(false);
> cCfg.setQueryEntities();
> return ignite.createCache(cCfg).withKeepBinary();
> }
> {code}
> The caches are placed in the queue and are picked up by the worker thread
> which just destroys them after removing from the queue.
> This setup seems to generate a memory leak of about 1GB per day.
> When looking at heap dump, I see all space is occupied by instances of
> java.util.concurrent.ConcurrentSkipListMap$Node.
> User list:
> http://apache-ignite-users.70518.x6.nabble.com/Memory-leak-in-GridCachePartitionExchangeManager-tt18995.html
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-5977) [Test Failed] IgniteClientDiscoveryDataStructuresTest.testSequence
[ https://issues.apache.org/jira/browse/IGNITE-5977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-5977: Fix Version/s: 2.6 > [Test Failed] IgniteClientDiscoveryDataStructuresTest.testSequence > --- > > Key: IGNITE-5977 > URL: https://issues.apache.org/jira/browse/IGNITE-5977 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.1 >Reporter: Eduard Shangareev >Assignee: Aleksey Plekhanov >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.6 > > > Fails locally. > Example of failing > http://ci.ignite.apache.org/viewLog.html?buildId=760759=buildResultsDiv=Ignite20Tests_IgniteDataStrucutures#testNameId2829619862655631000 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-602) [Test] GridToStringBuilder is vulnerable for StackOverflowError caused by infinite recursion
[ https://issues.apache.org/jira/browse/IGNITE-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16500595#comment-16500595 ] Andrey Gura commented on IGNITE-602: This changes requires reintegration with master branch due to a lot of changes. > [Test] GridToStringBuilder is vulnerable for StackOverflowError caused by > infinite recursion > > > Key: IGNITE-602 > URL: https://issues.apache.org/jira/browse/IGNITE-602 > Project: Ignite > Issue Type: Bug > Components: general >Reporter: Artem Shutak >Assignee: Ryabov Dmitrii >Priority: Major > Labels: MakeTeamcityGreenAgain, Muted_test > Fix For: 2.6 > > > See test > org.gridgain.grid.util.tostring.GridToStringBuilderSelfTest#_testToStringCheckAdvancedRecursionPrevention > and related TODO in same source file. > Also take a look at > http://stackoverflow.com/questions/11300203/most-efficient-way-to-prevent-an-infinite-recursion-in-tostring > Test should be unmuted on TC after fix. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-602) [Test] GridToStringBuilder is vulnerable for StackOverflowError caused by infinite recursion
[ https://issues.apache.org/jira/browse/IGNITE-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16500595#comment-16500595 ] Andrey Gura edited comment on IGNITE-602 at 6/4/18 5:41 PM: This changes require reintegration with master branch due to a lot of changes. was (Author: agura): This changes requires reintegration with master branch due to a lot of changes. > [Test] GridToStringBuilder is vulnerable for StackOverflowError caused by > infinite recursion > > > Key: IGNITE-602 > URL: https://issues.apache.org/jira/browse/IGNITE-602 > Project: Ignite > Issue Type: Bug > Components: general >Reporter: Artem Shutak >Assignee: Ryabov Dmitrii >Priority: Major > Labels: MakeTeamcityGreenAgain, Muted_test > Fix For: 2.6 > > > See test > org.gridgain.grid.util.tostring.GridToStringBuilderSelfTest#_testToStringCheckAdvancedRecursionPrevention > and related TODO in same source file. > Also take a look at > http://stackoverflow.com/questions/11300203/most-efficient-way-to-prevent-an-infinite-recursion-in-tostring > Test should be unmuted on TC after fix. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-602) [Test] GridToStringBuilder is vulnerable for StackOverflowError caused by infinite recursion
[ https://issues.apache.org/jira/browse/IGNITE-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16500595#comment-16500595 ] Andrey Gura edited comment on IGNITE-602 at 6/4/18 5:41 PM: This changes require reintegration with master branch and retesting due to a lot of changes. was (Author: agura): This changes require reintegration with master branch due to a lot of changes. > [Test] GridToStringBuilder is vulnerable for StackOverflowError caused by > infinite recursion > > > Key: IGNITE-602 > URL: https://issues.apache.org/jira/browse/IGNITE-602 > Project: Ignite > Issue Type: Bug > Components: general >Reporter: Artem Shutak >Assignee: Ryabov Dmitrii >Priority: Major > Labels: MakeTeamcityGreenAgain, Muted_test > Fix For: 2.6 > > > See test > org.gridgain.grid.util.tostring.GridToStringBuilderSelfTest#_testToStringCheckAdvancedRecursionPrevention > and related TODO in same source file. > Also take a look at > http://stackoverflow.com/questions/11300203/most-efficient-way-to-prevent-an-infinite-recursion-in-tostring > Test should be unmuted on TC after fix. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8642) Failure processor should dump state of all threads
[
https://issues.apache.org/jira/browse/IGNITE-8642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16500580#comment-16500580
]
Andrey Gura commented on IGNITE-8642:
-
[~andrey-kuznetsov] Please rename {{IGNITE_DUMP_THREADS_ON_FAILURE_PROP}}
property to {{IGNITE_DUMP_THREADS_ON_FAILURE}} and move it to
{{IgniteSystemProperties}}. Also properly comment added properties.
> Failure processor should dump state of all threads
> --
>
> Key: IGNITE-8642
> URL: https://issues.apache.org/jira/browse/IGNITE-8642
> Project: Ignite
> Issue Type: Improvement
>Reporter: Andrey Gura
>Assignee: Andrey Kuznetsov
>Priority: Major
> Fix For: 2.6
>
>
> Failure processor should dump state of all threads before failure handler is
> invoked.
> Use {{org.apache.ignite.internal.util.IgniteUtils#dumpThreads}} method.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8690) Missed package-info for some packages
[
https://issues.apache.org/jira/browse/IGNITE-8690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16500480#comment-16500480
]
Andrey Gura commented on IGNITE-8690:
-
Guys, in the future please just exclude `internal`-packages from package info
checking.
> Missed package-info for some packages
> -
>
> Key: IGNITE-8690
> URL: https://issues.apache.org/jira/browse/IGNITE-8690
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.5
>Reporter: Pavel Kovalenko
>Assignee: Pavel Kovalenko
>Priority: Major
> Fix For: 2.6
>
>
> List of affected packages:
> {noformat}
> org.apache.ignite.spi.communication.tcp.internal
> org.apache.ignite.spi.discovery.zk
> org.apache.ignite.spi.discovery.zk.internal
> org.apache.ignite.ml.structures.partition
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8562) Turn system-critical Ignite threads into GridWorkers
[
https://issues.apache.org/jira/browse/IGNITE-8562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16500375#comment-16500375
]
Andrey Gura commented on IGNITE-8562:
-
[~andrey-kuznetsov] I've reviewed your changes. Please see my comments in
Upsource.
> Turn system-critical Ignite threads into GridWorkers
>
>
> Key: IGNITE-8562
> URL: https://issues.apache.org/jira/browse/IGNITE-8562
> Project: Ignite
> Issue Type: Improvement
>Reporter: Andrey Kuznetsov
>Assignee: Andrey Kuznetsov
>Priority: Major
> Fix For: 2.6
>
>
> The goal of the change is to make system-critical threads (in terms of
> IEP-14, [1]) available to {{WorkersControlMXBean}}.
> [1]
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-14+Ignite+failures+handling
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8658) Add info message for complete partition exchange
[ https://issues.apache.org/jira/browse/IGNITE-8658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-8658: Fix Version/s: 2.6 > Add info message for complete partition exchange > > > Key: IGNITE-8658 > URL: https://issues.apache.org/jira/browse/IGNITE-8658 > Project: Ignite > Issue Type: Bug > Components: general >Reporter: Mikhail Cherkasov >Assignee: Mikhail Cherkasov >Priority: Major > Fix For: 2.6 > > > It's very difficult to debug PME problems without message about it's > completion. This message only available on debug level, however it's very > often that we have only info level which needs to be analysed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8293) BinaryUtils#isCustomJavaSerialization fails when only readObject is declared in a class
[
https://issues.apache.org/jira/browse/IGNITE-8293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16495376#comment-16495376
]
Andrey Gura commented on IGNITE-8293:
-
Thanks, [~MihkelJ]! Please move ticket to the "Patch available" status using
"Submit patch" button.
> BinaryUtils#isCustomJavaSerialization fails when only readObject is declared
> in a class
> ---
>
> Key: IGNITE-8293
> URL: https://issues.apache.org/jira/browse/IGNITE-8293
> Project: Ignite
> Issue Type: Bug
> Components: binary
>Affects Versions: 2.4
>Reporter: MihkelJ
>Assignee: MihkelJ
>Priority: Minor
> Fix For: 2.6
>
> Attachments: IGNITE-8293.patch
>
>
> Consider this class:
>
> {code:java}
> public class Test implements Serializable {
> private transient AtomicBoolean dirty = new AtomicBoolean(false);
> private void readObject(java.io.ObjectInputStream in) throws IOException,
> ClassNotFoundException {
> dirty = new AtomicBoolean(false);
> }
> //methods to check and mark class as dirty
> }{code}
> {{isCustomJavaSerialization}} will get a {{NoSuchMethodException}} when
> trying to grab the {{writeObject}} method and falsely conclude that Test
> doesn't use custom serialization.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-8642) Failure processor should dump state of all threads
Andrey Gura created IGNITE-8642:
---
Summary: Failure processor should dump state of all threads
Key: IGNITE-8642
URL: https://issues.apache.org/jira/browse/IGNITE-8642
Project: Ignite
Issue Type: Improvement
Reporter: Andrey Gura
Fix For: 2.6
Failure processor should dump state of all threads before failure processor
will be invoked.
Use {{org.apache.ignite.internal.util.IgniteUtils#dumpThreads}} method.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8641) SpringDataExample should use example-ignite.xml config
[
https://issues.apache.org/jira/browse/IGNITE-8641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura updated IGNITE-8641:
Description:
{{SpringDataExample}} uses
{{org.apache.ignite.examples.springdata.SpringAppCfg}} as Spring configuration
while all other examples use {{example-ignite.xml}} configuration file.
It leads to inconsistent examples behaviour.
was:
{{SpringDataExample}} uses
{{org.apache.ignite.examples.springdata.SpringAppCfg}} as Spring configuration
while all other example uses {{example-ignite.xml}} configuration file.
It leads to inconsistent examples behaviour.
> SpringDataExample should use example-ignite.xml config
> --
>
> Key: IGNITE-8641
> URL: https://issues.apache.org/jira/browse/IGNITE-8641
> Project: Ignite
> Issue Type: Bug
>Reporter: Andrey Gura
>Priority: Major
> Labels: newbie
> Fix For: 2.6
>
>
> {{SpringDataExample}} uses
> {{org.apache.ignite.examples.springdata.SpringAppCfg}} as Spring
> configuration while all other examples use {{example-ignite.xml}}
> configuration file.
> It leads to inconsistent examples behaviour.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-8641) SpringDataExample should use example-ignite.xml config
Andrey Gura created IGNITE-8641:
---
Summary: SpringDataExample should use example-ignite.xml config
Key: IGNITE-8641
URL: https://issues.apache.org/jira/browse/IGNITE-8641
Project: Ignite
Issue Type: Bug
Reporter: Andrey Gura
Fix For: 2.6
{{SpringDataExample}} uses
{{org.apache.ignite.examples.springdata.SpringAppCfg}} as Spring configuration
while all other example uses {{example-ignite.xml}} configuration file.
It leads to inconsistent examples behaviour.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8293) BinaryUtils#isCustomJavaSerialization fails when only readObject is declared in a class
[
https://issues.apache.org/jira/browse/IGNITE-8293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493947#comment-16493947
]
Andrey Gura commented on IGNITE-8293:
-
[~MihkelJ], I've reviewed your patch and have a comment:
{{BinaryUtilsIsCustomSerializationTest}} doesn't contains Apache 2.0 license
header and javadocs. Also this test uses JUnit 4 while we still use JUnit 3.
Test is ok, but it isn't related with binary marshaller. I think it would be
great if you remove your tests and add test cases to
{{BinaryMarshallerSelfTest}}. Use existing test cases as examples. Is there any
chance that you fix this comment?
> BinaryUtils#isCustomJavaSerialization fails when only readObject is declared
> in a class
> ---
>
> Key: IGNITE-8293
> URL: https://issues.apache.org/jira/browse/IGNITE-8293
> Project: Ignite
> Issue Type: Bug
> Components: binary
>Affects Versions: 2.4
>Reporter: MihkelJ
>Assignee: MihkelJ
>Priority: Minor
> Fix For: 2.6
>
> Attachments: IGNITE-8293.patch
>
>
> Consider this class:
>
> {code:java}
> public class Test implements Serializable {
> private transient AtomicBoolean dirty = new AtomicBoolean(false);
> private void readObject(java.io.ObjectInputStream in) throws IOException,
> ClassNotFoundException {
> dirty = new AtomicBoolean(false);
> }
> //methods to check and mark class as dirty
> }{code}
> {{isCustomJavaSerialization}} will get a {{NoSuchMethodException}} when
> trying to grab the {{writeObject}} method and falsely conclude that Test
> doesn't use custom serialization.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-4210) CacheLoadingConcurrentGridStartSelfTest.testLoadCacheFromStore() test lose data.
[ https://issues.apache.org/jira/browse/IGNITE-4210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493695#comment-16493695 ] Andrey Gura commented on IGNITE-4210: - I'll take a look. > CacheLoadingConcurrentGridStartSelfTest.testLoadCacheFromStore() test lose > data. > > > Key: IGNITE-4210 > URL: https://issues.apache.org/jira/browse/IGNITE-4210 > Project: Ignite > Issue Type: Bug >Reporter: Anton Vinogradov >Assignee: Alexey Kuznetsov >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.6 > > > org.apache.ignite.internal.processors.cache.distributed.CacheLoadingConcurrentGridStartSelfTest#testLoadCacheFromStore > sometimes have failures. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-1094) Ignite.createCache(CacheConfiguration) hangs if some exception occurs during cache initialization
[ https://issues.apache.org/jira/browse/IGNITE-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-1094: Fix Version/s: 2.6 > Ignite.createCache(CacheConfiguration) hangs if some exception occurs during > cache initialization > - > > Key: IGNITE-1094 > URL: https://issues.apache.org/jira/browse/IGNITE-1094 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Sergey Evdokimov >Assignee: Vyacheslav Koptilin >Priority: Major > Labels: Muted_test > Fix For: 2.6 > > > User can pass broken configuration, for example, store factory that throws > exception from create() method. I created test to demonstrate the problem. > See IgniteDynamicCacheStartSelfTest#testBrokenStoreFactory in 'ignite-1094' > branch -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7818) Incorrect assertion in PDS page eviction method
[
https://issues.apache.org/jira/browse/IGNITE-7818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura updated IGNITE-7818:
Fix Version/s: 2.6
> Incorrect assertion in PDS page eviction method
> ---
>
> Key: IGNITE-7818
> URL: https://issues.apache.org/jira/browse/IGNITE-7818
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Reporter: Aleksey Plekhanov
>Assignee: Ivan Fedotov
>Priority: Major
> Fix For: 2.6
>
> Attachments: PageMemoryPdsAssertTest.java
>
>
> There is an assertion in the method
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.Segment#removePageForReplacement:
>
> {code:java}
> assert relRmvAddr != INVALID_REL_PTR;{code}
> Which seems potentially dangerous. In some rare cases, when count of
> interations more then 40% of allocated pages and all processed pages are
> aquired, the {{relRmvAddr}} variable will be uninitialized and
> {{AssertionException}} will be thrown. But it's a correct case and page to
> evict can be found later in the method {{tryToFindSequentially.}}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-8529) Implement testing framework for checking WAL delta records consistency
[ https://issues.apache.org/jira/browse/IGNITE-8529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura reassigned IGNITE-8529: --- Assignee: Aleksey Plekhanov > Implement testing framework for checking WAL delta records consistency > -- > > Key: IGNITE-8529 > URL: https://issues.apache.org/jira/browse/IGNITE-8529 > Project: Ignite > Issue Type: New Feature > Components: persistence >Reporter: Ivan Rakov >Assignee: Aleksey Plekhanov >Priority: Major > Fix For: 2.6 > > > We use sharp checkpointing of page memory in persistent mode. That implies > that we write two types of record to write-ahead log: logical (e.g. data > records) and phyisical (page snapshots + binary delta records). Physical > records are applied only when node crashes/stops during ongoing checkpoint. > We have the following invariant: checkpoint #(n-1) + all physical records = > checkpoint #n. > If correctness of physical records is broken, Ignite node may recover with > incorrect page memory state, which in turn can bring unexpected delayed > errors. However, consistency of physical records is poorly tested: only small > part of our autotests perform node restarts, and even less part of them > perform node stop when ongoing checkpoint is running. > We should implement abstract test that: > 1. Enforces checkpoint, freezes memory state at the moment of checkpoint. > 2. Performs necessary test load. > 3. Enforces checkpoint again, replays WAL and checks that page store at the > moment of previous checkpoint with all applied physical records exactly > equals to current checkpoint state. > Except for checking correctness, test framework should do the following: > 1. Gather statistics (like histogram) for types of wriiten physical records. > That will help us to know what types of physical records are covered by test. > 2. Visualize expected and actual page state (with all applied physical > records) if incorrect page state is detected. > Regarding implementation, I suppose we can use checkpoint listener mechanism > to freeze page memory state at the moment of checkpoint. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8529) Implement testing framework for checking WAL delta records consistency
[ https://issues.apache.org/jira/browse/IGNITE-8529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-8529: Fix Version/s: 2.6 > Implement testing framework for checking WAL delta records consistency > -- > > Key: IGNITE-8529 > URL: https://issues.apache.org/jira/browse/IGNITE-8529 > Project: Ignite > Issue Type: New Feature > Components: persistence >Reporter: Ivan Rakov >Priority: Major > Fix For: 2.6 > > > We use sharp checkpointing of page memory in persistent mode. That implies > that we write two types of record to write-ahead log: logical (e.g. data > records) and phyisical (page snapshots + binary delta records). Physical > records are applied only when node crashes/stops during ongoing checkpoint. > We have the following invariant: checkpoint #(n-1) + all physical records = > checkpoint #n. > If correctness of physical records is broken, Ignite node may recover with > incorrect page memory state, which in turn can bring unexpected delayed > errors. However, consistency of physical records is poorly tested: only small > part of our autotests perform node restarts, and even less part of them > perform node stop when ongoing checkpoint is running. > We should implement abstract test that: > 1. Enforces checkpoint, freezes memory state at the moment of checkpoint. > 2. Performs necessary test load. > 3. Enforces checkpoint again, replays WAL and checks that page store at the > moment of previous checkpoint with all applied physical records exactly > equals to current checkpoint state. > Except for checking correctness, test framework should do the following: > 1. Gather statistics (like histogram) for types of wriiten physical records. > That will help us to know what types of physical records are covered by test. > 2. Visualize expected and actual page state (with all applied physical > records) if incorrect page state is detected. > Regarding implementation, I suppose we can use checkpoint listener mechanism > to freeze page memory state at the moment of checkpoint. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8563) WAL file archiver does not propagate file archiving error to error handler
[
https://issues.apache.org/jira/browse/IGNITE-8563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489055#comment-16489055
]
Andrey Gura commented on IGNITE-8563:
-
Fixed and merged to master branch.
> WAL file archiver does not propagate file archiving error to error handler
> --
>
> Key: IGNITE-8563
> URL: https://issues.apache.org/jira/browse/IGNITE-8563
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.5
>Reporter: Alexey Goncharuk
>Assignee: Andrey Gura
>Priority: Major
> Fix For: 2.6
>
>
> I observed this error when a disk with WAL archive left out of space:
> {code}
> ...
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.finishTx(GridDhtTxLocal.java:464)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.commitDhtLocalAsync(GridDhtTxLocal.java:517)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finishDhtLocal(IgniteTxHandler.java:940)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finish(IgniteTxHandler.java:819)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processNearTxFinishRequest(IgniteTxHandler.java:775)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.access$200(IgniteTxHandler.java:97)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$3.apply(IgniteTxHandler.java:189)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$3.apply(IgniteTxHandler.java:187)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1054)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:579)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:378)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:304)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:99)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:293)
> 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.communication.GridIoManager.access$4200(GridIoManager.java:125)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1091)
> at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.run(StripedExecutor.java:511)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.apache.ignite.IgniteException: Runtime failure on row:
> Row@1ec13b23[ key: 4458000681143704309, val:
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doPut(BPlusTree.java:2119)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.putx(BPlusTree.java:2066)
> at
> org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.putx(H2TreeIndex.java:247)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.addToIndex(GridH2Table.java:548)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.update(GridH2Table.java:480)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.store(IgniteH2Indexing.java:659)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.store(GridQueryProcessor.java:1866)
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.store(GridCacheQueryManager.java:403)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.finishUpdate(IgniteCacheOffheapManagerImpl.java:1393)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:1257)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.invoke(GridCacheOffheapManager.java:1511)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.invoke(IgniteCacheOffheapManagerImpl.java:352)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.storeValue(GridCacheMapEntry.java:3602)
>
[jira] [Assigned] (IGNITE-8563) WAL file archiver does not propagate file archiving error to error handler
[
https://issues.apache.org/jira/browse/IGNITE-8563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura reassigned IGNITE-8563:
---
Assignee: Andrey Gura
> WAL file archiver does not propagate file archiving error to error handler
> --
>
> Key: IGNITE-8563
> URL: https://issues.apache.org/jira/browse/IGNITE-8563
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.5
>Reporter: Alexey Goncharuk
>Assignee: Andrey Gura
>Priority: Major
> Fix For: 2.6
>
>
> I observed this error when a disk with WAL archive left out of space:
> {code}
> ...
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.finishTx(GridDhtTxLocal.java:464)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.commitDhtLocalAsync(GridDhtTxLocal.java:517)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finishDhtLocal(IgniteTxHandler.java:940)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finish(IgniteTxHandler.java:819)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processNearTxFinishRequest(IgniteTxHandler.java:775)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.access$200(IgniteTxHandler.java:97)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$3.apply(IgniteTxHandler.java:189)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$3.apply(IgniteTxHandler.java:187)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1054)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:579)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:378)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:304)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:99)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:293)
> 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.communication.GridIoManager.access$4200(GridIoManager.java:125)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1091)
> at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.run(StripedExecutor.java:511)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.apache.ignite.IgniteException: Runtime failure on row:
> Row@1ec13b23[ key: 4458000681143704309, val:
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doPut(BPlusTree.java:2119)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.putx(BPlusTree.java:2066)
> at
> org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.putx(H2TreeIndex.java:247)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.addToIndex(GridH2Table.java:548)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.update(GridH2Table.java:480)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.store(IgniteH2Indexing.java:659)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.store(GridQueryProcessor.java:1866)
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.store(GridCacheQueryManager.java:403)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.finishUpdate(IgniteCacheOffheapManagerImpl.java:1393)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:1257)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.invoke(GridCacheOffheapManager.java:1511)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.invoke(IgniteCacheOffheapManagerImpl.java:352)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.storeValue(GridCacheMapEntry.java:3602)
> at
>
[jira] [Commented] (IGNITE-8584) Provide ability to terminate any thread with enabled test features
[
https://issues.apache.org/jira/browse/IGNITE-8584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16488958#comment-16488958
]
Andrey Gura commented on IGNITE-8584:
-
LGTM! Merged to master branch. Thanks for contribution!
> Provide ability to terminate any thread with enabled test features
> --
>
> Key: IGNITE-8584
> URL: https://issues.apache.org/jira/browse/IGNITE-8584
> Project: Ignite
> Issue Type: New Feature
>Reporter: Andrey Gura
>Assignee: Dmitriy Sorokin
>Priority: Major
> Fix For: 2.6
>
>
> eWe already have {{WorkersControlMXBean}} that provides possibility to
> interrupt thread registered in system workers registry. We also want stop any
> thread in the system for testing purposes.
> Method {{stop(long id)}} should be added that have to find thread by id and
> stop it.
> Example of thread information form thread dump where thread id is bold:
> "tcp-disco-msg-worker-#2" #*62* prio=10 os_prio=0 tid=0x7f2519714800
> nid=0x32b4 runnable [0x7f24a425]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8584) Provide ability to terminate any thread with enabled test features
[
https://issues.apache.org/jira/browse/IGNITE-8584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura updated IGNITE-8584:
Description:
eWe already have {{WorkersControlMXBean}} that provides possibility to
interrupt thread registered in system workers registry. We also want stop any
thread in the system for testing purposes.
Method {{stop(long id)}} should be added that have to find thread by id and
stop it.
Example of thread information form thread dump where thread id is bold:
"tcp-disco-msg-worker-#2" #*62* prio=10 os_prio=0 tid=0x7f2519714800
nid=0x32b4 runnable [0x7f24a425]
was:
eWe already have {{WorkersControlMXBean}} that provides possibility to
interrupt thread registered in system workers registry. We also want stop any
thread in the system for testing purposes.
Method {{stop(long id)}} should be added that have to find thread by id and
stop it.
Example of thread information form thread dump where thread id is bold:
"tcp-disco-msg-worker-#2" *#62* prio=10 os_prio=0 tid=0x7f2519714800
nid=0x32b4 runnable [0x7f24a425]
> Provide ability to terminate any thread with enabled test features
> --
>
> Key: IGNITE-8584
> URL: https://issues.apache.org/jira/browse/IGNITE-8584
> Project: Ignite
> Issue Type: New Feature
>Reporter: Andrey Gura
>Assignee: Dmitriy Sorokin
>Priority: Major
> Fix For: 2.6
>
>
> eWe already have {{WorkersControlMXBean}} that provides possibility to
> interrupt thread registered in system workers registry. We also want stop any
> thread in the system for testing purposes.
> Method {{stop(long id)}} should be added that have to find thread by id and
> stop it.
> Example of thread information form thread dump where thread id is bold:
> "tcp-disco-msg-worker-#2" #*62* prio=10 os_prio=0 tid=0x7f2519714800
> nid=0x32b4 runnable [0x7f24a425]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8584) Provide ability to terminate any thread with enabled test features
[
https://issues.apache.org/jira/browse/IGNITE-8584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura updated IGNITE-8584:
Description:
eWe already have {{WorkersControlMXBean}} that provides possibility to
interrupt thread registered in system workers registry. We also want stop any
thread in the system for testing purposes.
Method {{stop(long id)}} should be added that have to find thread by id and
stop it.
Example of thread information form thread dump where thread id is bold:
"tcp-disco-msg-worker-#2" *#62* prio=10 os_prio=0 tid=0x7f2519714800
nid=0x32b4 runnable [0x7f24a425]
was:
We already have {{WorkersControlMXBean}} that provides possibility to interrupt
thread registered in system workers registry. We also want stop any thread in
the system for testing purposes.
Method {{stop(String tid_hex)}} should be added that have to find thread by id
and stop it.
> Provide ability to terminate any thread with enabled test features
> --
>
> Key: IGNITE-8584
> URL: https://issues.apache.org/jira/browse/IGNITE-8584
> Project: Ignite
> Issue Type: New Feature
>Reporter: Andrey Gura
>Assignee: Dmitriy Sorokin
>Priority: Major
> Fix For: 2.6
>
>
> eWe already have {{WorkersControlMXBean}} that provides possibility to
> interrupt thread registered in system workers registry. We also want stop any
> thread in the system for testing purposes.
> Method {{stop(long id)}} should be added that have to find thread by id and
> stop it.
> Example of thread information form thread dump where thread id is bold:
> "tcp-disco-msg-worker-#2" *#62* prio=10 os_prio=0 tid=0x7f2519714800
> nid=0x32b4 runnable [0x7f24a425]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8584) Provide ability to terminate any thread with enabled test features
[
https://issues.apache.org/jira/browse/IGNITE-8584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura updated IGNITE-8584:
Description:
We already have {{WorkersControlMXBean}} that provides possibility to interrupt
thread registered in system workers registry. We also want stop any thread in
the system for testing purposes.
Method {{stop(String tid_hex)}} should be added that have to find thread by id
and stop it.
was:
We already have {{WorkersControlMXBean}} that provides possibility to interrupt
thread registered in system workers registry. We also want stop any thread in
the system for testing purposes.
Method {{stop(String threadName)}} should be added that have to find thread by
name and stop it.
> Provide ability to terminate any thread with enabled test features
> --
>
> Key: IGNITE-8584
> URL: https://issues.apache.org/jira/browse/IGNITE-8584
> Project: Ignite
> Issue Type: New Feature
>Reporter: Andrey Gura
>Assignee: Dmitriy Sorokin
>Priority: Major
> Fix For: 2.6
>
>
> We already have {{WorkersControlMXBean}} that provides possibility to
> interrupt thread registered in system workers registry. We also want stop any
> thread in the system for testing purposes.
> Method {{stop(String tid_hex)}} should be added that have to find thread by
> id and stop it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8586) Minor fix for Apache Ignite's release procedure
[ https://issues.apache.org/jira/browse/IGNITE-8586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16487661#comment-16487661 ] Andrey Gura commented on IGNITE-8586: - Thanks for contribution! Merged to master and ignite-2.5 branches. > Minor fix for Apache Ignite's release procedure > --- > > Key: IGNITE-8586 > URL: https://issues.apache.org/jira/browse/IGNITE-8586 > Project: Ignite > Issue Type: Bug >Reporter: Peter Ivanov >Assignee: Peter Ivanov >Priority: Major > Fix For: 2.5 > > > Fix package.sh to not require sudo permissions for packages build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8586) Minor fix for Apache Ignite's release procedure
[ https://issues.apache.org/jira/browse/IGNITE-8586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-8586: Fix Version/s: 2.5 > Minor fix for Apache Ignite's release procedure > --- > > Key: IGNITE-8586 > URL: https://issues.apache.org/jira/browse/IGNITE-8586 > Project: Ignite > Issue Type: Bug >Reporter: Peter Ivanov >Assignee: Peter Ivanov >Priority: Major > Fix For: 2.5 > > > Fix package.sh to not require sudo permissions for packages build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8584) Provide ability to terminate any thread with enabled test features
Andrey Gura created IGNITE-8584:
---
Summary: Provide ability to terminate any thread with enabled test
features
Key: IGNITE-8584
URL: https://issues.apache.org/jira/browse/IGNITE-8584
Project: Ignite
Issue Type: New Feature
Reporter: Andrey Gura
Fix For: 2.6
We already have {{WorkersControlMXBean}} that provides possibility to interrupt
thread registered in system workers registry. We also want stop any thread in
the system for testing purposes.
Method {{stop(String threadName)}} should be added that have to find thread by
name and stop it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8461) Scala-2.10 modules compilation failure under JDK 9
[
https://issues.apache.org/jira/browse/IGNITE-8461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16484067#comment-16484067
]
Andrey Gura commented on IGNITE-8461:
-
[~vveider] TC run contains failed build configurations: {{Scala (Examples)}},
{{Scala (Visor Console)}} and {{RDD}}. All are failed with the same problem:
{{java.lang.NoClassDefFoundError: scala/Product$class}}
I've reran this configuration in order to exclude environment problems. Will
check later.
> Scala-2.10 modules compilation failure under JDK 9
> --
>
> Key: IGNITE-8461
> URL: https://issues.apache.org/jira/browse/IGNITE-8461
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Peter Ivanov
>Assignee: Peter Ivanov
>Priority: Critical
> Fix For: 2.6
>
>
> {code}
> [ERROR] error: java.lang.NoClassDefFoundError: javax/tools/ToolProvider
> [INFO]at
> scala.reflect.io.JavaToolsPlatformArchive.iterator(ZipArchive.scala:242)
> [INFO]at
> scala.collection.IterableLike$class.foreach(IterableLike.scala:72)
> [INFO]at scala.reflect.io.AbstractFile.foreach(AbstractFile.scala:92)
> [INFO]at
> scala.tools.nsc.util.DirectoryClassPath.traverse(ClassPath.scala:308)
> [INFO]at
> scala.tools.nsc.util.DirectoryClassPath.x$16$lzycompute(ClassPath.scala:317)
> [INFO]at
> scala.tools.nsc.util.DirectoryClassPath.x$16(ClassPath.scala:317)
> [INFO]at
> scala.tools.nsc.util.DirectoryClassPath.packages$lzycompute(ClassPath.scala:317)
> [INFO]at
> scala.tools.nsc.util.DirectoryClassPath.packages(ClassPath.scala:317)
> [INFO]at
> scala.tools.nsc.util.DirectoryClassPath.packages(ClassPath.scala:297)
> [INFO]at
> scala.tools.nsc.util.MergedClassPath$$anonfun$packages$1.apply(ClassPath.scala:375)
> [INFO]at
> scala.tools.nsc.util.MergedClassPath$$anonfun$packages$1.apply(ClassPath.scala:375)
> [INFO]at scala.collection.Iterator$class.foreach(Iterator.scala:727)
> [INFO]at
> scala.collection.AbstractIterator.foreach(Iterator.scala:1157)
> [INFO]at
> scala.collection.IterableLike$class.foreach(IterableLike.scala:72)
> [INFO]at scala.collection.AbstractIterable.foreach(Iterable.scala:54)
> [INFO]at
> scala.tools.nsc.util.MergedClassPath.packages$lzycompute(ClassPath.scala:375)
> [INFO]at
> scala.tools.nsc.util.MergedClassPath.packages(ClassPath.scala:370)
> [INFO]at
> scala.tools.nsc.symtab.SymbolLoaders$PackageLoader.doComplete(SymbolLoaders.scala:243)
> [INFO]at
> scala.tools.nsc.symtab.SymbolLoaders$SymbolLoader.complete(SymbolLoaders.scala:194)
> [INFO]at
> scala.reflect.internal.Symbols$Symbol.info(Symbols.scala:1231)
> [INFO]at
> scala.reflect.internal.Mirrors$RootsBase.init(Mirrors.scala:240)
> [INFO]at scala.tools.nsc.Global.rootMirror$lzycompute(Global.scala:59)
> [INFO]at scala.tools.nsc.Global.rootMirror(Global.scala:57)
> [INFO]at scala.tools.nsc.Global.rootMirror(Global.scala:37)
> [INFO]at
> scala.reflect.internal.Definitions$DefinitionsClass.(Definitions.scala:166)
> [INFO]at
> scala.reflect.internal.Definitions$definitions$.(Definitions.scala:20)
> [INFO]at
> scala.reflect.internal.SymbolTable.definitions$lzycompute(SymbolTable.scala:13)
> [INFO]at
> scala.reflect.internal.SymbolTable.definitions(SymbolTable.scala:13)
> [INFO]at scala.tools.nsc.Global$Run.(Global.scala:1290)
> [INFO]at scala.tools.nsc.Driver.doCompile(Driver.scala:32)
> [INFO]at scala.tools.nsc.Main$.doCompile(Main.scala:79)
> [INFO]at scala.tools.nsc.Driver.process(Driver.scala:54)
> [INFO]at scala.tools.nsc.Driver.main(Driver.scala:67)
> [INFO]at scala.tools.nsc.Main.main(Main.scala)
> [INFO]at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [INFO]at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [INFO]at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [INFO]at java.base/java.lang.reflect.Method.invoke(Method.java:564)
> [INFO]at
> scala_maven_executions.MainHelper.runMain(MainHelper.java:164)
> [INFO]at
> scala_maven_executions.MainWithArgsInFile.main(MainWithArgsInFile.java:26)
> [INFO]
> [INFO] java.lang.reflect.InvocationTargetException
> [INFO]at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [INFO]at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [INFO]at
>
[jira] [Assigned] (IGNITE-8514) Missed descriptions for a few packages in Javadoc
[
https://issues.apache.org/jira/browse/IGNITE-8514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura reassigned IGNITE-8514:
---
Assignee: (was: Andrey Gura)
> Missed descriptions for a few packages in Javadoc
> -
>
> Key: IGNITE-8514
> URL: https://issues.apache.org/jira/browse/IGNITE-8514
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Sergey Kozlov
>Priority: Major
> Fix For: 2.5
>
>
> The packages below have no descriptions in javadoc:
> /doc/javadoc/overview-summary.html
> {noformat}
> org.apache.ignite.spi.communication.tcp.internal
> org.apache.ignite.spi.discovery.zk
> org.apache.ignite.spi.discovery.zk.internal
> org.apache.ignite.ml.structures.partition
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-8514) Missed descriptions for a few packages in Javadoc
[
https://issues.apache.org/jira/browse/IGNITE-8514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura reassigned IGNITE-8514:
---
Assignee: Andrey Gura
> Missed descriptions for a few packages in Javadoc
> -
>
> Key: IGNITE-8514
> URL: https://issues.apache.org/jira/browse/IGNITE-8514
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Sergey Kozlov
>Assignee: Andrey Gura
>Priority: Major
> Fix For: 2.5
>
>
> The packages below have no descriptions in javadoc:
> /doc/javadoc/overview-summary.html
> {noformat}
> org.apache.ignite.spi.communication.tcp.internal
> org.apache.ignite.spi.discovery.zk
> org.apache.ignite.spi.discovery.zk.internal
> org.apache.ignite.ml.structures.partition
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8110) GridCacheWriteBehindStore.Flusher thread uses the wrong transformation from milliseconds to nanoseconds.
[
https://issues.apache.org/jira/browse/IGNITE-8110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura updated IGNITE-8110:
Fix Version/s: (was: 2.6)
> GridCacheWriteBehindStore.Flusher thread uses the wrong transformation from
> milliseconds to nanoseconds.
>
>
> Key: IGNITE-8110
> URL: https://issues.apache.org/jira/browse/IGNITE-8110
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.4
>Reporter: Vyacheslav Koptilin
>Assignee: Anton Kurbanov
>Priority: Minor
> Fix For: 2.5
>
>
> The initial value of a cache flushing frequency is defined as follows:
> {code}
> /** Cache flushing frequence in nanos. */
> protected long cacheFlushFreqNanos = cacheFlushFreq * 1000;
> {code}
> where is {{cacheFlushFreq}} is equal to
> {code}
> /** Default flush frequency for write-behind cache store in milliseconds.
> */
> public static final long DFLT_WRITE_BEHIND_FLUSH_FREQUENCY = 5000;
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8523) Java and Scala spark examples are mixed
[
https://issues.apache.org/jira/browse/IGNITE-8523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura updated IGNITE-8523:
Fix Version/s: (was: 2.5)
2.6
> Java and Scala spark examples are mixed
> ---
>
> Key: IGNITE-8523
> URL: https://issues.apache.org/jira/browse/IGNITE-8523
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Sergey Kozlov
>Priority: Blocker
> Fix For: 2.6
>
> Attachments: Снимок экрана от 2018-05-17 22-24-52.png
>
>
> Now {{ignite-example}} project has two locations to store spark examples:
> {{examples/src/main/scala/org/apache/ignite/scalar/examples/spark}} - single
> spark example on Scala
> {{examples/src/main/spark/org/apache/ignite/examples/spark}} - mix of java
> and scala examples
> Moreover the profile {{scala}} activates spark folder but that folder has
> Java examples as well. Thus I can't run java spark examples without {{scala}}
> profile.
> The current implementation is weird and should be fixed by following way:
> 1. Make two locations where collect java and scala examples separately:
> {{examples/src/main/java/org/apache/ignite/examples/spark}} for java examples
> {{examples/src/main/scala/org/apache/ignite/scalar/examples/spark}} for scala
> examples
> 2. Remove spark folder for {{scala}} profile
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8022) Need to add README.txt for ignite-direct-io
[ https://issues.apache.org/jira/browse/IGNITE-8022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-8022: Fix Version/s: (was: 2.5) 2.6 > Need to add README.txt for ignite-direct-io > --- > > Key: IGNITE-8022 > URL: https://issues.apache.org/jira/browse/IGNITE-8022 > Project: Ignite > Issue Type: Bug > Components: persistence >Affects Versions: 2.4 >Reporter: Ksenia Rybakova >Assignee: Dmitriy Pavlov >Priority: Major > Fix For: 2.6 > > > Need to add README.txt for ignite-direct-io -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8528) Peer deployment does not work for continuous query transformers
[
https://issues.apache.org/jira/browse/IGNITE-8528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16480911#comment-16480911
]
Andrey Gura commented on IGNITE-8528:
-
Merged to master and ignite-2.5 branches.
> Peer deployment does not work for continuous query transformers
> ---
>
> Key: IGNITE-8528
> URL: https://issues.apache.org/jira/browse/IGNITE-8528
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.5
>Reporter: Alexey Goncharuk
>Assignee: Nikolay Izhikov
>Priority: Major
> Fix For: 2.5
>
>
> Build local Ignite distribution using
> {code}
> mvn clean install -Pall-java,all-scala,licenses -DskipTests
> mvn initialize -Prelease
> {code}
> Start one node in console and run continuous query with transformer example
> in IDE. I am getting the following exception:
> {code}
> [15:30:43] To start Console Management & Monitoring run
> ignitevisorcmd.{sh|bat}
> [15:30:43]
> [15:30:43] Ignite node started OK (id=f1356a5b)
> [15:30:43] Topology snapshot [ver=1, servers=1, clients=0, CPUs=16,
> offheap=19.0GB, heap=2.0GB]
> [15:30:43] ^-- Node [id=F1356A5B-4CDB-4480-A64F-35BF2C96DBB5,
> clusterState=ACTIVE]
> [15:30:43] Data Regions Configured:
> [15:30:43] ^-- default [initSize=256.0 MiB, maxSize=18.9 GiB,
> persistenceEnabled=false]
> [15:30:52] Topology snapshot [ver=2, servers=2, clients=0, CPUs=16,
> offheap=38.0GB, heap=3.0GB]
> [15:30:52] ^-- Node [id=F1356A5B-4CDB-4480-A64F-35BF2C96DBB5,
> clusterState=ACTIVE]
> [15:30:52] Data Regions Configured:
> [15:30:52] ^-- default [initSize=256.0 MiB, maxSize=18.9 GiB,
> persistenceEnabled=false]
> [15:30:53,065][SEVERE][tcp-disco-msg-worker-#2][BinaryContext] Failed to
> deserialize object [typeName=java.lang.invoke.SerializedLambda]
> class org.apache.ignite.binary.BinaryObjectException: Failed to read field
> [name=capturingClass]
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor.read(BinaryFieldAccessor.java:187)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:870)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1762)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1714)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readField(BinaryReaderExImpl.java:1982)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read0(BinaryFieldAccessor.java:698)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor.read(BinaryFieldAccessor.java:183)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:870)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1762)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1714)
> at
> org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:310)
> at
> org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal0(BinaryMarshaller.java:99)
> at
> org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:82)
> at
> org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:9962)
> at
> org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:9991)
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryDeployableObject.unmarshal(CacheContinuousQueryDeployableObject.java:94)
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandlerV3.p2pUnmarshal(CacheContinuousQueryHandlerV3.java:155)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processStartRequest(GridContinuousProcessor.java:1327)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$400(GridContinuousProcessor.java:108)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:200)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:191)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:707)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery(GridDiscoveryManager.java:589)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.notifyDiscoveryListener(ServerImpl.java:5479)
> at
>
[jira] [Updated] (IGNITE-8528) Peer deployment does not work for continuous query transformers
[
https://issues.apache.org/jira/browse/IGNITE-8528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura updated IGNITE-8528:
Fix Version/s: (was: 2.6)
2.5
> Peer deployment does not work for continuous query transformers
> ---
>
> Key: IGNITE-8528
> URL: https://issues.apache.org/jira/browse/IGNITE-8528
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.5
>Reporter: Alexey Goncharuk
>Assignee: Nikolay Izhikov
>Priority: Major
> Fix For: 2.5
>
>
> Build local Ignite distribution using
> {code}
> mvn clean install -Pall-java,all-scala,licenses -DskipTests
> mvn initialize -Prelease
> {code}
> Start one node in console and run continuous query with transformer example
> in IDE. I am getting the following exception:
> {code}
> [15:30:43] To start Console Management & Monitoring run
> ignitevisorcmd.{sh|bat}
> [15:30:43]
> [15:30:43] Ignite node started OK (id=f1356a5b)
> [15:30:43] Topology snapshot [ver=1, servers=1, clients=0, CPUs=16,
> offheap=19.0GB, heap=2.0GB]
> [15:30:43] ^-- Node [id=F1356A5B-4CDB-4480-A64F-35BF2C96DBB5,
> clusterState=ACTIVE]
> [15:30:43] Data Regions Configured:
> [15:30:43] ^-- default [initSize=256.0 MiB, maxSize=18.9 GiB,
> persistenceEnabled=false]
> [15:30:52] Topology snapshot [ver=2, servers=2, clients=0, CPUs=16,
> offheap=38.0GB, heap=3.0GB]
> [15:30:52] ^-- Node [id=F1356A5B-4CDB-4480-A64F-35BF2C96DBB5,
> clusterState=ACTIVE]
> [15:30:52] Data Regions Configured:
> [15:30:52] ^-- default [initSize=256.0 MiB, maxSize=18.9 GiB,
> persistenceEnabled=false]
> [15:30:53,065][SEVERE][tcp-disco-msg-worker-#2][BinaryContext] Failed to
> deserialize object [typeName=java.lang.invoke.SerializedLambda]
> class org.apache.ignite.binary.BinaryObjectException: Failed to read field
> [name=capturingClass]
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor.read(BinaryFieldAccessor.java:187)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:870)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1762)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1714)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readField(BinaryReaderExImpl.java:1982)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read0(BinaryFieldAccessor.java:698)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor.read(BinaryFieldAccessor.java:183)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:870)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1762)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1714)
> at
> org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:310)
> at
> org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal0(BinaryMarshaller.java:99)
> at
> org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:82)
> at
> org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:9962)
> at
> org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:9991)
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryDeployableObject.unmarshal(CacheContinuousQueryDeployableObject.java:94)
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandlerV3.p2pUnmarshal(CacheContinuousQueryHandlerV3.java:155)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processStartRequest(GridContinuousProcessor.java:1327)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$400(GridContinuousProcessor.java:108)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:200)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:191)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:707)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery(GridDiscoveryManager.java:589)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.notifyDiscoveryListener(ServerImpl.java:5479)
> at
>
[jira] [Commented] (IGNITE-8520) ignite-gce/ignite-shmem is redundant
[
https://issues.apache.org/jira/browse/IGNITE-8520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16480641#comment-16480641
]
Andrey Gura commented on IGNITE-8520:
-
Merged to master and ignite-2.5 branches. Thanks!
> ignite-gce/ignite-shmem is redundant
>
>
> Key: IGNITE-8520
> URL: https://issues.apache.org/jira/browse/IGNITE-8520
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Sergey Kozlov
>Assignee: Peter Ivanov
>Priority: Major
> Fix For: 2.5
>
>
> {{ignite-shmem}} is already included in {{libs}} and thus should be excluded
> from {{libs/optional/ignite-gce}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8510) RPM package 2.4.0 is incorrectly upgraded by 2.5.0
[
https://issues.apache.org/jira/browse/IGNITE-8510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16478854#comment-16478854
]
Andrey Gura commented on IGNITE-8510:
-
Merged to master and ignite-2.5 branches. Thanks!
> RPM package 2.4.0 is incorrectly upgraded by 2.5.0
> --
>
> Key: IGNITE-8510
> URL: https://issues.apache.org/jira/browse/IGNITE-8510
> Project: Ignite
> Issue Type: Bug
>Reporter: Peter Ivanov
>Assignee: Peter Ivanov
>Priority: Blocker
> Fix For: 2.5
>
>
> Due to incorrect path to {{_sharedstatedir}} variable, RPM package 2.4.0 was
> built with {{/usr/com/apache-ignite}} as main work directory (instead of
> {{/var/lib/apache-ignite}}) and during upgrade procedure, postinstall script
> of 2.5.0 does not update permissions for correct directory.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8478) SqlLine run failure on Java 9
[
https://issues.apache.org/jira/browse/IGNITE-8478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura updated IGNITE-8478:
Fix Version/s: 2.5
> SqlLine run failure on Java 9
> -
>
> Key: IGNITE-8478
> URL: https://issues.apache.org/jira/browse/IGNITE-8478
> Project: Ignite
> Issue Type: Bug
>Reporter: Peter Ivanov
>Assignee: Peter Ivanov
>Priority: Critical
> Fix For: 2.5
>
>
> {code}
> *The version of JAVA installed in C:\Program Files\Java\jdk-9.0.1 is
> incorrect.*
> *Please point JAVA_HOME variable to installation of JDK 1.7 or JDK 1.8.**You
> can also download latest JDK at http://java.com/download
> .*
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-8472) Apache ignite for .NET has security vulnerabilities
[ https://issues.apache.org/jira/browse/IGNITE-8472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura resolved IGNITE-8472. - Resolution: Duplicate Fix Version/s: (was: 2.6) > Apache ignite for .NET has security vulnerabilities > --- > > Key: IGNITE-8472 > URL: https://issues.apache.org/jira/browse/IGNITE-8472 > Project: Ignite > Issue Type: Bug > Components: security >Affects Versions: 2.4 >Reporter: Harendra Rai >Priority: Critical > > There are two vulnerabilities in the latest 2.3.0 version. > # commons-beanutils-1.8.3.jar. Here is the vulnerability id CVE-2014-0114 : > [https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0114] > *Resolution to this issue is*: Upgrade Commons BeanUtils to the latest > version >= commons-beanutils-1.9.2 > # commons-codec-1.6.jar: Here is the vulnerability detail > https://issues.apache.org/jira/browse/CODEC-96 > *Resolution to this issue is:* To upgrade to the latest available Version 1.11 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8471) Apache ignite for .NET has security vulnerabilities
[ https://issues.apache.org/jira/browse/IGNITE-8471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-8471: Fix Version/s: (was: 2.6) 2.5 > Apache ignite for .NET has security vulnerabilities > --- > > Key: IGNITE-8471 > URL: https://issues.apache.org/jira/browse/IGNITE-8471 > Project: Ignite > Issue Type: Bug > Components: security >Affects Versions: 2.4 >Reporter: Harendra Rai >Assignee: Andrey Gura >Priority: Major > Fix For: 2.5 > > > There are two security vulnerabilities in the latest 2.4.0 version. > # commons-beanutils-1.8.3.jar. Here is the vulnerability id CVE-2014-0114 : > [https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0114] > *Resolution to this issue is*: All Commons BeanUtils users should upgrade to > the latest version >= commons-beanutils-1.9.2 > # commons-codec-1.6.jar: Here is the vulnerability detail > https://issues.apache.org/jira/browse/CODEC-96 > *Resolution* *to this issue is:* To upgrade to the latest available Version > 1.11 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-8471) Apache ignite for .NET has security vulnerabilities
[ https://issues.apache.org/jira/browse/IGNITE-8471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura reassigned IGNITE-8471: --- Assignee: Andrey Gura > Apache ignite for .NET has security vulnerabilities > --- > > Key: IGNITE-8471 > URL: https://issues.apache.org/jira/browse/IGNITE-8471 > Project: Ignite > Issue Type: Bug > Components: security >Affects Versions: 2.4 >Reporter: Harendra Rai >Assignee: Andrey Gura >Priority: Major > Fix For: 2.5 > > > There are two security vulnerabilities in the latest 2.4.0 version. > # commons-beanutils-1.8.3.jar. Here is the vulnerability id CVE-2014-0114 : > [https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0114] > *Resolution to this issue is*: All Commons BeanUtils users should upgrade to > the latest version >= commons-beanutils-1.9.2 > # commons-codec-1.6.jar: Here is the vulnerability detail > https://issues.apache.org/jira/browse/CODEC-96 > *Resolution* *to this issue is:* To upgrade to the latest available Version > 1.11 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8055) Sqline command !tables works incorrect for client node
[ https://issues.apache.org/jira/browse/IGNITE-8055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-8055: Fix Version/s: (was: 2.5) 2.6 > Sqline command !tables works incorrect for client node > -- > > Key: IGNITE-8055 > URL: https://issues.apache.org/jira/browse/IGNITE-8055 > Project: Ignite > Issue Type: Bug > Components: jdbc >Affects Versions: 2.4 >Reporter: Andrey Aleksandrov >Priority: Minor > Fix For: 2.6 > > > For reproducing: > You should start one local server and one local client nodes and follow the > instructions: > 1)Connect to server node: > sqlline.bat --color=true --verbose=true -u jdbc:ignite:thin://127.0.0.1:10800 > 2)Create new table on server node: > CREATE TABLE City (id LONG PRIMARY KEY, name VARCHAR)WITH > "template=replicated"; > 3)Check that table exists from server node: > !tables > On this step table should be shown in the response. > 4)Connect to client node: > sqlline.bat --color=true --verbose=true -u jdbc:ignite:thin://127.0.0.1:10801 > 5)Check that table exists from server node: > !tables > *On this step there is no "city" table in the list.* > Next commands work from client node as well: > SELECT * FROM City > DROP TABLE City > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8219) B+Tree operation may result in an infinite loop in some case
[ https://issues.apache.org/jira/browse/IGNITE-8219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-8219: Fix Version/s: (was: 2.5) 2.6 > B+Tree operation may result in an infinite loop in some case > - > > Key: IGNITE-8219 > URL: https://issues.apache.org/jira/browse/IGNITE-8219 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.4 >Reporter: Alexey Stelmak >Assignee: Alexey Stelmak >Priority: Major > Fix For: 2.6 > > > B+Tree operation may result in an infinite loop in case. Test > DynamicIndexServerCoordinatorBasicSelfTest#testCreateIndexWithInlineSizePartitionedAtomic > region size = 512Mb, KEY_BEFORE=1, KEY_AFTER=2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8298) Broken UI of the latest table cell
[ https://issues.apache.org/jira/browse/IGNITE-8298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-8298: Fix Version/s: (was: 2.5) 2.6 > Broken UI of the latest table cell > -- > > Key: IGNITE-8298 > URL: https://issues.apache.org/jira/browse/IGNITE-8298 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Dmitriy Shabalin >Assignee: Dmitriy Shabalin >Priority: Major > Fix For: 2.6 > > > Check the latest cell in a table. It's UI looks broken. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8060) Sqline creating tables on client nodes works incorrect in case of node's shutdown
[ https://issues.apache.org/jira/browse/IGNITE-8060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-8060: Fix Version/s: (was: 2.5) 2.6 > Sqline creating tables on client nodes works incorrect in case of node's > shutdown > - > > Key: IGNITE-8060 > URL: https://issues.apache.org/jira/browse/IGNITE-8060 > Project: Ignite > Issue Type: Bug > Components: jdbc >Affects Versions: 2.4 >Reporter: Andrey Aleksandrov >Priority: Major > Fix For: 2.6 > > Attachments: ignite-76cc6387.log, ignite-a1c90af9.log > > > For reproducing (master branch) > You should start one local server and one local client nodes and follow the > instructions: > 1)Connect to client node: > sqlline.bat --color=true --verbose=true -u jdbc:ignite:thin://127.0.0.1:10801 > 2)Create new table on client node: > CREATE TABLE City (id LONG PRIMARY KEY, name VARCHAR)WITH > "template=replicated"; > 3)Check that table exists from server node: > !tables > On this step table should be shown in the response. > 4)Drop the client node > 5)Create new client node > 6)Connect to new client node: > sqlline.bat --color=true --verbose=true -u jdbc:ignite:thin://127.0.0.1:10801 > 7)Check that table exists from server node: > !tables > *On this step there is no "city" table in the list.* > 8)Try to drop the table: > DROP TABLE City; > java.sql.SQLException: Table doesn't exist: CITY > at > org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:671) > at > org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:130) > at > org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:299) > at sqlline.Commands.execute(Commands.java:823) > at sqlline.Commands.sql(Commands.java:733) > at sqlline.SqlLine.dispatch(SqlLine.java:795) > at sqlline.SqlLine.begin(SqlLine.java:668) > at sqlline.SqlLine.start(SqlLine.java:373) > at sqlline.SqlLine.main(SqlLine.java:265) > 9)Try to create new table: > CREATE TABLE City (id LONG PRIMARY KEY, name VARCHAR)WITH > "template=replicated"; > java.sql.SQLException: Table already exists: CITY > at > org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:671) > at > org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:130) > at > org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:299) > at sqlline.Commands.execute(Commands.java:823) > at sqlline.Commands.sql(Commands.java:733) > at sqlline.SqlLine.dispatch(SqlLine.java:795) > at sqlline.SqlLine.begin(SqlLine.java:668) > at sqlline.SqlLine.start(SqlLine.java:373) > at sqlline.SqlLine.main(SqlLine.java:265) > Update: > Exceptions on CREATE/REMOVE are thrown only until first SELECT isn't done. > !tables doen\t work even after SELECT > SELECT works OK. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8220) Discovery worker termination in PDS test
[
https://issues.apache.org/jira/browse/IGNITE-8220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura updated IGNITE-8220:
Fix Version/s: (was: 2.5)
2.6
> Discovery worker termination in PDS test
>
>
> Key: IGNITE-8220
> URL: https://issues.apache.org/jira/browse/IGNITE-8220
> Project: Ignite
> Issue Type: Test
> Components: persistence
>Reporter: Dmitriy Pavlov
>Assignee: Alexey Goncharuk
>Priority: Critical
> Labels: MakeTeamcityGreenAgain, Muted_test
> Fix For: 2.6
>
>
> 3 suites failed
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_IgnitePds1_IgniteTests24Java8=%3Cdefault%3E=buildTypeStatusDiv
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_PdsDirectIo1_IgniteTests24Java8=%3Cdefault%3E=buildTypeStatusDiv
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_ActivateDeactivateCluster_IgniteTests24Java8=%3Cdefault%3E=buildTypeStatusDiv
> Example of tests failed:
> - IgniteClusterActivateDeactivateTestWithPersistence.testActivateFailover3
> - IgniteClusterActivateDeactivateTestWithPersistence.testDeactivateFailover3
> {noformat}
> [2018-04-11
> 02:43:09,769][ERROR][tcp-disco-srvr-#2298%cache.IgniteClusterActivateDeactivateTestWithPersistence0%][IgniteTestResources]
> Critical failure. Will be handled accordingly to configured handler
> [hnd=class o.a.i.failure.NoOpFailureHandler, failureCtx=FailureContext
> [type=SYSTEM_WORKER_TERMINATION, err=java.lang.IllegalStateException: Thread
> tcp-disco-srvr-#2298%cache.IgniteClusterActivateDeactivateTestWithPersistence0%
> is terminated unexpectedly.]]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8472) Apache ignite for .NET has security vulnerabilities
[ https://issues.apache.org/jira/browse/IGNITE-8472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-8472: Fix Version/s: (was: 2.5) 2.6 > Apache ignite for .NET has security vulnerabilities > --- > > Key: IGNITE-8472 > URL: https://issues.apache.org/jira/browse/IGNITE-8472 > Project: Ignite > Issue Type: Bug > Components: security >Affects Versions: 2.4 >Reporter: Harendra Rai >Priority: Critical > Fix For: 2.6 > > > There are two vulnerabilities in the latest 2.3.0 version. > # commons-beanutils-1.8.3.jar. Here is the vulnerability id CVE-2014-0114 : > [https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0114] > *Resolution to this issue is*: Upgrade Commons BeanUtils to the latest > version >= commons-beanutils-1.9.2 > # commons-codec-1.6.jar: Here is the vulnerability detail > https://issues.apache.org/jira/browse/CODEC-96 > *Resolution to this issue is:* To upgrade to the latest available Version 1.11 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8471) Apache ignite for .NET has security vulnerabilities
[ https://issues.apache.org/jira/browse/IGNITE-8471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-8471: Fix Version/s: (was: 2.5) 2.6 > Apache ignite for .NET has security vulnerabilities > --- > > Key: IGNITE-8471 > URL: https://issues.apache.org/jira/browse/IGNITE-8471 > Project: Ignite > Issue Type: Bug > Components: security >Affects Versions: 2.4 >Reporter: Harendra Rai >Priority: Major > Fix For: 2.6 > > > There are two security vulnerabilities in the latest 2.4.0 version. > # commons-beanutils-1.8.3.jar. Here is the vulnerability id CVE-2014-0114 : > [https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0114] > *Resolution to this issue is*: All Commons BeanUtils users should upgrade to > the latest version >= commons-beanutils-1.9.2 > # commons-codec-1.6.jar: Here is the vulnerability detail > https://issues.apache.org/jira/browse/CODEC-96 > *Resolution* *to this issue is:* To upgrade to the latest available Version > 1.11 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7896) Files of evicted partitions are not removed from disk storage
[ https://issues.apache.org/jira/browse/IGNITE-7896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16470751#comment-16470751 ] Andrey Gura commented on IGNITE-7896: - LGTM. Merged to master branch. Thanks for contribution! > Files of evicted partitions are not removed from disk storage > - > > Key: IGNITE-7896 > URL: https://issues.apache.org/jira/browse/IGNITE-7896 > Project: Ignite > Issue Type: Bug >Reporter: Vladislav Pyatkov >Assignee: Ivan Daschinskiy >Priority: Major > Fix For: 2.6 > > Attachments: IgnitePdsRebalanceCompletionAndPartitionFilesTest.java > > > Look at test reproduction: > [^IgnitePdsRebalanceCompletionAndPartitionFilesTest.java] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8441) Java 9 (Stage II)
[ https://issues.apache.org/jira/browse/IGNITE-8441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-8441: Priority: Critical (was: Blocker) > Java 9 (Stage II) > - > > Key: IGNITE-8441 > URL: https://issues.apache.org/jira/browse/IGNITE-8441 > Project: Ignite > Issue Type: Improvement >Reporter: Peter Ivanov >Assignee: Peter Ivanov >Priority: Critical > Fix For: 2.6 > > > Enhance [Ignite Tests 2.4+ (Java > 8)|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=projectOverview] > project with ability to run build and tests under JDK9. Fix all incoming > problems so that full Run All test runs on same branches provide similar > results (excluding flaky tests). > Some known problems: > * some current versions of used maven plugins and 3rd party dependencies are > still not ready for Java 9 > * some JVM options of current test build configurations require revision > * scala -- both 2.10 and 2.11 currently used in building and testing do not > support Java 9 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8441) Java 9 (Stage II)
[ https://issues.apache.org/jira/browse/IGNITE-8441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-8441: Fix Version/s: (was: 2.5) 2.6 > Java 9 (Stage II) > - > > Key: IGNITE-8441 > URL: https://issues.apache.org/jira/browse/IGNITE-8441 > Project: Ignite > Issue Type: Improvement >Reporter: Peter Ivanov >Assignee: Peter Ivanov >Priority: Blocker > Fix For: 2.6 > > > Enhance [Ignite Tests 2.4+ (Java > 8)|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=projectOverview] > project with ability to run build and tests under JDK9. Fix all incoming > problems so that full Run All test runs on same branches provide similar > results (excluding flaky tests). > Some known problems: > * some current versions of used maven plugins and 3rd party dependencies are > still not ready for Java 9 > * some JVM options of current test build configurations require revision > * scala -- both 2.10 and 2.11 currently used in building and testing do not > support Java 9 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8461) Scala-2.10 modules compilation failure under JDK 9
[
https://issues.apache.org/jira/browse/IGNITE-8461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura updated IGNITE-8461:
Fix Version/s: (was: 2.5)
2.6
> Scala-2.10 modules compilation failure under JDK 9
> --
>
> Key: IGNITE-8461
> URL: https://issues.apache.org/jira/browse/IGNITE-8461
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.4
>Reporter: Peter Ivanov
>Priority: Critical
> Fix For: 2.6
>
>
> {code}
> [ERROR] error: java.lang.NoClassDefFoundError: javax/tools/ToolProvider
> [INFO]at
> scala.reflect.io.JavaToolsPlatformArchive.iterator(ZipArchive.scala:242)
> [INFO]at
> scala.collection.IterableLike$class.foreach(IterableLike.scala:72)
> [INFO]at scala.reflect.io.AbstractFile.foreach(AbstractFile.scala:92)
> [INFO]at
> scala.tools.nsc.util.DirectoryClassPath.traverse(ClassPath.scala:308)
> [INFO]at
> scala.tools.nsc.util.DirectoryClassPath.x$16$lzycompute(ClassPath.scala:317)
> [INFO]at
> scala.tools.nsc.util.DirectoryClassPath.x$16(ClassPath.scala:317)
> [INFO]at
> scala.tools.nsc.util.DirectoryClassPath.packages$lzycompute(ClassPath.scala:317)
> [INFO]at
> scala.tools.nsc.util.DirectoryClassPath.packages(ClassPath.scala:317)
> [INFO]at
> scala.tools.nsc.util.DirectoryClassPath.packages(ClassPath.scala:297)
> [INFO]at
> scala.tools.nsc.util.MergedClassPath$$anonfun$packages$1.apply(ClassPath.scala:375)
> [INFO]at
> scala.tools.nsc.util.MergedClassPath$$anonfun$packages$1.apply(ClassPath.scala:375)
> [INFO]at scala.collection.Iterator$class.foreach(Iterator.scala:727)
> [INFO]at
> scala.collection.AbstractIterator.foreach(Iterator.scala:1157)
> [INFO]at
> scala.collection.IterableLike$class.foreach(IterableLike.scala:72)
> [INFO]at scala.collection.AbstractIterable.foreach(Iterable.scala:54)
> [INFO]at
> scala.tools.nsc.util.MergedClassPath.packages$lzycompute(ClassPath.scala:375)
> [INFO]at
> scala.tools.nsc.util.MergedClassPath.packages(ClassPath.scala:370)
> [INFO]at
> scala.tools.nsc.symtab.SymbolLoaders$PackageLoader.doComplete(SymbolLoaders.scala:243)
> [INFO]at
> scala.tools.nsc.symtab.SymbolLoaders$SymbolLoader.complete(SymbolLoaders.scala:194)
> [INFO]at
> scala.reflect.internal.Symbols$Symbol.info(Symbols.scala:1231)
> [INFO]at
> scala.reflect.internal.Mirrors$RootsBase.init(Mirrors.scala:240)
> [INFO]at scala.tools.nsc.Global.rootMirror$lzycompute(Global.scala:59)
> [INFO]at scala.tools.nsc.Global.rootMirror(Global.scala:57)
> [INFO]at scala.tools.nsc.Global.rootMirror(Global.scala:37)
> [INFO]at
> scala.reflect.internal.Definitions$DefinitionsClass.(Definitions.scala:166)
> [INFO]at
> scala.reflect.internal.Definitions$definitions$.(Definitions.scala:20)
> [INFO]at
> scala.reflect.internal.SymbolTable.definitions$lzycompute(SymbolTable.scala:13)
> [INFO]at
> scala.reflect.internal.SymbolTable.definitions(SymbolTable.scala:13)
> [INFO]at scala.tools.nsc.Global$Run.(Global.scala:1290)
> [INFO]at scala.tools.nsc.Driver.doCompile(Driver.scala:32)
> [INFO]at scala.tools.nsc.Main$.doCompile(Main.scala:79)
> [INFO]at scala.tools.nsc.Driver.process(Driver.scala:54)
> [INFO]at scala.tools.nsc.Driver.main(Driver.scala:67)
> [INFO]at scala.tools.nsc.Main.main(Main.scala)
> [INFO]at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [INFO]at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [INFO]at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [INFO]at java.base/java.lang.reflect.Method.invoke(Method.java:564)
> [INFO]at
> scala_maven_executions.MainHelper.runMain(MainHelper.java:164)
> [INFO]at
> scala_maven_executions.MainWithArgsInFile.main(MainWithArgsInFile.java:26)
> [INFO]
> [INFO] java.lang.reflect.InvocationTargetException
> [INFO]at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [INFO]at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [INFO]at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [INFO]at java.base/java.lang.reflect.Method.invoke(Method.java:564)
> [INFO]at
> scala_maven_executions.MainHelper.runMain(MainHelper.java:164)
> [INFO]at
> scala_maven_executions.MainWithArgsInFile.main(MainWithArgsInFile.java:26)
> [ERROR] Caused by:
[jira] [Updated] (IGNITE-8461) Scala-2.10 modules compilation failure under JDK 9
[
https://issues.apache.org/jira/browse/IGNITE-8461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura updated IGNITE-8461:
Priority: Critical (was: Blocker)
> Scala-2.10 modules compilation failure under JDK 9
> --
>
> Key: IGNITE-8461
> URL: https://issues.apache.org/jira/browse/IGNITE-8461
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.4
>Reporter: Peter Ivanov
>Priority: Critical
> Fix For: 2.6
>
>
> {code}
> [ERROR] error: java.lang.NoClassDefFoundError: javax/tools/ToolProvider
> [INFO]at
> scala.reflect.io.JavaToolsPlatformArchive.iterator(ZipArchive.scala:242)
> [INFO]at
> scala.collection.IterableLike$class.foreach(IterableLike.scala:72)
> [INFO]at scala.reflect.io.AbstractFile.foreach(AbstractFile.scala:92)
> [INFO]at
> scala.tools.nsc.util.DirectoryClassPath.traverse(ClassPath.scala:308)
> [INFO]at
> scala.tools.nsc.util.DirectoryClassPath.x$16$lzycompute(ClassPath.scala:317)
> [INFO]at
> scala.tools.nsc.util.DirectoryClassPath.x$16(ClassPath.scala:317)
> [INFO]at
> scala.tools.nsc.util.DirectoryClassPath.packages$lzycompute(ClassPath.scala:317)
> [INFO]at
> scala.tools.nsc.util.DirectoryClassPath.packages(ClassPath.scala:317)
> [INFO]at
> scala.tools.nsc.util.DirectoryClassPath.packages(ClassPath.scala:297)
> [INFO]at
> scala.tools.nsc.util.MergedClassPath$$anonfun$packages$1.apply(ClassPath.scala:375)
> [INFO]at
> scala.tools.nsc.util.MergedClassPath$$anonfun$packages$1.apply(ClassPath.scala:375)
> [INFO]at scala.collection.Iterator$class.foreach(Iterator.scala:727)
> [INFO]at
> scala.collection.AbstractIterator.foreach(Iterator.scala:1157)
> [INFO]at
> scala.collection.IterableLike$class.foreach(IterableLike.scala:72)
> [INFO]at scala.collection.AbstractIterable.foreach(Iterable.scala:54)
> [INFO]at
> scala.tools.nsc.util.MergedClassPath.packages$lzycompute(ClassPath.scala:375)
> [INFO]at
> scala.tools.nsc.util.MergedClassPath.packages(ClassPath.scala:370)
> [INFO]at
> scala.tools.nsc.symtab.SymbolLoaders$PackageLoader.doComplete(SymbolLoaders.scala:243)
> [INFO]at
> scala.tools.nsc.symtab.SymbolLoaders$SymbolLoader.complete(SymbolLoaders.scala:194)
> [INFO]at
> scala.reflect.internal.Symbols$Symbol.info(Symbols.scala:1231)
> [INFO]at
> scala.reflect.internal.Mirrors$RootsBase.init(Mirrors.scala:240)
> [INFO]at scala.tools.nsc.Global.rootMirror$lzycompute(Global.scala:59)
> [INFO]at scala.tools.nsc.Global.rootMirror(Global.scala:57)
> [INFO]at scala.tools.nsc.Global.rootMirror(Global.scala:37)
> [INFO]at
> scala.reflect.internal.Definitions$DefinitionsClass.(Definitions.scala:166)
> [INFO]at
> scala.reflect.internal.Definitions$definitions$.(Definitions.scala:20)
> [INFO]at
> scala.reflect.internal.SymbolTable.definitions$lzycompute(SymbolTable.scala:13)
> [INFO]at
> scala.reflect.internal.SymbolTable.definitions(SymbolTable.scala:13)
> [INFO]at scala.tools.nsc.Global$Run.(Global.scala:1290)
> [INFO]at scala.tools.nsc.Driver.doCompile(Driver.scala:32)
> [INFO]at scala.tools.nsc.Main$.doCompile(Main.scala:79)
> [INFO]at scala.tools.nsc.Driver.process(Driver.scala:54)
> [INFO]at scala.tools.nsc.Driver.main(Driver.scala:67)
> [INFO]at scala.tools.nsc.Main.main(Main.scala)
> [INFO]at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [INFO]at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [INFO]at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [INFO]at java.base/java.lang.reflect.Method.invoke(Method.java:564)
> [INFO]at
> scala_maven_executions.MainHelper.runMain(MainHelper.java:164)
> [INFO]at
> scala_maven_executions.MainWithArgsInFile.main(MainWithArgsInFile.java:26)
> [INFO]
> [INFO] java.lang.reflect.InvocationTargetException
> [INFO]at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [INFO]at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [INFO]at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [INFO]at java.base/java.lang.reflect.Method.invoke(Method.java:564)
> [INFO]at
> scala_maven_executions.MainHelper.runMain(MainHelper.java:164)
> [INFO]at
> scala_maven_executions.MainWithArgsInFile.main(MainWithArgsInFile.java:26)
> [ERROR] Caused by: java.lang.NoClassDefFoundError:
[jira] [Updated] (IGNITE-7896) Files of evicted partitions are not removed from disk storage
[ https://issues.apache.org/jira/browse/IGNITE-7896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-7896: Fix Version/s: 2.6 > Files of evicted partitions are not removed from disk storage > - > > Key: IGNITE-7896 > URL: https://issues.apache.org/jira/browse/IGNITE-7896 > Project: Ignite > Issue Type: Bug >Reporter: Vladislav Pyatkov >Assignee: Ivan Daschinskiy >Priority: Major > Fix For: 2.6 > > Attachments: IgnitePdsRebalanceCompletionAndPartitionFilesTest.java > > > Look at test reproduction: > [^IgnitePdsRebalanceCompletionAndPartitionFilesTest.java] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8424) Sort directories in readCacheConfigurations() to ensure consistent caches start
[
https://issues.apache.org/jira/browse/IGNITE-8424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura updated IGNITE-8424:
Fix Version/s: 2.6
> Sort directories in readCacheConfigurations() to ensure consistent caches
> start
> ---
>
> Key: IGNITE-8424
> URL: https://issues.apache.org/jira/browse/IGNITE-8424
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Assignee: Ivan Daschinskiy
>Priority: Critical
> Fix For: 2.6
>
>
> {{listFiles()}} may return different folders order on different nodes. We
> should sort directories just to be sure that this code is robust for cases
> when caches with the same names got into different cache groups.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8439) IGNITE_JETTY_HOST doesn't work (never has probably)
[ https://issues.apache.org/jira/browse/IGNITE-8439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16467465#comment-16467465 ] Andrey Gura commented on IGNITE-8439: - [~roman_s] I replied on dev-list about this fix. It will work but would be better to refactor class. So I didn't include it to 2.5 release. > IGNITE_JETTY_HOST doesn't work (never has probably) > --- > > Key: IGNITE-8439 > URL: https://issues.apache.org/jira/browse/IGNITE-8439 > Project: Ignite > Issue Type: Bug > Components: rest >Affects Versions: 2.4 >Reporter: Paul Anderson >Assignee: Roman Shtykh >Priority: Major > > GridJettyRestProtocol.java > > public void start(GridRestProtocolHandler hnd) > ... > System.setProperty(IGNITE_JETTY_HOST, locHost.getHostAddress()) > ... > should be > if(System.getProperty(IGNITE_JETTY_HOST)==null) > System.setProperty(IGNITE_JETTY_HOST, locHost.getHostAddress()); -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8435) Inconsistent data after StopNodeFailureHandler handles process termination
[
https://issues.apache.org/jira/browse/IGNITE-8435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16467454#comment-16467454
]
Andrey Gura commented on IGNITE-8435:
-
LGTM. Merged to master and ignite-2.5 branches. Thanks for contribution!
> Inconsistent data after StopNodeFailureHandler handles process termination
> --
>
> Key: IGNITE-8435
> URL: https://issues.apache.org/jira/browse/IGNITE-8435
> Project: Ignite
> Issue Type: Bug
>Reporter: Anton Kalashnikov
>Assignee: Anton Kalashnikov
>Priority: Major
> Fix For: 2.5
>
>
> Steps to reproduce:
> 1. Cluster started with StopNodeFailureHandler in config.
> 2. Upload data to the caches and run accounts task (transfer the amount from
> one account to another for some cache).
> 3. Terminate one thread (ttl-cleanup-worker for example for one node).
> 4. Wait until accounts task finished the work.
> 5. Check the sum for caches.
> Expected result:
> The sum is the same as before thread rermination.
> Actual result:
> The sum is not the same for some caches.
> Also, I see these exception in the logs for node with terminated thread:
> {code:java}
> [13:08:37,709][SEVERE][sys-stripe-1-#2][GridNearTxLocal] Commit failed.
> class
> org.apache.ignite.internal.transactions.IgniteTxHeuristicCheckedException:
> Commit produced a runtime exception (all transaction entries will be
> invalidated):
> GridDhtTxRemote[xid=8e4906dd261--0815-47fa--0004,
> xidVersion=GridCacheVersion [topVer=135612410, order=1524132517096, nod
> eOrder=4], concurrency=OPTIMISTIC, isolation=REPEATABLE_READ,
> state=COMMITTING, invalidate=false, rollbackOnly=false,
> nodeId=6f5954fa-e283-4506-9344-7a8914774681, timeout=4990, duration=41]
> at
> org.apache.ignite.internal.processors.cache.distributed.GridDistributedTxRemoteAdapter.commitIfLocked(GridDistributedTxRemoteAdapter.java:742)
> at
> org.apache.ignite.internal.processors.cache.distributed.GridDistributedTxRemoteAdapter.commitRemoteTx(GridDistributedTxRemoteAdapter.java:815)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finish(IgniteTxHandler.java:1316)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processDhtTxFinishRequest(IgniteTxHandler.java:1228)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.access$600(IgniteTxHandler.java:97)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$7.apply(IgniteTxHandler.java:213)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$7.apply(IgniteTxHandler.java:211)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1054)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:579)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:378)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:304)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:99)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:293)
> 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.communication.GridIoManager.access$4200(GridIoManager.java:125)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1091)
> at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.run(StripedExecutor.java:511)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.IgniteCheckedException: Runtime failure on
> search row:
> org.apache.ignite.internal.processors.cache.tree.SearchRow@1aa35c0b
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invoke(BPlusTree.java:1668)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:1263)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.invoke(GridCacheOffheapManager.java:1782)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.invoke(IgniteCacheOffheapManagerImpl.java:359)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.storeValue(GridCacheMapEntry.java:3604)
> at
>
[jira] [Assigned] (IGNITE-8452) ML module compilation failure under Java 9
[
https://issues.apache.org/jira/browse/IGNITE-8452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura reassigned IGNITE-8452:
---
Assignee: Yury Babak
> ML module compilation failure under Java 9
> --
>
> Key: IGNITE-8452
> URL: https://issues.apache.org/jira/browse/IGNITE-8452
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.4
>Reporter: Peter Ivanov
>Assignee: Yury Babak
>Priority: Blocker
> Fix For: 2.5
>
>
> Running Apache Ignite build on master branch (commit: ) fails with following
> error:
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.7.0:testCompile
> (default-testCompile) on project ignite-ml: Compilation failure: Compilation
> failure:
> [ERROR]
> /Users/vveider/Development/VCS/Git/ignite/modules/ml/src/test/java/org/apache/ignite/ml/dataset/primitive/DatasetWrapperTest.java:[62,45]
> incompatible types: java.lang.Object cannot be converted to java.lang.Integer
> [ERROR]
> /Users/vveider/Development/VCS/Git/ignite/modules/ml/src/test/java/org/apache/ignite/ml/dataset/primitive/DatasetWrapperTest.java:[74,38]
> incompatible types: java.lang.Object cannot be converted to java.lang.Integer
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8452) ML module compilation failure under Java 9
[
https://issues.apache.org/jira/browse/IGNITE-8452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura updated IGNITE-8452:
Priority: Blocker (was: Critical)
> ML module compilation failure under Java 9
> --
>
> Key: IGNITE-8452
> URL: https://issues.apache.org/jira/browse/IGNITE-8452
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.4
>Reporter: Peter Ivanov
>Priority: Blocker
> Fix For: 2.5
>
>
> Running Apache Ignite build on master branch (commit: ) fails with following
> error:
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.7.0:testCompile
> (default-testCompile) on project ignite-ml: Compilation failure: Compilation
> failure:
> [ERROR]
> /Users/vveider/Development/VCS/Git/ignite/modules/ml/src/test/java/org/apache/ignite/ml/dataset/primitive/DatasetWrapperTest.java:[62,45]
> incompatible types: java.lang.Object cannot be converted to java.lang.Integer
> [ERROR]
> /Users/vveider/Development/VCS/Git/ignite/modules/ml/src/test/java/org/apache/ignite/ml/dataset/primitive/DatasetWrapperTest.java:[74,38]
> incompatible types: java.lang.Object cannot be converted to java.lang.Integer
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8443) Flaky failure of IgniteCacheClientNodeChangingTopologyTest.testPessimisticTxPutAllMultinode
[
https://issues.apache.org/jira/browse/IGNITE-8443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura updated IGNITE-8443:
Fix Version/s: 2.6
> Flaky failure of
> IgniteCacheClientNodeChangingTopologyTest.testPessimisticTxPutAllMultinode
> ---
>
> Key: IGNITE-8443
> URL: https://issues.apache.org/jira/browse/IGNITE-8443
> Project: Ignite
> Issue Type: Bug
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.6
>
>
> Test fails on TC sometimes (failure rate: 30%) with the following error:
> {noformat}
> junit.framework.AssertionFailedError: Failed to wait for update.
> at
> org.apache.ignite.internal.processors.cache.distributed.IgniteCacheClientNodeChangingTopologyTest.multinode(IgniteCacheClientNodeChangingTopologyTest.java:1855)
> at
> org.apache.ignite.internal.processors.cache.distributed.IgniteCacheClientNodeChangingTopologyTest.testPessimisticTxPutAllMultinode(IgniteCacheClientNodeChangingTopologyTest.java:1673)
> {noformat}
> Each time some seconds prior to failure there is error in log:
> {noformat}
> [ERROR][sys-stripe-10-#90529%distributed.IgniteCacheClientNodeChangingTopologyTest0%][GridDhtColocatedCache]
> Failed to unmarshal at least one of the keys for lock request
> message: GridNearLockRequest [topVer=AffinityTopologyVersion [topVer=10,
> minorTopVer=0], miniId=1, dhtVers=[...],
> subjId=5ad87047-5d80-4530-bb48-f7c26846, taskNameHash=0, createTtl=-1,
> accessTtl=-1, flags=6, filter=null, super=GridDistributedLockRequest
> [nodeId=5ad87047-5d80-4530-bb48-f7c26846, nearXidVer=GridCacheVersion
> [topVer=136730132, order=1525250131532, nodeOrder=7], threadId=100107,
> futId=3e2912f2361-94bff164-8062-4fb4-8d85-c2e89e579148, timeout=0,
> isInTx=true, isInvalidate=false, isRead=false, isolation=REPEATABLE_READ,
> retVals=[...], txSize=0, flags=0, keysCnt=94,
> super=GridDistributedBaseMessage [ver=GridCacheVersion [topVer=136730132,
> order=1525250131532, nodeOrder=7], committedVers=null, rolledbackVers=null,
> cnt=0, super=GridCacheIdMessage [cacheId=1544803905
> class
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtInvalidPartitionException
> [part=54, msg=Adding entry to partition that is concurrently evicted
> [grp=default, part=54, shouldBeMoving=, belongs=true,
> topVer=AffinityTopologyVersion [topVer=10, minorTopVer=0],
> curTopVer=AffinityTopologyVersion [topVer=10, minorTopVer=1]]]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.localPartition0(GridDhtPartitionTopologyImpl.java:923)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.localPartition(GridDhtPartitionTopologyImpl.java:798)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridCachePartitionedConcurrentMap.localPartition(GridCachePartitionedConcurrentMap.java:69)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridCachePartitionedConcurrentMap.putEntryIfObsoleteOrAbsent(GridCachePartitionedConcurrentMap.java:88)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.entryEx(GridCacheAdapter.java:955)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter.entryEx(GridDhtCacheAdapter.java:525)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter.entryExx(GridDhtCacheAdapter.java:545)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.lockAllAsync(GridDhtTransactionalCacheAdapter.java:987)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.processNearLockRequest0(GridDhtTransactionalCacheAdapter.java:667)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.access$800(GridDhtTransactionalCacheAdapter.java:94)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$12$1.run(GridDhtTransactionalCacheAdapter.java:704)
> at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.run(StripedExecutor.java:511)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8434) .NET: Service proxies do not work on .NET Core
[
https://issues.apache.org/jira/browse/IGNITE-8434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura updated IGNITE-8434:
Fix Version/s: 2.5
> .NET: Service proxies do not work on .NET Core
> --
>
> Key: IGNITE-8434
> URL: https://issues.apache.org/jira/browse/IGNITE-8434
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET
> Fix For: 2.5
>
>
> Service proxies do not work on .NET Core because of conditional compilation
> in {{ServiceProxyTypeGenerator}}.
> We only compile for a single target, so {{NETCOREAPP2_0}} branch is never
> used.
> Except in tests, so they pass.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-8440) Transaction may hangs on node in PREPARED state
[
https://issues.apache.org/jira/browse/IGNITE-8440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16466023#comment-16466023
]
Andrey Gura edited comment on IGNITE-8440 at 5/7/18 3:23 PM:
-
[~v.pyatkov] Do you have any logs that contains information about described
situation? Also it would be great to have reproducer.
Information just isn't enough.
was (Author: agura):
[~v.pyatkov] Do you have any logs that contains information about described
situation? Also it would be great to have reproducer.
> Transaction may hangs on node in PREPARED state
> ---
>
> Key: IGNITE-8440
> URL: https://issues.apache.org/jira/browse/IGNITE-8440
> Project: Ignite
> Issue Type: Bug
>Reporter: Vladislav Pyatkov
>Priority: Major
>
> In some specific cases we can to see when transaction hangs on one node in
> {{PREPARED}} state, but does not hang in others.
> That unhappy node waiting to get {{TxFinishRequest}}, but never got it and
> continue to print _long running transaction message_.
> Should to check other nodes, when transaction hang on PREPARED state without
> progress.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8440) Transaction may hangs on node in PREPARED state
[
https://issues.apache.org/jira/browse/IGNITE-8440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16466023#comment-16466023
]
Andrey Gura commented on IGNITE-8440:
-
[~v.pyatkov] Do you have any logs that contains information about described
situation? Also it would be great to have reproducer.
> Transaction may hangs on node in PREPARED state
> ---
>
> Key: IGNITE-8440
> URL: https://issues.apache.org/jira/browse/IGNITE-8440
> Project: Ignite
> Issue Type: Bug
>Reporter: Vladislav Pyatkov
>Priority: Major
>
> In some specific cases we can to see when transaction hangs on one node in
> {{PREPARED}} state, but does not hang in others.
> That unhappy node waiting to get {{TxFinishRequest}}, but never got it and
> continue to print _long running transaction message_.
> Should to check other nodes, when transaction hang on PREPARED state without
> progress.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8435) Inconsistent data after StopNodeFailureHandler handles process termination
[
https://issues.apache.org/jira/browse/IGNITE-8435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura updated IGNITE-8435:
Fix Version/s: 2.5
> Inconsistent data after StopNodeFailureHandler handles process termination
> --
>
> Key: IGNITE-8435
> URL: https://issues.apache.org/jira/browse/IGNITE-8435
> Project: Ignite
> Issue Type: Bug
>Reporter: Anton Kalashnikov
>Assignee: Anton Kalashnikov
>Priority: Major
> Fix For: 2.5
>
>
> Steps to reproduce:
> 1. Cluster started with StopNodeFailureHandler in config.
> 2. Upload data to the caches and run accounts task (transfer the amount from
> one account to another for some cache).
> 3. Terminate one thread (ttl-cleanup-worker for example for one node).
> 4. Wait until accounts task finished the work.
> 5. Check the sum for caches.
> Expected result:
> The sum is the same as before thread rermination.
> Actual result:
> The sum is not the same for some caches.
> Also, I see these exception in the logs for node with terminated thread:
> {code:java}
> [13:08:37,709][SEVERE][sys-stripe-1-#2][GridNearTxLocal] Commit failed.
> class
> org.apache.ignite.internal.transactions.IgniteTxHeuristicCheckedException:
> Commit produced a runtime exception (all transaction entries will be
> invalidated):
> GridDhtTxRemote[xid=8e4906dd261--0815-47fa--0004,
> xidVersion=GridCacheVersion [topVer=135612410, order=1524132517096, nod
> eOrder=4], concurrency=OPTIMISTIC, isolation=REPEATABLE_READ,
> state=COMMITTING, invalidate=false, rollbackOnly=false,
> nodeId=6f5954fa-e283-4506-9344-7a8914774681, timeout=4990, duration=41]
> at
> org.apache.ignite.internal.processors.cache.distributed.GridDistributedTxRemoteAdapter.commitIfLocked(GridDistributedTxRemoteAdapter.java:742)
> at
> org.apache.ignite.internal.processors.cache.distributed.GridDistributedTxRemoteAdapter.commitRemoteTx(GridDistributedTxRemoteAdapter.java:815)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finish(IgniteTxHandler.java:1316)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processDhtTxFinishRequest(IgniteTxHandler.java:1228)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.access$600(IgniteTxHandler.java:97)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$7.apply(IgniteTxHandler.java:213)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$7.apply(IgniteTxHandler.java:211)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1054)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:579)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:378)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:304)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:99)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:293)
> 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.communication.GridIoManager.access$4200(GridIoManager.java:125)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1091)
> at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.run(StripedExecutor.java:511)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.IgniteCheckedException: Runtime failure on
> search row:
> org.apache.ignite.internal.processors.cache.tree.SearchRow@1aa35c0b
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invoke(BPlusTree.java:1668)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:1263)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.invoke(GridCacheOffheapManager.java:1782)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.invoke(IgniteCacheOffheapManagerImpl.java:359)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.storeValue(GridCacheMapEntry.java:3604)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.storeValue(GridCacheMapEntry.java:3580)
> at
>
[jira] [Commented] (IGNITE-8421) ZkDistributedCollectDataFuture fails to delete future data in case of concurrent deletion
[ https://issues.apache.org/jira/browse/IGNITE-8421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16465993#comment-16465993 ] Andrey Gura commented on IGNITE-8421: - Merged to ignite-2.5 branch. > ZkDistributedCollectDataFuture fails to delete future data in case of > concurrent deletion > - > > Key: IGNITE-8421 > URL: https://issues.apache.org/jira/browse/IGNITE-8421 > Project: Ignite > Issue Type: Bug > Components: zookeeper >Affects Versions: 2.5 >Reporter: Sergey Chugunov >Assignee: Sergey Chugunov >Priority: Critical > Fix For: 2.5 > > > In *ZkDistributedCollectDataFuture#deleteFutureData* method > KeeperException.NoNodeException may be thrown but the exception isn't > critical in this context and doesn't require special handling (just logging > is enough). > However *deleteFutureData* relies on *ZookeeperClient#getChildren* which > reacts on any exception (including NoNodeException) by killing current Ignite > node. > Another implementation of *ZookeeperClient#getChildren* is needed which > tolerates NoNodeException. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8347) Memory leaks on restart Ignite node with enabled persistence at ThreadLocal
[
https://issues.apache.org/jira/browse/IGNITE-8347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16465988#comment-16465988
]
Andrey Gura commented on IGNITE-8347:
-
Merged to ignite-2.5 branch.
> Memory leaks on restart Ignite node with enabled persistence at ThreadLocal
> ---
>
> Key: IGNITE-8347
> URL: https://issues.apache.org/jira/browse/IGNITE-8347
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Affects Versions: 2.4
>Reporter: Taras Ledkov
>Assignee: Dmitriy Pavlov
>Priority: Critical
> Fix For: 2.5
>
>
> Memory leaks on restart Ignite node with enabled persistence at ThreadLocal.
> The ThreadLocal {{DelayedPageReplacementTracker#delayedPageWriteThreadLoc}}
> looks suspicious.
> I've added the simple test to memory leak on restart Ignite nodes from the
> thread that is not terminated after node stopped.
> This case is very useful e.g. for all jUnit cache tests that starts Ignite
> cluster from the {{beforeTestsStarted()}} (this method is called from the
> {{main}} thread and alive for all tests in a test suite).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8347) Memory leaks on restart Ignite node with enabled persistence at ThreadLocal
[
https://issues.apache.org/jira/browse/IGNITE-8347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura updated IGNITE-8347:
Fix Version/s: (was: 2.6)
2.5
> Memory leaks on restart Ignite node with enabled persistence at ThreadLocal
> ---
>
> Key: IGNITE-8347
> URL: https://issues.apache.org/jira/browse/IGNITE-8347
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Affects Versions: 2.4
>Reporter: Taras Ledkov
>Assignee: Dmitriy Pavlov
>Priority: Critical
> Fix For: 2.5
>
>
> Memory leaks on restart Ignite node with enabled persistence at ThreadLocal.
> The ThreadLocal {{DelayedPageReplacementTracker#delayedPageWriteThreadLoc}}
> looks suspicious.
> I've added the simple test to memory leak on restart Ignite nodes from the
> thread that is not terminated after node stopped.
> This case is very useful e.g. for all jUnit cache tests that starts Ignite
> cluster from the {{beforeTestsStarted()}} (this method is called from the
> {{main}} thread and alive for all tests in a test suite).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8421) ZkDistributedCollectDataFuture fails to delete future data in case of concurrent deletion
[ https://issues.apache.org/jira/browse/IGNITE-8421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-8421: Fix Version/s: (was: 2.6) 2.5 > ZkDistributedCollectDataFuture fails to delete future data in case of > concurrent deletion > - > > Key: IGNITE-8421 > URL: https://issues.apache.org/jira/browse/IGNITE-8421 > Project: Ignite > Issue Type: Bug > Components: zookeeper >Affects Versions: 2.5 >Reporter: Sergey Chugunov >Assignee: Sergey Chugunov >Priority: Critical > Fix For: 2.5 > > > In *ZkDistributedCollectDataFuture#deleteFutureData* method > KeeperException.NoNodeException may be thrown but the exception isn't > critical in this context and doesn't require special handling (just logging > is enough). > However *deleteFutureData* relies on *ZookeeperClient#getChildren* which > reacts on any exception (including NoNodeException) by killing current Ignite > node. > Another implementation of *ZookeeperClient#getChildren* is needed which > tolerates NoNodeException. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8322) Yardstick benchmark preloading option
[ https://issues.apache.org/jira/browse/IGNITE-8322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-8322: Fix Version/s: 2.6 > Yardstick benchmark preloading option > - > > Key: IGNITE-8322 > URL: https://issues.apache.org/jira/browse/IGNITE-8322 > Project: Ignite > Issue Type: Improvement >Reporter: Oleg Ostanin >Assignee: Oleg Ostanin >Priority: Major > Fix For: 2.6 > > > Yardstick has no benchmarks with eviction on the disk (PDS). For that puspose > we need following: > 1. Make new configuration and put every cache into a separate date region: > atomic,tx,atomic-index,query,compute > 2. Add a new preload option for a benchmark: preload up to a size passed from > that option. There two options: > * total size of preload data (bytes) > * the size of data in memory against total size (percent) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8400) Flaky failure of IgniteTopologyValidatorGridSplitCacheTest.testTopologyValidatorWithCacheGroup (Grid is in invalid state)
[
https://issues.apache.org/jira/browse/IGNITE-8400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16465871#comment-16465871
]
Andrey Gura commented on IGNITE-8400:
-
LGTM! Merged to master branch. Thanks!
> Flaky failure of
> IgniteTopologyValidatorGridSplitCacheTest.testTopologyValidatorWithCacheGroup
> (Grid is in invalid state)
> -
>
> Key: IGNITE-8400
> URL: https://issues.apache.org/jira/browse/IGNITE-8400
> Project: Ignite
> Issue Type: Bug
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.6
>
>
> Test fails sometimes on TeamCity with exception:
> {noformat}
> java.lang.IllegalStateException: Grid is in invalid state to perform this
> operation. It either not started yet or has already being or have stopped
> [igniteInstanceName=cache.IgniteTopologyValidatorGridSplitCacheTest6,
> state=STOPPED]
> {noformat}
> Before this exception node is dropped out of topology by coordinator:
> {noformat}
> [tcp-disco-msg-worker-#7831%cache.IgniteTopologyValidatorGridSplitCacheTest6%][IgniteCacheTopologySplitAbstractTest$SplitTcpDiscoverySpi]
> Node is out of topology (probably, due to short-time network problems).
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-8293) BinaryUtils#isCustomJavaSerialization fails when only readObject is declared in a class
[
https://issues.apache.org/jira/browse/IGNITE-8293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16462533#comment-16462533
]
Andrey Gura edited comment on IGNITE-8293 at 5/3/18 2:38 PM:
-
[~MihkelJ] "all" plan is good candidate because marshalling bug can affect any
subsystem of Ignite. Unfortunately, we constantly have failed tests on TC so we
usually compare failed tests on PR with tests on master (default) branch. I'll
check your TC run later and let you know if new tests are failed. Also feel
free to compare your run vs master run.
was (Author: agura):
[~MihkelJ] "all" plan is good candidate because marshalling bug can affect any
subsystem of Ignite. Unfortunately, we constantly have failed tests on TC so we
usually compare failed tests on PR with tests on master (default) branch. I'll
check your TC run later and let you know if new tests are failed.
> BinaryUtils#isCustomJavaSerialization fails when only readObject is declared
> in a class
> ---
>
> Key: IGNITE-8293
> URL: https://issues.apache.org/jira/browse/IGNITE-8293
> Project: Ignite
> Issue Type: Bug
> Components: binary
>Affects Versions: 2.4
>Reporter: MihkelJ
>Assignee: MihkelJ
>Priority: Minor
> Fix For: 2.6
>
> Attachments: IGNITE-8293.patch
>
>
> Consider this class:
>
> {code:java}
> public class Test implements Serializable {
> private transient AtomicBoolean dirty = new AtomicBoolean(false);
> private void readObject(java.io.ObjectInputStream in) throws IOException,
> ClassNotFoundException {
> dirty = new AtomicBoolean(false);
> }
> //methods to check and mark class as dirty
> }{code}
> {{isCustomJavaSerialization}} will get a {{NoSuchMethodException}} when
> trying to grab the {{writeObject}} method and falsely conclude that Test
> doesn't use custom serialization.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
