[jira] [Assigned] (IGNITE-21051) Fix javadocs for IndexQuery

[ https://issues.apache.org/jira/browse/IGNITE-21051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Valuyskiy reassigned IGNITE-21051: --- Assignee: Oleg Valuyskiy > Fix javadocs for IndexQuery > -

[jira] [Updated] (IGNITE-20992) ODBC 3.0: Propagate username to connection_info

[ https://issues.apache.org/jira/browse/IGNITE-20992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-20992: - Fix Version/s: 3.0.0-beta2 > ODBC 3.0: Propagate username to connection_info >

[jira] [Updated] (IGNITE-20992) ODBC 3.0: Propagate username to connection_info

[ https://issues.apache.org/jira/browse/IGNITE-20992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-20992: - Ignite Flags: (was: Docs Required,Release Notes Required) > ODBC 3.0: Propagate username to c

[jira] [Commented] (IGNITE-20992) ODBC 3.0: Propagate username to connection_info

[ https://issues.apache.org/jira/browse/IGNITE-20992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795904#comment-17795904 ] Igor Sapego commented on IGNITE-20992: -- Looks good to me. > ODBC 3.0: Propagate u

[jira] [Commented] (IGNITE-21059) We have upgraded our ignite instance from 2.7.6 to 2.14. Found long running cache operations

[ https://issues.apache.org/jira/browse/IGNITE-21059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795899#comment-17795899 ] Vipul Thakur commented on IGNITE-21059: --- Thank you for your response [~zstan]  

[jira] [Commented] (IGNITE-21059) We have upgraded our ignite instance from 2.7.6 to 2.14. Found long running cache operations

[ https://issues.apache.org/jira/browse/IGNITE-21059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795883#comment-17795883 ] Evgeny Stanilovsky commented on IGNITE-21059: - 1. yep just erase or comment

[jira] [Commented] (IGNITE-21059) We have upgraded our ignite instance from 2.7.6 to 2.14. Found long running cache operations

[ https://issues.apache.org/jira/browse/IGNITE-21059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795867#comment-17795867 ] Vipul Thakur commented on IGNITE-21059: --- So as per my understanding i will be doi

[jira] [Commented] (IGNITE-21059) We have upgraded our ignite instance from 2.7.6 to 2.14. Found long running cache operations

[ https://issues.apache.org/jira/browse/IGNITE-21059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795864#comment-17795864 ] Evgeny Stanilovsky commented on IGNITE-21059: - if you are talking about Tcp

[jira] [Comment Edited] (IGNITE-21059) We have upgraded our ignite instance from 2.7.6 to 2.14. Found long running cache operations

[ https://issues.apache.org/jira/browse/IGNITE-21059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795861#comment-17795861 ] Vipul Thakur edited comment on IGNITE-21059 at 12/12/23 5:33 PM:

[jira] [Comment Edited] (IGNITE-21059) We have upgraded our ignite instance from 2.7.6 to 2.14. Found long running cache operations

[ https://issues.apache.org/jira/browse/IGNITE-21059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795861#comment-17795861 ] Vipul Thakur edited comment on IGNITE-21059 at 12/12/23 5:32 PM:

[jira] [Commented] (IGNITE-21059) We have upgraded our ignite instance from 2.7.6 to 2.14. Found long running cache operations

[ https://issues.apache.org/jira/browse/IGNITE-21059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795861#comment-17795861 ] Vipul Thakur commented on IGNITE-21059: --- We have daily requirement of 90-120 mill

[jira] [Commented] (IGNITE-21059) We have upgraded our ignite instance from 2.7.6 to 2.14. Found long running cache operations

[ https://issues.apache.org/jira/browse/IGNITE-21059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795860#comment-17795860 ] Evgeny Stanilovsky commented on IGNITE-21059: - failureDetectionTimeout - to

[jira] [Commented] (IGNITE-21059) We have upgraded our ignite instance from 2.7.6 to 2.14. Found long running cache operations

[ https://issues.apache.org/jira/browse/IGNITE-21059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795859#comment-17795859 ] Vipul Thakur commented on IGNITE-21059: --- We also have configured socket timeout a

[jira] [Comment Edited] (IGNITE-21059) We have upgraded our ignite instance from 2.7.6 to 2.14. Found long running cache operations

[ https://issues.apache.org/jira/browse/IGNITE-21059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795859#comment-17795859 ] Vipul Thakur edited comment on IGNITE-21059 at 12/12/23 5:12 PM:

[jira] [Commented] (IGNITE-21059) We have upgraded our ignite instance from 2.7.6 to 2.14. Found long running cache operations

[ https://issues.apache.org/jira/browse/IGNITE-21059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795858#comment-17795858 ] Vipul Thakur commented on IGNITE-21059: --- In 2.7.6 we use to observe long jvm paus

[jira] [Commented] (IGNITE-21059) We have upgraded our ignite instance from 2.7.6 to 2.14. Found long running cache operations

[ https://issues.apache.org/jira/browse/IGNITE-21059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795855#comment-17795855 ] Evgeny Stanilovsky commented on IGNITE-21059: - i suppose you no need such h

[jira] [Comment Edited] (IGNITE-21059) We have upgraded our ignite instance from 2.7.6 to 2.14. Found long running cache operations

[ https://issues.apache.org/jira/browse/IGNITE-21059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795851#comment-17795851 ] Vipul Thakur edited comment on IGNITE-21059 at 12/12/23 4:59 PM:

[jira] [Commented] (IGNITE-21059) We have upgraded our ignite instance from 2.7.6 to 2.14. Found long running cache operations

[ https://issues.apache.org/jira/browse/IGNITE-21059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795851#comment-17795851 ] Vipul Thakur commented on IGNITE-21059: --- we have two k8s cluster connected to tha

[jira] [Comment Edited] (IGNITE-21059) We have upgraded our ignite instance from 2.7.6 to 2.14. Found long running cache operations

[ https://issues.apache.org/jira/browse/IGNITE-21059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795851#comment-17795851 ] Vipul Thakur edited comment on IGNITE-21059 at 12/12/23 4:59 PM:

[jira] [Updated] (IGNITE-21059) We have upgraded our ignite instance from 2.7.6 to 2.14. Found long running cache operations

[ https://issues.apache.org/jira/browse/IGNITE-21059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vipul Thakur updated IGNITE-21059: -- Description: We have recently upgraded from 2.7.6 to 2.14 due to the issue observed in produ

[jira] [Commented] (IGNITE-21059) We have upgraded our ignite instance from 2.7.6 to 2.14. Found long running cache operations

[ https://issues.apache.org/jira/browse/IGNITE-21059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795846#comment-17795846 ] Evgeny Stanilovsky commented on IGNITE-21059: - do you really need 44 client

[jira] [Commented] (IGNITE-21059) We have upgraded our ignite instance from 2.7.6 to 2.14. Found long running cache operations

[ https://issues.apache.org/jira/browse/IGNITE-21059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795838#comment-17795838 ] Vipul Thakur commented on IGNITE-21059: --- Ok please give me sometime and we will c

[jira] [Commented] (IGNITE-21059) We have upgraded our ignite instance from 2.7.6 to 2.14. Found long running cache operations

[ https://issues.apache.org/jira/browse/IGNITE-21059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795836#comment-17795836 ] Evgeny Stanilovsky commented on IGNITE-21059: - need all logs from all nodes

[jira] [Commented] (IGNITE-20652) .NET: Thin 3.0: add SQL script execution API

[ https://issues.apache.org/jira/browse/IGNITE-20652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795818#comment-17795818 ] Pavel Tupitsyn commented on IGNITE-20652: - Comment addressed. Merged to main: 5

[jira] [Assigned] (IGNITE-19215) ODBC 3.0: Implement DML data batching

[ https://issues.apache.org/jira/browse/IGNITE-19215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego reassigned IGNITE-19215: Assignee: Dmitrii Zabotlin (was: Igor Sapego) > ODBC 3.0: Implement DML data batching >

[jira] [Assigned] (IGNITE-19720) ODBC 3.0: Implement retrieval of Ignite version on handshake

[ https://issues.apache.org/jira/browse/IGNITE-19720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego reassigned IGNITE-19720: Assignee: Dmitrii Zabotlin (was: Igor Sapego) > ODBC 3.0: Implement retrieval of Ignite

[jira] [Assigned] (IGNITE-19969) ODBC 3.0: Add support for period, duration and big_integer types

[ https://issues.apache.org/jira/browse/IGNITE-19969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego reassigned IGNITE-19969: Assignee: Dmitrii Zabotlin > ODBC 3.0: Add support for period, duration and big_integer

[jira] [Commented] (IGNITE-21032) ReadOnlyDynamicMBean.getAttributes may return a list of attribute values instead of Attribute instances

[ https://issues.apache.org/jira/browse/IGNITE-21032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795811#comment-17795811 ] Simon Greatrix commented on IGNITE-21032: - Fixed checkstyle issues and updated

[jira] [Assigned] (IGNITE-21032) ReadOnlyDynamicMBean.getAttributes may return a list of attribute values instead of Attribute instances

[ https://issues.apache.org/jira/browse/IGNITE-21032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Greatrix reassigned IGNITE-21032: --- Assignee: Vyacheslav Koptilin (was: Simon Greatrix) > ReadOnlyDynamicMBean.getAtt

[jira] [Updated] (IGNITE-20652) .NET: Thin 3.0: add SQL script execution API

[ https://issues.apache.org/jira/browse/IGNITE-20652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-20652: Summary: .NET: Thin 3.0: add SQL script execution API (was: .NET: Thin 3.0: support SQL

[jira] [Comment Edited] (IGNITE-21059) We have upgraded our ignite instance from 2.7.6 to 2.14. Found long running cache operations

[ https://issues.apache.org/jira/browse/IGNITE-21059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795714#comment-17795714 ] Vipul Thakur edited comment on IGNITE-21059 at 12/12/23 2:42 PM:

[jira] [Updated] (IGNITE-21072) NamedListConfiguration#get(java.util.UUID) should cast to polymorphic type

[ https://issues.apache.org/jira/browse/IGNITE-21072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Pakhnushev updated IGNITE-21072: -- Summary: NamedListConfiguration#get(java.util.UUID) should cast to polymorphic type

[jira] [Commented] (IGNITE-20652) .NET: Thin 3.0: support SQL script execution in dotnet thin client

[ https://issues.apache.org/jira/browse/IGNITE-20652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795773#comment-17795773 ] Igor Sapego commented on IGNITE-20652: -- Approved with a little comment. > .NET: T

[jira] [Created] (IGNITE-21072) NamedListConfiguration#get(java.util.UUID) doesn't work with polymorphic configurations

Vadim Pakhnushev created IGNITE-21072: - Summary: NamedListConfiguration#get(java.util.UUID) doesn't work with polymorphic configurations Key: IGNITE-21072 URL: https://issues.apache.org/jira/browse/IGNITE-2107

[jira] [Updated] (IGNITE-21071) Rollback the transaction on primary failure if replication is not finished

[ https://issues.apache.org/jira/browse/IGNITE-21071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin updated IGNITE-21071: - Description: h3. Motivation Despite the fact that it's not always necessary within ini

[jira] [Commented] (IGNITE-20994) Adjust writeIntentResolution logic in order to initiate the recovery if coordinator is dead

[ https://issues.apache.org/jira/browse/IGNITE-20994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795748#comment-17795748 ] Vladislav Pyatkov commented on IGNITE-20994: Merged 64d3bcb345a20e1dbcc554e

[jira] [Created] (IGNITE-21071) Rollback the transaction on primary failure if replication is not finished

Alexander Lapin created IGNITE-21071: Summary: Rollback the transaction on primary failure if replication is not finished Key: IGNITE-21071 URL: https://issues.apache.org/jira/browse/IGNITE-21071

[jira] [Updated] (IGNITE-21070) Ensure that data node's primary replica expiration properly handled

[ https://issues.apache.org/jira/browse/IGNITE-21070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin updated IGNITE-21070: - Labels: ignite-3 (was: ) > Ensure that data node's primary replica expiration properly

[jira] [Updated] (IGNITE-20652) .NET: Thin 3.0: support SQL script execution in dotnet thin client

[ https://issues.apache.org/jira/browse/IGNITE-20652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-20652: Ignite Flags: (was: Docs Required,Release Notes Required) > .NET: Thin 3.0: support SQL

[jira] [Updated] (IGNITE-21070) Ensure that data node's primary replica expiration properly handled

[ https://issues.apache.org/jira/browse/IGNITE-21070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin updated IGNITE-21070: - Description: h3. Motivation Corresponding primary replica expiration logic should alre

[jira] [Updated] (IGNITE-20994) Adjust writeIntentResolution logic in order to initiate the recovery if coordinator is dead

[ https://issues.apache.org/jira/browse/IGNITE-20994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Chudov updated IGNITE-20994: -- Reviewer: Vladislav Pyatkov > Adjust writeIntentResolution logic in order to initiate the rec

[jira] [Created] (IGNITE-21070) Ensure that data node's primary replica expiration properly handled

Alexander Lapin created IGNITE-21070: Summary: Ensure that data node's primary replica expiration properly handled Key: IGNITE-21070 URL: https://issues.apache.org/jira/browse/IGNITE-21070 Project

[jira] [Created] (IGNITE-21069) Tx on unstable topology: data node recovery

Alexander Lapin created IGNITE-21069: Summary: Tx on unstable topology: data node recovery Key: IGNITE-21069 URL: https://issues.apache.org/jira/browse/IGNITE-21069 Project: Ignite Issue

[jira] [Comment Edited] (IGNITE-21059) We have upgraded our ignite instance from 2.7.6 to 2.14. Found long running cache operations

[ https://issues.apache.org/jira/browse/IGNITE-21059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795735#comment-17795735 ] Vipul Thakur edited comment on IGNITE-21059 at 12/12/23 1:08 PM:

[jira] [Commented] (IGNITE-21059) We have upgraded our ignite instance from 2.7.6 to 2.14. Found long running cache operations

[ https://issues.apache.org/jira/browse/IGNITE-21059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795735#comment-17795735 ] Vipul Thakur commented on IGNITE-21059: --- Evidence that txn timeout is enabled at

[jira] [Created] (IGNITE-21068) Ignite node must not communicate with a node removed from the Physical Topology

Roman Puchkovskiy created IGNITE-21068: -- Summary: Ignite node must not communicate with a node removed from the Physical Topology Key: IGNITE-21068 URL: https://issues.apache.org/jira/browse/IGNITE-21068

[jira] [Comment Edited] (IGNITE-20745) TableManager.tableAsync(int tableId) is slowing down thin clients

[ https://issues.apache.org/jira/browse/IGNITE-20745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795722#comment-17795722 ] Igor Sapego edited comment on IGNITE-20745 at 12/12/23 12:44 PM:

[jira] [Comment Edited] (IGNITE-20745) TableManager.tableAsync(int tableId) is slowing down thin clients

[ https://issues.apache.org/jira/browse/IGNITE-20745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795722#comment-17795722 ] Igor Sapego edited comment on IGNITE-20745 at 12/12/23 12:42 PM:

[jira] [Commented] (IGNITE-20745) TableManager.tableAsync(int tableId) is slowing down thin clients

[ https://issues.apache.org/jira/browse/IGNITE-20745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795722#comment-17795722 ] Igor Sapego commented on IGNITE-20745: -- [~ibessonov] suggested to try the followin

[jira] [Assigned] (IGNITE-21032) ReadOnlyDynamicMBean.getAttributes may return a list of attribute values instead of Attribute instances

[ https://issues.apache.org/jira/browse/IGNITE-21032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Greatrix reassigned IGNITE-21032: --- Assignee: Simon Greatrix Taking ownership to fix checkstyle issues. > ReadOnlyDyn

[jira] [Commented] (IGNITE-21032) ReadOnlyDynamicMBean.getAttributes may return a list of attribute values instead of Attribute instances

[ https://issues.apache.org/jira/browse/IGNITE-21032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795719#comment-17795719 ] Simon Greatrix commented on IGNITE-21032: - Yes it is. However, the supplementar

[jira] [Assigned] (IGNITE-21063) Cannot create 1000 tables

[ https://issues.apache.org/jira/browse/IGNITE-21063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Bessonov reassigned IGNITE-21063: -- Assignee: Ivan Bessonov > Cannot create 1000 tables > - > >

[jira] [Commented] (IGNITE-21059) We have upgraded our ignite instance from 2.7.6 to 2.14. Found long running cache operations

[ https://issues.apache.org/jira/browse/IGNITE-21059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795714#comment-17795714 ] Vipul Thakur commented on IGNITE-21059: --- Hi  Thank you for quick response, we ha

[jira] [Commented] (IGNITE-21060) Extract ClusterNodeResolver as a separate entity

[ https://issues.apache.org/jira/browse/IGNITE-21060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795710#comment-17795710 ] Vladislav Pyatkov commented on IGNITE-21060: Merged 492f01b6423c3514cbe4b3a

[jira] [Updated] (IGNITE-21067) Clean up documents related to MVCC

[ https://issues.apache.org/jira/browse/IGNITE-21067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YuJue Li updated IGNITE-21067: -- Parent: IGNITE-13871 Issue Type: Sub-task (was: Improvement) > Clean up documents related to

[jira] [Commented] (IGNITE-21016) ItMixedQueriesTest.testIgniteSchemaAwaresAlterTableCommand is flaky

[ https://issues.apache.org/jira/browse/IGNITE-21016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795708#comment-17795708 ] Konstantin Orlov commented on IGNITE-21016: --- [~xtern], [~vpyatkov], folks, do

[jira] [Updated] (IGNITE-21039) Network performance optimization

[ https://issues.apache.org/jira/browse/IGNITE-21039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-21039: - Labels: ignite-3 (was: ) > Network performance optimization >

[jira] [Created] (IGNITE-21067) Clean up documents related to MVCC

YuJue Li created IGNITE-21067: - Summary: Clean up documents related to MVCC Key: IGNITE-21067 URL: https://issues.apache.org/jira/browse/IGNITE-21067 Project: Ignite Issue Type: Improvement

[jira] [Assigned] (IGNITE-20506) CacheAtomicityMode#TRANSACTIONAL_SNAPSHOT removal

[ https://issues.apache.org/jira/browse/IGNITE-20506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YuJue Li reassigned IGNITE-20506: - Assignee: Anton Vinogradov (was: YuJue Li) > CacheAtomicityMode#TRANSACTIONAL_SNAPSHOT remova

[jira] [Updated] (IGNITE-21063) Cannot create 1000 tables

[ https://issues.apache.org/jira/browse/IGNITE-21063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Bessonov updated IGNITE-21063: --- Description: Fails with OOM after a while, managing to create about 500 tales locally. We

[jira] [Updated] (IGNITE-21066) Create job priority change API

[ https://issues.apache.org/jira/browse/IGNITE-21066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin updated IGNITE-21066: --- Summary: Create job priority change API (was: Change job priority API) > Create jo

[jira] [Updated] (IGNITE-21066) Create job priority change API

[ https://issues.apache.org/jira/browse/IGNITE-21066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin updated IGNITE-21066: --- Description: Once a job has been accepted for execution and is in the queue, we sho

[jira] [Commented] (IGNITE-21059) We have upgraded our ignite instance from 2.7.6 to 2.14. Found long running cache operations

[ https://issues.apache.org/jira/browse/IGNITE-21059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795690#comment-17795690 ] Evgeny Stanilovsky commented on IGNITE-21059: - also you have infinite tx ti

[jira] [Commented] (IGNITE-21059) We have upgraded our ignite instance from 2.7.6 to 2.14. Found long running cache operations

[ https://issues.apache.org/jira/browse/IGNITE-21059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795688#comment-17795688 ] Evgeny Stanilovsky commented on IGNITE-21059: - also plz increase https://i

[jira] [Created] (IGNITE-21066) Change job priority API

Mikhail Pochatkin created IGNITE-21066: -- Summary: Change job priority API Key: IGNITE-21066 URL: https://issues.apache.org/jira/browse/IGNITE-21066 Project: Ignite Issue Type: Improvemen

[jira] [Resolved] (IGNITE-20847) Ownership mechanism for Compute Jobs

[ https://issues.apache.org/jira/browse/IGNITE-20847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin resolved IGNITE-20847. Resolution: Won't Fix > Ownership mechanism for Compute Jobs > --

[jira] [Comment Edited] (IGNITE-20463) Sql. Integration of TX-related statements into sql script processor

[ https://issues.apache.org/jira/browse/IGNITE-20463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795679#comment-17795679 ] Pavel Pereslegin edited comment on IGNITE-20463 at 12/12/23 10:58 AM: ---

[jira] [Updated] (IGNITE-20905) Make it possible to add an explicitly NULL column via ADD COLUMN

[ https://issues.apache.org/jira/browse/IGNITE-20905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Zhuravkov updated IGNITE-20905: -- Fix Version/s: 3.0.0-beta2 > Make it possible to add an explicitly NULL column via AD

[jira] [Updated] (IGNITE-21065) Enhance granularity of authentication events

[ https://issues.apache.org/jira/browse/IGNITE-21065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Gagarkin updated IGNITE-21065: --- Summary: Enhance granularity of authentication events (was: Extend AuthenticationEvent wit

[jira] [Commented] (IGNITE-20506) CacheAtomicityMode#TRANSACTIONAL_SNAPSHOT removal

[ https://issues.apache.org/jira/browse/IGNITE-20506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795678#comment-17795678 ] Anton Vinogradov commented on IGNITE-20506: --- [~liyuj], This Issue is already

[jira] [Created] (IGNITE-21065) Extend AuthenticationEvent with USER_CREATED and USER_CHANGED

Ivan Gagarkin created IGNITE-21065: -- Summary: Extend AuthenticationEvent with USER_CREATED and USER_CHANGED Key: IGNITE-21065 URL: https://issues.apache.org/jira/browse/IGNITE-21065 Project: Ignite

[jira] [Created] (IGNITE-21064) Refactor authentication naming and enum in Thin Client for clarity

Ivan Gagarkin created IGNITE-21064: -- Summary: Refactor authentication naming and enum in Thin Client for clarity Key: IGNITE-21064 URL: https://issues.apache.org/jira/browse/IGNITE-21064 Project: Ign

[jira] [Assigned] (IGNITE-20995) Add more integration tests for tx recovery on unstable topology

[ https://issues.apache.org/jira/browse/IGNITE-20995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin reassigned IGNITE-20995: Assignee:  Kirill Sizov > Add more integration tests for tx recovery on

[jira] [Updated] (IGNITE-21063) Cannot create 1000 tables

[ https://issues.apache.org/jira/browse/IGNITE-21063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Bessonov updated IGNITE-21063: --- Description: Fails with OOM after a while, managing to create about 500 tales locally. We n

[jira] [Assigned] (IGNITE-20918) Leases expire after a node has been restarted

[ https://issues.apache.org/jira/browse/IGNITE-20918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin reassigned IGNITE-20918: Assignee: Alexander Lapin (was: Vladislav Pyatkov) > Leases expire afte

[jira] [Assigned] (IGNITE-20993) Make the tables recover on the same assignments on different nodes

[ https://issues.apache.org/jira/browse/IGNITE-20993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin reassigned IGNITE-20993: Assignee: Denis Chudov > Make the tables recover on the same assignments

[jira] [Updated] (IGNITE-21063) Cannot create 1000 tables

[ https://issues.apache.org/jira/browse/IGNITE-21063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Bessonov updated IGNITE-21063: --- Description: Fails with OOM on TC. We need to research, why it happens. Is there a leak, or

[jira] [Assigned] (IGNITE-21014) Table creation revision for table descriptor

[ https://issues.apache.org/jira/browse/IGNITE-21014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mirza Aliev reassigned IGNITE-21014: Assignee: Mirza Aliev > Table creation revision for table descriptor > -

[jira] [Updated] (IGNITE-21014) Table creation revision for table descriptor

[ https://issues.apache.org/jira/browse/IGNITE-21014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-21014: - Epic Link: (was: IGNITE-19170) > Table creation revision for table descriptor

[jira] [Commented] (IGNITE-21059) We have upgraded our ignite instance from 2.7.6 to 2.14. Found long running cache operations

[ https://issues.apache.org/jira/browse/IGNITE-21059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795675#comment-17795675 ] Evgeny Stanilovsky commented on IGNITE-21059: - [~vipul.thakur] can you atta

[jira] [Updated] (IGNITE-21063) Cannot create 1000 tables

[ https://issues.apache.org/jira/browse/IGNITE-21063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Bessonov updated IGNITE-21063: --- Ignite Flags: (was: Docs Required,Release Notes Required) > Cannot create 1000 tables > -

[jira] [Assigned] (IGNITE-20745) TableManager.tableAsync(int tableId) is slowing down thin clients

[ https://issues.apache.org/jira/browse/IGNITE-20745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin reassigned IGNITE-20745: Assignee: Igor Sapego (was: Kirill Gusakov) > TableManager.tableAsync(i

[jira] [Updated] (IGNITE-21016) ItMixedQueriesTest.testIgniteSchemaAwaresAlterTableCommand is flaky

[ https://issues.apache.org/jira/browse/IGNITE-21016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Orlov updated IGNITE-21016: -- Ignite Flags: (was: Docs Required,Release Notes Required) > ItMixedQueriesTest.test

[jira] [Updated] (IGNITE-21016) ItMixedQueriesTest.testIgniteSchemaAwaresAlterTableCommand is flaky

[ https://issues.apache.org/jira/browse/IGNITE-21016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Orlov updated IGNITE-21016: -- Fix Version/s: 3.0.0-beta2 > ItMixedQueriesTest.testIgniteSchemaAwaresAlterTableComma

[jira] [Assigned] (IGNITE-20361) Implement the table storage description

[ https://issues.apache.org/jira/browse/IGNITE-20361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mirza Aliev reassigned IGNITE-20361: Assignee: Mirza Aliev > Implement the table storage description > --

[jira] [Created] (IGNITE-21063) Cannot create 1000 tables

Ivan Bessonov created IGNITE-21063: -- Summary: Cannot create 1000 tables Key: IGNITE-21063 URL: https://issues.apache.org/jira/browse/IGNITE-21063 Project: Ignite Issue Type: Bug

[jira] [Assigned] (IGNITE-21062) Safe time reordering in partitions

[ https://issues.apache.org/jira/browse/IGNITE-21062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Bessonov reassigned IGNITE-21062: -- Assignee: Ivan Bessonov > Safe time reordering in partitions > -

[jira] [Created] (IGNITE-21062) Safe time reordering in partitions

Ivan Bessonov created IGNITE-21062: -- Summary: Safe time reordering in partitions Key: IGNITE-21062 URL: https://issues.apache.org/jira/browse/IGNITE-21062 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-21061) Durable cleanup requires additional replication group command

Vladislav Pyatkov created IGNITE-21061: -- Summary: Durable cleanup requires additional replication group command Key: IGNITE-21061 URL: https://issues.apache.org/jira/browse/IGNITE-21061 Project:

[jira] [Assigned] (IGNITE-21060) Extract ClusterNodeResolver as a separate entity

[ https://issues.apache.org/jira/browse/IGNITE-21060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]  Kirill Sizov reassigned IGNITE-21060: -- Assignee:  Kirill Sizov > Extract ClusterNodeResolver as a separate entity > ---

[jira] [Created] (IGNITE-21060) Extract ClusterNodeResolver as a separate entity

 Kirill Sizov created IGNITE-21060: -- Summary: Extract ClusterNodeResolver as a separate entity Key: IGNITE-21060 URL: https://issues.apache.org/jira/browse/IGNITE-21060 Project: Ignite Issue

[jira] [Updated] (IGNITE-20909) Thin 3.0: Compute jobs should use server notification to signal completion to the client

[ https://issues.apache.org/jira/browse/IGNITE-20909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-20909: Ignite Flags: (was: Docs Required,Release Notes Required) > Thin 3.0: Compute jobs shou

[jira] [Commented] (IGNITE-20909) Thin 3.0: Compute jobs should use server notification to signal completion to the client

[ https://issues.apache.org/jira/browse/IGNITE-20909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795641#comment-17795641 ] Pavel Tupitsyn commented on IGNITE-20909: - Merged to main: 0f5434baf426f9c56fb1

[jira] [Resolved] (IGNITE-21056) Use thread local buffer for encrypted dump

[ https://issues.apache.org/jira/browse/IGNITE-21056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov resolved IGNITE-21056. -- Resolution: Fixed > Use thread local buffer for encrypted dump >

[jira] [Updated] (IGNITE-21056) Use thread local buffer for encrypted dump

[ https://issues.apache.org/jira/browse/IGNITE-21056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-21056: - Fix Version/s: 2.16 > Use thread local buffer for encrypted dump >

[jira] [Commented] (IGNITE-21056) Use thread local buffer for encrypted dump

[ https://issues.apache.org/jira/browse/IGNITE-21056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795636#comment-17795636 ] Ignite TC Bot commented on IGNITE-21056: {panel:title=Branch: [pull/11086/head]