[jira] [Commented] (IGNITE-14547) NPE in control.sh if there is unknown argument after --cache indexes_force_rebuild
[
https://issues.apache.org/jira/browse/IGNITE-14547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17321908#comment-17321908
]
Ilya Kazakov commented on IGNITE-14547:
---
https://github.com/apache/ignite/pull/9005
> NPE in control.sh if there is unknown argument after --cache
> indexes_force_rebuild
> --
>
> Key: IGNITE-14547
> URL: https://issues.apache.org/jira/browse/IGNITE-14547
> Project: Ignite
> Issue Type: Bug
> Components: control.sh
>Affects Versions: 2.10
>Reporter: Ilya Kazakov
>Assignee: Ilya Kazakov
>Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> ./control.sh --cache indexes_force_rebuild --foo
> gets NPE instead of "Unknown argument: --foo" message
> {code:java}
> java.lang.NullPointerException
> Command [] finished with code: 4
> Error stack trace:
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.commandline.cache.CacheIndexesForceRebuild.parseArguments(CacheIndexesForceRebuild.java:210)
> at
> org.apache.ignite.internal.commandline.cache.CacheCommands.parseArguments(CacheCommands.java:97)
> at
> org.apache.ignite.internal.commandline.CommonArgParser.parseAndValidate(CommonArgParser.java:241)
> at
> org.apache.ignite.internal.commandline.CommandHandler.execute(CommandHandler.java:244)
> at
> org.apache.ignite.internal.commandline.CommandHandler.main(CommandHandler.java:141){code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14547) NPE in control.sh if there is unknown argument after --cache indexes_force_rebuild
Ilya Kazakov created IGNITE-14547:
-
Summary: NPE in control.sh if there is unknown argument after
--cache indexes_force_rebuild
Key: IGNITE-14547
URL: https://issues.apache.org/jira/browse/IGNITE-14547
Project: Ignite
Issue Type: Bug
Components: control.sh
Affects Versions: 2.10
Reporter: Ilya Kazakov
Assignee: Ilya Kazakov
./control.sh --cache indexes_force_rebuild --foo
gets NPE instead of "Unknown argument: --foo" message
{code:java}
java.lang.NullPointerException
Command [] finished with code: 4
Error stack trace:
java.lang.NullPointerException
at
org.apache.ignite.internal.commandline.cache.CacheIndexesForceRebuild.parseArguments(CacheIndexesForceRebuild.java:210)
at
org.apache.ignite.internal.commandline.cache.CacheCommands.parseArguments(CacheCommands.java:97)
at
org.apache.ignite.internal.commandline.CommonArgParser.parseAndValidate(CommonArgParser.java:241)
at
org.apache.ignite.internal.commandline.CommandHandler.execute(CommandHandler.java:244)
at
org.apache.ignite.internal.commandline.CommandHandler.main(CommandHandler.java:141){code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14331) Possible distributed race related to a data streamer flushing leading to a thread being stuck forever trying to close the streamer
[
https://issues.apache.org/jira/browse/IGNITE-14331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17321101#comment-17321101
]
Vladislav Pyatkov commented on IGNITE-14331:
[~slava.koptilin] I left minor comment, but in general this fix looks good to
me.
> Possible distributed race related to a data streamer flushing leading to a
> thread being stuck forever trying to close the streamer
> --
>
> Key: IGNITE-14331
> URL: https://issues.apache.org/jira/browse/IGNITE-14331
> Project: Ignite
> Issue Type: Bug
> Components: streaming
>Affects Versions: 2.10
>Reporter: Vladimir Pligin
>Assignee: Vyacheslav Koptilin
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> It seems that a streamer could stuck forever flushing internal buffers on a
> client side.
> It will stay in a busy-loop forever hoping on remapping but it's possible
> that it won't happen for example in case of long GC pauses on server(s) and
> long timeouts.
> It that case a streamer would be trapped inside this
> [loop|https://github.com/apache/ignite/blob/ignite-2.10/modules/core/src/main/java/org/apache/ignite/internal/processors/datastreamer/DataStreamerImpl.java#L1168].
> Stack trace snippet:
> {code:java}
> java.lang.Thread.State: RUNNABLE at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$Buffer.flush(DataStreamerImpl.java:1706)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.doFlush(DataStreamerImpl.java:1170)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.closeEx(DataStreamerImpl.java:1365)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.closeEx(DataStreamerImpl.java:1323)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.close(DataStreamerImpl.java:1311)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.close(DataStreamerImpl.java:1415){code}
>
> It becomes possible when a
> IgniteSpiOperationTimeoutException
> is being thrown from
> org.apache.ignite.internal.managers.communication.GridIoManager.sendToGridTopic()
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14331) Possible distributed race related to a data streamer flushing leading to a thread being stuck forever trying to close the streamer
[
https://issues.apache.org/jira/browse/IGNITE-14331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17321081#comment-17321081
]
Vyacheslav Koptilin commented on IGNITE-14331:
--
Hi [~v.pyatkov],
Could you please take a look at my patch?
> Possible distributed race related to a data streamer flushing leading to a
> thread being stuck forever trying to close the streamer
> --
>
> Key: IGNITE-14331
> URL: https://issues.apache.org/jira/browse/IGNITE-14331
> Project: Ignite
> Issue Type: Bug
> Components: streaming
>Affects Versions: 2.10
>Reporter: Vladimir Pligin
>Assignee: Vyacheslav Koptilin
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> It seems that a streamer could stuck forever flushing internal buffers on a
> client side.
> It will stay in a busy-loop forever hoping on remapping but it's possible
> that it won't happen for example in case of long GC pauses on server(s) and
> long timeouts.
> It that case a streamer would be trapped inside this
> [loop|https://github.com/apache/ignite/blob/ignite-2.10/modules/core/src/main/java/org/apache/ignite/internal/processors/datastreamer/DataStreamerImpl.java#L1168].
> Stack trace snippet:
> {code:java}
> java.lang.Thread.State: RUNNABLE at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$Buffer.flush(DataStreamerImpl.java:1706)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.doFlush(DataStreamerImpl.java:1170)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.closeEx(DataStreamerImpl.java:1365)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.closeEx(DataStreamerImpl.java:1323)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.close(DataStreamerImpl.java:1311)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.close(DataStreamerImpl.java:1415){code}
>
> It becomes possible when a
> IgniteSpiOperationTimeoutException
> is being thrown from
> org.apache.ignite.internal.managers.communication.GridIoManager.sendToGridTopic()
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14331) Possible distributed race related to a data streamer flushing leading to a thread being stuck forever trying to close the streamer
[
https://issues.apache.org/jira/browse/IGNITE-14331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-14331:
-
Reviewer: Vladislav Pyatkov (was: Vyacheslav Koptilin)
> Possible distributed race related to a data streamer flushing leading to a
> thread being stuck forever trying to close the streamer
> --
>
> Key: IGNITE-14331
> URL: https://issues.apache.org/jira/browse/IGNITE-14331
> Project: Ignite
> Issue Type: Bug
> Components: streaming
>Affects Versions: 2.10
>Reporter: Vladimir Pligin
>Assignee: Vyacheslav Koptilin
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> It seems that a streamer could stuck forever flushing internal buffers on a
> client side.
> It will stay in a busy-loop forever hoping on remapping but it's possible
> that it won't happen for example in case of long GC pauses on server(s) and
> long timeouts.
> It that case a streamer would be trapped inside this
> [loop|https://github.com/apache/ignite/blob/ignite-2.10/modules/core/src/main/java/org/apache/ignite/internal/processors/datastreamer/DataStreamerImpl.java#L1168].
> Stack trace snippet:
> {code:java}
> java.lang.Thread.State: RUNNABLE at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$Buffer.flush(DataStreamerImpl.java:1706)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.doFlush(DataStreamerImpl.java:1170)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.closeEx(DataStreamerImpl.java:1365)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.closeEx(DataStreamerImpl.java:1323)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.close(DataStreamerImpl.java:1311)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.close(DataStreamerImpl.java:1415){code}
>
> It becomes possible when a
> IgniteSpiOperationTimeoutException
> is being thrown from
> org.apache.ignite.internal.managers.communication.GridIoManager.sendToGridTopic()
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14523) .NET: Add support for string.Compare method in LINQ provider
[ https://issues.apache.org/jira/browse/IGNITE-14523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-14523: Summary: .NET: Add support for string.Compare method in LINQ provider (was: Support for string.Compare method in Apache Ignite LINQ provider) > .NET: Add support for string.Compare method in LINQ provider > > > Key: IGNITE-14523 > URL: https://issues.apache.org/jira/browse/IGNITE-14523 > Project: Ignite > Issue Type: New Feature > Components: platforms >Affects Versions: 2.9.1 >Reporter: Oleg Bevz >Assignee: Oleg Bevz >Priority: Minor > Labels: .NET > Fix For: 2.11 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Hello, currently Apache Ignite does not support string comparison for LINQ > provider (Apache.Ignite.Linq project). > For example following modified query > insideThinClientQueryExample.ScanQueryExample method will throw Exception: > var employees = cache.AsCacheQueryable().Select(x => x.Value).Where(x => > string.Compare(x.Name, "Daniel Adams") >= 0); > Business case: in our project we use DevExteme.AspNet.Data library to build > LINQ queries for Apache Ignite and in some cases the library builds complex > queries with string.Compare method call. > Exception details: > Exception has been thrown by the target of an invocation. > System.Reflection.TargetInvocationException System.Object > InvokeMethod(System.Object, System.Object[], System.Signature, Boolean) > System.Reflection.TargetInvocationException: Exception has been thrown by the > target of an invocation. ---> System.NotSupportedException: Method not > supported: System.String.(Int32 Compare(System.String, System.String)) > at > Apache.Ignite.Linq.Impl.MethodVisitor.VisitMethodCall(MethodCallExpression > expression, CacheQueryExpressionVisitor visitor) > at > Apache.Ignite.Linq.Impl.CacheQueryExpressionVisitor.VisitMethodCall(MethodCallExpression > expression) > at Remotion.Linq.Parsing.ThrowingExpressionVisitor.Visit(Expression > expression) > at > Apache.Ignite.Linq.Impl.CacheQueryExpressionVisitor.VisitBinary(BinaryExpression > expression) > at Remotion.Linq.Parsing.ThrowingExpressionVisitor.Visit(Expression > expression) > at > Apache.Ignite.Linq.Impl.CacheQueryExpressionVisitor.VisitBinary(BinaryExpression > expression) > at Remotion.Linq.Parsing.ThrowingExpressionVisitor.Visit(Expression > expression) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.VisitWhereClause(WhereClause > whereClause, Int32 index, Boolean hasGroups) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.ProcessGroupings(QueryModel > queryModel) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.VisitBodyClauses(ObservableCollection`1 > bodyClauses, QueryModel queryModel) > at Remotion.Linq.QueryModelVisitorBase.VisitQueryModel(QueryModel > queryModel) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.VisitQueryModel(QueryModel > queryModel, Boolean includeAllFields, Boolean copyAliases) > at > Apache.Ignite.Linq.Impl.CacheQueryModelVisitor.GenerateQuery(QueryModel > queryModel) > at > Apache.Ignite.Linq.Impl.CacheFieldsQueryExecutor.ExecuteCollection[T](QueryModel > queryModel) > at > Remotion.Linq.Clauses.StreamedData.StreamedSequenceInfo.ExecuteQueryModel(QueryModel > queryModel, IQueryExecutor executor) > at > Apache.Ignite.Linq.Impl.CacheFieldsQueryProvider.Execute[TResult](Expression > expression) > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-14533) [Ignite Website] Update for top line event promotion
[ https://issues.apache.org/jira/browse/IGNITE-14533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl resolved IGNITE-14533. - Resolution: Done > [Ignite Website] Update for top line event promotion > > > Key: IGNITE-14533 > URL: https://issues.apache.org/jira/browse/IGNITE-14533 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Kseniya Romanova >Assignee: Mauricio Stekl >Priority: Minor > > [~mstekl], please change the topline event promotion for the next meetup: > > April 28, 2021: Apache Ignite Native Persistence Storage. Overview by Ignite > Developer > [https://www.meetup.com/Apache-Ignite-Virtual-Meetup/events/277298901/] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-14533) [Ignite Website] Update for top line event promotion
[ https://issues.apache.org/jira/browse/IGNITE-14533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl reassigned IGNITE-14533: --- Assignee: Mauricio Stekl > [Ignite Website] Update for top line event promotion > > > Key: IGNITE-14533 > URL: https://issues.apache.org/jira/browse/IGNITE-14533 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Kseniya Romanova >Assignee: Mauricio Stekl >Priority: Minor > > [~mstekl], please change the topline event promotion for the next meetup: > > April 28, 2021: Apache Ignite Native Persistence Storage. Overview by Ignite > Developer > [https://www.meetup.com/Apache-Ignite-Virtual-Meetup/events/277298901/] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14546) Calcite engine. MIN/MAX aggregates doesn't support string types
Taras Ledkov created IGNITE-14546:
-
Summary: Calcite engine. MIN/MAX aggregates doesn't support string
types
Key: IGNITE-14546
URL: https://issues.apache.org/jira/browse/IGNITE-14546
Project: Ignite
Issue Type: Bug
Reporter: Taras Ledkov
MIN/MAX aggregates doesn't support string types.
e.g.
{{CREATE TABLE TEST(val VARCHAR) }}
{{INSERT INTO TEST VALUES ('A'), ('B'), ('C') }}
{{ SELECT MIN(val), MAX(val) FROM TEST}}
Test: {{src/test/sql/aggregate/aggregates/test_aggr_string.test}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14545) Calcite engine. Unicode literal not supported
Taras Ledkov created IGNITE-14545:
-
Summary: Calcite engine. Unicode literal not supported
Key: IGNITE-14545
URL: https://issues.apache.org/jira/browse/IGNITE-14545
Project: Ignite
Issue Type: Bug
Reporter: Taras Ledkov
Unicode literal not supported.
e.g. {{SELECT }}
Tests:
{{aggregate/aggregates/test_aggr_string.test}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14544) Calcite engine. Implement DISTING aggregates
Taras Ledkov created IGNITE-14544:
-
Summary: Calcite engine. Implement DISTING aggregates
Key: IGNITE-14544
URL: https://issues.apache.org/jira/browse/IGNITE-14544
Project: Ignite
Issue Type: Bug
Reporter: Taras Ledkov
Now, DISTINCT aggregates not implemented.
(e.g. {{SELECT COUNT (DISTINCT lastName) FROM person}})
Tests:
{{aggregate/aggregates/test_count.test_ignored}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14543) Calcite engine. COUNT agregate on scalar values fails
[
https://issues.apache.org/jira/browse/IGNITE-14543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-14543:
--
Description:
Failed queries:
{{SELECT COUNT(*)}}
{{SELECT COUNT(NULL)}}
Test:
{{aggregate/aggregates/test_count.test_ignored}}
was:
Failed queries:
{{SELECT COUNT(*)}}
{{SELECT COUNT(NULL)}}
> Calcite engine. COUNT agregate on scalar values fails
> -
>
> Key: IGNITE-14543
> URL: https://issues.apache.org/jira/browse/IGNITE-14543
> Project: Ignite
> Issue Type: Bug
>Reporter: Taras Ledkov
>Priority: Major
>
> Failed queries:
> {{SELECT COUNT(*)}}
> {{SELECT COUNT(NULL)}}
> Test:
> {{aggregate/aggregates/test_count.test_ignored}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14543) Calcite engine. COUNT agregate on scalar values fails
Taras Ledkov created IGNITE-14543:
-
Summary: Calcite engine. COUNT agregate on scalar values fails
Key: IGNITE-14543
URL: https://issues.apache.org/jira/browse/IGNITE-14543
Project: Ignite
Issue Type: Bug
Reporter: Taras Ledkov
Failed queries:
{{SELECT COUNT(*)}}
{{SELECT COUNT(NULL)}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14534) Python thin: Add script for building wheels on Windows
[ https://issues.apache.org/jira/browse/IGNITE-14534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17320990#comment-17320990 ] Ivan Daschinsky commented on IGNITE-14534: -- [~isapego] LGTM, please proceed wit merge. > Python thin: Add script for building wheels on Windows > -- > > Key: IGNITE-14534 > URL: https://issues.apache.org/jira/browse/IGNITE-14534 > Project: Ignite > Issue Type: Improvement > Components: thin client >Affects Versions: python-0.3.4 >Reporter: Igor Sapego >Assignee: Igor Sapego >Priority: Major > Fix For: python-0.4.0 > > Time Spent: 10m > Remaining Estimate: 0h > > We already have scripts to build wheels on Linux, now we need script to build > wheels on Windows. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13547) Calcite integration. CREATE TABLE support
[ https://issues.apache.org/jira/browse/IGNITE-13547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17320989#comment-17320989 ] Stanilovsky Evgeny commented on IGNITE-13547: - [~korlov] check my few minor comments, overall looks good. > Calcite integration. CREATE TABLE support > - > > Key: IGNITE-13547 > URL: https://issues.apache.org/jira/browse/IGNITE-13547 > Project: Ignite > Issue Type: New Feature > Components: sql >Reporter: Yury Gerzhedovich >Assignee: Konstantin Orlov >Priority: Critical > Original Estimate: 40h > Time Spent: 2.5h > Remaining Estimate: 37.5h > > We need to support DDL commands. The task about the support of CREATE TABLE. > Potentially with syntaxis as we already have in the H2 engine. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14542) Calcite engine. Need to support TableFunctions / SYSTEM_RANGE dynamic table
Taras Ledkov created IGNITE-14542:
-
Summary: Calcite engine. Need to support TableFunctions /
SYSTEM_RANGE dynamic table
Key: IGNITE-14542
URL: https://issues.apache.org/jira/browse/IGNITE-14542
Project: Ignite
Issue Type: Bug
Components: sql
Reporter: Taras Ledkov
A lot of cases require dynamic range data source.
Tests:
{{aggregate/aggregates/test_perfect_ht.test_ignored}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14541) Calcite engine. HAVING fails on scalar
Taras Ledkov created IGNITE-14541:
-
Summary: Calcite engine. HAVING fails on scalar
Key: IGNITE-14541
URL: https://issues.apache.org/jira/browse/IGNITE-14541
Project: Ignite
Issue Type: Bug
Reporter: Taras Ledkov
Query to reproduce:
{{SELECT 42 HAVING 42 > 20}}
Test: {{aggregate/having/test_scalar_having.test_ignore}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14539) Calcite engine. Support DISTINCT ON expression
[
https://issues.apache.org/jira/browse/IGNITE-14539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-14539:
--
Description:
Now DISTINCT ON expression isn't supported.
e.g.:
{{SELECT DISTINCT ON (lastName) firstName, lastName FROM Person WHERE ...}}
Test: {{aggregate/distinct/test_distinct_on.test_ignored}}
was:
Now DISTINCT ON expression isn't supported.
e.g.:
{{SELECT DISTINCT ON (lastName) firstName, lastName FROM Person WHERE ... }}
Test: {{aggregate/distinct/test_distinct_on.test_ignored}}
> Calcite engine. Support DISTINCT ON expression
> --
>
> Key: IGNITE-14539
> URL: https://issues.apache.org/jira/browse/IGNITE-14539
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Taras Ledkov
>Priority: Major
>
> Now DISTINCT ON expression isn't supported.
> e.g.:
> {{SELECT DISTINCT ON (lastName) firstName, lastName FROM Person WHERE ...}}
> Test: {{aggregate/distinct/test_distinct_on.test_ignored}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14540) Calcite engine. Support correlated subquery in having
Taras Ledkov created IGNITE-14540:
-
Summary: Calcite engine. Support correlated subquery in having
Key: IGNITE-14540
URL: https://issues.apache.org/jira/browse/IGNITE-14540
Project: Ignite
Issue Type: Improvement
Components: sql
Reporter: Taras Ledkov
Correlated subquery in having isn't supported now.
Test: {{aggregate/having/test_corel_subquery_in_having.test_ignored}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14537) Calcite engine. Nested arbitrary queries hangs on optimizing
[
https://issues.apache.org/jira/browse/IGNITE-14537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-14537:
--
Summary: Calcite engine. Nested arbitrary queries hangs on optimizing
(was: Nested arbitrary queries hangs on optimizing )
> Calcite engine. Nested arbitrary queries hangs on optimizing
> --
>
> Key: IGNITE-14537
> URL: https://issues.apache.org/jira/browse/IGNITE-14537
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Taras Ledkov
>Priority: Major
>
> The query with nested arbitrary subqueries aren't planned.
> Test: {{subquery/test_neumann.test_ignore}}
> See more: [Unnesting Arbitrary
> Queries|https://subs.emis.de/LNI/Proceedings/Proceedings241/383.pdf]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14539) Calcite engine. Support DISTINCT ON expression
Taras Ledkov created IGNITE-14539:
-
Summary: Calcite engine. Support DISTINCT ON expression
Key: IGNITE-14539
URL: https://issues.apache.org/jira/browse/IGNITE-14539
Project: Ignite
Issue Type: Improvement
Components: sql
Reporter: Taras Ledkov
Now DISTINCT ON expression isn't supported.
e.g.:
{{SELECT DISTINCT ON (lastName) firstName, lastName FROM Person WHERE ... }}
Test: {{aggregate/distinct/test_distinct_on.test_ignored}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14538) Add ScaleCube configuration
Semyon Danilov created IGNITE-14538: --- Summary: Add ScaleCube configuration Key: IGNITE-14538 URL: https://issues.apache.org/jira/browse/IGNITE-14538 Project: Ignite Issue Type: Sub-task Reporter: Semyon Danilov Right now we are using default ScaleCube parameters. ScaleCube configuration should be introduced as a part of networking configuration. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14537) Nested arbitrary queries hangs on optimizing
[
https://issues.apache.org/jira/browse/IGNITE-14537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-14537:
--
Issue Type: Bug (was: Improvement)
> Nested arbitrary queries hangs on optimizing
> -
>
> Key: IGNITE-14537
> URL: https://issues.apache.org/jira/browse/IGNITE-14537
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Taras Ledkov
>Priority: Major
>
> The query with nested arbitrary subqueries aren't planned.
> Test: {{subquery/test_neumann.test_ignore}}
> See more: [Unnesting Arbitrary
> Queries|https://subs.emis.de/LNI/Proceedings/Proceedings241/383.pdf]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14537) Nested arbitrary queries hangs on optimizing
Taras Ledkov created IGNITE-14537:
-
Summary: Nested arbitrary queries hangs on optimizing
Key: IGNITE-14537
URL: https://issues.apache.org/jira/browse/IGNITE-14537
Project: Ignite
Issue Type: Improvement
Components: sql
Reporter: Taras Ledkov
The query with nested arbitrary subqueries aren't planned.
Test: {{subquery/test_neumann.test_ignore}}
See more: [Unnesting Arbitrary
Queries|https://subs.emis.de/LNI/Proceedings/Proceedings241/383.pdf]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14536) Handle forceful shutdown of ScaleCube cluster node
Semyon Danilov created IGNITE-14536: --- Summary: Handle forceful shutdown of ScaleCube cluster node Key: IGNITE-14536 URL: https://issues.apache.org/jira/browse/IGNITE-14536 Project: Ignite Issue Type: Bug Reporter: Semyon Danilov Assignee: Semyon Danilov Right now, if scalecube cluster node was shutdown forcefully no event will be propagated to ClusterService and topology wouldn't change -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14535) Caclite SQL engine capabilities
Taras Ledkov created IGNITE-14535: - Summary: Caclite SQL engine capabilities Key: IGNITE-14535 URL: https://issues.apache.org/jira/browse/IGNITE-14535 Project: Ignite Issue Type: Improvement Reporter: Taras Ledkov Umbrella ticket to track issues related to SQL logical tests. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14535) Caclite SQL engine capabilities
[ https://issues.apache.org/jira/browse/IGNITE-14535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov updated IGNITE-14535: -- Component/s: sql > Caclite SQL engine capabilities > --- > > Key: IGNITE-14535 > URL: https://issues.apache.org/jira/browse/IGNITE-14535 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Taras Ledkov >Priority: Major > > Umbrella ticket to track issues related to SQL logical tests. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13029) Support Spring Data repositories initialization with Spring Boot auto-starter
[
https://issues.apache.org/jira/browse/IGNITE-13029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17320912#comment-17320912
]
Sergey Chugunov commented on IGNITE-13029:
--
[~stalkxt],
I reviewed your changes, they look reasonable to me, but unfortunately TC
results have expired. I tried to restart TC on your PR but for some reason
didn't get a green run.
Could you please re-run TC on your patch and update the TC link in the ticket?
I will merge the patch after that.
Thank you!
> Support Spring Data repositories initialization with Spring Boot auto-starter
> -
>
> Key: IGNITE-13029
> URL: https://issues.apache.org/jira/browse/IGNITE-13029
> Project: Ignite
> Issue Type: Improvement
> Components: spring, springdata
>Affects Versions: 2.8
>Reporter: Denis A. Magda
>Assignee: Sergey Dorozhkin
>Priority: Major
> Labels: newbie
>
> It's required to use {{@EnableIgniteRepositories}} annotation and follow this
> procedure to enable Ignite Spring Data repositories:
> https://apacheignite-mix.readme.io/docs/spring-data#spring-data-and-apache-ignite-configuration
> Support the Spring Data repositories enablement via the Spring Boot
> auto-starter if Spring Boot is used by a project:
> https://apacheignite-mix.readme.io/docs/spring-boot
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14423) Node failure caused by AssertionError: Transaction does not own lock for update
[
https://issues.apache.org/jira/browse/IGNITE-14423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Ivanov updated IGNITE-14423:
--
Reviewer: Slava Koptilin (was: Peter Ivanov)
> Node failure caused by AssertionError: Transaction does not own lock for
> update
> ---
>
> Key: IGNITE-14423
> URL: https://issues.apache.org/jira/browse/IGNITE-14423
> Project: Ignite
> Issue Type: Bug
>Reporter: Denis Chudov
>Assignee: Denis Chudov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Scenario:
> 1. Start 3 servers
> 2. Start 2 clients
> 3. Start two OPTIMISTIC transactions with the same key from different client
> nodes
> 4. Transfer transactions to PREPARED STATE on primary node
> 5. Stop one client node(whose transaction changed state to PREPARED last)
>
> Error in log:
> {code:java}
> [2021-03-03
> 08:52:59,807][ERROR][sys-#499%transactions.TxRecoveryWithConcurrentRollbackTest1%][GridNearTxLocal]
> Failed completing the transaction: [commit=true, tx=GridDhtTxLocal
> [nearNodeId=29551b46-74ef-4e35-af4a-d97809cc5260,
> nearFutId=08b25a6f771-eec14fa0-02ef-46b9-97d9-0f2b7c851ddb, nearMiniId=1,
> nearFinFutId=null, nearFinMiniId=0, nearXidVer=GridCacheVersion
> [topVer=226230774, order=1614750773047, nodeOrder=4], lb=tx,
> super=GridDhtTxLocalAdapter [nearOnOriginatingNode=false,
> nearNodes=KeySetView [], dhtNodes=KeySetView [], explicitLock=false,
> super=IgniteTxLocalAdapter [completedBase=null, sndTransformedVals=false,
> depEnabled=false, txState=IgniteTxStateImpl [activeCacheIds=[1544803905],
> recovery=false, mvccEnabled=false, mvccCachingCacheIds=[], txMap=ArrayList
> [IgniteTxEntry [txKey=IgniteTxKey [key=KeyCacheObjectImpl [part=1, val=1,
> hasValBytes=true], cacheId=1544803905], val=TxEntryValueHolder
> [val=CacheObjectImpl [val=null, hasValBytes=true], op=CREATE],
> prevVal=TxEntryValueHolder [val=null, op=NOOP], oldVal=TxEntryValueHolder
> [val=null, op=NOOP], entryProcessorsCol=null, ttl=-1, conflictExpireTime=-1,
> conflictVer=null, explicitVer=null, dhtVer=null,
> filters=CacheEntryPredicate[] [], filtersPassed=false, filtersSet=false,
> entry=GridDhtCacheEntry [rdrs=ReaderId[] [], part=1,
> super=GridDistributedCacheEntry [super=GridCacheMapEntry
> [key=KeyCacheObjectImpl [part=1, val=1, hasValBytes=true], val=null,
> ver=GridCacheVersion [topVer=226230774, order=1614750774035, nodeOrder=2],
> hash=1, extras=GridCacheMvccEntryExtras [mvcc=GridCacheMvcc [locs=LinkedList
> [GridCacheMvccCandidate [nodeId=b1f1a8e0-e1e8-4084-b9c6-bdd2a271,
> ver=GridCacheVersion [topVer=226230774, order=1614750774033, nodeOrder=2],
> threadId=364, id=5, topVer=AffinityTopologyVersion [topVer=5, minorTopVer=0],
> reentry=null, otherNodeId=207c7f09-21a9-4b99-b631-3304a522b002,
> otherVer=GridCacheVersion [topVer=226230774, order=1614750774032,
> nodeOrder=5], mappedDhtNodes=null, mappedNearNodes=null, ownerVer=null,
> serOrder=null, key=KeyCacheObjectImpl [part=1, val=1, hasValBytes=true],
> masks=local=1|owner=1|ready=1|reentry=0|used=0|tx=1|single_implicit=0|dht_local=1|near_local=0|removed=0|read=0,
> prevVer=null, nextVer=null]], rmts=null]], flags=3]]], prepared=1,
> locked=false, nodeId=null, locMapped=false, expiryPlc=null,
> transferExpiryPlc=false, flags=0, partUpdateCntr=0, serReadVer=null,
> xidVer=null]]], super=IgniteTxAdapter [xidVer=GridCacheVersion
> [topVer=226230774, order=1614750774035, nodeOrder=2], writeVer=null,
> implicit=false, loc=true, threadId=686, startTime=1614750774753,
> nodeId=b1f1a8e0-e1e8-4084-b9c6-bdd2a271, isolation=READ_COMMITTED,
> concurrency=OPTIMISTIC, timeout=5000, sysInvalidate=true, sys=false, plc=2,
> commitVer=GridCacheVersion [topVer=226230774, order=1614750774035,
> nodeOrder=2], finalizing=RECOVERY_FINISH, invalidParts=null, state=UNKNOWN,
> timedOut=false, topVer=AffinityTopologyVersion [topVer=5, minorTopVer=0],
> mvccSnapshot=null, skipCompletedVers=false, parentTx=null, duration=5048ms,
> onePhaseCommit=false], size=1
> class
> org.apache.ignite.internal.transactions.IgniteTxHeuristicCheckedException:
> Committing a transaction has produced runtime exception
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxAdapter.heuristicException(IgniteTxAdapter.java:813)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter.userCommit(IgniteTxLocalAdapter.java:969)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocalAdapter.localFinish(GridDhtTxLocalAdapter.java:794)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.localFinish(GridDhtTxLocal.java:605)
> at
>
[jira] [Updated] (IGNITE-14534) Python thin: Add script for building wheels on Windows
[ https://issues.apache.org/jira/browse/IGNITE-14534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Daschinsky updated IGNITE-14534: - Fix Version/s: (was: python-0.3.4) python-0.4.0 > Python thin: Add script for building wheels on Windows > -- > > Key: IGNITE-14534 > URL: https://issues.apache.org/jira/browse/IGNITE-14534 > Project: Ignite > Issue Type: Improvement > Components: thin client >Affects Versions: python-0.3.4 >Reporter: Igor Sapego >Assignee: Igor Sapego >Priority: Major > Fix For: python-0.4.0 > > Time Spent: 10m > Remaining Estimate: 0h > > We already have scripts to build wheels on Linux, now we need script to build > wheels on Windows. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14532) Thin client: Unordered map used for putAll warning is unavoidable
[
https://issues.apache.org/jira/browse/IGNITE-14532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-14532:
Priority: Minor (was: Major)
> Thin client: Unordered map used for putAll warning is unavoidable
> -
>
> Key: IGNITE-14532
> URL: https://issues.apache.org/jira/browse/IGNITE-14532
> Project: Ignite
> Issue Type: New Feature
> Components: thin client
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Minor
> Fix For: 2.11
>
>
> Thin client uses LinkedHashMap to preserve client-side entry order. Ignite
> logs a warning and there is no way to fix it for the user:
> {code}
> Unordered map java.util.HashMap is used for putAll operation on cache exact.
> This can lead to a distributed deadlock. Switch to a sorted map like TreeMap
> instead.
> {code}
> We should suppress this warning for thin client operations, since it does not
> make sense. Thin clients have different language-specific APIs, some of them
> don't even use maps. The same applies to PlatformCache (thick C# & C++).
> We should have an internal method that does not produce a warning, and,
> ideally, does not require a Map. Using LinkedHashMap as an intermediate
> collection produces unnecessary overhead and allocations, we could use an
> array of key-value pairs instead.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14534) Python thin: Add script for building wheels on Windows
Igor Sapego created IGNITE-14534: Summary: Python thin: Add script for building wheels on Windows Key: IGNITE-14534 URL: https://issues.apache.org/jira/browse/IGNITE-14534 Project: Ignite Issue Type: Improvement Components: thin client Affects Versions: python-0.3.4 Reporter: Igor Sapego Assignee: Igor Sapego Fix For: python-0.3.4 We already have scripts to build wheels on Linux, now we need script to build wheels on Windows. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14423) Node failure caused by AssertionError: Transaction does not own lock for update
[
https://issues.apache.org/jira/browse/IGNITE-14423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Ivanov updated IGNITE-14423:
--
Reviewer: Peter Ivanov (was: Slava Koptilin)
> Node failure caused by AssertionError: Transaction does not own lock for
> update
> ---
>
> Key: IGNITE-14423
> URL: https://issues.apache.org/jira/browse/IGNITE-14423
> Project: Ignite
> Issue Type: Bug
>Reporter: Denis Chudov
>Assignee: Denis Chudov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Scenario:
> 1. Start 3 servers
> 2. Start 2 clients
> 3. Start two OPTIMISTIC transactions with the same key from different client
> nodes
> 4. Transfer transactions to PREPARED STATE on primary node
> 5. Stop one client node(whose transaction changed state to PREPARED last)
>
> Error in log:
> {code:java}
> [2021-03-03
> 08:52:59,807][ERROR][sys-#499%transactions.TxRecoveryWithConcurrentRollbackTest1%][GridNearTxLocal]
> Failed completing the transaction: [commit=true, tx=GridDhtTxLocal
> [nearNodeId=29551b46-74ef-4e35-af4a-d97809cc5260,
> nearFutId=08b25a6f771-eec14fa0-02ef-46b9-97d9-0f2b7c851ddb, nearMiniId=1,
> nearFinFutId=null, nearFinMiniId=0, nearXidVer=GridCacheVersion
> [topVer=226230774, order=1614750773047, nodeOrder=4], lb=tx,
> super=GridDhtTxLocalAdapter [nearOnOriginatingNode=false,
> nearNodes=KeySetView [], dhtNodes=KeySetView [], explicitLock=false,
> super=IgniteTxLocalAdapter [completedBase=null, sndTransformedVals=false,
> depEnabled=false, txState=IgniteTxStateImpl [activeCacheIds=[1544803905],
> recovery=false, mvccEnabled=false, mvccCachingCacheIds=[], txMap=ArrayList
> [IgniteTxEntry [txKey=IgniteTxKey [key=KeyCacheObjectImpl [part=1, val=1,
> hasValBytes=true], cacheId=1544803905], val=TxEntryValueHolder
> [val=CacheObjectImpl [val=null, hasValBytes=true], op=CREATE],
> prevVal=TxEntryValueHolder [val=null, op=NOOP], oldVal=TxEntryValueHolder
> [val=null, op=NOOP], entryProcessorsCol=null, ttl=-1, conflictExpireTime=-1,
> conflictVer=null, explicitVer=null, dhtVer=null,
> filters=CacheEntryPredicate[] [], filtersPassed=false, filtersSet=false,
> entry=GridDhtCacheEntry [rdrs=ReaderId[] [], part=1,
> super=GridDistributedCacheEntry [super=GridCacheMapEntry
> [key=KeyCacheObjectImpl [part=1, val=1, hasValBytes=true], val=null,
> ver=GridCacheVersion [topVer=226230774, order=1614750774035, nodeOrder=2],
> hash=1, extras=GridCacheMvccEntryExtras [mvcc=GridCacheMvcc [locs=LinkedList
> [GridCacheMvccCandidate [nodeId=b1f1a8e0-e1e8-4084-b9c6-bdd2a271,
> ver=GridCacheVersion [topVer=226230774, order=1614750774033, nodeOrder=2],
> threadId=364, id=5, topVer=AffinityTopologyVersion [topVer=5, minorTopVer=0],
> reentry=null, otherNodeId=207c7f09-21a9-4b99-b631-3304a522b002,
> otherVer=GridCacheVersion [topVer=226230774, order=1614750774032,
> nodeOrder=5], mappedDhtNodes=null, mappedNearNodes=null, ownerVer=null,
> serOrder=null, key=KeyCacheObjectImpl [part=1, val=1, hasValBytes=true],
> masks=local=1|owner=1|ready=1|reentry=0|used=0|tx=1|single_implicit=0|dht_local=1|near_local=0|removed=0|read=0,
> prevVer=null, nextVer=null]], rmts=null]], flags=3]]], prepared=1,
> locked=false, nodeId=null, locMapped=false, expiryPlc=null,
> transferExpiryPlc=false, flags=0, partUpdateCntr=0, serReadVer=null,
> xidVer=null]]], super=IgniteTxAdapter [xidVer=GridCacheVersion
> [topVer=226230774, order=1614750774035, nodeOrder=2], writeVer=null,
> implicit=false, loc=true, threadId=686, startTime=1614750774753,
> nodeId=b1f1a8e0-e1e8-4084-b9c6-bdd2a271, isolation=READ_COMMITTED,
> concurrency=OPTIMISTIC, timeout=5000, sysInvalidate=true, sys=false, plc=2,
> commitVer=GridCacheVersion [topVer=226230774, order=1614750774035,
> nodeOrder=2], finalizing=RECOVERY_FINISH, invalidParts=null, state=UNKNOWN,
> timedOut=false, topVer=AffinityTopologyVersion [topVer=5, minorTopVer=0],
> mvccSnapshot=null, skipCompletedVers=false, parentTx=null, duration=5048ms,
> onePhaseCommit=false], size=1
> class
> org.apache.ignite.internal.transactions.IgniteTxHeuristicCheckedException:
> Committing a transaction has produced runtime exception
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxAdapter.heuristicException(IgniteTxAdapter.java:813)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter.userCommit(IgniteTxLocalAdapter.java:969)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocalAdapter.localFinish(GridDhtTxLocalAdapter.java:794)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.localFinish(GridDhtTxLocal.java:605)
> at
>
[jira] [Updated] (IGNITE-14423) Node failure caused by AssertionError: Transaction does not own lock for update
[
https://issues.apache.org/jira/browse/IGNITE-14423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Ivanov updated IGNITE-14423:
--
Reviewer: Slava Koptilin (was: Peter Ivanov)
> Node failure caused by AssertionError: Transaction does not own lock for
> update
> ---
>
> Key: IGNITE-14423
> URL: https://issues.apache.org/jira/browse/IGNITE-14423
> Project: Ignite
> Issue Type: Bug
>Reporter: Denis Chudov
>Assignee: Denis Chudov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Scenario:
> 1. Start 3 servers
> 2. Start 2 clients
> 3. Start two OPTIMISTIC transactions with the same key from different client
> nodes
> 4. Transfer transactions to PREPARED STATE on primary node
> 5. Stop one client node(whose transaction changed state to PREPARED last)
>
> Error in log:
> {code:java}
> [2021-03-03
> 08:52:59,807][ERROR][sys-#499%transactions.TxRecoveryWithConcurrentRollbackTest1%][GridNearTxLocal]
> Failed completing the transaction: [commit=true, tx=GridDhtTxLocal
> [nearNodeId=29551b46-74ef-4e35-af4a-d97809cc5260,
> nearFutId=08b25a6f771-eec14fa0-02ef-46b9-97d9-0f2b7c851ddb, nearMiniId=1,
> nearFinFutId=null, nearFinMiniId=0, nearXidVer=GridCacheVersion
> [topVer=226230774, order=1614750773047, nodeOrder=4], lb=tx,
> super=GridDhtTxLocalAdapter [nearOnOriginatingNode=false,
> nearNodes=KeySetView [], dhtNodes=KeySetView [], explicitLock=false,
> super=IgniteTxLocalAdapter [completedBase=null, sndTransformedVals=false,
> depEnabled=false, txState=IgniteTxStateImpl [activeCacheIds=[1544803905],
> recovery=false, mvccEnabled=false, mvccCachingCacheIds=[], txMap=ArrayList
> [IgniteTxEntry [txKey=IgniteTxKey [key=KeyCacheObjectImpl [part=1, val=1,
> hasValBytes=true], cacheId=1544803905], val=TxEntryValueHolder
> [val=CacheObjectImpl [val=null, hasValBytes=true], op=CREATE],
> prevVal=TxEntryValueHolder [val=null, op=NOOP], oldVal=TxEntryValueHolder
> [val=null, op=NOOP], entryProcessorsCol=null, ttl=-1, conflictExpireTime=-1,
> conflictVer=null, explicitVer=null, dhtVer=null,
> filters=CacheEntryPredicate[] [], filtersPassed=false, filtersSet=false,
> entry=GridDhtCacheEntry [rdrs=ReaderId[] [], part=1,
> super=GridDistributedCacheEntry [super=GridCacheMapEntry
> [key=KeyCacheObjectImpl [part=1, val=1, hasValBytes=true], val=null,
> ver=GridCacheVersion [topVer=226230774, order=1614750774035, nodeOrder=2],
> hash=1, extras=GridCacheMvccEntryExtras [mvcc=GridCacheMvcc [locs=LinkedList
> [GridCacheMvccCandidate [nodeId=b1f1a8e0-e1e8-4084-b9c6-bdd2a271,
> ver=GridCacheVersion [topVer=226230774, order=1614750774033, nodeOrder=2],
> threadId=364, id=5, topVer=AffinityTopologyVersion [topVer=5, minorTopVer=0],
> reentry=null, otherNodeId=207c7f09-21a9-4b99-b631-3304a522b002,
> otherVer=GridCacheVersion [topVer=226230774, order=1614750774032,
> nodeOrder=5], mappedDhtNodes=null, mappedNearNodes=null, ownerVer=null,
> serOrder=null, key=KeyCacheObjectImpl [part=1, val=1, hasValBytes=true],
> masks=local=1|owner=1|ready=1|reentry=0|used=0|tx=1|single_implicit=0|dht_local=1|near_local=0|removed=0|read=0,
> prevVer=null, nextVer=null]], rmts=null]], flags=3]]], prepared=1,
> locked=false, nodeId=null, locMapped=false, expiryPlc=null,
> transferExpiryPlc=false, flags=0, partUpdateCntr=0, serReadVer=null,
> xidVer=null]]], super=IgniteTxAdapter [xidVer=GridCacheVersion
> [topVer=226230774, order=1614750774035, nodeOrder=2], writeVer=null,
> implicit=false, loc=true, threadId=686, startTime=1614750774753,
> nodeId=b1f1a8e0-e1e8-4084-b9c6-bdd2a271, isolation=READ_COMMITTED,
> concurrency=OPTIMISTIC, timeout=5000, sysInvalidate=true, sys=false, plc=2,
> commitVer=GridCacheVersion [topVer=226230774, order=1614750774035,
> nodeOrder=2], finalizing=RECOVERY_FINISH, invalidParts=null, state=UNKNOWN,
> timedOut=false, topVer=AffinityTopologyVersion [topVer=5, minorTopVer=0],
> mvccSnapshot=null, skipCompletedVers=false, parentTx=null, duration=5048ms,
> onePhaseCommit=false], size=1
> class
> org.apache.ignite.internal.transactions.IgniteTxHeuristicCheckedException:
> Committing a transaction has produced runtime exception
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxAdapter.heuristicException(IgniteTxAdapter.java:813)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter.userCommit(IgniteTxLocalAdapter.java:969)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocalAdapter.localFinish(GridDhtTxLocalAdapter.java:794)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.localFinish(GridDhtTxLocal.java:605)
> at
>
[jira] [Commented] (IGNITE-14384) Remove diagnostics at the stop of the node in case of CorruptedTreeException
[
https://issues.apache.org/jira/browse/IGNITE-14384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17320885#comment-17320885
]
Ignite TC Bot commented on IGNITE-14384:
{panel:title=Branch: [pull/8926/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8926/head] Base: [master] : New Tests
(4)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}PDS 1{color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=5966028]]
* {color:#013220}IgnitePdsTestSuite:
DiagnosticProcessorTest.testOutputDiagnosticCorruptedPagesInfo - PASSED{color}
* {color:#013220}IgnitePdsTestSuite:
DiagnosticProcessorTest.testCorruptedPagesFile - PASSED{color}
* {color:#013220}IgnitePdsTestSuite: DiagnosticProcessorTest.testWalDirs -
PASSED{color}
{color:#8b}Dev Utils{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5966048]]
* {color:#013220}DevUtilsTestSuite:
IgniteWalConverterArgumentsTest.testCorruptedPagesFile - PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5966059buildTypeId=IgniteTests24Java8_RunAll]
> Remove diagnostics at the stop of the node in case of CorruptedTreeException
>
>
> Key: IGNITE-14384
> URL: https://issues.apache.org/jira/browse/IGNITE-14384
> Project: Ignite
> Issue Type: Improvement
> Components: persistence
>Reporter: Kirill Tkalenko
>Assignee: Kirill Tkalenko
>Priority: Major
> Fix For: 2.11
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When an error *CorruptedTreeException*, diagnostics are launched, which may
> take a long time and do not allow the node to be stopped until it completes.
> Instead of waiting for a long time to complete the diagnostics, a command
> will be output that will allow to do it offline.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14528) AssertionError in GridDhtPartitionDemander$RebalanceFuture.ownPartitionsAndFinishFuture:1528
[
https://issues.apache.org/jira/browse/IGNITE-14528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17320880#comment-17320880
]
Ignite TC Bot commented on IGNITE-14528:
{panel:title=Branch: [pull/9003/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9003/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}PDS (Indexing){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5965245]]
* {color:#013220}IgnitePdsWithIndexingCoreTestSuite:
IgniteWalRebalanceTest.testRebalanceReassignAndOwnPartitions - PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5965278buildTypeId=IgniteTests24Java8_RunAll]
> AssertionError in
> GridDhtPartitionDemander$RebalanceFuture.ownPartitionsAndFinishFuture:1528
>
>
> Key: IGNITE-14528
> URL: https://issues.apache.org/jira/browse/IGNITE-14528
> Project: Ignite
> Issue Type: Bug
>Reporter: Denis Chudov
>Assignee: Denis Chudov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> the fall of the node during a rebalance
> {code:java}
> 2021-01-31
> 07:45:29.174[ERROR][exchange-worker-#168%DPL_GRID%DplGridNodeName%][org.apache.ignite.Ignite]
> Critical system error detected. Will be handled accordingly to configured
> handler [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
> super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet
> [SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]],
> failureCtx=FailureContext [type=SYSTEM_WORKER_TERMINATION,
> err=java.lang.AssertionError: RebalanceFuture [grp=CacheGroupContext
> [grp=CACHEGROUP_OBJECT_TO_EVICTION_REGISTRY], topVer=AffinityTopologyVersion
> [topVer=46, minorTopVer=0], rebalanceId=27299, routines=22, receivedBytes=0,
> receivedKeys=0, partitionsLeft=1659, startTime=-1, endTime=-1,
> lastCancelledTime=1612068328290, result=true]]]
> java.lang.AssertionError: RebalanceFuture [grp=CacheGroupContext
> [grp=CACHEGROUP_OBJECT_TO_EVICTION_REGISTRY], topVer=AffinityTopologyVersion
> [topVer=46, minorTopVer=0], rebalanceId=27299, routines=22, receivedBytes=0,
> receivedKeys=0, partitionsLeft=1659, startTime=-1, endTime=-1,
> lastCancelledTime=1612068328290, result=true]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander$RebalanceFuture.ownPartitionsAndFinishFuture(GridDhtPartitionDemander.java:1528)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander.finishPreloading(GridDhtPartitionDemander.java:2064)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader.finishPreloading(GridDhtPreloader.java:577)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.processCustomExchangeTask(GridCacheProcessor.java:419)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.processCustomTask(GridCachePartitionExchangeManager.java:3133)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:3280)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:3195)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
> at java.lang.Thread.run(Thread.java:748)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14501) Ignite 3: Fix toString implementations
[
https://issues.apache.org/jira/browse/IGNITE-14501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17320869#comment-17320869
]
Yury Gerzhedovich commented on IGNITE-14501:
[~amashenkov], LGTM
> Ignite 3: Fix toString implementations
> --
>
> Key: IGNITE-14501
> URL: https://issues.apache.org/jira/browse/IGNITE-14501
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Assignee: Andrey Mashenkov
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha2
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> There is a number of places in the codebase where autogenerated IDEA
> {{toString()}} implementations are used (for example, {{ModuleRegistry}},
> {{NetworkMember}})) or non-conformant {{toString()}} implementations
> ({{Peer}} in raft-client).
> We need to fix the {{toString()}} implementations and move
> GridToStringBuilder from Ignite 2.x to avoid further similar issues.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14503) Ability to specify project (fork) via the Version
[
https://issues.apache.org/jira/browse/IGNITE-14503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17320855#comment-17320855
]
Anton Vinogradov commented on IGNITE-14503:
---
Merged into ignite-ducktape.
> Ability to specify project (fork) via the Version
> -
>
> Key: IGNITE-14503
> URL: https://issues.apache.org/jira/browse/IGNITE-14503
> Project: Ignite
> Issue Type: Improvement
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently we able to define fork name via globals
> {{"project": "fork", "ignite_versions": "dev"}}
> This should be also possible to define a project by version
> {{ "ignite_versions": "[dev, ignite-2.8.1, fork-dev, superfork-9.999]"}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14423) Node failure caused by AssertionError: Transaction does not own lock for update
[
https://issues.apache.org/jira/browse/IGNITE-14423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Ivanov updated IGNITE-14423:
--
Reviewer: Peter Ivanov (was: Vyacheslav Koptilin)
> Node failure caused by AssertionError: Transaction does not own lock for
> update
> ---
>
> Key: IGNITE-14423
> URL: https://issues.apache.org/jira/browse/IGNITE-14423
> Project: Ignite
> Issue Type: Bug
>Reporter: Denis Chudov
>Assignee: Denis Chudov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Scenario:
> 1. Start 3 servers
> 2. Start 2 clients
> 3. Start two OPTIMISTIC transactions with the same key from different client
> nodes
> 4. Transfer transactions to PREPARED STATE on primary node
> 5. Stop one client node(whose transaction changed state to PREPARED last)
>
> Error in log:
> {code:java}
> [2021-03-03
> 08:52:59,807][ERROR][sys-#499%transactions.TxRecoveryWithConcurrentRollbackTest1%][GridNearTxLocal]
> Failed completing the transaction: [commit=true, tx=GridDhtTxLocal
> [nearNodeId=29551b46-74ef-4e35-af4a-d97809cc5260,
> nearFutId=08b25a6f771-eec14fa0-02ef-46b9-97d9-0f2b7c851ddb, nearMiniId=1,
> nearFinFutId=null, nearFinMiniId=0, nearXidVer=GridCacheVersion
> [topVer=226230774, order=1614750773047, nodeOrder=4], lb=tx,
> super=GridDhtTxLocalAdapter [nearOnOriginatingNode=false,
> nearNodes=KeySetView [], dhtNodes=KeySetView [], explicitLock=false,
> super=IgniteTxLocalAdapter [completedBase=null, sndTransformedVals=false,
> depEnabled=false, txState=IgniteTxStateImpl [activeCacheIds=[1544803905],
> recovery=false, mvccEnabled=false, mvccCachingCacheIds=[], txMap=ArrayList
> [IgniteTxEntry [txKey=IgniteTxKey [key=KeyCacheObjectImpl [part=1, val=1,
> hasValBytes=true], cacheId=1544803905], val=TxEntryValueHolder
> [val=CacheObjectImpl [val=null, hasValBytes=true], op=CREATE],
> prevVal=TxEntryValueHolder [val=null, op=NOOP], oldVal=TxEntryValueHolder
> [val=null, op=NOOP], entryProcessorsCol=null, ttl=-1, conflictExpireTime=-1,
> conflictVer=null, explicitVer=null, dhtVer=null,
> filters=CacheEntryPredicate[] [], filtersPassed=false, filtersSet=false,
> entry=GridDhtCacheEntry [rdrs=ReaderId[] [], part=1,
> super=GridDistributedCacheEntry [super=GridCacheMapEntry
> [key=KeyCacheObjectImpl [part=1, val=1, hasValBytes=true], val=null,
> ver=GridCacheVersion [topVer=226230774, order=1614750774035, nodeOrder=2],
> hash=1, extras=GridCacheMvccEntryExtras [mvcc=GridCacheMvcc [locs=LinkedList
> [GridCacheMvccCandidate [nodeId=b1f1a8e0-e1e8-4084-b9c6-bdd2a271,
> ver=GridCacheVersion [topVer=226230774, order=1614750774033, nodeOrder=2],
> threadId=364, id=5, topVer=AffinityTopologyVersion [topVer=5, minorTopVer=0],
> reentry=null, otherNodeId=207c7f09-21a9-4b99-b631-3304a522b002,
> otherVer=GridCacheVersion [topVer=226230774, order=1614750774032,
> nodeOrder=5], mappedDhtNodes=null, mappedNearNodes=null, ownerVer=null,
> serOrder=null, key=KeyCacheObjectImpl [part=1, val=1, hasValBytes=true],
> masks=local=1|owner=1|ready=1|reentry=0|used=0|tx=1|single_implicit=0|dht_local=1|near_local=0|removed=0|read=0,
> prevVer=null, nextVer=null]], rmts=null]], flags=3]]], prepared=1,
> locked=false, nodeId=null, locMapped=false, expiryPlc=null,
> transferExpiryPlc=false, flags=0, partUpdateCntr=0, serReadVer=null,
> xidVer=null]]], super=IgniteTxAdapter [xidVer=GridCacheVersion
> [topVer=226230774, order=1614750774035, nodeOrder=2], writeVer=null,
> implicit=false, loc=true, threadId=686, startTime=1614750774753,
> nodeId=b1f1a8e0-e1e8-4084-b9c6-bdd2a271, isolation=READ_COMMITTED,
> concurrency=OPTIMISTIC, timeout=5000, sysInvalidate=true, sys=false, plc=2,
> commitVer=GridCacheVersion [topVer=226230774, order=1614750774035,
> nodeOrder=2], finalizing=RECOVERY_FINISH, invalidParts=null, state=UNKNOWN,
> timedOut=false, topVer=AffinityTopologyVersion [topVer=5, minorTopVer=0],
> mvccSnapshot=null, skipCompletedVers=false, parentTx=null, duration=5048ms,
> onePhaseCommit=false], size=1
> class
> org.apache.ignite.internal.transactions.IgniteTxHeuristicCheckedException:
> Committing a transaction has produced runtime exception
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxAdapter.heuristicException(IgniteTxAdapter.java:813)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter.userCommit(IgniteTxLocalAdapter.java:969)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocalAdapter.localFinish(GridDhtTxLocalAdapter.java:794)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.localFinish(GridDhtTxLocal.java:605)
> at
>
[jira] [Commented] (IGNITE-14517) Inconsistent behavior of the method NetworkCluster#allMembers
[ https://issues.apache.org/jira/browse/IGNITE-14517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17320843#comment-17320843 ] Alexey Scherbakov commented on IGNITE-14517: [~sdanilov] LGTM. Merged to master #6b2086977c730296caebcd3264bd75ac6a9dfcee > Inconsistent behavior of the method NetworkCluster#allMembers > - > > Key: IGNITE-14517 > URL: https://issues.apache.org/jira/browse/IGNITE-14517 > Project: Ignite > Issue Type: Bug >Reporter: Alexey Scherbakov >Assignee: Semyon Danilov >Priority: Major > Labels: ignite-3 > Time Spent: 1.5h > Remaining Estimate: 0h > > This method reports invalid number of alive nodes when a node is stopped > gracefully. > The scenario: > # Start the cluster of 3 nodes: n1, n2, n3, wait for topology. > # Request n2 NetworkCluster#allMembers. It will return 3. > # Stop node n1. > # Request n2 NetworkCluster#allMembers again. It will return 3, but should > return 2. > Here is a failed test from my working branch [1][2] > I've looked into scalecube code and found out the node is stuck in the > io.scalecube.cluster.membership.MembershipProtocolImpl#membershipTable having > MemberStatus.LEAVING state. > The possible fix would avoid using cluster.members at all and instead use > events to maintain local topology. Events seem to work fine. > [1] > [https://github.com/gridgain/apache-ignite-3/blob/ignite-13885/modules/network/src/integrationTest/java/org/apache/ignite/network/scalecube/ITScaleCubeNetworkClusterMessagingTest.java] > [2] > [https://ci.ignite.apache.org/viewLog.html?buildId=5963158=buildResultsDiv=ignite3_Tests_IntegrationTests_ignite3_Tests=pull%2F78] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-14164) SQL. Calcite: org.apache.ignite.internal.processors.query.calcite.exec.ExecutionCancelledException: null
[
https://issues.apache.org/jira/browse/IGNITE-14164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Orlov resolved IGNITE-14164.
---
Resolution: Duplicate
> SQL. Calcite:
> org.apache.ignite.internal.processors.query.calcite.exec.ExecutionCancelledException:
> null
>
>
> Key: IGNITE-14164
> URL: https://issues.apache.org/jira/browse/IGNITE-14164
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Fedor Malchikov
>Priority: Minor
> Attachments: ignite.log
>
>
> {code:java}
> [20:48:28,961][INFO][client-connector-#135][CalciteQueryProcessor] Going to
> execute new query with Calcite: sql=SELECT t17_1.int_col1, t17_2.int_col1,
> t17_1.id FROM t17_1 INNER JOIN t17_2 ON t17_1.id=t17_2.id ORDER BY t17_1.id
> [20:48:28,980][WARNING][calciteQry-#176][ExecutionServiceImpl] Execution is
> cancelled.
> class
> org.apache.ignite.internal.processors.query.calcite.exec.ExecutionCancelledException:
> null
> at
> org.apache.ignite.internal.processors.query.calcite.exec.rel.AbstractNode.checkState(AbstractNode.java:183)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.rel.Outbox.onAcknowledge(Outbox.java:107)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.ExchangeServiceImpl.onMessage(ExchangeServiceImpl.java:198)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.ExchangeServiceImpl.lambda$init$2(ExchangeServiceImpl.java:147)
> at
> org.apache.ignite.internal.processors.query.calcite.message.MessageServiceImpl.onMessageInternal(MessageServiceImpl.java:276)
> at
> org.apache.ignite.internal.processors.query.calcite.message.MessageServiceImpl.lambda$onMessage$0(MessageServiceImpl.java:256)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13548) Calcite integration. DROP TABLE support
[ https://issues.apache.org/jira/browse/IGNITE-13548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17320799#comment-17320799 ] Konstantin Orlov commented on IGNITE-13548: --- [~zstan], [~tledkov-gridgain], folks, do a review please. You could find a PR [here|https://github.com/gridgain/apache-ignite/pull/264]. > Calcite integration. DROP TABLE support > --- > > Key: IGNITE-13548 > URL: https://issues.apache.org/jira/browse/IGNITE-13548 > Project: Ignite > Issue Type: New Feature > Components: sql >Reporter: Yury Gerzhedovich >Assignee: Konstantin Orlov >Priority: Critical > Original Estimate: 40h > Remaining Estimate: 40h > > We need to support DDL commands. The task about the support of DROP TABLE. > Potentially with syntaxis as we already have in the H2 engine. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14385) Add checkpoit information to performance statistics.
[ https://issues.apache.org/jira/browse/IGNITE-14385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-14385: - Fix Version/s: 2.11 > Add checkpoit information to performance statistics. > > > Key: IGNITE-14385 > URL: https://issues.apache.org/jira/browse/IGNITE-14385 > Project: Ignite > Issue Type: Sub-task >Reporter: Sergei Ryzhov >Assignee: Sergei Ryzhov >Priority: Minor > Labels: IEP-35 > Fix For: 2.11 > > Time Spent: 8h 10m > Remaining Estimate: 0h > > Add start/end time and other parameters of checkpoint to performance > statistics. > Add information about throttling if necessary -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-13548) Calcite integration. DROP TABLE support
[ https://issues.apache.org/jira/browse/IGNITE-13548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Orlov reassigned IGNITE-13548: - Assignee: Konstantin Orlov > Calcite integration. DROP TABLE support > --- > > Key: IGNITE-13548 > URL: https://issues.apache.org/jira/browse/IGNITE-13548 > Project: Ignite > Issue Type: New Feature > Components: sql >Reporter: Yury Gerzhedovich >Assignee: Konstantin Orlov >Priority: Critical > Original Estimate: 40h > Remaining Estimate: 40h > > We need to support DDL commands. The task about the support of DROP TABLE. > Potentially with syntaxis as we already have in the H2 engine. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14528) AssertionError in GridDhtPartitionDemander$RebalanceFuture.ownPartitionsAndFinishFuture:1528
[
https://issues.apache.org/jira/browse/IGNITE-14528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17320791#comment-17320791
]
Denis Chudov commented on IGNITE-14528:
---
[~slava.koptilin] could you pls review this fix?
> AssertionError in
> GridDhtPartitionDemander$RebalanceFuture.ownPartitionsAndFinishFuture:1528
>
>
> Key: IGNITE-14528
> URL: https://issues.apache.org/jira/browse/IGNITE-14528
> Project: Ignite
> Issue Type: Bug
>Reporter: Denis Chudov
>Assignee: Denis Chudov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> the fall of the node during a rebalance
> {code:java}
> 2021-01-31
> 07:45:29.174[ERROR][exchange-worker-#168%DPL_GRID%DplGridNodeName%][org.apache.ignite.Ignite]
> Critical system error detected. Will be handled accordingly to configured
> handler [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
> super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet
> [SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]],
> failureCtx=FailureContext [type=SYSTEM_WORKER_TERMINATION,
> err=java.lang.AssertionError: RebalanceFuture [grp=CacheGroupContext
> [grp=CACHEGROUP_OBJECT_TO_EVICTION_REGISTRY], topVer=AffinityTopologyVersion
> [topVer=46, minorTopVer=0], rebalanceId=27299, routines=22, receivedBytes=0,
> receivedKeys=0, partitionsLeft=1659, startTime=-1, endTime=-1,
> lastCancelledTime=1612068328290, result=true]]]
> java.lang.AssertionError: RebalanceFuture [grp=CacheGroupContext
> [grp=CACHEGROUP_OBJECT_TO_EVICTION_REGISTRY], topVer=AffinityTopologyVersion
> [topVer=46, minorTopVer=0], rebalanceId=27299, routines=22, receivedBytes=0,
> receivedKeys=0, partitionsLeft=1659, startTime=-1, endTime=-1,
> lastCancelledTime=1612068328290, result=true]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander$RebalanceFuture.ownPartitionsAndFinishFuture(GridDhtPartitionDemander.java:1528)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander.finishPreloading(GridDhtPartitionDemander.java:2064)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader.finishPreloading(GridDhtPreloader.java:577)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.processCustomExchangeTask(GridCacheProcessor.java:419)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.processCustomTask(GridCachePartitionExchangeManager.java:3133)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:3280)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:3195)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
> at java.lang.Thread.run(Thread.java:748)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14528) AssertionError in GridDhtPartitionDemander$RebalanceFuture.ownPartitionsAndFinishFuture:1528
[
https://issues.apache.org/jira/browse/IGNITE-14528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17320789#comment-17320789
]
Ignite TC Bot commented on IGNITE-14528:
{panel:title=Branch: [pull/9003/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9003/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}PDS (Indexing){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5965245]]
* {color:#013220}IgnitePdsWithIndexingCoreTestSuite:
IgniteWalRebalanceTest.testRebalanceReassignAndOwnPartitions - PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5965278buildTypeId=IgniteTests24Java8_RunAll]
> AssertionError in
> GridDhtPartitionDemander$RebalanceFuture.ownPartitionsAndFinishFuture:1528
>
>
> Key: IGNITE-14528
> URL: https://issues.apache.org/jira/browse/IGNITE-14528
> Project: Ignite
> Issue Type: Bug
>Reporter: Denis Chudov
>Assignee: Denis Chudov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> the fall of the node during a rebalance
> {code:java}
> 2021-01-31
> 07:45:29.174[ERROR][exchange-worker-#168%DPL_GRID%DplGridNodeName%][org.apache.ignite.Ignite]
> Critical system error detected. Will be handled accordingly to configured
> handler [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
> super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet
> [SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]],
> failureCtx=FailureContext [type=SYSTEM_WORKER_TERMINATION,
> err=java.lang.AssertionError: RebalanceFuture [grp=CacheGroupContext
> [grp=CACHEGROUP_OBJECT_TO_EVICTION_REGISTRY], topVer=AffinityTopologyVersion
> [topVer=46, minorTopVer=0], rebalanceId=27299, routines=22, receivedBytes=0,
> receivedKeys=0, partitionsLeft=1659, startTime=-1, endTime=-1,
> lastCancelledTime=1612068328290, result=true]]]
> java.lang.AssertionError: RebalanceFuture [grp=CacheGroupContext
> [grp=CACHEGROUP_OBJECT_TO_EVICTION_REGISTRY], topVer=AffinityTopologyVersion
> [topVer=46, minorTopVer=0], rebalanceId=27299, routines=22, receivedBytes=0,
> receivedKeys=0, partitionsLeft=1659, startTime=-1, endTime=-1,
> lastCancelledTime=1612068328290, result=true]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander$RebalanceFuture.ownPartitionsAndFinishFuture(GridDhtPartitionDemander.java:1528)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander.finishPreloading(GridDhtPartitionDemander.java:2064)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader.finishPreloading(GridDhtPreloader.java:577)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.processCustomExchangeTask(GridCacheProcessor.java:419)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.processCustomTask(GridCachePartitionExchangeManager.java:3133)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:3280)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:3195)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
> at java.lang.Thread.run(Thread.java:748)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-14411) Define minimal set of cluster components and their lifecycle
[ https://issues.apache.org/jira/browse/IGNITE-14411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin reassigned IGNITE-14411: Assignee: Alexander Lapin > Define minimal set of cluster components and their lifecycle > > > Key: IGNITE-14411 > URL: https://issues.apache.org/jira/browse/IGNITE-14411 > Project: Ignite > Issue Type: Sub-task >Reporter: Vyacheslav Koptilin >Assignee: Alexander Lapin >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-13810) Append additional log and metrics info regarding cache expiration.
[ https://issues.apache.org/jira/browse/IGNITE-13810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Sirotkin reassigned IGNITE-13810: Assignee: Konstantin Sirotkin (was: Stanilovsky Evgeny) > Append additional log and metrics info regarding cache expiration. > --- > > Key: IGNITE-13810 > URL: https://issues.apache.org/jira/browse/IGNITE-13810 > Project: Ignite > Issue Type: Improvement > Components: cache >Affects Versions: 2.9 >Reporter: Stanilovsky Evgeny >Assignee: Konstantin Sirotkin >Priority: Major > > Currently we have no any additional information regarding > _cache.withExpiryPolicy_ execution. Additionally it would be very useful to > have a corresponding metric. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-6324) Transactional cache data partially available after crash and further recovery.
[ https://issues.apache.org/jira/browse/IGNITE-6324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17320726#comment-17320726 ] Stanilovsky Evgeny commented on IGNITE-6324: [~sergey-chugunov] can you take a look plz ? > Transactional cache data partially available after crash and further recovery. > -- > > Key: IGNITE-6324 > URL: https://issues.apache.org/jira/browse/IGNITE-6324 > Project: Ignite > Issue Type: Bug > Components: persistence >Affects Versions: 2.10 >Reporter: Stanilovsky Evgeny >Assignee: Stanilovsky Evgeny >Priority: Critical > Attachments: InterruptCommitedThreadTest.java > > Time Spent: 20m > Remaining Estimate: 0h > > If InterruptedException raise in client code during pds store operations we > can obtain inconsistent cache after restart. -- This message was sent by Atlassian Jira (v8.3.4#803005)
