[jira] [Comment Edited] (IGNITE-15528) JRaft creates at least 4 threads for every raft group on a leader
[
https://issues.apache.org/jira/browse/IGNITE-15528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17437924#comment-17437924
]
Alexey Scherbakov edited comment on IGNITE-15528 at 11/3/21, 2:59 PM:
--
This patch includes a shared pool for timers and a refactoring for explicit
shared pool mods.
In this mode node will not manage it's resources, otherwise it will cleanup
everything on node stop.
As a result of a patch threads are not longer spawn during test runs. I was
able to susccesfully start 500 raft groupusing a small amount of heap.
Ready for review.
was (Author: ascherbakov):
Ready for review.
> JRaft creates at least 4 threads for every raft group on a leader
> --
>
> Key: IGNITE-15528
> URL: https://issues.apache.org/jira/browse/IGNITE-15528
> Project: Ignite
> Issue Type: Improvement
>Reporter: Mirza Aliev
>Assignee: Alexey Scherbakov
>Priority: Blocker
> Labels: ignite-3
> Fix For: 3.0.0-alpha4
>
>
> When we create a raft group on a leader, jraft creates at least 4 threads for
> every raft group: one thread for {{electionTimer}}, {{voteTimer}},
> {{stepDownTimer}}, and {{snapshotTimer}}. To be more precise, every timer is
> an instance of {{HashedWheelTimer}}, which creates one thread:
> {code:java}
> private final Worker worker = new Worker();
> ...
> workerThread = threadFactory.newThread(worker);
> {code}
> This fact leads to restrictions on the number of partitions that might be
> created, as far as every partition is associated with a raft group. For
> example, one table with 1024 partitions leads to at least 4096 threads on a
> single node.
> Changing {{HashedWheelTimer}} to {{DefaultTimer}} with shared pool won't make
> any sense, as far as the workload of the shared executor likely will lead to
> instability of cluster because threads are timer threads (election timer, for
> example).
> A possible solution is to implement batched handling of raft groups requests,
> like {{appendEntriesRequest}}. In this approach, timers could be shared by
> raft groups. There is an issue in original JRaft repo with some close ideas
> https://github.com/sofastack/sofa-jraft/issues/672
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12310) SortedEvictionPolicy fails with java.lang.ClassCastException: java.lang.Integer cannot be cast to java.lang. in case of Byte, Short, Long, etc.
[
https://issues.apache.org/jira/browse/IGNITE-12310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolay Izhikov updated IGNITE-12310:
-
Labels: ise (was: )
> SortedEvictionPolicy fails with java.lang.ClassCastException:
> java.lang.Integer cannot be cast to java.lang. in case of Byte,
> Short, Long, etc.
>
>
> Key: IGNITE-12310
> URL: https://issues.apache.org/jira/browse/IGNITE-12310
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexander Lapin
>Priority: Major
> Labels: ise
>
> {code:java}
> java.lang.ClassCastException: java.lang.Long cannot be cast to
> java.lang.Integer
> at java.lang.Integer.compareTo(Integer.java:52)
> at
> org.apache.ignite.cache.eviction.sorted.SortedEvictionPolicy$DefaultHolderComparator.compare(SortedEvictionPolicy.java:359)
> at
> org.apache.ignite.cache.eviction.sorted.SortedEvictionPolicy$DefaultHolderComparator.compare(SortedEvictionPolicy.java:347)
> at
> java.util.concurrent.ConcurrentSkipListMap.cpr(ConcurrentSkipListMap.java:655)
> at
> java.util.concurrent.ConcurrentSkipListMap.doPut(ConcurrentSkipListMap.java:835)
> at
> java.util.concurrent.ConcurrentSkipListMap.putIfAbsent(ConcurrentSkipListMap.java:1979)
> at
> org.apache.ignite.internal.util.GridConcurrentSkipListSet.add(GridConcurrentSkipListSet.java:142)
> at
> org.apache.ignite.cache.eviction.sorted.SortedEvictionPolicy$GridConcurrentSkipListSetEx.add(SortedEvictionPolicy.java:397)
> at
> org.apache.ignite.cache.eviction.sorted.SortedEvictionPolicy.touch(SortedEvictionPolicy.java:175)
> at
> org.apache.ignite.cache.eviction.AbstractEvictionPolicy.onEntryAccessed(AbstractEvictionPolicy.java:87)
> at
> org.apache.ignite.internal.processors.cache.GridCacheEvictionManager.notifyPolicy(GridCacheEvictionManager.java:319)
> at
> org.apache.ignite.internal.processors.cache.GridCacheEvictionManager.touch(GridCacheEvictionManager.java:228)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.touch(GridCacheMapEntry.java:5052)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.unlockEntries(GridDhtAtomicCache.java:3104)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1905)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1668)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.sendSingleRequest(GridNearAtomicAbstractUpdateFuture.java:299)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.map(GridNearAtomicUpdateFuture.java:814)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapOnTopology(GridNearAtomicUpdateFuture.java:666)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.map(GridNearAtomicAbstractUpdateFuture.java:248)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAll0(GridDhtAtomicCache.java:1104)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.putAll0(GridDhtAtomicCache.java:654)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.putAll(GridCacheAdapter.java:2513)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.putAll(IgniteCacheProxyImpl.java:1264)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.putAll(GatewayProtectedCacheProxy.java:863)
> at
> org.apache.ignite.internal.processors.cache.GridCacheDataTypesCoverageTest.checkBasicCacheOperations(GridCacheDataTypesCoverageTest.java:624)
> at
> org.apache.ignite.internal.processors.cache.GridCacheDataTypesCoverageTest.testLongDataType(GridCacheDataTypesCoverageTest.java:347)
> 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:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
>
[jira] [Resolved] (IGNITE-12314) Unexpected return type in case of retrieving Byte[]{1,2,3} from cache value.
[
https://issues.apache.org/jira/browse/IGNITE-12314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolay Izhikov resolved IGNITE-12314.
--
Resolution: Duplicate
The issue resolved in scope of IGNITE-14742.
For {{IgniteSystemProperties#USE_TYPED_ARRAYS=true}} mode array component type
preserved during SerDe.
> Unexpected return type in case of retrieving Byte[]{1,2,3} from cache value.
>
>
> Key: IGNITE-12314
> URL: https://issues.apache.org/jira/browse/IGNITE-12314
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexander Lapin
>Priority: Major
> Labels: ise, newbie
>
> Unexpected return type in case of retrieving Byte[]\{1,2,3} from cache value:
> {code:java}
> cache.put("aaa", new Byte[] {1, 2, 3});
> cache.get("aaa");{code}
> Byte[3]@... expected with corresponding content, however Object[3]@... got.
>
> Seems that it's related to primitive wrapers, cause String[] as value works
> as expected:
> {code:java}
> cache.put("aaa", new String[] {"1", "2", "3"});
> cache.get("aaa");{code}
>
> Arrays of primitives also works as expected:
> {code:java}
> cache.put("aaa", new byte[] {1, 2, 3});
> cache.get("aaa");{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15234) Thin 3.0: Perf: ByteBuf-based message packer and unpacker
[
https://issues.apache.org/jira/browse/IGNITE-15234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-15234:
Fix Version/s: 3.0.0-alpha4
> Thin 3.0: Perf: ByteBuf-based message packer and unpacker
> -
>
> Key: IGNITE-15234
> URL: https://issues.apache.org/jira/browse/IGNITE-15234
> Project: Ignite
> Issue Type: Improvement
> Components: thin client
>Affects Versions: 3.0.0-alpha3
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha4
>
>
> Current implementations of *ClientMessagePacker* and *ClientMessageUnpacker*
> are based on *msgpack-core* library and involve intermediate classes and
> buffers:
> {code:java}
> public ClientMessageUnpacker(ByteBuf buf) {
> super(new InputStreamBufferInput(new ByteBufInputStream(buf)),
> MessagePack.DEFAULT_UNPACKER_CONFIG);
> this.buf = buf;
> }
> {code}
> * MessageUnpacker and MessagePacker classes use internal heap-allocated
> buffers
> * InputStreamBufferInput uses another buffer
> Netty ByteBuf is efficient by itself, we can implement packer and unpacker
> directly on top of it without extra buffers and indirection.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15870) Calcite. Replace usages of Lists and Sets of int to IntList\IntSet where possible
[
https://issues.apache.org/jira/browse/IGNITE-15870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yury Gerzhedovich updated IGNITE-15870:
---
Labels: calcite calcite2-required calcite3-required ignite-3 tech-debt
(was: calcite calcite3-required ignite-3 tech-debt)
> Calcite. Replace usages of Lists and Sets of int to IntList\IntSet where
> possible
> -
>
> Key: IGNITE-15870
> URL: https://issues.apache.org/jira/browse/IGNITE-15870
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Affects Versions: 3.0.0-alpha3
>Reporter: Vladimir Ermakov
>Priority: Major
> Labels: calcite, calcite2-required, calcite3-required, ignite-3,
> tech-debt
>
> Currently there is a number of List\Set usages in
> {{ignite-calcite}} module. Better to replace them with more optimal fastUtils
> List\Set for int primitives.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15870) Calcite. Replace usages of Lists and Sets of int to IntList\IntSet where possible
[
https://issues.apache.org/jira/browse/IGNITE-15870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yury Gerzhedovich updated IGNITE-15870:
---
Labels: calcite calcite3-required ignite-3 tech-debt (was: calcite
calcite2-required calcite3-required ignite-3 tech-debt)
> Calcite. Replace usages of Lists and Sets of int to IntList\IntSet where
> possible
> -
>
> Key: IGNITE-15870
> URL: https://issues.apache.org/jira/browse/IGNITE-15870
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Affects Versions: 3.0.0-alpha3
>Reporter: Vladimir Ermakov
>Priority: Major
> Labels: calcite, calcite3-required, ignite-3, tech-debt
>
> Currently there is a number of List\Set usages in
> {{ignite-calcite}} module. Better to replace them with more optimal fastUtils
> List\Set for int primitives.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-15443) Add Map with primitive keys implementations.
[ https://issues.apache.org/jira/browse/IGNITE-15443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17438054#comment-17438054 ] Vladimir Ermakov commented on IGNITE-15443: --- Based on the article ([http://java-performance.info/hashmap-overview-jdk-fastutil-goldman-sachs-hppc-koloboke-trove-january-2015/)] and the tests attached to it ([https://github.com/mikvor/hashmapTest]), I made a comparison of different map implementations(including IntMap from Ignite 2, FastUtils, Netty, Trove, JDK and OpenHFT). The fastest in the tests were Ignite 2 and FastUtils implementations. After reviewing the code, it became clear that the implementation of the maps is quite similar. However, in FastUtils library some parts of the code are more optimal due to less creation of objects. Given that FastUtils library may contain other useful data structures, it was decided to add it as dependency to the project using the maven-shading plugin. The dependency will be added in the IGNITE-15462 task. > Add Map with primitive keys implementations. > > > Key: IGNITE-15443 > URL: https://issues.apache.org/jira/browse/IGNITE-15443 > Project: Ignite > Issue Type: Improvement >Reporter: Andrey Mashenkov >Assignee: Vladimir Ermakov >Priority: Major > Labels: ignite-3, newbie, perfomance > > There are a number of places where Map and Map Object> are used. > Let's add an optimized Map with a primitive key (IntMap, IntIntMap) to the > ignite-core module. > Let's benchmark next candidates and choose one > * IntMap from Ignite 2 with robinhood hashing. > * FastUtils > * Netty > * OpenHFT -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-15868) Unexpected command: PROBE when Control Center authorisation is enabled
[
https://issues.apache.org/jira/browse/IGNITE-15868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17437995#comment-17437995
]
Dmitriy Borunov commented on IGNITE-15868:
--
[~anovikov] pls review [https://github.com/apache/ignite/pull/9551]
> Unexpected command: PROBE when Control Center authorisation is enabled
> --
>
> Key: IGNITE-15868
> URL: https://issues.apache.org/jira/browse/IGNITE-15868
> Project: Ignite
> Issue Type: Bug
> Components: platforms, thin client
>Affects Versions: 2.12
>Reporter: Dmitriy Borunov
>Priority: Major
> Fix For: 2.13
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Rest API Probe is not working when Control Center authorisation is enabled
> {noformat}
> [2021-11-01T13:35:33,550][ERROR][rest-#125%nebula-node%][GridRestProcessor]
> Runtime error caught during grid runnable execution: GridWorker
> [name=rest-proc-work
> er, igniteInstanceName=nebula-node, finished=false,
> heartbeatTs=1635773733544, hashCode=1386655371, interrupted=false,
> runner=rest-#125%nebula-node%]
> java.lang.AssertionError: Unexpected command: PROBE
> at
> org.apache.ignite.internal.processors.rest.GridRestProcessor.authorize(GridRestProcessor.java:968)
> ~[ignite-core-8.8.10.jar:8.8.10]
> at
> org.apache.ignite.internal.processors.rest.GridRestProcessor.handleRequest(GridRestProcessor.java:286)
> ~[ignite-core-8.8.10.jar:8.8.10]
> at
> org.apache.ignite.internal.processors.rest.GridRestProcessor.access$100(GridRestProcessor.java:108)
> ~[ignite-core-8.8.10.jar:8.8.10]
> at
> org.apache.ignite.internal.processors.rest.GridRestProcessor$2.body(GridRestProcessor.java:183)
> ~[ignite-core-8.8.10.jar:8.8.10]
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
> [ignite-core-8.8.10.jar:8.8.10]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> [?:?]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> [?:?]
> at java.lang.Thread.run(Thread.java:829) [?:?]{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15869) Fix build for aws, gce, azure cloud storages for ignite extensions
[
https://issues.apache.org/jira/browse/IGNITE-15869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-15869:
-
Description:
Running tests finishes with an error:
{code}
[ERROR] Failures:
[ERROR]
S3CheckpointSpiConfigSelfTest.:28->GridSpiAbstractConfigTest.:34->GridSpiAbstractTest.:112->GridAbstractTest.:320
null
[ERROR] Errors:
[ERROR]
S3CheckpointSpiStartStopBucketEndpointSelfTest.:32->GridSpiStartStopAbstractTest.:33->GridSpiAbstractTest.:112->GridAbstractTest.:320
» NoClassDefFound
[ERROR]
S3CheckpointSpiStartStopSSEAlgorithmSelfTest.:32->GridSpiStartStopAbstractTest.:33->GridSpiAbstractTest.:112->GridAbstractTest.:320
» NoClassDefFound
[ERROR]
S3CheckpointSpiStartStopSelfTest.:32->GridSpiStartStopAbstractTest.:33->GridSpiAbstractTest.:112->GridAbstractTest.:320
» NoClassDefFound
[ERROR] TcpDiscoveryAlbIpFinderSelfTest » InvocationTarget
[ERROR] TcpDiscoveryElbIpFinderSelfTest » InvocationTarget
[ERROR] TcpDiscoveryS3IpFinderAwsCredentialsProviderSelfTest »
InvocationTarget
[ERROR] TcpDiscoveryS3IpFinderAwsCredentialsSelfTest » InvocationTarget
[ERROR] TcpDiscoveryS3IpFinderBucketEndpointSelfTest » InvocationTarget
[ERROR] TcpDiscoveryS3IpFinderKeyPrefixSelfTest » InvocationTarget
[ERROR] TcpDiscoveryS3IpFinderSSEAlgorithmSelfTest » InvocationTarget
[ERROR] DummyObjectListingTest » InvocationTarget
[ERROR] DummyS3ClientTest » InvocationTarget
[ERROR] AsymmetricKeyEncryptionServiceTest » InvocationTarget
[ERROR] AwsKmsEncryptionServiceTest » InvocationTarget
[ERROR] MockEncryptionServiceTest » InvocationTarget
[ERROR] SymmetricKeyEncryptionServiceTest » InvocationTarget
{code}
The azure module running with exception (the {{jackson-databind}} dependency
required to be updated):
{code}
[ERROR] Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 1.763 s
<<< FAILURE! - in
org.apache.ignite.spi.discovery.tcp.ipfinder.azure.TcpDiscoveryAzureBlobStoreIpFinderSelfTest
[ERROR]
org.apache.ignite.spi.discovery.tcp.ipfinder.azure.TcpDiscoveryAzureBlobStoreIpFinderSelfTest.testIpFinder
Time elapsed: 0.35 s <<< ERROR!
java.lang.NoClassDefFoundError: com/fasterxml/jackson/databind/cfg/MapperBuilder
at
org.apache.ignite.spi.discovery.tcp.ipfinder.azure.TcpDiscoveryAzureBlobStoreIpFinderSelfTest.ipFinder(TcpDiscoveryAzureBlobStoreIpFinderSelfTest.java:85)
at
org.apache.ignite.spi.discovery.tcp.ipfinder.azure.TcpDiscoveryAzureBlobStoreIpFinderSelfTest.ipFinder(TcpDiscoveryAzureBlobStoreIpFinderSelfTest.java:31)
Caused by: java.lang.ClassNotFoundException:
com.fasterxml.jackson.databind.cfg.MapperBuilder
at
org.apache.ignite.spi.discovery.tcp.ipfinder.azure.TcpDiscoveryAzureBlobStoreIpFinderSelfTest.ipFinder(TcpDiscoveryAzureBlobStoreIpFinderSelfTest.java:85)
at
org.apache.ignite.spi.discovery.tcp.ipfinder.azure.TcpDiscoveryAzureBlobStoreIpFinderSelfTest.ipFinder(TcpDiscoveryAzureBlobStoreIpFinderSelfTest.java:31)
{code}
was:
Running tests finishes with an error:
{code}
[ERROR] Failures:
[ERROR]
S3CheckpointSpiConfigSelfTest.:28->GridSpiAbstractConfigTest.:34->GridSpiAbstractTest.:112->GridAbstractTest.:320
null
[ERROR] Errors:
[ERROR]
S3CheckpointSpiStartStopBucketEndpointSelfTest.:32->GridSpiStartStopAbstractTest.:33->GridSpiAbstractTest.:112->GridAbstractTest.:320
» NoClassDefFound
[ERROR]
S3CheckpointSpiStartStopSSEAlgorithmSelfTest.:32->GridSpiStartStopAbstractTest.:33->GridSpiAbstractTest.:112->GridAbstractTest.:320
» NoClassDefFound
[ERROR]
S3CheckpointSpiStartStopSelfTest.:32->GridSpiStartStopAbstractTest.:33->GridSpiAbstractTest.:112->GridAbstractTest.:320
» NoClassDefFound
[ERROR] TcpDiscoveryAlbIpFinderSelfTest » InvocationTarget
[ERROR] TcpDiscoveryElbIpFinderSelfTest » InvocationTarget
[ERROR] TcpDiscoveryS3IpFinderAwsCredentialsProviderSelfTest »
InvocationTarget
[ERROR] TcpDiscoveryS3IpFinderAwsCredentialsSelfTest » InvocationTarget
[ERROR] TcpDiscoveryS3IpFinderBucketEndpointSelfTest » InvocationTarget
[ERROR] TcpDiscoveryS3IpFinderKeyPrefixSelfTest » InvocationTarget
[ERROR] TcpDiscoveryS3IpFinderSSEAlgorithmSelfTest » InvocationTarget
[ERROR] DummyObjectListingTest » InvocationTarget
[ERROR] DummyS3ClientTest » InvocationTarget
[ERROR] AsymmetricKeyEncryptionServiceTest » InvocationTarget
[ERROR] AwsKmsEncryptionServiceTest » InvocationTarget
[ERROR] MockEncryptionServiceTest » InvocationTarget
[ERROR] SymmetricKeyEncryptionServiceTest » InvocationTarget
{code}
> Fix build for aws, gce, azure cloud storages for ignite extensions
> --
>
> Key: IGNITE-15869
> URL: https://issues.apache.org/jira/browse/IGNITE-15869
> Project: Ignite
> Issue Type: Task
> Components: extensions
>Reporter: Maxim Muzafarov
>
[jira] [Updated] (IGNITE-15375) Add README.md for vault module
[ https://issues.apache.org/jira/browse/IGNITE-15375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-15375: - Ignite Flags: (was: Release Notes Required) > Add README.md for vault module > -- > > Key: IGNITE-15375 > URL: https://issues.apache.org/jira/browse/IGNITE-15375 > Project: Ignite > Issue Type: Sub-task >Reporter: Mirza Aliev >Assignee: Mirza Aliev >Priority: Major > Labels: ignite-3, internal-doc > > Need to add descriptive README.md for vault module -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15870) Calcite. Replace usages of Lists and Sets of int to IntList\IntSet where possible
[
https://issues.apache.org/jira/browse/IGNITE-15870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ermakov updated IGNITE-15870:
--
Description: Currently there is a number of List\Set
usages in {{ignite-calcite}} module. Better to replace them with more optimal
fastUtils List\Set for int primitives.
> Calcite. Replace usages of Lists and Sets of int to IntList\IntSet where
> possible
> -
>
> Key: IGNITE-15870
> URL: https://issues.apache.org/jira/browse/IGNITE-15870
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Affects Versions: 3.0.0-alpha3
>Reporter: Vladimir Ermakov
>Priority: Major
> Labels: calcite, calcite2-required, calcite3-required, ignite-3,
> tech-debt
>
> Currently there is a number of List\Set usages in
> {{ignite-calcite}} module. Better to replace them with more optimal fastUtils
> List\Set for int primitives.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-15870) Calcite. Replace usages of Lists and Sets of int to IntList\IntSet where possible
Vladimir Ermakov created IGNITE-15870: - Summary: Calcite. Replace usages of Lists and Sets of int to IntList\IntSet where possible Key: IGNITE-15870 URL: https://issues.apache.org/jira/browse/IGNITE-15870 Project: Ignite Issue Type: Improvement Components: sql Affects Versions: 3.0.0-alpha3 Reporter: Vladimir Ermakov -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15371) [Ignite 3] Switch to Google code style
[ https://issues.apache.org/jira/browse/IGNITE-15371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-15371: - Ignite Flags: (was: Docs Required,Release Notes Required) > [Ignite 3] Switch to Google code style > -- > > Key: IGNITE-15371 > URL: https://issues.apache.org/jira/browse/IGNITE-15371 > Project: Ignite > Issue Type: Improvement > Components: build >Affects Versions: 3.0.0-alpha2 >Reporter: Valentin Kulichenko >Assignee: Kirill Tkalenko >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha4 > > Attachments: ignite-checks.xml > > Time Spent: 20m > Remaining Estimate: 0h > > As agreed in [1], we need to switch to the Google code style with two changes: > * 140 column limit instead of 100 > * 4/8 spaces indentation instead of 2/4 > The updated XML file for the Checkstyle Plugin is attached. > Also, > # Create coding guideline wiki page for Ignite 3 > # Update links to CONTRIBUTING.md > [1] > https://lists.apache.org/thread.html/rfa1e775f27b99b1f14c356e25cc52f83eb90c7553db1f1a2aba136c6%40%3Cdev.ignite.apache.org%3E -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15869) Fix build for aws, gce, azure cloud storages for ignite extensions
[
https://issues.apache.org/jira/browse/IGNITE-15869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-15869:
-
Ignite Flags: (was: Docs Required,Release Notes Required)
> Fix build for aws, gce, azure cloud storages for ignite extensions
> --
>
> Key: IGNITE-15869
> URL: https://issues.apache.org/jira/browse/IGNITE-15869
> Project: Ignite
> Issue Type: Task
> Components: extensions
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Major
>
> Running tests finishes with an error:
> {code}
> [ERROR] Failures:
> [ERROR]
> S3CheckpointSpiConfigSelfTest.:28->GridSpiAbstractConfigTest.:34->GridSpiAbstractTest.:112->GridAbstractTest.:320
> null
> [ERROR] Errors:
> [ERROR]
> S3CheckpointSpiStartStopBucketEndpointSelfTest.:32->GridSpiStartStopAbstractTest.:33->GridSpiAbstractTest.:112->GridAbstractTest.:320
> » NoClassDefFound
> [ERROR]
> S3CheckpointSpiStartStopSSEAlgorithmSelfTest.:32->GridSpiStartStopAbstractTest.:33->GridSpiAbstractTest.:112->GridAbstractTest.:320
> » NoClassDefFound
> [ERROR]
> S3CheckpointSpiStartStopSelfTest.:32->GridSpiStartStopAbstractTest.:33->GridSpiAbstractTest.:112->GridAbstractTest.:320
> » NoClassDefFound
> [ERROR] TcpDiscoveryAlbIpFinderSelfTest » InvocationTarget
> [ERROR] TcpDiscoveryElbIpFinderSelfTest » InvocationTarget
> [ERROR] TcpDiscoveryS3IpFinderAwsCredentialsProviderSelfTest »
> InvocationTarget
> [ERROR] TcpDiscoveryS3IpFinderAwsCredentialsSelfTest » InvocationTarget
> [ERROR] TcpDiscoveryS3IpFinderBucketEndpointSelfTest » InvocationTarget
> [ERROR] TcpDiscoveryS3IpFinderKeyPrefixSelfTest » InvocationTarget
> [ERROR] TcpDiscoveryS3IpFinderSSEAlgorithmSelfTest » InvocationTarget
> [ERROR] DummyObjectListingTest » InvocationTarget
> [ERROR] DummyS3ClientTest » InvocationTarget
> [ERROR] AsymmetricKeyEncryptionServiceTest » InvocationTarget
> [ERROR] AwsKmsEncryptionServiceTest » InvocationTarget
> [ERROR] MockEncryptionServiceTest » InvocationTarget
> [ERROR] SymmetricKeyEncryptionServiceTest » InvocationTarget
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-15869) Fix build for aws, gce, azure cloud storages for ignite extensions
Maxim Muzafarov created IGNITE-15869:
Summary: Fix build for aws, gce, azure cloud storages for ignite
extensions
Key: IGNITE-15869
URL: https://issues.apache.org/jira/browse/IGNITE-15869
Project: Ignite
Issue Type: Task
Components: extensions
Reporter: Maxim Muzafarov
Assignee: Maxim Muzafarov
Running tests finishes with an error:
{code}
[ERROR] Failures:
[ERROR]
S3CheckpointSpiConfigSelfTest.:28->GridSpiAbstractConfigTest.:34->GridSpiAbstractTest.:112->GridAbstractTest.:320
null
[ERROR] Errors:
[ERROR]
S3CheckpointSpiStartStopBucketEndpointSelfTest.:32->GridSpiStartStopAbstractTest.:33->GridSpiAbstractTest.:112->GridAbstractTest.:320
» NoClassDefFound
[ERROR]
S3CheckpointSpiStartStopSSEAlgorithmSelfTest.:32->GridSpiStartStopAbstractTest.:33->GridSpiAbstractTest.:112->GridAbstractTest.:320
» NoClassDefFound
[ERROR]
S3CheckpointSpiStartStopSelfTest.:32->GridSpiStartStopAbstractTest.:33->GridSpiAbstractTest.:112->GridAbstractTest.:320
» NoClassDefFound
[ERROR] TcpDiscoveryAlbIpFinderSelfTest » InvocationTarget
[ERROR] TcpDiscoveryElbIpFinderSelfTest » InvocationTarget
[ERROR] TcpDiscoveryS3IpFinderAwsCredentialsProviderSelfTest »
InvocationTarget
[ERROR] TcpDiscoveryS3IpFinderAwsCredentialsSelfTest » InvocationTarget
[ERROR] TcpDiscoveryS3IpFinderBucketEndpointSelfTest » InvocationTarget
[ERROR] TcpDiscoveryS3IpFinderKeyPrefixSelfTest » InvocationTarget
[ERROR] TcpDiscoveryS3IpFinderSSEAlgorithmSelfTest » InvocationTarget
[ERROR] DummyObjectListingTest » InvocationTarget
[ERROR] DummyS3ClientTest » InvocationTarget
[ERROR] AsymmetricKeyEncryptionServiceTest » InvocationTarget
[ERROR] AwsKmsEncryptionServiceTest » InvocationTarget
[ERROR] MockEncryptionServiceTest » InvocationTarget
[ERROR] SymmetricKeyEncryptionServiceTest » InvocationTarget
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15868) Unexpected command: PROBE when Control Center authorisation is enabled
[
https://issues.apache.org/jira/browse/IGNITE-15868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Borunov updated IGNITE-15868:
-
Component/s: (was: rest)
thin client
platforms
> Unexpected command: PROBE when Control Center authorisation is enabled
> --
>
> Key: IGNITE-15868
> URL: https://issues.apache.org/jira/browse/IGNITE-15868
> Project: Ignite
> Issue Type: Bug
> Components: platforms, thin client
>Affects Versions: 2.12
>Reporter: Dmitriy Borunov
>Priority: Major
> Fix For: 2.13
>
>
> Rest API Probe is not working when Control Center authorisation is enabled
> {noformat}
> [2021-11-01T13:35:33,550][ERROR][rest-#125%nebula-node%][GridRestProcessor]
> Runtime error caught during grid runnable execution: GridWorker
> [name=rest-proc-work
> er, igniteInstanceName=nebula-node, finished=false,
> heartbeatTs=1635773733544, hashCode=1386655371, interrupted=false,
> runner=rest-#125%nebula-node%]
> java.lang.AssertionError: Unexpected command: PROBE
> at
> org.apache.ignite.internal.processors.rest.GridRestProcessor.authorize(GridRestProcessor.java:968)
> ~[ignite-core-8.8.10.jar:8.8.10]
> at
> org.apache.ignite.internal.processors.rest.GridRestProcessor.handleRequest(GridRestProcessor.java:286)
> ~[ignite-core-8.8.10.jar:8.8.10]
> at
> org.apache.ignite.internal.processors.rest.GridRestProcessor.access$100(GridRestProcessor.java:108)
> ~[ignite-core-8.8.10.jar:8.8.10]
> at
> org.apache.ignite.internal.processors.rest.GridRestProcessor$2.body(GridRestProcessor.java:183)
> ~[ignite-core-8.8.10.jar:8.8.10]
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
> [ignite-core-8.8.10.jar:8.8.10]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> [?:?]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> [?:?]
> at java.lang.Thread.run(Thread.java:829) [?:?]{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15528) JRaft creates at least 4 threads for every raft group on a leader
[
https://issues.apache.org/jira/browse/IGNITE-15528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Scherbakov updated IGNITE-15528:
---
Ignite Flags: (was: Docs Required,Release Notes Required)
> JRaft creates at least 4 threads for every raft group on a leader
> --
>
> Key: IGNITE-15528
> URL: https://issues.apache.org/jira/browse/IGNITE-15528
> Project: Ignite
> Issue Type: Improvement
>Reporter: Mirza Aliev
>Assignee: Alexey Scherbakov
>Priority: Blocker
> Labels: ignite-3
> Fix For: 3.0.0-alpha4
>
>
> When we create a raft group on a leader, jraft creates at least 4 threads for
> every raft group: one thread for {{electionTimer}}, {{voteTimer}},
> {{stepDownTimer}}, and {{snapshotTimer}}. To be more precise, every timer is
> an instance of {{HashedWheelTimer}}, which creates one thread:
> {code:java}
> private final Worker worker = new Worker();
> ...
> workerThread = threadFactory.newThread(worker);
> {code}
> This fact leads to restrictions on the number of partitions that might be
> created, as far as every partition is associated with a raft group. For
> example, one table with 1024 partitions leads to at least 4096 threads on a
> single node.
> Changing {{HashedWheelTimer}} to {{DefaultTimer}} with shared pool won't make
> any sense, as far as the workload of the shared executor likely will lead to
> instability of cluster because threads are timer threads (election timer, for
> example).
> A possible solution is to implement batched handling of raft groups requests,
> like {{appendEntriesRequest}}. In this approach, timers could be shared by
> raft groups. There is an issue in original JRaft repo with some close ideas
> https://github.com/sofastack/sofa-jraft/issues/672
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-15868) Unexpected command: PROBE when Control Center authorisation is enabled
Dmitriy Borunov created IGNITE-15868:
Summary: Unexpected command: PROBE when Control Center
authorisation is enabled
Key: IGNITE-15868
URL: https://issues.apache.org/jira/browse/IGNITE-15868
Project: Ignite
Issue Type: Bug
Components: rest
Affects Versions: 2.12
Reporter: Dmitriy Borunov
Fix For: 2.13
Rest API Probe is not working when Control Center authorisation is enabled
{noformat}
[2021-11-01T13:35:33,550][ERROR][rest-#125%nebula-node%][GridRestProcessor]
Runtime error caught during grid runnable execution: GridWorker
[name=rest-proc-work
er, igniteInstanceName=nebula-node, finished=false, heartbeatTs=1635773733544,
hashCode=1386655371, interrupted=false, runner=rest-#125%nebula-node%]
java.lang.AssertionError: Unexpected command: PROBE
at
org.apache.ignite.internal.processors.rest.GridRestProcessor.authorize(GridRestProcessor.java:968)
~[ignite-core-8.8.10.jar:8.8.10]
at
org.apache.ignite.internal.processors.rest.GridRestProcessor.handleRequest(GridRestProcessor.java:286)
~[ignite-core-8.8.10.jar:8.8.10]
at
org.apache.ignite.internal.processors.rest.GridRestProcessor.access$100(GridRestProcessor.java:108)
~[ignite-core-8.8.10.jar:8.8.10]
at
org.apache.ignite.internal.processors.rest.GridRestProcessor$2.body(GridRestProcessor.java:183)
~[ignite-core-8.8.10.jar:8.8.10]
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
[ignite-core-8.8.10.jar:8.8.10]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
[?:?]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
[?:?]
at java.lang.Thread.run(Thread.java:829) [?:?]{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14742) Store array component type in binary object
[
https://issues.apache.org/jira/browse/IGNITE-14742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17437885#comment-17437885
]
Nikolay Izhikov commented on IGNITE-14742:
--
The second visa is for {{DFLT_USE_TYPED_ARRAYS=ture}} mode.
{{ServicesClientTest.TestOverloadResolution}} - expected fail. This case will
be fixed in IGNITE-14299
> Store array component type in binary object
> ---
>
> Key: IGNITE-14742
> URL: https://issues.apache.org/jira/browse/IGNITE-14742
> Project: Ignite
> Issue Type: Improvement
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Currently, an array of custom objects can't be retrieved from the cache
> {code:java}
> public class BinaryObjectTest extends GridCommonAbstractTest {
> /** */
> @Test
> public void testArray() throws Exception {
> Ignite ign = startGrid();
> IgniteCache cache =
> ign.createCache("my-cache");
> cache.put(1, new TestClass1[] {new TestClass1(), new TestClass1()});
> TestClass1[] obj = cache.get(1);
> assertEquals(TestClass1[].class, obj.getClass());
> }
> }
> {code}
> The fix should preserve backward compatibility.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14742) Store array component type in binary object
[
https://issues.apache.org/jira/browse/IGNITE-14742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17437883#comment-17437883
]
Ignite TC Bot commented on IGNITE-14742:
{panel:title=Branch: [pull/9490/head] Base: [master] : Possible Blockers
(5)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET (Windows){color} [[tests 1 Exit Code
|https://ci2.ignite.apache.org/viewLog.html?buildId=6195588]]
* exe: ServicesClientTest.TestOverloadResolution - Test has low fail rate in
base branch 0,0% and is not flaky
{color:#d04437}GCE{color} [[tests 0 Exit Code
|https://ci2.ignite.apache.org/viewLog.html?buildId=6195560]]
{color:#d04437}AWS{color} [[tests 0 Exit Code
|https://ci2.ignite.apache.org/viewLog.html?buildId=6195520]]
{color:#d04437}Platform .NET (Core Linux){color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=6195587]]
* dll: ServicesClientTest.TestOverloadResolution - Test has low fail rate in
base branch 0,0% and is not flaky
{panel}
{panel:title=Branch: [pull/9490/head] Base: [master] : New Tests
(2720)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Cache 9{color} [[tests
360|https://ci2.ignite.apache.org/viewLog.html?buildId=6195533]]
* {color:#013220}IgniteCacheTestSuite9:
GridCacheDataTypesCoverageTest.testObjectBasedOnPrimitivesDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=2, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=FULL_SYNC, persistenceEnabled=false,
useTypedArrays=true] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite9:
GridCacheDataTypesCoverageTest.testShortDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=2, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=FULL_SYNC, persistenceEnabled=false,
useTypedArrays=true] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite9:
GridCacheDataTypesCoverageTest.testCharacterDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=2, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=FULL_SYNC, persistenceEnabled=false,
useTypedArrays=true] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite9:
GridCacheDataTypesCoverageTest.testSetDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=2, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=FULL_SYNC, persistenceEnabled=false,
useTypedArrays=true] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite9:
GridCacheDataTypesCoverageTest.testIntegerDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=2, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=FULL_SYNC, persistenceEnabled=false,
useTypedArrays=true] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite9:
GridCacheDataTypesCoverageTest.testObjectBasedOnPrimitivesAndCollectionsDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=2, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=FULL_SYNC, persistenceEnabled=false,
useTypedArrays=true] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite9:
GridCacheDataTypesCoverageTest.testSqlDateDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=2, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=FULL_SYNC, persistenceEnabled=false,
useTypedArrays=true] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite9:
GridCacheDataTypesCoverageTest.testLocalTimeDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=2, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=FULL_SYNC, persistenceEnabled=false,
useTypedArrays=true] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite9:
GridCacheDataTypesCoverageTest.testLocalDateTimeDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=2, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=FULL_SYNC, persistenceEnabled=false,
useTypedArrays=true] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite9:
GridCacheDataTypesCoverageTest.testDoubleDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=2, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=FULL_SYNC, persistenceEnabled=false,
useTypedArrays=true] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite9:
GridCacheDataTypesCoverageTest.testStringDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=2, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=FULL_SYNC, persistenceEnabled=false,
useTypedArrays=true] - PASSED{color}
... and 349 new tests
{color:#8b}Queries 2{color} [[tests
150|https://ci2.ignite.apache.org/viewLog.html?buildId=6195590]]
* {color:#013220}IgniteBinaryCacheQueryTestSuite2:
SqlDataTypesCoverageTests.testDecimalDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED,
[jira] [Assigned] (IGNITE-15150) Fix javadoc in Cli module.
[
https://issues.apache.org/jira/browse/IGNITE-15150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin reassigned IGNITE-15150:
Assignee: Vyacheslav Koptilin
> Fix javadoc in Cli module.
> --
>
> Key: IGNITE-15150
> URL: https://issues.apache.org/jira/browse/IGNITE-15150
> Project: Ignite
> Issue Type: Bug
>Reporter: Andrey Mashenkov
>Assignee: Vyacheslav Koptilin
>Priority: Major
> Labels: ignite-3
>
> Let's fix Javadoc styles regarding the policy.
> Startpoint is to remove modules from excludes
> {noformat}
> ./check-rules/checkstyle-disabled-modules.xml
> {noformat}
> and run
> {code:java}
> mvn clean checkstyle:checkstyle-aggregate -P javadoc-public-api
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-15151) Fix javadoc in Examples module.
[
https://issues.apache.org/jira/browse/IGNITE-15151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin reassigned IGNITE-15151:
Assignee: Vyacheslav Koptilin
> Fix javadoc in Examples module.
> ---
>
> Key: IGNITE-15151
> URL: https://issues.apache.org/jira/browse/IGNITE-15151
> Project: Ignite
> Issue Type: Bug
>Reporter: Andrey Mashenkov
>Assignee: Vyacheslav Koptilin
>Priority: Major
> Labels: ignite-3
>
> Let's fix Javadoc styles regarding the policy.
> Startpoint is to remove modules from excludes
> {noformat}
> ./check-rules/checkstyle-disabled-modules.xml
> {noformat}
> and run
> {code:java}
> mvn clean checkstyle:checkstyle-aggregate -P javadoc-public-api
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-15462) Calcite. Replace usages of map of int to IntMap where possible
[
https://issues.apache.org/jira/browse/IGNITE-15462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17437816#comment-17437816
]
Yury Gerzhedovich commented on IGNITE-15462:
[~vermakov] LGTM
> Calcite. Replace usages of map of int to IntMap where possible
> --
>
> Key: IGNITE-15462
> URL: https://issues.apache.org/jira/browse/IGNITE-15462
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Konstantin Orlov
>Assignee: Vladimir Ermakov
>Priority: Major
> Labels: calcite, calcite2-required, calcite3-required, ignite-3,
> tech-debt
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> Currently there is a number of {{Map}} usages in
> {{ignite-calcite}} module. Better to replace them with more optimal
> {{org.apache.ignite.internal.util.collection.IntMap}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-15855) BinaryObjectBuilder builds invalid object in case the original object contains several collection or reference fields
[
https://issues.apache.org/jira/browse/IGNITE-15855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17437243#comment-17437243
]
Taras Ledkov edited comment on IGNITE-15855 at 11/3/21, 8:15 AM:
-
[~amashenkov], [~jooger], please review the patch.
was (Author: tledkov-gridgain):
[~amashenkov], please review the patch.
> BinaryObjectBuilder builds invalid object in case the original object
> contains several collection or reference fields
> -
>
> Key: IGNITE-15855
> URL: https://issues.apache.org/jira/browse/IGNITE-15855
> Project: Ignite
> Issue Type: Bug
> Components: binary
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
>Priority: Major
> Fix For: 2.13
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Looks like the issue is partially related to the IGNITE-14610
> *Root cause:*
> Fill the {{BinaryBuilderReader#objMap}} with invalid offsets (with offset of
> the next field).
> The reader is used to write binary object when an object is partially changed
> by builder.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-15855) BinaryObjectBuilder builds invalid object in case the original object contains several collection or reference fields
[
https://issues.apache.org/jira/browse/IGNITE-15855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17437814#comment-17437814
]
Yury Gerzhedovich commented on IGNITE-15855:
[~tledkov-gridgain], LGTM. Thanks!
> BinaryObjectBuilder builds invalid object in case the original object
> contains several collection or reference fields
> -
>
> Key: IGNITE-15855
> URL: https://issues.apache.org/jira/browse/IGNITE-15855
> Project: Ignite
> Issue Type: Bug
> Components: binary
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
>Priority: Major
> Fix For: 2.13
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Looks like the issue is partially related to the IGNITE-14610
> *Root cause:*
> Fill the {{BinaryBuilderReader#objMap}} with invalid offsets (with offset of
> the next field).
> The reader is used to write binary object when an object is partially changed
> by builder.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14742) Store array component type in binary object
[
https://issues.apache.org/jira/browse/IGNITE-14742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17437791#comment-17437791
]
Nikolay Izhikov commented on IGNITE-14742:
--
The visa above is for {{DFLT_USE_TYPED_ARRAYS=false}} mode.
Failured unrelated.
> GCE [tests 0 Exit Code
> AWS [tests 0 Exit Code
Modules moved to extensions and don't exists in ignite repo anymore.
> Platform .NET (Windows) [tests 0 Exit Code
https://ci2.ignite.apache.org/buildConfiguration/IgniteTests24Java8_PlatformNetWindows/6195507
Three failures of flacky tests.
> Store array component type in binary object
> ---
>
> Key: IGNITE-14742
> URL: https://issues.apache.org/jira/browse/IGNITE-14742
> Project: Ignite
> Issue Type: Improvement
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Currently, an array of custom objects can't be retrieved from the cache
> {code:java}
> public class BinaryObjectTest extends GridCommonAbstractTest {
> /** */
> @Test
> public void testArray() throws Exception {
> Ignite ign = startGrid();
> IgniteCache cache =
> ign.createCache("my-cache");
> cache.put(1, new TestClass1[] {new TestClass1(), new TestClass1()});
> TestClass1[] obj = cache.get(1);
> assertEquals(TestClass1[].class, obj.getClass());
> }
> }
> {code}
> The fix should preserve backward compatibility.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14742) Store array component type in binary object
[
https://issues.apache.org/jira/browse/IGNITE-14742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17437790#comment-17437790
]
Ignite TC Bot commented on IGNITE-14742:
{panel:title=Branch: [pull/9490/head] Base: [master] : Possible Blockers
(3)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET (Windows){color} [[tests 0 Exit Code
|https://ci2.ignite.apache.org/viewLog.html?buildId=6195507]]
{color:#d04437}GCE{color} [[tests 0 Exit Code
|https://ci2.ignite.apache.org/viewLog.html?buildId=6194451]]
{color:#d04437}AWS{color} [[tests 0 Exit Code
|https://ci2.ignite.apache.org/viewLog.html?buildId=6194411]]
{panel}
{panel:title=Branch: [pull/9490/head] Base: [master] : New Tests
(2716)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Cache 9{color} [[tests
360|https://ci2.ignite.apache.org/viewLog.html?buildId=6194424]]
* {color:#013220}IgniteCacheTestSuite9:
GridCacheDataTypesCoverageTest.testLocalTimeDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=2, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=FULL_ASYNC, persistenceEnabled=false,
useTypedArrays=false] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite9:
GridCacheDataTypesCoverageTest.testLocalDateTimeDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=2, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=FULL_ASYNC, persistenceEnabled=false,
useTypedArrays=false] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite9:
GridCacheDataTypesCoverageTest.testDoubleDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=2, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=FULL_ASYNC, persistenceEnabled=false,
useTypedArrays=false] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite9:
GridCacheDataTypesCoverageTest.testStringDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=2, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=FULL_ASYNC, persistenceEnabled=false,
useTypedArrays=false] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite9:
GridCacheDataTypesCoverageTest.testListDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=2, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=FULL_ASYNC, persistenceEnabled=false,
useTypedArrays=false] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite9:
GridCacheDataTypesCoverageTest.testObjectArrayDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=2, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=FULL_ASYNC, persistenceEnabled=false,
useTypedArrays=false] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite9:
GridCacheDataTypesCoverageTest.testBigDecimalDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=2, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=FULL_ASYNC, persistenceEnabled=false,
useTypedArrays=false] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite9:
GridCacheDataTypesCoverageTest.testCalendarDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=2, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=FULL_ASYNC, persistenceEnabled=false,
useTypedArrays=false] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite9:
GridCacheDataTypesCoverageTest.testLongDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=2, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=FULL_ASYNC, persistenceEnabled=false,
useTypedArrays=false] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite9:
GridCacheDataTypesCoverageTest.testBigIntegerDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=2, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=FULL_ASYNC, persistenceEnabled=false,
useTypedArrays=false] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite9:
GridCacheDataTypesCoverageTest.testByteDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=2, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=FULL_ASYNC, persistenceEnabled=false,
useTypedArrays=false] - PASSED{color}
... and 349 new tests
{color:#8b}Queries 2{color} [[tests
150|https://ci2.ignite.apache.org/viewLog.html?buildId=6194481]]
* {color:#013220}IgniteBinaryCacheQueryTestSuite2:
SqlDataTypesCoverageTests.testVarcharDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=EternalExpiryPolicy, backups=2,
evictionFactory=null, onheapCacheEnabled=false, writeSyncMode=FULL_SYNC,
persistenceEnabled=false, useTypedArrays=false] - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite2:
SqlDataTypesCoverageTests.testDecimalDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=EternalExpiryPolicy, backups=2,
[jira] [Closed] (IGNITE-15698) SQL query may hangs where table is dropped concurrently
[
https://issues.apache.org/jira/browse/IGNITE-15698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Belyak closed IGNITE-15698.
-
Ignite Flags: (was: Docs Required,Release Notes Required)
> SQL query may hangs where table is dropped concurrently
>
>
> Key: IGNITE-15698
> URL: https://issues.apache.org/jira/browse/IGNITE-15698
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Alexander Belyak
>Assignee: Alexander Belyak
>Priority: Major
> Fix For: 2.13
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> SQL query may hangs where table is dropped concurrently.
> *Root cause:*
> Unhanded exception at the query thread at:
> {{GridMapQueryExecutor#onQueryRequest}} when a cache is destroyed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-15729) RecordViewExample fails with two remote nodes
[
https://issues.apache.org/jira/browse/IGNITE-15729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17435945#comment-17435945
]
Sergey Uttsel edited comment on IGNITE-15729 at 11/3/21, 7:40 AM:
--
Need to enable the IgniteCliRunnerTest.runnerArgsSmokeTest test when the bug
will be fixed (https://issues.apache.org/jira/browse/IGNITE-15060)
was (Author: sergey uttsel):
Need to enable the IgniteCliRunnerTest.runnerArgsSmokeTest test when the bug
will be fixed.
> RecordViewExample fails with two remote nodes
> -
>
> Key: IGNITE-15729
> URL: https://issues.apache.org/jira/browse/IGNITE-15729
> Project: Ignite
> Issue Type: Bug
> Components: examples
>Affects Versions: 3.0.0-alpha3
>Reporter: Valentin Kulichenko
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha4
>
>
> To reproduce:
> # Start *two* nodes using the CLI tool.
> # Run the {{RecordViewExample}} (need to check other examples as well).
> # Observe the exception shown below.
> {noformat}
> Exception in thread "main" java.util.concurrent.CompletionException: class
> org.apache.ignite.client.IgniteClientException: class
> org.apache.ignite.client.IgniteClientException: class
> org.apache.ignite.raft.jraft.rpc.impl.RaftException: ENOENT:No nodes in group
> 1-40f121ca-81e4-4929-8ad3-24f5742c81af_part_6
> at
> java.base/java.util.concurrent.CompletableFuture.encodeRelay(CompletableFuture.java:367)
> at
> java.base/java.util.concurrent.CompletableFuture.completeRelay(CompletableFuture.java:376)
> at
> java.base/java.util.concurrent.CompletableFuture$UniRelay.tryFire(CompletableFuture.java:1019)
> at
> java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
> at
> java.base/java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2088)
> at
> org.apache.ignite.internal.client.ReliableChannel.lambda$handleServiceAsync$3(ReliableChannel.java:213)
> at
> java.base/java.util.concurrent.CompletableFuture.uniHandle(CompletableFuture.java:930)
> at
> java.base/java.util.concurrent.CompletableFuture$UniHandle.tryFire(CompletableFuture.java:907)
> at
> java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
> at
> java.base/java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2088)
> at
> org.apache.ignite.internal.client.TcpClientChannel.processNextMessage(TcpClientChannel.java:260)
> at
> org.apache.ignite.internal.client.TcpClientChannel.onMessage(TcpClientChannel.java:109)
> at
> org.apache.ignite.internal.client.io.netty.NettyClientConnection.onMessage(NettyClientConnection.java:85)
> at
> org.apache.ignite.internal.client.io.netty.NettyClientMessageHandler.channelRead(NettyClientMessageHandler.java:33)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)
> at
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357)
> at
> io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:324)
> at
> io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:296)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)
> at
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357)
> at
> io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1410)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)
> at
> io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:919)
> at
> io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:166)
> at
> io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:719)
> at
> io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:655)
> at
> io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:581)
> at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:493)
> at
>
[jira] [Commented] (IGNITE-15733) Eventually failure of baseline registration.
[
https://issues.apache.org/jira/browse/IGNITE-15733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17437758#comment-17437758
]
Ignite TC Bot commented on IGNITE-15733:
{panel:title=Branch: [pull/9527/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9527/head] Base: [master] : New Tests
(12)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}ZooKeeper (Discovery) 4{color} [[tests
10|https://ci.ignite.apache.org/viewLog.html?buildId=6251057]]
* {color:#013220}ZookeeperDiscoverySpiTestSuite4:
DistributedMetaStoragePersistentTest.testStoreLagOnOneNode - PASSED{color}
* {color:#013220}ZookeeperDiscoverySpiTestSuite4:
DistributedMetaStoragePersistentTest.changeTagWithNodeCrash - PASSED{color}
* {color:#013220}ZookeeperDiscoverySpiTestSuite4:
IgniteClusterIdTagTest.testTagChangedEvent - PASSED{color}
* {color:#013220}ZookeeperDiscoverySpiTestSuite4:
IgniteClusterIdTagTest.testInMemoryClusterIdWithClientReconnect - PASSED{color}
* {color:#013220}ZookeeperDiscoverySpiTestSuite4:
IgniteClusterIdTagTest.testInMemoryClusterId - PASSED{color}
* {color:#013220}ZookeeperDiscoverySpiTestSuite4:
IgniteClusterIdTagTest.testPersistentClusterTag - PASSED{color}
* {color:#013220}ZookeeperDiscoverySpiTestSuite4:
IgniteClusterIdTagTest.testInMemoryClusterTag - PASSED{color}
* {color:#013220}ZookeeperDiscoverySpiTestSuite4:
IgniteClusterIdTagTest.testPersistentClusterId - PASSED{color}
* {color:#013220}ZookeeperDiscoverySpiTestSuite4:
IgniteClusterIdTagTest.testChangeTagExceptions - PASSED{color}
* {color:#013220}ZookeeperDiscoverySpiTestSuite4:
IgniteClusterIdTagTest.testTagChangedEventMultinodeWithRemoteFilter -
PASSED{color}
{color:#8b}PDS 1{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=6250825]]
* {color:#013220}IgnitePdsTestSuite:
DistributedMetaStoragePersistentTest.testStoreLagOnOneNode - PASSED{color}
* {color:#013220}IgnitePdsTestSuite:
DistributedMetaStoragePersistentTest.changeTagWithNodeCrash - PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6250853buildTypeId=IgniteTests24Java8_RunAll]
> Eventually failure of baseline registration.
>
>
> Key: IGNITE-15733
> URL: https://issues.apache.org/jira/browse/IGNITE-15733
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.11
>Reporter: Evgeny Stanilovsky
>Assignee: Evgeny Stanilovsky
>Priority: Major
> Attachments: _Community_Edition_Cache_9_18998_cut.log
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> All info can be found in attached log:
> briefly: Cluster of 2 nodes with persistence, sequentially start nodes,
> activate, stop nodes using org.apache.ignite.Ignite#close, start nodes,
> activate:
> expected :
> 1 node : Cluster ID and tag has been read from metastorage: null
> 2 node : Cluster ID and tag has been read from metastorage: null
> stop
> start
> 1 node: Cluster ID and tag has been read from metastorage: ClusterIdAndTag
> [id=some_id, tag=some_tag]
> 2 node: Cluster ID and tag has been read from metastorage: ClusterIdAndTag
> [id=some_id, tag=some_tag]
> but obtained (check attach)
>
> 1 node : Cluster ID and tag has been read from metastorage: null
> 2 node : Cluster ID and tag has been read from metastorage: null
> stop
> start
> 1 node: Cluster ID and tag has been read from metastorage: null
> 2 node: Cluster ID and tag has been read from metastorage: ClusterIdAndTag
> [id=some_id, tag=some_tag]
> and as a result :
> _Joining node has conflicting distributed metastorage data_
> [^_Community_Edition_Cache_9_18998_cut.log]
> this test MetricsConfigurationTest.testNodeRestart [1] is flaky
> [1][https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_Cache9/6220901?buildTab=tests=MetricsConfigurationTes=tests=passed=org.apache.ignite.testsuites.IgniteCacheTestSuite9%3A+=org.apache.ignite.internal.metric=build%3A%28id%3A6220901%29%2Cid%3A576406]
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-15841) Ignite node starts with a default configuration in case of the user-provided configuration cannot be properly parsed
[
https://issues.apache.org/jira/browse/IGNITE-15841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17437754#comment-17437754
]
Sergey Uttsel commented on IGNITE-15841:
https://github.com/apache/ignite-3/pull/423
> Ignite node starts with a default configuration in case of the user-provided
> configuration cannot be properly parsed
>
>
> Key: IGNITE-15841
> URL: https://issues.apache.org/jira/browse/IGNITE-15841
> Project: Ignite
> Issue Type: Bug
>Reporter: Vyacheslav Koptilin
>Assignee: Sergey Uttsel
>Priority: Major
> Labels: ignite-3
>
> In case of the user-provided configuration is broken (for example, it is an
> incorrect JSON file), Ignite node still tries to start with a default
> configuration.
> {noformat}
> Unable to read user specific configuration, default configuration will be
> used: ...{noformat}
> It does not seem this behavior is correct. The implementation should throw an
> exception with an appropriate message.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
