[jira] [Commented] (IGNITE-12471) .NET Thin Client: WithExpiryPolicy crashes client connection on old servers
[
https://issues.apache.org/jira/browse/IGNITE-12471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17023386#comment-17023386
]
Ignite TC Bot commented on IGNITE-12471:
{panel:title=Branch: [pull/7212/head] Base: [master] : Possible Blockers
(5)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET (Long Running){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=4896179]]
* exe: CacheAbstractTransactionalTest.TestTxDeadlockDetection - Test has low
fail rate in base branch 0,0% and is not flaky
{color:#d04437}Queries 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=4896181]]
* IgniteBinaryCacheQueryTestSuite:
IndexingCachePartitionLossPolicySelfTest.testReadWriteSafeWithPersistence[ATOMIC]
- Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Basic 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=4896093]]
* IgniteComputeBasicConfigVariationsFullApiTestSuite:
IgniteComputeConfigVariationsFullApiTest_26.testDeployExecuteByName - Test has
low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Thin client: PHP{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=4896140]]
{color:#d04437}MVCC Cache 7{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=4896195]]
* IgniteCacheMvccTestSuite7:
GridTransactionsSystemUserTimeMetricsTest.testUserDelayOnRolledBackTx - Test
has low fail rate in base branch 0,0% and is not flaky
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4896205buildTypeId=IgniteTests24Java8_RunAll]
> .NET Thin Client: WithExpiryPolicy crashes client connection on old servers
> ---
>
> Key: IGNITE-12471
> URL: https://issues.apache.org/jira/browse/IGNITE-12471
> Project: Ignite
> Issue Type: Task
> Components: platforms
>Affects Versions: 2.8
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET
> Fix For: 2.8
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> ICacheClient.WithExpiryPolicy does not check protocol version and causes
> exception and disconnect:
> * Run Ignite 2.7.6 server node
> * Connect thin client from master branch
> * {{cache.WithExpiryPolicy(..).Put(1, 2)}}:
> {code}
> Unhandled exception. System.Net.Sockets.SocketException (10053): An
> established connection was aborted by the software in your host machine.
>at Apache.Ignite.Core.Impl.Client.ClientSocket.ReceiveBytes(Int32 size)
>at Apache.Ignite.Core.Impl.Client.ClientSocket.ReceiveMessage()
>at Apache.Ignite.Core.Impl.Client.ClientSocket.SendRequest(RequestMessage&
> reqMsg)
>at Apache.Ignite.Core.Impl.Client.ClientSocket.DoOutInOp[T](ClientOp opId,
> Action`1 writeAction, Func`2 readFunc, Func`3 errorFunc)
>at
> Apache.Ignite.Core.Impl.Client.ClientFailoverSocket.DoOutInOpAffinity[T,TKey](ClientOp
> opId, Action`1 writeAction, Func`2 readFunc, Int32 cacheId, TKey key, Func`3
> errorFunc)
>at
> Apache.Ignite.Core.Impl.Client.Cache.CacheClient`2.DoOutInOpAffinity[T](ClientOp
> opId, TK key, TV val, Func`2 readFunc)
>at
> Apache.Ignite.Core.Impl.Client.Cache.CacheClient`2.DoOutOpAffinity(ClientOp
> opId, TK key, TV val)
>at Apache.Ignite.Core.Impl.Client.Cache.CacheClient`2.Put(TK key, TV val)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-11906) Scalar examples fails on TC
[ https://issues.apache.org/jira/browse/IGNITE-11906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17023177#comment-17023177 ] Ilya Kasnacheev commented on IGNITE-11906: -- [~akuznetsov] please review scala tests fix > Scalar examples fails on TC > --- > > Key: IGNITE-11906 > URL: https://issues.apache.org/jira/browse/IGNITE-11906 > Project: Ignite > Issue Type: Bug > Components: examples >Reporter: Nikolay Izhikov >Assignee: Ilya Kasnacheev >Priority: Major > Labels: scala > Time Spent: 10m > Remaining Estimate: 0h > > Scalar examples tests fails in master. > https://ci.ignite.apache.org/viewLog.html?buildId=4085544=buildResultsDiv=IgniteTests24Java8_ScalaExamples -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-9184) Cluster hangs during concurrent node client and server nodes restart
[ https://issues.apache.org/jira/browse/IGNITE-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17023166#comment-17023166 ] Dmitriy Sorokin commented on IGNITE-9184: - [~mcherkasov] It would be great if you can attach your initial reproducer, if possible. But while, at the moment I decided to close this issue as non-reproducable. > Cluster hangs during concurrent node client and server nodes restart > > > Key: IGNITE-9184 > URL: https://issues.apache.org/jira/browse/IGNITE-9184 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 2.6 >Reporter: Mikhail Cherkasov >Assignee: Dmitriy Sorokin >Priority: Blocker > Fix For: 2.8 > > Attachments: StressTest2.java, StressTest3.java, logs, stacktrace > > > Please check the attached test case and stack trace. > I can see: "Failed to wait for initial partition map exchange" message. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-9184) Cluster hangs during concurrent node client and server nodes restart
[ https://issues.apache.org/jira/browse/IGNITE-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Sorokin resolved IGNITE-9184. - Resolution: Cannot Reproduce > Cluster hangs during concurrent node client and server nodes restart > > > Key: IGNITE-9184 > URL: https://issues.apache.org/jira/browse/IGNITE-9184 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 2.6 >Reporter: Mikhail Cherkasov >Assignee: Dmitriy Sorokin >Priority: Blocker > Fix For: 2.8 > > Attachments: StressTest2.java, StressTest3.java, logs, stacktrace > > > Please check the attached test case and stack trace. > I can see: "Failed to wait for initial partition map exchange" message. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-9184) Cluster hangs during concurrent node client and server nodes restart
[
https://issues.apache.org/jira/browse/IGNITE-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17023160#comment-17023160
]
Dmitriy Sorokin commented on IGNITE-9184:
-
[~mmuzaf]
I wrote the new version of reproducer (see the StressTest3.java attachment)
which provides true concurrent nodes restart, but subject problem with cluster
hanging never met, neither on version 2.6 nor current master branch. However,
short-time hangings with logs similar to ones published at comment above still
appearing at the current master:
{noformat}
[2019-12-06 13:10:21,381][INFO
][exchange-worker-#1448818%hang.StressTest325879%][time] Started exchange init
[topVer=AffinityTopologyVersion [topVer=51762, minorTopVer=0], crd=false,
evt=NODE_JOINED, evtNode=92f30d54-e3ec-4292-84fa-e1f399325881, customEvt=null,
allowMerge=true]
[2019-12-06 13:10:21,381][INFO
][exchange-worker-#1448818%hang.StressTest325879%][GridDhtPartitionsExchangeFuture]
Finished waiting for partition release future [topVer=AffinityTopologyVersion
[topVer=51762, minorTopVer=0], waitTime=0ms, futInfo=NA, mode=DISTRIBUTED]
[2019-12-06 13:10:21,381][INFO
][exchange-worker-#1448936%hang.StressTest325881%][time] Started exchange init
[topVer=AffinityTopologyVersion [topVer=51762, minorTopVer=0], crd=false,
evt=NODE_JOINED, evtNode=92f30d54-e3ec-4292-84fa-e1f399325881, customEvt=null,
allowMerge=true]
[2019-12-06 13:10:21,382][INFO
][exchange-worker-#1448936%hang.StressTest325881%][IgniteCacheDatabaseSharedManager]
Configured data regions started successfully [total=3]
[2019-12-06 13:10:21,382][INFO
][exchange-worker-#1448936%hang.StressTest325881%][msg] Components activation
performed in 1 ms.
[2019-12-06 13:10:21,383][INFO
][sys-#1448940%hang.StressTest325881%][GridCacheProcessor] Started cache
[name=ignite-sys-cache, id=-2100569601, dataRegionName=sysMemPlc,
mode=REPLICATED, atomicity=TRANSACTIONAL, backups=2147483647, mvcc=false]
[2019-12-06 13:10:21,383][INFO
][exchange-worker-#1448936%hang.StressTest325881%][GridCacheProcessor] Started
cache [name=default, id=1544803905, dataRegionName=default, mode=PARTITIONED,
atomicity=ATOMIC, backups=1, mvcc=false]
[2019-12-06 13:10:21,383][INFO
][exchange-worker-#1448936%hang.StressTest325881%][GridCacheProcessor] Starting
caches on local join performed in 10 ms.
[2019-12-06 13:10:21,381][WARN ][Thread-9][StressTest325881] Nodes started on
local machine require more than 80% of physical RAM what can lead to
significant slowdown due to swapping (please decrease JVM heap size, data
region size or checkpoint buffer size) [required=35144MB, available=16280MB]
[2019-12-06 13:10:21,384][INFO
][exchange-worker-#1448936%hang.StressTest325881%][GridDhtPartitionsExchangeFuture]
Skipped waiting for partitions release future (local node is joining)
[topVer=AffinityTopologyVersion [topVer=51762, minorTopVer=0]]
[2019-12-06 13:10:21,385][INFO
][grid-nio-worker-tcp-comm-2-#1448576%hang.StressTest325875%][TcpCommunicationSpi]
Accepted incoming communication connection [locAddr=/127.0.0.1:45014,
rmtAddr=/127.0.0.1:55957]
[2019-12-06 13:10:21,386][INFO
][grid-nio-worker-tcp-comm-0-#1448902%hang.StressTest325881%][TcpCommunicationSpi]
Established outgoing communication connection [locAddr=/127.0.0.1:55957,
rmtAddr=/127.0.0.1:45014]
[2019-12-06 13:10:21,386][INFO
][exchange-worker-#1448936%hang.StressTest325881%][time] Finished exchange init
[topVer=AffinityTopologyVersion [topVer=51762, minorTopVer=0], crd=false]
[2019-12-06 13:10:21,413][INFO
][grid-nio-worker-tcp-comm-2-#1448910%hang.StressTest325882%][TcpCommunicationSpi]
Accepted incoming communication connection [locAddr=/127.0.0.1:45013,
rmtAddr=/127.0.0.1:55958]
[2019-12-06 13:10:21,463][INFO
][grid-nio-worker-tcp-comm-3-#1448911%hang.StressTest325882%][TcpCommunicationSpi]
Accepted incoming communication connection [locAddr=/127.0.0.1:45013,
rmtAddr=/127.0.0.1:55959]
[2019-12-06 13:10:21,514][INFO
][grid-nio-worker-tcp-comm-0-#1448908%hang.StressTest325882%][TcpCommunicationSpi]
Accepted incoming communication connection [locAddr=/127.0.0.1:45013,
rmtAddr=/127.0.0.1:55960]
[2019-12-06 13:10:21,565][INFO
][grid-nio-worker-tcp-comm-1-#1448909%hang.StressTest325882%][TcpCommunicationSpi]
Accepted incoming communication connection [locAddr=/127.0.0.1:45013,
rmtAddr=/127.0.0.1:55961]
[2019-12-06 13:10:21,569][INFO
][sys-#1448612%hang.StressTest325875%][GridCachePartitionExchangeManager]
Ignore single message without exchange id (there is exchange in progress)
[nodeId=4422f968-e654-4376-bef6-262125325879]
[2019-12-06 13:10:21,617][INFO
][grid-nio-worker-tcp-comm-2-#1448910%hang.StressTest325882%][TcpCommunicationSpi]
Accepted incoming communication connection [locAddr=/127.0.0.1:45013,
rmtAddr=/127.0.0.1:55962]
[2019-12-06 13:10:21,667][INFO
][grid-nio-worker-tcp-comm-3-#1448911%hang.StressTest325882%][TcpCommunicationSpi]
Accepted incoming
[jira] [Commented] (IGNITE-12578) CAS cache operations (replace(K, V, V), remove(K, V)) don't work with array data type
[
https://issues.apache.org/jira/browse/IGNITE-12578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17023159#comment-17023159
]
Aleksey Plekhanov commented on IGNITE-12578:
[~amashenkov], I'm not sure. {{F.eq}} is widely used. I think it's safer to fix
{{CacheEntryPredicateContainsValue}}.
> CAS cache operations (replace(K, V, V), remove(K, V)) don't work with array
> data type
> -
>
> Key: IGNITE-12578
> URL: https://issues.apache.org/jira/browse/IGNITE-12578
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Reporter: Aleksey Plekhanov
>Priority: Major
>
> Values are compared using {{CacheEntryPredicateContainsValue}} predicate,
> this predicate call {{F.eq(thisVal, cacheVal)}} to compare, which gives false
> for two instances of arrays with the same content.
> Reproducer:
> {code:java}
> IgniteCache cache =
> startGrid().getOrCreateCache(DEFAULT_CACHE_NAME);
> Object val = new byte[] {1};
> cache.put(1, val);
> assertTrue(cache.replace(1, val, val));
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-9184) Cluster hangs during concurrent node client and server nodes restart
[ https://issues.apache.org/jira/browse/IGNITE-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Sorokin updated IGNITE-9184: Attachment: StressTest3.java > Cluster hangs during concurrent node client and server nodes restart > > > Key: IGNITE-9184 > URL: https://issues.apache.org/jira/browse/IGNITE-9184 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 2.6 >Reporter: Mikhail Cherkasov >Assignee: Dmitriy Sorokin >Priority: Blocker > Fix For: 2.8 > > Attachments: StressTest2.java, StressTest3.java, logs, stacktrace > > > Please check the attached test case and stack trace. > I can see: "Failed to wait for initial partition map exchange" message. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12522) Extend test coverage [IGNITE-12104] Check deployment from cache before to load it from local or version storage
[ https://issues.apache.org/jira/browse/IGNITE-12522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17023053#comment-17023053 ] Anton Kalashnikov commented on IGNITE-12522: [~v.pyatkov] now everything looks good to me. It can be merged. > Extend test coverage [IGNITE-12104] Check deployment from cache before to > load it from local or version storage > --- > > Key: IGNITE-12522 > URL: https://issues.apache.org/jira/browse/IGNITE-12522 > Project: Ignite > Issue Type: Improvement >Reporter: Vladislav Pyatkov >Assignee: Vladislav Pyatkov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12568) MessageFactory implementations refactoring
[
https://issues.apache.org/jira/browse/IGNITE-12568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17023037#comment-17023037
]
Alexey Goncharuk commented on IGNITE-12568:
---
Agree, the second approach looks clean.
> MessageFactory implementations refactoring
> --
>
> Key: IGNITE-12568
> URL: https://issues.apache.org/jira/browse/IGNITE-12568
> Project: Ignite
> Issue Type: Improvement
>Reporter: Andrey N. Gura
>Assignee: Andrey N. Gura
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently existing {{MessageFactory}} implementations (at least
> {{GridIoMessageFactory}} and {{GridH2ValueMessageFactory}}) have serious
> problem: it is possible to register several messages with the same direct
> type. It could lead to the cluster freeze due to unexpected unmarshaling
> error.
> *Solution:*
> Each message should be registered and during registration we can check that
> there is no registered message with the same type. Otherwise we should not
> start node and print error message.
> *Proposed implementation:*
> Instead of {{switch-case}} block new array of size 2^16 should be created.
> Each array cell should contain message default constructor reference or
> lambda which is responsible for message instance creation. So during message
> unmarshaling system just lookup ctor-ref or lambda from array by index and
> invoke it in order to create proper message instance.
> All message factory extensions and custom message should be registered at the
> same array before communication SPI will be started.
> If we try to register message with direct type for which already exists
> registered message then node start process must be terminated (directly, with
> out any failure handlers).
> If we get message with unknown direct type (there is now registered message
> for this direct type) then failure handler be invoked.
> It could affect perfromance so we should run microbenchmark for this change.
> Additional benefit of this change is improving code readability. At present
> we have the following code:
> {code:java}
> @Override public Message create(short type) {
> Message msg = null;
> switch (type) {
> case -61:
> msg = new IgniteDiagnosticMessage();
> break;
> case -53:
> msg = new SchemaOperationStatusMessage();
> break;
> // etc.
> }
> {code}
> After refactoring it will looks like:
> {code:java}
> private Supplier[] msgCtrs;
> public GridIoMessageFactory(MessageFactory[] ext) {
> this.ext = ext;
>registerMessage(-61, IgniteDiagnosticMessage::new)
>registerMessage(-53, SchemaOperationStatusMessage::new)
> }
> @Override public Message create(short type) {
> return msgCtros[type].get();
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12578) CAS cache operations (replace(K, V, V), remove(K, V)) don't work with array data type
[
https://issues.apache.org/jira/browse/IGNITE-12578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17022989#comment-17022989
]
Andrey Mashenkov commented on IGNITE-12578:
---
F.eq use equals method for comparing arrays.
I believe F.eq should compare arrays using Arrays.equals() instead.
> CAS cache operations (replace(K, V, V), remove(K, V)) don't work with array
> data type
> -
>
> Key: IGNITE-12578
> URL: https://issues.apache.org/jira/browse/IGNITE-12578
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Reporter: Aleksey Plekhanov
>Priority: Major
>
> Values are compared using {{CacheEntryPredicateContainsValue}} predicate,
> this predicate call {{F.eq(thisVal, cacheVal)}} to compare, which gives false
> for two instances of arrays with the same content.
> Reproducer:
> {code:java}
> IgniteCache cache =
> startGrid().getOrCreateCache(DEFAULT_CACHE_NAME);
> Object val = new byte[] {1};
> cache.put(1, val);
> assertTrue(cache.replace(1, val, val));
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12291) Create controllable paged query requests / responses for TextQuery similar to current SQL result processing
[ https://issues.apache.org/jira/browse/IGNITE-12291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17022948#comment-17022948 ] Ivan Pavlukhin commented on IGNITE-12291: - [~Yuriy_Shuliha], what problem should this ticket primarily solve? Let me describe my understanding on example. Correct me if I am getting something wrong. An example: _A query with a limit 1000. With current implementation we must receive 1000 entries from every node before finishing query. With NextPageRequest (e.g. page size is 100) we will be able to stop processing as long as we received 1000 entries which fit our needs._ > Create controllable paged query requests / responses for TextQuery similar to > current SQL result processing > --- > > Key: IGNITE-12291 > URL: https://issues.apache.org/jira/browse/IGNITE-12291 > Project: Ignite > Issue Type: Improvement >Reporter: Yuriy Shuliha >Assignee: Yuriy Shuliha >Priority: Major > > For now query initiator node sends 1 _GridCacheQueryRequest_ and can get > multiple _GridCacheQueryResponse_-s per remote. > TextQuery processing finishes when all remotes send _GridCacheQueryResponse_ > with 'finished' flag. > _TextQuery_ processing should be reworked like it was done for SQL queries. > Ignite has _GridQueryNextPageRequest \ Response_ classes for SQL result > processing. > Similar processing should be implemented for _TextQueries_: > *GridTextQueryNextPageRequest* > *GridTextQueryNextPageResponse* > Proper _TextQuery_ response processing should be implemented in > _GridCacheQueryFutureAdapter._ > This will allow us to add correct sorting and apply limit correctly on reduce. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12562) FreeListCachingTest.testPageListCacheLimit failing in Disk Page Compressions suite
[ https://issues.apache.org/jira/browse/IGNITE-12562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Plekhanov updated IGNITE-12562: --- Affects Version/s: 2.9 > FreeListCachingTest.testPageListCacheLimit failing in Disk Page Compressions > suite > -- > > Key: IGNITE-12562 > URL: https://issues.apache.org/jira/browse/IGNITE-12562 > Project: Ignite > Issue Type: Bug > Components: persistence >Affects Versions: 2.9 >Reporter: Aleksey Plekhanov >Assignee: Aleksey Plekhanov >Priority: Major > Fix For: 2.9 > > Time Spent: 20m > Remaining Estimate: 0h > > Test failing with IgniteOutOfMemory exception because Disk Page Compressions > changes default page size to 8192, we need at least 2*1024 (2 caches, 1024 > partitions) pages to store freelist metadata and there is no such amount of > not dirty pages after checkpoint is triggered by "too many dirty page" reason. > Explicitly defined data region max size should take into account page size to > avoid such errors. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12530) Pages list caching can cause IgniteOOME when checkpoint is triggered by "too many dirty pages" reason
[
https://issues.apache.org/jira/browse/IGNITE-12530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Plekhanov updated IGNITE-12530:
---
Fix Version/s: 2.8
> Pages list caching can cause IgniteOOME when checkpoint is triggered by "too
> many dirty pages" reason
> -
>
> Key: IGNITE-12530
> URL: https://issues.apache.org/jira/browse/IGNITE-12530
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Affects Versions: 2.8
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Critical
> Fix For: 2.8, 2.9
>
> Attachments: screenshot-1.png, screenshot-2.png
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> When a checkpoint is triggered, we need some amount of page memory to store
> pages list on-heap cache.
> If data region is too small, a checkpoint is triggered by "too many dirty
> pages" reason and pages list cache is rather big, we can get
> IgniteOutOfMemoryException.
> Reproducer:
> {code:java}
> @Override protected IgniteConfiguration getConfiguration(String name) throws
> Exception {
> IgniteConfiguration cfg = super.getConfiguration(name);
> cfg.setDataStorageConfiguration(new DataStorageConfiguration()
> .setDefaultDataRegionConfiguration(new DataRegionConfiguration()
> .setPersistenceEnabled(true)
> .setMaxSize(50 * 1024 * 1024)
> ));
> return cfg;
> }
> @Test
> public void testUpdatesNotFittingIntoMemoryRegion() throws Exception {
> IgniteEx ignite = startGrid(0);
> ignite.cluster().active(true);
> ignite.getOrCreateCache(DEFAULT_CACHE_NAME);
> try (IgniteDataStreamer streamer =
> ignite.dataStreamer(DEFAULT_CACHE_NAME)) {
> for (int i = 0; i < 100_000; i++)
> streamer.addData(i, new byte[i % 2048]);
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12530) Pages list caching can cause IgniteOOME when checkpoint is triggered by "too many dirty pages" reason
[
https://issues.apache.org/jira/browse/IGNITE-12530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17022933#comment-17022933
]
Aleksey Plekhanov commented on IGNITE-12530:
Cherry-picked to 2.8
> Pages list caching can cause IgniteOOME when checkpoint is triggered by "too
> many dirty pages" reason
> -
>
> Key: IGNITE-12530
> URL: https://issues.apache.org/jira/browse/IGNITE-12530
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Affects Versions: 2.8
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Critical
> Fix For: 2.9
>
> Attachments: screenshot-1.png, screenshot-2.png
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> When a checkpoint is triggered, we need some amount of page memory to store
> pages list on-heap cache.
> If data region is too small, a checkpoint is triggered by "too many dirty
> pages" reason and pages list cache is rather big, we can get
> IgniteOutOfMemoryException.
> Reproducer:
> {code:java}
> @Override protected IgniteConfiguration getConfiguration(String name) throws
> Exception {
> IgniteConfiguration cfg = super.getConfiguration(name);
> cfg.setDataStorageConfiguration(new DataStorageConfiguration()
> .setDefaultDataRegionConfiguration(new DataRegionConfiguration()
> .setPersistenceEnabled(true)
> .setMaxSize(50 * 1024 * 1024)
> ));
> return cfg;
> }
> @Test
> public void testUpdatesNotFittingIntoMemoryRegion() throws Exception {
> IgniteEx ignite = startGrid(0);
> ignite.cluster().active(true);
> ignite.getOrCreateCache(DEFAULT_CACHE_NAME);
> try (IgniteDataStreamer streamer =
> ignite.dataStreamer(DEFAULT_CACHE_NAME)) {
> for (int i = 0; i < 100_000; i++)
> streamer.addData(i, new byte[i % 2048]);
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12580) NPE in GridMetricManager
[
https://issues.apache.org/jira/browse/IGNITE-12580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Scherbakov updated IGNITE-12580:
---
Priority: Critical (was: Major)
> NPE in GridMetricManager
>
>
> Key: IGNITE-12580
> URL: https://issues.apache.org/jira/browse/IGNITE-12580
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexey Scherbakov
>Priority: Critical
> Fix For: 2.9
>
>
> NPE is thrown during cache recovery:
> {noformat}
> class org.apache.ignite.IgniteCheckedException: null
> at
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7534)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.resolve(GridFutureAdapter.java:260)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:234)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:160)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:152)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.onKernalStart(GridCachePartitionExchangeManager.java:816)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStart(GridCacheProcessor.java:675)
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1375)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2038)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1703)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1117)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:615)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:1017)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:958)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:946)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:895)
> at
> org.apache.ignite.internal.processors.cache.persistence.LocalWalModeChangeDuringRebalancingSelfTest.doTestSimple(LocalWalModeChangeDuringRebalancingSelfTest.java:263)
> at
> org.apache.ignite.internal.processors.cache.persistence.LocalWalModeChangeDuringRebalancingSelfTest.testWalDisabledDuringRebalancing(LocalWalModeChangeDuringRebalancingSelfTest.java:234)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2124)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.metric.GridMetricManager.remove(GridMetricManager.java:396)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.stop(GridCacheAdapter.java:669)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.stopCache(GridCacheProcessor.java:1024)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.stopCache(GridCacheProcessor.java:998)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.stopCaches(GridCacheProcessor.java:754)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor$CacheRecoveryLifecycle.onBaselineChange(GridCacheProcessor.java:5460)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.initCachesOnLocalJoin(GridDhtPartitionsExchangeFuture.java:982)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:849)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:3236)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:3085)
> at
[jira] [Updated] (IGNITE-12577) High persistence load can trigger erroneous assert: "Page was pin when we resolve abs pointer, it can not be evicted".
[ https://issues.apache.org/jira/browse/IGNITE-12577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-12577: - Priority: Critical (was: Blocker) > High persistence load can trigger erroneous assert: "Page was pin when we > resolve abs pointer, it can not be evicted". > -- > > Key: IGNITE-12577 > URL: https://issues.apache.org/jira/browse/IGNITE-12577 > Project: Ignite > Issue Type: Bug > Components: data structures >Affects Versions: 2.7.6 >Reporter: Stanilovsky Evgeny >Assignee: Stanilovsky Evgeny >Priority: Critical > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > For now It seems erroneous assertion in checkpointer code : "Page was pin > when we resolve abs pointer, it can not be evicted", need to be removed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12577) High persistence load can trigger erroneous assert: "Page was pin when we resolve abs pointer, it can not be evicted".
[ https://issues.apache.org/jira/browse/IGNITE-12577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17022914#comment-17022914 ] Maxim Muzafarov commented on IGNITE-12577: -- [~zstan] I think it's not a good approach by simply removing assertions without any strong reasons (at least some additional tests). WDYT? > High persistence load can trigger erroneous assert: "Page was pin when we > resolve abs pointer, it can not be evicted". > -- > > Key: IGNITE-12577 > URL: https://issues.apache.org/jira/browse/IGNITE-12577 > Project: Ignite > Issue Type: Bug > Components: data structures >Affects Versions: 2.7.6 >Reporter: Stanilovsky Evgeny >Assignee: Stanilovsky Evgeny >Priority: Blocker > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > For now It seems erroneous assertion in checkpointer code : "Page was pin > when we resolve abs pointer, it can not be evicted", need to be removed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12577) High persistence load can trigger erroneous assert: "Page was pin when we resolve abs pointer, it can not be evicted".
[ https://issues.apache.org/jira/browse/IGNITE-12577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-12577: - Priority: Blocker (was: Major) > High persistence load can trigger erroneous assert: "Page was pin when we > resolve abs pointer, it can not be evicted". > -- > > Key: IGNITE-12577 > URL: https://issues.apache.org/jira/browse/IGNITE-12577 > Project: Ignite > Issue Type: Bug > Components: data structures >Affects Versions: 2.7.6 >Reporter: Stanilovsky Evgeny >Assignee: Stanilovsky Evgeny >Priority: Blocker > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > For now It seems erroneous assertion in checkpointer code : "Page was pin > when we resolve abs pointer, it can not be evicted", need to be removed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12580) NPE in GridMetricManager
Alexey Scherbakov created IGNITE-12580:
--
Summary: NPE in GridMetricManager
Key: IGNITE-12580
URL: https://issues.apache.org/jira/browse/IGNITE-12580
Project: Ignite
Issue Type: Bug
Reporter: Alexey Scherbakov
Fix For: 2.9
NPE is thrown during cache recovery:
{noformat}
class org.apache.ignite.IgniteCheckedException: null
at
org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7534)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.resolve(GridFutureAdapter.java:260)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:234)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:160)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:152)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.onKernalStart(GridCachePartitionExchangeManager.java:816)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStart(GridCacheProcessor.java:675)
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1375)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2038)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1703)
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1117)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:615)
at
org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:1017)
at
org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:958)
at
org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:946)
at
org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:895)
at
org.apache.ignite.internal.processors.cache.persistence.LocalWalModeChangeDuringRebalancingSelfTest.doTestSimple(LocalWalModeChangeDuringRebalancingSelfTest.java:263)
at
org.apache.ignite.internal.processors.cache.persistence.LocalWalModeChangeDuringRebalancingSelfTest.testWalDisabledDuringRebalancing(LocalWalModeChangeDuringRebalancingSelfTest.java:234)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2124)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.NullPointerException
at
org.apache.ignite.internal.processors.metric.GridMetricManager.remove(GridMetricManager.java:396)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.stop(GridCacheAdapter.java:669)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.stopCache(GridCacheProcessor.java:1024)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.stopCache(GridCacheProcessor.java:998)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.stopCaches(GridCacheProcessor.java:754)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor$CacheRecoveryLifecycle.onBaselineChange(GridCacheProcessor.java:5460)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.initCachesOnLocalJoin(GridDhtPartitionsExchangeFuture.java:982)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:849)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:3236)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:3085)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
... 1 more
{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12570) What is the root cause of IgniteCheckedException: Invalid handshake message
[
https://issues.apache.org/jira/browse/IGNITE-12570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17022907#comment-17022907
]
Ivan Pavlukhin commented on IGNITE-12570:
-
[~sen.shubhendra], some clarifying questions:
# How often exceptions arrive to log? Does it cause any problems for your
deployment?
# In what network is your server located?
As Igor wrote it might be caused by some software which is not an Ignite client
sending data to thin client port. For example, some network scanning software
can cause it.
Also, if you do not need thin clients and ODBC/JDBC in your deployment, you can
disable client connector in IgniteConfiguration. After that you will not see
mentioned exceptions in logs.
{code}
IgniteConfiguration cfg = new
IgniteConfiguration().setClientConnectorConfiguration(null);
{code}
> What is the root cause of IgniteCheckedException: Invalid handshake message
> ---
>
> Key: IGNITE-12570
> URL: https://issues.apache.org/jira/browse/IGNITE-12570
> Project: Ignite
> Issue Type: Bug
> Components: examples
>Affects Versions: 2.7.5
>Reporter: shubhendra sen
>Priority: Major
>
> Two environments are there. On one environment ignite servers are working
> properly. but on the other environment i am getting an exception.
>
> **
> Closing NIO session because of unhandled exception.
> org.apache.ignite.IgniteCheckedException: Invalid handshake message
> at
> org.apache.ignite.internal.processors.odbc.ClientListenerNioServerBuffer.read(ClientListenerNioServerBuffer.java:114)
> ~[ignite-core-8.7.5.jar!/:8.7.5]
> at
> org.apache.ignite.internal.processors.odbc.ClientListenerBufferedParser.decode(ClientListenerBufferedParser.java:59)
> ~[ignite-core-8.7.5.jar!/:8.7.5]
> at
> org.apache.ignite.internal.processors.odbc.ClientListenerBufferedParser.decode(ClientListenerBufferedParser.java:39)
> ~[ignite-core-8.7.5.jar!/:8.7.5]
> at
> org.apache.ignite.internal.util.nio.GridNioCodecFilter.onMessageReceived(GridNioCodecFilter.java:113)
> ~[ignite-core-8.7.5.jar!/:8.7.5]
> at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:108)
> ~[ignite-core-8.7.5.jar!/:8.7.5]
> at
> org.apache.ignite.internal.util.nio.GridNioServer$HeadFilter.onMessageReceived(GridNioServer.java:3575)
> ~[ignite-core-8.7.5.jar!/:8.7.5]
> at
> org.apache.ignite.internal.util.nio.GridNioFilterChain.onMessageReceived(GridNioFilterChain.java:174)
> ~[ignite-core-8.7.5.jar!/:8.7.5]
> at
> org.apache.ignite.internal.util.nio.GridNioServer$ByteBufferNioClientWorker.processRead(GridNioServer.java:1150)
> ~[ignite-core-8.7.5.jar!/:8.7.5]
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNioServer.java:2411)
> ~[ignite-core-8.7.5.jar!/:8.7.5]
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:2178)
> ~[ignite-core-8.7.5.jar!/:8.7.5]
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1819)
> ~[ignite-core-8.7.5.jar!/:8.7.5]
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
> ~[ignite-core-8.7.5.jar!/:8.7.5]
> at java.base/java.lang.Thread.run(Thread.java:834) ~[na:na]
>
> So i have two Questions.
> 1) What could be the possible causes of this exception ?. and
> 2)What re the solutions.
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12579) SQL INSERT operation hangs with security enabled.
[
https://issues.apache.org/jira/browse/IGNITE-12579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
PetrovMikhail updated IGNITE-12579:
---
Description:
SQL INSERT operation hangs in case INSERT KEY belongs to remote node(node that
is different from one to which jdbc connection was established) and security
enabled with the following exception in log:
{code:java}
[2020-01-24
14:59:42,189][ERROR][sys-stripe-4-#48%jdbc.JdbcRemoteKeyInsertTest1%][IgniteTestResources]
Critical system error detected. Will be handled accordingly to configured
handler [hnd=NoOpFailureHandler [super=AbstractFailureHandler
[ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED,
SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext
[type=SYSTEM_WORKER_TERMINATION,
err=java.lang.NullPointerException]][2020-01-24
14:59:42,189][ERROR][sys-stripe-4-#48%jdbc.JdbcRemoteKeyInsertTest1%][IgniteTestResources]
Critical system error detected. Will be handled accordingly to configured
handler [hnd=NoOpFailureHandler [super=AbstractFailureHandler
[ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED,
SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext
[type=SYSTEM_WORKER_TERMINATION,
err=java.lang.NullPointerException]]java.lang.NullPointerException at
org.apache.ignite.internal.processors.security.SecurityUtils.nodeSecurityContext(SecurityUtils.java:132)
at
org.apache.ignite.internal.processors.security.IgniteSecurityProcessor.lambda$withContext$0(IgniteSecurityProcessor.java:106)
at
java.util.concurrent.ConcurrentHashMap.computeIfAbsent(ConcurrentHashMap.java:1660)
at
org.apache.ignite.internal.processors.security.IgniteSecurityProcessor.withContext(IgniteSecurityProcessor.java:105)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1844)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1470)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$5200(GridIoManager.java:229)
at
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1365)
at
org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:565)
at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748)[2020-01-24 14:59:42,198][WARN
][sys-stripe-4-#48%jdbc.JdbcRemoteKeyInsertTest1%][CacheDiagnosticManager] Page
locks dump:
Thread=[name=auth-#83%jdbc.JdbcRemoteKeyInsertTest1%, id=116],
state=WAITINGLocked pages = []Locked pages log:
name=auth-#83%jdbc.JdbcRemoteKeyInsertTest1% time=(1579867182194, 2020-01-24
14:59:42.194)Thread=[name=db-checkpoint-thread-#101%jdbc.JdbcRemoteKeyInsertTest1%,
id=135], state=TIMED_WAITINGLocked pages = []Locked pages log:
name=db-checkpoint-thread-#101%jdbc.JdbcRemoteKeyInsertTest1%
time=(1579867182194, 2020-01-24
14:59:42.194)Thread=[name=dms-writer-thread-#92%jdbc.JdbcRemoteKeyInsertTest1%,
id=126], state=WAITINGLocked pages = []Locked pages log:
name=dms-writer-thread-#92%jdbc.JdbcRemoteKeyInsertTest1% time=(1579867182194,
2020-01-24
14:59:42.194)Thread=[name=exchange-worker-#84%jdbc.JdbcRemoteKeyInsertTest1%,
id=117], state=TIMED_WAITINGLocked pages = []Locked pages log:
name=exchange-worker-#84%jdbc.JdbcRemoteKeyInsertTest1% time=(1579867182194,
2020-01-24 14:59:42.194)Thread=[name=main, id=1], state=TIMED_WAITINGLocked
pages = []Locked pages log: name=main time=(1579867182193, 2020-01-24
14:59:42.193)
[2020-01-24
14:59:42,198][ERROR][sys-stripe-4-#48%jdbc.JdbcRemoteKeyInsertTest1%][G] Failed
to execute runnable.java.lang.NullPointerException at
org.apache.ignite.internal.processors.security.SecurityUtils.nodeSecurityContext(SecurityUtils.java:132)
at
org.apache.ignite.internal.processors.security.IgniteSecurityProcessor.lambda$withContext$0(IgniteSecurityProcessor.java:106)
at
java.util.concurrent.ConcurrentHashMap.computeIfAbsent(ConcurrentHashMap.java:1660)
at
org.apache.ignite.internal.processors.security.IgniteSecurityProcessor.withContext(IgniteSecurityProcessor.java:105)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1844)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1470)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$5200(GridIoManager.java:229)
at
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1365)
at
org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:565)
at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748)
{code}
Reproducer is attached to the ticket.
It seems that a remote node while sql execution receives a security context
with a subject id
[jira] [Updated] (IGNITE-12486) Truncation of archived WAL segments doesn't work
[ https://issues.apache.org/jira/browse/IGNITE-12486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-12486: - Fix Version/s: (was: 2.9) 2.8 > Truncation of archived WAL segments doesn't work > > > Key: IGNITE-12486 > URL: https://issues.apache.org/jira/browse/IGNITE-12486 > Project: Ignite > Issue Type: Bug >Reporter: Ivan Bessonov >Assignee: Ivan Bessonov >Priority: Critical > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > Index calculation is wrong in FileWriteAheadLogManager#rollOver. > It leads to unexpected and faulty WAL segments truncation and data corruption > as a result. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12486) Truncation of archived WAL segments doesn't work
[ https://issues.apache.org/jira/browse/IGNITE-12486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17022901#comment-17022901 ] Maxim Muzafarov commented on IGNITE-12486: -- Cherry-picked to 2.8 > Truncation of archived WAL segments doesn't work > > > Key: IGNITE-12486 > URL: https://issues.apache.org/jira/browse/IGNITE-12486 > Project: Ignite > Issue Type: Bug >Reporter: Ivan Bessonov >Assignee: Ivan Bessonov >Priority: Critical > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > Index calculation is wrong in FileWriteAheadLogManager#rollOver. > It leads to unexpected and faulty WAL segments truncation and data corruption > as a result. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12562) FreeListCachingTest.testPageListCacheLimit failing in Disk Page Compressions suite
[
https://issues.apache.org/jira/browse/IGNITE-12562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17022897#comment-17022897
]
Ignite TC Bot commented on IGNITE-12562:
{panel:title=Branch: [pull/7288/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4956570buildTypeId=IgniteTests24Java8_RunAll]
> FreeListCachingTest.testPageListCacheLimit failing in Disk Page Compressions
> suite
> --
>
> Key: IGNITE-12562
> URL: https://issues.apache.org/jira/browse/IGNITE-12562
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Test failing with IgniteOutOfMemory exception because Disk Page Compressions
> changes default page size to 8192, we need at least 2*1024 (2 caches, 1024
> partitions) pages to store freelist metadata and there is no such amount of
> not dirty pages after checkpoint is triggered by "too many dirty page" reason.
> Explicitly defined data region max size should take into account page size to
> avoid such errors.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12540) Update versions of vulnerable dependencies
[ https://issues.apache.org/jira/browse/IGNITE-12540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17022898#comment-17022898 ] Maxim Muzafarov commented on IGNITE-12540: -- Cherry-picked to 2.8 > Update versions of vulnerable dependencies > -- > > Key: IGNITE-12540 > URL: https://issues.apache.org/jira/browse/IGNITE-12540 > Project: Ignite > Issue Type: Improvement > Components: general, hibernate, rest, spring >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Major > Fix For: 2.8 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Let's bump some crucial dependencies to their latest minor versions and try > to include it in 2.8 also. > spring 4 and 5, spring data, hibernate, jetty, jackson-databind. > Lesser-used packages, notable Zk discovery, are not affected. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12486) Truncation of archived WAL segments doesn't work
[ https://issues.apache.org/jira/browse/IGNITE-12486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-12486: - Priority: Critical (was: Major) > Truncation of archived WAL segments doesn't work > > > Key: IGNITE-12486 > URL: https://issues.apache.org/jira/browse/IGNITE-12486 > Project: Ignite > Issue Type: Bug >Reporter: Ivan Bessonov >Assignee: Ivan Bessonov >Priority: Critical > Fix For: 2.9 > > Time Spent: 10m > Remaining Estimate: 0h > > Index calculation is wrong in FileWriteAheadLogManager#rollOver. > It leads to unexpected and faulty WAL segments truncation and data corruption > as a result. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12540) Update versions of vulnerable dependencies
[ https://issues.apache.org/jira/browse/IGNITE-12540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-12540: - Fix Version/s: (was: 2.9) 2.8 > Update versions of vulnerable dependencies > -- > > Key: IGNITE-12540 > URL: https://issues.apache.org/jira/browse/IGNITE-12540 > Project: Ignite > Issue Type: Improvement > Components: general, hibernate, rest, spring >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Major > Fix For: 2.8 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Let's bump some crucial dependencies to their latest minor versions and try > to include it in 2.8 also. > spring 4 and 5, spring data, hibernate, jetty, jackson-databind. > Lesser-used packages, notable Zk discovery, are not affected. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12540) Update versions of vulnerable dependencies
[ https://issues.apache.org/jira/browse/IGNITE-12540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-12540: - Release Note: Increase minor dependency version for spring-data, spring modules and jetty, jackson, beanutils dependencies. (was: Increase minor dependency version for spring-data, spring modules.) > Update versions of vulnerable dependencies > -- > > Key: IGNITE-12540 > URL: https://issues.apache.org/jira/browse/IGNITE-12540 > Project: Ignite > Issue Type: Improvement > Components: general, hibernate, rest, spring >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Major > Fix For: 2.9 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Let's bump some crucial dependencies to their latest minor versions and try > to include it in 2.8 also. > spring 4 and 5, spring data, hibernate, jetty, jackson-databind. > Lesser-used packages, notable Zk discovery, are not affected. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12540) Update versions of vulnerable dependencies
[ https://issues.apache.org/jira/browse/IGNITE-12540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-12540: - Release Note: Increase minor dependency version for spring-data, spring modules. (was: Update dependencies of essential modules.) > Update versions of vulnerable dependencies > -- > > Key: IGNITE-12540 > URL: https://issues.apache.org/jira/browse/IGNITE-12540 > Project: Ignite > Issue Type: Improvement > Components: general, hibernate, rest, spring >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Major > Fix For: 2.9 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Let's bump some crucial dependencies to their latest minor versions and try > to include it in 2.8 also. > spring 4 and 5, spring data, hibernate, jetty, jackson-databind. > Lesser-used packages, notable Zk discovery, are not affected. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12579) SQL INSERT operation hangs with security enabled.
[
https://issues.apache.org/jira/browse/IGNITE-12579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
PetrovMikhail updated IGNITE-12579:
---
Description:
SQL INSERT operation hangs in case INSERT KEY belongs to remote node(node that
is different from one to which jdbc connection was established) and security
enabled with the following exception in log:
{code:java}
[2020-01-24
14:59:42,189][ERROR][sys-stripe-4-#48%jdbc.JdbcRemoteKeyInsertTest1%][IgniteTestResources]
Critical system error detected. Will be handled accordingly to configured
handler [hnd=NoOpFailureHandler [super=AbstractFailureHandler
[ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED,
SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext
[type=SYSTEM_WORKER_TERMINATION,
err=java.lang.NullPointerException]][2020-01-24
14:59:42,189][ERROR][sys-stripe-4-#48%jdbc.JdbcRemoteKeyInsertTest1%][IgniteTestResources]
Critical system error detected. Will be handled accordingly to configured
handler [hnd=NoOpFailureHandler [super=AbstractFailureHandler
[ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED,
SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext
[type=SYSTEM_WORKER_TERMINATION,
err=java.lang.NullPointerException]]java.lang.NullPointerException at
org.apache.ignite.internal.processors.security.SecurityUtils.nodeSecurityContext(SecurityUtils.java:132)
at
org.apache.ignite.internal.processors.security.IgniteSecurityProcessor.lambda$withContext$0(IgniteSecurityProcessor.java:106)
at
java.util.concurrent.ConcurrentHashMap.computeIfAbsent(ConcurrentHashMap.java:1660)
at
org.apache.ignite.internal.processors.security.IgniteSecurityProcessor.withContext(IgniteSecurityProcessor.java:105)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1844)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1470)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$5200(GridIoManager.java:229)
at
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1365)
at
org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:565)
at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748)[2020-01-24 14:59:42,198][WARN
][sys-stripe-4-#48%jdbc.JdbcRemoteKeyInsertTest1%][CacheDiagnosticManager] Page
locks dump:
Thread=[name=auth-#83%jdbc.JdbcRemoteKeyInsertTest1%, id=116],
state=WAITINGLocked pages = []Locked pages log:
name=auth-#83%jdbc.JdbcRemoteKeyInsertTest1% time=(1579867182194, 2020-01-24
14:59:42.194)Thread=[name=db-checkpoint-thread-#101%jdbc.JdbcRemoteKeyInsertTest1%,
id=135], state=TIMED_WAITINGLocked pages = []Locked pages log:
name=db-checkpoint-thread-#101%jdbc.JdbcRemoteKeyInsertTest1%
time=(1579867182194, 2020-01-24
14:59:42.194)Thread=[name=dms-writer-thread-#92%jdbc.JdbcRemoteKeyInsertTest1%,
id=126], state=WAITINGLocked pages = []Locked pages log:
name=dms-writer-thread-#92%jdbc.JdbcRemoteKeyInsertTest1% time=(1579867182194,
2020-01-24
14:59:42.194)Thread=[name=exchange-worker-#84%jdbc.JdbcRemoteKeyInsertTest1%,
id=117], state=TIMED_WAITINGLocked pages = []Locked pages log:
name=exchange-worker-#84%jdbc.JdbcRemoteKeyInsertTest1% time=(1579867182194,
2020-01-24 14:59:42.194)Thread=[name=main, id=1], state=TIMED_WAITINGLocked
pages = []Locked pages log: name=main time=(1579867182193, 2020-01-24
14:59:42.193)
[2020-01-24
14:59:42,198][ERROR][sys-stripe-4-#48%jdbc.JdbcRemoteKeyInsertTest1%][G] Failed
to execute runnable.java.lang.NullPointerException at
org.apache.ignite.internal.processors.security.SecurityUtils.nodeSecurityContext(SecurityUtils.java:132)
at
org.apache.ignite.internal.processors.security.IgniteSecurityProcessor.lambda$withContext$0(IgniteSecurityProcessor.java:106)
at
java.util.concurrent.ConcurrentHashMap.computeIfAbsent(ConcurrentHashMap.java:1660)
at
org.apache.ignite.internal.processors.security.IgniteSecurityProcessor.withContext(IgniteSecurityProcessor.java:105)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1844)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1470)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$5200(GridIoManager.java:229)
at
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1365)
at
org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:565)
at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748)
{code}
Reproducer is attached to the ticket.
It seems that remote node while sql execution receives security context with
subject id
[jira] [Updated] (IGNITE-12579) SQL INSERT operation hangs with security enabled.
[
https://issues.apache.org/jira/browse/IGNITE-12579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
PetrovMikhail updated IGNITE-12579:
---
Attachment: JdbcRemoteKeyInsertTest.java
> SQL INSERT operation hangs with security enabled.
> -
>
> Key: IGNITE-12579
> URL: https://issues.apache.org/jira/browse/IGNITE-12579
> Project: Ignite
> Issue Type: Bug
>Reporter: PetrovMikhail
>Priority: Major
> Attachments: JdbcRemoteKeyInsertTest.java
>
>
>
> SQL INSERT operation may hangs in case INSERT KEY belongs to remote node(node
> that is different from one to which jdbc connection was established) with the
> following exception in log:
> {code:java}
> [2020-01-24
> 14:59:42,189][ERROR][sys-stripe-4-#48%jdbc.JdbcRemoteKeyInsertTest1%][IgniteTestResources]
> Critical system error detected. Will be handled accordingly to configured
> handler [hnd=NoOpFailureHandler [super=AbstractFailureHandler
> [ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED,
> SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext
> [type=SYSTEM_WORKER_TERMINATION,
> err=java.lang.NullPointerException]][2020-01-24
> 14:59:42,189][ERROR][sys-stripe-4-#48%jdbc.JdbcRemoteKeyInsertTest1%][IgniteTestResources]
> Critical system error detected. Will be handled accordingly to configured
> handler [hnd=NoOpFailureHandler [super=AbstractFailureHandler
> [ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED,
> SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext
> [type=SYSTEM_WORKER_TERMINATION,
> err=java.lang.NullPointerException]]java.lang.NullPointerException at
> org.apache.ignite.internal.processors.security.SecurityUtils.nodeSecurityContext(SecurityUtils.java:132)
> at
> org.apache.ignite.internal.processors.security.IgniteSecurityProcessor.lambda$withContext$0(IgniteSecurityProcessor.java:106)
> at
> java.util.concurrent.ConcurrentHashMap.computeIfAbsent(ConcurrentHashMap.java:1660)
> at
> org.apache.ignite.internal.processors.security.IgniteSecurityProcessor.withContext(IgniteSecurityProcessor.java:105)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1844)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1470)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$5200(GridIoManager.java:229)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1365)
> at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:565)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120) at
> java.lang.Thread.run(Thread.java:748)[2020-01-24 14:59:42,198][WARN
> ][sys-stripe-4-#48%jdbc.JdbcRemoteKeyInsertTest1%][CacheDiagnosticManager]
> Page locks dump:
> Thread=[name=auth-#83%jdbc.JdbcRemoteKeyInsertTest1%, id=116],
> state=WAITINGLocked pages = []Locked pages log:
> name=auth-#83%jdbc.JdbcRemoteKeyInsertTest1% time=(1579867182194, 2020-01-24
> 14:59:42.194)Thread=[name=db-checkpoint-thread-#101%jdbc.JdbcRemoteKeyInsertTest1%,
> id=135], state=TIMED_WAITINGLocked pages = []Locked pages log:
> name=db-checkpoint-thread-#101%jdbc.JdbcRemoteKeyInsertTest1%
> time=(1579867182194, 2020-01-24
> 14:59:42.194)Thread=[name=dms-writer-thread-#92%jdbc.JdbcRemoteKeyInsertTest1%,
> id=126], state=WAITINGLocked pages = []Locked pages log:
> name=dms-writer-thread-#92%jdbc.JdbcRemoteKeyInsertTest1%
> time=(1579867182194, 2020-01-24
> 14:59:42.194)Thread=[name=exchange-worker-#84%jdbc.JdbcRemoteKeyInsertTest1%,
> id=117], state=TIMED_WAITINGLocked pages = []Locked pages log:
> name=exchange-worker-#84%jdbc.JdbcRemoteKeyInsertTest1% time=(1579867182194,
> 2020-01-24 14:59:42.194)Thread=[name=main, id=1], state=TIMED_WAITINGLocked
> pages = []Locked pages log: name=main time=(1579867182193, 2020-01-24
> 14:59:42.193)
> [2020-01-24
> 14:59:42,198][ERROR][sys-stripe-4-#48%jdbc.JdbcRemoteKeyInsertTest1%][G]
> Failed to execute runnable.java.lang.NullPointerException at
> org.apache.ignite.internal.processors.security.SecurityUtils.nodeSecurityContext(SecurityUtils.java:132)
> at
> org.apache.ignite.internal.processors.security.IgniteSecurityProcessor.lambda$withContext$0(IgniteSecurityProcessor.java:106)
> at
> java.util.concurrent.ConcurrentHashMap.computeIfAbsent(ConcurrentHashMap.java:1660)
> at
> org.apache.ignite.internal.processors.security.IgniteSecurityProcessor.withContext(IgniteSecurityProcessor.java:105)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1844)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1470)
> at
[jira] [Updated] (IGNITE-12579) SQL INSERT operation hangs with security enabled.
[
https://issues.apache.org/jira/browse/IGNITE-12579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
PetrovMikhail updated IGNITE-12579:
---
Description:
SQL INSERT operation may hangs in case INSERT KEY belongs to remote node(node
that is different from one to which jdbc connection was established) and
security enabled with the following exception in log:
{code:java}
[2020-01-24
14:59:42,189][ERROR][sys-stripe-4-#48%jdbc.JdbcRemoteKeyInsertTest1%][IgniteTestResources]
Critical system error detected. Will be handled accordingly to configured
handler [hnd=NoOpFailureHandler [super=AbstractFailureHandler
[ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED,
SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext
[type=SYSTEM_WORKER_TERMINATION,
err=java.lang.NullPointerException]][2020-01-24
14:59:42,189][ERROR][sys-stripe-4-#48%jdbc.JdbcRemoteKeyInsertTest1%][IgniteTestResources]
Critical system error detected. Will be handled accordingly to configured
handler [hnd=NoOpFailureHandler [super=AbstractFailureHandler
[ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED,
SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext
[type=SYSTEM_WORKER_TERMINATION,
err=java.lang.NullPointerException]]java.lang.NullPointerException at
org.apache.ignite.internal.processors.security.SecurityUtils.nodeSecurityContext(SecurityUtils.java:132)
at
org.apache.ignite.internal.processors.security.IgniteSecurityProcessor.lambda$withContext$0(IgniteSecurityProcessor.java:106)
at
java.util.concurrent.ConcurrentHashMap.computeIfAbsent(ConcurrentHashMap.java:1660)
at
org.apache.ignite.internal.processors.security.IgniteSecurityProcessor.withContext(IgniteSecurityProcessor.java:105)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1844)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1470)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$5200(GridIoManager.java:229)
at
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1365)
at
org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:565)
at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748)[2020-01-24 14:59:42,198][WARN
][sys-stripe-4-#48%jdbc.JdbcRemoteKeyInsertTest1%][CacheDiagnosticManager] Page
locks dump:
Thread=[name=auth-#83%jdbc.JdbcRemoteKeyInsertTest1%, id=116],
state=WAITINGLocked pages = []Locked pages log:
name=auth-#83%jdbc.JdbcRemoteKeyInsertTest1% time=(1579867182194, 2020-01-24
14:59:42.194)Thread=[name=db-checkpoint-thread-#101%jdbc.JdbcRemoteKeyInsertTest1%,
id=135], state=TIMED_WAITINGLocked pages = []Locked pages log:
name=db-checkpoint-thread-#101%jdbc.JdbcRemoteKeyInsertTest1%
time=(1579867182194, 2020-01-24
14:59:42.194)Thread=[name=dms-writer-thread-#92%jdbc.JdbcRemoteKeyInsertTest1%,
id=126], state=WAITINGLocked pages = []Locked pages log:
name=dms-writer-thread-#92%jdbc.JdbcRemoteKeyInsertTest1% time=(1579867182194,
2020-01-24
14:59:42.194)Thread=[name=exchange-worker-#84%jdbc.JdbcRemoteKeyInsertTest1%,
id=117], state=TIMED_WAITINGLocked pages = []Locked pages log:
name=exchange-worker-#84%jdbc.JdbcRemoteKeyInsertTest1% time=(1579867182194,
2020-01-24 14:59:42.194)Thread=[name=main, id=1], state=TIMED_WAITINGLocked
pages = []Locked pages log: name=main time=(1579867182193, 2020-01-24
14:59:42.193)
[2020-01-24
14:59:42,198][ERROR][sys-stripe-4-#48%jdbc.JdbcRemoteKeyInsertTest1%][G] Failed
to execute runnable.java.lang.NullPointerException at
org.apache.ignite.internal.processors.security.SecurityUtils.nodeSecurityContext(SecurityUtils.java:132)
at
org.apache.ignite.internal.processors.security.IgniteSecurityProcessor.lambda$withContext$0(IgniteSecurityProcessor.java:106)
at
java.util.concurrent.ConcurrentHashMap.computeIfAbsent(ConcurrentHashMap.java:1660)
at
org.apache.ignite.internal.processors.security.IgniteSecurityProcessor.withContext(IgniteSecurityProcessor.java:105)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1844)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1470)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$5200(GridIoManager.java:229)
at
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1365)
at
org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:565)
at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748)
{code}
Reproducer is attached to the ticket.
It seems that remote node while sql execution receives security context with
subject id
[jira] [Created] (IGNITE-12579) SQL INSERT operation hangs with security enabled.
PetrovMikhail created IGNITE-12579:
--
Summary: SQL INSERT operation hangs with security enabled.
Key: IGNITE-12579
URL: https://issues.apache.org/jira/browse/IGNITE-12579
Project: Ignite
Issue Type: Bug
Reporter: PetrovMikhail
SQL INSERT operation may hangs in case INSERT KEY belongs to remote node(node
that is different from one to which jdbc connection was established) with the
following exception in log:
{code:java}
[2020-01-24
14:59:42,189][ERROR][sys-stripe-4-#48%jdbc.JdbcRemoteKeyInsertTest1%][IgniteTestResources]
Critical system error detected. Will be handled accordingly to configured
handler [hnd=NoOpFailureHandler [super=AbstractFailureHandler
[ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED,
SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext
[type=SYSTEM_WORKER_TERMINATION,
err=java.lang.NullPointerException]][2020-01-24
14:59:42,189][ERROR][sys-stripe-4-#48%jdbc.JdbcRemoteKeyInsertTest1%][IgniteTestResources]
Critical system error detected. Will be handled accordingly to configured
handler [hnd=NoOpFailureHandler [super=AbstractFailureHandler
[ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED,
SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext
[type=SYSTEM_WORKER_TERMINATION,
err=java.lang.NullPointerException]]java.lang.NullPointerException at
org.apache.ignite.internal.processors.security.SecurityUtils.nodeSecurityContext(SecurityUtils.java:132)
at
org.apache.ignite.internal.processors.security.IgniteSecurityProcessor.lambda$withContext$0(IgniteSecurityProcessor.java:106)
at
java.util.concurrent.ConcurrentHashMap.computeIfAbsent(ConcurrentHashMap.java:1660)
at
org.apache.ignite.internal.processors.security.IgniteSecurityProcessor.withContext(IgniteSecurityProcessor.java:105)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1844)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1470)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$5200(GridIoManager.java:229)
at
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1365)
at
org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:565)
at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748)[2020-01-24 14:59:42,198][WARN
][sys-stripe-4-#48%jdbc.JdbcRemoteKeyInsertTest1%][CacheDiagnosticManager] Page
locks dump:
Thread=[name=auth-#83%jdbc.JdbcRemoteKeyInsertTest1%, id=116],
state=WAITINGLocked pages = []Locked pages log:
name=auth-#83%jdbc.JdbcRemoteKeyInsertTest1% time=(1579867182194, 2020-01-24
14:59:42.194)Thread=[name=db-checkpoint-thread-#101%jdbc.JdbcRemoteKeyInsertTest1%,
id=135], state=TIMED_WAITINGLocked pages = []Locked pages log:
name=db-checkpoint-thread-#101%jdbc.JdbcRemoteKeyInsertTest1%
time=(1579867182194, 2020-01-24
14:59:42.194)Thread=[name=dms-writer-thread-#92%jdbc.JdbcRemoteKeyInsertTest1%,
id=126], state=WAITINGLocked pages = []Locked pages log:
name=dms-writer-thread-#92%jdbc.JdbcRemoteKeyInsertTest1% time=(1579867182194,
2020-01-24
14:59:42.194)Thread=[name=exchange-worker-#84%jdbc.JdbcRemoteKeyInsertTest1%,
id=117], state=TIMED_WAITINGLocked pages = []Locked pages log:
name=exchange-worker-#84%jdbc.JdbcRemoteKeyInsertTest1% time=(1579867182194,
2020-01-24 14:59:42.194)Thread=[name=main, id=1], state=TIMED_WAITINGLocked
pages = []Locked pages log: name=main time=(1579867182193, 2020-01-24
14:59:42.193)
[2020-01-24
14:59:42,198][ERROR][sys-stripe-4-#48%jdbc.JdbcRemoteKeyInsertTest1%][G] Failed
to execute runnable.java.lang.NullPointerException at
org.apache.ignite.internal.processors.security.SecurityUtils.nodeSecurityContext(SecurityUtils.java:132)
at
org.apache.ignite.internal.processors.security.IgniteSecurityProcessor.lambda$withContext$0(IgniteSecurityProcessor.java:106)
at
java.util.concurrent.ConcurrentHashMap.computeIfAbsent(ConcurrentHashMap.java:1660)
at
org.apache.ignite.internal.processors.security.IgniteSecurityProcessor.withContext(IgniteSecurityProcessor.java:105)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1844)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1470)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$5200(GridIoManager.java:229)
at
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1365)
at
org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:565)
at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748)
{code}
Reproducer is attached
[jira] [Commented] (IGNITE-12578) CAS cache operations (replace(K, V, V), remove(K, V)) don't work with array data type
[
https://issues.apache.org/jira/browse/IGNITE-12578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17022888#comment-17022888
]
Aleksey Plekhanov commented on IGNITE-12578:
[~avinogradov], yes, it works well with List.
> CAS cache operations (replace(K, V, V), remove(K, V)) don't work with array
> data type
> -
>
> Key: IGNITE-12578
> URL: https://issues.apache.org/jira/browse/IGNITE-12578
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Reporter: Aleksey Plekhanov
>Priority: Major
>
> Values are compared using {{CacheEntryPredicateContainsValue}} predicate,
> this predicate call {{F.eq(thisVal, cacheVal)}} to compare, which gives false
> for two instances of arrays with the same content.
> Reproducer:
> {code:java}
> IgniteCache cache =
> startGrid().getOrCreateCache(DEFAULT_CACHE_NAME);
> Object val = new byte[] {1};
> cache.put(1, val);
> assertTrue(cache.replace(1, val, val));
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-12578) CAS cache operations (replace(K, V, V), remove(K, V)) don't work with array data type
[
https://issues.apache.org/jira/browse/IGNITE-12578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17022872#comment-17022872
]
Anton Vinogradov edited comment on IGNITE-12578 at 1/24/20 11:45 AM:
-
[~alex_pl]
Does it work well with List?
was (Author: avinogradov):
[~alex_pl]
Does it work well with Array?
> CAS cache operations (replace(K, V, V), remove(K, V)) don't work with array
> data type
> -
>
> Key: IGNITE-12578
> URL: https://issues.apache.org/jira/browse/IGNITE-12578
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Reporter: Aleksey Plekhanov
>Priority: Major
>
> Values are compared using {{CacheEntryPredicateContainsValue}} predicate,
> this predicate call {{F.eq(thisVal, cacheVal)}} to compare, which gives false
> for two instances of arrays with the same content.
> Reproducer:
> {code:java}
> IgniteCache cache =
> startGrid().getOrCreateCache(DEFAULT_CACHE_NAME);
> Object val = new byte[] {1};
> cache.put(1, val);
> assertTrue(cache.replace(1, val, val));
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12578) CAS cache operations (replace(K, V, V), remove(K, V)) don't work with array data type
[
https://issues.apache.org/jira/browse/IGNITE-12578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17022872#comment-17022872
]
Anton Vinogradov commented on IGNITE-12578:
---
[~alex_pl]
Does it work well with Array?
> CAS cache operations (replace(K, V, V), remove(K, V)) don't work with array
> data type
> -
>
> Key: IGNITE-12578
> URL: https://issues.apache.org/jira/browse/IGNITE-12578
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Reporter: Aleksey Plekhanov
>Priority: Major
>
> Values are compared using {{CacheEntryPredicateContainsValue}} predicate,
> this predicate call {{F.eq(thisVal, cacheVal)}} to compare, which gives false
> for two instances of arrays with the same content.
> Reproducer:
> {code:java}
> IgniteCache cache =
> startGrid().getOrCreateCache(DEFAULT_CACHE_NAME);
> Object val = new byte[] {1};
> cache.put(1, val);
> assertTrue(cache.replace(1, val, val));
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12578) CAS cache operations (replace(K, V, V), remove(K, V)) don't work with array data type
Aleksey Plekhanov created IGNITE-12578:
--
Summary: CAS cache operations (replace(K, V, V), remove(K, V))
don't work with array data type
Key: IGNITE-12578
URL: https://issues.apache.org/jira/browse/IGNITE-12578
Project: Ignite
Issue Type: Bug
Components: cache
Reporter: Aleksey Plekhanov
Values are compared using {{CacheEntryPredicateContainsValue}} predicate, this
predicate call {{F.eq(thisVal, cacheVal)}} to compare, which gives false for
two instances of arrays with the same content.
Reproducer:
{code:java}
IgniteCache cache =
startGrid().getOrCreateCache(DEFAULT_CACHE_NAME);
Object val = new byte[] {1};
cache.put(1, val);
assertTrue(cache.replace(1, val, val));
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12574) Fix failing IoStatisticsBasicIndexSelfTest
[ https://issues.apache.org/jira/browse/IGNITE-12574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17022854#comment-17022854 ] Ivan Pavlukhin commented on IGNITE-12574: - [~korlov], could you please review the patch? Visa in progress. > Fix failing IoStatisticsBasicIndexSelfTest > -- > > Key: IGNITE-12574 > URL: https://issues.apache.org/jira/browse/IGNITE-12574 > Project: Ignite > Issue Type: Bug > Components: sql >Reporter: Ivan Pavlukhin >Assignee: Ivan Pavlukhin >Priority: Major > Fix For: 2.9 > > Time Spent: 10m > Remaining Estimate: 0h > > Need to move > org.apache.ignite.internal.processors.cache.index.IoStatisticsBasicIndexSelfTest > into a test suite with enabled persistence. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12577) High persistence load can trigger erroneous assert: "Page was pin when we resolve abs pointer, it can not be evicted".
[ https://issues.apache.org/jira/browse/IGNITE-12577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stanilovsky Evgeny updated IGNITE-12577: Description: For now It seems erroneous assertion in checkpointer code : "Page was pin when we resolve abs pointer, it can not be evicted", need to be removed. (was: For now It seems erroneous assertion in checkpointer code : "") > High persistence load can trigger erroneous assert: "Page was pin when we > resolve abs pointer, it can not be evicted". > -- > > Key: IGNITE-12577 > URL: https://issues.apache.org/jira/browse/IGNITE-12577 > Project: Ignite > Issue Type: Bug > Components: data structures >Affects Versions: 2.7.6 >Reporter: Stanilovsky Evgeny >Assignee: Stanilovsky Evgeny >Priority: Major > Fix For: 2.8 > > > For now It seems erroneous assertion in checkpointer code : "Page was pin > when we resolve abs pointer, it can not be evicted", need to be removed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12577) High persistence load can trigger erroneous assert: "Page was pin when we resolve abs pointer, it can not be evicted".
[ https://issues.apache.org/jira/browse/IGNITE-12577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stanilovsky Evgeny updated IGNITE-12577: Description: For now It seems erroneous assertion in checkpointer code : "" > High persistence load can trigger erroneous assert: "Page was pin when we > resolve abs pointer, it can not be evicted". > -- > > Key: IGNITE-12577 > URL: https://issues.apache.org/jira/browse/IGNITE-12577 > Project: Ignite > Issue Type: Bug > Components: data structures >Affects Versions: 2.7.6 >Reporter: Stanilovsky Evgeny >Assignee: Stanilovsky Evgeny >Priority: Major > Fix For: 2.8 > > > For now It seems erroneous assertion in checkpointer code : "" -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12562) FreeListCachingTest.testPageListCacheLimit failing in Disk Page Compressions suite
[ https://issues.apache.org/jira/browse/IGNITE-12562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17022837#comment-17022837 ] Stanilovsky Evgeny commented on IGNITE-12562: - Seems besides Cache 2 suite timeout all other looks good, i rerun it, after green visa plz proceed. > FreeListCachingTest.testPageListCacheLimit failing in Disk Page Compressions > suite > -- > > Key: IGNITE-12562 > URL: https://issues.apache.org/jira/browse/IGNITE-12562 > Project: Ignite > Issue Type: Bug > Components: persistence >Reporter: Aleksey Plekhanov >Assignee: Aleksey Plekhanov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Test failing with IgniteOutOfMemory exception because Disk Page Compressions > changes default page size to 8192, we need at least 2*1024 (2 caches, 1024 > partitions) pages to store freelist metadata and there is no such amount of > not dirty pages after checkpoint is triggered by "too many dirty page" reason. > Explicitly defined data region max size should take into account page size to > avoid such errors. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12577) High persistence load can trigger erroneous assert: "Page was pin when we resolve abs pointer, it can not be evicted".
Stanilovsky Evgeny created IGNITE-12577: --- Summary: High persistence load can trigger erroneous assert: "Page was pin when we resolve abs pointer, it can not be evicted". Key: IGNITE-12577 URL: https://issues.apache.org/jira/browse/IGNITE-12577 Project: Ignite Issue Type: Bug Components: data structures Affects Versions: 2.7.6 Reporter: Stanilovsky Evgeny Assignee: Stanilovsky Evgeny Fix For: 2.8 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12559) Introduce @IgniteExperimental API annotation
[ https://issues.apache.org/jira/browse/IGNITE-12559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-12559: -- Ignite Flags: Docs Required > Introduce @IgniteExperimental API annotation > > > Key: IGNITE-12559 > URL: https://issues.apache.org/jira/browse/IGNITE-12559 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.8 >Reporter: Alexey Goncharuk >Assignee: Alexey Goncharuk >Priority: Major > Fix For: 2.8 > > Time Spent: 1h > Remaining Estimate: 0h > > This is a follow-up for the discussion on the dev-list: > http://apache-ignite-developers.2346864.n4.nabble.com/Internal-classes-are-exposed-in-public-API-td45146.html > The annotation will mark new APIs which are not yet finalized, but the > underlying functionality is ready to be tried by users. The annotation will > provide a good way to collect user feedback and correct wrong design choices > without a need to preserve binary and source compatibility. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12559) Introduce @IgniteExperimental API annotation
[ https://issues.apache.org/jira/browse/IGNITE-12559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-12559: -- Ignite Flags: (was: Docs Required,Release Notes Required) > Introduce @IgniteExperimental API annotation > > > Key: IGNITE-12559 > URL: https://issues.apache.org/jira/browse/IGNITE-12559 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.8 >Reporter: Alexey Goncharuk >Assignee: Alexey Goncharuk >Priority: Major > Fix For: 2.8 > > Time Spent: 1h > Remaining Estimate: 0h > > This is a follow-up for the discussion on the dev-list: > http://apache-ignite-developers.2346864.n4.nabble.com/Internal-classes-are-exposed-in-public-API-td45146.html > The annotation will mark new APIs which are not yet finalized, but the > underlying functionality is ready to be tried by users. The annotation will > provide a good way to collect user feedback and correct wrong design choices > without a need to preserve binary and source compatibility. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12576) [IEP-35] TCP communication metrics use node ID instead of consistent ID
Ivan Bessonov created IGNITE-12576: -- Summary: [IEP-35] TCP communication metrics use node ID instead of consistent ID Key: IGNITE-12576 URL: https://issues.apache.org/jira/browse/IGNITE-12576 Project: Ignite Issue Type: Improvement Reporter: Ivan Bessonov Assignee: Ivan Bessonov TcpCommunicationMetricsListener uses nodeId for metrics name. consistentId should be used instead. Also all metrics for registry should be created at once before registry added to GridMetricManager. There is no need in separate initialization for sent and received counters. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12575) Document @IgniteExperimental annotation
Alexey Goncharuk created IGNITE-12575: - Summary: Document @IgniteExperimental annotation Key: IGNITE-12575 URL: https://issues.apache.org/jira/browse/IGNITE-12575 Project: Ignite Issue Type: Task Components: documentation Affects Versions: 2.8 Reporter: Alexey Goncharuk Fix For: 2.8 We introduced the annotation to mark APIs which are exposed to users to try out new features, but the APIs are likely to evolve in the future. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12573) Copy ML dependencies to other standalone pom files in examples
[
https://issues.apache.org/jira/browse/IGNITE-12573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17022815#comment-17022815
]
Alexey Goncharuk commented on IGNITE-12573:
---
Verified by building both non-lgpl and lgpl binaries locally.
> Copy ML dependencies to other standalone pom files in examples
> ---
>
> Key: IGNITE-12573
> URL: https://issues.apache.org/jira/browse/IGNITE-12573
> Project: Ignite
> Issue Type: Task
> Components: examples
>Affects Versions: 2.8
>Reporter: Stepan Pilschikov
>Assignee: Alexey Goncharuk
>Priority: Critical
> Fix For: 2.8
>
>
> 2 dependencies missed from pom-standalone.xml and pom-standalone-lgpl.xml
> {code}
>
> org.apache.ignite
> ignite-ml-tensorflow-model-parser
> ${project.version}
>
>
> org.apache.ignite
> ignite-ml-h2o-model-parser
> ${project.version}
>
> {code}
> Need to copy this libraries from original pom.xml because examples in
> released build can't be build
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12573) Copy ML dependencies to other standalone pom files in examples
[
https://issues.apache.org/jira/browse/IGNITE-12573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17022816#comment-17022816
]
Alexey Goncharuk commented on IGNITE-12573:
---
Merged to master and ignite-2.8.
> Copy ML dependencies to other standalone pom files in examples
> ---
>
> Key: IGNITE-12573
> URL: https://issues.apache.org/jira/browse/IGNITE-12573
> Project: Ignite
> Issue Type: Task
> Components: examples
>Affects Versions: 2.8
>Reporter: Stepan Pilschikov
>Assignee: Alexey Goncharuk
>Priority: Critical
> Fix For: 2.8
>
>
> 2 dependencies missed from pom-standalone.xml and pom-standalone-lgpl.xml
> {code}
>
> org.apache.ignite
> ignite-ml-tensorflow-model-parser
> ${project.version}
>
>
> org.apache.ignite
> ignite-ml-h2o-model-parser
> ${project.version}
>
> {code}
> Need to copy this libraries from original pom.xml because examples in
> released build can't be build
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12573) Copy ML dependencies to other standalone pom files in examples
[
https://issues.apache.org/jira/browse/IGNITE-12573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-12573:
--
Ignite Flags: (was: Docs Required,Release Notes Required)
> Copy ML dependencies to other standalone pom files in examples
> ---
>
> Key: IGNITE-12573
> URL: https://issues.apache.org/jira/browse/IGNITE-12573
> Project: Ignite
> Issue Type: Task
> Components: examples
>Affects Versions: 2.8
>Reporter: Stepan Pilschikov
>Assignee: Alexey Goncharuk
>Priority: Critical
> Fix For: 2.8
>
>
> 2 dependencies missed from pom-standalone.xml and pom-standalone-lgpl.xml
> {code}
>
> org.apache.ignite
> ignite-ml-tensorflow-model-parser
> ${project.version}
>
>
> org.apache.ignite
> ignite-ml-h2o-model-parser
> ${project.version}
>
> {code}
> Need to copy this libraries from original pom.xml because examples in
> released build can't be build
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12573) Copy ML dependencies to other standalone pom files in examples
[
https://issues.apache.org/jira/browse/IGNITE-12573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-12573:
--
Fix Version/s: 2.8
> Copy ML dependencies to other standalone pom files in examples
> ---
>
> Key: IGNITE-12573
> URL: https://issues.apache.org/jira/browse/IGNITE-12573
> Project: Ignite
> Issue Type: Task
> Components: examples
>Affects Versions: 2.8
>Reporter: Stepan Pilschikov
>Assignee: Alexey Goncharuk
>Priority: Critical
> Fix For: 2.8
>
>
> 2 dependencies missed from pom-standalone.xml and pom-standalone-lgpl.xml
> {code}
>
> org.apache.ignite
> ignite-ml-tensorflow-model-parser
> ${project.version}
>
>
> org.apache.ignite
> ignite-ml-h2o-model-parser
> ${project.version}
>
> {code}
> Need to copy this libraries from original pom.xml because examples in
> released build can't be build
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12573) Copy ML dependencies to other standalone pom files in examples
[
https://issues.apache.org/jira/browse/IGNITE-12573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-12573:
--
Description:
2 dependencies missed from pom-standalone.xml and pom-standalone-lgpl.xml
{code}
org.apache.ignite
ignite-ml-tensorflow-model-parser
${project.version}
org.apache.ignite
ignite-ml-h2o-model-parser
${project.version}
{code}
Need to copy this libraries from original pom.xml because examples in released
build can't be build
was:
2 dependencies missed from pom-standalone.xml and pom-standalone-lgpl.xml
{color:#9876aa}<{color}{color:#e8bf6a}dependency{color}{color:#9876aa}>
{color}{color:#9876aa}
<{color}{color:#e8bf6a}groupId{color}{color:#9876aa}>{color}org.apache.ignite{color:#9876aa}
{color}{color:#9876aa}
<{color}{color:#e8bf6a}artifactId{color}{color:#9876aa}>{color}ignite-ml-tensorflow-model-parser{color:#9876aa}
{color}{color:#9876aa}
<{color}{color:#e8bf6a}version{color}{color:#9876aa}>{color}${project.version}{color:#9876aa}
{color}{color:#9876aa}{color}
{color:#9876aa}<{color}{color:#e8bf6a}dependency{color}{color:#9876aa}>
{color}{color:#9876aa}
<{color}{color:#e8bf6a}groupId{color}{color:#9876aa}>{color}org.apache.ignite{color:#9876aa}
{color}{color:#9876aa}
<{color}{color:#e8bf6a}artifactId{color}{color:#9876aa}>{color}ignite-ml-h2o-model-parser{color:#9876aa}
{color}{color:#9876aa}
<{color}{color:#e8bf6a}version{color}{color:#9876aa}>{color}${project.version}{color:#9876aa}
{color}{color:#9876aa}{color}
Need to copy this libraries from original pom.xml because examples in released
build can't be build
> Copy ML dependencies to other standalone pom files in examples
> ---
>
> Key: IGNITE-12573
> URL: https://issues.apache.org/jira/browse/IGNITE-12573
> Project: Ignite
> Issue Type: Task
> Components: examples
>Affects Versions: 2.8
>Reporter: Stepan Pilschikov
>Priority: Critical
>
> 2 dependencies missed from pom-standalone.xml and pom-standalone-lgpl.xml
> {code}
>
> org.apache.ignite
> ignite-ml-tensorflow-model-parser
> ${project.version}
>
>
> org.apache.ignite
> ignite-ml-h2o-model-parser
> ${project.version}
>
> {code}
> Need to copy this libraries from original pom.xml because examples in
> released build can't be build
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-12573) Copy ML dependencies to other standalone pom files in examples
[
https://issues.apache.org/jira/browse/IGNITE-12573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk reassigned IGNITE-12573:
-
Assignee: Alexey Goncharuk
> Copy ML dependencies to other standalone pom files in examples
> ---
>
> Key: IGNITE-12573
> URL: https://issues.apache.org/jira/browse/IGNITE-12573
> Project: Ignite
> Issue Type: Task
> Components: examples
>Affects Versions: 2.8
>Reporter: Stepan Pilschikov
>Assignee: Alexey Goncharuk
>Priority: Critical
>
> 2 dependencies missed from pom-standalone.xml and pom-standalone-lgpl.xml
> {code}
>
> org.apache.ignite
> ignite-ml-tensorflow-model-parser
> ${project.version}
>
>
> org.apache.ignite
> ignite-ml-h2o-model-parser
> ${project.version}
>
> {code}
> Need to copy this libraries from original pom.xml because examples in
> released build can't be build
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12559) Introduce @IgniteExperimental API annotation
[
https://issues.apache.org/jira/browse/IGNITE-12559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17022813#comment-17022813
]
Ignite TC Bot commented on IGNITE-12559:
{panel:title=Branch: [pull/7279/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4954089buildTypeId=IgniteTests24Java8_RunAll]
> Introduce @IgniteExperimental API annotation
>
>
> Key: IGNITE-12559
> URL: https://issues.apache.org/jira/browse/IGNITE-12559
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.8
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> This is a follow-up for the discussion on the dev-list:
> http://apache-ignite-developers.2346864.n4.nabble.com/Internal-classes-are-exposed-in-public-API-td45146.html
> The annotation will mark new APIs which are not yet finalized, but the
> underlying functionality is ready to be tried by users. The annotation will
> provide a good way to collect user feedback and correct wrong design choices
> without a need to preserve binary and source compatibility.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12522) Extend test coverage [IGNITE-12104] Check deployment from cache before to load it from local or version storage
[ https://issues.apache.org/jira/browse/IGNITE-12522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17022811#comment-17022811 ] Vladislav Pyatkov commented on IGNITE-12522: [~akalashnikov] Thanks for review. Fixed. Please, look again. > Extend test coverage [IGNITE-12104] Check deployment from cache before to > load it from local or version storage > --- > > Key: IGNITE-12522 > URL: https://issues.apache.org/jira/browse/IGNITE-12522 > Project: Ignite > Issue Type: Improvement >Reporter: Vladislav Pyatkov >Assignee: Vladislav Pyatkov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12571) Statistics of query cache statements
[
https://issues.apache.org/jira/browse/IGNITE-12571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17022807#comment-17022807
]
Ignite TC Bot commented on IGNITE-12571:
{panel:title=Branch: [pull/7299/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4954467buildTypeId=IgniteTests24Java8_RunAll]
> Statistics of query cache statements
>
>
> Key: IGNITE-12571
> URL: https://issues.apache.org/jira/browse/IGNITE-12571
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Konstantin Orlov
>Assignee: Konstantin Orlov
>Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We need to collect hit/miss statistics for the query cache.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-12470) Pme-free switch feature should be deactivatable
[ https://issues.apache.org/jira/browse/IGNITE-12470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov reassigned IGNITE-12470: - Assignee: Anton Vinogradov (was: Sergei Ryzhov) > Pme-free switch feature should be deactivatable > --- > > Key: IGNITE-12470 > URL: https://issues.apache.org/jira/browse/IGNITE-12470 > Project: Ignite > Issue Type: Task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Blocker > Labels: newbie > Fix For: 2.8, 2.9 > > Time Spent: 4h 50m > Remaining Estimate: 0h > > We should be able to disable this feature by some env/jvm property. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12470) Pme-free switch feature should be deactivatable
[ https://issues.apache.org/jira/browse/IGNITE-12470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17022798#comment-17022798 ] Anton Vinogradov commented on IGNITE-12470: --- [~mmuzaf], Going to provide solution next week. > Pme-free switch feature should be deactivatable > --- > > Key: IGNITE-12470 > URL: https://issues.apache.org/jira/browse/IGNITE-12470 > Project: Ignite > Issue Type: Task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Blocker > Labels: newbie > Fix For: 2.8, 2.9 > > Time Spent: 4h 50m > Remaining Estimate: 0h > > We should be able to disable this feature by some env/jvm property. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12557) Destroy of big cache which is not only cache in cache group causes IgniteOOME
[
https://issues.apache.org/jira/browse/IGNITE-12557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17022796#comment-17022796
]
Alexey Scherbakov commented on IGNITE-12557:
[~alex_pl]
I've prepared a fix for blocked checkpoint, but it doesn't solves everything.
As you noted we still have critical issues with cache destroying:
1. A garbage remains in cache group if node has left/failed during destroy. [1]
2. A cache is destroyed synchronously during PME impairing grid availability.
[2]
Unfortunately it seems I cannot be able to start working on them in nearest
future.
You can pick them up if you want.
Waiting for review. [~ivan.glukos] [~agoncharuk] can you join ?
[1] https://issues.apache.org/jira/browse/IGNITE-11578
[2] https://issues.apache.org/jira/browse/IGNITE-12572
> Destroy of big cache which is not only cache in cache group causes IgniteOOME
> -
>
> Key: IGNITE-12557
> URL: https://issues.apache.org/jira/browse/IGNITE-12557
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Reporter: Aleksey Plekhanov
>Assignee: Alexey Scherbakov
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When {{destroyCache()}} is invoked {{checkpointReadLock}} is held by exchange
> thread during all time cache entries are cleaning. Meanwhile,
> {{db-checkpoint-thread}} can't acquire checkpoint write lock and can't start
> checkpoint. After some time all page-memory has filled with dirty pages and
> attempt to acquire a new page causes IgniteOOM exception:
> {noformat}
> class org.apache.ignite.internal.mem.IgniteOutOfMemoryException: Failed to
> find a page for eviction [segmentCapacity=40485, loaded=15881,
> maxDirtyPages=11910, dirtyPages=15881, cpPages=0, pinnedInSegment=0,
> failedToPrepare=15881]
> at
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$Segment.tryToFindSequentially(PageMemoryImpl.java:2420)
> at
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$Segment.removePageForReplacement(PageMemoryImpl.java:2314)
> at
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:743)
> at
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:679)
> at
> org.apache.ignite.internal.processors.cache.persistence.DataStructure.acquirePage(DataStructure.java:158)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.acquirePage(BPlusTree.java:5872)
> at
> org.apache.ignite.internal.processors.cache.tree.CacheDataTree.compareKeys(CacheDataTree.java:435)
> at
> org.apache.ignite.internal.processors.cache.tree.CacheDataTree.compare(CacheDataTree.java:384)
> at
> org.apache.ignite.internal.processors.cache.tree.CacheDataTree.compare(CacheDataTree.java:63)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.compare(BPlusTree.java:5214)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.findInsertionPoint(BPlusTree.java:5134)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Search.run0(BPlusTree.java:298)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$GetPageHandler.run(BPlusTree.java:5723)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Search.run(BPlusTree.java:278)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$GetPageHandler.run(BPlusTree.java:5709)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.readPage(PageHandler.java:169)
> at
> org.apache.ignite.internal.processors.cache.persistence.DataStructure.read(DataStructure.java:364)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.read(BPlusTree.java:5910)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.removeDown(BPlusTree.java:2077)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doRemove(BPlusTree.java:2007)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.removex(BPlusTree.java:1838)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.clear(IgniteCacheOffheapManagerImpl.java:2963)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.clear(GridCacheOffheapManager.java:2611)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.removeCacheData(IgniteCacheOffheapManagerImpl.java:296)
> at
>
[jira] [Commented] (IGNITE-12557) Destroy of big cache which is not only cache in cache group causes IgniteOOME
[
https://issues.apache.org/jira/browse/IGNITE-12557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17022785#comment-17022785
]
Ignite TC Bot commented on IGNITE-12557:
{panel:title=Branch: [pull/7298/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4954351buildTypeId=IgniteTests24Java8_RunAll]
> Destroy of big cache which is not only cache in cache group causes IgniteOOME
> -
>
> Key: IGNITE-12557
> URL: https://issues.apache.org/jira/browse/IGNITE-12557
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Reporter: Aleksey Plekhanov
>Assignee: Alexey Scherbakov
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When {{destroyCache()}} is invoked {{checkpointReadLock}} is held by exchange
> thread during all time cache entries are cleaning. Meanwhile,
> {{db-checkpoint-thread}} can't acquire checkpoint write lock and can't start
> checkpoint. After some time all page-memory has filled with dirty pages and
> attempt to acquire a new page causes IgniteOOM exception:
> {noformat}
> class org.apache.ignite.internal.mem.IgniteOutOfMemoryException: Failed to
> find a page for eviction [segmentCapacity=40485, loaded=15881,
> maxDirtyPages=11910, dirtyPages=15881, cpPages=0, pinnedInSegment=0,
> failedToPrepare=15881]
> at
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$Segment.tryToFindSequentially(PageMemoryImpl.java:2420)
> at
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$Segment.removePageForReplacement(PageMemoryImpl.java:2314)
> at
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:743)
> at
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:679)
> at
> org.apache.ignite.internal.processors.cache.persistence.DataStructure.acquirePage(DataStructure.java:158)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.acquirePage(BPlusTree.java:5872)
> at
> org.apache.ignite.internal.processors.cache.tree.CacheDataTree.compareKeys(CacheDataTree.java:435)
> at
> org.apache.ignite.internal.processors.cache.tree.CacheDataTree.compare(CacheDataTree.java:384)
> at
> org.apache.ignite.internal.processors.cache.tree.CacheDataTree.compare(CacheDataTree.java:63)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.compare(BPlusTree.java:5214)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.findInsertionPoint(BPlusTree.java:5134)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Search.run0(BPlusTree.java:298)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$GetPageHandler.run(BPlusTree.java:5723)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Search.run(BPlusTree.java:278)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$GetPageHandler.run(BPlusTree.java:5709)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.readPage(PageHandler.java:169)
> at
> org.apache.ignite.internal.processors.cache.persistence.DataStructure.read(DataStructure.java:364)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.read(BPlusTree.java:5910)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.removeDown(BPlusTree.java:2077)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doRemove(BPlusTree.java:2007)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.removex(BPlusTree.java:1838)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.clear(IgniteCacheOffheapManagerImpl.java:2963)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.clear(GridCacheOffheapManager.java:2611)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.removeCacheData(IgniteCacheOffheapManagerImpl.java:296)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.stopCache(IgniteCacheOffheapManagerImpl.java:258)
> at
> org.apache.ignite.internal.processors.cache.CacheGroupContext.stopCache(CacheGroupContext.java:825)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.stopCache(GridCacheProcessor.java:1070)
> at
>
[jira] [Created] (IGNITE-12574) Fix failing IoStatisticsBasicIndexSelfTest
Ivan Pavlukhin created IGNITE-12574: --- Summary: Fix failing IoStatisticsBasicIndexSelfTest Key: IGNITE-12574 URL: https://issues.apache.org/jira/browse/IGNITE-12574 Project: Ignite Issue Type: Bug Components: sql Reporter: Ivan Pavlukhin Assignee: Ivan Pavlukhin Fix For: 2.9 Need to move org.apache.ignite.internal.processors.cache.index.IoStatisticsBasicIndexSelfTest into a test suite with enabled persistence. -- This message was sent by Atlassian Jira (v8.3.4#803005)
