[
https://issues.apache.org/jira/browse/IGNITE-22376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-22376:
--
Component/s: rest
(was: jdbc)
> RestAPI get logical topology freeze if 1 node was
[
https://issues.apache.org/jira/browse/IGNITE-22187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-22187:
--
Component/s: rest
> Cluster of 2 or 3 nodes doesn't work if one node is down
>
[
https://issues.apache.org/jira/browse/IGNITE-22187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-22187:
--
Affects Version/s: 3.0.0-beta2
> Cluster of 2 or 3 nodes doesn't work if one node is down
>
[
https://issues.apache.org/jira/browse/IGNITE-22376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-22376:
--
Affects Version/s: 3.0.0-beta2
> RestAPI get logical topology freeze if 1 node was replaced in 3 nodes
[
https://issues.apache.org/jira/browse/IGNITE-22376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-22376:
--
Environment: The 3 nodes cluster running locally. (was: The 2 or 3 nodes
cluster running locally.)
>
[
https://issues.apache.org/jira/browse/IGNITE-22376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-22376:
--
Description:
*Steps to reproduce:*
# Create zone with replication equals to amount of nodes (2 or 3
[
https://issues.apache.org/jira/browse/IGNITE-22376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-22376:
--
Summary: RestAPI get logical topology freeze if 1 node was replaced in 3
nodes cluster (was: RestAPI get
Igor created IGNITE-22376:
-
Summary: RestAPI get logical topology freeze if 1 node was replace
in 3 nodes cluster
Key: IGNITE-22376
URL: https://issues.apache.org/jira/browse/IGNITE-22376
Project: Ignite
[
https://issues.apache.org/jira/browse/IGNITE-22348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-22348:
--
Description:
*Steps to reproduce:*
# Create a cluster with 2 or 3 nodes.
# Connect via JDBC.
# Create 5
[
https://issues.apache.org/jira/browse/IGNITE-22348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-22348:
--
Description:
*Steps to reproduce:*
# Create a cluster with 2 or 3 nodes.
# Connect via JDBC.
# Create 5
[
https://issues.apache.org/jira/browse/IGNITE-22348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-22348:
--
Description:
*Steps to reproduce:*
# Create a cluster with 2 or 3 nodes.
# Connect via JDBC.
# Create 5
[
https://issues.apache.org/jira/browse/IGNITE-22348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-22348:
--
Description:
*Steps to reproduce:*
# Create a cluster with 2 or 3 nodes.
# Connect via JDBC.
# Create 5
Igor created IGNITE-22348:
-
Summary: Storage aimem throws 'Replication is timed out' on batch
insert
Key: IGNITE-22348
URL: https://issues.apache.org/jira/browse/IGNITE-22348
Project: Ignite
Issue
[
https://issues.apache.org/jira/browse/IGNITE-22331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-22331:
--
Description:
*Steps to reproduce:*
1. Start cluster with 1 node with JVM options: "-Xms4096m -Xmx4096m"
2.
Igor created IGNITE-22331:
-
Summary: Storage aimem throws "Failed to commit the transaction."
on creation of 1000 tables
Key: IGNITE-22331
URL: https://issues.apache.org/jira/browse/IGNITE-22331
Project:
[
https://issues.apache.org/jira/browse/IGNITE-22327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-22327:
--
Description:
*Steps to reproduce:*
# Start cluster of 3 nodes on 3 hosts.
# Create 10 tables and insert 10
[
https://issues.apache.org/jira/browse/IGNITE-22327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-22327:
--
Description:
*Steps to reproduce:*
# Start cluster of 3 nodes on 3 hosts.
# Create 10 tables and insert 10
[
https://issues.apache.org/jira/browse/IGNITE-22327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-22327:
--
Environment: 3 nodes (with arguments "-Xms4096m", "-Xmx4096m" ) on *3 host*
(was: 2 nodes (with arguments
[
https://issues.apache.org/jira/browse/IGNITE-22327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-22327:
--
Environment: 3 nodes (with arguments "-Xms4096m", "-Xmx4096m" ) on *3
hosts* (was: 3 nodes (with arguments
Igor created IGNITE-22327:
-
Summary: Error "StateMachine meet critical error" on restart
Key: IGNITE-22327
URL: https://issues.apache.org/jira/browse/IGNITE-22327
Project: Ignite
Issue Type: Bug
[
https://issues.apache.org/jira/browse/IGNITE-22324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-22324:
--
Description:
*Steps to reproduce:*
1. Start cluster with 1 node with JVM options: "-Xms4096m -Xmx4096m"
2.
Igor created IGNITE-22324:
-
Summary: The exception "The primary replica has changed" on
creation of 1000 tables
Key: IGNITE-22324
URL: https://issues.apache.org/jira/browse/IGNITE-22324
Project: Ignite
[
https://issues.apache.org/jira/browse/IGNITE-22324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-22324:
--
Affects Version/s: 3.0.0-beta2
(was: 3.0.0-beta1)
> The exception "The primary
[
https://issues.apache.org/jira/browse/IGNITE-22280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-22280:
--
Attachment: image-2024-05-17-18-06-23-594.png
> Error "A critical thread is blocked" on restart
>
[
https://issues.apache.org/jira/browse/IGNITE-22280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-22280:
--
Description:
*Steps to reproduce:*
# Start cluster of 2 nodes on single host.
# Create 5 tables and insert
[
https://issues.apache.org/jira/browse/IGNITE-22280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-22280:
--
Attachment: image-2024-05-17-18-06-04-081.png
> Error "A critical thread is blocked" on restart
>
[
https://issues.apache.org/jira/browse/IGNITE-22280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-22280:
--
Description:
*Steps to reproduce:*
# Start cluster of 2 nodes on single host.
# Create 5 tables and insert
Igor created IGNITE-22280:
-
Summary: Error "A critical thread is blocked" on restart
Key: IGNITE-22280
URL: https://issues.apache.org/jira/browse/IGNITE-22280
Project: Ignite
Issue Type: Bug
[
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-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+
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-22137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17845871#comment-17845871
]
Igor commented on IGNITE-22137:
---
[~apolovtcev]
The file
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-22139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor resolved IGNITE-22139.
---
Resolution: Cannot Reproduce
> JDBC request to degraded cluster freezes forever
>
[
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
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-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
[
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.
>
[
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 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 resolved IGNITE-22117.
---
Resolution: Abandoned
> 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 closed IGNITE-22117.
-
Ignite Flags: (was: Docs Required,Release Notes Required)
> Node restart fails due to error: marshaller
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-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
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-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-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-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-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-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
[
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:
--
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: 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:
--
Component/s: jdbc
> aimem: repeat of create table and drop column leads to freeze of client
>
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-21894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-21894:
--
Summary: Undescriptive error when restart cluster node during open JDBC
transaction (was: Undescriptive
[
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
[
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
[ 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-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-21663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-21663:
--
Description:
*Steps to reproduce:*
# Start cluster with 2 nodes running locally.
# Make connection like
Igor created IGNITE-21663:
-
Summary: Cluster load balancing when 1 node is killed doesn't work
Key: IGNITE-21663
URL: https://issues.apache.org/jira/browse/IGNITE-21663
Project: Ignite
Issue Type:
[
https://issues.apache.org/jira/browse/IGNITE-21639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17822465#comment-17822465
]
Igor commented on IGNITE-21639:
---
The run with logs
Igor created IGNITE-21639:
-
Summary: Server after kill does not start and stuck on election
Key: IGNITE-21639
URL: https://issues.apache.org/jira/browse/IGNITE-21639
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 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-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
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:
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
[
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
[
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
[
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-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
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
[
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
>
[
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:
--
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:
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:
--
Description:
Creating 1000 tables with 5 column each.
Expected:
1000 tables are created.
Actual:
After
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-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-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
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
[
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-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-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
[
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
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:
[
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
1 - 100 of 134 matches
Mail list logo
