[jira] [Commented] (IGNITE-20534) Transactions. It is possible to call enlist on a rollbacked transaction and cause a resource leak

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

[jira] [Updated] (IGNITE-20534) Transactions. It is possible to call enlist on a rollbacked transaction and cause a resource leak

[ https://issues.apache.org/jira/browse/IGNITE-20534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-20534: --- Summary: Transactions. It is possible to call enlist on a rollbacked transaction

[jira] [Created] (IGNITE-20756) Partially unresolved OOM issue in thin client protocol handler caused by malicious or garbage data.

timus1 created IGNITE-20756: --- Summary: Partially unresolved OOM issue in thin client protocol handler caused by malicious or garbage data. Key: IGNITE-20756 URL: https://issues.apache.org/jira/browse/IGNITE-20756

[jira] [Assigned] (IGNITE-20455) Sql. Test Framework. Add System View support.

[ https://issues.apache.org/jira/browse/IGNITE-20455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Zhuravkov reassigned IGNITE-20455: - Assignee: Maksim Zhuravkov > Sql. Test Framework. Add System View support. >

[jira] [Commented] (IGNITE-20740) SocketChannel May leak when connection can not be established

[ https://issues.apache.org/jira/browse/IGNITE-20740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17780410#comment-17780410 ] Ignite TC Bot commented on IGNITE-20740: {panel:title=Branch: [pull/11016/head] Base: [master]

[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: Kirill Gusakov > TableManager.tableAsync(int tableId) is

[jira] [Updated] (IGNITE-20753) Add additional information on the recoverable exception

[ https://issues.apache.org/jira/browse/IGNITE-20753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Chudov updated IGNITE-20753: -- Description: *Motivation* This warning has happened due to the recoverable exception

[jira] [Updated] (IGNITE-20617) SQL: ~20x performance degradation in SELECTS (2 nodes VS 1 node)

[ https://issues.apache.org/jira/browse/IGNITE-20617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Artiukhov updated IGNITE-20617: Attachment: 6b6f0c-select-logs.zip.zip > SQL: ~20x performance degradation in SELECTS (2

[jira] [Commented] (IGNITE-20617) SQL: ~20x performance degradation in SELECTS (2 nodes VS 1 node)

[ https://issues.apache.org/jira/browse/IGNITE-20617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17780404#comment-17780404 ] Ivan Artiukhov commented on IGNITE-20617: - AI3, rev. 6b6f0cb6109d7906a980a31522a1b9c36f88e43a

[jira] [Updated] (IGNITE-20617) SQL: ~20x performance degradation in SELECTS (2 nodes VS 1 node)

[ https://issues.apache.org/jira/browse/IGNITE-20617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Artiukhov updated IGNITE-20617: Attachment: 6b6f0c-select-2srv.png > SQL: ~20x performance degradation in SELECTS (2

[jira] [Updated] (IGNITE-20678) Adding ReplicaMeta#getLeaseholderId to avoid errors during node recovery

[ https://issues.apache.org/jira/browse/IGNITE-20678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Tkalenko updated IGNITE-20678: - Description: After discussions and code analysis, I found out that this problem needs

[jira] [Updated] (IGNITE-19908) Sql. EXPLAIN should return plan that actually being used for execution

[ https://issues.apache.org/jira/browse/IGNITE-19908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Orlov updated IGNITE-19908: -- Fix Version/s: 3.0.0-beta2 > Sql. EXPLAIN should return plan that actually being

[jira] [Created] (IGNITE-20755) Do not use join() in ExecutionServiceImpl#stop()

Roman Puchkovskiy created IGNITE-20755: -- Summary: Do not use join() in ExecutionServiceImpl#stop() Key: IGNITE-20755 URL: https://issues.apache.org/jira/browse/IGNITE-20755 Project: Ignite

[jira] [Updated] (IGNITE-20705) Switch user context when reconnecting

[ https://issues.apache.org/jira/browse/IGNITE-20705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Pakhnushev updated IGNITE-20705: -- Summary: Switch user context when reconnecting (was: CLI does not switch user

[jira] [Updated] (IGNITE-20160) NullPointerException in FSMCallerImpl.doCommitted

[ https://issues.apache.org/jira/browse/IGNITE-20160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]  Kirill Sizov updated IGNITE-20160: --- Description: {code:java} java.lang.NullPointerException at

[jira] [Updated] (IGNITE-20160) NullPointerException in FSMCallerImpl.doCommitted

[ https://issues.apache.org/jira/browse/IGNITE-20160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]  Kirill Sizov updated IGNITE-20160: --- Description: {code:java} java.lang.NullPointerException at

[jira] [Updated] (IGNITE-20160) NullPointerException in FSMCallerImpl.doCommitted

[ https://issues.apache.org/jira/browse/IGNITE-20160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]  Kirill Sizov updated IGNITE-20160: --- Description: {code:java} java.lang.NullPointerException at

[jira] [Commented] (IGNITE-20690) Ignite client nodes are getting terminated when we stop the ignite server.

[ https://issues.apache.org/jira/browse/IGNITE-20690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17780316#comment-17780316 ] Vaibhav Shrivastava commented on IGNITE-20690: -- Hello Team Is there any update on this? >

[jira] [Commented] (IGNITE-20724) Exception "Type conversion is not supported yet" after "ALTER TABLE DROP COLUMN"

[ https://issues.apache.org/jira/browse/IGNITE-20724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17780306#comment-17780306 ] Evgeny Stanilovsky commented on IGNITE-20724: - [~xtern]  looks good ! > Exception "Type

[jira] [Assigned] (IGNITE-19453) Serialize commands before sending them in ActionRequest

[ https://issues.apache.org/jira/browse/IGNITE-19453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Bessonov reassigned IGNITE-19453: -- Assignee: Ivan Bessonov > Serialize commands before sending them in ActionRequest >

[jira] [Updated] (IGNITE-20678) Adding ReplicaMeta#getLeaseholderId to avoid errors during node recovery

[ https://issues.apache.org/jira/browse/IGNITE-20678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Tkalenko updated IGNITE-20678: - Summary: Adding ReplicaMeta#getLeaseholderId to avoid errors during node recovery

[jira] [Updated] (IGNITE-20678) Find a way to get a MvTableStorage on recovery the index build

[ https://issues.apache.org/jira/browse/IGNITE-20678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Tkalenko updated IGNITE-20678: - Description: After discussions and code analysis, I found out that this problem needs

[jira] [Updated] (IGNITE-20753) Add additional information on the recoverable exception

[ https://issues.apache.org/jira/browse/IGNITE-20753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Chudov updated IGNITE-20753: -- Description: *Motivation* This warning has happened due to the recoverable exception

[jira] [Created] (IGNITE-20754) Fix log prefix truncation in logit storage

Ivan Bessonov created IGNITE-20754: -- Summary: Fix log prefix truncation in logit storage Key: IGNITE-20754 URL: https://issues.apache.org/jira/browse/IGNITE-20754 Project: Ignite Issue

[jira] [Updated] (IGNITE-20753) Add additional information on the recoverable exception

[ https://issues.apache.org/jira/browse/IGNITE-20753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-20753: --- Description: This warning has happened due to the recoverable exception (timeout,

[jira] [Created] (IGNITE-20753) Add additional information on the recoverable exception

Vladislav Pyatkov created IGNITE-20753: -- Summary: Add additional information on the recoverable exception Key: IGNITE-20753 URL: https://issues.apache.org/jira/browse/IGNITE-20753 Project: Ignite

[jira] [Updated] (IGNITE-20609) Move last commit timestamp into BinaryRowMessage

[ https://issues.apache.org/jira/browse/IGNITE-20609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-20609: --- Reviewer: Kirill Sizov > Move last commit timestamp into BinaryRowMessage >

[jira] [Updated] (IGNITE-20534) Transactions. It is possible to call enlist on a rollbacked transaction and cause a resource leak.

[ https://issues.apache.org/jira/browse/IGNITE-20534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov updated IGNITE-20534: --- Reviewer: Denis Chudov > Transactions. It is possible to call enlist on a

[jira] [Updated] (IGNITE-20705) CLI does not switch user context when connect command executed with different credentials

[ https://issues.apache.org/jira/browse/IGNITE-20705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Pakhnushev updated IGNITE-20705: -- Description: h3. Description: When a user connects using the {{connect}} command in

[jira] [Assigned] (IGNITE-20705) CLI does not switch user context when connect command executed with different credentials

[ https://issues.apache.org/jira/browse/IGNITE-20705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Pakhnushev reassigned IGNITE-20705: - Assignee: Vadim Pakhnushev > CLI does not switch user context when connect