[jira] [Updated] (IGNITE-16882) Enlist txnState into single parition only
[ https://issues.apache.org/jira/browse/IGNITE-16882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin updated IGNITE-16882: - Reviewer: Sergey Uttsel > Enlist txnState into single parition only > - > > Key: IGNITE-16882 > URL: https://issues.apache.org/jira/browse/IGNITE-16882 > Project: Ignite > Issue Type: Improvement >Reporter: Alexander Lapin >Assignee: Alexander Lapin >Priority: Major > Labels: ignite-3, transaction3_rw > > Currenlly txState(PENDING|ABORTED|COMMITED) is updated within all enlisted > partitions which is not an atomic solution. According to new tx design it's > required to replicate tx state with single partition only. > As a prerequisite persisted replicated TxnStateStore should be introduced > https://issues.apache.org/jira/browse/IGNITE-15931 > Such introduction will allow to rework existing tx implementaiton in order to > store txState only within single partition. > instead of using > {code:java} > partId = abs(txId.hashCode() % partCnt) {code} > we might use any other idempotent funtion, e.g. first partition of first > enlisted key. > Tx.Phase1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-16040) Calcite. Unable to plan query with several correlated sub-queries in select list
[ https://issues.apache.org/jira/browse/IGNITE-16040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgeny Stanilovsky updated IGNITE-16040: Ignite Flags: (was: Docs Required,Release Notes Required) > Calcite. Unable to plan query with several correlated sub-queries in select > list > > > Key: IGNITE-16040 > URL: https://issues.apache.org/jira/browse/IGNITE-16040 > Project: Ignite > Issue Type: Bug > Components: sql >Reporter: Konstantin Orlov >Assignee: Evgeny Stanilovsky >Priority: Major > Labels: calcite, calcite2-required, calcite3-required > Time Spent: 20m > Remaining Estimate: 0h > > Currently the query like below can't be planned by calcite-based sql engine: > {code:java} > SELECT a+b*2, >(a+b+c+d+e)/5, >(SELECT count(*) FROM t1 AS x WHERE x.c>t1.c AND x.d(SELECT count(*) FROM t1 AS x WHERE x.babs(b-c), >a-b > FROM t1 > WHERE EXISTS(SELECT 1 FROM t1 AS x WHERE x.bAND c>d > ORDER BY 6,5,4,1,3,2 > {code} > Need to figure it out how to fix this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-17587) The "io.datastorage.StorageSize" metric shows incorrect values in case of multiple persistence dataregions
[ https://issues.apache.org/jira/browse/IGNITE-17587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17597963#comment-17597963 ] Pavel Pereslegin commented on IGNITE-17587: --- [~NSAmelchev], looks good, let's merge! > The "io.datastorage.StorageSize" metric shows incorrect values in case of > multiple persistence dataregions > -- > > Key: IGNITE-17587 > URL: https://issues.apache.org/jira/browse/IGNITE-17587 > Project: Ignite > Issue Type: Bug >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Labels: ise > Time Spent: 40m > Remaining Estimate: 0h > > The metric was broken after IGNITE-13207: it sets the value of the last group > instead of the sum of all groups. See > {{DataStorageMetricsImpl#onStorageSizeChanged}} for details. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-17587) The "io.datastorage.StorageSize" metric shows incorrect values in case of multiple persistence dataregions
[ https://issues.apache.org/jira/browse/IGNITE-17587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17597942#comment-17597942 ] Amelchev Nikita commented on IGNITE-17587: -- [~xtern], Could you take a look, please? > The "io.datastorage.StorageSize" metric shows incorrect values in case of > multiple persistence dataregions > -- > > Key: IGNITE-17587 > URL: https://issues.apache.org/jira/browse/IGNITE-17587 > Project: Ignite > Issue Type: Bug >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > The metric was broken after IGNITE-13207: it sets the value of the last group > instead of the sum of all groups. See > {{DataStorageMetricsImpl#onStorageSizeChanged}} for details. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17587) The "io.datastorage.StorageSize" metric shows incorrect values in case of multiple persistence dataregions
[ https://issues.apache.org/jira/browse/IGNITE-17587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-17587: - Labels: ise (was: ) > The "io.datastorage.StorageSize" metric shows incorrect values in case of > multiple persistence dataregions > -- > > Key: IGNITE-17587 > URL: https://issues.apache.org/jira/browse/IGNITE-17587 > Project: Ignite > Issue Type: Bug >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Labels: ise > Time Spent: 10m > Remaining Estimate: 0h > > The metric was broken after IGNITE-13207: it sets the value of the last group > instead of the sum of all groups. See > {{DataStorageMetricsImpl#onStorageSizeChanged}} for details. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17599) Calcite engine. Support LocalDate/LocalTime types
[ https://issues.apache.org/jira/browse/IGNITE-17599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Plekhanov updated IGNITE-17599: --- Summary: Calcite engine. Support LocalDate/LocalTime types (was: Calcite engine. Support LocalData/LocalTime types) > Calcite engine. Support LocalDate/LocalTime types > - > > Key: IGNITE-17599 > URL: https://issues.apache.org/jira/browse/IGNITE-17599 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksey Plekhanov >Priority: Major > > H2-based engine works with LocalData/LocalTime types as > java.sql.Data/java.sql.Time types. To check if value with LocalDate type can > be inserted to descriptor with type java.sql.Data some logic from > \{{IgniteH2Indexing.isConvertibleToColumnType}} is used. If Calcite engine > used without ignite-indexing this logic is unavailable. > We should: > # Provide an ability to work in Calcite-based engine with > LocalDate/LocalTime type in the same way as java.sql.Data/java.sql.Time types. > # Move \{{IgniteH2Indexing.isConvertibleToColumnType}} logic to the core > module (perhaps delegating this call from the core to the QueryEngine > instance) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-17599) Calcite engine. Support LocalData/LocalTime types
Aleksey Plekhanov created IGNITE-17599: -- Summary: Calcite engine. Support LocalData/LocalTime types Key: IGNITE-17599 URL: https://issues.apache.org/jira/browse/IGNITE-17599 Project: Ignite Issue Type: Improvement Reporter: Aleksey Plekhanov H2-based engine works with LocalData/LocalTime types as java.sql.Data/java.sql.Time types. To check if value with LocalDate type can be inserted to descriptor with type java.sql.Data some logic from \{{IgniteH2Indexing.isConvertibleToColumnType}} is used. If Calcite engine used without ignite-indexing this logic is unavailable. We should: # Provide an ability to work in Calcite-based engine with LocalDate/LocalTime type in the same way as java.sql.Data/java.sql.Time types. # Move \{{IgniteH2Indexing.isConvertibleToColumnType}} logic to the core module (perhaps delegating this call from the core to the QueryEngine instance) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-17598) Unbind some JDBC/ODBC metadata requests from the ignite-indexing module
Aleksey Plekhanov created IGNITE-17598: -- Summary: Unbind some JDBC/ODBC metadata requests from the ignite-indexing module Key: IGNITE-17598 URL: https://issues.apache.org/jira/browse/IGNITE-17598 Project: Ignite Issue Type: Improvement Reporter: Aleksey Plekhanov After IGNITE-15424 some JDBC/ODBC metadata requests still require indexing module (Methods {{IgniteH2Indexing.resultMetaData}} and \{{IgniteH2Indexing.parameterMetaData}} are used). If query engine used without ignite-indexing module such requests can fail. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17597) Calcite engine. Indexes for table can't be used after columns added or dropped
[ https://issues.apache.org/jira/browse/IGNITE-17597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Plekhanov updated IGNITE-17597: --- Labels: calcite calcite2-required calcite3-required (was: ) > Calcite engine. Indexes for table can't be used after columns added or dropped > -- > > Key: IGNITE-17597 > URL: https://issues.apache.org/jira/browse/IGNITE-17597 > Project: Ignite > Issue Type: Bug >Reporter: Aleksey Plekhanov >Assignee: Aleksey Plekhanov >Priority: Blocker > Labels: calcite, calcite2-required, calcite3-required > Fix For: 2.14 > > > We recreate tables, but not copy indexes in schema change listener > (\{{SchemaHolderImpl#onColumnsAdded}}, \{{SchemaHolderImpl#onColumnsDropped}}) > Reproducer: > > {code:java} > public void testIndexAfterColumnsChange() { > sql("create table t(id int)"); > sql("create index t_idx on t(id)"); > for (int i = 0; i < 100; i++) > sql("insert into t values (?)", i); > assertQuery("select * from t where id = 0") > .matches(QueryChecker.containsIndexScan("PUBLIC", "T", "T_IDX")) > .check(); > sql("alter table t add column new_col int"); > assertQuery("select * from t where id = 0") > .matches(QueryChecker.containsIndexScan("PUBLIC", "T", "T_IDX")) > .check(); > } {code} > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-17597) Calcite engine. Indexes for table can't be used after columns added or dropped
Aleksey Plekhanov created IGNITE-17597: -- Summary: Calcite engine. Indexes for table can't be used after columns added or dropped Key: IGNITE-17597 URL: https://issues.apache.org/jira/browse/IGNITE-17597 Project: Ignite Issue Type: Bug Reporter: Aleksey Plekhanov Assignee: Aleksey Plekhanov Fix For: 2.14 We recreate tables, but not copy indexes in schema change listener (\{{SchemaHolderImpl#onColumnsAdded}}, \{{SchemaHolderImpl#onColumnsDropped}}) Reproducer: {code:java} public void testIndexAfterColumnsChange() { sql("create table t(id int)"); sql("create index t_idx on t(id)"); for (int i = 0; i < 100; i++) sql("insert into t values (?)", i); assertQuery("select * from t where id = 0") .matches(QueryChecker.containsIndexScan("PUBLIC", "T", "T_IDX")) .check(); sql("alter table t add column new_col int"); assertQuery("select * from t where id = 0") .matches(QueryChecker.containsIndexScan("PUBLIC", "T", "T_IDX")) .check(); } {code} -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-17596) ItThinClientComputeTest fails on Windows
Vadim Pakhnushev created IGNITE-17596: - Summary: ItThinClientComputeTest fails on Windows Key: IGNITE-17596 URL: https://issues.apache.org/jira/browse/IGNITE-17596 Project: Ignite Issue Type: Bug Reporter: Vadim Pakhnushev {{ItThinClientComputeTest}} fails on Windows due to the not correlated changes in two tickets. In IGNITE-16734 the test was added which compared the result of {{NodeNameJob}} to the hardcoded string. In IGNITE-16691 {{org.apache.ignite.internal.testframework.IgniteTestUtils#testNodeName}} was changed so on Windows node name in those tests is now not the expected {{"ItThinClientComputeTest_null_3344"}}, but short {{"n_3344"}} -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17595) Add a test to check required constructor presence in all public exception types
[ https://issues.apache.org/jira/browse/IGNITE-17595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-17595: Description: *IgniteException#wrap* throws "IgniteException-derived class does not have required constructor" when a constructor with expected signature "UUID traceId, int code, String message, Throwable cause" is not present. We should catch those issues early. Write a test to scan all jars/classes and check constructors. > Add a test to check required constructor presence in all public exception > types > --- > > Key: IGNITE-17595 > URL: https://issues.apache.org/jira/browse/IGNITE-17595 > Project: Ignite > Issue Type: Task >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha6 > > > *IgniteException#wrap* throws "IgniteException-derived class does not have > required constructor" when a constructor with expected signature "UUID > traceId, int code, String message, Throwable cause" is not present. > We should catch those issues early. Write a test to scan all jars/classes and > check constructors. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-17595) Add a test to check required constructor presence in all public exception types
Pavel Tupitsyn created IGNITE-17595: --- Summary: Add a test to check required constructor presence in all public exception types Key: IGNITE-17595 URL: https://issues.apache.org/jira/browse/IGNITE-17595 Project: Ignite Issue Type: Task Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn Fix For: 3.0.0-alpha6 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-17552) The snapshot error is not propagated to the initiating node if it is not the coordinator.
[ https://issues.apache.org/jira/browse/IGNITE-17552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17597847#comment-17597847 ] Ignite TC Bot commented on IGNITE-17552: {panel:title=Branch: [pull/10221/head] Base: [master] : No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel} {panel:title=Branch: [pull/10221/head] Base: [master] : New Tests (2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1} {color:#8b}Snapshots{color} [[tests 2|https://ci2.ignite.apache.org/viewLog.html?buildId=6581415]] * {color:#013220}IgniteSnapshotTestSuite: IgniteClusterSnapshotSelfTest.testClusterSnapshotWithExplicitPathError[Encryption=true] - PASSED{color} * {color:#013220}IgniteSnapshotTestSuite: IgniteClusterSnapshotSelfTest.testClusterSnapshotWithExplicitPathError[Encryption=false] - PASSED{color} {panel} [TeamCity *-- Run :: All* Results|https://ci2.ignite.apache.org/viewLog.html?buildId=6581433buildTypeId=IgniteTests24Java8_RunAll] > The snapshot error is not propagated to the initiating node if it is not the > coordinator. > - > > Key: IGNITE-17552 > URL: https://issues.apache.org/jira/browse/IGNITE-17552 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.13 >Reporter: Stepanov Ilya >Assignee: Pavel Pereslegin >Priority: Major > Labels: iep-43, ise > Attachments: error.log > > Time Spent: 10m > Remaining Estimate: 0h > > In some cases, when we execute "createSnapshot" on non-coordinator node, the > snapshot error is not reported in the "LastSnapshotErrorMessage" metric, but > the "LastSnapshotStartTime" and "LastSnapshotErrorMessage" metrics are > updated. > This is misleading that the snapshot was taken successfully. > The problem concerns not only metrics, despite the error, the user future > completes successfully and error does not reach the user. > Reproducer: > {code:java} > startGridsWithCache(2, dfltCacheCfg, CACHE_KEYS_RANGE); > // Must fail, but on non-coordinator finishes successfully. > > grid(1).context().cache().context().snapshotMgr().createSnapshot(SNAPSHOT_NAME, > "/bad/path").get(); > // Fails (as expected). > > grid(0).context().cache().context().snapshotMgr().createSnapshot(SNAPSHOT_NAME, > "/bad/path").get(); > {code} -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-17522) Add documentation for the index rebuild operation in the maintenance mode
[ https://issues.apache.org/jira/browse/IGNITE-17522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Gusev reassigned IGNITE-17522: --- Assignee: Igor Gusev > Add documentation for the index rebuild operation in the maintenance mode > - > > Key: IGNITE-17522 > URL: https://issues.apache.org/jira/browse/IGNITE-17522 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Semyon Danilov >Assignee: Igor Gusev >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > The new command's syntax is as follows: > {noformat} > --cache schedule_indexes_rebuild --node-id nodeId --cache-names > cacheName[index1,...indexN],cacheName2,cacheName3[index1] --group-names > groupName1,groupName2,...groupNameN > Schedules rebuild of the indexes for specified caches via the Maintenance > Mode. Schedules rebuild of specified caches and cache-groups > Parameters: > --node-id - (Optional) Specify node for indexes rebuild. If not > specified, schedules rebuild on all nodes. > --cache-names - Comma-separated list of cache names with optionally > specified indexes. If indexes are not specified then all indexes of the cache > will be scheduled for the rebuild operation. Can be used simultaneously with > cache group names. > --group-names - Comma-separated list of cache group names for which > indexes should be scheduled for the rebuild. Can be used simultaneously with > cache names. > {noformat} -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17576) Update Ignite dependency: MySQL Connector
[ https://issues.apache.org/jira/browse/IGNITE-17576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julia Bakulina updated IGNITE-17576: Ignite Flags: Release Notes Required Release Note: Updated the MySql connector dependency version (fixes CVE-2021-2471, CVE-2022-21363). > Update Ignite dependency: MySQL Connector > - > > Key: IGNITE-17576 > URL: https://issues.apache.org/jira/browse/IGNITE-17576 > Project: Ignite > Issue Type: Improvement >Reporter: Julia Bakulina >Assignee: Julia Bakulina >Priority: Minor > Labels: ise, newbie > Fix For: 2.14 > > Time Spent: 50m > Remaining Estimate: 0h > > Update Ignite dependency: MySQL Connector 8.0.26 to 8.0.30 to avoid CVE -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17168) Ducktests: bump the LATEST release version
[ https://issues.apache.org/jira/browse/IGNITE-17168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Daschinsky updated IGNITE-17168: - Ignite Flags: (was: Docs Required,Release Notes Required) > Ducktests: bump the LATEST release version > -- > > Key: IGNITE-17168 > URL: https://issues.apache.org/jira/browse/IGNITE-17168 > Project: Ignite > Issue Type: Test >Reporter: Sergey Korotkov >Assignee: Sergey Korotkov >Priority: Minor > Labels: ducktests, ise > Time Spent: 20m > Remaining Estimate: 0h > > Most ducktests are run twice. One time against the current development > version and another one against the most recent released version. It's > configured by the decorator applied to test class: > {code:python} > @ignite_versions(str(DEV_BRANCH), str(LATEST)) > {code} > The task is to update the LATEST to current most recent release (2.13) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17159) Server node failed due to java.lang.AssertionError: Client already created
[ https://issues.apache.org/jira/browse/IGNITE-17159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov updated IGNITE-17159: -- Release Note: Fixed race condition in GridNioServer. > Server node failed due to java.lang.AssertionError: Client already created > -- > > Key: IGNITE-17159 > URL: https://issues.apache.org/jira/browse/IGNITE-17159 > Project: Ignite > Issue Type: Bug > Components: networking >Affects Versions: 2.13 >Reporter: Semyon Danilov >Assignee: Semyon Danilov >Priority: Major > Fix For: 2.14 > > Time Spent: 20m > Remaining Estimate: 0h > > It seems like we release recovery descriptor prior to removing communication > client from the connection pool. So another thread successfully reserves > descriptor, creates a client and tries to put a newly created client into the > pool and fails because there is a stale client which we didn’t remove yet. I > think we should release descriptor AFTER we remove communication client and > it should fix the issue. > {noformat} > at > org.apache.ignite.spi.communication.tcp.internal.ConnectionClientPool.addNodeClient(ConnectionClientPool.java:638) > at > org.apache.ignite.spi.communication.tcp.internal.ConnectionClientPool.reserveClient(ConnectionClientPool.java:242) > at > org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(TcpCommunicationSpi.java:1174) > at > org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage(TcpCommunicationSpi.java:1123) > at > org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1817) > at > org.apache.ignite.internal.managers.communication.GridIoManager.sendToGridTopic(GridIoManager.java:1944) > at > org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1265) > at > org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1304) > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicAbstractUpdateFuture.sendDhtRequests(GridDhtAtomicAbstractUpdateFuture.java:489) > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicAbstractUpdateFuture.map(GridDhtAtomicAbstractUpdateFuture.java:445) > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1921) > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1685) > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.sendSingleRequest(GridNearAtomicAbstractUpdateFuture.java:319) > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.map(GridNearAtomicSingleUpdateFuture.java:496) > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.mapOnTopology(GridNearAtomicSingleUpdateFuture.java:454) > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.map(GridNearAtomicAbstractUpdateFuture.java:267) > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update0(GridDhtAtomicCache.java:1164) > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.put0(GridDhtAtomicCache.java:627) > at > org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2073) > at > org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2048) > at > org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1311) > at > org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.put(GatewayProtectedCacheProxy.java:817) > at > com.autozone.supplychain.csr.receiver.QuantityCacheTupleReceiver.processRecord(QuantityCacheTupleReceiver.java:123) > at > com.autozone.supplychain.csr.receiver.QuantityCacheTupleReceiver.receive(QuantityCacheTupleReceiver.java:47) > at > org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.call(DataStreamerUpdateJob.java:137) > at > org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.localUpdate(DataStreamProcessor.java:401) > at > org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:306) > at > org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:59) > at >
[jira] [Updated] (IGNITE-16582) Improve behavior of speed-based throttling when dirty pages ratio is low
[ https://issues.apache.org/jira/browse/IGNITE-16582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov updated IGNITE-16582: -- Release Note: Improved behavior of speed-based throttling when dirty pages ratio is low. > Improve behavior of speed-based throttling when dirty pages ratio is low > > > Key: IGNITE-16582 > URL: https://issues.apache.org/jira/browse/IGNITE-16582 > Project: Ignite > Issue Type: Improvement > Components: persistence >Affects Versions: 2.12 >Reporter: Roman Puchkovskiy >Assignee: Roman Puchkovskiy >Priority: Major > Fix For: 2.14 > > Time Spent: 3h 10m > Remaining Estimate: 0h > > There is a log: > {{Throttling is applied to page modifications [}} > percentOfPartTime=0.59, > markDirty=7424 pages/sec, > checkpointWrite=6268 pages/sec, > estIdealMarkDirty=0 pages/sec, > curDirty=0.00, > maxDirty=0.24, > avgParkTime=79770 ns, > {{pages: (total=67085, evicted=0, written=40916, synced=0, cpBufUsed=3, > cpBufTotal=518215)]}} > Here, it can be seen that, although there are plenty of non-dirty pages, > throttling is applied. This happens because our speed-based throttling has 2 > algorithms for protecting non-dirty pages from exhaustion: > # A more complex one that computes max allowable dirty ratio and ideal > marking speed and throttles when both dirty ratio and current marking speed > surpass these values > # A simpler one that throttles if the current marking speed is higher than > the average checkpointing speed > In the shown example the first algorithm does not throttle, but the second > one does. > It looks like the throttling is enabled too early. > One way to solve this problem is to just disable the second algorithm as the > first seems to be more adequate (but this needs careful consideration of all > possible cases). > Another way is to consider averaged marking speed instead of (or in addition > to) the current marking speed when deciding whether to throttle or not. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17151) Inconsistent keys after deletion during rebalance
[ https://issues.apache.org/jira/browse/IGNITE-17151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov updated IGNITE-17151: -- Release Note: Fixed an issue that caused inconsistent keys after deletion during rebalance. > Inconsistent keys after deletion during rebalance > - > > Key: IGNITE-17151 > URL: https://issues.apache.org/jira/browse/IGNITE-17151 > Project: Ignite > Issue Type: Bug >Reporter: Vladislav Pyatkov >Assignee: Vladislav Pyatkov >Priority: Major > Fix For: 2.14 > > Attachments: DeletionDuringRebalanceTest.java > > Time Spent: 20m > Remaining Estimate: 0h > > Scenario: > # Stop a node > # Load data while the node is still offline > # Start the node > # While the node is online and rebalancing delete objects > # Wait for the node to complete rebalancing and verified the partitions via > partition_reconciliation > Reproduced is attached. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17152) Improve logging levels for situations when dealing with a client node
[ https://issues.apache.org/jira/browse/IGNITE-17152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov updated IGNITE-17152: -- Release Note: Improved logging levels for situations when dealing with a client node. > Improve logging levels for situations when dealing with a client node > - > > Key: IGNITE-17152 > URL: https://issues.apache.org/jira/browse/IGNITE-17152 > Project: Ignite > Issue Type: Improvement > Components: networking >Reporter: Roman Puchkovskiy >Assignee: Roman Puchkovskiy >Priority: Major > Fix For: 2.14 > > Time Spent: 20m > Remaining Estimate: 0h > > An example follows: > [2022-04-27T23:01:17,872][ERROR][query-#17069%nebula-node%][TcpCommunicationSpi] > Failed to send message to remote node [node=TcpDiscoveryNode > [id=67cf0e5e-974c-463a-a1f2-915fe3cdd3e7, consistentId=67cf0e5e-974c- > 2463a-a1f2-915fe3cdd3e7, addrs=ArrayList [0:0:0:0:0:0:0:1%lo0, 127.0.0.1, > 127.94.0.1, 192.168.1.35], sockAddrs=HashSet [/127.0.0.1:0, > 0:0:0:0:0:0:0:1%lo0:0, /192.168.1.35:0, /127.94.0.1:0], discPort=0, order=25, > 3intOrder=15, lastExchangeTime=1651100317979, loc=false, > ver=8.8.14#20220124-sha1:53de42db, isClient=true], msg=GridIoMessage [plc=10, > topic=TOPIC_QUERY, topicOrd=19, ordered=false, timeout=0, skipOnTimeout=false > 4, msg=GridQueryFailResponse [qryReqId=1, errMsg=Failed to wait for > establishing inverse connection (node left topology): > 67cf0e5e-974c-463a-a1f2-915fe3cdd3e7, failCode=0, sqlErrCode=0]]] > org.apache.ignite.internal.cluster.ClusterTopologyCheckedException: Failed to > wait for establishing inverse connection (node left topology): > 67cf0e5e-974c-463a-a1f2-915fe3cdd3e7 > Here, a client has left the topology, hence we were not able to send it some > message. The resulting problem is not the server internal problem, it is just > a consequence of a client leaving (which is normal). So in this case the > problem should not be logged as an ERROR to avoid too much noise in the log. > > Another similar log is > [2022-04-27T23:01:17,872][ERROR][query-#17069%xxx-node%][GridMapQueryExecutor] > Failed to send error message. > 2org.apache.ignite.internal.cluster.ClusterTopologyCheckedException: Failed > to wait for establishing inverse connection (node left topology): > 67cf0e5e-974c-463a-a1f2-915fe3cdd3e7 3 > > Here, an error message was tried to be sent to a client, but it has already > left. Similar reasoning implies that we should not log at as ERROR. > > One more situation is demonstrated by the following log: > [2022-05-16T16:43:51,301][ERROR][sys-#51%xxx-node%][TcpCommunicationSpi] > Failed to send message to remote node [node=TcpDiscoveryNode > [id=68e268f7-abf2-41a1-a4fa-520169d2dac5, > consistentId=68e268f7-abf2-41a1-a4fa-520169d2dac5, addrs=ArrayList > 2[0:0:0:0:0:0:0:1%lo0, 127.0.0.1, 127.94.0.1, 192.168.1.170], > sockAddrs=HashSet [/127.0.0.1:0, 0:0:0:0:0:0:0:1%lo0:0, /192.168.1.170:0, > /127.94.0.1:0], discPort=0, order=79, intOrder=44, > lastExchangeTime=1652719430974, loc=false, ver=8.8.14#202201 > 324-sha1:53de42db, isClient=true], msg=GridIoMessage [plc=0, > topic=TOPIC_COMM_USER, topicOrd=9, ordered=true, timeout=5000, > skipOnTimeout=true, msg=GridIoUserMessage [clsLdrId=null, depMode=null, > depClsName=null, userVer=null, ldrParties=null, dep 4=null]]] > org.apache.ignite.IgniteCheckedException: Failed to connect to node > 68e268f7-abf2-41a1-a4fa-520169d2dac5 because it is started in > 'forceClientToServerConnections' mode; inverse connection will be requested. > > Here, the exception is not a problem at all, it's just used for flow control, > and it should not be logged at ERROR as well. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-16920) Calcite Engine. COUNT(*) lacks trivial optimization.
[ https://issues.apache.org/jira/browse/IGNITE-16920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov updated IGNITE-16920: -- Release Note: Improved SQL calcite: use index count scan for COUNT(*) > Calcite Engine. COUNT(*) lacks trivial optimization. > > > Key: IGNITE-16920 > URL: https://issues.apache.org/jira/browse/IGNITE-16920 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 2.13 >Reporter: YuJue Li >Assignee: Vladimir Steshin >Priority: Major > Labels: calcite, calcite3-required > Fix For: 2.14 > > Attachments: PI_COM_DAY.sql, example-calcite.xml, > image-2022-05-01-13-35-59-275.png > > Time Spent: 9h 50m > Remaining Estimate: 0h > > !image-2022-05-01-13-35-59-275.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17576) Update Ignite dependency: MySQL Connector
[ https://issues.apache.org/jira/browse/IGNITE-17576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Pavlov updated IGNITE-17576: --- Labels: ise newbie (was: newbie) > Update Ignite dependency: MySQL Connector > - > > Key: IGNITE-17576 > URL: https://issues.apache.org/jira/browse/IGNITE-17576 > Project: Ignite > Issue Type: Improvement >Reporter: Julia Bakulina >Assignee: Julia Bakulina >Priority: Minor > Labels: ise, newbie > Fix For: 2.14 > > Time Spent: 50m > Remaining Estimate: 0h > > Update Ignite dependency: MySQL Connector 8.0.26 to 8.0.30 to avoid CVE -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17576) Update Ignite dependency: MySQL Connector
[ https://issues.apache.org/jira/browse/IGNITE-17576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julia Bakulina updated IGNITE-17576: Priority: Minor (was: Major) > Update Ignite dependency: MySQL Connector > - > > Key: IGNITE-17576 > URL: https://issues.apache.org/jira/browse/IGNITE-17576 > Project: Ignite > Issue Type: Improvement >Reporter: Julia Bakulina >Assignee: Julia Bakulina >Priority: Minor > Labels: newbie > Fix For: 2.14 > > Time Spent: 50m > Remaining Estimate: 0h > > Update Ignite dependency: MySQL Connector 8.0.26 to 8.0.30 to avoid CVE -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17025) Remove the ability to manually set INLINE_SIZE for types with a fixed length
[ https://issues.apache.org/jira/browse/IGNITE-17025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov updated IGNITE-17025: -- Release Note: Improved adjustment inline size for fixed size index items. > Remove the ability to manually set INLINE_SIZE for types with a fixed length > > > Key: IGNITE-17025 > URL: https://issues.apache.org/jira/browse/IGNITE-17025 > Project: Ignite > Issue Type: Improvement >Reporter: Luchnikov Alexander >Assignee: Nikolay Izhikov >Priority: Minor > Labels: ise > Fix For: 2.14 > > Attachments: InlineIndexTest1.patch > > Time Spent: 20m > Remaining Estimate: 0h > > The reproducer ( [^InlineIndexTest1.patch] ) shows index.bin size growing > when INLINE_SIZE increases when creating indexes on fixed length fields.The > negative point is that a place is reserved that does not carry any profit. > As a solution. When trying to build an index on a field with a fixed length > type, do not allow this. The value of INLINE_SIZE for such types is > calculated automatically. And display a WARN level message about it. > To see the size of index.bin, run the > {code:java} > du -sh IGNITE_HOME/db/node*/*INLINE*/* | grep index.bin" > {code} > after running the reproducer. > {code:java} > 36K BIGINT_INLINE10/index.bin > 320K BIGINT_INLINE100/index.bin > 128K INT_INLINE10/index.bin > 324K INT_INLINE100/index.bin > 64K NUMBER_INLINE10/index.bin > 64K NUMBER_INLINE100/index.bin > 128K VARCHAR_INLINE10/index.bin > 256K VARCHAR_INLINE100/index.bin > {code} -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-16757) Add cache create/destroy events to CDCConsumer
[ https://issues.apache.org/jira/browse/IGNITE-16757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov updated IGNITE-16757: -- Release Note: Added cache change events for CDCCosumer. > Add cache create/destroy events to CDCConsumer > -- > > Key: IGNITE-16757 > URL: https://issues.apache.org/jira/browse/IGNITE-16757 > Project: Ignite > Issue Type: Improvement >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: IEP-59 > Fix For: 2.14 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > Need to provide the way to notify {{CDCConsumer}} about creation/destroying > caches(tables). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-14449) Add binary meta change event to CDCCosumer
[ https://issues.apache.org/jira/browse/IGNITE-14449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov updated IGNITE-14449: -- Release Note: Added CDC binary meta change events. > Add binary meta change event to CDCCosumer > -- > > Key: IGNITE-14449 > URL: https://issues.apache.org/jira/browse/IGNITE-14449 > Project: Ignite > Issue Type: Improvement >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: IEP-59 > Fix For: 2.14 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Need to provide the way to notify {{CDCConsumer}} about changes in binary > meta. > Required to correctly notify subsequent systems about new types that can be > found in change events. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-16822) Fix GridCacheLifecycleAwareSelfTest.testLifecycleAware
[ https://issues.apache.org/jira/browse/IGNITE-16822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov updated IGNITE-16822: -- Ignite Flags: (was: Docs Required,Release Notes Required) > Fix GridCacheLifecycleAwareSelfTest.testLifecycleAware > -- > > Key: IGNITE-16822 > URL: https://issues.apache.org/jira/browse/IGNITE-16822 > Project: Ignite > Issue Type: Bug >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Minor > Fix For: 2.14 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > GridCacheLifecycleAwareSelfTest.testLifecycleAware always fail. > Need to fix it > https://ci2.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-5330309473671089592=testDetails -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17075) Cache 6 suite timeouts sporadically
[ https://issues.apache.org/jira/browse/IGNITE-17075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov updated IGNITE-17075: -- Ignite Flags: (was: Docs Required,Release Notes Required) > Cache 6 suite timeouts sporadically > --- > > Key: IGNITE-17075 > URL: https://issues.apache.org/jira/browse/IGNITE-17075 > Project: Ignite > Issue Type: Bug >Reporter: Vladislav Pyatkov >Assignee: Vladislav Pyatkov >Priority: Major > Fix For: 2.14 > > Time Spent: 10m > Remaining Estimate: 0h > > Let’s investigate and fix this. > https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_Cache6?branch=%3Cdefault%3E=overview=builds -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17161) index-reader contains repeated stack trace
[ https://issues.apache.org/jira/browse/IGNITE-17161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov updated IGNITE-17161: -- Release Note: Improved index-reader.sh utility: exclude repeated stack traces. > index-reader contains repeated stack trace > -- > > Key: IGNITE-17161 > URL: https://issues.apache.org/jira/browse/IGNITE-17161 > Project: Ignite > Issue Type: Improvement >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Minor > Fix For: 2.14 > > Time Spent: 20m > Remaining Estimate: 0h > > index-reader log looks a bit overwhelmed. > The same stack trace repeated 40k times with the only difference in pageId. > It seems we can keep one line for each error and don't repeat whole stack > trace. > Also, index-reader use own logging way - we should keep consistent user > experience and log the same way as control.sh do. > {noformat} > ---These pages types were encountered during sequential scan: > TrackingPageIO: 61 > PageMetaIOV2: 1 > InlineInnerIO: 50885 > MetaStoreLeafIO: 47 > BPlusMetaIO: 170 > PagesListNodeIO: 1671 > MetaStoreInnerIO: 15 > InlineLeafIO: 928993 > PagesListMetaIO: 1 > --- > Errors: > class org.apache.ignite.IgniteException: Exception occurred on step 271: > Possibly orphan InlineInnerIO page, pageId=844420635164943 > at > org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.lambda$scanFileStore$9(IgniteIndexReader.java:560) > at > org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.doWithBuffer(IgniteIndexReader.java:520) > at > org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.scanFileStore(IgniteIndexReader.java:539) > at > org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.readIdx(IgniteIndexReader.java:405) > at > org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.main(IgniteIndexReader.java:1373) > Caused by: class org.apache.ignite.IgniteException: Possibly orphan > InlineInnerIO page, pageId=844420635164943 > at > org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.lambda$readIdx$6(IgniteIndexReader.java:417) > at > org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.lambda$scanFileStore$9(IgniteIndexReader.java:554) > ... 4 more > class org.apache.ignite.IgniteException: Exception occurred on step 981775: > Possibly orphan InlineInnerIO page, pageId=844420636146447 > at > org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.lambda$scanFileStore$9(IgniteIndexReader.java:560) > at > org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.doWithBuffer(IgniteIndexReader.java:520) > at > org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.scanFileStore(IgniteIndexReader.java:539) > at > org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.readIdx(IgniteIndexReader.java:405) > at > org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.main(IgniteIndexReader.java:1373) > Caused by: class org.apache.ignite.IgniteException: Possibly orphan > InlineInnerIO page, pageId=844420636146447 > at > org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.lambda$readIdx$6(IgniteIndexReader.java:417) > at > org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.lambda$scanFileStore$9(IgniteIndexReader.java:554) > ... 4 more > ... > class org.apache.ignite.IgniteException: Exception occurred on step 981790: > Possibly orphan InlineInnerIO page, pageId=844420636146462 > at > org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.lambda$scanFileStore$9(IgniteIndexReader.java:560) > at > org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.doWithBuffer(IgniteIndexReader.java:520) > at > org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.scanFileStore(IgniteIndexReader.java:539) > at > org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.readIdx(IgniteIndexReader.java:405) > at > org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.main(IgniteIndexReader.java:1373) > Caused by: class org.apache.ignite.IgniteException: Possibly orphan > InlineInnerIO page, pageId=844420636146462 > at > org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.lambda$readIdx$6(IgniteIndexReader.java:417) > at > org.apache.ignite.internal.commandline.indexreader.IgniteIndexReader.lambda$scanFileStore$9(IgniteIndexReader.java:554) > ... 4 more > --- > Total pages encountered during sequential scan: 981844 > Total errors occurred during sequential scan: 44853 > {noformat} > The following
[jira] [Updated] (IGNITE-17181) index-reader add size of data
[ https://issues.apache.org/jira/browse/IGNITE-17181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov updated IGNITE-17181: -- Release Note: Improved index-reader.sh utility: add free size calculation. > index-reader add size of data > - > > Key: IGNITE-17181 > URL: https://issues.apache.org/jira/browse/IGNITE-17181 > Project: Ignite > Issue Type: Improvement >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Fix For: 2.14 > > Time Spent: 20m > Remaining Estimate: 0h > > It will be useful to calculate and output size of indexes pages vs. size of > data stored inside pages. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17234) "version" and "probe" REST commands should not require authentication
[ https://issues.apache.org/jira/browse/IGNITE-17234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov updated IGNITE-17234: -- Release Note: Improved REST commands: skip authorization for 'Probe' and 'Version' commands. > "version" and "probe" REST commands should not require authentication > - > > Key: IGNITE-17234 > URL: https://issues.apache.org/jira/browse/IGNITE-17234 > Project: Ignite > Issue Type: Improvement > Components: rest >Reporter: Dmitriy Borunov >Assignee: Dmitriy Borunov >Priority: Major > Fix For: 2.14 > > Time Spent: 20m > Remaining Estimate: 0h > > *Actual:* > /ignite?cmd=version and /ignite?cmd=probe both return: > {code:java} > {"successStatus":2,"error":"Failed to authenticate remote client (secure > session SPI not set?): GridRestRequest [destId=null, > clientId=3fbf0a38-4d80-42f3-9f77-a0ba7e2da396, addr=/127.0.0.1:54649, > cmd=, authCtx=null]","sessionToken":null,"response":null} {code} > *Expected:* > {code:java} > {"successStatus":0,"error":null,"sessionToken":null,"response":"grid has > started"} {code} > These two commands should not require authentication because it could cause a > timeout due to system cache usage (transactions + pme ). These commands may > be blocked for some time or timed out. It can be interpreted as a cluster > failure. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17415) A node receives and resolves obsolete addresses from the previously restarted and killed nodes
[ https://issues.apache.org/jira/browse/IGNITE-17415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov updated IGNITE-17415: -- Release Note: Fixed an issue that caused a node resolves obsolete addresses from the previously restarted and killed nodes. > A node receives and resolves obsolete addresses from the previously restarted > and killed nodes > -- > > Key: IGNITE-17415 > URL: https://issues.apache.org/jira/browse/IGNITE-17415 > Project: Ignite > Issue Type: Bug > Components: networking >Affects Versions: 2.13 >Reporter: Semyon Danilov >Assignee: Semyon Danilov >Priority: Major > Fix For: 2.14 > > Time Spent: 20m > Remaining Estimate: 0h > > Observation: Ignite tries to resolve *all* known IP and DNS names exposed by > the nodes since the cluster startup. This might cause a delay in response if > DNS resolution takes some time and critical for Kubernetes envroments. > The issue is due to the ignite keeping track of the topology history. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17414) A node is trying to resolve its DNS even if raw IP is configured in IGNITE_LOCAL_HOST
[ https://issues.apache.org/jira/browse/IGNITE-17414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov updated IGNITE-17414: -- Ignite Flags: Release Notes Required (was: Docs Required,Release Notes Required) > A node is trying to resolve its DNS even if raw IP is configured in > IGNITE_LOCAL_HOST > - > > Key: IGNITE-17414 > URL: https://issues.apache.org/jira/browse/IGNITE-17414 > Project: Ignite > Issue Type: Bug > Components: networking >Affects Versions: 2.13 >Reporter: Semyon Danilov >Assignee: Semyon Danilov >Priority: Major > Fix For: 2.14 > > Time Spent: 20m > Remaining Estimate: 0h > > Scenario: > Given the following etc/hosts from a Kubernetes POD: > 127.0.0.1 localhost > ::1 localhost ip6-localhost ip6-loopback > fe00::0 ip6-localnet > fe00::0 ip6-mcastprefix > fe00::1 ip6-allnodes > fe00::2 ip6-allrouters > 10.1.2.108 apache-ignite-cluster-2-client-1-0 > And ENV variable IGNITE_LOCAL_HOST=10.1.2.108, we are still resolving this as > apache-ignite-cluster-2-client-1-0/10.1.2.108 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17414) A node is trying to resolve its DNS even if raw IP is configured in IGNITE_LOCAL_HOST
[ https://issues.apache.org/jira/browse/IGNITE-17414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov updated IGNITE-17414: -- Release Note: Fixed an issue that caused a node is trying to resolve its hostname if IP is configured with IGNITE_LOCAL_HOST. > A node is trying to resolve its DNS even if raw IP is configured in > IGNITE_LOCAL_HOST > - > > Key: IGNITE-17414 > URL: https://issues.apache.org/jira/browse/IGNITE-17414 > Project: Ignite > Issue Type: Bug > Components: networking >Affects Versions: 2.13 >Reporter: Semyon Danilov >Assignee: Semyon Danilov >Priority: Major > Fix For: 2.14 > > Time Spent: 20m > Remaining Estimate: 0h > > Scenario: > Given the following etc/hosts from a Kubernetes POD: > 127.0.0.1 localhost > ::1 localhost ip6-localhost ip6-loopback > fe00::0 ip6-localnet > fe00::0 ip6-mcastprefix > fe00::1 ip6-allnodes > fe00::2 ip6-allrouters > 10.1.2.108 apache-ignite-cluster-2-client-1-0 > And ENV variable IGNITE_LOCAL_HOST=10.1.2.108, we are still resolving this as > apache-ignite-cluster-2-client-1-0/10.1.2.108 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17415) A node receives and resolves obsolete addresses from the previously restarted and killed nodes
[ https://issues.apache.org/jira/browse/IGNITE-17415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov updated IGNITE-17415: -- Ignite Flags: Release Notes Required (was: Docs Required,Release Notes Required) > A node receives and resolves obsolete addresses from the previously restarted > and killed nodes > -- > > Key: IGNITE-17415 > URL: https://issues.apache.org/jira/browse/IGNITE-17415 > Project: Ignite > Issue Type: Bug > Components: networking >Affects Versions: 2.13 >Reporter: Semyon Danilov >Assignee: Semyon Danilov >Priority: Major > Fix For: 2.14 > > Time Spent: 20m > Remaining Estimate: 0h > > Observation: Ignite tries to resolve *all* known IP and DNS names exposed by > the nodes since the cluster startup. This might cause a delay in response if > DNS resolution takes some time and critical for Kubernetes envroments. > The issue is due to the ignite keeping track of the topology history. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-17196) Implement in-memory raft group reconfiguration on node failure
[ https://issues.apache.org/jira/browse/IGNITE-17196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17597731#comment-17597731 ] Ivan Bessonov commented on IGNITE-17196: Looks good to me! > Implement in-memory raft group reconfiguration on node failure > -- > > Key: IGNITE-17196 > URL: https://issues.apache.org/jira/browse/IGNITE-17196 > Project: Ignite > Issue Type: Improvement > Components: persistence >Reporter: Roman Puchkovskiy >Assignee: Semyon Danilov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha6 > > Time Spent: 12h 20m > Remaining Estimate: 0h > > We need to implement design described in IGNITE-16668 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (IGNITE-15424) Calcite engine. Move schema management infrastructure to the core module
[ https://issues.apache.org/jira/browse/IGNITE-15424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17597725#comment-17597725 ] Taras Ledkov edited comment on IGNITE-15424 at 8/30/22 9:46 AM: [~alex_pl], please take a look at the comment in the PR. The patch is OK with me. Please fix synchronization for the {{H2SchemaManager}} and {{SchemaManager}}. was (Author: tledkov): [~alex_pl], please take a look at the comment in the PR. The patch is OK with me. Please fix synchronization for the `H2SchemaManager` and `SchemaManager`. > Calcite engine. Move schema management infrastructure to the core module > - > > Key: IGNITE-15424 > URL: https://issues.apache.org/jira/browse/IGNITE-15424 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksey Plekhanov >Assignee: Aleksey Plekhanov >Priority: Major > Labels: calcite2-required, ignite-osgi, important, osgi > Fix For: 2.14 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Currently, schema management commands initiated in the {{ignite-core}} > module, but all processing implemented in the {{ignite-indexing}} module. > Ignite Calciite SQL engine use {{SchemaChangeListener}} to maintain own > structures. > To get rid of {{ignite-indexing}} (and H2) dependency from the > {{ignite-calcite}} module we should move schema management implementation to > the core module. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (IGNITE-15424) Calcite engine. Move schema management infrastructure to the core module
[ https://issues.apache.org/jira/browse/IGNITE-15424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17597725#comment-17597725 ] Taras Ledkov edited comment on IGNITE-15424 at 8/30/22 9:43 AM: [~alex_pl], please take a look at the comment in the PR. The patch is OK with me. Please fix synchronization for the `H2SchemaManager` and `SchemaManager`. was (Author: tledkov): [~alex_pl], please take a look at the comment in the PR. > Calcite engine. Move schema management infrastructure to the core module > - > > Key: IGNITE-15424 > URL: https://issues.apache.org/jira/browse/IGNITE-15424 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksey Plekhanov >Assignee: Aleksey Plekhanov >Priority: Major > Labels: calcite2-required, ignite-osgi, important, osgi > Fix For: 2.14 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Currently, schema management commands initiated in the {{ignite-core}} > module, but all processing implemented in the {{ignite-indexing}} module. > Ignite Calciite SQL engine use {{SchemaChangeListener}} to maintain own > structures. > To get rid of {{ignite-indexing}} (and H2) dependency from the > {{ignite-calcite}} module we should move schema management implementation to > the core module. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-15424) Calcite engine. Move schema management infrastructure to the core module
[ https://issues.apache.org/jira/browse/IGNITE-15424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17597725#comment-17597725 ] Taras Ledkov commented on IGNITE-15424: --- [~alex_pl], please take a look at the comment in the PR. > Calcite engine. Move schema management infrastructure to the core module > - > > Key: IGNITE-15424 > URL: https://issues.apache.org/jira/browse/IGNITE-15424 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksey Plekhanov >Assignee: Aleksey Plekhanov >Priority: Major > Labels: calcite2-required, ignite-osgi, important, osgi > Fix For: 2.14 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Currently, schema management commands initiated in the {{ignite-core}} > module, but all processing implemented in the {{ignite-indexing}} module. > Ignite Calciite SQL engine use {{SchemaChangeListener}} to maintain own > structures. > To get rid of {{ignite-indexing}} (and H2) dependency from the > {{ignite-calcite}} module we should move schema management implementation to > the core module. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-17594) Improve structures for query monitoring
[ https://issues.apache.org/jira/browse/IGNITE-17594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Novikov reassigned IGNITE-17594: --- Assignee: Andrey Novikov > Improve structures for query monitoring > --- > > Key: IGNITE-17594 > URL: https://issues.apache.org/jira/browse/IGNITE-17594 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Andrey Novikov >Assignee: Andrey Novikov >Priority: Major > Fix For: 2.15 > > > To improve monitor of running queries on node we need to pass following > properties {{{}cancellable{}}}, > {{{}enforceJoinOrder{}}},{{{}lazy{}}},{{{}distributedJoins{}}},{{{}failedReason{}}} > to existing listeners IgniteH2Indexing#registerQueryStartedListener, > IgniteH2Indexing#registerQueryFinishedListener. > *What to do:* > Add > {{{}enforceJoinOrder{}}},{{{}lazy{}}},{{{}distributedJoins{}}},{{{}failedReason{}}} > to GridQueryFinishedInfo > Add {{{}cancellable{}}}, > {{{}enforceJoinOrder{}}},{{{}lazy{}}},{{{}distributedJoins{}}} to > GridQueryStartedInfo -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-17561) SQLException: Hexadecimal string with odd number of characters
[ https://issues.apache.org/jira/browse/IGNITE-17561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17597706#comment-17597706 ] Dren commented on IGNITE-17561: --- Hi [~jooger] , after in place upgrade from 2.7.6 to 2.13 this problem happened to me on development environment. I solved the problem by dropping the table and re-creating it. For data insert I use the Python module pyignite. {code:java} // code placeholder SQL_STORE_ENRICH_PROCESSOR_STAT = ''' INSERT INTO STAT_ENRICH_PROCESSOR (SAMPLE_TIME, CACHE_NAME, CACHE_SIZE, ACTIVE_THREADS, THREAD_QUEUE, PROC_TIME ) VALUES (CURRENT_TIMESTAMP(3), ?, ?, ?, ?, ? ) ''' try: client.sql(SQL_STORE_ENRICH_PROCESSOR_STAT, query_args=data) except Exception as e: logger.error('ERROR in SQL_STORE_ENRICH_PROCESSOR_STAT: %s ' % (e)) {code} > SQLException: Hexadecimal string with odd number of characters > -- > > Key: IGNITE-17561 > URL: https://issues.apache.org/jira/browse/IGNITE-17561 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.13 > Environment: Ignite 2.13.0 >Reporter: Dren >Priority: Critical > Attachments: CREATE_TABLE_STAT_ENRICH_PROCESSOR.sql, Ignite_log.txt, > data_sample_in_table.jpg, error_sql1.jpg, ok_sql2.jpg > > > After in place upgrade from 2.7.6 to 2.13.0 SQL failed with error. > {code:java} > // > Caused by: org.h2.jdbc.JdbcSQLException: Hexadecimal string with odd number > of characters: "2022-08-22 10:30:58.938" [90003-197] > at > org.h2.message.DbException.getJdbcSQLException(DbException.java:357) > ... 57 more {code} > After creation of new table with same columns and same data SQL return result > without error. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-17508) Exception handling in the partition replication listener for RAFT futures
[ https://issues.apache.org/jira/browse/IGNITE-17508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin reassigned IGNITE-17508: Assignee: Vladislav Pyatkov > Exception handling in the partition replication listener for RAFT futures > - > > Key: IGNITE-17508 > URL: https://issues.apache.org/jira/browse/IGNITE-17508 > Project: Ignite > Issue Type: Improvement >Reporter: Vladislav Pyatkov >Assignee: Vladislav Pyatkov >Priority: Major > Labels: ignite-3 > > In the replication listener ({_}PartitionReplicaListener{_}) where we have > the pattern: > {code:java} > raftFut.thenApply(ignored -> result);{code} > we should worry about handling RAFT exceptions, including analyzing whether > raftFut result. > Can distinguish following exception types for RAFT: > * RAFT cannot replicate a command for the timeout ({_}TimeoutException{_}). > Hence, this exception leads to the replication timeout exception > ({_}ReplicationTimeoutException{_}). > * It throws some internal exception ({_}RaftException{_}). This exception > should be wrapped of the common replication exception > ({_}ReplicationException{_}). > * Finally, RAFT throws java exceptions (NullPointerException, > IndexOutOfRangeException e.t.c). Those exceptions shouldn't be touched, is > will be through as is. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (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:all-tabpanel ] Vyacheslav Koptilin reassigned IGNITE-17260: Assignee: Alexander Lapin > Enrich IgniteTransactions and Transaction interfaces with RO related methods > > > Key: IGNITE-17260 > URL: https://issues.apache.org/jira/browse/IGNITE-17260 > Project: Ignite > Issue Type: Improvement >Reporter: Alexander Lapin >Assignee: Alexander Lapin >Priority: Major > Labels: ignite-3, transaction3_ro > > It's required to explicitly register an intent of starting readOnly > transaction, so that overloaded versions > {code:java} > Transaction begin(HybridTimestamp timestamp){code} > and > {code:java} > CompletableFuture beginAsync(HybridTimestamp timestamp){code} > should be added to IgniteTransactions together with corresponding > implementation. > Besides that Transaction interface should be extended with > {code:java} > boolean isReadOnly();{code} > and > {code:java} > HybridTimestamp timestamp();{code} > methods. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-17222) Need to propagate HLC with transaction protocol events
[ https://issues.apache.org/jira/browse/IGNITE-17222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin reassigned IGNITE-17222: Assignee: Sergey Uttsel > Need to propagate HLC with transaction protocol events > -- > > Key: IGNITE-17222 > URL: https://issues.apache.org/jira/browse/IGNITE-17222 > Project: Ignite > Issue Type: Improvement >Reporter: Sergey Uttsel >Assignee: Sergey Uttsel >Priority: Major > Labels: ignite-3, transaction3_ro > > One of source of HLC sync is a transaction protocol. Each ReplicaRequest и > ReplicaResponse should carry the sender’s HLC and updates receiver HLC > according to rules. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17498) Update HeapLockManager in order to support Intention locks
[ https://issues.apache.org/jira/browse/IGNITE-17498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Uttsel updated IGNITE-17498: --- Description: It's required to implement new lock upgrade logic that will consider not only S and X locks but also IS, IX and SIX. Also need create method for lock downgrading. was: It's required to implement new lock upgrade logic that will consider not only S and X locks but also IS, IX and SIX. > Update HeapLockManager in order to support Intention locks > -- > > Key: IGNITE-17498 > URL: https://issues.apache.org/jira/browse/IGNITE-17498 > Project: Ignite > Issue Type: Improvement >Reporter: Alexander Lapin >Assignee: Sergey Uttsel >Priority: Major > Labels: ignite-3, transaction3_rw > > It's required to implement new lock upgrade logic that will consider not only > S and X locks but also IS, IX and SIX. > Also need create method for lock downgrading. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-17535) Implementing a hash index B+Tree
[ https://issues.apache.org/jira/browse/IGNITE-17535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Bessonov reassigned IGNITE-17535: -- Assignee: Ivan Bessonov (was: Kirill Tkalenko) > Implementing a hash index B+Tree > > > Key: IGNITE-17535 > URL: https://issues.apache.org/jira/browse/IGNITE-17535 > Project: Ignite > Issue Type: Task >Reporter: Kirill Tkalenko >Assignee: Ivan Bessonov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha6 > > Time Spent: 10m > Remaining Estimate: 0h > > It is necessary to implement a hash index B+Tree, for simplicity, without > inlining a *BinaryTuple*, but simply storing a link to it. > The key will be: hash and link of the *BinaryTuple*. > The value will be: *RowId*. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-17541) Add "set" prefix to ThinClientConfiguration#sendServerExceptionStackTraceToClient()
[ https://issues.apache.org/jira/browse/IGNITE-17541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17597594#comment-17597594 ] Ignite TC Bot commented on IGNITE-17541: {panel:title=Branch: [pull/10220/head] Base: [master] : Possible Blockers (4)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1} {color:#d04437}Platform .NET (Windows){color} [[tests 0 TIMEOUT , Exit Code |https://ci2.ignite.apache.org/viewLog.html?buildId=6579878]] {color:#d04437}Cache 6{color} [[tests 1|https://ci2.ignite.apache.org/viewLog.html?buildId=6579814]] * IgniteCacheTestSuite6: CacheExchangeMergeTest.testMergeAndHistoryCleanup - Test has low fail rate in base branch 0,0% and is not flaky {color:#d04437}Cache (Failover) 1{color} [[tests 0 TIMEOUT , Exit Code |https://ci2.ignite.apache.org/viewLog.html?buildId=6579820]] {color:#d04437}Service Grid{color} [[tests 1|https://ci2.ignite.apache.org/viewLog.html?buildId=6579890]] * IgniteServiceGridTestSuite: IgniteServiceReassignmentTest.testNodeRestartRandom - Test has low fail rate in base branch 0,0% and is not flaky {panel} {panel:title=Branch: [pull/10220/head] Base: [master] : No new tests found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel} [TeamCity *-- Run :: All* Results|https://ci2.ignite.apache.org/viewLog.html?buildId=6579909buildTypeId=IgniteTests24Java8_RunAll] > Add "set" prefix to > ThinClientConfiguration#sendServerExceptionStackTraceToClient() > --- > > Key: IGNITE-17541 > URL: https://issues.apache.org/jira/browse/IGNITE-17541 > Project: Ignite > Issue Type: Improvement > Components: thin client >Affects Versions: 2.13 >Reporter: Ilya Shishkov >Assignee: Julia Bakulina >Priority: Minor > Labels: ise, newbie > Time Spent: 25m > Remaining Estimate: 0h > > IGNITE-13389 introduces > {{ThinClientConfiguration#sendServerExceptionStackTraceToClient()}}, but name > of the method does not allow to set up this option in XML configuration, > because Spring expects "set" prefix for setters. > As you can see below, there is a workaround, but it would be more convenient > to set up this property directly. > Workaround: > {code:xml|title=Add extra ThinClientConfiguration bean with necessary > parameters} > class="org.apache.ignite.configuration.ThinClientConfiguration"> > > > {code} > {code:xml|title=Set up thinClientConfiguration by means of SpEL} > > class="org.apache.ignite.configuration.ClientConnectorConfiguration"> > > value="#{thinClientCfg.sendServerExceptionStackTraceToClient(true)}"/> > > > {code} > We should add "set" and "get" prefix to setter and getter methods > respectively or add extra methods with such prefixes from the point of > possible compatibility issues (see IGNITE-16549). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17576) Update Ignite dependency: MySQL Connector
[ https://issues.apache.org/jira/browse/IGNITE-17576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julia Bakulina updated IGNITE-17576: Description: Update Ignite dependency: MySQL Connector 8.0.26 to 8.0.30 (was: Update Ignite dependency: MySQL Connector 8.0.26 to 8.0.28) > Update Ignite dependency: MySQL Connector > - > > Key: IGNITE-17576 > URL: https://issues.apache.org/jira/browse/IGNITE-17576 > Project: Ignite > Issue Type: Improvement >Reporter: Julia Bakulina >Assignee: Julia Bakulina >Priority: Major > Labels: newbie > Fix For: 2.14 > > Time Spent: 50m > Remaining Estimate: 0h > > Update Ignite dependency: MySQL Connector 8.0.26 to 8.0.30 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17576) Update Ignite dependency: MySQL Connector
[ https://issues.apache.org/jira/browse/IGNITE-17576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julia Bakulina updated IGNITE-17576: Description: Update Ignite dependency: MySQL Connector 8.0.26 to 8.0.30 to avoid CVE (was: Update Ignite dependency: MySQL Connector 8.0.26 to 8.0.30) > Update Ignite dependency: MySQL Connector > - > > Key: IGNITE-17576 > URL: https://issues.apache.org/jira/browse/IGNITE-17576 > Project: Ignite > Issue Type: Improvement >Reporter: Julia Bakulina >Assignee: Julia Bakulina >Priority: Major > Labels: newbie > Fix For: 2.14 > > Time Spent: 50m > Remaining Estimate: 0h > > Update Ignite dependency: MySQL Connector 8.0.26 to 8.0.30 to avoid CVE -- This message was sent by Atlassian Jira (v8.20.10#820010)