[jira] [Resolved] (IGNITE-22542) Synchronous message handling on local node
[
https://issues.apache.org/jira/browse/IGNITE-22542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko resolved IGNITE-22542.
--
Resolution: Done
Performance analysis was performed and improvement tickets were created.
> Synchronous message handling on local node
> --
>
> Key: IGNITE-22542
> URL: https://issues.apache.org/jira/browse/IGNITE-22542
> Project: Ignite
> Issue Type: Bug
>Reporter: Ivan Bessonov
>Assignee: Kirill Tkalenko
>Priority: Major
> Labels: ignite-3, ignite3_performance
>
> {{org.apache.ignite.internal.network.DefaultMessagingService#isSelf}} - if we
> detect that we send a message to the local node, we handle it immediately in
> the same thread, which could be very bad for throughput of the system.
> "send"/"invoke" themselves appear to be slow as well, we should benchmark
> them. We should remove instantiation of InetSocketAddress for sure, if it's
> possible, it takes time to resolve it. Maybe we should create it unresolved
> or just cache it like in Ignite 2.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-22614) Get rid of @Marshallable in package org.apache.ignite.internal.partition.replicator.network
Kirill Tkalenko created IGNITE-22614: Summary: Get rid of @Marshallable in package org.apache.ignite.internal.partition.replicator.network Key: IGNITE-22614 URL: https://issues.apache.org/jira/browse/IGNITE-22614 Project: Ignite Issue Type: Improvement Reporter: Kirill Tkalenko Assignee: Kirill Tkalenko To increase performance when sending messages, in which some of the time was spent on marshaling objects that were not needed, we will get rid of *@Marshallable* in package *org.apache.ignite.internal.partition.replicator.network*. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-22444) Sql. Assign CHARACTER or CHARACTER VARYING to the other type.
[
https://issues.apache.org/jira/browse/IGNITE-22444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin reassigned IGNITE-22444:
-
Assignee: Pavel Pereslegin
> Sql. Assign CHARACTER or CHARACTER VARYING to the other type.
> -
>
> Key: IGNITE-22444
> URL: https://issues.apache.org/jira/browse/IGNITE-22444
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 3.0.0-beta1
>Reporter: Evgeny Stanilovsky
>Assignee: Pavel Pereslegin
>Priority: Major
> Labels: ignite-3
>
> According to standard:
> {noformat}
> Values of either the CHARACTER or CHARACTER VARYING data type can be assigned
> to the other type, subject to truncation conditions
> {noformat}
> Thus i expect such expressions need to be processed correctly, but it fails:
> {noformat}
> create table tiny(v TINYINT);
> insert into tiny values(127);
> SELECT * FROM tiny WHERE v < '300';
> {noformat}
> {noformat}
> Caused by: org.apache.ignite.sql.SqlException: IGN-SQL-5
> TraceId:cfce3f69-606e-482b-b267-260f8569df62 Value '300' out of range for
> type TINYINT
> at
> org.apache.ignite.internal.sql.engine.prepare.IgniteSqlValidator.literalCanFitType(IgniteSqlValidator.java:714)
> at
> org.apache.ignite.internal.sql.engine.prepare.IgniteSqlValidator.checkTypesInteroperability(IgniteSqlValidator.java:680)
> at
> org.apache.ignite.internal.sql.engine.prepare.IgniteSqlValidator.deriveType(IgniteSqlValidator.java:550)
> {noformat}
> Seems such a problem was introduced here [1]
> [1] IGNITE-18662
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-22613) Sql. Scalar subquery that returns more than one column produces unexpected validation error
Maksim Zhuravkov created IGNITE-22613:
-
Summary: Sql. Scalar subquery that returns more than one column
produces unexpected validation error
Key: IGNITE-22613
URL: https://issues.apache.org/jira/browse/IGNITE-22613
Project: Ignite
Issue Type: Bug
Components: sql
Reporter: Maksim Zhuravkov
{noformat}
SELECT (VALUES ROW(2, 4))
{noformat}
Produces the following error:
{noformat}
Cannot apply '$SCALAR_QUERY' to arguments of type
'$SCALAR_QUERY()'. Supported
form(s): '$SCALAR_QUERY()'
at
java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)
{noformat}
*Expected error*: Subquery must return only 1 column.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-22612) SQL highlighter sometimes fails
Vadim Pakhnushev created IGNITE-22612:
-
Summary: SQL highlighter sometimes fails
Key: IGNITE-22612
URL: https://issues.apache.org/jira/browse/IGNITE-22612
Project: Ignite
Issue Type: Bug
Components: cli
Reporter: Vadim Pakhnushev
Assignee: Vadim Pakhnushev
While writing and deleting random symbols in the sql prompt in the REPL mode
these errors occur sometimes:
{noformat}
[node1]> sql
sql-cli> CR
Unknown error
Cannot invoke "String.hashCode()" because "" is null
{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-22114) NullPointerException when restarting a node few times in a row
[
https://issues.apache.org/jira/browse/IGNITE-22114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17860820#comment-17860820
]
Kirill Gusakov commented on IGNITE-22114:
-
On the commit `d593e6487aa36a806bab075d19c8b831ca096a28` the issue can be
reproduced by the simple test like:
{code:java}
public class ReproduceTest extends ClusterPerTestIntegrationTest {
/** Table name. */
private static final String TABLE_NAME = "test_table";
private static final int PART_ID = 0;
@BeforeEach
@Override
public void setup(TestInfo testInfo) throws Exception {
super.setup(testInfo);
String zoneSql = "create zone test_zone with partitions=1, replicas=3,
storage_profiles='" + DEFAULT_PROFILE_NAME + "'";
String sql = "create table " + TABLE_NAME + " (key int primary key, val
int) with primary_zone='TEST_ZONE'";
String insertStmt = "INSERT INTO " + TABLE_NAME + "(key, val)"
+ " VALUES (1, 1)";
cluster.doInSession(0, session -> {
executeUpdate(zoneSql, session);
executeUpdate(sql, session);
executeUpdate(insertStmt, session);
});
}
@Test
void test() throws InterruptedException {
for (int i = 0; i < 4; i++) {
stopNode(1);
Thread.sleep(3);
startNode(1);
}
}
}
{code}
But on the current main `079225e5764e5537844c6e499f0a513c44a1e62d` this issue
is not reproducing anymore
> NullPointerException when restarting a node few times in a row
> --
>
> Key: IGNITE-22114
> URL: https://issues.apache.org/jira/browse/IGNITE-22114
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 3.0.0-beta2
>Reporter: Andrey Khitrin
>Priority: Major
> Labels: ignite-3
>
> Steps to reproduce:
> 1. Start a 3-node cluster (`node-1`, `node-2`, `node-3`)
> 2. Run some load on it (read and write)
> 3. Shutdown a single node, wait some time, start it again
> 4. After a little time (say, 30 seconds) shutdown the same node again, wait
> some time, start it again
> In my case, an issue was reproduced on commit
> `d593e6487aa36a806bab075d19c8b831ca096a28` (2024-04-24 IGNITE-2124) on the
> 2nd restart of `node-3`.
> Expected results: node starts without error.
> Actual results: NPE in `ignite3-startup.log`.
> {code}
> Error when starting the node: org.apache.ignite.lang.IgniteException:
> IGN-CMN-65535 TraceId:c7b27181-0977-4925-b0ba-fa07d8a3bebe
> org.apache.ignite.lang.IgniteException: IGN-CMN-65535
> TraceId:c7b27181-0977-4925-b0ba-fa07d8a3bebe Unable to start [node=node-3]
> java.util.concurrent.ExecutionException:
> org.apache.ignite.lang.IgniteException: IGN-CMN-65535
> TraceId:c7b27181-0977-4925-b0ba-fa07d8a3bebe
> org.apache.ignite.lang.IgniteException: IGN-CMN-65535
> TraceId:c7b27181-0977-4925-b0ba-fa07d8a3bebe Unable to start [node=node-3]
> at
> java.base/java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:395)
> at
> java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1999)
> at
> org.apache.ignite.internal.app.IgniteRunner.main(IgniteRunner.java:74)
> Caused by: org.apache.ignite.lang.IgniteException: IGN-CMN-65535
> TraceId:c7b27181-0977-4925-b0ba-fa07d8a3bebe
> org.apache.ignite.lang.IgniteException: IGN-CMN-65535
> TraceId:c7b27181-0977-4925-b0ba-fa07d8a3bebe Unable to start [node=node-3]
> at
> org.apache.ignite.internal.app.IgnitionImpl.handleStartException(IgnitionImpl.java:224)
> at
> org.apache.ignite.internal.app.IgnitionImpl.lambda$doStart$1(IgnitionImpl.java:205)
> at
> java.base/java.util.concurrent.CompletableFuture.uniHandle(CompletableFuture.java:930)
> at
> java.base/java.util.concurrent.CompletableFuture$UniHandle.tryFire(CompletableFuture.java:907)
> at
> java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
> at
> java.base/java.util.concurrent.CompletableFuture.postFire(CompletableFuture.java:610)
> at
> java.base/java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:840)
> at
> java.base/java.util.concurrent.CompletableFuture$Completion.exec(CompletableFuture.java:479)
> at
> java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:290)
> at
> java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1020)
> at
> java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1656)
> at
> java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1594)
> at
> java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:183)
> Caused by: java.util.co
[jira] [Updated] (IGNITE-22586) .NET: Fix build failure due to ComputeTaskSessionTest
[
https://issues.apache.org/jira/browse/IGNITE-22586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Shishkov updated IGNITE-22586:
---
Description:
We need fix build failure of .NET project in Windows. Currently it fails with
an error:
{code}
dotnet build Apache.Ignite.sln
...
C:\BuildAgent\work\7bc1c54bc719b67c\modules\platforms\dotnet\Apache.Ignite.Core.Tests\Compute\ComputeTaskSessionTest.cs(103,44):
error CS0305: Using the generic type 'KeyValuePair' requires 2
type arguments
[C:\BuildAgent\work\7bc1c54bc719b67c\modules\platforms\dotnet\Apache.Ignite.Core.Tests\Apache.Ignite.Core.Tests.csproj]
{code}
Full build log from TC:
[^Ignite_Tests_2.x_JDK_8_11_Platform_.NET_Windows_10531.log.zip]
Link to build log:
https://ci2.ignite.apache.org/buildConfiguration/IgniteTests24Java8_PlatformNetWindows/7930403?hideTestsFromDependencies=false&hideProblemsFromDependencies=false&expandBuildDeploymentsSection=false&expandBuildProblemsSection=true&showLog=7930403_153_113&logFilter=debug&logView=flowAware
was:
We need fix build failure of .NET project in Windows. Currently it fails woth
an error:
{code}
dotnet build Apache.Ignite.sln
...
C:\BuildAgent\work\7bc1c54bc719b67c\modules\platforms\dotnet\Apache.Ignite.Core.Tests\Compute\ComputeTaskSessionTest.cs(103,44):
error CS0305: Using the generic type 'KeyValuePair' requires 2
type arguments
[C:\BuildAgent\work\7bc1c54bc719b67c\modules\platforms\dotnet\Apache.Ignite.Core.Tests\Apache.Ignite.Core.Tests.csproj]
{code}
Full build log from TC:
[^Ignite_Tests_2.x_JDK_8_11_Platform_.NET_Windows_10531.log.zip]
Link to build log:
https://ci2.ignite.apache.org/buildConfiguration/IgniteTests24Java8_PlatformNetWindows/7930403?hideTestsFromDependencies=false&hideProblemsFromDependencies=false&expandBuildDeploymentsSection=false&expandBuildProblemsSection=true&showLog=7930403_153_113&logFilter=debug&logView=flowAware
> .NET: Fix build failure due to ComputeTaskSessionTest
> -
>
> Key: IGNITE-22586
> URL: https://issues.apache.org/jira/browse/IGNITE-22586
> Project: Ignite
> Issue Type: Bug
>Reporter: Ilya Shishkov
>Assignee: Ilya Shishkov
>Priority: Critical
> Labels: .net, ise, platforms
> Fix For: 2.17
>
> Attachments:
> Ignite_Tests_2.x_JDK_8_11_Platform_.NET_Windows_10531.log.zip
>
>
> We need fix build failure of .NET project in Windows. Currently it fails with
> an error:
> {code}
> dotnet build Apache.Ignite.sln
> ...
> C:\BuildAgent\work\7bc1c54bc719b67c\modules\platforms\dotnet\Apache.Ignite.Core.Tests\Compute\ComputeTaskSessionTest.cs(103,44):
> error CS0305: Using the generic type 'KeyValuePair' requires 2
> type arguments
> [C:\BuildAgent\work\7bc1c54bc719b67c\modules\platforms\dotnet\Apache.Ignite.Core.Tests\Apache.Ignite.Core.Tests.csproj]
> {code}
> Full build log from TC:
> [^Ignite_Tests_2.x_JDK_8_11_Platform_.NET_Windows_10531.log.zip]
> Link to build log:
> https://ci2.ignite.apache.org/buildConfiguration/IgniteTests24Java8_PlatformNetWindows/7930403?hideTestsFromDependencies=false&hideProblemsFromDependencies=false&expandBuildDeploymentsSection=false&expandBuildProblemsSection=true&showLog=7930403_153_113&logFilter=debug&logView=flowAware
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-22611) SQL. Statement should not extends AutoClosable
[ https://issues.apache.org/jira/browse/IGNITE-22611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov reassigned IGNITE-22611: - Assignee: Andrey Mashenkov > SQL. Statement should not extends AutoClosable > --- > > Key: IGNITE-22611 > URL: https://issues.apache.org/jira/browse/IGNITE-22611 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Andrey Mashenkov >Assignee: Andrey Mashenkov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > Statement doesn't hold any resources, but AutoClosable interface assume using > try-with-resources. > A try-with-resources block forces user to catch the exception, because of > `close()` method signature. > However, all of this make no sense, single implementation has empty `close()` > method. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22599) Exception inside RAFT listener does not invoke falure handler
[
https://issues.apache.org/jira/browse/IGNITE-22599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Lapin updated IGNITE-22599:
-
Description:
h3. Motivation
An exception that is thrown during handling RAFT command cannot be recovered,
because a RAFT storage is already corrupted. This is a reason to call Falure
handler:
{code:java}
failureProcessor.process(new FailureContext(CRITICAL_ERROR, err));
{code}
Currently, I do not see any FH invokation in the log, but many exception has
been thrown.
h3. Definition of done
FH is invoked in the case where RAFT listener fails.
h3. Implementation Notes
* Failure handler should be invoked in case of critical exceptions while
onWrite processing onRead processing, snapshotting and snapshot installation.
* While testing, it's required to test all CMG MG and Partition listeners.
* In order to ease testing, it worth implementing a test failure handler in
order to detect that it was triggered.
was:
h3. Motivation
An exception that is thrown during handling RAFT command cannot be recovered,
because a RAFT storage is already corrupted. This is a reason to call Falure
handler:
{code:java}
failureProcessor.process(new FailureContext(CRITICAL_ERROR, err));
{code}
Currently, I do not see any FH invokation in the log, but many exception has
been thrown.
h3. Definition of done
FH is invoked in the case where RAFT listener fails.
> Exception inside RAFT listener does not invoke falure handler
> -
>
> Key: IGNITE-22599
> URL: https://issues.apache.org/jira/browse/IGNITE-22599
> Project: Ignite
> Issue Type: Bug
>Reporter: Vladislav Pyatkov
>Priority: Major
> Labels: ignite-3
> Attachments:
> poc-tester-SERVER-192.168.1.41-id-0-2024-06-27-09-14-17-client.log.2
>
>
> h3. Motivation
> An exception that is thrown during handling RAFT command cannot be recovered,
> because a RAFT storage is already corrupted. This is a reason to call Falure
> handler:
> {code:java}
> failureProcessor.process(new FailureContext(CRITICAL_ERROR, err));
> {code}
> Currently, I do not see any FH invokation in the log, but many exception has
> been thrown.
> h3. Definition of done
> FH is invoked in the case where RAFT listener fails.
> h3. Implementation Notes
> * Failure handler should be invoked in case of critical exceptions while
> onWrite processing onRead processing, snapshotting and snapshot installation.
> * While testing, it's required to test all CMG MG and Partition listeners.
> * In order to ease testing, it worth implementing a test failure handler in
> order to detect that it was triggered.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-22611) SQL. Statement should not extends AutoClosable
[ https://issues.apache.org/jira/browse/IGNITE-22611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Iurii Gerzhedovich updated IGNITE-22611: Component/s: sql > SQL. Statement should not extends AutoClosable > --- > > Key: IGNITE-22611 > URL: https://issues.apache.org/jira/browse/IGNITE-22611 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Andrey Mashenkov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > Statement doesn't hold any resources, but AutoClosable interface assume using > try-with-resources. > A try-with-resources block forces user to catch the exception, because of > `close()` method signature. > However, all of this make no sense, single implementation has empty `close()` > method. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22611) SQL. Statement should not extends AutoClosable
[ https://issues.apache.org/jira/browse/IGNITE-22611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Iurii Gerzhedovich updated IGNITE-22611: Labels: ignite-3 (was: ) > SQL. Statement should not extends AutoClosable > --- > > Key: IGNITE-22611 > URL: https://issues.apache.org/jira/browse/IGNITE-22611 > Project: Ignite > Issue Type: Improvement >Reporter: Andrey Mashenkov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > Statement doesn't hold any resources, but AutoClosable interface assume using > try-with-resources. > A try-with-resources block forces user to catch the exception, because of > `close()` method signature. > However, all of this make no sense, single implementation has empty `close()` > method. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22611) SQL. Statement should not extends AutoClosable
Andrey Mashenkov created IGNITE-22611: - Summary: SQL. Statement should not extends AutoClosable Key: IGNITE-22611 URL: https://issues.apache.org/jira/browse/IGNITE-22611 Project: Ignite Issue Type: Improvement Reporter: Andrey Mashenkov Fix For: 3.0.0-beta2 Statement doesn't hold any resources, but AutoClosable interface assume using try-with-resources. A try-with-resources block forces user to catch the exception, because of `close()` method signature. However, all of this make no sense, single implementation has empty `close()` method. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-22597) Exception trace id is not propagated from RAFT listener
[
https://issues.apache.org/jira/browse/IGNITE-22597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17860812#comment-17860812
]
Mirza Aliev commented on IGNITE-22597:
--
[~ktkale...@gridgain.com] could you please clarify, what specifically you want
to be fixed within this ticket?
> Exception trace id is not propagated from RAFT listener
> ---
>
> Key: IGNITE-22597
> URL: https://issues.apache.org/jira/browse/IGNITE-22597
> Project: Ignite
> Issue Type: Bug
>Reporter: Vladislav Pyatkov
>Priority: Major
> Labels: ignite-3
> Attachments: error_log.txt
>
>
> h3. Motivation
> The trace id is generated at the place where the original exception was
> created and should be propogated to other derevatives. Right now, we send
> only an exception message and class name to the RAFT listener response.
> {code:java}
> private void sendSMError(RpcContext ctx, Throwable th, boolean compacted) {
> RpcRequests.SMErrorResponse resp = factory.sMErrorResponse()
> .error(compacted ? new SMCompactedThrowable(th) : new
> SMFullThrowable(th))
> .build();
> ctx.sendResponse(resp);
> LOG.info("Error occurred on a user's state machine", th);
> }
> {code}
> Hence, we cannot restore the trace id and create an exception with a new
> trace id:
> {code:java}
> Throwable restoredTh = (Throwable)
> Class.forName(compactedThrowable.throwableClassName())
> .getConstructor(String.class)
> .newInstance(compactedThrowable.throwableMessage());
> fut.completeExceptionally(restoredTh);
> {code}
> h3. Definition of done
> * Both attached logs should be logged with the same trace id.
> * Massage in the RAFT listener should be logged in error (or warning) level.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (IGNITE-22603) Add InetSocketAddress caching for DefaultMessagingService
[ https://issues.apache.org/jira/browse/IGNITE-22603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Tkalenko resolved IGNITE-22603. -- Fix Version/s: 3.0.0-beta2 Resolution: Fixed > Add InetSocketAddress caching for DefaultMessagingService > - > > Key: IGNITE-22603 > URL: https://issues.apache.org/jira/browse/IGNITE-22603 > Project: Ignite > Issue Type: Improvement >Reporter: Kirill Tkalenko >Assignee: Kirill Tkalenko >Priority: Major > Labels: ignite3, ignite3_performance > Fix For: 3.0.0-beta2 > > > As a result of analyzing the flamegraph of sending messages between two nodes > through *org.apache.ignite.internal.network.DefaultMessagingService*, I > noticed that we can use *java.net.InetSocketAddress* caching and not create > it every time, which increased the number of messages sent by about 10% on my > PC. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (IGNITE-22527) C++ 3.0: Add parameter object to Compute API
[ https://issues.apache.org/jira/browse/IGNITE-22527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17860802#comment-17860802 ] Igor Sapego edited comment on IGNITE-22527 at 6/28/24 12:19 PM: Ready for review. [~dzabotlin], can you take a look please? was (Author: isapego): Ready for review. [~ptupitsyn], [~dzabotlin], can you guys take a look please? > C++ 3.0: Add parameter object to Compute API > > > Key: IGNITE-22527 > URL: https://issues.apache.org/jira/browse/IGNITE-22527 > Project: Ignite > Issue Type: Improvement > Components: compute, platforms >Reporter: Igor Sapego >Assignee: Igor Sapego >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > *compute* methods have too many arguments. The following part repeats and can > be combined into a single argument *job_descriptor*: *units*, > *job_class_name*, *options* -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-22364) Zip script improvement
[ https://issues.apache.org/jira/browse/IGNITE-22364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17860797#comment-17860797 ] Mikhail Pochatkin commented on IGNITE-22364: Merged to main 8a1a15a0d77bc3dffd7c1f81eae0a9dc4fd826ff > Zip script improvement > -- > > Key: IGNITE-22364 > URL: https://issues.apache.org/jira/browse/IGNITE-22364 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr >Assignee: Maksim Myskov >Priority: Major > Labels: ignite-3 > Time Spent: 10m > Remaining Estimate: 0h > > After several discussions, it was decided to redesign the Ignite launch > architecture for zip distribution. > At the moment, launching is only possible in daemon mode; this needs to be > changed to launch within the terminal process. > Currently the script for Windows works this way, but we need to do exactly > the same for Unix systems. > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22588) AI3 JDBC performance is low
[ https://issues.apache.org/jira/browse/IGNITE-22588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Orlov updated IGNITE-22588: -- Ignite Flags: (was: Docs Required,Release Notes Required) > AI3 JDBC performance is low > --- > > Key: IGNITE-22588 > URL: https://issues.apache.org/jira/browse/IGNITE-22588 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Assignee: Konstantin Orlov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > Despite resolving IGNITE-22413 we still have bad JDBC performance. > Let's investigate the reason and prepare plan to improve it -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22588) AI3 JDBC performance is low
[ https://issues.apache.org/jira/browse/IGNITE-22588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Orlov updated IGNITE-22588: -- Fix Version/s: 3.0.0-beta2 > AI3 JDBC performance is low > --- > > Key: IGNITE-22588 > URL: https://issues.apache.org/jira/browse/IGNITE-22588 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Assignee: Konstantin Orlov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > Despite resolving IGNITE-22413 we still have bad JDBC performance. > Let's investigate the reason and prepare plan to improve it -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-22610) Fix flaky NettyServerTest
[
https://issues.apache.org/jira/browse/IGNITE-22610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko reassigned IGNITE-22610:
Assignee: Kirill Tkalenko
> Fix flaky NettyServerTest
> -
>
> Key: IGNITE-22610
> URL: https://issues.apache.org/jira/browse/IGNITE-22610
> Project: Ignite
> Issue Type: Bug
>Reporter: Kirill Tkalenko
>Assignee: Kirill Tkalenko
>Priority: Major
> Labels: ignite-3
>
> Fix flaky *org.apache.ignite.internal.network.netty.NettyServerTest*.
> [Tc
> link|https://ci.ignite.apache.org/viewLog.html?buildId=8246027&buildTypeId=ApacheIgnite3xGradle_Test_RunAllTests&fromSakuraUI=true].
> {noformat}
> org.opentest4j.AssertionFailedError
> at
> app//org.junit.jupiter.api.AssertionUtils.fail(AssertionUtils.java:46)
> at app//org.junit.jupiter.api.Assertions.fail(Assertions.java:161)
> at
> app//org.apache.ignite.internal.network.netty.NettyServerTest.getServer(NettyServerTest.java:314)
> at
> app//org.apache.ignite.internal.network.netty.NettyServerTest.testStartTwice(NettyServerTest.java:149)
> at java.base@11.0.17/java.lang.reflect.Method.invoke(Method.java:566)
> at java.base@11.0.17/java.util.ArrayList.forEach(ArrayList.java:1541)
> at java.base@11.0.17/java.util.ArrayList.forEach(ArrayList.java:1541)
> Caused by: java.util.concurrent.ExecutionException:
> org.apache.ignite.lang.IgniteException: IGN-NETWORK-2
> TraceId:bec147ac-e70d-4713-ab05-2f197822a718 Port 47500 is not available.
> at
> java.base/java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:395)
> at
> java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2022)
> at
> org.apache.ignite.internal.network.netty.NettyServerTest.getServer(NettyServerTest.java:311)
> ... 4 more
> Caused by: org.apache.ignite.lang.IgniteException: IGN-NETWORK-2
> TraceId:bec147ac-e70d-4713-ab05-2f197822a718 Port 47500 is not available.
> at
> app//org.apache.ignite.internal.network.netty.NettyServer.lambda$start$0(NettyServer.java:159)
> at
> app//io.netty.util.concurrent.DefaultPromise.notifyListener0(DefaultPromise.java:590)
> at
> app//io.netty.util.concurrent.DefaultPromise.notifyListenersNow(DefaultPromise.java:557)
> at
> app//io.netty.util.concurrent.DefaultPromise.notifyListeners(DefaultPromise.java:492)
> at
> app//io.netty.util.concurrent.DefaultPromise.setValue0(DefaultPromise.java:636)
> at
> app//io.netty.util.concurrent.DefaultPromise.setFailure0(DefaultPromise.java:629)
> at
> app//io.netty.util.concurrent.DefaultPromise.tryFailure(DefaultPromise.java:118)
> at
> app//io.netty.channel.AbstractChannel$AbstractUnsafe.safeSetFailure(AbstractChannel.java:997)
> at
> app//io.netty.channel.AbstractChannel$AbstractUnsafe.bind(AbstractChannel.java:563)
> at
> app//io.netty.channel.DefaultChannelPipeline$HeadContext.bind(DefaultChannelPipeline.java:1331)
> at
> app//io.netty.channel.AbstractChannelHandlerContext.invokeBind(AbstractChannelHandlerContext.java:600)
> at
> app//io.netty.channel.AbstractChannelHandlerContext.bind(AbstractChannelHandlerContext.java:579)
> at
> app//io.netty.channel.DefaultChannelPipeline.bind(DefaultChannelPipeline.java:972)
> at app//io.netty.channel.AbstractChannel.bind(AbstractChannel.java:259)
> at
> app//io.netty.bootstrap.AbstractBootstrap$2.run(AbstractBootstrap.java:380)
> at
> app//io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java:173)
> at
> app//io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:166)
> at
> app//io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:469)
> at app//io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:569)
> at
> app//io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:994)
> at
> app//io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
> at
> app//io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.base@11.0.17/java.lang.Thread.run(Thread.java:834)
> Caused by: java.net.BindException: Address already in use
> at java.base/sun.nio.ch.Net.bind0(Native Method)
> at java.base/sun.nio.ch.Net.bind(Net.java:459)
> at java.base/sun.nio.ch.Net.bind(Net.java:448)
> at
> java.base/sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:227)
> at
> io.netty.channel.socket.nio.NioServerSocketChannel.doBind(NioServerSocketChannel.java:141)
> at
> io.netty.channel.AbstractChannel$AbstractUnsafe.bind(AbstractChannel.java:561)
> ... 14 more
> {nof
[jira] [Commented] (IGNITE-22426) Move DeploymentUnit from compute to deployment package
[ https://issues.apache.org/jira/browse/IGNITE-22426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17860788#comment-17860788 ] Mikhail Pochatkin commented on IGNITE-22426: Merged to main fa931b1c02d0dd472f27d42329676513a4b2126c > Move DeploymentUnit from compute to deployment package > -- > > Key: IGNITE-22426 > URL: https://issues.apache.org/jira/browse/IGNITE-22426 > Project: Ignite > Issue Type: Improvement > Components: compute >Affects Versions: 3.0.0-beta1 >Reporter: Pavel Tupitsyn >Assignee: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > *DeploymentUnit* is not only used in Compute API, but also Streamer and > potentially other places in the future. > Move it from *compute* package to *deployment* -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22609) MetaStorageListener can access KeyValueStorage after it had been closed
[
https://issues.apache.org/jira/browse/IGNITE-22609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Polovtsev updated IGNITE-22609:
-
Description:
See the attached stacktrace for details. Looks like we are trying to process a
read command in {{MetaStorageListener}} while the underlying storage has
already been closed.
This may be happening because looks like we don't guarantee that
{{RaftManager#stopRaftNodes}} waits for all read commands to be processed. If
this is the case, a possible solution would be to add a busy lock either to the
{{MetaStorageListener}} or to the {{KeyValueStorage}}. But this needs to be
verified first.
Also, it must be checked if similar Raft Listeners in other components are
affected by the same issue.
was:See the attached stacktrace for details
> MetaStorageListener can access KeyValueStorage after it had been closed
> ---
>
> Key: IGNITE-22609
> URL: https://issues.apache.org/jira/browse/IGNITE-22609
> Project: Ignite
> Issue Type: Bug
>Reporter: Aleksandr Polovtsev
>Priority: Major
> Labels: ignite-3
> Attachments: hs_err_pid2936001.log
>
>
> See the attached stacktrace for details. Looks like we are trying to process
> a read command in {{MetaStorageListener}} while the underlying storage has
> already been closed.
> This may be happening because looks like we don't guarantee that
> {{RaftManager#stopRaftNodes}} waits for all read commands to be processed. If
> this is the case, a possible solution would be to add a busy lock either to
> the {{MetaStorageListener}} or to the {{KeyValueStorage}}. But this needs to
> be verified first.
> Also, it must be checked if similar Raft Listeners in other components are
> affected by the same issue.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-22609) MetaStorageListener can access KeyValueStorage after it had been closed
[ https://issues.apache.org/jira/browse/IGNITE-22609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Polovtsev updated IGNITE-22609: - Attachment: hs_err_pid2936001.log > MetaStorageListener can access KeyValueStorage after it had been closed > --- > > Key: IGNITE-22609 > URL: https://issues.apache.org/jira/browse/IGNITE-22609 > Project: Ignite > Issue Type: Bug >Reporter: Aleksandr Polovtsev >Priority: Major > Labels: ignite-3 > Attachments: hs_err_pid2936001.log > > > See the attached stacktrace for details -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22609) MetaStorageListener can access KeyValueStorage after it had been closed
[ https://issues.apache.org/jira/browse/IGNITE-22609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Polovtsev updated IGNITE-22609: - Attachment: (was: hs_err_pid2936001.log) > MetaStorageListener can access KeyValueStorage after it had been closed > --- > > Key: IGNITE-22609 > URL: https://issues.apache.org/jira/browse/IGNITE-22609 > Project: Ignite > Issue Type: Bug >Reporter: Aleksandr Polovtsev >Priority: Major > Labels: ignite-3 > > See the attached stacktrace for details -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22609) MetaStorageListener can access KeyValueStorage after it had been closed
[ https://issues.apache.org/jira/browse/IGNITE-22609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Polovtsev updated IGNITE-22609: - Attachment: hs_err_pid2936001.log > MetaStorageListener can access KeyValueStorage after it had been closed > --- > > Key: IGNITE-22609 > URL: https://issues.apache.org/jira/browse/IGNITE-22609 > Project: Ignite > Issue Type: Bug >Reporter: Aleksandr Polovtsev >Priority: Major > Labels: ignite-3 > > See the attached stacktrace for details -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22610) Fix flaky NettyServerTest
Kirill Tkalenko created IGNITE-22610:
Summary: Fix flaky NettyServerTest
Key: IGNITE-22610
URL: https://issues.apache.org/jira/browse/IGNITE-22610
Project: Ignite
Issue Type: Bug
Reporter: Kirill Tkalenko
Fix flaky *org.apache.ignite.internal.network.netty.NettyServerTest*.
[Tc
link|https://ci.ignite.apache.org/viewLog.html?buildId=8246027&buildTypeId=ApacheIgnite3xGradle_Test_RunAllTests&fromSakuraUI=true].
{noformat}
org.opentest4j.AssertionFailedError
at
app//org.junit.jupiter.api.AssertionUtils.fail(AssertionUtils.java:46)
at app//org.junit.jupiter.api.Assertions.fail(Assertions.java:161)
at
app//org.apache.ignite.internal.network.netty.NettyServerTest.getServer(NettyServerTest.java:314)
at
app//org.apache.ignite.internal.network.netty.NettyServerTest.testStartTwice(NettyServerTest.java:149)
at java.base@11.0.17/java.lang.reflect.Method.invoke(Method.java:566)
at java.base@11.0.17/java.util.ArrayList.forEach(ArrayList.java:1541)
at java.base@11.0.17/java.util.ArrayList.forEach(ArrayList.java:1541)
Caused by: java.util.concurrent.ExecutionException:
org.apache.ignite.lang.IgniteException: IGN-NETWORK-2
TraceId:bec147ac-e70d-4713-ab05-2f197822a718 Port 47500 is not available.
at
java.base/java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:395)
at
java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2022)
at
org.apache.ignite.internal.network.netty.NettyServerTest.getServer(NettyServerTest.java:311)
... 4 more
Caused by: org.apache.ignite.lang.IgniteException: IGN-NETWORK-2
TraceId:bec147ac-e70d-4713-ab05-2f197822a718 Port 47500 is not available.
at
app//org.apache.ignite.internal.network.netty.NettyServer.lambda$start$0(NettyServer.java:159)
at
app//io.netty.util.concurrent.DefaultPromise.notifyListener0(DefaultPromise.java:590)
at
app//io.netty.util.concurrent.DefaultPromise.notifyListenersNow(DefaultPromise.java:557)
at
app//io.netty.util.concurrent.DefaultPromise.notifyListeners(DefaultPromise.java:492)
at
app//io.netty.util.concurrent.DefaultPromise.setValue0(DefaultPromise.java:636)
at
app//io.netty.util.concurrent.DefaultPromise.setFailure0(DefaultPromise.java:629)
at
app//io.netty.util.concurrent.DefaultPromise.tryFailure(DefaultPromise.java:118)
at
app//io.netty.channel.AbstractChannel$AbstractUnsafe.safeSetFailure(AbstractChannel.java:997)
at
app//io.netty.channel.AbstractChannel$AbstractUnsafe.bind(AbstractChannel.java:563)
at
app//io.netty.channel.DefaultChannelPipeline$HeadContext.bind(DefaultChannelPipeline.java:1331)
at
app//io.netty.channel.AbstractChannelHandlerContext.invokeBind(AbstractChannelHandlerContext.java:600)
at
app//io.netty.channel.AbstractChannelHandlerContext.bind(AbstractChannelHandlerContext.java:579)
at
app//io.netty.channel.DefaultChannelPipeline.bind(DefaultChannelPipeline.java:972)
at app//io.netty.channel.AbstractChannel.bind(AbstractChannel.java:259)
at
app//io.netty.bootstrap.AbstractBootstrap$2.run(AbstractBootstrap.java:380)
at
app//io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java:173)
at
app//io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:166)
at
app//io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:469)
at app//io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:569)
at
app//io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:994)
at
app//io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
at
app//io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.base@11.0.17/java.lang.Thread.run(Thread.java:834)
Caused by: java.net.BindException: Address already in use
at java.base/sun.nio.ch.Net.bind0(Native Method)
at java.base/sun.nio.ch.Net.bind(Net.java:459)
at java.base/sun.nio.ch.Net.bind(Net.java:448)
at
java.base/sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:227)
at
io.netty.channel.socket.nio.NioServerSocketChannel.doBind(NioServerSocketChannel.java:141)
at
io.netty.channel.AbstractChannel$AbstractUnsafe.bind(AbstractChannel.java:561)
... 14 more
{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-22609) MetaStorageListener can access KeyValueStorage after it had been closed
[ https://issues.apache.org/jira/browse/IGNITE-22609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Polovtsev updated IGNITE-22609: - Description: See the attached stacktrace for details > MetaStorageListener can access KeyValueStorage after it had been closed > --- > > Key: IGNITE-22609 > URL: https://issues.apache.org/jira/browse/IGNITE-22609 > Project: Ignite > Issue Type: Bug >Reporter: Aleksandr Polovtsev >Priority: Major > Labels: ignite-3 > > See the attached stacktrace for details -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-22603) Add InetSocketAddress caching for DefaultMessagingService
[ https://issues.apache.org/jira/browse/IGNITE-22603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Tkalenko reassigned IGNITE-22603: Assignee: Kirill Tkalenko > Add InetSocketAddress caching for DefaultMessagingService > - > > Key: IGNITE-22603 > URL: https://issues.apache.org/jira/browse/IGNITE-22603 > Project: Ignite > Issue Type: Improvement >Reporter: Kirill Tkalenko >Assignee: Kirill Tkalenko >Priority: Major > Labels: ignite3, ignite3_performance > > As a result of analyzing the flamegraph of sending messages between two nodes > through *org.apache.ignite.internal.network.DefaultMessagingService*, I > noticed that we can use *java.net.InetSocketAddress* caching and not create > it every time, which increased the number of messages sent by about 10% on my > PC. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22609) MetaStorageListener can access KeyValueStorage after it had been closed
Aleksandr Polovtsev created IGNITE-22609: Summary: MetaStorageListener can access KeyValueStorage after it had been closed Key: IGNITE-22609 URL: https://issues.apache.org/jira/browse/IGNITE-22609 Project: Ignite Issue Type: Bug Reporter: Aleksandr Polovtsev -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22608) MetaStorageListener can access KeyValueStorage after it had been closed
Aleksandr Polovtsev created IGNITE-22608: Summary: MetaStorageListener can access KeyValueStorage after it had been closed Key: IGNITE-22608 URL: https://issues.apache.org/jira/browse/IGNITE-22608 Project: Ignite Issue Type: Bug Reporter: Aleksandr Polovtsev -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22607) IEP-119 Binary infrastructure modularization
Nikolay Izhikov created IGNITE-22607: Summary: IEP-119 Binary infrastructure modularization Key: IGNITE-22607 URL: https://issues.apache.org/jira/browse/IGNITE-22607 Project: Ignite Issue Type: Task Components: binary Reporter: Nikolay Izhikov Assignee: Nikolay Izhikov https://cwiki.apache.org/confluence/display/IGNITE/IEP-119+Binary+infrastructure+modularization -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-22602) .NET: Use single argument in Compute API
[ https://issues.apache.org/jira/browse/IGNITE-22602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17860766#comment-17860766 ] Pavel Tupitsyn commented on IGNITE-22602: - Branch: https://github.com/ptupitsyn/ignite-3/tree/IGNITE-22478-dotnet-api Might be merged as part of IGNITE-22478 > .NET: Use single argument in Compute API > > > Key: IGNITE-22602 > URL: https://issues.apache.org/jira/browse/IGNITE-22602 > Project: Ignite > Issue Type: Improvement > Components: compute, platforms, thin client >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Blocker > Fix For: 3.0.0-beta2 > > > See IGNITE-22478, update .NET API accordingly. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-22303) Sql. Retry operation when plan gets outdated by the time of execution
[ https://issues.apache.org/jira/browse/IGNITE-22303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov reassigned IGNITE-22303: - Assignee: Andrey Mashenkov > Sql. Retry operation when plan gets outdated by the time of execution > - > > Key: IGNITE-22303 > URL: https://issues.apache.org/jira/browse/IGNITE-22303 > Project: Ignite > Issue Type: Bug > Components: sql >Reporter: Konstantin Orlov >Assignee: Andrey Mashenkov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > In IGNITE-22263 start of the transaction was moved to execution phase. This > may cause situation, when plan gets outdated by the time of execution. Such > cases should be detected and handled properly (by retrying operation one more > time). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22564) Decouple metastore and CMG RAFT log from data partitions RAFT log
[ https://issues.apache.org/jira/browse/IGNITE-22564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Sizov updated IGNITE-22564: --- Summary: Decouple metastore and CMG RAFT log from data partitions RAFT log (was: Decouple meta store RAFT log from data partitions RAFT log) > Decouple metastore and CMG RAFT log from data partitions RAFT log > - > > Key: IGNITE-22564 > URL: https://issues.apache.org/jira/browse/IGNITE-22564 > Project: Ignite > Issue Type: Improvement >Reporter: Vladimir Pligin >Priority: Major > Labels: ignite-3 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-22588) AI3 JDBC performance is low
[ https://issues.apache.org/jira/browse/IGNITE-22588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Iurii Gerzhedovich reassigned IGNITE-22588: --- Assignee: Konstantin Orlov > AI3 JDBC performance is low > --- > > Key: IGNITE-22588 > URL: https://issues.apache.org/jira/browse/IGNITE-22588 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Iurii Gerzhedovich >Assignee: Konstantin Orlov >Priority: Major > Labels: ignite-3 > > Despite resolving IGNITE-22413 we still have bad JDBC performance. > Let's investigate the reason and prepare plan to improve it -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22606) Add an option to update cluster configuration from file
Igor Gusev created IGNITE-22606: --- Summary: Add an option to update cluster configuration from file Key: IGNITE-22606 URL: https://issues.apache.org/jira/browse/IGNITE-22606 Project: Ignite Issue Type: Task Reporter: Igor Gusev Updating cluster configuration often requires updating multiple configuration properties at once. It would be convenient to be able to load a file instead of using a string to update the configuration. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-22597) Exception trace id is not propagated from RAFT listener
[
https://issues.apache.org/jira/browse/IGNITE-22597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17860734#comment-17860734
]
Kirill Tkalenko commented on IGNITE-22597:
--
This also needs to be fixed.
{noformat}
Caused by: org.apache.ignite.internal.storage.StorageException: IGN-STORAGE-1
TraceId:66de6dce-e425-4815-b910-295bc21f1172 Error while executing
addWriteCommitted: [rowId=RowId [partitionId=8,
uuid=0d5b2f79-3586-4ecc-a248-dcbb74926f78], tableId=10, partitionId=8]
at
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at
java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at
java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)
at
org.apache.ignite.internal.raft.RaftGroupServiceImpl.handleSmErrorResponse(RaftGroupServiceImpl.java:682)
... 27 more
{noformat}
> Exception trace id is not propagated from RAFT listener
> ---
>
> Key: IGNITE-22597
> URL: https://issues.apache.org/jira/browse/IGNITE-22597
> Project: Ignite
> Issue Type: Bug
>Reporter: Vladislav Pyatkov
>Priority: Major
> Labels: ignite-3
> Attachments: error_log.txt
>
>
> h3. Motivation
> The trace id is generated at the place where the original exception was
> created and should be propogated to other derevatives. Right now, we send
> only an exception message and class name to the RAFT listener response.
> {code:java}
> private void sendSMError(RpcContext ctx, Throwable th, boolean compacted) {
> RpcRequests.SMErrorResponse resp = factory.sMErrorResponse()
> .error(compacted ? new SMCompactedThrowable(th) : new
> SMFullThrowable(th))
> .build();
> ctx.sendResponse(resp);
> LOG.info("Error occurred on a user's state machine", th);
> }
> {code}
> Hence, we cannot restore the trace id and create an exception with a new
> trace id:
> {code:java}
> Throwable restoredTh = (Throwable)
> Class.forName(compactedThrowable.throwableClassName())
> .getConstructor(String.class)
> .newInstance(compactedThrowable.throwableMessage());
> fut.completeExceptionally(restoredTh);
> {code}
> h3. Definition of done
> * Both attached logs should be logged with the same trace id.
> * Massage in the RAFT listener should be logged in error (or warning) level.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-22605) Wrong certificate chain might lead to split brain
[ https://issues.apache.org/jira/browse/IGNITE-22605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Timonin updated IGNITE-22605: Labels: ise (was: ) > Wrong certificate chain might lead to split brain > - > > Key: IGNITE-22605 > URL: https://issues.apache.org/jira/browse/IGNITE-22605 > Project: Ignite > Issue Type: Bug >Reporter: Maksim Timonin >Assignee: Maksim Timonin >Priority: Major > Labels: ise > > There is a flaky test > TcpDiscoverySslTrustedUntrustedTest#testMismatchingCaFirst > Connection might fail on writing to the open socket while writing header or > message. It might happen due to a receipent ultimately close connection on > SSL handshake. The sender make a wrong decision that there is no cluster at > all and it's a first node. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22605) Wrong certificate chain might lead to split brain
[ https://issues.apache.org/jira/browse/IGNITE-22605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Timonin updated IGNITE-22605: Ignite Flags: Release Notes Required (was: Docs Required,Release Notes Required) > Wrong certificate chain might lead to split brain > - > > Key: IGNITE-22605 > URL: https://issues.apache.org/jira/browse/IGNITE-22605 > Project: Ignite > Issue Type: Bug >Reporter: Maksim Timonin >Assignee: Maksim Timonin >Priority: Major > Labels: ise > > There is a flaky test > TcpDiscoverySslTrustedUntrustedTest#testMismatchingCaFirst > Connection might fail on writing to the open socket while writing header or > message. It might happen due to a receipent ultimately close connection on > SSL handshake. The sender make a wrong decision that there is no cluster at > all and it's a first node. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22605) Wrong certificate chain might lead to split brain
[ https://issues.apache.org/jira/browse/IGNITE-22605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Timonin updated IGNITE-22605: Fix Version/s: 2.17 > Wrong certificate chain might lead to split brain > - > > Key: IGNITE-22605 > URL: https://issues.apache.org/jira/browse/IGNITE-22605 > Project: Ignite > Issue Type: Bug >Reporter: Maksim Timonin >Assignee: Maksim Timonin >Priority: Major > Labels: ise > Fix For: 2.17 > > > There is a flaky test > TcpDiscoverySslTrustedUntrustedTest#testMismatchingCaFirst > Connection might fail on writing to the open socket while writing header or > message. It might happen due to a receipent ultimately close connection on > SSL handshake. The sender make a wrong decision that there is no cluster at > all and it's a first node. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-22605) Wrong certificate chain might lead to split brain
[ https://issues.apache.org/jira/browse/IGNITE-22605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Timonin reassigned IGNITE-22605: --- Assignee: Maksim Timonin > Wrong certificate chain might lead to split brain > - > > Key: IGNITE-22605 > URL: https://issues.apache.org/jira/browse/IGNITE-22605 > Project: Ignite > Issue Type: Bug >Reporter: Maksim Timonin >Assignee: Maksim Timonin >Priority: Major > > There is a flaky test > TcpDiscoverySslTrustedUntrustedTest#testMismatchingCaFirst > Connection might fail on writing to the open socket while writing header or > message. It might happen due to a receipent ultimately close connection on > SSL handshake. The sender make a wrong decision that there is no cluster at > all and it's a first node. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22605) Wrong certificate chain might lead to split brain
Maksim Timonin created IGNITE-22605: --- Summary: Wrong certificate chain might lead to split brain Key: IGNITE-22605 URL: https://issues.apache.org/jira/browse/IGNITE-22605 Project: Ignite Issue Type: Bug Reporter: Maksim Timonin There is a flaky test TcpDiscoverySslTrustedUntrustedTest#testMismatchingCaFirst Connection might fail on writing to the open socket while writing header or message. It might happen due to a receipent ultimately close connection on SSL handshake. The sender make a wrong decision that there is no cluster at all and it's a first node. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-22264) Startup instructions in examples are outdated
[ https://issues.apache.org/jira/browse/IGNITE-22264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17860723#comment-17860723 ] Ivan Artiukhov commented on IGNITE-22264: - Merged. Rev. 3acfe1c. > Startup instructions in examples are outdated > - > > Key: IGNITE-22264 > URL: https://issues.apache.org/jira/browse/IGNITE-22264 > Project: Ignite > Issue Type: Bug > Components: examples >Reporter: Pavel Tupitsyn >Assignee: Ivan Artiukhov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > Verify startup instructions (at the top of every example), make sure they > work with upcoming Ignite beta2. > https://github.com/apache/ignite-3/tree/main/examples/src/main/java/org/apache/ignite/example -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-22576) Calcite engine. Cast varchar to timestamp truncates millis
[
https://issues.apache.org/jira/browse/IGNITE-22576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17860721#comment-17860721
]
Ignite TC Bot commented on IGNITE-22576:
{panel:title=Branch: [pull/11407/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/11407/head] Base: [master] : New Tests
(10)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Calcite SQL{color} [[tests
10|https://ci2.ignite.apache.org/viewLog.html?buildId=798]]
* {color:#013220}IgniteCalciteTestSuite: DateTimeTest.testDateTimeCast -
PASSED{color}
* {color:#013220}IgniteCalciteTestSuite: DateTimeTest.testQuery1 - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite: DateTimeTest.testDstShift -
PASSED{color}
* {color:#013220}IgniteCalciteTestSuite: DateTimeTest.testQuery4 - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite: DateTimeTest.testQuery5 - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite: DateTimeTest.testQuery2 - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite: DateTimeTest.testQuery3 - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite: test_timestamp_ms.test - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite: DateTimeTest.testQuery6 - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite: DateTimeTest.testQuery7 - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7930742&buildTypeId=IgniteTests24Java8_RunAll]
> Calcite engine. Cast varchar to timestamp truncates millis
> --
>
> Key: IGNITE-22576
> URL: https://issues.apache.org/jira/browse/IGNITE-22576
> Project: Ignite
> Issue Type: Bug
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Labels: calcite, ise
>
> Reproducer:
> {noformat}
> SELECT CAST('2021-01-01 01:02:03.456' AS TIMESTAMP)
> {noformat}
> Returns "2021-01-01 01:02:03.000"
> Root cause: default precision for {{TIMESTAMP}} in Calcite is 0, so
> {{TIMESTAMP}} threated as {{TIMESTAMP(0)}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-22434) Do not inherit TaskExecution from JobExecution
[ https://issues.apache.org/jira/browse/IGNITE-22434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin reassigned IGNITE-22434: -- Assignee: Mikhail Pochatkin (was: Pavel Tupitsyn) > Do not inherit TaskExecution from JobExecution > -- > > Key: IGNITE-22434 > URL: https://issues.apache.org/jira/browse/IGNITE-22434 > Project: Ignite > Issue Type: Improvement > Components: compute >Affects Versions: 3.0.0-beta1 >Reporter: Pavel Tupitsyn >Assignee: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > Do not inherit *TaskExecution* from *JobExecution*: > * Tasks and jobs are too different > * We can't add something to JobExecution without affecting tasks > * JobExecution javadoc are job-specific, but are inherited by Task -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-22590) Calcite engine. Distribution by affinity function for columns with null values fails
[
https://issues.apache.org/jira/browse/IGNITE-22590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17860722#comment-17860722
]
Ignite TC Bot commented on IGNITE-22590:
{panel:title=Branch: [pull/11410/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/11410/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Calcite SQL{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=7931945]]
* {color:#013220}IgniteCalciteTestSuite:
JoinRehashIntegrationTest.testNullAffinityKeys - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7932022&buildTypeId=IgniteTests24Java8_RunAll]
> Calcite engine. Distribution by affinity function for columns with null
> values fails
>
>
> Key: IGNITE-22590
> URL: https://issues.apache.org/jira/browse/IGNITE-22590
> Project: Ignite
> Issue Type: Bug
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Labels: calcite, ise
>
> If one side of the join converted to distribution of another side by affinity
> function there can be an errors like:
> {noformat}
> Caused by: java.lang.IllegalArgumentException: Null key is passed for a
> partition calculation. Make sure that an affinity key that is used is
> initialized properly.
> at
> org.apache.ignite.cache.affinity.rendezvous.RendezvousAffinityFunction.partition(RendezvousAffinityFunction.java:506)
> at
> org.apache.ignite.internal.processors.query.calcite.trait.AffinityAdapter.applyAsInt(AffinityAdapter.java:46)
> at
> org.apache.ignite.internal.processors.query.calcite.trait.Partitioned.targets(Partitioned.java:42)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.rel.Outbox.flush(Outbox.java:233)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.rel.Outbox.push(Outbox.java:141)
> {noformat}
> If input to rehash contains null values.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-22426) Move DeploymentUnit from compute to deployment package
[ https://issues.apache.org/jira/browse/IGNITE-22426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin reassigned IGNITE-22426: -- Assignee: Mikhail Pochatkin (was: Pavel Tupitsyn) > Move DeploymentUnit from compute to deployment package > -- > > Key: IGNITE-22426 > URL: https://issues.apache.org/jira/browse/IGNITE-22426 > Project: Ignite > Issue Type: Improvement > Components: compute >Affects Versions: 3.0.0-beta1 >Reporter: Pavel Tupitsyn >Assignee: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > *DeploymentUnit* is not only used in Compute API, but also Streamer and > potentially other places in the future. > Move it from *compute* package to *deployment* -- This message was sent by Atlassian Jira (v8.20.10#820010)
