[jira] [Commented] (IGNITE-11384) Introduce an ability of services hot redeployment via DeploymentSpi

[ https://issues.apache.org/jira/browse/IGNITE-11384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16785391#comment-16785391 ] Alexey Goncharuk commented on IGNITE-11384: --- Looks good to me. [~vozerov], do you have any

[jira] [Commented] (IGNITE-11364) Segmenting node can cause ring topology broke

[ https://issues.apache.org/jira/browse/IGNITE-11364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16784505#comment-16784505 ] Alexey Goncharuk commented on IGNITE-11364: --- [~sergey-chugunov], looks good, thanks for

[jira] [Updated] (IGNITE-11468) System caches should not survive client reconnect

[ https://issues.apache.org/jira/browse/IGNITE-11468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-11468: -- Ignite Flags: (was: Docs Required) > System caches should not survive client

[jira] [Assigned] (IGNITE-11468) System caches should not survive client reconnect

[ https://issues.apache.org/jira/browse/IGNITE-11468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk reassigned IGNITE-11468: - Assignee: Alexey Goncharuk > System caches should not survive client

[jira] [Updated] (IGNITE-11468) System caches should not survive client reconnect

[ https://issues.apache.org/jira/browse/IGNITE-11468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-11468: -- Fix Version/s: 2.8 > System caches should not survive client reconnect >

[jira] [Created] (IGNITE-11468) System caches should not survive client reconnect

Alexey Goncharuk created IGNITE-11468: - Summary: System caches should not survive client reconnect Key: IGNITE-11468 URL: https://issues.apache.org/jira/browse/IGNITE-11468 Project: Ignite

[jira] [Commented] (IGNITE-11394) Infinite No next node in topology messages during node restart scenario

[ https://issues.apache.org/jira/browse/IGNITE-11394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16781567#comment-16781567 ] Alexey Goncharuk commented on IGNITE-11394: --- [~sergey-chugunov], this is the first solution I

[jira] [Updated] (IGNITE-11454) Race in ClientImpl may lead to client node segmentation on fast reconnect

[ https://issues.apache.org/jira/browse/IGNITE-11454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-11454: -- Description: We have the following code in {{ClientImpl#tryJoin}}: {code}

[jira] [Commented] (IGNITE-11454) Race in ClientImpl may lead to client node segmentation on fast reconnect

[ https://issues.apache.org/jira/browse/IGNITE-11454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16780624#comment-16780624 ] Alexey Goncharuk commented on IGNITE-11454: --- Suggested solution is to check the join count in

[jira] [Updated] (IGNITE-11454) Race in ClientImpl may lead to client node segmentation on fast reconnect

[ https://issues.apache.org/jira/browse/IGNITE-11454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-11454: -- Ignite Flags: (was: Docs Required) > Race in ClientImpl may lead to client node

[jira] [Assigned] (IGNITE-11454) Race in ClientImpl may lead to client node segmentation on fast reconnect

[ https://issues.apache.org/jira/browse/IGNITE-11454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk reassigned IGNITE-11454: - Assignee: Alexey Goncharuk > Race in ClientImpl may lead to client node

[jira] [Created] (IGNITE-11454) Race in ClientImpl may lead to client node segmentation on fast reconnect

Alexey Goncharuk created IGNITE-11454: - Summary: Race in ClientImpl may lead to client node segmentation on fast reconnect Key: IGNITE-11454 URL: https://issues.apache.org/jira/browse/IGNITE-11454

[jira] [Updated] (IGNITE-11454) Race in ClientImpl may lead to client node segmentation on fast reconnect

[ https://issues.apache.org/jira/browse/IGNITE-11454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-11454: -- Fix Version/s: 2.8 > Race in ClientImpl may lead to client node segmentation on fast

[jira] [Commented] (IGNITE-11394) Infinite No next node in topology messages during node restart scenario

[ https://issues.apache.org/jira/browse/IGNITE-11394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16780331#comment-16780331 ] Alexey Goncharuk commented on IGNITE-11394: --- [~sergey-chugunov], can you please take a look

[jira] [Comment Edited] (IGNITE-11401) [ML] Labmdas doesn't work in binary builds

[ https://issues.apache.org/jira/browse/IGNITE-11401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16780313#comment-16780313 ] Alexey Goncharuk edited comment on IGNITE-11401 at 2/28/19 9:40 AM:

[jira] [Updated] (IGNITE-11432) Add ability to specify auto-generated consistent ID in IgniteConfiguration

[ https://issues.apache.org/jira/browse/IGNITE-11432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-11432: -- Description: Let's consider the following scenario: 1) A user starts an empty node,

[jira] [Created] (IGNITE-11432) Add ability to specify auto-generated consistent ID in IgniteConfiguration

Alexey Goncharuk created IGNITE-11432: - Summary: Add ability to specify auto-generated consistent ID in IgniteConfiguration Key: IGNITE-11432 URL: https://issues.apache.org/jira/browse/IGNITE-11432

[jira] [Commented] (IGNITE-11050) Potential deadlock caused by DhtColocatedLockFuture#map being called inside topology read lock

[ https://issues.apache.org/jira/browse/IGNITE-11050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16777885#comment-16777885 ] Alexey Goncharuk commented on IGNITE-11050: --- Thanks, merged to master. > Potential deadlock

[jira] [Commented] (IGNITE-11059) Print information about pending locks queue in case of dht local tx timeout.

[ https://issues.apache.org/jira/browse/IGNITE-11059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16777860#comment-16777860 ] Alexey Goncharuk commented on IGNITE-11059: --- [~ivandasch] [~ascherbakov] Do we need to print

[jira] [Updated] (IGNITE-11059) Print information about pending locks queue in case of dht local tx timeout.

[ https://issues.apache.org/jira/browse/IGNITE-11059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-11059: -- Ignite Flags: (was: Docs Required) > Print information about pending locks queue

[jira] [Updated] (IGNITE-11171) Assertion on tx preparing

[ https://issues.apache.org/jira/browse/IGNITE-11171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-11171: -- Ignite Flags: (was: Docs Required) > Assertion on tx preparing >

[jira] [Resolved] (IGNITE-11407) AssertionError may occurs on server start

[ https://issues.apache.org/jira/browse/IGNITE-11407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk resolved IGNITE-11407. --- Resolution: Duplicate Fix Version/s: 2.5 > AssertionError may occurs on

[jira] [Commented] (IGNITE-11407) AssertionError may occurs on server start

[ https://issues.apache.org/jira/browse/IGNITE-11407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16777007#comment-16777007 ] Alexey Goncharuk commented on IGNITE-11407: --- [~qvad] this issue is not relevant to current

[jira] [Updated] (IGNITE-11407) AssertionError may occurs on server start

[ https://issues.apache.org/jira/browse/IGNITE-11407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-11407: -- Ignite Flags: (was: Docs Required) > AssertionError may occurs on server start >

[jira] [Commented] (IGNITE-11050) Potential deadlock caused by DhtColocatedLockFuture#map being called inside topology read lock

[ https://issues.apache.org/jira/browse/IGNITE-11050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16776829#comment-16776829 ] Alexey Goncharuk commented on IGNITE-11050: --- [~mstepachev], looks like with this change the

[jira] [Updated] (IGNITE-11394) Infinite No next node in topology messages during node restart scenario

[ https://issues.apache.org/jira/browse/IGNITE-11394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-11394: -- Ignite Flags: (was: Docs Required) > Infinite No next node in topology messages

[jira] [Updated] (IGNITE-11394) Infinite No next node in topology messages during node restart scenario

[ https://issues.apache.org/jira/browse/IGNITE-11394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-11394: -- Fix Version/s: 2.8 > Infinite No next node in topology messages during node restart

[jira] [Assigned] (IGNITE-11394) Infinite No next node in topology messages during node restart scenario

[ https://issues.apache.org/jira/browse/IGNITE-11394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk reassigned IGNITE-11394: - Assignee: Alexey Goncharuk > Infinite No next node in topology messages

[jira] [Updated] (IGNITE-11408) AssertionError may occurs on client start

[ https://issues.apache.org/jira/browse/IGNITE-11408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-11408: -- Ignite Flags: (was: Docs Required) > AssertionError may occurs on client start >

[jira] [Updated] (IGNITE-11394) Infinite No next node in topology messages during node restart scenario

[ https://issues.apache.org/jira/browse/IGNITE-11394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-11394: -- Description: I observe a situation with the following symptoms during a cycled nodes

[jira] [Created] (IGNITE-11394) Infinite No next node in topology messages during node restart scenario

Alexey Goncharuk created IGNITE-11394: - Summary: Infinite No next node in topology messages during node restart scenario Key: IGNITE-11394 URL: https://issues.apache.org/jira/browse/IGNITE-11394

[jira] [Created] (IGNITE-11392) Improve LRT diagnostic messages

Alexey Goncharuk created IGNITE-11392: - Summary: Improve LRT diagnostic messages Key: IGNITE-11392 URL: https://issues.apache.org/jira/browse/IGNITE-11392 Project: Ignite Issue Type:

[jira] [Updated] (IGNITE-11255) Fix test failure after IGNITE-7648.

[ https://issues.apache.org/jira/browse/IGNITE-11255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-11255: -- Fix Version/s: 2.8 > Fix test failure after IGNITE-7648. >

[jira] [Updated] (IGNITE-11058) Possible OOM due to large discard queue in TcpDiscoverySpi

[ https://issues.apache.org/jira/browse/IGNITE-11058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-11058: -- Ignite Flags: (was: Docs Required) > Possible OOM due to large discard queue in

[jira] [Updated] (IGNITE-11352) CacheMetricsSnapshot deserialization may be broken in some cases

[ https://issues.apache.org/jira/browse/IGNITE-11352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-11352: -- Fix Version/s: (was: 2.7) 2.8 > CacheMetricsSnapshot

[jira] [Updated] (IGNITE-11364) Segmenting node can cause ring topology broke

[ https://issues.apache.org/jira/browse/IGNITE-11364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-11364: -- Ignite Flags: (was: Docs Required) > Segmenting node can cause ring topology broke

[jira] [Updated] (IGNITE-11352) CacheMetricsSnapshot deserialization may be broken in some cases

[ https://issues.apache.org/jira/browse/IGNITE-11352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-11352: -- Ignite Flags: (was: Docs Required) > CacheMetricsSnapshot deserialization may be

[jira] [Updated] (IGNITE-10669) NPE in freelist.PagesList.findTailIndex

[ https://issues.apache.org/jira/browse/IGNITE-10669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-10669: -- Component/s: (was: data structures) persistence > NPE in

[jira] [Commented] (IGNITE-11059) Print information about pending locks queue in case of dht local tx timeout.

[ https://issues.apache.org/jira/browse/IGNITE-11059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16772886#comment-16772886 ] Alexey Goncharuk commented on IGNITE-11059: --- [~ascherbakov] We have a limit on the number of

[jira] [Updated] (IGNITE-10669) NPE in freelist.PagesList.findTailIndex

[ https://issues.apache.org/jira/browse/IGNITE-10669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-10669: -- Ignite Flags: (was: Docs Required) > NPE in freelist.PagesList.findTailIndex >

[jira] [Updated] (IGNITE-11243) Not working control.sh / control.bat in master NPE in output

[ https://issues.apache.org/jira/browse/IGNITE-11243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-11243: -- Ignite Flags: (was: Docs Required) > Not working control.sh / control.bat in

[jira] [Updated] (IGNITE-11352) CacheMetricsSnapshot deserialization may be broken in some cases

[ https://issues.apache.org/jira/browse/IGNITE-11352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-11352: -- Description: There is an incompatible changes in CacheMetricsSnapshot serialization

[jira] [Updated] (IGNITE-11352) CacheMetricsSnapshot deserialization may be broken in some cases

[ https://issues.apache.org/jira/browse/IGNITE-11352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-11352: -- Summary: CacheMetricsSnapshot deserialization may be broken in some cases (was:

[jira] [Assigned] (IGNITE-11050) Potential deadlock caused by DhtColocatedLockFuture#map being called inside topology read lock

[ https://issues.apache.org/jira/browse/IGNITE-11050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk reassigned IGNITE-11050: - Assignee: Stepachev Maksim (was: Alexey Goncharuk) > Potential deadlock

[jira] [Commented] (IGNITE-11050) Potential deadlock caused by DhtColocatedLockFuture#map being called inside topology read lock

[ https://issues.apache.org/jira/browse/IGNITE-11050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771742#comment-16771742 ] Alexey Goncharuk commented on IGNITE-11050: --- [~mstepachev], I see a consistent fails of the

[jira] [Updated] (IGNITE-10720) Decrease time to save metadata during checkpoint

[ https://issues.apache.org/jira/browse/IGNITE-10720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-10720: -- Fix Version/s: 2.8 > Decrease time to save metadata during checkpoint >

[jira] [Assigned] (IGNITE-11100) AssertionError LocalJoinCachesContext occurs in sequential cluster restart

[ https://issues.apache.org/jira/browse/IGNITE-11100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk reassigned IGNITE-11100: - Assignee: Alexey Goncharuk > AssertionError LocalJoinCachesContext occurs in

[jira] [Updated] (IGNITE-11100) AssertionError LocalJoinCachesContext occurs in sequential cluster restart

[ https://issues.apache.org/jira/browse/IGNITE-11100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-11100: -- Ignite Flags: (was: Docs Required) > AssertionError LocalJoinCachesContext occurs

[jira] [Resolved] (IGNITE-11100) AssertionError LocalJoinCachesContext occurs in sequential cluster restart

[ https://issues.apache.org/jira/browse/IGNITE-11100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk resolved IGNITE-11100. --- Resolution: Duplicate > AssertionError LocalJoinCachesContext occurs in sequential

[jira] [Created] (IGNITE-11272) Investigate race between local node promotion to the first node in topology and NodeAddedMessage

Alexey Goncharuk created IGNITE-11272: - Summary: Investigate race between local node promotion to the first node in topology and NodeAddedMessage Key: IGNITE-11272 URL:

[jira] [Updated] (IGNITE-11271) Investigate setting discardCustomMsgId to null in prepareNodeAddedMessage

[ https://issues.apache.org/jira/browse/IGNITE-11271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-11271: -- Fix Version/s: 2.8 > Investigate setting discardCustomMsgId to null in

[jira] [Created] (IGNITE-11271) Investigate setting discardCustomMsgId to null in prepareNodeAddedMessage

Alexey Goncharuk created IGNITE-11271: - Summary: Investigate setting discardCustomMsgId to null in prepareNodeAddedMessage Key: IGNITE-11271 URL: https://issues.apache.org/jira/browse/IGNITE-11271

[jira] [Commented] (IGNITE-10920) Optimize HistoryAffinityAssignment heap usage.

[ https://issues.apache.org/jira/browse/IGNITE-10920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16763616#comment-16763616 ] Alexey Goncharuk commented on IGNITE-10920: --- Looks good to me. > Optimize

[jira] [Updated] (IGNITE-11238) Possible hang on exchange

[ https://issues.apache.org/jira/browse/IGNITE-11238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-11238: -- Ignite Flags: (was: Docs Required) > Possible hang on exchange >

[jira] [Updated] (IGNITE-11238) Possible hang on exchange

[ https://issues.apache.org/jira/browse/IGNITE-11238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-11238: -- Fix Version/s: 2.8 > Possible hang on exchange > - > >

[jira] [Commented] (IGNITE-11153) Support Java 11 for control.sh & ignitevisorcmd.sh: remove odd --add-modules for java.xml.bind

[ https://issues.apache.org/jira/browse/IGNITE-11153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16761685#comment-16761685 ] Alexey Goncharuk commented on IGNITE-11153: --- [~dpavlov], I am not an expert in shell scripts,

[jira] [Updated] (IGNITE-11214) IgniteCacheAtomicPutAllFailoverSelfTest fails with "Cannot find cache"

[ https://issues.apache.org/jira/browse/IGNITE-11214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-11214: -- Labels: MakeTeamcityGreenAgain (was: ) > IgniteCacheAtomicPutAllFailoverSelfTest

[jira] [Created] (IGNITE-11214) IgniteCacheAtomicPutAllFailoverSelfTest fails with "Cannot find cache"

Alexey Goncharuk created IGNITE-11214: - Summary: IgniteCacheAtomicPutAllFailoverSelfTest fails with "Cannot find cache" Key: IGNITE-11214 URL: https://issues.apache.org/jira/browse/IGNITE-11214

[jira] [Updated] (IGNITE-11214) IgniteCacheAtomicPutAllFailoverSelfTest fails with "Cannot find cache"

[ https://issues.apache.org/jira/browse/IGNITE-11214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-11214: -- Ignite Flags: (was: Docs Required) > IgniteCacheAtomicPutAllFailoverSelfTest fails

[jira] [Assigned] (IGNITE-11214) IgniteCacheAtomicPutAllFailoverSelfTest fails with "Cannot find cache"

[ https://issues.apache.org/jira/browse/IGNITE-11214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk reassigned IGNITE-11214: - Assignee: Alexey Goncharuk > IgniteCacheAtomicPutAllFailoverSelfTest fails

[jira] [Updated] (IGNITE-10920) Optimize HistoryAffinityAssignment heap usage.

[ https://issues.apache.org/jira/browse/IGNITE-10920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-10920: -- Ignite Flags: (was: Docs Required) > Optimize HistoryAffinityAssignment heap

[jira] [Updated] (IGNITE-10920) Optimize HistoryAffinityAssignment heap usage.

[ https://issues.apache.org/jira/browse/IGNITE-10920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-10920: -- Fix Version/s: 2.8 > Optimize HistoryAffinityAssignment heap usage. >

[jira] [Updated] (IGNITE-10720) Decrease time to save metadata during checkpoint

[ https://issues.apache.org/jira/browse/IGNITE-10720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-10720: -- Ignite Flags: (was: Docs Required) > Decrease time to save metadata during

[jira] [Commented] (IGNITE-11204) Merged partitions exchange future ignores NODE_LEFT/FAILED events for merged exchanges

[ https://issues.apache.org/jira/browse/IGNITE-11204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16760782#comment-16760782 ] Alexey Goncharuk commented on IGNITE-11204: --- After allowing the node failed event to be

[jira] [Updated] (IGNITE-11204) Merged partitions exchange future ignores NODE_LEFT/FAILED events for merged exchanges

[ https://issues.apache.org/jira/browse/IGNITE-11204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-11204: -- Ignite Flags: (was: Docs Required) > Merged partitions exchange future ignores

[jira] [Updated] (IGNITE-11204) Merged partitions exchange future ignores NODE_LEFT/FAILED events for merged exchanges

[ https://issues.apache.org/jira/browse/IGNITE-11204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-11204: -- Fix Version/s: 2.8 > Merged partitions exchange future ignores NODE_LEFT/FAILED

[jira] [Updated] (IGNITE-11204) Merged partitions exchange future ignores NODE_LEFT/FAILED events for merged exchanges

[ https://issues.apache.org/jira/browse/IGNITE-11204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-11204: -- Priority: Critical (was: Major) > Merged partitions exchange future ignores

[jira] [Created] (IGNITE-11204) Merged partitions exchange future ignores NODE_LEFT/FAILED events for merged exchanges

Alexey Goncharuk created IGNITE-11204: - Summary: Merged partitions exchange future ignores NODE_LEFT/FAILED events for merged exchanges Key: IGNITE-11204 URL:

[jira] [Assigned] (IGNITE-11204) Merged partitions exchange future ignores NODE_LEFT/FAILED events for merged exchanges

[ https://issues.apache.org/jira/browse/IGNITE-11204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk reassigned IGNITE-11204: - Assignee: Alexey Goncharuk > Merged partitions exchange future ignores

[jira] [Commented] (IGNITE-5569) TCP Discovery SPI allows multiple NODE_JOINED / NODE_FAILED leading to a cluster DDoS

[ https://issues.apache.org/jira/browse/IGNITE-5569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16760650#comment-16760650 ] Alexey Goncharuk commented on IGNITE-5569: -- I've recently stumbled upon another duplicate

[jira] [Commented] (IGNITE-11195) Platform C++ tests failed to find JVM for Java 11 build

[ https://issues.apache.org/jira/browse/IGNITE-11195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16760102#comment-16760102 ] Alexey Goncharuk commented on IGNITE-11195: --- In the run I can see that {{JAVA_HOME}} is set

[jira] [Updated] (IGNITE-11023) Processing data bag on GridMarshallerMappingProcessor consume many time

[ https://issues.apache.org/jira/browse/IGNITE-11023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-11023: -- Ignite Flags: (was: Docs Required) > Processing data bag on

[jira] [Updated] (IGNITE-11023) Processing data bag on GridMarshallerMappingProcessor consume many time

[ https://issues.apache.org/jira/browse/IGNITE-11023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-11023: -- Fix Version/s: 2.8 > Processing data bag on GridMarshallerMappingProcessor consume

[jira] [Updated] (IGNITE-10876) "Affinity changes (coordinator) applied" can be executed in parallel

[ https://issues.apache.org/jira/browse/IGNITE-10876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-10876: -- Fix Version/s: 2.8 > "Affinity changes (coordinator) applied" can be executed in

[jira] [Updated] (IGNITE-10876) "Affinity changes (coordinator) applied" can be executed in parallel

[ https://issues.apache.org/jira/browse/IGNITE-10876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-10876: -- Ignite Flags: (was: Docs Required) > "Affinity changes (coordinator) applied" can

[jira] [Updated] (IGNITE-10905) org.apache.ignite.internal.processors.cache.distributed.dht.topology.GridDhtInvalidPartitionException happens during rolling restart of a cluster

[ https://issues.apache.org/jira/browse/IGNITE-10905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-10905: -- Ignite Flags: (was: Docs Required) >

[jira] [Updated] (IGNITE-9803) GridDhtInvalidPartitionException in GridDhtPartitionDemander

[ https://issues.apache.org/jira/browse/IGNITE-9803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-9803: - Ignite Flags: (was: Docs Required) > GridDhtInvalidPartitionException in

[jira] [Assigned] (IGNITE-11050) Potential deadlock caused by DhtColocatedLockFuture#map being called inside topology read lock

[ https://issues.apache.org/jira/browse/IGNITE-11050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk reassigned IGNITE-11050: - Assignee: (was: Alexey Goncharuk) > Potential deadlock caused by

[jira] [Commented] (IGNITE-11030) Cache page corruption after a page being rotated having partition ID=0

[ https://issues.apache.org/jira/browse/IGNITE-11030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16757272#comment-16757272 ] Alexey Goncharuk commented on IGNITE-11030: --- [~dpavlov], thanks, changes look good to me. >

[jira] [Commented] (IGNITE-4380) Cache invoke calls can be lost

[ https://issues.apache.org/jira/browse/IGNITE-4380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16757182#comment-16757182 ] Alexey Goncharuk commented on IGNITE-4380: -- [~NSAmelchev], the reason I do not like key lock

[jira] [Commented] (IGNITE-11140) Check and fix Ignite examples for Java 11

[ https://issues.apache.org/jira/browse/IGNITE-11140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16757171#comment-16757171 ] Alexey Goncharuk commented on IGNITE-11140: --- [~dpavlov], changes look good to me! > Check

[jira] [Updated] (IGNITE-10179) Change new tests root to use @BeforeClass and @AfterClass instead of isFirstTest() and isLastTest()

[ https://issues.apache.org/jira/browse/IGNITE-10179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-10179: -- Fix Version/s: 2.8 > Change new tests root to use @BeforeClass and @AfterClass

[jira] [Commented] (IGNITE-10179) Change new tests root to use @BeforeClass and @AfterClass instead of isFirstTest() and isLastTest()

[ https://issues.apache.org/jira/browse/IGNITE-10179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16756538#comment-16756538 ] Alexey Goncharuk commented on IGNITE-10179: --- Thanks, [~oignatenko], merged your changes to

[jira] [Commented] (IGNITE-10926) ZookeeperDiscoverySpi: client does not survive after several cluster restarts

[ https://issues.apache.org/jira/browse/IGNITE-10926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16756243#comment-16756243 ] Alexey Goncharuk commented on IGNITE-10926: --- This is a tricky question. I think the

[jira] [Commented] (IGNITE-10926) ZookeeperDiscoverySpi: client does not survive after several cluster restarts

[ https://issues.apache.org/jira/browse/IGNITE-10926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16756121#comment-16756121 ] Alexey Goncharuk commented on IGNITE-10926: --- [~sergey-chugunov] [~NSAmelchev] So with this

[jira] [Updated] (IGNITE-10758) remove from tests scaffolding annotations "@RunWith(JUnit4.class)" and their respective imports

[ https://issues.apache.org/jira/browse/IGNITE-10758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-10758: -- Fix Version/s: 2.8 > remove from tests scaffolding annotations

[jira] [Commented] (IGNITE-10935) "Invalid node order" error occurs while cycle cluster nodes restart

[ https://issues.apache.org/jira/browse/IGNITE-10935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16755861#comment-16755861 ] Alexey Goncharuk commented on IGNITE-10935: --- Several issues were discovered and fixed in the

[jira] [Updated] (IGNITE-11129) Incorrect size calculation for SWITCH_SEGMENT_RECORD for TDE

[ https://issues.apache.org/jira/browse/IGNITE-11129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-11129: -- Ignite Flags: (was: Docs Required) > Incorrect size calculation for

[jira] [Updated] (IGNITE-10995) GridDhtPartitionSupplier::handleDemandMessage suppress errors

[ https://issues.apache.org/jira/browse/IGNITE-10995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-10995: -- Fix Version/s: 2.8 > GridDhtPartitionSupplier::handleDemandMessage suppress errors >

[jira] [Commented] (IGNITE-10995) GridDhtPartitionSupplier::handleDemandMessage suppress errors

[ https://issues.apache.org/jira/browse/IGNITE-10995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16754197#comment-16754197 ] Alexey Goncharuk commented on IGNITE-10995: --- [~mstepachev], a few comments: 1) Please change

[jira] [Updated] (IGNITE-11050) Potential deadlock caused by DhtColocatedLockFuture#map being called inside topology read lock

[ https://issues.apache.org/jira/browse/IGNITE-11050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-11050: -- Labels: MakeTeamcityGreenAgain (was: ) > Potential deadlock caused by

[jira] [Updated] (IGNITE-11048) Start node with TTL caches causes failure handler activity

[ https://issues.apache.org/jira/browse/IGNITE-11048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-11048: -- Ignite Flags: (was: Docs Required) > Start node with TTL caches causes failure

[jira] [Commented] (IGNITE-11048) Start node with TTL caches causes failure handler activity

[ https://issues.apache.org/jira/browse/IGNITE-11048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16752493#comment-16752493 ] Alexey Goncharuk commented on IGNITE-11048: --- [~aealeksandrov], thanks, merged your changes to

[jira] [Commented] (IGNITE-11023) Processing data bag on GridMarshallerMappingProcessor consume many time

[ https://issues.apache.org/jira/browse/IGNITE-11023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16752453#comment-16752453 ] Alexey Goncharuk commented on IGNITE-11023: --- [~ascherbakov], are you ok with the changes? I

[jira] [Commented] (IGNITE-10978) Remove unused tests marked with unclear todo

[ https://issues.apache.org/jira/browse/IGNITE-10978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16752443#comment-16752443 ] Alexey Goncharuk commented on IGNITE-10978: --- [~dpavlov], yes, unless I am missing something,

[jira] [Comment Edited] (IGNITE-11089) Get rid of partition ID in intra-partition page links stored in delta records

[ https://issues.apache.org/jira/browse/IGNITE-11089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16752256#comment-16752256 ] Alexey Goncharuk edited comment on IGNITE-11089 at 1/25/19 2:25 PM:

[jira] [Commented] (IGNITE-11089) Get rid of partition ID in intra-partition page links stored in delta records

[ https://issues.apache.org/jira/browse/IGNITE-11089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16752256#comment-16752256 ] Alexey Goncharuk commented on IGNITE-11089: --- This is a good idea. I think to properly

[jira] [Commented] (IGNITE-11016) RecoveryLastReceivedMessage(NEED_WAIT) fails with "Failed to encrypt data (SSL engine error)".

[ https://issues.apache.org/jira/browse/IGNITE-11016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16750873#comment-16750873 ] Alexey Goncharuk commented on IGNITE-11016: --- [~voropava], changes look good to me.

[jira] [Updated] (IGNITE-11050) Potential deadlock caused by DhtColocatedLockFuture#map being called inside topology read lock

[ https://issues.apache.org/jira/browse/IGNITE-11050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-11050: -- Priority: Critical (was: Major) > Potential deadlock caused by

[jira] [Assigned] (IGNITE-11050) Potential deadlock caused by DhtColocatedLockFuture#map being called inside topology read lock

[ https://issues.apache.org/jira/browse/IGNITE-11050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk reassigned IGNITE-11050: - Assignee: Alexey Goncharuk > Potential deadlock caused by

<    2   3   4   5   6   7   8   9   10   11   >