[jira] [Commented] (IGNITE-12852) Comma in field is not supported by COPY command
[ https://issues.apache.org/jira/browse/IGNITE-12852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17584361#comment-17584361 ] Anton Kurbanov commented on IGNITE-12852: - [~tledkov], I've created ticket for that: https://issues.apache.org/jira/browse/IGNITE-17573 > Comma in field is not supported by COPY command > --- > > Key: IGNITE-12852 > URL: https://issues.apache.org/jira/browse/IGNITE-12852 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.8 >Reporter: YuJue Li >Assignee: Anton Kurbanov >Priority: Critical > Fix For: 2.14 > > Time Spent: 1h > Remaining Estimate: 0h > > CREATE TABLE test(a int,b varchar(100),c int,PRIMARY key(a)); > > a.csv: > 1,"a,b",2 > > COPY FROM '/data/a.csv' INTO test (a,b,c) FORMAT CSV; > > The copy command fails because there is a comma in the second field,but this > is a fully legal and compliant CSV format -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-17573) SQL COPY command should support all RFC4180 compatible CSV files
Anton Kurbanov created IGNITE-17573: --- Summary: SQL COPY command should support all RFC4180 compatible CSV files Key: IGNITE-17573 URL: https://issues.apache.org/jira/browse/IGNITE-17573 Project: Ignite Issue Type: Improvement Components: sql Affects Versions: 2.13 Reporter: Anton Kurbanov Assignee: Anton Kurbanov https://www.rfc-editor.org/rfc/rfc4180 Currently there are no ways to handle CSV files with optional header with column names and with line breaks in fields content. SQL COPY command must correctly process all RFC compatible files. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-12852) Comma in field is not supported by COPY command
[ https://issues.apache.org/jira/browse/IGNITE-12852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17584216#comment-17584216 ] Anton Kurbanov commented on IGNITE-12852: - [~tledkov] So, the two major points we are currently missing from the RFC are: ability to parse optional CSV file header and fields with linebreaks. I absolutely agree that we must support both of them, please let me know your opinion whether: 1. should it be implemented as part of this ticket or as a separate issue? 2. we may think of some cumbersome corner case, like: — in current implementation we have relaxed requirements on number of fields in the record, RFC4180 explicitly requires that a number of fields in each row should be the same — this may lead to delayed detection of whether the row is on multiple lines or the record is broken as we may potentially lookup for enclosing bracket until the unknown place in the file which may be even not found, a simple example would be a single column CSV file (something like dictionary) with broken record in the very beginning with the linebreak. so the question is that do we want to commit to RFC or leave this option as a flag and attempt to introduce some fail-fast option? > Comma in field is not supported by COPY command > --- > > Key: IGNITE-12852 > URL: https://issues.apache.org/jira/browse/IGNITE-12852 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.8 >Reporter: YuJue Li >Assignee: Anton Kurbanov >Priority: Critical > Fix For: 2.14 > > Time Spent: 1h > Remaining Estimate: 0h > > CREATE TABLE test(a int,b varchar(100),c int,PRIMARY key(a)); > > a.csv: > 1,"a,b",2 > > COPY FROM '/data/a.csv' INTO test (a,b,c) FORMAT CSV; > > The copy command fails because there is a comma in the second field,but this > is a fully legal and compliant CSV format -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-12852) Comma in field is not supported by COPY command
[ https://issues.apache.org/jira/browse/IGNITE-12852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17572473#comment-17572473 ] Anton Kurbanov commented on IGNITE-12852: - [~dpavlov][~nizhikov] Could you please check the patch once again as the branch has been rebased agains fresher master and TC re-run for this ticket? > Comma in field is not supported by COPY command > --- > > Key: IGNITE-12852 > URL: https://issues.apache.org/jira/browse/IGNITE-12852 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.8 >Reporter: YuJue Li >Assignee: Anton Kurbanov >Priority: Critical > Fix For: 2.14 > > Time Spent: 50m > Remaining Estimate: 0h > > CREATE TABLE test(a int,b varchar(100),c int,PRIMARY key(a)); > > a.csv: > 1,"a,b",2 > > COPY FROM '/data/a.csv' INTO test (a,b,c) FORMAT CSV; > > The copy command fails because there is a comma in the second field,but this > is a fully legal and compliant CSV format -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-12852) Comma in field is not supported by COPY command
[ https://issues.apache.org/jira/browse/IGNITE-12852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17563409#comment-17563409 ] Anton Kurbanov commented on IGNITE-12852: - [~liyuj] would it be ok for me to get this ticket assigned back to me? > Comma in field is not supported by COPY command > --- > > Key: IGNITE-12852 > URL: https://issues.apache.org/jira/browse/IGNITE-12852 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.8 >Reporter: YuJue Li >Assignee: YuJue Li >Priority: Critical > Fix For: 2.14 > > Time Spent: 50m > Remaining Estimate: 0h > > CREATE TABLE test(a int,b varchar(100),c int,PRIMARY key(a)); > > a.csv: > 1,"a,b",2 > > COPY FROM '/data/a.csv' INTO test (a,b,c) FORMAT CSV; > > The copy command fails because there is a comma in the second field,but this > is a fully legal and compliant CSV format -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-15977) H2 internally wraps OOM in SQLException
Anton Kurbanov created IGNITE-15977:
---
Summary: H2 internally wraps OOM in SQLException
Key: IGNITE-15977
URL: https://issues.apache.org/jira/browse/IGNITE-15977
Project: Ignite
Issue Type: New Feature
Environment:
Reporter: Anton Kurbanov
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing#executeSqlQuery
should handle the OOME that is wrapped here:
https://github.com/h2database/h2database/blob/master/h2/src/main/org/h2/command/Command.java#L174
{code:java}
catch (OutOfMemoryError e) {
callStop = false;
// there is a serious problem:
// the transaction may be applied partially
// in this case we need to panic:
// close the database
database.shutdownImmediately();
throw DbException.convert(e);
}
{code}
It seems that the exception should be correctly processed here and failure
handler must be called:
https://github.com/apache/ignite/blob/master/modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/IgniteH2Indexing.java#L852
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (IGNITE-14886) Binary metadata registration in EntryProcessor fails after CREATE TABLE with same type
Anton Kurbanov created IGNITE-14886: --- Summary: Binary metadata registration in EntryProcessor fails after CREATE TABLE with same type Key: IGNITE-14886 URL: https://issues.apache.org/jira/browse/IGNITE-14886 Project: Ignite Issue Type: Bug Reporter: Anton Kurbanov Attachments: BinaryObjectEntryProcessorTest.java https://ignite.apache.org/docs/latest/key-value-api/binary-objects#creating-and-modifying-binary-objects This part of documentation assumes that binary object can be processed/created/modified within the EntryProcessor, however in this case it is no longer working unless the type is manually registered before executing the invoke or create table is removed, which renders this documentation part incorrect. This situation happens since the attempt to fix metadata registration deadlock here: https://issues.apache.org/jira/browse/IGNITE-11313 Failing test attached. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-8632) Exception in Ignite shutdown routine can prevent JVM shutdown
[ https://issues.apache.org/jira/browse/IGNITE-8632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Kurbanov reassigned IGNITE-8632: -- Assignee: (was: Anton Kurbanov) > Exception in Ignite shutdown routine can prevent JVM shutdown > - > > Key: IGNITE-8632 > URL: https://issues.apache.org/jira/browse/IGNITE-8632 > Project: Ignite > Issue Type: Bug > Components: general >Reporter: Anton Kurbanov >Priority: Major > > The exception like below left node in stopping state fo forever: > java.lang.NullPointerException: null > at > java.util.concurrent.ConcurrentLinkedQueue.checkNotNull(ConcurrentLinkedQueue.java:914) > at > java.util.concurrent.ConcurrentLinkedQueue.offer(ConcurrentLinkedQueue.java:327) > at > java.util.concurrent.ConcurrentLinkedQueue.add(ConcurrentLinkedQueue.java:297) > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateResponse.addFailedKey(GridNearAtomicUpdateResponse.java:347) > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicSingleUpdateFuture.addFailedKeys(GridDhtAtomicSingleUpdateFuture.java:166) > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicAbstractUpdateFuture.onDone(GridDhtAtomicAbstractUpdateFuture.java:446) > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicAbstractUpdateFuture.onDone(GridDhtAtomicAbstractUpdateFuture.java:56) > at > org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:345) > at > org.apache.ignite.internal.processors.cache.GridCacheMvccManager.cancelClientFutures(GridCacheMvccManager.java:388) > at > org.apache.ignite.internal.processors.cache.GridCacheMvccManager.onStop(GridCacheMvccManager.java:370) > at > org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStop(GridCacheProcessor.java:956) > at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2095) > at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2041) > at > org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2397) > at > org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2360) > at > org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.run(IgnitionEx.java:1871) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-7231) Cassandra-sessions-pool is running after Ignition.stop
[ https://issues.apache.org/jira/browse/IGNITE-7231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Kurbanov reassigned IGNITE-7231: -- Assignee: (was: Anton Kurbanov) > Cassandra-sessions-pool is running after Ignition.stop > -- > > Key: IGNITE-7231 > URL: https://issues.apache.org/jira/browse/IGNITE-7231 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.3 >Reporter: Mikhail Cherkasov >Priority: Minor > Attachments: ThreadDump.txt > > > Cassandra-sessions-pool is running after Ignition.stop. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14379) Fix vulnerability of commons-codec <1.13
[ https://issues.apache.org/jira/browse/IGNITE-14379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17310725#comment-17310725 ] Anton Kurbanov commented on IGNITE-14379: - LGTM, proceed with merge. > Fix vulnerability of commons-codec <1.13 > > > Key: IGNITE-14379 > URL: https://issues.apache.org/jira/browse/IGNITE-14379 > Project: Ignite > Issue Type: Bug > Components: build >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Major > Fix For: 2.11 > > Time Spent: 10m > Remaining Estimate: 0h > > https://www.whitesourcesoftware.com/vulnerability-database/WS-2019-0379 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14115) Introduce JAVA API for persistent store defragmentation and maintenance mode
[ https://issues.apache.org/jira/browse/IGNITE-14115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Kurbanov updated IGNITE-14115: Description: Since a lot of API is available in Java, it would be great to have a possibility to build and develop a cluster management tool. Defragmentation schedule, cancellation and status should be available with Java as well as moving nodes into maintenance mode. was: Since a lot of API is available in Java, it would be great to have a possibility to build and develop a cluster management tool. Defragmentation schedule, cancellation and status should be available with Java. > Introduce JAVA API for persistent store defragmentation and maintenance mode > > > Key: IGNITE-14115 > URL: https://issues.apache.org/jira/browse/IGNITE-14115 > Project: Ignite > Issue Type: Improvement > Components: persistence >Reporter: Anton Kurbanov >Priority: Minor > > Since a lot of API is available in Java, it would be great to have a > possibility to build and develop a cluster management tool. > Defragmentation schedule, cancellation and status should be available with > Java as well as moving nodes into maintenance mode. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14115) Introduce JAVA API for persistent store defragmentation and maintenance mode
[ https://issues.apache.org/jira/browse/IGNITE-14115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Kurbanov updated IGNITE-14115: Summary: Introduce JAVA API for persistent store defragmentation and maintenance mode (was: Introduce JAVA API for persistent store defragmentation) > Introduce JAVA API for persistent store defragmentation and maintenance mode > > > Key: IGNITE-14115 > URL: https://issues.apache.org/jira/browse/IGNITE-14115 > Project: Ignite > Issue Type: Improvement > Components: persistence >Reporter: Anton Kurbanov >Priority: Minor > > Since a lot of API is available in Java, it would be great to have a > possibility to build and develop a cluster management tool. > Defragmentation schedule, cancellation and status should be available with > Java. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14115) Introduce JAVA API for persistent store defragmentation
Anton Kurbanov created IGNITE-14115: --- Summary: Introduce JAVA API for persistent store defragmentation Key: IGNITE-14115 URL: https://issues.apache.org/jira/browse/IGNITE-14115 Project: Ignite Issue Type: Improvement Components: persistence Reporter: Anton Kurbanov Since a lot of API is available in Java, it would be great to have a possibility to build and develop a cluster management tool. Defragmentation schedule, cancellation and status should be available with Java. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13963) Excessive classloading of PlatformDotNetSessionLockResult on thin client connection
[
https://issues.apache.org/jira/browse/IGNITE-13963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Kurbanov updated IGNITE-13963:
Affects Version/s: 2.9
> Excessive classloading of PlatformDotNetSessionLockResult on thin client
> connection
> ---
>
> Key: IGNITE-13963
> URL: https://issues.apache.org/jira/browse/IGNITE-13963
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.9
>Reporter: Anton Kurbanov
>Assignee: Anton Kurbanov
>Priority: Major
>
> Empty constructor must be added to
> org.apache.ignite.internal.processors.platform.websession.PlatformDotNetSessionLockResult.
> Multiple thin clients connections are causing this class to generate
> constructors:
> {code:java}
> [Loaded *sun.reflect.GeneratedSerializationConstructorAccessor99* from
> __JVM_DefineClass__]
> {code}
> This is caused by U.forceEmptyConstructor(cls) call from
> org.apache.ignite.internal.binary.BinaryClassDescriptor#constructor.
> With lots of clients it is possible to create high load on metaspace which
> results in lots of metaspace GC.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13963) Excessive classloading of PlatformDotNetSessionLockResult on thin client connection
[
https://issues.apache.org/jira/browse/IGNITE-13963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Kurbanov updated IGNITE-13963:
Ignite Flags: Release Notes Required (was: Docs Required,Release Notes
Required)
> Excessive classloading of PlatformDotNetSessionLockResult on thin client
> connection
> ---
>
> Key: IGNITE-13963
> URL: https://issues.apache.org/jira/browse/IGNITE-13963
> Project: Ignite
> Issue Type: Bug
>Reporter: Anton Kurbanov
>Assignee: Anton Kurbanov
>Priority: Major
>
> Empty constructor must be added to
> org.apache.ignite.internal.processors.platform.websession.PlatformDotNetSessionLockResult.
> Multiple thin clients connections are causing this class to generate
> constructors:
> {code:java}
> [Loaded *sun.reflect.GeneratedSerializationConstructorAccessor99* from
> __JVM_DefineClass__]
> {code}
> This is caused by U.forceEmptyConstructor(cls) call from
> org.apache.ignite.internal.binary.BinaryClassDescriptor#constructor.
> With lots of clients it is possible to create high load on metaspace which
> results in lots of metaspace GC.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-13963) Excessive classloading of PlatformDotNetSessionLockResult on thin client connection
Anton Kurbanov created IGNITE-13963:
---
Summary: Excessive classloading of PlatformDotNetSessionLockResult
on thin client connection
Key: IGNITE-13963
URL: https://issues.apache.org/jira/browse/IGNITE-13963
Project: Ignite
Issue Type: Bug
Reporter: Anton Kurbanov
Assignee: Anton Kurbanov
Empty constructor must be added to
org.apache.ignite.internal.processors.platform.websession.PlatformDotNetSessionLockResult.
Multiple thin clients connections are causing this class to generate
constructors:
{code:java}
[Loaded *sun.reflect.GeneratedSerializationConstructorAccessor99* from
__JVM_DefineClass__]
{code}
This is caused by U.forceEmptyConstructor(cls) call from
org.apache.ignite.internal.binary.BinaryClassDescriptor#constructor.
With lots of clients it is possible to create high load on metaspace which
results in lots of metaspace GC.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-11110) UnsupportedOperationException: null when stopping grid
[
https://issues.apache.org/jira/browse/IGNITE-0?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Kurbanov updated IGNITE-0:
Release Note: Fixed NPE on stopping grid node with enabled collision SPI.
> UnsupportedOperationException: null when stopping grid
> --
>
> Key: IGNITE-0
> URL: https://issues.apache.org/jira/browse/IGNITE-0
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Jens Borgland
>Assignee: Anton Kurbanov
>Priority: Major
> Fix For: 2.10
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> After upgrading to 2.7 we've started getting these errors when stopping grids:
> {noformat}
> java.lang.UnsupportedOperationException: null
> at
> org.jsr166.ConcurrentLinkedHashMap.clear(ConcurrentLinkedHashMap.java:1551)
> ~[ignite-core-2.7.0.jar:2.7.0]
> at
> org.apache.ignite.internal.processors.job.GridJobProcessor.stop(GridJobProcessor.java:264)
> ~[ignite-core-2.7.0.jar:2.7.0]
> at
> org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2356)
> ~[ignite-core-2.7.0.jar:2.7.0]
> at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2228)
> ~[ignite-core-2.7.0.jar:2.7.0]
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2612)
> ~[ignite-core-2.7.0.jar:2.7.0]
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2575)
> ~[ignite-core-2.7.0.jar:2.7.0]
> at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:379)
> ~[ignite-core-2.7.0.jar:2.7.0]
> at org.apache.ignite.Ignition.stop(Ignition.java:225)
> ~[ignite-core-2.7.0.jar:2.7.0]
> at
> org.apache.ignite.internal.IgniteKernal.close(IgniteKernal.java:3568)
> ~[ignite-core-2.7.0.jar:2.7.0]
> {noformat}
> At first glance it looks likely that it was introduced with commit
> [d04d764|https://github.com/apache/ignite/commit/d04d76440ce86873de7aebc8c03d39484cd1e3e5]
> (the {{GridJobProcessor}} still calls {{clear()}} on maps).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-11110) UnsupportedOperationException: null when stopping grid
[
https://issues.apache.org/jira/browse/IGNITE-0?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17255900#comment-17255900
]
Anton Kurbanov commented on IGNITE-0:
-
[~ilyak] Could you please review the patch?
> UnsupportedOperationException: null when stopping grid
> --
>
> Key: IGNITE-0
> URL: https://issues.apache.org/jira/browse/IGNITE-0
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Jens Borgland
>Assignee: Anton Kurbanov
>Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> After upgrading to 2.7 we've started getting these errors when stopping grids:
> {noformat}
> java.lang.UnsupportedOperationException: null
> at
> org.jsr166.ConcurrentLinkedHashMap.clear(ConcurrentLinkedHashMap.java:1551)
> ~[ignite-core-2.7.0.jar:2.7.0]
> at
> org.apache.ignite.internal.processors.job.GridJobProcessor.stop(GridJobProcessor.java:264)
> ~[ignite-core-2.7.0.jar:2.7.0]
> at
> org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2356)
> ~[ignite-core-2.7.0.jar:2.7.0]
> at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2228)
> ~[ignite-core-2.7.0.jar:2.7.0]
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2612)
> ~[ignite-core-2.7.0.jar:2.7.0]
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2575)
> ~[ignite-core-2.7.0.jar:2.7.0]
> at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:379)
> ~[ignite-core-2.7.0.jar:2.7.0]
> at org.apache.ignite.Ignition.stop(Ignition.java:225)
> ~[ignite-core-2.7.0.jar:2.7.0]
> at
> org.apache.ignite.internal.IgniteKernal.close(IgniteKernal.java:3568)
> ~[ignite-core-2.7.0.jar:2.7.0]
> {noformat}
> At first glance it looks likely that it was introduced with commit
> [d04d764|https://github.com/apache/ignite/commit/d04d76440ce86873de7aebc8c03d39484cd1e3e5]
> (the {{GridJobProcessor}} still calls {{clear()}} on maps).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-11110) UnsupportedOperationException: null when stopping grid
[
https://issues.apache.org/jira/browse/IGNITE-0?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Kurbanov reassigned IGNITE-0:
---
Assignee: Anton Kurbanov
> UnsupportedOperationException: null when stopping grid
> --
>
> Key: IGNITE-0
> URL: https://issues.apache.org/jira/browse/IGNITE-0
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Jens Borgland
>Assignee: Anton Kurbanov
>Priority: Major
>
> After upgrading to 2.7 we've started getting these errors when stopping grids:
> {noformat}
> java.lang.UnsupportedOperationException: null
> at
> org.jsr166.ConcurrentLinkedHashMap.clear(ConcurrentLinkedHashMap.java:1551)
> ~[ignite-core-2.7.0.jar:2.7.0]
> at
> org.apache.ignite.internal.processors.job.GridJobProcessor.stop(GridJobProcessor.java:264)
> ~[ignite-core-2.7.0.jar:2.7.0]
> at
> org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2356)
> ~[ignite-core-2.7.0.jar:2.7.0]
> at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2228)
> ~[ignite-core-2.7.0.jar:2.7.0]
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2612)
> ~[ignite-core-2.7.0.jar:2.7.0]
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2575)
> ~[ignite-core-2.7.0.jar:2.7.0]
> at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:379)
> ~[ignite-core-2.7.0.jar:2.7.0]
> at org.apache.ignite.Ignition.stop(Ignition.java:225)
> ~[ignite-core-2.7.0.jar:2.7.0]
> at
> org.apache.ignite.internal.IgniteKernal.close(IgniteKernal.java:3568)
> ~[ignite-core-2.7.0.jar:2.7.0]
> {noformat}
> At first glance it looks likely that it was introduced with commit
> [d04d764|https://github.com/apache/ignite/commit/d04d76440ce86873de7aebc8c03d39484cd1e3e5]
> (the {{GridJobProcessor}} still calls {{clear()}} on maps).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-10913) Reduce heap occupation by o.a.i.i.processors.cache.persistence.file.FilePageStore instances.
[ https://issues.apache.org/jira/browse/IGNITE-10913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16829308#comment-16829308 ] Anton Kurbanov commented on IGNITE-10913: - [~Denis Chudov], LGTM, except one thing, do we really need new property IGNITE_ENABLE_FILE_STORE_HEAP_OPTIMIZATION? Now it looks like it should be enabled by default. > Reduce heap occupation by > o.a.i.i.processors.cache.persistence.file.FilePageStore instances. > > > Key: IGNITE-10913 > URL: https://issues.apache.org/jira/browse/IGNITE-10913 > Project: Ignite > Issue Type: Improvement >Reporter: Alexei Scherbakov >Assignee: Denis Chudov >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > With large topology and large amount of caches/partitions and enabled > persistence could be millions of FilePageStore objects in heap (for each > partition). > Each instance has a reference to a File (field cfgFile) storing as String > absolute path to a partition. > Also internal File inplementation (on example UnixFile) also allocates space > for file path. > I observed about 2Gb of heap space occupied by these objects in one of > environments. > Solution: dereference (set to null) cfgFile after object creation, create > File object lazily on demand when needed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11721) IgniteJdbcDriver with streaming enabled doesn't use IgniteDataStreamer on executeBatch
Anton Kurbanov created IGNITE-11721: --- Summary: IgniteJdbcDriver with streaming enabled doesn't use IgniteDataStreamer on executeBatch Key: IGNITE-11721 URL: https://issues.apache.org/jira/browse/IGNITE-11721 Project: Ignite Issue Type: Bug Components: jdbc, streaming Affects Versions: 2.7 Reporter: Anton Kurbanov -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11614) Transaction with timeout on cache hangs after cache store failure
[ https://issues.apache.org/jira/browse/IGNITE-11614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Kurbanov updated IGNITE-11614: Attachment: CacheStoreTxPutAllMultiNodeTest.java > Transaction with timeout on cache hangs after cache store failure > - > > Key: IGNITE-11614 > URL: https://issues.apache.org/jira/browse/IGNITE-11614 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.7 >Reporter: Anton Kurbanov >Priority: Major > Attachments: CacheStoreTxPutAllMultiNodeTest.java > > > If CacheStore fails before/during transaction commit, transaction with set > timeout remains active. > Setting cfg.setTransactionConfiguration(new > TransactionConfiguration().setTxTimeoutOnPartitionMapExchange(5000)); fixes > the issue in test. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11614) Transaction with timeout on cache hangs after cache store failure
[ https://issues.apache.org/jira/browse/IGNITE-11614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Kurbanov updated IGNITE-11614: Attachment: (was: GridNearCacheStoreTxPutAllMultiNodeTest.java) > Transaction with timeout on cache hangs after cache store failure > - > > Key: IGNITE-11614 > URL: https://issues.apache.org/jira/browse/IGNITE-11614 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.7 >Reporter: Anton Kurbanov >Priority: Major > > If CacheStore fails before/during transaction commit, transaction with set > timeout remains active. > Setting cfg.setTransactionConfiguration(new > TransactionConfiguration().setTxTimeoutOnPartitionMapExchange(5000)); fixes > the issue in test. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11614) Transaction with timeout on cache hangs after cache store failure
[ https://issues.apache.org/jira/browse/IGNITE-11614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Kurbanov updated IGNITE-11614: Description: If CacheStore fails before/during transaction commit, transaction with set timeout remains active. Setting cfg.setTransactionConfiguration(new TransactionConfiguration().setTxTimeoutOnPartitionMapExchange(5000)); fixes the issue in test. > Transaction with timeout on cache hangs after cache store failure > - > > Key: IGNITE-11614 > URL: https://issues.apache.org/jira/browse/IGNITE-11614 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.7 >Reporter: Anton Kurbanov >Priority: Major > > If CacheStore fails before/during transaction commit, transaction with set > timeout remains active. > Setting cfg.setTransactionConfiguration(new > TransactionConfiguration().setTxTimeoutOnPartitionMapExchange(5000)); fixes > the issue in test. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11614) Transaction with timeout on cache hangs after cache store failure
[ https://issues.apache.org/jira/browse/IGNITE-11614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Kurbanov updated IGNITE-11614: Attachment: GridNearCacheStoreTxPutAllMultiNodeTest.java > Transaction with timeout on cache hangs after cache store failure > - > > Key: IGNITE-11614 > URL: https://issues.apache.org/jira/browse/IGNITE-11614 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.7 >Reporter: Anton Kurbanov >Priority: Major > Attachments: GridNearCacheStoreTxPutAllMultiNodeTest.java > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11614) Transaction with timeout on cache hangs after cache store failure
[ https://issues.apache.org/jira/browse/IGNITE-11614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Kurbanov updated IGNITE-11614: Summary: Transaction with timeout on cache hangs after cache store failure (was: Transaction with timeout on cache with near configuration hangs after cache store failure indefinitely) > Transaction with timeout on cache hangs after cache store failure > - > > Key: IGNITE-11614 > URL: https://issues.apache.org/jira/browse/IGNITE-11614 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.7 >Reporter: Anton Kurbanov >Priority: Major > Attachments: GridNearCacheStoreTxPutAllMultiNodeTest.java > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11614) Transaction with timeout on cache with near configuration hangs after cache store failure indefinitely
Anton Kurbanov created IGNITE-11614: --- Summary: Transaction with timeout on cache with near configuration hangs after cache store failure indefinitely Key: IGNITE-11614 URL: https://issues.apache.org/jira/browse/IGNITE-11614 Project: Ignite Issue Type: Bug Affects Versions: 2.7 Reporter: Anton Kurbanov -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11436) sqlline is not working on Java 9+
[ https://issues.apache.org/jira/browse/IGNITE-11436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Kurbanov updated IGNITE-11436: Component/s: (was: sql) > sqlline is not working on Java 9+ > - > > Key: IGNITE-11436 > URL: https://issues.apache.org/jira/browse/IGNITE-11436 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.7 >Reporter: Anton Kurbanov >Assignee: Anton Kurbanov >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11436) sqlline is not working on Java 9+
Anton Kurbanov created IGNITE-11436: --- Summary: sqlline is not working on Java 9+ Key: IGNITE-11436 URL: https://issues.apache.org/jira/browse/IGNITE-11436 Project: Ignite Issue Type: Bug Components: sql Affects Versions: 2.7 Reporter: Anton Kurbanov Assignee: Anton Kurbanov -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11150) Exchange future synchronously waits for page memory cleanup
[
https://issues.apache.org/jira/browse/IGNITE-11150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Kurbanov updated IGNITE-11150:
Description:
Currently on calling cache.destroy() exchange future waits for page memory to
be cleaned up in
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager#onCacheGroupsStopped
in synchronous way making all cluster operations unresponsive, it severely
affects cases where large caches are destroyed.
{noformat}
"sys-#1009" #1314 prio=5 os_prio=0 tid=0x1824c800 nid=0x308c waiting on
condition [0x7c82e000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:178)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:141)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.onCacheGroupsStopped(GridCacheDatabaseSharedManager.java:1461)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.processCacheStopRequestOnExchangeDone(GridCacheProcessor.java:3081)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.onExchangeDone(GridCacheProcessor.java:3112)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:2162)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.processFullMessage(GridDhtPartitionsExchangeFuture.java:4074)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.access$1600(GridDhtPartitionsExchangeFuture.java:144)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$5.apply(GridDhtPartitionsExchangeFuture.java:3767)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$5.apply(GridDhtPartitionsExchangeFuture.java:3755)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:399)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:354)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onReceiveFullMessage(GridDhtPartitionsExchangeFuture.java:3755)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.processFullPartitionUpdate(GridCachePartitionExchangeManager.java:1737)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$3.onMessage(GridCachePartitionExchangeManager.java:401)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$3.onMessage(GridCachePartitionExchangeManager.java:388)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:3334)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:3313)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1125)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:590)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:391)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:317)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:108)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:307)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1561)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1189)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:127)
at
org.apache.ignite.internal.managers.communication.GridIoManager$8.run(GridIoManager.java:1086)
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)
{noformat}
was:
Currently on calling cache.destroy() exchange future waits for page memory to
be cleaned up in
[jira] [Created] (IGNITE-11150) Exchange future synchronously waits for page memory cleanup
Anton Kurbanov created IGNITE-11150: --- Summary: Exchange future synchronously waits for page memory cleanup Key: IGNITE-11150 URL: https://issues.apache.org/jira/browse/IGNITE-11150 Project: Ignite Issue Type: Bug Affects Versions: 2.7 Reporter: Anton Kurbanov Currently exchange future waits for page memory to be cleaned up in org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager#onCacheGroupsStopped in synchronous way making all cluster operations unresponsive, it severely affects cases where large caches are destroyed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11150) Exchange future synchronously waits for page memory cleanup
[
https://issues.apache.org/jira/browse/IGNITE-11150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Kurbanov updated IGNITE-11150:
Description:
Currently on calling cache.destroy() exchange future waits for page memory to
be cleaned up in
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager#onCacheGroupsStopped
in synchronous way making all cluster operations unresponsive, it severely
affects cases where large caches are destroyed.
{code:java}
"sys-#1009" #1314 prio=5 os_prio=0 tid=0x1824c800 nid=0x308c waiting on
condition [0x7c82e000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:178)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:141)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.onCacheGroupsStopped(GridCacheDatabaseSharedManager.java:1461)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.processCacheStopRequestOnExchangeDone(GridCacheProcessor.java:3081)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.onExchangeDone(GridCacheProcessor.java:3112)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:2162)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.processFullMessage(GridDhtPartitionsExchangeFuture.java:4074)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.access$1600(GridDhtPartitionsExchangeFuture.java:144)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$5.apply(GridDhtPartitionsExchangeFuture.java:3767)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$5.apply(GridDhtPartitionsExchangeFuture.java:3755)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:399)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:354)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onReceiveFullMessage(GridDhtPartitionsExchangeFuture.java:3755)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.processFullPartitionUpdate(GridCachePartitionExchangeManager.java:1737)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$3.onMessage(GridCachePartitionExchangeManager.java:401)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$3.onMessage(GridCachePartitionExchangeManager.java:388)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:3334)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:3313)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1125)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:590)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:391)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:317)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:108)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:307)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1561)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1189)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:127)
at
org.apache.ignite.internal.managers.communication.GridIoManager$8.run(GridIoManager.java:1086)
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}
was:
Currently on calling cache.destroy() exchange future waits for page memory to
be cleaned up in
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager#onCacheGroupsStopped
in synchronous way making all cluster operations unresponsive, it severely
affects cases where large caches are destroyed.
{noformat}
"sys-#1009" #1314 prio=5
[jira] [Updated] (IGNITE-11150) Exchange future synchronously waits for page memory cleanup
[
https://issues.apache.org/jira/browse/IGNITE-11150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Kurbanov updated IGNITE-11150:
Description:
Currently on calling cache.destroy() exchange future waits for page memory to
be cleaned up in
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager#onCacheGroupsStopped
in synchronous way making all cluster operations unresponsive, it severely
affects cases where large caches are destroyed.
{noformat}
"sys-#1009" #1314 prio=5 os_prio=0 tid=0x1824c800 nid=0x308c waiting on
condition [0x7c82e000] java.lang.Thread.State: WAITING (parking) at
sun.misc.Unsafe.park(Native Method) at
java.util.concurrent.locks.LockSupport.park(LockSupport.java:304) at
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:178)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:141)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.onCacheGroupsStopped(GridCacheDatabaseSharedManager.java:1461)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.processCacheStopRequestOnExchangeDone(GridCacheProcessor.java:3081)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.onExchangeDone(GridCacheProcessor.java:3112)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:2162)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.processFullMessage(GridDhtPartitionsExchangeFuture.java:4074)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.access$1600(GridDhtPartitionsExchangeFuture.java:144)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$5.apply(GridDhtPartitionsExchangeFuture.java:3767)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$5.apply(GridDhtPartitionsExchangeFuture.java:3755)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:399)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:354)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onReceiveFullMessage(GridDhtPartitionsExchangeFuture.java:3755)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.processFullPartitionUpdate(GridCachePartitionExchangeManager.java:1737)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$3.onMessage(GridCachePartitionExchangeManager.java:401)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$3.onMessage(GridCachePartitionExchangeManager.java:388)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:3334)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:3313)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1125)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:590)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:391)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:317)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:108)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:307)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1561)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1189)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:127)
at
org.apache.ignite.internal.managers.communication.GridIoManager$8.run(GridIoManager.java:1086)
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)
{noformat}
was:
Currently on calling cache.destroy() exchange future waits for page memory to
be cleaned up in
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager#onCacheGroupsStopped
in synchronous way making all cluster operations unresponsive, it severely
affects cases where large caches are destroyed.
>
[jira] [Updated] (IGNITE-11150) Exchange future synchronously waits for page memory cleanup
[ https://issues.apache.org/jira/browse/IGNITE-11150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Kurbanov updated IGNITE-11150: Description: Currently on calling cache.destroy() exchange future waits for page memory to be cleaned up in org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager#onCacheGroupsStopped in synchronous way making all cluster operations unresponsive, it severely affects cases where large caches are destroyed. was: Currently exchange future waits for page memory to be cleaned up in org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager#onCacheGroupsStopped in synchronous way making all cluster operations unresponsive, it severely affects cases where large caches are destroyed. > Exchange future synchronously waits for page memory cleanup > --- > > Key: IGNITE-11150 > URL: https://issues.apache.org/jira/browse/IGNITE-11150 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.7 >Reporter: Anton Kurbanov >Priority: Major > > Currently on calling cache.destroy() exchange future waits for page memory to > be cleaned up in > org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager#onCacheGroupsStopped > in synchronous way making all cluster operations unresponsive, it severely > affects cases where large caches are destroyed. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10860) Exception on GridJobProcessor.stop()
[ https://issues.apache.org/jira/browse/IGNITE-10860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Kurbanov reassigned IGNITE-10860: --- Assignee: Anton Kurbanov > Exception on GridJobProcessor.stop() > > > Key: IGNITE-10860 > URL: https://issues.apache.org/jira/browse/IGNITE-10860 > Project: Ignite > Issue Type: Bug >Reporter: Anton Kurbanov >Assignee: Anton Kurbanov >Priority: Minor > > IGNITE-9056 made calling clear() to throw UnsupportedOperationException from > org.jsr166.ConcurrentLinkedHashMap. > > Need to verify all calls to .clear(). > > java.lang.UnsupportedOperationException: null > at > org.jsr166.ConcurrentLinkedHashMap.clear(ConcurrentLinkedHashMap.java:1551) > at > org.apache.ignite.internal.processors.job.GridJobProcessor.stop(GridJobProcessor.java:264) > at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2356) > at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2228) > at > org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2612) > at > org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2575) > at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:379) > at org.apache.ignite.Ignition.stop(Ignition.java:225) > at org.apache.ignite.internal.IgniteKernal.close(IgniteKernal.java:3568) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10860) Exception on GridJobProcessor.stop()
Anton Kurbanov created IGNITE-10860: --- Summary: Exception on GridJobProcessor.stop() Key: IGNITE-10860 URL: https://issues.apache.org/jira/browse/IGNITE-10860 Project: Ignite Issue Type: Bug Reporter: Anton Kurbanov IGNITE-9056 made calling clear() to throw UnsupportedOperationException from org.jsr166.ConcurrentLinkedHashMap. Need to verify all calls to .clear(). java.lang.UnsupportedOperationException: null at org.jsr166.ConcurrentLinkedHashMap.clear(ConcurrentLinkedHashMap.java:1551) at org.apache.ignite.internal.processors.job.GridJobProcessor.stop(GridJobProcessor.java:264) at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2356) at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2228) at org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2612) at org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2575) at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:379) at org.apache.ignite.Ignition.stop(Ignition.java:225) at org.apache.ignite.internal.IgniteKernal.close(IgniteKernal.java:3568) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10385) NPE in CachePartitionPartialCountersMap.toString
[
https://issues.apache.org/jira/browse/IGNITE-10385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Kurbanov reassigned IGNITE-10385:
---
Assignee: Anton Kurbanov
> NPE in CachePartitionPartialCountersMap.toString
>
>
> Key: IGNITE-10385
> URL: https://issues.apache.org/jira/browse/IGNITE-10385
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.4
>Reporter: Anton Kurbanov
>Assignee: Anton Kurbanov
>Priority: Blocker
>
> {noformat}
> Failed to reinitialize local partitions (preloading will be stopped)
> org.apache.ignite.IgniteException: null
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1032)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:868)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.managers.communication.GridIoMessage.toString(GridIoMessage.java:358)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at java.lang.String.valueOf(String.java:2994) ~[?:1.8.0_171]
> at java.lang.StringBuilder.append(StringBuilder.java:131) ~[?:1.8.0_171]
> at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(TcpCommunicationSpi.java:2653)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage(TcpCommunicationSpi.java:2586)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1642)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.sendToGridTopic(GridIoManager.java:1714)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1160)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.sendLocalPartitions(GridDhtPartitionsExchangeFuture.java:1399)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.sendPartitions(GridDhtPartitionsExchangeFuture.java:1506)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchangeFuture.java:1139)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:703)
> [ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2379)
> [ignite-core-2.4.10.jar:2.4.10]
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> [ignite-core-2.4.10.jar:2.4.10]
> at java.lang.Thread.run(Thread.java:748) [?:1.8.0_171]
> Caused by: org.apache.ignite.IgniteException
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1032)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:830)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:787)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:889)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsSingleMessage.toString(GridDhtPartitionsSingleMessage.java:551)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at java.lang.String.valueOf(String.java:2994) ~[?:1.8.0_171]
> at
> org.apache.ignite.internal.util.GridStringBuilder.a(GridStringBuilder.java:101)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.util.tostring.SBLimitedLength.a(SBLimitedLength.java:88)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:943)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1009)
> ~[ignite-core-2.4.10.jar:2.4.10]
> ... 16 more
> Caused by: java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.CachePartitionPartialCountersMap.toString(CachePartitionPartialCountersMap.java:231)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
[jira] [Updated] (IGNITE-10815) NullPointerException in InitNewCoordinatorFuture.init() leads to cluster hang
[
https://issues.apache.org/jira/browse/IGNITE-10815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Kurbanov updated IGNITE-10815:
Summary: NullPointerException in InitNewCoordinatorFuture.init() leads to
cluster hang (was: NullPointerException during InitNewCoordinatorFuture.init()
leads to cluster hang)
> NullPointerException in InitNewCoordinatorFuture.init() leads to cluster hang
> -
>
> Key: IGNITE-10815
> URL: https://issues.apache.org/jira/browse/IGNITE-10815
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.4
>Reporter: Anton Kurbanov
>Priority: Critical
>
> Possible scenario to reproduce:
> 1. Force few consecutive exchange merges and finish.
> 2. Trigger exchange.
> 3. Shutdown coordinator node before sending/receiving full partitions message.
>
> Stacktrace:
> {code:java}
> 2018-12-24 15:54:02,664 sys-#48%gg% ERROR
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture
> - Failed to init new coordinator future: bd74f7ed-6984-4f78-9941-480df673ab77
> java.lang.NullPointerException: null
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.events(GridDhtPartitionsExchangeFuture.java:534)
> ~[ignite-core-2.4.13.b4.jar:2.4.13.b4]
> at
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager$18.applyx(CacheAffinitySharedManager.java:1790)
> ~[ignite-core-2.4.13.b4.jar:2.4.13.b4]
> at
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager$18.applyx(CacheAffinitySharedManager.java:1738)
> ~[ignite-core-2.4.13.b4.jar:2.4.13.b4]
> at
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.forAllRegisteredCacheGroups(CacheAffinitySharedManager.java:1107)
> ~[ignite-core-2.4.13.b4.jar:2.4.13.b4]
> at
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.initCoordinatorCaches(CacheAffinitySharedManager.java:1738)
> ~[ignite-core-2.4.13.b4.jar:2.4.13.b4]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.InitNewCoordinatorFuture.init(InitNewCoordinatorFuture.java:104)
> ~[ignite-core-2.4.13.b4.jar:2.4.13.b4]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$8$1.call(GridDhtPartitionsExchangeFuture.java:3439)
> [ignite-core-2.4.13.b4.jar:2.4.13.b4]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$8$1.call(GridDhtPartitionsExchangeFuture.java:3435)
> [ignite-core-2.4.13.b4.jar:2.4.13.b4]
> at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6720)
> [ignite-core-2.4.13.b4.jar:2.4.13.b4]
> at
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$2.body(GridClosureProcessor.java:967)
> [ignite-core-2.4.13.b4.jar:2.4.13.b4]
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> [ignite-core-2.4.13.b4.jar:2.4.13.b4]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> [?:1.8.0_171]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> [?:1.8.0_171]
> at java.lang.Thread.run(Thread.java:748) [?:1.8.0_171]
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10815) NullPointerException during InitNewCoordinatorFuture.init() leads to cluster hang
[
https://issues.apache.org/jira/browse/IGNITE-10815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Kurbanov updated IGNITE-10815:
Description:
Possible scenario to reproduce:
1. Force few consecutive exchange merges and finish.
2. Trigger exchange.
3. Shutdown coordinator node before sending/receiving full partitions message.
Stacktrace:
{code:java}
2018-12-24 15:54:02,664 sys-#48%gg% ERROR
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture
- Failed to init new coordinator future: bd74f7ed-6984-4f78-9941-480df673ab77
java.lang.NullPointerException: null
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.events(GridDhtPartitionsExchangeFuture.java:534)
~[ignite-core-2.4.13.b4.jar:2.4.13.b4]
at
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager$18.applyx(CacheAffinitySharedManager.java:1790)
~[ignite-core-2.4.13.b4.jar:2.4.13.b4]
at
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager$18.applyx(CacheAffinitySharedManager.java:1738)
~[ignite-core-2.4.13.b4.jar:2.4.13.b4]
at
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.forAllRegisteredCacheGroups(CacheAffinitySharedManager.java:1107)
~[ignite-core-2.4.13.b4.jar:2.4.13.b4]
at
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.initCoordinatorCaches(CacheAffinitySharedManager.java:1738)
~[ignite-core-2.4.13.b4.jar:2.4.13.b4]
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.InitNewCoordinatorFuture.init(InitNewCoordinatorFuture.java:104)
~[ignite-core-2.4.13.b4.jar:2.4.13.b4]
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$8$1.call(GridDhtPartitionsExchangeFuture.java:3439)
[ignite-core-2.4.13.b4.jar:2.4.13.b4]
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$8$1.call(GridDhtPartitionsExchangeFuture.java:3435)
[ignite-core-2.4.13.b4.jar:2.4.13.b4]
at
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6720)
[ignite-core-2.4.13.b4.jar:2.4.13.b4]
at
org.apache.ignite.internal.processors.closure.GridClosureProcessor$2.body(GridClosureProcessor.java:967)
[ignite-core-2.4.13.b4.jar:2.4.13.b4]
at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
[ignite-core-2.4.13.b4.jar:2.4.13.b4]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
[?:1.8.0_171]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
[?:1.8.0_171]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_171]
{code}
was:
Possible scenario to reproduce:
1. Force few consecutive exchange merges and finish.
2. Trigger exchange.
3. Shutdown coordinator node before sending/receiving full partitions message.
Stacktrace:
2018-12-24 15:54:02,664 [sys-#48%gg%] ERROR
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture
- Failed to init new coordinator future: bd74f7ed-6984-4f78-9941-480df673ab77
java.lang.NullPointerException: null
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.events(GridDhtPartitionsExchangeFuture.java:534)
~[ignite-core-2.4.13.b4.jar:2.4.13.b4]
at
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager$18.applyx(CacheAffinitySharedManager.java:1790)
~[ignite-core-2.4.13.b4.jar:2.4.13.b4]
at
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager$18.applyx(CacheAffinitySharedManager.java:1738)
~[ignite-core-2.4.13.b4.jar:2.4.13.b4]
at
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.forAllRegisteredCacheGroups(CacheAffinitySharedManager.java:1107)
~[ignite-core-2.4.13.b4.jar:2.4.13.b4]
at
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.initCoordinatorCaches(CacheAffinitySharedManager.java:1738)
~[ignite-core-2.4.13.b4.jar:2.4.13.b4]
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.InitNewCoordinatorFuture.init(InitNewCoordinatorFuture.java:104)
~[ignite-core-2.4.13.b4.jar:2.4.13.b4]
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$8$1.call(GridDhtPartitionsExchangeFuture.java:3439)
[ignite-core-2.4.13.b4.jar:2.4.13.b4]
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$8$1.call(GridDhtPartitionsExchangeFuture.java:3435)
[ignite-core-2.4.13.b4.jar:2.4.13.b4]
at
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6720)
[ignite-core-2.4.13.b4.jar:2.4.13.b4]
at
org.apache.ignite.internal.processors.closure.GridClosureProcessor$2.body(GridClosureProcessor.java:967)
[jira] [Created] (IGNITE-10815) NullPointerException during InitNewCoordinatorFuture.init() leads to cluster hang
Anton Kurbanov created IGNITE-10815: --- Summary: NullPointerException during InitNewCoordinatorFuture.init() leads to cluster hang Key: IGNITE-10815 URL: https://issues.apache.org/jira/browse/IGNITE-10815 Project: Ignite Issue Type: Bug Affects Versions: 2.4 Reporter: Anton Kurbanov Possible scenario to reproduce: 1. Force few consecutive exchange merges and finish. 2. Trigger exchange. 3. Shutdown coordinator node before sending/receiving full partitions message. Stacktrace: 2018-12-24 15:54:02,664 [sys-#48%gg%] ERROR org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture - Failed to init new coordinator future: bd74f7ed-6984-4f78-9941-480df673ab77 java.lang.NullPointerException: null at org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.events(GridDhtPartitionsExchangeFuture.java:534) ~[ignite-core-2.4.13.b4.jar:2.4.13.b4] at org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager$18.applyx(CacheAffinitySharedManager.java:1790) ~[ignite-core-2.4.13.b4.jar:2.4.13.b4] at org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager$18.applyx(CacheAffinitySharedManager.java:1738) ~[ignite-core-2.4.13.b4.jar:2.4.13.b4] at org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.forAllRegisteredCacheGroups(CacheAffinitySharedManager.java:1107) ~[ignite-core-2.4.13.b4.jar:2.4.13.b4] at org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.initCoordinatorCaches(CacheAffinitySharedManager.java:1738) ~[ignite-core-2.4.13.b4.jar:2.4.13.b4] at org.apache.ignite.internal.processors.cache.distributed.dht.preloader.InitNewCoordinatorFuture.init(InitNewCoordinatorFuture.java:104) ~[ignite-core-2.4.13.b4.jar:2.4.13.b4] at org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$8$1.call(GridDhtPartitionsExchangeFuture.java:3439) [ignite-core-2.4.13.b4.jar:2.4.13.b4] at org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$8$1.call(GridDhtPartitionsExchangeFuture.java:3435) [ignite-core-2.4.13.b4.jar:2.4.13.b4] at org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6720) [ignite-core-2.4.13.b4.jar:2.4.13.b4] at org.apache.ignite.internal.processors.closure.GridClosureProcessor$2.body(GridClosureProcessor.java:967) [ignite-core-2.4.13.b4.jar:2.4.13.b4] at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110) [ignite-core-2.4.13.b4.jar:2.4.13.b4] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_171] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_171] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_171] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10814) Exceptions thrown in InitNewCoordinatorFuture.init() are ignored
Anton Kurbanov created IGNITE-10814: --- Summary: Exceptions thrown in InitNewCoordinatorFuture.init() are ignored Key: IGNITE-10814 URL: https://issues.apache.org/jira/browse/IGNITE-10814 Project: Ignite Issue Type: Bug Affects Versions: 2.4 Reporter: Anton Kurbanov Exceptions thrown by InitNewCoordinatorFuture.init() called from GridDhtPartitionsExchangeFuture.onNodeLeft is ignored silently and may result in cluster hang without cause seen in logs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10385) NPE in CachePartitionPartialCountersMap.toString
[
https://issues.apache.org/jira/browse/IGNITE-10385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Kurbanov updated IGNITE-10385:
Ignite Flags: (was: Docs Required)
Component/s: general
> NPE in CachePartitionPartialCountersMap.toString
>
>
> Key: IGNITE-10385
> URL: https://issues.apache.org/jira/browse/IGNITE-10385
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.4
>Reporter: Anton Kurbanov
>Priority: Major
>
> {noformat}
> Failed to reinitialize local partitions (preloading will be stopped)
> org.apache.ignite.IgniteException: null
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1032)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:868)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.managers.communication.GridIoMessage.toString(GridIoMessage.java:358)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at java.lang.String.valueOf(String.java:2994) ~[?:1.8.0_171]
> at java.lang.StringBuilder.append(StringBuilder.java:131) ~[?:1.8.0_171]
> at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(TcpCommunicationSpi.java:2653)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage(TcpCommunicationSpi.java:2586)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1642)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.sendToGridTopic(GridIoManager.java:1714)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1160)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.sendLocalPartitions(GridDhtPartitionsExchangeFuture.java:1399)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.sendPartitions(GridDhtPartitionsExchangeFuture.java:1506)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchangeFuture.java:1139)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:703)
> [ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2379)
> [ignite-core-2.4.10.jar:2.4.10]
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> [ignite-core-2.4.10.jar:2.4.10]
> at java.lang.Thread.run(Thread.java:748) [?:1.8.0_171]
> Caused by: org.apache.ignite.IgniteException
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1032)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:830)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:787)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:889)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsSingleMessage.toString(GridDhtPartitionsSingleMessage.java:551)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at java.lang.String.valueOf(String.java:2994) ~[?:1.8.0_171]
> at
> org.apache.ignite.internal.util.GridStringBuilder.a(GridStringBuilder.java:101)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.util.tostring.SBLimitedLength.a(SBLimitedLength.java:88)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:943)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1009)
> ~[ignite-core-2.4.10.jar:2.4.10]
> ... 16 more
> Caused by: java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.CachePartitionPartialCountersMap.toString(CachePartitionPartialCountersMap.java:231)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
[jira] [Updated] (IGNITE-10385) NPE in CachePartitionPartialCountersMap.toString
[
https://issues.apache.org/jira/browse/IGNITE-10385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Kurbanov updated IGNITE-10385:
Description:
{noformat}
Failed to reinitialize local partitions (preloading will be stopped)
org.apache.ignite.IgniteException: null
at
org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1032)
~[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:868)
~[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.internal.managers.communication.GridIoMessage.toString(GridIoMessage.java:358)
~[ignite-core-2.4.10.jar:2.4.10]
at java.lang.String.valueOf(String.java:2994) ~[?:1.8.0_171]
at java.lang.StringBuilder.append(StringBuilder.java:131) ~[?:1.8.0_171]
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(TcpCommunicationSpi.java:2653)
~[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage(TcpCommunicationSpi.java:2586)
~[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1642)
~[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.internal.managers.communication.GridIoManager.sendToGridTopic(GridIoManager.java:1714)
~[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1160)
~[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.sendLocalPartitions(GridDhtPartitionsExchangeFuture.java:1399)
~[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.sendPartitions(GridDhtPartitionsExchangeFuture.java:1506)
~[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchangeFuture.java:1139)
~[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:703)
[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2379)
[ignite-core-2.4.10.jar:2.4.10]
at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
[ignite-core-2.4.10.jar:2.4.10]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_171]
Caused by: org.apache.ignite.IgniteException
at
org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1032)
~[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:830)
~[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:787)
~[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:889)
~[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsSingleMessage.toString(GridDhtPartitionsSingleMessage.java:551)
~[ignite-core-2.4.10.jar:2.4.10]
at java.lang.String.valueOf(String.java:2994) ~[?:1.8.0_171]
at
org.apache.ignite.internal.util.GridStringBuilder.a(GridStringBuilder.java:101)
~[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.internal.util.tostring.SBLimitedLength.a(SBLimitedLength.java:88)
~[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:943)
~[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1009)
~[ignite-core-2.4.10.jar:2.4.10]
... 16 more
Caused by: java.lang.NullPointerException
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.CachePartitionPartialCountersMap.toString(CachePartitionPartialCountersMap.java:231)
~[ignite-core-2.4.10.jar:2.4.10]
at java.lang.String.valueOf(String.java:2994) ~[?:1.8.0_171]
at java.lang.StringBuilder.append(StringBuilder.java:131) ~[?:1.8.0_171]
at java.util.AbstractMap.toString(AbstractMap.java:559) ~[?:1.8.0_171]
at java.lang.String.valueOf(String.java:2994) ~[?:1.8.0_171]
at
org.apache.ignite.internal.util.tostring.CircularStringBuilder.append(CircularStringBuilder.java:84)
~[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.internal.util.tostring.SBLimitedLength.a(SBLimitedLength.java:82)
~[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:943)
[jira] [Updated] (IGNITE-10385) NPE in CachePartitionPartialCountersMap.toString
[
https://issues.apache.org/jira/browse/IGNITE-10385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Kurbanov updated IGNITE-10385:
Description:
{noformat}
exchange-worker-#44%gg% ERROR
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture
- Failed to reinitialize local partitions (preloading will be stopped):
GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=411,
minorTopVer=0], discoEvt=DiscoveryEvent [evtNode=TcpDiscoveryNode
[id=0a755ac5-2bf2-4cd8-b73a-c2bd5f0e66ed, addrs=[10.131.0.164],
sockAddrs=[/10.131.0.164:47500], discPort=47500, order=2, intOrder=2,
lastExchangeTime=1542811944907, loc=false, ver=2.4.10#20180926-sha1:82656e70,
isClient=false], topVer=411, nodeId8=bd022daa, msg=Node failed:
TcpDiscoveryNode [id=0a755ac5-2bf2-4cd8-b73a-c2bd5f0e66ed,
addrs=[10.131.0.164], sockAddrs=[/10.131.0.164:47500], discPort=47500, order=2,
intOrder=2, lastExchangeTime=1542811944907, loc=false,
ver=2.4.10#20180926-sha1:82656e70, isClient=false], type=NODE_FAILED,
tstamp=1542812954959], nodeId=0a755ac5, evt=NODE_FAILED]
org.apache.ignite.IgniteException: null
at
org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1032)
~[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:868)
~[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.internal.managers.communication.GridIoMessage.toString(GridIoMessage.java:358)
~[ignite-core-2.4.10.jar:2.4.10]
at java.lang.String.valueOf(String.java:2994) ~[?:1.8.0_171]
at java.lang.StringBuilder.append(StringBuilder.java:131) ~[?:1.8.0_171]
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(TcpCommunicationSpi.java:2653)
~[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage(TcpCommunicationSpi.java:2586)
~[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1642)
~[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.internal.managers.communication.GridIoManager.sendToGridTopic(GridIoManager.java:1714)
~[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1160)
~[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.sendLocalPartitions(GridDhtPartitionsExchangeFuture.java:1399)
~[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.sendPartitions(GridDhtPartitionsExchangeFuture.java:1506)
~[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchangeFuture.java:1139)
~[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:703)
[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2379)
[ignite-core-2.4.10.jar:2.4.10]
at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
[ignite-core-2.4.10.jar:2.4.10]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_171]
Caused by: org.apache.ignite.IgniteException
at
org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1032)
~[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:830)
~[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:787)
~[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:889)
~[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsSingleMessage.toString(GridDhtPartitionsSingleMessage.java:551)
~[ignite-core-2.4.10.jar:2.4.10]
at java.lang.String.valueOf(String.java:2994) ~[?:1.8.0_171]
at
org.apache.ignite.internal.util.GridStringBuilder.a(GridStringBuilder.java:101)
~[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.internal.util.tostring.SBLimitedLength.a(SBLimitedLength.java:88)
~[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:943)
~[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1009)
~[ignite-core-2.4.10.jar:2.4.10]
... 16 more
Caused
[jira] [Updated] (IGNITE-10385) NPE in CachePartitionPartialCountersMap.toString
[
https://issues.apache.org/jira/browse/IGNITE-10385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Kurbanov updated IGNITE-10385:
Description:
{code:java}
exchange-worker-#44%gg% ERROR
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture
- Failed to reinitialize local partitions (preloading will be stopped):
GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=411,
minorTopVer=0], discoEvt=DiscoveryEvent [evtNode=TcpDiscoveryNode
[id=0a755ac5-2bf2-4cd8-b73a-c2bd5f0e66ed, addrs=[10.131.0.164],
sockAddrs=[/10.131.0.164:47500], discPort=47500, order=2, intOrder=2,
lastExchangeTime=1542811944907, loc=false, ver=2.4.10#20180926-sha1:82656e70,
isClient=false], topVer=411, nodeId8=bd022daa, msg=Node failed:
TcpDiscoveryNode [id=0a755ac5-2bf2-4cd8-b73a-c2bd5f0e66ed,
addrs=[10.131.0.164], sockAddrs=[/10.131.0.164:47500], discPort=47500, order=2,
intOrder=2, lastExchangeTime=1542811944907, loc=false,
ver=2.4.10#20180926-sha1:82656e70, isClient=false], type=NODE_FAILED,
tstamp=1542812954959], nodeId=0a755ac5, evt=NODE_FAILED]
org.apache.ignite.IgniteException: null
at
org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1032)
~[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:868)
~[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.internal.managers.communication.GridIoMessage.toString(GridIoMessage.java:358)
~[ignite-core-2.4.10.jar:2.4.10]
at java.lang.String.valueOf(String.java:2994) ~[?:1.8.0_171]
at java.lang.StringBuilder.append(StringBuilder.java:131) ~[?:1.8.0_171]
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(TcpCommunicationSpi.java:2653)
~[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage(TcpCommunicationSpi.java:2586)
~[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1642)
~[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.internal.managers.communication.GridIoManager.sendToGridTopic(GridIoManager.java:1714)
~[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1160)
~[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.sendLocalPartitions(GridDhtPartitionsExchangeFuture.java:1399)
~[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.sendPartitions(GridDhtPartitionsExchangeFuture.java:1506)
~[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchangeFuture.java:1139)
~[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:703)
[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2379)
[ignite-core-2.4.10.jar:2.4.10]
at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
[ignite-core-2.4.10.jar:2.4.10]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_171]
Caused by: org.apache.ignite.IgniteException
at
org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1032)
~[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:830)
~[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:787)
~[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:889)
~[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsSingleMessage.toString(GridDhtPartitionsSingleMessage.java:551)
~[ignite-core-2.4.10.jar:2.4.10]
at java.lang.String.valueOf(String.java:2994) ~[?:1.8.0_171]
at
org.apache.ignite.internal.util.GridStringBuilder.a(GridStringBuilder.java:101)
~[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.internal.util.tostring.SBLimitedLength.a(SBLimitedLength.java:88)
~[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:943)
~[ignite-core-2.4.10.jar:2.4.10]
at
org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1009)
~[ignite-core-2.4.10.jar:2.4.10]
... 16 more
[jira] [Created] (IGNITE-10385) NPE in CachePartitionPartialCountersMap.toString
Anton Kurbanov created IGNITE-10385: --- Summary: NPE in CachePartitionPartialCountersMap.toString Key: IGNITE-10385 URL: https://issues.apache.org/jira/browse/IGNITE-10385 Project: Ignite Issue Type: Bug Affects Versions: 2.4 Reporter: Anton Kurbanov [exchange-worker-#44%gg%] ERROR org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture - Failed to reinitialize local partitions (preloading will be stopped): GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=411, minorTopVer=0], discoEvt=DiscoveryEvent [evtNode=TcpDiscoveryNode [id=0a755ac5-2bf2-4cd8-b73a-c2bd5f0e66ed, addrs=[10.131.0.164], sockAddrs=[/10.131.0.164:47500], discPort=47500, order=2, intOrder=2, lastExchangeTime=1542811944907, loc=false, ver=2.4.10#20180926-sha1:82656e70, isClient=false], topVer=411, nodeId8=bd022daa, msg=Node failed: TcpDiscoveryNode [id=0a755ac5-2bf2-4cd8-b73a-c2bd5f0e66ed, addrs=[10.131.0.164], sockAddrs=[/10.131.0.164:47500], discPort=47500, order=2, intOrder=2, lastExchangeTime=1542811944907, loc=false, ver=2.4.10#20180926-sha1:82656e70, isClient=false], type=NODE_FAILED, tstamp=1542812954959], nodeId=0a755ac5, evt=NODE_FAILED] org.apache.ignite.IgniteException: null at org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1032) ~[ignite-core-2.4.10.jar:2.4.10] at org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:868) ~[ignite-core-2.4.10.jar:2.4.10] at org.apache.ignite.internal.managers.communication.GridIoMessage.toString(GridIoMessage.java:358) ~[ignite-core-2.4.10.jar:2.4.10] at java.lang.String.valueOf(String.java:2994) ~[?:1.8.0_171] at java.lang.StringBuilder.append(StringBuilder.java:131) ~[?:1.8.0_171] at org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(TcpCommunicationSpi.java:2653) ~[ignite-core-2.4.10.jar:2.4.10] at org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage(TcpCommunicationSpi.java:2586) ~[ignite-core-2.4.10.jar:2.4.10] at org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1642) ~[ignite-core-2.4.10.jar:2.4.10] at org.apache.ignite.internal.managers.communication.GridIoManager.sendToGridTopic(GridIoManager.java:1714) ~[ignite-core-2.4.10.jar:2.4.10] at org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1160) ~[ignite-core-2.4.10.jar:2.4.10] at org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.sendLocalPartitions(GridDhtPartitionsExchangeFuture.java:1399) ~[ignite-core-2.4.10.jar:2.4.10] at org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.sendPartitions(GridDhtPartitionsExchangeFuture.java:1506) ~[ignite-core-2.4.10.jar:2.4.10] at org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchangeFuture.java:1139) ~[ignite-core-2.4.10.jar:2.4.10] at org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:703) [ignite-core-2.4.10.jar:2.4.10] at org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2379) [ignite-core-2.4.10.jar:2.4.10] at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110) [ignite-core-2.4.10.jar:2.4.10] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_171] Caused by: org.apache.ignite.IgniteException at org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1032) ~[ignite-core-2.4.10.jar:2.4.10] at org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:830) ~[ignite-core-2.4.10.jar:2.4.10] at org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:787) ~[ignite-core-2.4.10.jar:2.4.10] at org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:889) ~[ignite-core-2.4.10.jar:2.4.10] at org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsSingleMessage.toString(GridDhtPartitionsSingleMessage.java:551) ~[ignite-core-2.4.10.jar:2.4.10] at java.lang.String.valueOf(String.java:2994) ~[?:1.8.0_171] at org.apache.ignite.internal.util.GridStringBuilder.a(GridStringBuilder.java:101) ~[ignite-core-2.4.10.jar:2.4.10] at org.apache.ignite.internal.util.tostring.SBLimitedLength.a(SBLimitedLength.java:88) ~[ignite-core-2.4.10.jar:2.4.10] at org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:943)
[jira] [Updated] (IGNITE-9972) Deleted entries remain in local partition internal map
[ https://issues.apache.org/jira/browse/IGNITE-9972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Kurbanov updated IGNITE-9972: --- Description: Concurrent transactions leave entries in deleted state in local partition map. > Deleted entries remain in local partition internal map > -- > > Key: IGNITE-9972 > URL: https://issues.apache.org/jira/browse/IGNITE-9972 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.6 >Reporter: Anton Kurbanov >Priority: Major > Attachments: IgniteTxConcurrentRemoveObjectsTest.java > > > Concurrent transactions leave entries in deleted state in local partition map. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9972) Deleted entries remain in local partition internal map
[ https://issues.apache.org/jira/browse/IGNITE-9972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Kurbanov updated IGNITE-9972: --- Attachment: IgniteTxConcurrentRemoveObjectsTest.java > Deleted entries remain in local partition internal map > -- > > Key: IGNITE-9972 > URL: https://issues.apache.org/jira/browse/IGNITE-9972 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.6 >Reporter: Anton Kurbanov >Priority: Major > Attachments: IgniteTxConcurrentRemoveObjectsTest.java > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9972) Deleted entries remain in local partition internal map
Anton Kurbanov created IGNITE-9972: -- Summary: Deleted entries remain in local partition internal map Key: IGNITE-9972 URL: https://issues.apache.org/jira/browse/IGNITE-9972 Project: Ignite Issue Type: Bug Affects Versions: 2.6 Reporter: Anton Kurbanov -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9899) Continuous query handlers are not called on backups when one-phase commit is used
[ https://issues.apache.org/jira/browse/IGNITE-9899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16658879#comment-16658879 ] Anton Kurbanov commented on IGNITE-9899: [~dmekhanikov], the change looks good to me. > Continuous query handlers are not called on backups when one-phase commit is > used > - > > Key: IGNITE-9899 > URL: https://issues.apache.org/jira/browse/IGNITE-9899 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.6 >Reporter: Denis Mekhanikov >Assignee: Denis Mekhanikov >Priority: Major > Fix For: 2.8 > > Attachments: CacheContinuousQueryTxBackupTest.java > > > Consider the following cache configuration: > * Atomicity mode: Transactional > * Cache mode: Partitioned > * Backups: 1 > If a continuous query is registered for such cache, then it's not processed > on backup copies. It results in remote filters not being called on backups > and lost events on changing topology. > Test case is attached: [^CacheContinuousQueryTxBackupTest.java] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9676) Ignite as storage in Spring Session
Anton Kurbanov created IGNITE-9676: -- Summary: Ignite as storage in Spring Session Key: IGNITE-9676 URL: https://issues.apache.org/jira/browse/IGNITE-9676 Project: Ignite Issue Type: New Feature Reporter: Anton Kurbanov Assignee: Anton Kurbanov Implement repository backed with Ignite for sessions clustering with Spring Session. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-8834) SqlQuery not throwing exception after partition loss events
[
https://issues.apache.org/jira/browse/IGNITE-8834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Kurbanov reassigned IGNITE-8834:
--
Assignee: Anton Kurbanov
> SqlQuery not throwing exception after partition loss events
> ---
>
> Key: IGNITE-8834
> URL: https://issues.apache.org/jira/browse/IGNITE-8834
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.4, 2.5
>Reporter: Anton Kurbanov
>Assignee: Anton Kurbanov
>Priority: Major
> Labels: sql-stability
> Fix For: 2.7
>
>
>
> Precondition: 3 server nodes, client listening for partition loss events,
> partitioned cache with backups = 1, partition loss policy = READ_ONLY_SAFE,
> stream some data. Kill 2 nodes, call:
> {code:java}
> SqlQuery query = new SqlQuery<>(Integer.class, "where
> _key>0");
> query.setLocal(false);
> List> list = cache.query(query).getAll();
> {code}
> Cache configuration:
> {code:java}
> public IgniteConfiguration getCfg() {
> IgniteConfiguration cfg = new IgniteConfiguration();
> cfg.setConsistentId(cfg.getIgniteInstanceName());
> cfg.setIncludeEventTypes(EventType.EVT_CACHE_REBALANCE_PART_DATA_LOST);
> TcpDiscoverySpi discovery = new TcpDiscoverySpi();
> TcpDiscoveryVmIpFinder finder = new TcpDiscoveryVmIpFinder();
> finder.setAddresses(Arrays.asList("127.0.0.1:47500..47509"));
> discovery.setIpFinder(finder);
> cfg.setDiscoverySpi(discovery);
> QueryEntity queryEntity = new QueryEntity();
> queryEntity.setKeyType(Integer.class.getName());
> queryEntity.setValueType(Integer.class.getName());
> cfg.setCacheConfiguration(new CacheConfiguration(CACHE)
> .setCacheMode(CacheMode.PARTITIONED)
> .setBackups(1)
> .setAffinity(new RendezvousAffinityFunction())
> .setWriteSynchronizationMode(CacheWriteSynchronizationMode.FULL_SYNC)
> .setPartitionLossPolicy(PartitionLossPolicy.READ_ONLY_SAFE)
> .setQueryEntities(Collections.singletonList(queryEntity)));
> DataStorageConfiguration storageCfg = new DataStorageConfiguration();
>
> storageCfg.getDefaultDataRegionConfiguration().setPersistenceEnabled(true);
> cfg.setDataStorageConfiguration(storageCfg);
> return cfg;
> }
> {code}
> Query is expected to fail, but succeeds and returns entries from partitions
> that are alive.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-8834) SqlQuery not throwing exception after partition loss events
[
https://issues.apache.org/jira/browse/IGNITE-8834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Kurbanov resolved IGNITE-8834.
Resolution: Fixed
Fix Version/s: 2.7
> SqlQuery not throwing exception after partition loss events
> ---
>
> Key: IGNITE-8834
> URL: https://issues.apache.org/jira/browse/IGNITE-8834
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.4, 2.5
>Reporter: Anton Kurbanov
>Priority: Major
> Labels: sql-stability
> Fix For: 2.7
>
>
>
> Precondition: 3 server nodes, client listening for partition loss events,
> partitioned cache with backups = 1, partition loss policy = READ_ONLY_SAFE,
> stream some data. Kill 2 nodes, call:
> {code:java}
> SqlQuery query = new SqlQuery<>(Integer.class, "where
> _key>0");
> query.setLocal(false);
> List> list = cache.query(query).getAll();
> {code}
> Cache configuration:
> {code:java}
> public IgniteConfiguration getCfg() {
> IgniteConfiguration cfg = new IgniteConfiguration();
> cfg.setConsistentId(cfg.getIgniteInstanceName());
> cfg.setIncludeEventTypes(EventType.EVT_CACHE_REBALANCE_PART_DATA_LOST);
> TcpDiscoverySpi discovery = new TcpDiscoverySpi();
> TcpDiscoveryVmIpFinder finder = new TcpDiscoveryVmIpFinder();
> finder.setAddresses(Arrays.asList("127.0.0.1:47500..47509"));
> discovery.setIpFinder(finder);
> cfg.setDiscoverySpi(discovery);
> QueryEntity queryEntity = new QueryEntity();
> queryEntity.setKeyType(Integer.class.getName());
> queryEntity.setValueType(Integer.class.getName());
> cfg.setCacheConfiguration(new CacheConfiguration(CACHE)
> .setCacheMode(CacheMode.PARTITIONED)
> .setBackups(1)
> .setAffinity(new RendezvousAffinityFunction())
> .setWriteSynchronizationMode(CacheWriteSynchronizationMode.FULL_SYNC)
> .setPartitionLossPolicy(PartitionLossPolicy.READ_ONLY_SAFE)
> .setQueryEntities(Collections.singletonList(queryEntity)));
> DataStorageConfiguration storageCfg = new DataStorageConfiguration();
>
> storageCfg.getDefaultDataRegionConfiguration().setPersistenceEnabled(true);
> cfg.setDataStorageConfiguration(storageCfg);
> return cfg;
> }
> {code}
> Query is expected to fail, but succeeds and returns entries from partitions
> that are alive.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8900) SqlFieldsQuery provides incorrect result when item size exceeds page size
[ https://issues.apache.org/jira/browse/IGNITE-8900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Kurbanov updated IGNITE-8900: --- Description: Start several server nodes, then start client, execute queries with value range in where clause. Duplicate entries may be found, some entries may be missing. Results as an example: expected 5 results but got back 3 results (query range 61002664327616 to 610026643276160004), cache.getAll returned 5 entries. expected 8 results but got back 7 results (query range 61002664327616 to 610026643276160007), cache.getAll returned 8 entries. Query results: [61002664327616, 610026643276160003, 610026643276160004, 610026643276160005, 610026643276160005, 610026643276160006, 610026643276160007] Please find reproducer attached. was: Start several server nodes, then start client. As an example: expected 5 results but got back 3 results (query range 61002664327616 to 610026643276160004), cache.getAll returned 5 entries. expected 8 results but got back 7 results (query range 61002664327616 to 610026643276160007), cache.getAll returned 8 entries. Query results: [61002664327616, 610026643276160003, 610026643276160004, 610026643276160005, 610026643276160005, 610026643276160006, 610026643276160007] Please find reproducer attached. > SqlFieldsQuery provides incorrect result when item size exceeds page size > - > > Key: IGNITE-8900 > URL: https://issues.apache.org/jira/browse/IGNITE-8900 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.4 >Reporter: Anton Kurbanov >Priority: Blocker > Attachments: Main.java, Node.java > > > Start several server nodes, then start client, execute queries with value > range in where clause. Duplicate entries may be found, some entries may be > missing. > Results as an example: > expected 5 results but got back 3 results (query range 61002664327616 to > 610026643276160004), cache.getAll returned 5 entries. > expected 8 results but got back 7 results (query range 61002664327616 to > 610026643276160007), cache.getAll returned 8 entries. > Query results: [61002664327616, 610026643276160003, 610026643276160004, > 610026643276160005, 610026643276160005, 610026643276160006, > 610026643276160007] > Please find reproducer attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8900) SqlFieldsQuery provides incorrect result when item size exceeds page size
[ https://issues.apache.org/jira/browse/IGNITE-8900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Kurbanov updated IGNITE-8900: --- Attachment: Main.java > SqlFieldsQuery provides incorrect result when item size exceeds page size > - > > Key: IGNITE-8900 > URL: https://issues.apache.org/jira/browse/IGNITE-8900 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.4 >Reporter: Anton Kurbanov >Priority: Blocker > Attachments: Main.java, Node.java > > > Start several server nodes, then start client. > As an example: > expected 5 results but got back 3 results (query range 61002664327616 to > 610026643276160004), cache.getAll returned 5 entries. > expected 8 results but got back 7 results (query range 61002664327616 to > 610026643276160007), cache.getAll returned 8 entries. > Query results: [61002664327616, 610026643276160003, 610026643276160004, > 610026643276160005, 610026643276160005, 610026643276160006, > 610026643276160007] > Please find reproducer attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8900) SqlFieldsQuery provides incorrect result when item size exceeds page size
[ https://issues.apache.org/jira/browse/IGNITE-8900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Kurbanov updated IGNITE-8900: --- Attachment: Node.java > SqlFieldsQuery provides incorrect result when item size exceeds page size > - > > Key: IGNITE-8900 > URL: https://issues.apache.org/jira/browse/IGNITE-8900 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.4 >Reporter: Anton Kurbanov >Priority: Blocker > Attachments: Main.java, Node.java > > > Start several server nodes, then start client. > As an example: > expected 5 results but got back 3 results (query range 61002664327616 to > 610026643276160004), cache.getAll returned 5 entries. > expected 8 results but got back 7 results (query range 61002664327616 to > 610026643276160007), cache.getAll returned 8 entries. > Query results: [61002664327616, 610026643276160003, 610026643276160004, > 610026643276160005, 610026643276160005, 610026643276160006, > 610026643276160007] > Please find reproducer attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8900) SqlFieldsQuery provides incorrect result when item size exceeds page size
[ https://issues.apache.org/jira/browse/IGNITE-8900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Kurbanov updated IGNITE-8900: --- Attachment: Main.java > SqlFieldsQuery provides incorrect result when item size exceeds page size > - > > Key: IGNITE-8900 > URL: https://issues.apache.org/jira/browse/IGNITE-8900 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.4 >Reporter: Anton Kurbanov >Priority: Blocker > > Start several server nodes, then start client. > As an example: > expected 5 results but got back 3 results (query range 61002664327616 to > 610026643276160004), cache.getAll returned 5 entries. > expected 8 results but got back 7 results (query range 61002664327616 to > 610026643276160007), cache.getAll returned 8 entries. > Query results: [61002664327616, 610026643276160003, 610026643276160004, > 610026643276160005, 610026643276160005, 610026643276160006, > 610026643276160007] > Please find reproducer attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8900) SqlFieldsQuery provides incorrect result when item size exceeds page size
[ https://issues.apache.org/jira/browse/IGNITE-8900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Kurbanov updated IGNITE-8900: --- Attachment: (was: Main.java) > SqlFieldsQuery provides incorrect result when item size exceeds page size > - > > Key: IGNITE-8900 > URL: https://issues.apache.org/jira/browse/IGNITE-8900 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.4 >Reporter: Anton Kurbanov >Priority: Blocker > > Start several server nodes, then start client. > As an example: > expected 5 results but got back 3 results (query range 61002664327616 to > 610026643276160004), cache.getAll returned 5 entries. > expected 8 results but got back 7 results (query range 61002664327616 to > 610026643276160007), cache.getAll returned 8 entries. > Query results: [61002664327616, 610026643276160003, 610026643276160004, > 610026643276160005, 610026643276160005, 610026643276160006, > 610026643276160007] > Please find reproducer attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8900) SqlFieldsQuery provides incorrect result when item size exceeds page size
Anton Kurbanov created IGNITE-8900: -- Summary: SqlFieldsQuery provides incorrect result when item size exceeds page size Key: IGNITE-8900 URL: https://issues.apache.org/jira/browse/IGNITE-8900 Project: Ignite Issue Type: Bug Components: sql Affects Versions: 2.4 Reporter: Anton Kurbanov Start several server nodes, then start client. As an example: expected 5 results but got back 3 results (query range 61002664327616 to 610026643276160004), cache.getAll returned 5 entries. expected 8 results but got back 7 results (query range 61002664327616 to 610026643276160007), cache.getAll returned 8 entries. Query results: [61002664327616, 610026643276160003, 610026643276160004, 610026643276160005, 610026643276160005, 610026643276160006, 610026643276160007] Please find reproducer attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8836) NullPointerException during Ignition.start prevents JVM shutdown
[ https://issues.apache.org/jira/browse/IGNITE-8836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16522117#comment-16522117 ] Anton Kurbanov commented on IGNITE-8836: [TC|https://ci.ignite.apache.org/viewLog.html?buildId=1416980=buildResultsDiv=IgniteTests24Java8_RunAll] > NullPointerException during Ignition.start prevents JVM shutdown > > > Key: IGNITE-8836 > URL: https://issues.apache.org/jira/browse/IGNITE-8836 > Project: Ignite > Issue Type: Bug >Reporter: Anton Kurbanov >Assignee: Anton Kurbanov >Priority: Major > Fix For: 1.9 > > > The exception like below leaves node in stopping state forever: > java.lang.NullPointerException: null > at > java.util.concurrent.ConcurrentLinkedQueue.checkNotNull(ConcurrentLinkedQueue.java:914) > at > java.util.concurrent.ConcurrentLinkedQueue.offer(ConcurrentLinkedQueue.java:327) > at > java.util.concurrent.ConcurrentLinkedQueue.add(ConcurrentLinkedQueue.java:297) > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateResponse.addFailedKey(GridNearAtomicUpdateResponse.java:347) > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicSingleUpdateFuture.addFailedKeys(GridDhtAtomicSingleUpdateFuture.java:166) > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicAbstractUpdateFuture.onDone(GridDhtAtomicAbstractUpdateFuture.java:446) > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicAbstractUpdateFuture.onDone(GridDhtAtomicAbstractUpdateFuture.java:56) > at > org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:345) > at > org.apache.ignite.internal.processors.cache.GridCacheMvccManager.cancelClientFutures(GridCacheMvccManager.java:388) > at > org.apache.ignite.internal.processors.cache.GridCacheMvccManager.onStop(GridCacheMvccManager.java:370) > at > org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStop(GridCacheProcessor.java:956) > at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2095) > at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2041) > at > org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2397) > at > org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2360) > at > org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.run(IgnitionEx.java:1871) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8834) SqlQuery not throwing exception after partition loss events
[
https://issues.apache.org/jira/browse/IGNITE-8834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Kurbanov updated IGNITE-8834:
---
Affects Version/s: 2.5
> SqlQuery not throwing exception after partition loss events
> ---
>
> Key: IGNITE-8834
> URL: https://issues.apache.org/jira/browse/IGNITE-8834
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.4, 2.5
>Reporter: Anton Kurbanov
>Priority: Major
>
>
> Precondition: 3 server nodes, client listening for partition loss events,
> partitioned cache with backups = 1, partition loss policy = READ_ONLY_SAFE,
> stream some data. Kill 2 nodes, call:
> {code:java}
> SqlQuery query = new SqlQuery<>(Integer.class, "where
> _key>0");
> query.setLocal(false);
> List> list = cache.query(query).getAll();
> {code}
> Cache configuration:
> {code:java}
> public IgniteConfiguration getCfg() {
> IgniteConfiguration cfg = new IgniteConfiguration();
> cfg.setConsistentId(cfg.getIgniteInstanceName());
> cfg.setIncludeEventTypes(EventType.EVT_CACHE_REBALANCE_PART_DATA_LOST);
> TcpDiscoverySpi discovery = new TcpDiscoverySpi();
> TcpDiscoveryVmIpFinder finder = new TcpDiscoveryVmIpFinder();
> finder.setAddresses(Arrays.asList("127.0.0.1:47500..47509"));
> discovery.setIpFinder(finder);
> cfg.setDiscoverySpi(discovery);
> QueryEntity queryEntity = new QueryEntity();
> queryEntity.setKeyType(Integer.class.getName());
> queryEntity.setValueType(Integer.class.getName());
> cfg.setCacheConfiguration(new CacheConfiguration(CACHE)
> .setCacheMode(CacheMode.PARTITIONED)
> .setBackups(1)
> .setAffinity(new RendezvousAffinityFunction())
> .setWriteSynchronizationMode(CacheWriteSynchronizationMode.FULL_SYNC)
> .setPartitionLossPolicy(PartitionLossPolicy.READ_ONLY_SAFE)
> .setQueryEntities(Collections.singletonList(queryEntity)));
> DataStorageConfiguration storageCfg = new DataStorageConfiguration();
>
> storageCfg.getDefaultDataRegionConfiguration().setPersistenceEnabled(true);
> cfg.setDataStorageConfiguration(storageCfg);
> return cfg;
> }
> {code}
> Query is expected to fail, but succeeds and returns entries from partitions
> that are alive.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-8836) NullPointerException during Ignition.start prevents JVM shutdown
[ https://issues.apache.org/jira/browse/IGNITE-8836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Kurbanov reassigned IGNITE-8836: -- Assignee: Anton Kurbanov > NullPointerException during Ignition.start prevents JVM shutdown > > > Key: IGNITE-8836 > URL: https://issues.apache.org/jira/browse/IGNITE-8836 > Project: Ignite > Issue Type: Bug >Reporter: Anton Kurbanov >Assignee: Anton Kurbanov >Priority: Major > Fix For: 1.9 > > > The exception like below leaves node in stopping state forever: > java.lang.NullPointerException: null > at > java.util.concurrent.ConcurrentLinkedQueue.checkNotNull(ConcurrentLinkedQueue.java:914) > at > java.util.concurrent.ConcurrentLinkedQueue.offer(ConcurrentLinkedQueue.java:327) > at > java.util.concurrent.ConcurrentLinkedQueue.add(ConcurrentLinkedQueue.java:297) > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateResponse.addFailedKey(GridNearAtomicUpdateResponse.java:347) > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicSingleUpdateFuture.addFailedKeys(GridDhtAtomicSingleUpdateFuture.java:166) > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicAbstractUpdateFuture.onDone(GridDhtAtomicAbstractUpdateFuture.java:446) > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicAbstractUpdateFuture.onDone(GridDhtAtomicAbstractUpdateFuture.java:56) > at > org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:345) > at > org.apache.ignite.internal.processors.cache.GridCacheMvccManager.cancelClientFutures(GridCacheMvccManager.java:388) > at > org.apache.ignite.internal.processors.cache.GridCacheMvccManager.onStop(GridCacheMvccManager.java:370) > at > org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStop(GridCacheProcessor.java:956) > at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2095) > at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2041) > at > org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2397) > at > org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2360) > at > org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.run(IgnitionEx.java:1871) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8836) NullPointerException during Ignition.start prevents JVM shutdown
Anton Kurbanov created IGNITE-8836: -- Summary: NullPointerException during Ignition.start prevents JVM shutdown Key: IGNITE-8836 URL: https://issues.apache.org/jira/browse/IGNITE-8836 Project: Ignite Issue Type: Bug Reporter: Anton Kurbanov Fix For: 1.9 The exception like below leaves node in stopping state forever: java.lang.NullPointerException: null at java.util.concurrent.ConcurrentLinkedQueue.checkNotNull(ConcurrentLinkedQueue.java:914) at java.util.concurrent.ConcurrentLinkedQueue.offer(ConcurrentLinkedQueue.java:327) at java.util.concurrent.ConcurrentLinkedQueue.add(ConcurrentLinkedQueue.java:297) at org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateResponse.addFailedKey(GridNearAtomicUpdateResponse.java:347) at org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicSingleUpdateFuture.addFailedKeys(GridDhtAtomicSingleUpdateFuture.java:166) at org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicAbstractUpdateFuture.onDone(GridDhtAtomicAbstractUpdateFuture.java:446) at org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicAbstractUpdateFuture.onDone(GridDhtAtomicAbstractUpdateFuture.java:56) at org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:345) at org.apache.ignite.internal.processors.cache.GridCacheMvccManager.cancelClientFutures(GridCacheMvccManager.java:388) at org.apache.ignite.internal.processors.cache.GridCacheMvccManager.onStop(GridCacheMvccManager.java:370) at org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStop(GridCacheProcessor.java:956) at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2095) at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2041) at org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2397) at org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2360) at org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.run(IgnitionEx.java:1871) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8834) SqlQuery not throwing exception after partition loss events
Anton Kurbanov created IGNITE-8834:
--
Summary: SqlQuery not throwing exception after partition loss
events
Key: IGNITE-8834
URL: https://issues.apache.org/jira/browse/IGNITE-8834
Project: Ignite
Issue Type: Bug
Components: sql
Affects Versions: 2.4
Reporter: Anton Kurbanov
Precondition: 3 server nodes, client listening for partition loss events,
partitioned cache with backups = 1, partition loss policy = READ_ONLY_SAFE,
stream some data. Kill 2 nodes, call:
{code:java}
SqlQuery query = new SqlQuery<>(Integer.class, "where
_key>0");
query.setLocal(false);
List> list = cache.query(query).getAll();
{code}
Cache configuration:
{code:java}
public IgniteConfiguration getCfg() {
IgniteConfiguration cfg = new IgniteConfiguration();
cfg.setConsistentId(cfg.getIgniteInstanceName());
cfg.setIncludeEventTypes(EventType.EVT_CACHE_REBALANCE_PART_DATA_LOST);
TcpDiscoverySpi discovery = new TcpDiscoverySpi();
TcpDiscoveryVmIpFinder finder = new TcpDiscoveryVmIpFinder();
finder.setAddresses(Arrays.asList("127.0.0.1:47500..47509"));
discovery.setIpFinder(finder);
cfg.setDiscoverySpi(discovery);
QueryEntity queryEntity = new QueryEntity();
queryEntity.setKeyType(Integer.class.getName());
queryEntity.setValueType(Integer.class.getName());
cfg.setCacheConfiguration(new CacheConfiguration(CACHE)
.setCacheMode(CacheMode.PARTITIONED)
.setBackups(1)
.setAffinity(new RendezvousAffinityFunction())
.setWriteSynchronizationMode(CacheWriteSynchronizationMode.FULL_SYNC)
.setPartitionLossPolicy(PartitionLossPolicy.READ_ONLY_SAFE)
.setQueryEntities(Collections.singletonList(queryEntity)));
DataStorageConfiguration storageCfg = new DataStorageConfiguration();
storageCfg.getDefaultDataRegionConfiguration().setPersistenceEnabled(true);
cfg.setDataStorageConfiguration(storageCfg);
return cfg;
}
{code}
Query is expected to fail, but succeeds and returns entries from partitions
that are alive.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-8632) Exception in shutdown routine can prevent JVM shutdown
Anton Kurbanov created IGNITE-8632: -- Summary: Exception in shutdown routine can prevent JVM shutdown Key: IGNITE-8632 URL: https://issues.apache.org/jira/browse/IGNITE-8632 Project: Ignite Issue Type: Bug Components: general Reporter: Anton Kurbanov Assignee: Anton Kurbanov Fix For: 2.6 The exception like below left node in stopping state fo forever: java.lang.NullPointerException: null at java.util.concurrent.ConcurrentLinkedQueue.checkNotNull(ConcurrentLinkedQueue.java:914) at java.util.concurrent.ConcurrentLinkedQueue.offer(ConcurrentLinkedQueue.java:327) at java.util.concurrent.ConcurrentLinkedQueue.add(ConcurrentLinkedQueue.java:297) at org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateResponse.addFailedKey(GridNearAtomicUpdateResponse.java:347) at org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicSingleUpdateFuture.addFailedKeys(GridDhtAtomicSingleUpdateFuture.java:166) at org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicAbstractUpdateFuture.onDone(GridDhtAtomicAbstractUpdateFuture.java:446) at org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicAbstractUpdateFuture.onDone(GridDhtAtomicAbstractUpdateFuture.java:56) at org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:345) at org.apache.ignite.internal.processors.cache.GridCacheMvccManager.cancelClientFutures(GridCacheMvccManager.java:388) at org.apache.ignite.internal.processors.cache.GridCacheMvccManager.onStop(GridCacheMvccManager.java:370) at org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStop(GridCacheProcessor.java:956) at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2095) at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2041) at org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2397) at org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2360) at org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.run(IgnitionEx.java:1871) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8632) Exception in Ignite shutdown routine can prevent JVM shutdown
[ https://issues.apache.org/jira/browse/IGNITE-8632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Kurbanov updated IGNITE-8632: --- Summary: Exception in Ignite shutdown routine can prevent JVM shutdown (was: Exception in shutdown routine can prevent JVM shutdown) > Exception in Ignite shutdown routine can prevent JVM shutdown > - > > Key: IGNITE-8632 > URL: https://issues.apache.org/jira/browse/IGNITE-8632 > Project: Ignite > Issue Type: Bug > Components: general >Reporter: Anton Kurbanov >Assignee: Anton Kurbanov >Priority: Major > Fix For: 2.6 > > > The exception like below left node in stopping state fo forever: > java.lang.NullPointerException: null > at > java.util.concurrent.ConcurrentLinkedQueue.checkNotNull(ConcurrentLinkedQueue.java:914) > at > java.util.concurrent.ConcurrentLinkedQueue.offer(ConcurrentLinkedQueue.java:327) > at > java.util.concurrent.ConcurrentLinkedQueue.add(ConcurrentLinkedQueue.java:297) > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateResponse.addFailedKey(GridNearAtomicUpdateResponse.java:347) > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicSingleUpdateFuture.addFailedKeys(GridDhtAtomicSingleUpdateFuture.java:166) > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicAbstractUpdateFuture.onDone(GridDhtAtomicAbstractUpdateFuture.java:446) > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicAbstractUpdateFuture.onDone(GridDhtAtomicAbstractUpdateFuture.java:56) > at > org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:345) > at > org.apache.ignite.internal.processors.cache.GridCacheMvccManager.cancelClientFutures(GridCacheMvccManager.java:388) > at > org.apache.ignite.internal.processors.cache.GridCacheMvccManager.onStop(GridCacheMvccManager.java:370) > at > org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStop(GridCacheProcessor.java:956) > at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2095) > at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2041) > at > org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2397) > at > org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2360) > at > org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.run(IgnitionEx.java:1871) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-7231) Cassandra-sessions-pool is running after Ignition.stop
[ https://issues.apache.org/jira/browse/IGNITE-7231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Kurbanov reassigned IGNITE-7231: -- Assignee: Anton Kurbanov (was: Mikhail Cherkasov) > Cassandra-sessions-pool is running after Ignition.stop > -- > > Key: IGNITE-7231 > URL: https://issues.apache.org/jira/browse/IGNITE-7231 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.3 >Reporter: Mikhail Cherkasov >Assignee: Anton Kurbanov >Priority: Minor > Fix For: 2.6 > > Attachments: ThreadDump.txt > > > Cassandra-sessions-pool is running after Ignition.stop. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8154) Add an ability to provide ExceptionListener to JmsStreamer
[
https://issues.apache.org/jira/browse/IGNITE-8154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16446193#comment-16446193
]
Anton Kurbanov commented on IGNITE-8154:
Done.
> Add an ability to provide ExceptionListener to JmsStreamer
> --
>
> Key: IGNITE-8154
> URL: https://issues.apache.org/jira/browse/IGNITE-8154
> Project: Ignite
> Issue Type: Improvement
> Components: streaming
>Affects Versions: 2.4
>Reporter: Valentin Kulichenko
>Assignee: Anton Kurbanov
>Priority: Major
> Fix For: 2.6
>
>
> JMS API allows to provide custom {{ExceptionListener}} that is invoked when
> an exception occurs within JMS queue/topic. Currently, {{JmsStreamer}}
> doesn't use this in any way which creates two issues:
> * If there is an exception, it's lost and not even logged.
> * User can't provide their own listener.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8154) Add an ability to provide ExceptionListener to JmsStreamer
[
https://issues.apache.org/jira/browse/IGNITE-8154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16444392#comment-16444392
]
Anton Kurbanov commented on IGNITE-8154:
[~vkulichenko], thank you for review! Made some changes as per your
suggestions, PR refreshed: [PR|https://github.com/apache/ignite/pull/3828]
> Add an ability to provide ExceptionListener to JmsStreamer
> --
>
> Key: IGNITE-8154
> URL: https://issues.apache.org/jira/browse/IGNITE-8154
> Project: Ignite
> Issue Type: Improvement
> Components: streaming
>Affects Versions: 2.4
>Reporter: Valentin Kulichenko
>Assignee: Anton Kurbanov
>Priority: Major
> Fix For: 2.6
>
>
> JMS API allows to provide custom {{ExceptionListener}} that is invoked when
> an exception occurs within JMS queue/topic. Currently, {{JmsStreamer}}
> doesn't use this in any way which creates two issues:
> * If there is an exception, it's lost and not even logged.
> * User can't provide their own listener.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8154) Add an ability to provide ExceptionListener to JmsStreamer
[
https://issues.apache.org/jira/browse/IGNITE-8154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16439494#comment-16439494
]
Anton Kurbanov commented on IGNITE-8154:
Artifact links: [PR|https://github.com/apache/ignite/pull/3828] /
[TC|https://ci.ignite.apache.org/viewQueued.html?itemId=1212512=queuedBuildOverviewTab]
[~slukyanov], [~vkulichenko], could you please review?
> Add an ability to provide ExceptionListener to JmsStreamer
> --
>
> Key: IGNITE-8154
> URL: https://issues.apache.org/jira/browse/IGNITE-8154
> Project: Ignite
> Issue Type: Improvement
> Components: streaming
>Affects Versions: 2.4
>Reporter: Valentin Kulichenko
>Assignee: Anton Kurbanov
>Priority: Major
> Fix For: 2.5
>
>
> JMS API allows to provide custom {{ExceptionListener}} that is invoked when
> an exception occurs within JMS queue/topic. Currently, {{JmsStreamer}}
> doesn't use this in any way which creates two issues:
> * If there is an exception, it's lost and not even logged.
> * User can't provide their own listener.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8110) GridCacheWriteBehindStore.Flusher thread uses the wrong transformation from milliseconds to nanoseconds.
[
https://issues.apache.org/jira/browse/IGNITE-8110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16433999#comment-16433999
]
Anton Kurbanov commented on IGNITE-8110:
[~dpavlov], looks like this test is unrelated. Only affected functionality is
write-behind cache, also found several failures in test's history. On my local
machine this test in suite runs fine.
Failed tests are also different on separate runs for my branch:
RunAll execution, these test succeeded:
[https://ci.ignite.apache.org/viewLog.html?buildId=1176364=buildResultsDiv=IgniteTests24Java8_Cache2]
Separate Cache tests execution where they failed:
[https://ci.ignite.apache.org/viewLog.html?buildId=1177272=buildResultsDiv=IgniteTests24Java8_Cache2]
> GridCacheWriteBehindStore.Flusher thread uses the wrong transformation from
> milliseconds to nanoseconds.
>
>
> Key: IGNITE-8110
> URL: https://issues.apache.org/jira/browse/IGNITE-8110
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.4
>Reporter: Vyacheslav Koptilin
>Assignee: Anton Kurbanov
>Priority: Minor
> Fix For: 2.6
>
>
> The initial value of a cache flushing frequency is defined as follows:
> {code}
> /** Cache flushing frequence in nanos. */
> protected long cacheFlushFreqNanos = cacheFlushFreq * 1000;
> {code}
> where is {{cacheFlushFreq}} is equal to
> {code}
> /** Default flush frequency for write-behind cache store in milliseconds.
> */
> public static final long DFLT_WRITE_BEHIND_FLUSH_FREQUENCY = 5000;
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-8154) Add an ability to provide ExceptionListener to JmsStreamer
[
https://issues.apache.org/jira/browse/IGNITE-8154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Kurbanov reassigned IGNITE-8154:
--
Assignee: Anton Kurbanov (was: Valentin Kulichenko)
> Add an ability to provide ExceptionListener to JmsStreamer
> --
>
> Key: IGNITE-8154
> URL: https://issues.apache.org/jira/browse/IGNITE-8154
> Project: Ignite
> Issue Type: Improvement
> Components: streaming
>Affects Versions: 2.4
>Reporter: Valentin Kulichenko
>Assignee: Anton Kurbanov
>Priority: Major
> Fix For: 2.5
>
>
> JMS API allows to provide custom {{ExceptionListener}} that is invoked when
> an exception occurs within JMS queue/topic. Currently, {{JmsStreamer}}
> doesn't use this in any way which creates two issues:
> * If there is an exception, it's lost and not even logged.
> * User can't provide their own listener.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-2096) AtomicConfiguration and CollectionConfiguration should be properly checked for consistency
[
https://issues.apache.org/jira/browse/IGNITE-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16430511#comment-16430511
]
Anton Kurbanov commented on IGNITE-2096:
Added java code to test how AtomicConfiguration works.
> AtomicConfiguration and CollectionConfiguration should be properly checked
> for consistency
> --
>
> Key: IGNITE-2096
> URL: https://issues.apache.org/jira/browse/IGNITE-2096
> Project: Ignite
> Issue Type: Bug
> Components: data structures
>Reporter: Valentin Kulichenko
>Assignee: Anton Kurbanov
>Priority: Major
> Labels: newbie, usability
> Attachments: IgniteAtomicTypesConfigurationTest.java
>
>
> Currently {{AtomicConfiguration}} and {{CollectionConfiguration}} are mapped
> to system caches configuration and consistency is checked like for any other
> cache. This leads to unintuitive errors.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-2096) AtomicConfiguration and CollectionConfiguration should be properly checked for consistency
[
https://issues.apache.org/jira/browse/IGNITE-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Kurbanov updated IGNITE-2096:
---
Attachment: (was: IgniteAtomicTypesConfigurationTest.java)
> AtomicConfiguration and CollectionConfiguration should be properly checked
> for consistency
> --
>
> Key: IGNITE-2096
> URL: https://issues.apache.org/jira/browse/IGNITE-2096
> Project: Ignite
> Issue Type: Bug
> Components: data structures
>Reporter: Valentin Kulichenko
>Assignee: Anton Kurbanov
>Priority: Major
> Labels: newbie, usability
> Attachments: IgniteAtomicTypesConfigurationTest.java
>
>
> Currently {{AtomicConfiguration}} and {{CollectionConfiguration}} are mapped
> to system caches configuration and consistency is checked like for any other
> cache. This leads to unintuitive errors.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-2096) AtomicConfiguration and CollectionConfiguration should be properly checked for consistency
[
https://issues.apache.org/jira/browse/IGNITE-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Kurbanov updated IGNITE-2096:
---
Attachment: IgniteAtomicTypesConfigurationTest.java
> AtomicConfiguration and CollectionConfiguration should be properly checked
> for consistency
> --
>
> Key: IGNITE-2096
> URL: https://issues.apache.org/jira/browse/IGNITE-2096
> Project: Ignite
> Issue Type: Bug
> Components: data structures
>Reporter: Valentin Kulichenko
>Assignee: Anton Kurbanov
>Priority: Major
> Labels: newbie, usability
> Attachments: IgniteAtomicTypesConfigurationTest.java
>
>
> Currently {{AtomicConfiguration}} and {{CollectionConfiguration}} are mapped
> to system caches configuration and consistency is checked like for any other
> cache. This leads to unintuitive errors.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-2096) AtomicConfiguration and CollectionConfiguration should be properly checked for consistency
[
https://issues.apache.org/jira/browse/IGNITE-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Kurbanov updated IGNITE-2096:
---
Attachment: IgniteAtomicTypesConfigurationTest.java
> AtomicConfiguration and CollectionConfiguration should be properly checked
> for consistency
> --
>
> Key: IGNITE-2096
> URL: https://issues.apache.org/jira/browse/IGNITE-2096
> Project: Ignite
> Issue Type: Bug
> Components: data structures
>Reporter: Valentin Kulichenko
>Assignee: Anton Kurbanov
>Priority: Major
> Labels: newbie, usability
> Attachments: IgniteAtomicTypesConfigurationTest.java
>
>
> Currently {{AtomicConfiguration}} and {{CollectionConfiguration}} are mapped
> to system caches configuration and consistency is checked like for any other
> cache. This leads to unintuitive errors.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-6826) Change default DiscoverySpi ipFinder type for examples
[ https://issues.apache.org/jira/browse/IGNITE-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16428231#comment-16428231 ] Anton Kurbanov commented on IGNITE-6826: [~SomeFire], exactly what what already described in comment section. Launching examples using both .exe and from VS with properly configured nodes using Apache.Ignite.exe. Nodes started by Ignite.bat/sh are using different configuration sourced from config/default-config.xml. As you already mentioned there are some exceptions being thrown in this case due to configuration mismatch. Wondering if this should work with default configuration. > Change default DiscoverySpi ipFinder type for examples > -- > > Key: IGNITE-6826 > URL: https://issues.apache.org/jira/browse/IGNITE-6826 > Project: Ignite > Issue Type: Improvement > Components: examples >Affects Versions: 2.3 >Reporter: Alexey Popov >Assignee: Ryabov Dmitrii >Priority: Major > Labels: newbie > Fix For: 2.5 > > > It is better to change multicast ipFinder to static (vm) ipFinder for java > examples, .NET examples and C++ examples. > http://apache-ignite-developers.2346864.n4.nabble.com/ipFinder-configuration-for-Samples-td23818.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-2096) AtomicConfiguration and CollectionConfiguration should be properly checked for consistency
[
https://issues.apache.org/jira/browse/IGNITE-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Kurbanov reassigned IGNITE-2096:
--
Assignee: Anton Kurbanov
> AtomicConfiguration and CollectionConfiguration should be properly checked
> for consistency
> --
>
> Key: IGNITE-2096
> URL: https://issues.apache.org/jira/browse/IGNITE-2096
> Project: Ignite
> Issue Type: Bug
> Components: data structures
>Reporter: Valentin Kulichenko
>Assignee: Anton Kurbanov
>Priority: Major
> Labels: newbie, usability
>
> Currently {{AtomicConfiguration}} and {{CollectionConfiguration}} are mapped
> to system caches configuration and consistency is checked like for any other
> cache. This leads to unintuitive errors.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-6826) Change default DiscoverySpi ipFinder type for examples
[ https://issues.apache.org/jira/browse/IGNITE-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426694#comment-16426694 ] Anton Kurbanov commented on IGNITE-6826: [~SomeFire], can you clarify what needs to be done in order to resolve this issue? I've changed ipFinder from multicast to static/vm and examples are working fine. > Change default DiscoverySpi ipFinder type for examples > -- > > Key: IGNITE-6826 > URL: https://issues.apache.org/jira/browse/IGNITE-6826 > Project: Ignite > Issue Type: Improvement > Components: examples >Affects Versions: 2.3 >Reporter: Alexey Popov >Assignee: Ryabov Dmitrii >Priority: Major > Labels: newbie > Fix For: 2.5 > > > It is better to change multicast ipFinder to static (vm) ipFinder for java > examples, .NET examples and C++ examples. > http://apache-ignite-developers.2346864.n4.nabble.com/ipFinder-configuration-for-Samples-td23818.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-8110) GridCacheWriteBehindStore.Flusher thread uses the wrong transformation from milliseconds to nanoseconds.
[
https://issues.apache.org/jira/browse/IGNITE-8110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Kurbanov reassigned IGNITE-8110:
--
Assignee: Anton Kurbanov
> GridCacheWriteBehindStore.Flusher thread uses the wrong transformation from
> milliseconds to nanoseconds.
>
>
> Key: IGNITE-8110
> URL: https://issues.apache.org/jira/browse/IGNITE-8110
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.4
>Reporter: Vyacheslav Koptilin
>Assignee: Anton Kurbanov
>Priority: Minor
>
> The initial value of a cache flushing frequency is defined as follows:
> {code}
> /** Cache flushing frequence in nanos. */
> protected long cacheFlushFreqNanos = cacheFlushFreq * 1000;
> {code}
> where is {{cacheFlushFreq}} is equal to
> {code}
> /** Default flush frequency for write-behind cache store in milliseconds.
> */
> public static final long DFLT_WRITE_BEHIND_FLUSH_FREQUENCY = 5000;
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
