[jira] [Updated] (IGNITE-18441) Fix busylock usage in MetastorageManager

[ https://issues.apache.org/jira/browse/IGNITE-18441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-18441: --- Description: *Motivation:* We are using a busy lock to avoid invocation of a

[jira] [Commented] (IGNITE-18057) Sql. Fix index scan transactional consistency.

[ https://issues.apache.org/jira/browse/IGNITE-18057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17651371#comment-17651371 ] Vladislav Pyatkov commented on IGNITE-18057: Merged

[jira] [Commented] (IGNITE-18432) SafeTimeCandidateManager#commitIndex() fails assertion if indices have different terms

[ https://issues.apache.org/jira/browse/IGNITE-18432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17651291#comment-17651291 ] Vladislav Pyatkov commented on IGNITE-18432: Merged

[jira] [Commented] (IGNITE-18050) Possible phantom reads during sorted index scan

[ https://issues.apache.org/jira/browse/IGNITE-18050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17650482#comment-17650482 ] Vladislav Pyatkov commented on IGNITE-18050: Merged

[jira] [Commented] (IGNITE-18316) Reusing same waiter for multiple acquisitions can lead to races due to future rewrite outside of synchronized section

[ https://issues.apache.org/jira/browse/IGNITE-18316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17649746#comment-17649746 ] Vladislav Pyatkov commented on IGNITE-18316: Merged

[jira] [Commented] (IGNITE-18316) Reusing same waiter for multiple acquisitions can lead to races due to future rewrite outside of synchronized section

[ https://issues.apache.org/jira/browse/IGNITE-18316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17649745#comment-17649745 ] Vladislav Pyatkov commented on IGNITE-18316: LGTM > Reusing same waiter for multiple

[jira] [Assigned] (IGNITE-18057) Sql. Fix index scan transactional consistency.

[ https://issues.apache.org/jira/browse/IGNITE-18057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov reassigned IGNITE-18057: -- Assignee: Vladislav Pyatkov > Sql. Fix index scan transactional

[jira] [Commented] (IGNITE-14793) Remove temporary messages serialization code

[ https://issues.apache.org/jira/browse/IGNITE-14793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17649373#comment-17649373 ] Vladislav Pyatkov commented on IGNITE-14793: LGTM && Merged:

[jira] [Comment Edited] (IGNITE-18044) ItIgniteNodeRestartTest#testTwoNodesRestartDirect is failed after schema recovery fix.

[ https://issues.apache.org/jira/browse/IGNITE-18044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17646704#comment-17646704 ] Vladislav Pyatkov edited comment on IGNITE-18044 at 12/13/22 3:46 PM:

[jira] [Commented] (IGNITE-18044) ItIgniteNodeRestartTest#testTwoNodesRestartDirect is failed after schema recovery fix.

[ https://issues.apache.org/jira/browse/IGNITE-18044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17646704#comment-17646704 ] Vladislav Pyatkov commented on IGNITE-18044: The root cause of the is that we do not

[jira] [Commented] (IGNITE-18264) Add PeerId index support

[ https://issues.apache.org/jira/browse/IGNITE-18264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17646203#comment-17646203 ] Vladislav Pyatkov commented on IGNITE-18264: Merged

[jira] [Commented] (IGNITE-18264) Add PeerId index support

[ https://issues.apache.org/jira/browse/IGNITE-18264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17646200#comment-17646200 ] Vladislav Pyatkov commented on IGNITE-18264: LGTM > Add PeerId index support >

[jira] [Commented] (IGNITE-17871) Use network serialization for RAFT commands

[ https://issues.apache.org/jira/browse/IGNITE-17871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17645996#comment-17645996 ] Vladislav Pyatkov commented on IGNITE-17871: LGTM > Use network serialization for RAFT

[jira] [Assigned] (IGNITE-18044) ItIgniteNodeRestartTest#testTwoNodesRestartDirect is failed after schema recovery fix.

[ https://issues.apache.org/jira/browse/IGNITE-18044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov reassigned IGNITE-18044: -- Assignee: Vladislav Pyatkov >

[jira] [Commented] (IGNITE-18294) Multiple lock intentions support

[ https://issues.apache.org/jira/browse/IGNITE-18294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17644484#comment-17644484 ] Vladislav Pyatkov commented on IGNITE-18294: Merged

[jira] [Updated] (IGNITE-18351) Make a lock menagment interface modre friendly

[ https://issues.apache.org/jira/browse/IGNITE-18351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-18351: --- Description: Recently, we redesigned the behavior of lock manager, but did not

[jira] [Created] (IGNITE-18351) Make a lock menagment interface modre friendly

Vladislav Pyatkov created IGNITE-18351: -- Summary: Make a lock menagment interface modre friendly Key: IGNITE-18351 URL: https://issues.apache.org/jira/browse/IGNITE-18351 Project: Ignite

[jira] [Updated] (IGNITE-18350) Redesign two ciollections of lock modes to a bitset into the heap lock manager

[ https://issues.apache.org/jira/browse/IGNITE-18350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-18350: --- Description: We have two collections, those store lock modes: {code}

[jira] [Updated] (IGNITE-18350) Redesign two ciollections of lock modes to a bitset into the heap lock manager

[ https://issues.apache.org/jira/browse/IGNITE-18350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-18350: --- Description: We have two collections, those store lock modes: {code}

[jira] [Updated] (IGNITE-18350) Redesign two ciollections of lock modes to a bitset into the heap lock manager

[ https://issues.apache.org/jira/browse/IGNITE-18350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-18350: --- Summary: Redesign two ciollections of lock modes to a bitset into the heap lock

[jira] [Updated] (IGNITE-18350) Redesign two ciollection of lock modes to a bitset into the heap lock manager

[ https://issues.apache.org/jira/browse/IGNITE-18350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-18350: --- Labels: ignite-3 (was: ) > Redesign two ciollection of lock modes to a bitset

[jira] [Created] (IGNITE-18350) Redesign two ciollection of lock modes to a bitset into the heap lock manager

Vladislav Pyatkov created IGNITE-18350: -- Summary: Redesign two ciollection of lock modes to a bitset into the heap lock manager Key: IGNITE-18350 URL: https://issues.apache.org/jira/browse/IGNITE-18350

[jira] [Assigned] (IGNITE-18294) Multiple lock intentions support

[ https://issues.apache.org/jira/browse/IGNITE-18294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov reassigned IGNITE-18294: -- Assignee: Vladislav Pyatkov (was: Denis Chudov) > Multiple lock intentions

[jira] [Commented] (IGNITE-17938) Implement thread-safe enlisting of a primary node into a transaction

[ https://issues.apache.org/jira/browse/IGNITE-17938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17643773#comment-17643773 ] Vladislav Pyatkov commented on IGNITE-17938: LGTM This patch is solved the issue, but we

[jira] [Commented] (IGNITE-18051) Extend test coverage for lock model

[ https://issues.apache.org/jira/browse/IGNITE-18051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17642335#comment-17642335 ] Vladislav Pyatkov commented on IGNITE-18051: Merged

[jira] [Assigned] (IGNITE-18051) Extend test coverage for lock model

[ https://issues.apache.org/jira/browse/IGNITE-18051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov reassigned IGNITE-18051: -- Assignee: Vladislav Pyatkov > Extend test coverage for lock model >

[jira] [Updated] (IGNITE-18299) Value comparison in table operations

[ https://issues.apache.org/jira/browse/IGNITE-18299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-18299: --- Labels: ignite-3 (was: ) > Value comparison in table operations >

[jira] [Created] (IGNITE-18299) Value comparison in table operations

Vladislav Pyatkov created IGNITE-18299: -- Summary: Value comparison in table operations Key: IGNITE-18299 URL: https://issues.apache.org/jira/browse/IGNITE-18299 Project: Ignite Issue

[jira] [Commented] (IGNITE-18172) Raft learners rebalance

[ https://issues.apache.org/jira/browse/IGNITE-18172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17640021#comment-17640021 ] Vladislav Pyatkov commented on IGNITE-18172: Merged

[jira] [Commented] (IGNITE-18172) Raft learners rebalance

[ https://issues.apache.org/jira/browse/IGNITE-18172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17640004#comment-17640004 ] Vladislav Pyatkov commented on IGNITE-18172: LGTM > Raft learners rebalance >

[jira] [Commented] (IGNITE-18050) Possible phantom reads during sorted index scan

[ https://issues.apache.org/jira/browse/IGNITE-18050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17639891#comment-17639891 ] Vladislav Pyatkov commented on IGNITE-18050: The issue can not be fixed until IGNITE-18243

[jira] [Commented] (IGNITE-17733) Change lock manager implementation

[ https://issues.apache.org/jira/browse/IGNITE-17733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17638752#comment-17638752 ] Vladislav Pyatkov commented on IGNITE-17733: Merged

[jira] [Comment Edited] (IGNITE-17733) Change lock manager implementation

[ https://issues.apache.org/jira/browse/IGNITE-17733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17638752#comment-17638752 ] Vladislav Pyatkov edited comment on IGNITE-17733 at 11/25/22 7:28 PM:

[jira] [Commented] (IGNITE-17733) Change lock manager implementation

[ https://issues.apache.org/jira/browse/IGNITE-17733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17638751#comment-17638751 ] Vladislav Pyatkov commented on IGNITE-17733: LGTM > Change lock manager implementation >

[jira] [Updated] (IGNITE-18243) Implement a peek method for the sorted index cursor

[ https://issues.apache.org/jira/browse/IGNITE-18243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-18243: --- Ignite Flags: (was: Docs Required,Release Notes Required) > Implement a peek

[jira] [Updated] (IGNITE-18243) Implement a peek method for the sorted index cursor

[ https://issues.apache.org/jira/browse/IGNITE-18243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-18243: --- Labels: ignite-3 (was: ) > Implement a peek method for the sorted index cursor >

[jira] [Created] (IGNITE-18243) Implement a peek method for the sorted index cursor

Vladislav Pyatkov created IGNITE-18243: -- Summary: Implement a peek method for the sorted index cursor Key: IGNITE-18243 URL: https://issues.apache.org/jira/browse/IGNITE-18243 Project: Ignite

[jira] [Updated] (IGNITE-18050) Possible phantom reads during sorted index scan

[ https://issues.apache.org/jira/browse/IGNITE-18050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-18050: --- Description: According to transaction protocol IEP [1], locking protocol for scan

[jira] [Updated] (IGNITE-18050) Possible phantom reads during sorted index scan

[ https://issues.apache.org/jira/browse/IGNITE-18050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-18050: --- Description: According to transaction protocol IEP [1], locking protocol for scan

[jira] [Commented] (IGNITE-18165) Apply short term locks to sorted indexes

[ https://issues.apache.org/jira/browse/IGNITE-18165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17637743#comment-17637743 ] Vladislav Pyatkov commented on IGNITE-18165: Merged

[jira] [Assigned] (IGNITE-18050) Possible phantom reads during sorted index scan

[ https://issues.apache.org/jira/browse/IGNITE-18050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov reassigned IGNITE-18050: -- Assignee: Vladislav Pyatkov > Possible phantom reads during sorted index

[jira] [Commented] (IGNITE-18204) Start RAFT groups of table partitions in parallel

[ https://issues.apache.org/jira/browse/IGNITE-18204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17637206#comment-17637206 ] Vladislav Pyatkov commented on IGNITE-18204: Merged

[jira] [Commented] (IGNITE-18204) Start RAFT groups of table partitions in parallel

[ https://issues.apache.org/jira/browse/IGNITE-18204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17637146#comment-17637146 ] Vladislav Pyatkov commented on IGNITE-18204: LGTM > Start RAFT groups of table partitions

[jira] [Updated] (IGNITE-18192) Conditional lock

[ https://issues.apache.org/jira/browse/IGNITE-18192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-18192: --- Epic Link: IGNITE-18042 > Conditional lock > > >

[jira] [Created] (IGNITE-18194) Scan chooses incorerect timestamp to scan storage in RO transaction

Vladislav Pyatkov created IGNITE-18194: -- Summary: Scan chooses incorerect timestamp to scan storage in RO transaction Key: IGNITE-18194 URL: https://issues.apache.org/jira/browse/IGNITE-18194

[jira] [Created] (IGNITE-18192) Conditional lock

Vladislav Pyatkov created IGNITE-18192: -- Summary: Conditional lock Key: IGNITE-18192 URL: https://issues.apache.org/jira/browse/IGNITE-18192 Project: Ignite Issue Type: Improvement

[jira] [Commented] (IGNITE-18181) Race during table creation

[ https://issues.apache.org/jira/browse/IGNITE-18181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17635237#comment-17635237 ] Vladislav Pyatkov commented on IGNITE-18181: Merged

[jira] [Commented] (IGNITE-18181) Race during table creation

[ https://issues.apache.org/jira/browse/IGNITE-18181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17635236#comment-17635236 ] Vladislav Pyatkov commented on IGNITE-18181: LGTM > Race during table creation >

[jira] [Commented] (IGNITE-18122) Track last applied term and group config in storages

[ https://issues.apache.org/jira/browse/IGNITE-18122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17634764#comment-17634764 ] Vladislav Pyatkov commented on IGNITE-18122: The modification connected with transferring a

[jira] [Assigned] (IGNITE-18165) Apply short term loks to sorted indexes

[ https://issues.apache.org/jira/browse/IGNITE-18165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov reassigned IGNITE-18165: -- Assignee: Vladislav Pyatkov > Apply short term loks to sorted indexes >

[jira] [Updated] (IGNITE-18052) Introduce short term locks for sorted indexes operations

[ https://issues.apache.org/jira/browse/IGNITE-18052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-18052: --- Description: *Motivation:* In some case, required to release a specific lock

[jira] [Updated] (IGNITE-18165) Apply short term loks to sorted indexes

[ https://issues.apache.org/jira/browse/IGNITE-18165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-18165: --- Description: *Motivation:* Transaction isolation requires using short term locks

[jira] [Created] (IGNITE-18165) Apply short term loks to sorted indexes

Vladislav Pyatkov created IGNITE-18165: -- Summary: Apply short term loks to sorted indexes Key: IGNITE-18165 URL: https://issues.apache.org/jira/browse/IGNITE-18165 Project: Ignite Issue

[jira] [Commented] (IGNITE-18048) Issues breakdown for lock management

[ https://issues.apache.org/jira/browse/IGNITE-18048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17633555#comment-17633555 ] Vladislav Pyatkov commented on IGNITE-18048: All tasks haves been created and been attached

[jira] [Resolved] (IGNITE-18048) Issues breakdown for lock management

[ https://issues.apache.org/jira/browse/IGNITE-18048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov resolved IGNITE-18048. Resolution: Fixed > Issues breakdown for lock management >

[jira] [Updated] (IGNITE-17999) Incorrect handling of TxStateReplicaRequest

[ https://issues.apache.org/jira/browse/IGNITE-17999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-17999: --- Description: *Motivation:* After observation, the following points were

[jira] [Updated] (IGNITE-17999) Incorrect handling of TxStateReplicaRequest

[ https://issues.apache.org/jira/browse/IGNITE-17999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-17999: --- Description: *Motivation:* After observation, the following points were

[jira] [Updated] (IGNITE-17999) Incorrect handling of TxStateReplicaRequest

[ https://issues.apache.org/jira/browse/IGNITE-17999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-17999: --- Description: *Motivation:* After observation, the following points were

[jira] [Updated] (IGNITE-17999) Incorrect handling of TxStateReplicaRequest

[ https://issues.apache.org/jira/browse/IGNITE-17999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-17999: --- Description: *Motivation:* After observation, the following points were

[jira] [Commented] (IGNITE-18124) [Ignite Website] Ignite Summit Europe_Update website banners_Recordings Now Available

[ https://issues.apache.org/jira/browse/IGNITE-18124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17632320#comment-17632320 ] Vladislav Pyatkov commented on IGNITE-18124: Merged

[jira] [Commented] (IGNITE-17846) Direct configuration request leads to synchronously waiting on network

[ https://issues.apache.org/jira/browse/IGNITE-17846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17632239#comment-17632239 ] Vladislav Pyatkov commented on IGNITE-17846: Merged

[jira] [Assigned] (IGNITE-18052) Introduce short term locks for sorted indexes operations

[ https://issues.apache.org/jira/browse/IGNITE-18052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov reassigned IGNITE-18052: -- Assignee: Vladislav Pyatkov > Introduce short term locks for sorted indexes

[jira] [Commented] (IGNITE-17846) Direct configuration request leads to synchronously waiting on network

[ https://issues.apache.org/jira/browse/IGNITE-17846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17629770#comment-17629770 ] Vladislav Pyatkov commented on IGNITE-17846: [~alapin] I tried to explain what have done

[jira] [Updated] (IGNITE-17999) Incorrect handling of TxStateReplicaRequest

[ https://issues.apache.org/jira/browse/IGNITE-17999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-17999: --- Description: *Motivation:* After observation, the following points were

[jira] [Updated] (IGNITE-17999) Incorrect handling of TxStateReplicaRequest

[ https://issues.apache.org/jira/browse/IGNITE-17999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-17999: --- Description: *Motivation:* After observation, the following points were

[jira] [Updated] (IGNITE-17999) Incorrect handling of TxStateReplicaRequest

[ https://issues.apache.org/jira/browse/IGNITE-17999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-17999: --- Description: *Motivation* After observation, the following points were

[jira] [Updated] (IGNITE-17846) Direct configuration request leads to synchronously waiting on network

[ https://issues.apache.org/jira/browse/IGNITE-17846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-17846: --- Description: *Motivation* .NET suite periodical hang out. Log shows the suspicious

[jira] [Updated] (IGNITE-17846) Direct configuration request leads to synchronously waiting on network

[ https://issues.apache.org/jira/browse/IGNITE-17846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-17846: --- Description: *Motivation* .NET suite periodical hang out. Log shows the suspicious

[jira] [Updated] (IGNITE-17846) Direct configuration request leads to synchronously waiting on network

[ https://issues.apache.org/jira/browse/IGNITE-17846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-17846: --- Description: *Motivation* .NET suite periodical hang out. Log shows the suspicious

[jira] [Updated] (IGNITE-17846) Direct configuration request leads to synchronously waiting on network

[ https://issues.apache.org/jira/browse/IGNITE-17846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-17846: --- Description: *Motivation* .NET suite periodical hang out. Log shows the suspicious

[jira] [Updated] (IGNITE-17846) Direct configuration request leads to synchronously waiting on network

[ https://issues.apache.org/jira/browse/IGNITE-17846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-17846: --- Ignite Flags: (was: Docs Required,Release Notes Required) > Direct configuration

[jira] [Assigned] (IGNITE-17846) Direct configuration request leads to synchronously waiting on network

[ https://issues.apache.org/jira/browse/IGNITE-17846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov reassigned IGNITE-17846: -- Assignee: Vladislav Pyatkov > Direct configuration request leads to

[jira] [Updated] (IGNITE-18043) Replaceable deadlock prevention mechanism

[ https://issues.apache.org/jira/browse/IGNITE-18043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-18043: --- Description: *Motivation:* We have an embedded deadlock prevention strategy

[jira] [Updated] (IGNITE-17733) Chnage lock manager implementation

[ https://issues.apache.org/jira/browse/IGNITE-17733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-17733: --- Description: *Motivation:* Lock manager should be based on _Wait-Die_ deadlock

[jira] [Updated] (IGNITE-17733) Chnage lock manager implementation

[ https://issues.apache.org/jira/browse/IGNITE-17733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-17733: --- Description: Lock manager should be based on _Wait-Die_ deadlock resolution

[jira] [Updated] (IGNITE-17733) Chnage lock manager implementation

[ https://issues.apache.org/jira/browse/IGNITE-17733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-17733: --- Summary: Chnage lock manager implementation (was: Resume honest index lock) >

[jira] [Updated] (IGNITE-18048) Breack down issues for lock managment

[ https://issues.apache.org/jira/browse/IGNITE-18048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-18048: --- Description: Estimate and add a description in detail for all tickets from the

[jira] [Updated] (IGNITE-18048) Breack down issues for lock managment

[ https://issues.apache.org/jira/browse/IGNITE-18048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-18048: --- Description: Estimate and add a description in detail for all ticket for the epic.

[jira] [Created] (IGNITE-18048) Breack down issues for lock managment

Vladislav Pyatkov created IGNITE-18048: -- Summary: Breack down issues for lock managment Key: IGNITE-18048 URL: https://issues.apache.org/jira/browse/IGNITE-18048 Project: Ignite Issue

[jira] [Updated] (IGNITE-18045) Short term locks support

[ https://issues.apache.org/jira/browse/IGNITE-18045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-18045: --- Description: [Transaction

[jira] [Updated] (IGNITE-18045) Short term locks support

[ https://issues.apache.org/jira/browse/IGNITE-18045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-18045: --- Description: [Transaction

[jira] [Created] (IGNITE-18045) Short term locks support

Vladislav Pyatkov created IGNITE-18045: -- Summary: Short term locks support Key: IGNITE-18045 URL: https://issues.apache.org/jira/browse/IGNITE-18045 Project: Ignite Issue Type:

[jira] [Updated] (IGNITE-18043) Replaceable deadlock prevention mechanism

[ https://issues.apache.org/jira/browse/IGNITE-18043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-18043: --- Description: We have an embedded deadlock prevention strategy (presently, it is

[jira] [Created] (IGNITE-18043) Replaceable deadlock prevention mechanism

Vladislav Pyatkov created IGNITE-18043: -- Summary: Replaceable deadlock prevention mechanism Key: IGNITE-18043 URL: https://issues.apache.org/jira/browse/IGNITE-18043 Project: Ignite

[jira] [Updated] (IGNITE-17733) Resume honest index lock

[ https://issues.apache.org/jira/browse/IGNITE-17733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-17733: --- Epic Link: IGNITE-18042 > Resume honest index lock > > >

[jira] [Updated] (IGNITE-18042) Rework lock management mechanism

[ https://issues.apache.org/jira/browse/IGNITE-18042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-18042: --- Description: Today lock management is represented by interface LockManager

[jira] [Updated] (IGNITE-18042) Rework lock management mechanism

[ https://issues.apache.org/jira/browse/IGNITE-18042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-18042: --- Description: Today lock management is represented by interface LockManager

[jira] [Created] (IGNITE-18042) Rework locks menegment mechanism

Vladislav Pyatkov created IGNITE-18042: -- Summary: Rework locks menegment mechanism Key: IGNITE-18042 URL: https://issues.apache.org/jira/browse/IGNITE-18042 Project: Ignite Issue Type:

[jira] [Commented] (IGNITE-17980) ./gradlew clean build -x test fails

[ https://issues.apache.org/jira/browse/IGNITE-17980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17627002#comment-17627002 ] Vladislav Pyatkov commented on IGNITE-17980: [~aleksandr.pakhomov] Could you, prepare a

[jira] [Commented] (IGNITE-17759) Need to pass commitTableId and commitPartitionId to MvPartitionStorage#addWrite

[ https://issues.apache.org/jira/browse/IGNITE-17759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17626430#comment-17626430 ] Vladislav Pyatkov commented on IGNITE-17759: Merged

[jira] [Commented] (IGNITE-18005) ItDataTypesTest#testUnicodeStrings fails with IndexOutOfBoundsException

[ https://issues.apache.org/jira/browse/IGNITE-18005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17625617#comment-17625617 ] Vladislav Pyatkov commented on IGNITE-18005: Merged

[jira] [Commented] (IGNITE-18005) ItDataTypesTest#testUnicodeStrings fails with IndexOutOfBoundsException

[ https://issues.apache.org/jira/browse/IGNITE-18005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17625603#comment-17625603 ] Vladislav Pyatkov commented on IGNITE-18005: It is nor exactly right, because the tombstone

[jira] [Comment Edited] (IGNITE-18005) ItDataTypesTest#testUnicodeStrings fails with IndexOutOfBoundsException

[ https://issues.apache.org/jira/browse/IGNITE-18005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17625603#comment-17625603 ] Vladislav Pyatkov edited comment on IGNITE-18005 at 10/28/22 10:56 AM:

[jira] [Assigned] (IGNITE-18005) ItDataTypesTest#testUnicodeStrings fails with IndexOutOfBoundsException

[ https://issues.apache.org/jira/browse/IGNITE-18005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov reassigned IGNITE-18005: -- Assignee: Vladislav Pyatkov > ItDataTypesTest#testUnicodeStrings fails with

[jira] [Commented] (IGNITE-18004) Fix compilation after merging safe time propagation

[ https://issues.apache.org/jira/browse/IGNITE-18004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17625328#comment-17625328 ] Vladislav Pyatkov commented on IGNITE-18004: LGTM > Fix compilation after merging safe

[jira] [Created] (IGNITE-17999) Incorrect handling of TxStateReplicaRequest

Vladislav Pyatkov created IGNITE-17999: -- Summary: Incorrect handling of TxStateReplicaRequest Key: IGNITE-17999 URL: https://issues.apache.org/jira/browse/IGNITE-17999 Project: Ignite

[jira] [Commented] (IGNITE-17980) ./gradlew clean build -x test fails

[ https://issues.apache.org/jira/browse/IGNITE-17980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17624969#comment-17624969 ] Vladislav Pyatkov commented on IGNITE-17980: Merged

[jira] [Assigned] (IGNITE-17967) RO writeIntent resolution tests hang up in case of multi node cluster

[ https://issues.apache.org/jira/browse/IGNITE-17967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov reassigned IGNITE-17967: -- Assignee: Vladislav Pyatkov > RO writeIntent resolution tests hang up in

[jira] [Commented] (IGNITE-17260) Enrich IgniteTransactions and Transaction interfaces with RO related methods

[ https://issues.apache.org/jira/browse/IGNITE-17260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17623756#comment-17623756 ] Vladislav Pyatkov commented on IGNITE-17260: LGTM > Enrich IgniteTransactions and

[jira] [Updated] (IGNITE-17938) Different primary nodes can be enlisted in one transaction for the same replication group

[ https://issues.apache.org/jira/browse/IGNITE-17938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-17938: --- Labels: ignite-3 (was: ) > Different primary nodes can be enlisted in one

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