[
https://issues.apache.org/jira/browse/IGNITE-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor reassigned IGNITE-1580:
Assignee: Igor
> CPP: Review Ignition interface.
> ---
>
>
[
https://issues.apache.org/jira/browse/IGNITE-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14936797#comment-14936797
]
Igor commented on IGNITE-1580:
--
1. Why threre is {{std::string}} used in one part of API (i.e. {{SqlQuery}}
[
https://issues.apache.org/jira/browse/IGNITE-1460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor reassigned IGNITE-1460:
Assignee: Igor
> CPP: Review all "const" usages on public API.
>
Igor created IGNITE-1586:
Summary: CPP: Add isValid() method to all proxy-like classes
Key: IGNITE-1586
URL: https://issues.apache.org/jira/browse/IGNITE-1586
Project: Ignite
Issue Type: Task
[
https://issues.apache.org/jira/browse/IGNITE-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-1586:
-
Component/s: interop
> CPP: Add isValid() method to all proxy-like classes
>
[
https://issues.apache.org/jira/browse/IGNITE-20615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor resolved IGNITE-20615.
---
Resolution: Not A Problem
Pyodbc tries to get metadata about non executed query - this feature is not yet
[
https://issues.apache.org/jira/browse/IGNITE-20625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-20625:
--
Description:
h3. Steps to reproduce:
# Connect to Ignite using ODBC driver (Python).
# Execute separate
[
https://issues.apache.org/jira/browse/IGNITE-20625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-20625:
--
Summary: SELECT MIN(column), MAX(column) by ODBC throws exception (was:
SELECT MIN(column), MAX(column) by
Igor created IGNITE-20625:
-
Summary: SELECT MIN(column), MAX(column) by ODBC throws exceptions
Key: IGNITE-20625
URL: https://issues.apache.org/jira/browse/IGNITE-20625
Project: Ignite
Issue Type:
Igor created IGNITE-20777:
-
Summary: Exception while init cluster due to missed `add-opens`
argument
Key: IGNITE-20777
URL: https://issues.apache.org/jira/browse/IGNITE-20777
Project: Ignite
Issue
[
https://issues.apache.org/jira/browse/IGNITE-20777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-20777:
--
Description:
*Steps to reproduce:*
# Start cluster with 2 nodes.
# Init cluster
*Expected result:*
Igor created IGNITE-20615:
-
Summary: SQL queries by ODBC throws exceptions
Key: IGNITE-20615
URL: https://issues.apache.org/jira/browse/IGNITE-20615
Project: Ignite
Issue Type: Bug
[
https://issues.apache.org/jira/browse/IGNITE-20615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-20615:
--
Labels: ignite-3 (was: )
> SQL queries by ODBC throws exceptions
> -
>
Igor created IGNITE-20716:
-
Summary: Partial data loss after node restart
Key: IGNITE-20716
URL: https://issues.apache.org/jira/browse/IGNITE-20716
Project: Ignite
Issue Type: Bug
[
https://issues.apache.org/jira/browse/IGNITE-20724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-20724:
--
Description:
*Steps to reproduce:*
Run the next sequence of separate queries one by one (via JDBC or ODBC)
Igor created IGNITE-20724:
-
Summary: Exception "Type conversion is not supported yet" after
"ALTER TABLE DROP COLUMN"
Key: IGNITE-20724
URL: https://issues.apache.org/jira/browse/IGNITE-20724
Project: Ignite
Igor created IGNITE-20731:
-
Summary: Exception "The primary replica has changed" on big amount
of rows
Key: IGNITE-20731
URL: https://issues.apache.org/jira/browse/IGNITE-20731
Project: Ignite
Igor created IGNITE-20286:
-
Summary: Information about REST port disappeared from logs
Key: IGNITE-20286
URL: https://issues.apache.org/jira/browse/IGNITE-20286
Project: Ignite
Issue Type: Bug
[
https://issues.apache.org/jira/browse/IGNITE-20286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-20286:
--
Description:
The information about taken REST port is disappeared from logs.
Previously the string was
[
https://issues.apache.org/jira/browse/IGNITE-20286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-20286:
--
Description:
The information about taken REST port is disappeared from logs.
Previously the string was
[
https://issues.apache.org/jira/browse/IGNITE-19247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17711287#comment-17711287
]
Igor edited comment on IGNITE-19247 at 4/20/23 1:54 PM:
I had the same
Igor created IGNITE-19275:
-
Summary: Creation of big amount of tables throws exception
Key: IGNITE-19275
URL: https://issues.apache.org/jira/browse/IGNITE-19275
Project: Ignite
Issue Type: Bug
[
https://issues.apache.org/jira/browse/IGNITE-19275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-19275:
--
Description:
h1. *Steps:*
# Sart 2 nodes
# Init cluster
# Connect to cluster via jdbc
# Create table
[
https://issues.apache.org/jira/browse/IGNITE-19247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-19247:
--
Attachment: node_0.log.zip
node_1.log.zip
test.log
> Replication is timed
[
https://issues.apache.org/jira/browse/IGNITE-19247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17711287#comment-17711287
]
Igor commented on IGNITE-19247:
---
I had the same exception when tried to insert 1M rows into table.
Igor created IGNITE-19727:
-
Summary: Server nodes cannot find each other and log
NullPointerException
Key: IGNITE-19727
URL: https://issues.apache.org/jira/browse/IGNITE-19727
Project: Ignite
Issue
[
https://issues.apache.org/jira/browse/IGNITE-19456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-19456:
--
Description:
h1. Steps to reproduce:
1. Create table.
{code:java}
CREATE TABLE index_test_table_5(id INT
[
https://issues.apache.org/jira/browse/IGNITE-19456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-19456:
--
Summary: Dropping one column of the composite index makes impossible
queries to other columns in the index
[
https://issues.apache.org/jira/browse/IGNITE-19456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-19456:
--
Description:
h1. Steps to reproduce:
1. Create table.
{code:java}
CREATE TABLE index_test_table_5(id INT
Igor created IGNITE-19456:
-
Summary: Drop one column of composite index makes impossible
queries to other columns in the index
Key: IGNITE-19456
URL: https://issues.apache.org/jira/browse/IGNITE-19456
[
https://issues.apache.org/jira/browse/IGNITE-19247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17723198#comment-17723198
]
Igor commented on IGNITE-19247:
---
Retry on Ignite 3 main branch commit
Igor created IGNITE-19488:
-
Summary: RemoteFragmentExecutionException when inserting more than
30 000 rows into one table
Key: IGNITE-19488
URL: https://issues.apache.org/jira/browse/IGNITE-19488
Project:
[
https://issues.apache.org/jira/browse/IGNITE-19488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-19488:
--
Priority: Critical (was: Major)
> RemoteFragmentExecutionException when inserting more than 30 000 rows
[
https://issues.apache.org/jira/browse/IGNITE-19247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17723215#comment-17723215
]
Igor commented on IGNITE-19247:
---
[~xtern] there is no such words in logs. Full bug description and logs
[
https://issues.apache.org/jira/browse/IGNITE-19488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-19488:
--
Description:
h1. Steps to reproduce
Ignite 3 main branch commit 45380a6c802203dab0d72bd1eb9fb202b2a345b0
#
[
https://issues.apache.org/jira/browse/IGNITE-19488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-19488:
--
Description:
h1. Steps to reproduce
# Create table with 5 columns
# Insert into table rows by batches 1000
[
https://issues.apache.org/jira/browse/IGNITE-19456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-19456:
--
Description:
h1. Steps to reproduce:
1. Create table.
{code:java}
CREATE TABLE index_test_table_5(id INT
[
https://issues.apache.org/jira/browse/IGNITE-19461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-19461:
--
Summary: The composite index is used when single column index expected to
be used (was: The composite index
[
https://issues.apache.org/jira/browse/IGNITE-19461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-19461:
--
Description:
h1. Steps to reproduce:
1. Create table.
{code:java}
CREATE TABLE index_test_table_5(id INT
Igor created IGNITE-19461:
-
Summary: The composite index used when single column index
expected to be used
Key: IGNITE-19461
URL: https://issues.apache.org/jira/browse/IGNITE-19461
Project: Ignite
[
https://issues.apache.org/jira/browse/IGNITE-19488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-19488:
--
Attachment: logs_with_ignored_erorr.zip
> RemoteFragmentExecutionException when inserting more than 30 000
[
https://issues.apache.org/jira/browse/IGNITE-19488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17723807#comment-17723807
]
Igor edited comment on IGNITE-19488 at 5/18/23 7:01 AM:
If errors in `SELECT
[
https://issues.apache.org/jira/browse/IGNITE-19488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17723807#comment-17723807
]
Igor commented on IGNITE-19488:
---
If errors in `SELECT count(*)` are ignored then it is possible to insert
[
https://issues.apache.org/jira/browse/IGNITE-19488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17723474#comment-17723474
]
Igor commented on IGNITE-19488:
---
[~xtern] there is the code to reproduce the error
[
https://issues.apache.org/jira/browse/IGNITE-21451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-21451:
--
Description:
h3. Steps to reproduce:
Run the next queries in cycle with 50 repeats in single connection:
Igor created IGNITE-21451:
-
Summary: RocksDB: repeat of create table and drop column leads to
freeze of client
Key: IGNITE-21451
URL: https://issues.apache.org/jira/browse/IGNITE-21451
Project: Ignite
Igor created IGNITE-21577:
-
Summary: JDBC throws exception when multiple endpoints are used
Key: IGNITE-21577
URL: https://issues.apache.org/jira/browse/IGNITE-21577
Project: Ignite
Issue Type:
[
https://issues.apache.org/jira/browse/IGNITE-21577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-21577:
--
Description:
*Steps to reproduce:*
1. Start cluster of 2 nodes.
2. Execute the code:
{code:java}
try
[
https://issues.apache.org/jira/browse/IGNITE-21577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor closed IGNITE-21577.
-
Ignite Flags: (was: Docs Required,Release Notes Required)
> JDBC throws exception when multiple endpoints
[
https://issues.apache.org/jira/browse/IGNITE-21577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor resolved IGNITE-21577.
---
Resolution: Won't Fix
The functionality is not supported.
> JDBC throws exception when multiple endpoints
[
https://issues.apache.org/jira/browse/IGNITE-21472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-21472:
--
Description:
h3. Steps to reproduce:
Run the next code:
{code:java}
try (Session session =
Igor created IGNITE-21472:
-
Summary: Exception: Invalid length for a tuple element on prepared
statement
Key: IGNITE-21472
URL: https://issues.apache.org/jira/browse/IGNITE-21472
Project: Ignite
Igor created IGNITE-21489:
-
Summary: Add running script files to .jar file
Key: IGNITE-21489
URL: https://issues.apache.org/jira/browse/IGNITE-21489
Project: Ignite
Issue Type: Improvement
Igor created IGNITE-21088:
-
Summary: Impossible to restart node with json config
Key: IGNITE-21088
URL: https://issues.apache.org/jira/browse/IGNITE-21088
Project: Ignite
Issue Type: Bug
Igor created IGNITE-21200:
-
Summary: IgniteRunner start fails in Windows via git-bash
Key: IGNITE-21200
URL: https://issues.apache.org/jira/browse/IGNITE-21200
Project: Ignite
Issue Type: Bug
[
https://issues.apache.org/jira/browse/IGNITE-21200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-21200:
--
Labels: ignite-3 windows (was: ignite-3)
> IgniteRunner start fails in Windows via git-bash
>
Igor created IGNITE-20971:
-
Summary: The Ignite process quietly tear down while creating a lot
of tables
Key: IGNITE-20971
URL: https://issues.apache.org/jira/browse/IGNITE-20971
Project: Ignite
[
https://issues.apache.org/jira/browse/IGNITE-20971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-20971:
--
Description:
Creating 1000 tables with 5 column each.
Expected:
1000 tables are created.
Actual:
After
[
https://issues.apache.org/jira/browse/IGNITE-20971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-20971:
--
Description:
Creating 1000 tables with 5 column each.
*Expected:*
1000 tables are created.
*Actual:*
[
https://issues.apache.org/jira/browse/IGNITE-20971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-20971:
--
Summary: The Ignite process huge memory overhead for tables creation (was:
The Ignite process quietly tear
[
https://issues.apache.org/jira/browse/IGNITE-20971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-20971:
--
Description:
*Steps to reproduce*
# Start process with `-Xms4096m -Xmx4096m`
# Create tables with 5
[
https://issues.apache.org/jira/browse/IGNITE-20971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-20971:
--
Attachment: gc.20231128_132812_386649.log
> The Ignite process huge memory overhead for tables creation
>
Igor created IGNITE-22088:
-
Summary: retryPolicy of IgniteClient doesn't work on transaction
fail
Key: IGNITE-22088
URL: https://issues.apache.org/jira/browse/IGNITE-22088
Project: Ignite
Issue
[
https://issues.apache.org/jira/browse/IGNITE-22088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-22088:
--
Description:
*Details:*
IgniteClient do not run retry with set retryPolicy on transaction lock. The
default
[
https://issues.apache.org/jira/browse/IGNITE-22117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor closed IGNITE-22117.
-
Ignite Flags: (was: Docs Required,Release Notes Required)
> Node restart fails due to error: marshaller
[
https://issues.apache.org/jira/browse/IGNITE-22117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-22117:
--
Labels: (was: ignite)
> Node restart fails due to error: marshaller mappings storage is broken
>
[
https://issues.apache.org/jira/browse/IGNITE-22117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-22117:
--
Component/s: (was: persistence)
Affects Version/s: (was: 2.9.1)
> Node restart fails due
[
https://issues.apache.org/jira/browse/IGNITE-22117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor resolved IGNITE-22117.
---
Resolution: Abandoned
> Node restart fails due to error: marshaller mappings storage is broken
>
Igor created IGNITE-22117:
-
Summary: Node restart fails due to error: marshaller mappings
storage is broken
Key: IGNITE-22117
URL: https://issues.apache.org/jira/browse/IGNITE-22117
Project: Ignite
[
https://issues.apache.org/jira/browse/IGNITE-22139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-22139:
--
Summary: JDBC request to degraded cluster freezes (was: JDBC request to
degraded cluster stucks)
> JDBC
[
https://issues.apache.org/jira/browse/IGNITE-22139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-22139:
--
Description:
*Steps to reproduce:*
# Create zone with replication equals to amount of nodes (2 or 3
[
https://issues.apache.org/jira/browse/IGNITE-22139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-22139:
--
Summary: JDBC request to degraded cluster freezes forever (was: JDBC
request to degraded cluster freezes)
[
https://issues.apache.org/jira/browse/IGNITE-22139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-22139:
--
Summary: JDBC request to degraded cluster stucks (was: JDBC request to
degraded cluster stuck)
> JDBC
Igor created IGNITE-22139:
-
Summary: JDBC request to degraded cluster stuck
Key: IGNITE-22139
URL: https://issues.apache.org/jira/browse/IGNITE-22139
Project: Ignite
Issue Type: Bug
[
https://issues.apache.org/jira/browse/IGNITE-22088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor resolved IGNITE-22088.
---
Resolution: Not A Bug
>From the doc:
_Sets the retry policy. When a request fails due to a connection
Igor created IGNITE-22187:
-
Summary: Cluster of 2 or 3 nodes doesn't work if one node is down
Key: IGNITE-22187
URL: https://issues.apache.org/jira/browse/IGNITE-22187
Project: Ignite
Issue Type:
[
https://issues.apache.org/jira/browse/IGNITE-22187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-22187:
--
Description:
*Steps to reproduce:*
# Create zone with replication equals to amount of nodes (2 or 3
[
https://issues.apache.org/jira/browse/IGNITE-22139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor resolved IGNITE-22139.
---
Resolution: Cannot Reproduce
> JDBC request to degraded cluster freezes forever
>
Igor created IGNITE-22248:
-
Summary: Creation of new tables in 1 node cluster stuck after 850+
tables
Key: IGNITE-22248
URL: https://issues.apache.org/jira/browse/IGNITE-22248
Project: Ignite
Issue
[
https://issues.apache.org/jira/browse/IGNITE-22248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-22248:
--
Attachment: image-2024-05-15-13-22-40-059.png
> Creation of new tables in 1 node cluster stuck after 850+
[
https://issues.apache.org/jira/browse/IGNITE-22248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-22248:
--
Description:
*Steps to reproduce:*
# Single node cluster with arguments "-Xms4096m", "-Xmx4096m"
# Create
[
https://issues.apache.org/jira/browse/IGNITE-22088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841970#comment-17841970
]
Igor commented on IGNITE-22088:
---
[~isapego] sorry, misread the doc. Then it is not the issue.
>
Igor created IGNITE-22209:
-
Summary: Creation of new tables in multinode cluster stuck after
150+ tables
Key: IGNITE-22209
URL: https://issues.apache.org/jira/browse/IGNITE-22209
Project: Ignite
[
https://issues.apache.org/jira/browse/IGNITE-22137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17845871#comment-17845871
]
Igor commented on IGNITE-22137:
---
[~apolovtcev]
The file
[
https://issues.apache.org/jira/browse/IGNITE-21725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-21725:
--
Summary: The exception "Primary replica has expired" on creation of 1000
tables (was: The exception
Igor created IGNITE-21725:
-
Summary: The exception "Primary replica has expired" on a lot
creation of 1000 tables
Key: IGNITE-21725
URL: https://issues.apache.org/jira/browse/IGNITE-21725
Project: Ignite
[ https://issues.apache.org/jira/browse/IGNITE-21639 ]
Igor deleted comment on IGNITE-21639:
---
was (Author: JIRAUSER299771):
The run with logs
[
https://issues.apache.org/jira/browse/IGNITE-22009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-22009:
--
Component/s: jdbc
> aimem: repeat of create table and drop column leads to freeze of client
>
[
https://issues.apache.org/jira/browse/IGNITE-22009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-22009:
--
Description:
h3. Steps to reproduce:
Run the next queries using *JDBC* in cycle with 10 repeats in single
[
https://issues.apache.org/jira/browse/IGNITE-22009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-22009:
--
Description:
h3. Steps to reproduce:
Run the next queries using *JDBC* in cycle with 50 repeats in single
Igor created IGNITE-22009:
-
Summary: aimem: repeat of create table and drop column leads to
freeze of client
Key: IGNITE-22009
URL: https://issues.apache.org/jira/browse/IGNITE-22009
Project: Ignite
[
https://issues.apache.org/jira/browse/IGNITE-22009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-22009:
--
Environment: 1 node cluster running on remote machine or locally (was: 1
node cluster running on remote
[
https://issues.apache.org/jira/browse/IGNITE-22009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-22009:
--
Environment: 1 node cluster running on remote machine (was: 1 node cluster
running locally)
> aimem:
[
https://issues.apache.org/jira/browse/IGNITE-22009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-22009:
--
Environment: 2 nodes cluster running on remote machine or locally (was: 1
node cluster running on remote
Igor created IGNITE-22011:
-
Summary: aimem: repeat of create table and drop column leads to
Failed to get the primary replica
Key: IGNITE-22011
URL: https://issues.apache.org/jira/browse/IGNITE-22011
[
https://issues.apache.org/jira/browse/IGNITE-22011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-22011:
--
Environment: 2 nodes cluster running on remote machine or locally
> aimem: repeat of create table and drop
[
https://issues.apache.org/jira/browse/IGNITE-22011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-22011:
--
Description:
*Comment:*
This is the flaky issue and can happen on any operation to table with aimem
[
https://issues.apache.org/jira/browse/IGNITE-22009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-22009:
--
Description:
h3. Steps to reproduce:
Run the next queries using *JDBC* in cycle with 50 repeats in single
[
https://issues.apache.org/jira/browse/IGNITE-21894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-21894:
--
Description:
*Steps to reproduce:*
1. Start 2 nodes cluster.
2. Open JDBC connection, start transaction
Igor created IGNITE-21894:
-
Summary: Undescriptive error when restart cluster during open JDBC
transaction
Key: IGNITE-21894
URL: https://issues.apache.org/jira/browse/IGNITE-21894
Project: Ignite
1 - 100 of 134 matches
Mail list logo
