[jira] [Commented] (IGNITE-9283) [ML] Add Discrete Cosine preprocessor

[ https://issues.apache.org/jira/browse/IGNITE-9283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16896482#comment-16896482 ] Ilya Lantukh commented on IGNITE-9283: -- [~zaleslaw] Please review

[jira] [Commented] (IGNITE-9283) [ML] Add Discrete Cosine preprocessor

[ https://issues.apache.org/jira/browse/IGNITE-9283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16887941#comment-16887941 ] Ilya Lantukh commented on IGNITE-9283: -- [~zaleslaw] , I will prepare a PR in a few days. > [ML]

[jira] [Commented] (IGNITE-8828) Detecting and stopping unresponsive nodes during Partition Map Exchange

[ https://issues.apache.org/jira/browse/IGNITE-8828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16805255#comment-16805255 ] Ilya Lantukh commented on IGNITE-8828: -- Hi [~agoncharuk] , Thanks for the review! I don't think I

[jira] [Assigned] (IGNITE-8828) Detecting and stopping unresponsive nodes during Partition Map Exchange

[ https://issues.apache.org/jira/browse/IGNITE-8828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Lantukh reassigned IGNITE-8828: Assignee: (was: Ilya Lantukh) > Detecting and stopping unresponsive nodes during

[jira] [Commented] (IGNITE-9913) Prevent data updates blocking in case of backup BLT server node leave

[ https://issues.apache.org/jira/browse/IGNITE-9913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16803972#comment-16803972 ] Ilya Lantukh commented on IGNITE-9913: -- Hi [~NSAmelchev],   Thanks for the contribution! I've

[jira] [Assigned] (IGNITE-8877) PartitionsExchangeOnDiscoveryHistoryOverflowTest.testDynamicCacheCreation leads to OutOfMemoryError

[ https://issues.apache.org/jira/browse/IGNITE-8877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Lantukh reassigned IGNITE-8877: Assignee: (was: Ilya Lantukh) >

[jira] [Assigned] (IGNITE-4003) Slow or faulty client can stall the whole cluster.

[ https://issues.apache.org/jira/browse/IGNITE-4003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Lantukh reassigned IGNITE-4003: Assignee: (was: Ilya Lantukh) > Slow or faulty client can stall the whole cluster. >

[jira] [Commented] (IGNITE-11457) Prewarming of page memory after node restart

[ https://issues.apache.org/jira/browse/IGNITE-11457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16787867#comment-16787867 ] Ilya Lantukh commented on IGNITE-11457: --- [~cyberdemon], Thanks for the contribution! To me it

[jira] [Commented] (IGNITE-9739) Critical exception in transaction processing in case we have nodes out of baseline and non-persisted cache

[ https://issues.apache.org/jira/browse/IGNITE-9739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744028#comment-16744028 ] Ilya Lantukh commented on IGNITE-9739: -- Looks good. > Critical exception in transaction processing

[jira] [Assigned] (IGNITE-10898) Exchange coordinator failover breaks in some cases when node filter is used

[ https://issues.apache.org/jira/browse/IGNITE-10898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Lantukh reassigned IGNITE-10898: - Assignee: Ilya Lantukh > Exchange coordinator failover breaks in some cases when node

[jira] [Commented] (IGNITE-10290) Map.Entry interface for key cache may lead to incorrect hash code calculation

[ https://issues.apache.org/jira/browse/IGNITE-10290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16728404#comment-16728404 ] Ilya Lantukh commented on IGNITE-10290: --- [~DmitriyGovorukhin], thanks for the contribution!

[jira] [Commented] (IGNITE-9149) Get rid of logging remaining supplier nodes rebalance time

[ https://issues.apache.org/jira/browse/IGNITE-9149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16728396#comment-16728396 ] Ilya Lantukh commented on IGNITE-9149: -- Thanks for the contribution! Changes look good. > Get rid

[jira] [Commented] (IGNITE-9303) PageSnapshot can contain wrong pageId tag when not dirty page is recycling

[ https://issues.apache.org/jira/browse/IGNITE-9303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16725845#comment-16725845 ] Ilya Lantukh commented on IGNITE-9303: -- [~agoncharuk], thanks for the review. I've addressed all

[jira] [Comment Edited] (IGNITE-9303) PageSnapshot can contain wrong pageId tag when not dirty page is recycling

[ https://issues.apache.org/jira/browse/IGNITE-9303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16725845#comment-16725845 ] Ilya Lantukh edited comment on IGNITE-9303 at 12/20/18 1:44 PM:

[jira] [Commented] (IGNITE-10058) resetLostPartitions() leaves an additional copy of a partition in the cluster

[ https://issues.apache.org/jira/browse/IGNITE-10058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16724935#comment-16724935 ] Ilya Lantukh commented on IGNITE-10058: --- Hi [~xtern], I think that

[jira] [Assigned] (IGNITE-10589) Multiple server node failure after a client node stopping

[ https://issues.apache.org/jira/browse/IGNITE-10589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Lantukh reassigned IGNITE-10589: - Assignee: Ilya Lantukh > Multiple server node failure after a client node stopping >

[jira] [Commented] (IGNITE-10058) resetLostPartitions() leaves an additional copy of a partition in the cluster

[ https://issues.apache.org/jira/browse/IGNITE-10058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16711600#comment-16711600 ] Ilya Lantukh commented on IGNITE-10058: --- [~xtern], Thanks for your efforts and willingness to

[jira] [Commented] (IGNITE-9303) PageSnapshot can contain wrong pageId tag when not dirty page is recycling

[ https://issues.apache.org/jira/browse/IGNITE-9303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16710108#comment-16710108 ] Ilya Lantukh commented on IGNITE-9303: -- Actually, there was a bug in page recycling mechanism,

[jira] [Commented] (IGNITE-9290) Make remove explicit locks async when node left.

[ https://issues.apache.org/jira/browse/IGNITE-9290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16710008#comment-16710008 ] Ilya Lantukh commented on IGNITE-9290: -- [~amashenkov], why did you remove onLeft() call in

[jira] [Commented] (IGNITE-10437) GridCacheWriteBehindStoreMultithreadedSelfTest.testFlushFromTheSameThreadWithCoalescing is flaky

[ https://issues.apache.org/jira/browse/IGNITE-10437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16709992#comment-16709992 ] Ilya Lantukh commented on IGNITE-10437: --- Thanks, looks good now. >

[jira] [Assigned] (IGNITE-9213) CacheLockReleaseNodeLeaveTest.testLockTopologyChange hangs sometimes, leading to TC timeout

[ https://issues.apache.org/jira/browse/IGNITE-9213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Lantukh reassigned IGNITE-9213: Assignee: (was: Ilya Lantukh) > CacheLockReleaseNodeLeaveTest.testLockTopologyChange

[jira] [Commented] (IGNITE-9303) PageSnapshot can contain wrong pageId tag when not dirty page is recycling

[ https://issues.apache.org/jira/browse/IGNITE-9303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16707262#comment-16707262 ] Ilya Lantukh commented on IGNITE-9303: -- I don't see any problem in PageMemory code, only in

[jira] [Commented] (IGNITE-10437) GridCacheWriteBehindStoreMultithreadedSelfTest.testFlushFromTheSameThreadWithCoalescing is flaky

[ https://issues.apache.org/jira/browse/IGNITE-10437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16707174#comment-16707174 ] Ilya Lantukh commented on IGNITE-10437: --- [~SomeFire], It seems to me that your patch doesn't

[jira] [Assigned] (IGNITE-9303) PageSnapshot can contain wrong pageId tag when not dirty page is recycling

[ https://issues.apache.org/jira/browse/IGNITE-9303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Lantukh reassigned IGNITE-9303: Assignee: Ilya Lantukh > PageSnapshot can contain wrong pageId tag when not dirty page

[jira] [Commented] (IGNITE-10427) GridClusterStateProcessor#changeGlobalState0() should wrap future before sending ChangeGlobalStateMessage

[ https://issues.apache.org/jira/browse/IGNITE-10427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16705013#comment-16705013 ] Ilya Lantukh commented on IGNITE-10427: --- Thanks for the contribution! Looks good. >

[jira] [Commented] (IGNITE-10437) GridCacheWriteBehindStoreMultithreadedSelfTest.testFlushFromTheSameThreadWithCoalescing is flaky

[ https://issues.apache.org/jira/browse/IGNITE-10437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16703180#comment-16703180 ] Ilya Lantukh commented on IGNITE-10437: --- [~SomeFire], Can you please explain what was the reason

[jira] [Commented] (IGNITE-4111) Communication fails to send message if target node did not finish join process

[ https://issues.apache.org/jira/browse/IGNITE-4111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16703178#comment-16703178 ] Ilya Lantukh commented on IGNITE-4111: -- Thanks, looks good now. > Communication fails to send

[jira] [Commented] (IGNITE-10392) Client broken cluster where try to connect. Server nodes drop by handler

[ https://issues.apache.org/jira/browse/IGNITE-10392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697322#comment-16697322 ] Ilya Lantukh commented on IGNITE-10392: --- The aforementioned test failures are known issues. >

[jira] [Created] (IGNITE-10392) Client broken cluster where try to connect. Server nodes drop by handler

Ilya Lantukh created IGNITE-10392: - Summary: Client broken cluster where try to connect. Server nodes drop by handler Key: IGNITE-10392 URL: https://issues.apache.org/jira/browse/IGNITE-10392

[jira] [Assigned] (IGNITE-9283) [ML] Add Discrete Cosine preprocessor

[ https://issues.apache.org/jira/browse/IGNITE-9283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Lantukh reassigned IGNITE-9283: Assignee: Ilya Lantukh > [ML] Add Discrete Cosine preprocessor >

[jira] [Commented] (IGNITE-4111) Communication fails to send message if target node did not finish join process

[ https://issues.apache.org/jira/browse/IGNITE-4111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16695805#comment-16695805 ] Ilya Lantukh commented on IGNITE-4111: -- [~NSAmelchev], thanks for the contribution! I've reviewed

[jira] [Commented] (IGNITE-9558) Avoid changing AffinityTopologyVersion on client connect when possible

[ https://issues.apache.org/jira/browse/IGNITE-9558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16682961#comment-16682961 ] Ilya Lantukh commented on IGNITE-9558: -- [~agoncharuk], thanks for uncovering that issue! I've

[jira] [Assigned] (IGNITE-9840) Possible deadlock on transactional future on client node in case of network problems or long GC pauses

[ https://issues.apache.org/jira/browse/IGNITE-9840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Lantukh reassigned IGNITE-9840: Assignee: Ilya Lantukh (was: Alexey Stelmak) > Possible deadlock on transactional

[jira] [Assigned] (IGNITE-4003) Slow or faulty client can stall the whole cluster.

[ https://issues.apache.org/jira/browse/IGNITE-4003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Lantukh reassigned IGNITE-4003: Assignee: Ilya Lantukh (was: Semen Boikov) > Slow or faulty client can stall the whole

[jira] [Created] (IGNITE-10186) Revise ability to merge client-only exchanges

Ilya Lantukh created IGNITE-10186: - Summary: Revise ability to merge client-only exchanges Key: IGNITE-10186 URL: https://issues.apache.org/jira/browse/IGNITE-10186 Project: Ignite Issue

[jira] [Commented] (IGNITE-9769) IgniteCacheAtomicProtocolTest.testPutReaderUpdate1 is flaky

[ https://issues.apache.org/jira/browse/IGNITE-9769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16668642#comment-16668642 ] Ilya Lantukh commented on IGNITE-9769: -- OK, patch looks good to me. Thanks for the contribution! >

[jira] [Commented] (IGNITE-9769) IgniteCacheAtomicProtocolTest.testPutReaderUpdate1 is flaky

[ https://issues.apache.org/jira/browse/IGNITE-9769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16668625#comment-16668625 ] Ilya Lantukh commented on IGNITE-9769: -- [~SomeFire], Do we still need changes in

[jira] [Resolved] (IGNITE-10046) MVCC: IgniteCachePrimaryNodeFailureRecoveryAbstractTest.testPessimisticPrimaryNodeFailureRollback hangs sometimes.

[ https://issues.apache.org/jira/browse/IGNITE-10046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Lantukh resolved IGNITE-10046. --- Resolution: Invalid > MVCC: >

[jira] [Updated] (IGNITE-10046) MVCC: IgniteCachePrimaryNodeFailureRecoveryAbstractTest.testPessimisticPrimaryNodeFailureRollback hangs sometimes.

[ https://issues.apache.org/jira/browse/IGNITE-10046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Lantukh updated IGNITE-10046: -- Fix Version/s: (was: 2.7) > MVCC: >

[jira] [Updated] (IGNITE-10046) MVCC: IgniteCachePrimaryNodeFailureRecoveryAbstractTest.testPessimisticPrimaryNodeFailureRollback hangs sometimes.

[ https://issues.apache.org/jira/browse/IGNITE-10046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Lantukh updated IGNITE-10046: -- Issue Type: Bug (was: Improvement) > MVCC: >

[jira] [Created] (IGNITE-10046) MVCC: IgniteCachePrimaryNodeFailureRecoveryAbstractTest.testPessimisticPrimaryNodeFailureRollback hangs sometimes.

Ilya Lantukh created IGNITE-10046: - Summary: MVCC: IgniteCachePrimaryNodeFailureRecoveryAbstractTest.testPessimisticPrimaryNodeFailureRollback hangs sometimes. Key: IGNITE-10046 URL:

[jira] [Commented] (IGNITE-9558) Avoid changing AffinityTopologyVersion on client connect when possible

[ https://issues.apache.org/jira/browse/IGNITE-9558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1095#comment-1095 ] Ilya Lantukh commented on IGNITE-9558: -- Done. > Avoid changing AffinityTopologyVersion on client

[jira] [Commented] (IGNITE-9091) IEP-25: creating documentation

[ https://issues.apache.org/jira/browse/IGNITE-9091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665182#comment-16665182 ] Ilya Lantukh commented on IGNITE-9091: -- [~agoncharuk], yes, everything is correct. > IEP-25:

[jira] [Commented] (IGNITE-9753) Control.sh validate index work long and with errors

[ https://issues.apache.org/jira/browse/IGNITE-9753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665155#comment-16665155 ] Ilya Lantukh commented on IGNITE-9753: -- Looks good. > Control.sh validate index work long and with

[jira] [Updated] (IGNITE-9558) Avoid changing AffinityTopologyVersion on client connect when possible

[ https://issues.apache.org/jira/browse/IGNITE-9558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Lantukh updated IGNITE-9558: - Fix Version/s: 2.8 > Avoid changing AffinityTopologyVersion on client connect when possible >

[jira] [Commented] (IGNITE-9769) IgniteCacheAtomicProtocolTest.testPutReaderUpdate1 is flaky

[ https://issues.apache.org/jira/browse/IGNITE-9769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16663626#comment-16663626 ] Ilya Lantukh commented on IGNITE-9769: -- [~SomeFire], The name *equalsPrimaryAffNodes* is

[jira] [Commented] (IGNITE-9673) Timeout in Java Client suite.

[ https://issues.apache.org/jira/browse/IGNITE-9673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16662194#comment-16662194 ] Ilya Lantukh commented on IGNITE-9673: -- [~sergey-chugunov], These changes affect only handlers

[jira] [Commented] (IGNITE-8020) Rebalancing for persistent caches should transfer file store over network instead of using existing supply/demand protocol

[ https://issues.apache.org/jira/browse/IGNITE-8020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16658757#comment-16658757 ] Ilya Lantukh commented on IGNITE-8020: -- Of course, you can! > Rebalancing for persistent caches

[jira] [Assigned] (IGNITE-9905) After transaction load cluster inconsistent

[ https://issues.apache.org/jira/browse/IGNITE-9905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Lantukh reassigned IGNITE-9905: Assignee: Ilya Lantukh > After transaction load cluster inconsistent >

[jira] [Commented] (IGNITE-9769) IgniteCacheAtomicProtocolTest.testPutReaderUpdate1 is flaky

[ https://issues.apache.org/jira/browse/IGNITE-9769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16656725#comment-16656725 ] Ilya Lantukh commented on IGNITE-9769: --

[jira] [Updated] (IGNITE-9917) Write proper tests for start/stop client.

[ https://issues.apache.org/jira/browse/IGNITE-9917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Lantukh updated IGNITE-9917: - Description: Write proper tests for start/stop client. For now we only have "start client"

[jira] [Commented] (IGNITE-9694) Add tests to check that reading queries are not blocked on exchange events that don't change data visibility

[ https://issues.apache.org/jira/browse/IGNITE-9694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16653589#comment-16653589 ] Ilya Lantukh commented on IGNITE-9694: -- [~DmitriyGovorukhin] [~ibessonov], We still don't have

[jira] [Comment Edited] (IGNITE-9694) Add tests to check that reading queries are not blocked on exchange events that don't change data visibility

[ https://issues.apache.org/jira/browse/IGNITE-9694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16653589#comment-16653589 ] Ilya Lantukh edited comment on IGNITE-9694 at 10/17/18 2:00 PM:

[jira] [Comment Edited] (IGNITE-9868) Refactor [GridCachePartitionExchangeManager] Sending Full Message/Full Message creating

[ https://issues.apache.org/jira/browse/IGNITE-9868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16653238#comment-16653238 ] Ilya Lantukh edited comment on IGNITE-9868 at 10/17/18 9:21 AM: Looks

[jira] [Commented] (IGNITE-9868) Refactor [GridCachePartitionExchangeManager] Sending Full Message/Full Message creating

[ https://issues.apache.org/jira/browse/IGNITE-9868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16653238#comment-16653238 ] Ilya Lantukh commented on IGNITE-9868: -- Thanks for the contribution! Looks good. > Refactor

[jira] [Commented] (IGNITE-9794) Registration of a binary type with POJO field under topology lock leads to UnregisteredBinaryTypeException

[ https://issues.apache.org/jira/browse/IGNITE-9794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16639794#comment-16639794 ] Ilya Lantukh commented on IGNITE-9794: -- [~dmekhanikov], Thanks! Looks good. > Registration of a

[jira] [Commented] (IGNITE-9561) Optimize affinity initialization for started cache groups

[ https://issues.apache.org/jira/browse/IGNITE-9561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16633898#comment-16633898 ] Ilya Lantukh commented on IGNITE-9561: -- [~Jokser], thanks for the contribution! I have a few

[jira] [Commented] (IGNITE-8619) Remote node could not start in ssh connection

[ https://issues.apache.org/jira/browse/IGNITE-8619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617419#comment-16617419 ] Ilya Lantukh commented on IGNITE-8619: -- [~ivanan.fed], thanks for detailed explanation, but by "add

[jira] [Commented] (IGNITE-9392) CacheAsyncOperationsFailoverTxTest hangs on TC

[ https://issues.apache.org/jira/browse/IGNITE-9392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16614799#comment-16614799 ] Ilya Lantukh commented on IGNITE-9392: -- Done. > CacheAsyncOperationsFailoverTxTest hangs on TC >

[jira] [Commented] (IGNITE-9249) Tests hang when different threads try to start and stop nodes at the same time.

[ https://issues.apache.org/jira/browse/IGNITE-9249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16613471#comment-16613471 ] Ilya Lantukh commented on IGNITE-9249: -- [~agoncharuk], I've pushed fix for join timeout handling

[jira] [Commented] (IGNITE-9249) Tests hang when different threads try to start and stop nodes at the same time.

[ https://issues.apache.org/jira/browse/IGNITE-9249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16612277#comment-16612277 ] Ilya Lantukh commented on IGNITE-9249: -- https://ci.ignite.apache.org/viewQueued.html?itemId=1850938

[jira] [Commented] (IGNITE-9558) Avoid changing AffinityTopologyVersion on client connect when possible

[ https://issues.apache.org/jira/browse/IGNITE-9558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16612152#comment-16612152 ] Ilya Lantukh commented on IGNITE-9558: -- It looks like special handling for near caches isn't

[jira] [Assigned] (IGNITE-9558) Avoid changing AffinityTopologyVersion on client connect when possible

[ https://issues.apache.org/jira/browse/IGNITE-9558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Lantukh reassigned IGNITE-9558: Assignee: Ilya Lantukh > Avoid changing AffinityTopologyVersion on client connect when

[jira] [Commented] (IGNITE-9249) Tests hang when different threads try to start and stop nodes at the same time.

[ https://issues.apache.org/jira/browse/IGNITE-9249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16610545#comment-16610545 ] Ilya Lantukh commented on IGNITE-9249: -- https://ci.ignite.apache.org/viewQueued.html?itemId=1841812

[jira] [Commented] (IGNITE-8619) Remote node could not start in ssh connection

[ https://issues.apache.org/jira/browse/IGNITE-8619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16609360#comment-16609360 ] Ilya Lantukh commented on IGNITE-8619: -- [~ivanan.fed], I've reviewed your PR from a Java developer

[jira] [Resolved] (IGNITE-8830) Non-coordinator node unable to finish local exchange should detect it and stop

[ https://issues.apache.org/jira/browse/IGNITE-8830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Lantukh resolved IGNITE-8830. -- Resolution: Duplicate > Non-coordinator node unable to finish local exchange should detect it

[jira] [Commented] (IGNITE-8830) Non-coordinator node unable to finish local exchange should detect it and stop

[ https://issues.apache.org/jira/browse/IGNITE-8830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16609262#comment-16609262 ] Ilya Lantukh commented on IGNITE-8830: -- Implemented in the scope of IGNITE-8828. > Non-coordinator

[jira] [Commented] (IGNITE-8832) Detecting hanging of coordinator during processing local partition maps messages

[ https://issues.apache.org/jira/browse/IGNITE-8832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16609254#comment-16609254 ] Ilya Lantukh commented on IGNITE-8832: -- This situation is already covered by IGNITE-6890 and

[jira] [Resolved] (IGNITE-8832) Detecting hanging of coordinator during processing local partition maps messages

[ https://issues.apache.org/jira/browse/IGNITE-8832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Lantukh resolved IGNITE-8832. -- Resolution: Not A Problem > Detecting hanging of coordinator during processing local

[jira] [Commented] (IGNITE-9475) Closures that has been created on client does not provide real class name to TASK_* permissions

[ https://issues.apache.org/jira/browse/IGNITE-9475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16607210#comment-16607210 ] Ilya Lantukh commented on IGNITE-9475: -- Thanks for contribution, changes look good to me. >

[jira] [Comment Edited] (IGNITE-9419) Avoid saving cache configuration synchronously during PME

[ https://issues.apache.org/jira/browse/IGNITE-9419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16605879#comment-16605879 ] Ilya Lantukh edited comment on IGNITE-9419 at 9/6/18 3:48 PM: -- [~Jokser],

[jira] [Issue Comment Deleted] (IGNITE-9084) Trash in WAL after node stop may affect WAL rebalance

[ https://issues.apache.org/jira/browse/IGNITE-9084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Lantukh updated IGNITE-9084: - Comment: was deleted (was: [~Jokser], Thanks for contribution! I've reviewed your PR, you can

[jira] [Commented] (IGNITE-9084) Trash in WAL after node stop may affect WAL rebalance

[ https://issues.apache.org/jira/browse/IGNITE-9084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16605924#comment-16605924 ] Ilya Lantukh commented on IGNITE-9084: -- [~Jokser], Thanks for contribution! I've reviewed your PR,

[jira] [Commented] (IGNITE-9419) Avoid saving cache configuration synchronously during PME

[ https://issues.apache.org/jira/browse/IGNITE-9419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16605879#comment-16605879 ] Ilya Lantukh commented on IGNITE-9419: -- [~Jokser], Thanks for contribution! In my opinion, adding

[jira] [Commented] (IGNITE-9472) REST API has no permission checks for cluster activation/deactivation

[ https://issues.apache.org/jira/browse/IGNITE-9472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16604357#comment-16604357 ] Ilya Lantukh commented on IGNITE-9472: -- [~ibessonov], thanks for contribution! Please add test for

[jira] [Commented] (IGNITE-9068) Node fails to stop when CacheObjectBinaryProcessor.addMeta() is executed inside guard()/unguard()

[ https://issues.apache.org/jira/browse/IGNITE-9068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16602213#comment-16602213 ] Ilya Lantukh commented on IGNITE-9068: -- We need full thread dump from all nodes if such situation

[jira] [Commented] (IGNITE-8286) ScanQuery ignore setLocal with non local partition

[ https://issues.apache.org/jira/browse/IGNITE-8286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16598756#comment-16598756 ] Ilya Lantukh commented on IGNITE-8286: -- [~agoncharuk], I think we can merge it into master and

[jira] [Comment Edited] (IGNITE-9093) IgniteDbPutGetWithCacheStoreTest.testReadThrough fails every time when run on master

[ https://issues.apache.org/jira/browse/IGNITE-9093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16597456#comment-16597456 ] Ilya Lantukh edited comment on IGNITE-9093 at 8/30/18 1:34 PM: --- [~ilyak],

[jira] [Commented] (IGNITE-9093) IgniteDbPutGetWithCacheStoreTest.testReadThrough fails every time when run on master

[ https://issues.apache.org/jira/browse/IGNITE-9093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16597456#comment-16597456 ] Ilya Lantukh commented on IGNITE-9093: -- [~ilyak], This is not a big issue and your fix looks OK. >

[jira] [Commented] (IGNITE-8286) ScanQuery ignore setLocal with non local partition

[ https://issues.apache.org/jira/browse/IGNITE-8286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16597347#comment-16597347 ] Ilya Lantukh commented on IGNITE-8286: -- [~roman_s], thanks! There is still one minor issue - new

[jira] [Commented] (IGNITE-9326) IgniteCacheFailedUpdateResponseTest hangs in master

[ https://issues.apache.org/jira/browse/IGNITE-9326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16596604#comment-16596604 ] Ilya Lantukh commented on IGNITE-9326: -- Looks good. > IgniteCacheFailedUpdateResponseTest hangs in

[jira] [Created] (IGNITE-9400) TC bot: add progress bar to history page

Ilya Lantukh created IGNITE-9400: Summary: TC bot: add progress bar to history page Key: IGNITE-9400 URL: https://issues.apache.org/jira/browse/IGNITE-9400 Project: Ignite Issue Type:

[jira] [Updated] (IGNITE-9392) CacheAsyncOperationsFailoverTxTest hangs on TC

[ https://issues.apache.org/jira/browse/IGNITE-9392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Lantukh updated IGNITE-9392: - Labels: MakeTeamcityGreenAgain (was: ) > CacheAsyncOperationsFailoverTxTest hangs on TC >

[jira] [Updated] (IGNITE-9392) CacheAsyncOperationsFailoverTxTest hangs on TC

[ https://issues.apache.org/jira/browse/IGNITE-9392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Lantukh updated IGNITE-9392: - Ignite Flags: (was: Docs Required) > CacheAsyncOperationsFailoverTxTest hangs on TC >

[jira] [Commented] (IGNITE-9392) CacheAsyncOperationsFailoverTxTest hangs on TC

[ https://issues.apache.org/jira/browse/IGNITE-9392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16594903#comment-16594903 ] Ilya Lantukh commented on IGNITE-9392: -- Looks like setting TX timeout resolves this issue. >

[jira] [Created] (IGNITE-9392) CacheAsyncOperationsFailoverTxTest hangs on TC

Ilya Lantukh created IGNITE-9392: Summary: CacheAsyncOperationsFailoverTxTest hangs on TC Key: IGNITE-9392 URL: https://issues.apache.org/jira/browse/IGNITE-9392 Project: Ignite Issue Type:

[jira] [Commented] (IGNITE-9249) Tests hang when different threads try to start and stop nodes at the same time.

[ https://issues.apache.org/jira/browse/IGNITE-9249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16576286#comment-16576286 ] Ilya Lantukh commented on IGNITE-9249: -- https://ci.ignite.apache.org/viewQueued.html?itemId=1628472

[jira] [Commented] (IGNITE-9249) Tests hang when different threads try to start and stop nodes at the same time.

[ https://issues.apache.org/jira/browse/IGNITE-9249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16576277#comment-16576277 ] Ilya Lantukh commented on IGNITE-9249: -- As a temporary solution I suggest to set join timeout in

[jira] [Created] (IGNITE-9249) Tests hang when different threads try to start and stop nodes at the same time.

Ilya Lantukh created IGNITE-9249: Summary: Tests hang when different threads try to start and stop nodes at the same time. Key: IGNITE-9249 URL: https://issues.apache.org/jira/browse/IGNITE-9249

[jira] [Commented] (IGNITE-8724) Skip logging 3-rd parameter while calling U.warn with initialized logger.

[ https://issues.apache.org/jira/browse/IGNITE-8724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16576224#comment-16576224 ] Ilya Lantukh commented on IGNITE-8724: -- Thanks! Looks good now. > Skip logging 3-rd parameter

[jira] [Commented] (IGNITE-9178) Partition lost event are not triggered if multiple nodes left cluster

[ https://issues.apache.org/jira/browse/IGNITE-9178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16576209#comment-16576209 ] Ilya Lantukh commented on IGNITE-9178: -- [~agoncharuk], I've double-checked this PR, it looks

[jira] [Commented] (IGNITE-8724) Skip logging 3-rd parameter while calling U.warn with initialized logger.

[ https://issues.apache.org/jira/browse/IGNITE-8724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16573354#comment-16573354 ] Ilya Lantukh commented on IGNITE-8724: -- Hi [~zstan], Thanks for contribution! I think that fixing

[jira] [Commented] (IGNITE-9236) Handshake timeout never completes in some tests (GridCacheReplicatedFailoverSelfTest in particular)

[ https://issues.apache.org/jira/browse/IGNITE-9236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16573255#comment-16573255 ] Ilya Lantukh commented on IGNITE-9236: --

[jira] [Created] (IGNITE-9236) Handshake timeout never completes in some tests (GridCacheReplicatedFailoverSelfTest in particular)

Ilya Lantukh created IGNITE-9236: Summary: Handshake timeout never completes in some tests (GridCacheReplicatedFailoverSelfTest in particular) Key: IGNITE-9236 URL:

[jira] [Updated] (IGNITE-9213) CacheLockReleaseNodeLeaveTest.testLockTopologyChange hangs sometimes, leading to TC timeout

[ https://issues.apache.org/jira/browse/IGNITE-9213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Lantukh updated IGNITE-9213: - Attachment: ignite-9213-threaddump.txt > CacheLockReleaseNodeLeaveTest.testLockTopologyChange

[jira] [Created] (IGNITE-9213) CacheLockReleaseNodeLeaveTest.testLockTopologyChange hangs sometimes, leading to TC timeout

Ilya Lantukh created IGNITE-9213: Summary: CacheLockReleaseNodeLeaveTest.testLockTopologyChange hangs sometimes, leading to TC timeout Key: IGNITE-9213 URL: https://issues.apache.org/jira/browse/IGNITE-9213

[jira] [Commented] (IGNITE-9184) Cluster hangs during concurrent node restart and continues query registration

[ https://issues.apache.org/jira/browse/IGNITE-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16571580#comment-16571580 ] Ilya Lantukh commented on IGNITE-9184: -- Discovered the following exception while running this test,

[jira] [Comment Edited] (IGNITE-9184) Cluster hangs during concurrent node restart and continues query registration

[ https://issues.apache.org/jira/browse/IGNITE-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16571513#comment-16571513 ] Ilya Lantukh edited comment on IGNITE-9184 at 8/7/18 12:01 PM: ---

[jira] [Assigned] (IGNITE-9184) Cluster hangs during concurrent node restart and continues query registration

[ https://issues.apache.org/jira/browse/IGNITE-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Lantukh reassigned IGNITE-9184: Assignee: Mikhail Cherkasov (was: Ilya Lantukh) > Cluster hangs during concurrent node

[jira] [Commented] (IGNITE-9184) Cluster hangs during concurrent node restart and continues query registration

[ https://issues.apache.org/jira/browse/IGNITE-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16571513#comment-16571513 ] Ilya Lantukh commented on IGNITE-9184: -- [~mcherkas], I cannot understand the problem from the

  1   2   3   4   5   >