[jira] [Commented] (IGNITE-13112) The current security context should be obtained using the IgniteSecurity interface only.
[
https://issues.apache.org/jira/browse/IGNITE-13112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17239088#comment-17239088
]
Ignite TC Bot commented on IGNITE-13112:
{panel:title=Branch: [pull/8038/head] Base: [master] : Possible Blockers
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET (Inspections)*{color} [[tests 0 Failure on metric
|https://ci.ignite.apache.org/viewLog.html?buildId=5757897]]
{panel}
{panel:title=Branch: [pull/8038/head] Base: [master] : New Tests
(344)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Security{color} [[tests
344|https://ci.ignite.apache.org/viewLog.html?buildId=5755955]]
* {color:#013220}SecurityTestSuite:
CacheEventsTest.testCacheEvent[atomicMode=ATOMIC, expLogin=server, evtType=63,
op=GET_AND_PUT_ASYNC] - PASSED{color}
* {color:#013220}SecurityTestSuite:
CacheEventsTest.testCacheEvent[atomicMode=TRANSACTIONAL, expLogin=client,
evtType=64, op=GET_AND_PUT_IF_ABSENT] - PASSED{color}
* {color:#013220}SecurityTestSuite:
CacheEventsTest.testCacheEvent[atomicMode=TRANSACTIONAL, expLogin=server,
evtType=64, op=GET_AND_PUT_IF_ABSENT] - PASSED{color}
* {color:#013220}SecurityTestSuite:
CacheEventsTest.testCacheEvent[atomicMode=TRANSACTIONAL, expLogin=rest,
evtType=64, op=GET_AND_PUT_IF_ABSENT] - PASSED{color}
* {color:#013220}SecurityTestSuite:
CacheEventsTest.testCacheEvent[atomicMode=TRANSACTIONAL, expLogin=client,
evtType=63, op=GET_AND_PUT_IF_ABSENT_PUT_CASE] - PASSED{color}
* {color:#013220}SecurityTestSuite:
CacheEventsTest.testCacheEvent[atomicMode=ATOMIC, expLogin=client, evtType=63,
op=GET_AND_PUT_IF_ABSENT_PUT_CASE] - PASSED{color}
* {color:#013220}SecurityTestSuite:
CacheEventsTest.testCacheEvent[atomicMode=TRANSACTIONAL, expLogin=server,
evtType=63, op=GET_AND_PUT_IF_ABSENT_PUT_CASE] - PASSED{color}
* {color:#013220}SecurityTestSuite:
CacheEventsTest.testCacheEvent[atomicMode=ATOMIC, expLogin=server, evtType=63,
op=GET_AND_PUT_IF_ABSENT_PUT_CASE] - PASSED{color}
* {color:#013220}SecurityTestSuite:
CacheEventsTest.testCacheEvent[atomicMode=ATOMIC, expLogin=thin, evtType=63,
op=GET_AND_PUT] - PASSED{color}
* {color:#013220}SecurityTestSuite:
CacheEventsTest.testCacheEvent[atomicMode=TRANSACTIONAL, expLogin=rest,
evtType=63, op=GET_AND_PUT] - PASSED{color}
* {color:#013220}SecurityTestSuite:
CacheEventsTest.testCacheEvent[atomicMode=ATOMIC, expLogin=rest, evtType=63,
op=GET_AND_PUT] - PASSED{color}
... and 333 new tests
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5754228buildTypeId=IgniteTests24Java8_RunAll]
> The current security context should be obtained using the IgniteSecurity
> interface only.
>
>
> Key: IGNITE-13112
> URL: https://issues.apache.org/jira/browse/IGNITE-13112
> Project: Ignite
> Issue Type: Bug
> Components: cache, security
>Affects Versions: 2.8.1
>Reporter: Denis Garus
>Assignee: Denis Garus
>Priority: Major
> Labels: iep-41
> Fix For: 2.10
>
> Time Spent: 4h 40m
> Remaining Estimate: 0h
>
> For getting the current security context, we have to use the IgniteSecurity
> interface only.
> We need to get rid of all other ways to transfer a security subject id.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13765) Incorrect work of predicates (< and >) in where clause with compound primary key.
[ https://issues.apache.org/jira/browse/IGNITE-13765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kazakov updated IGNITE-13765: -- Description: The combination of these two conditions always gives an empty selection, but the result must not be empty. * Compound primary key (2 or more columns) * In select query in where clause use condition on every pk-column only once and one of this conditions should be < or > The reproducer is attached. was: The combination of these two conditions results in an empty selection always, but the result must not be empty. * Compound primary key (2 or more columns) * In select query in where clause use condition on every pk-column only once and one of this conditions should be < or > The reproducer is attached. > Incorrect work of predicates (< and >) in where clause with compound primary > key. > - > > Key: IGNITE-13765 > URL: https://issues.apache.org/jira/browse/IGNITE-13765 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.9, 2.8.1 >Reporter: Ilya Kazakov >Priority: Major > Attachments: CompoundPkPredicateTest.java > > > The combination of these two conditions always gives an empty selection, but > the result must not be empty. > * Compound primary key (2 or more columns) > * In select query in where clause use condition on every pk-column only once > and one of this conditions should be < or > > The reproducer is attached. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13765) Incorrect work of predicates (< and >) in where clause with compound primary key.
[ https://issues.apache.org/jira/browse/IGNITE-13765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kazakov updated IGNITE-13765: -- Description: The combination of these two conditions results in an empty selection always, but the result must not be empty. * Compound primary key (2 or more columns) * In select query in where clause use condition on every pk-column only once and one of this conditions should be < or > The reproducer is attached. was: Еhe combination of these two conditions results in an empty selection always, but the result must not be empty. * Compound primary key (2 or more columns) * In select query in where clause use condition on every pk-column only once and one of this conditions should be < or > The reproducer is attached. > Incorrect work of predicates (< and >) in where clause with compound primary > key. > - > > Key: IGNITE-13765 > URL: https://issues.apache.org/jira/browse/IGNITE-13765 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.9, 2.8.1 >Reporter: Ilya Kazakov >Priority: Major > Attachments: CompoundPkPredicateTest.java > > > The combination of these two conditions results in an empty selection always, > but the result must not be empty. > * Compound primary key (2 or more columns) > * In select query in where clause use condition on every pk-column only once > and one of this conditions should be < or > > The reproducer is attached. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13765) Incorrect work of predicates (< and >) in where clause with compound primary key.
Ilya Kazakov created IGNITE-13765: - Summary: Incorrect work of predicates (< and >) in where clause with compound primary key. Key: IGNITE-13765 URL: https://issues.apache.org/jira/browse/IGNITE-13765 Project: Ignite Issue Type: Bug Components: sql Affects Versions: 2.8.1, 2.9 Reporter: Ilya Kazakov Attachments: CompoundPkPredicateTest.java Еhe combination of these two conditions results in an empty selection always, but the result must not be empty. * Compound primary key (2 or more columns) * In select query in where clause use condition on every pk-column only once and one of this conditions should be < or > The reproducer is attached. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13764) NodeJS Thin Client cannot handle multiple concurrent requests
Simon Liang created IGNITE-13764: Summary: NodeJS Thin Client cannot handle multiple concurrent requests Key: IGNITE-13764 URL: https://issues.apache.org/jira/browse/IGNITE-13764 Project: Ignite Issue Type: Bug Components: thin client Affects Versions: 2.9 Reporter: Simon Liang When we are using the NodeJS Thin Client, we found that whenever we have multiple requests in-flight, the response ID came out to be mismatched. Upon investigating, I saw that our current response handling is using a blocking loop whenever one data packet arrives, and the subsequent data packet triggers the loop again, causing the response ID mismatch issue. I have a fix ready on a fork at [https://github.com/lhr0909/ignite/pull/1] and I would like to see if there is a chance to merge in. I use RxJS to handle the packets in full asynchronous fashion. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13731) High contention on GridCachePartitionExchangeManager.ExchangeFutureSet#values.
[
https://issues.apache.org/jira/browse/IGNITE-13731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-13731:
-
Fix Version/s: 2.10
> High contention on GridCachePartitionExchangeManager.ExchangeFutureSet#values.
> --
>
> Key: IGNITE-13731
> URL: https://issues.apache.org/jira/browse/IGNITE-13731
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.9
>Reporter: Sergey Uttsel
>Assignee: Sergey Uttsel
>Priority: Major
> Fix For: 2.10
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Thread dump highlights high contention ~ 4 min on sync block :
> GridCachePartitionExchangeManager.ExchangeFutureSet#values
>
> {code:java}
> Stack Trace Count Duration
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeFutureSet.values()
> line: 3411 546 284 964 247 989
>
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.exchangeFutures()
> line: 1006 546 284 964 247 989
>
> org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedLockFuture.map()
> line: 780 546 284 964 247 989
>
> org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedCache.lockAllAsync(Collection,
> long, IgniteTxLocalEx, boolean, boolean, boolean, TransactionIsolation,
> long, long) line: 657 546 284 964 247 989
>
> org.apache.ignite.internal.processors.cache.distributed.GridDistributedCacheAdapter.txLockAsync(Collection,
> long, IgniteTxLocalEx, boolean, boolean, TransactionIsolation, boolean,
> long, long) line: 109 546 284 964 247 989
>
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.putAsync0(GridCacheContext,
> AffinityTopologyVersion, Object, Object, EntryProcessor, Object[], boolean,
> CacheEntryPredicate) line: 602 541 282 015 678 231
>
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.putAsync(GridCacheContext,
> AffinityTopologyVersion, Object, Object, boolean, CacheEntryPredicate) line:
> 415 541 282 015 678 231
>
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$22.op(GridNearTxLocal)
> line: 2451 386 211 315 142 845
>
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$22.op(GridNearTxLocal)
> line: 2449 386 211 315 142 845
>
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.syncOp(GridCacheAdapter$SyncOp)
> line: 4230 386 211 315 142 845
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.put0(Object,
> Object, CacheEntryPredicate) line: 2449 386 211 315 142 845
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(Object,
> Object, CacheEntryPredicate) line: 2430 386 211 315 142 845
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.replace(Object,
> Object) line: 2833 386 211 315 142 845
>
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.replace(Object,
> Object) line: 1506 386 211 315 142 845
>
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.replace(Object,
> Object) line: 978 386 211 315 14
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-13763) C++: Add a configuration property allowing thin CPP client to limit connection count.
Vladimir Pligin created IGNITE-13763: Summary: C++: Add a configuration property allowing thin CPP client to limit connection count. Key: IGNITE-13763 URL: https://issues.apache.org/jira/browse/IGNITE-13763 Project: Ignite Issue Type: Improvement Components: thin client Affects Versions: 2.9 Reporter: Vladimir Pligin It seems that C++ thin client behaves differently from Java client. Assuming that partition awareness is disabled we still have connection attempts to all servers from the list. It would be great to have a property to limit it somehow. It could potentially cause performance issues in some cases involving big number of clients per server. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13760) .NET: GetAffinity fails with NullPointerException on client node
[
https://issues.apache.org/jira/browse/IGNITE-13760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-13760:
Description:
* Given there are Ignite.NET server and client nodes
* When the server node creates a cache and then the client node immediately
gets affinity for the cache
* Then getting affinity fails with NullPointerException
{code:c#}
IgniteConfiguration IgniteCfg(bool clientMode = false) => new
IgniteConfiguration
{
ClientMode = clientMode,
IgniteInstanceName = Guid.NewGuid().ToString(),
DiscoverySpi = new TcpDiscoverySpi
{
IpFinder = new TcpDiscoveryStaticIpFinder
{
Endpoints = new[] { "127.0.0.1:47500" }
}
}
};
using var igniteSrv = Ignition.Start(IgniteCfg());
using var igniteClient = Ignition.Start(IgniteCfg(true));
var cache1 = igniteSrv.GetOrCreateCache("cache1");
igniteClient.GetAffinity("cache1");
{code}
The igniteClient.GetAffinity fails with this exception:
{code}
Apache.Ignite.Core.Common.IgniteException
HResult=0x80131500
Message=Java exception occurred [class=java.lang.NullPointerException,
message=]
Source=Apache.Ignite.Core
StackTrace:
at Apache.Ignite.Core.Impl.PlatformJniTarget.InStreamOutObject(Int32 type,
Action`1 writeAction)
at Apache.Ignite.Core.Impl.PlatformTargetAdapter.DoOutOpObject(Int32 type,
Action`1 action)
at
Apache.Ignite.Core.Impl.Ignite.Apache.Ignite.Core.Impl.IIgniteInternal.GetAffinity(String
cacheName)
at Apache.Ignite.Core.Impl.Ignite.GetAffinity(String cacheName)
at DotNet.Sandbox.Program.Main(String[] args) in
C:\Dev\tmp\DotNet.Sandbox\Program.cs:line 32
This exception was originally thrown at this call stack:
Apache.Ignite.Core.Impl.Unmanaged.Jni.Env.ExceptionCheck()
Apache.Ignite.Core.Impl.Unmanaged.Jni.Env.CallObjectMethod(Apache.Ignite.Core.Impl.Unmanaged.Jni.GlobalRef,
System.IntPtr, long*)
Apache.Ignite.Core.Impl.Unmanaged.UnmanagedUtils.TargetInStreamOutObject(Apache.Ignite.Core.Impl.Unmanaged.Jni.GlobalRef,
int, long)
Apache.Ignite.Core.Impl.PlatformJniTarget.InStreamOutObject(int,
System.Action)
Inner Exception 1:
JavaException: java.lang.NullPointerException
at
org.apache.ignite.internal.processors.platform.cache.affinity.PlatformAffinity.(PlatformAffinity.java:125)
at
org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.processInStreamOutObject(PlatformProcessorImpl.java:640)
at
org.apache.ignite.internal.processors.platform.PlatformTargetProxyImpl.inStreamOutObject(PlatformTargetProxyImpl.java:79)
{code}
h1. Workaround
Add {{GetCache}} call before {{GetAffinity}}:
{code:c#}
...
var cache1 = igniteSrv.GetOrCreateCache("cache1");
igniteClient.GetCache("cache1");
igniteClient.GetAffinity("cache1");
{code}
was:
* Given there are Ignite.NET server and client nodes
* When the server node creates a cache and then the client node immediately
gets affinity for the cache
* Then getting affinity fails with NullPointerException
{code:c#}
IgniteConfiguration IgniteCfg(bool clientMode = false) => new
IgniteConfiguration
{
ClientMode = clientMode,
IgniteInstanceName = Guid.NewGuid().ToString(),
DiscoverySpi = new TcpDiscoverySpi
{
IpFinder = new TcpDiscoveryStaticIpFinder
{
Endpoints = new[] { "127.0.0.1:47500" }
}
}
};
using var igniteSrv = Ignition.Start(IgniteCfg());
using var igniteClient = Ignition.Start(IgniteCfg(true));
var cache1 = igniteSrv.GetOrCreateCache("cache1");
igniteClient.GetAffinity("cache1");
{code}
The igniteClient.GetAffinity fails with this exception:
{code}
Apache.Ignite.Core.Common.IgniteException
HResult=0x80131500
Message=Java exception occurred [class=java.lang.NullPointerException,
message=]
Source=Apache.Ignite.Core
StackTrace:
at Apache.Ignite.Core.Impl.PlatformJniTarget.InStreamOutObject(Int32 type,
Action`1 writeAction)
at Apache.Ignite.Core.Impl.PlatformTargetAdapter.DoOutOpObject(Int32 type,
Action`1 action)
at
Apache.Ignite.Core.Impl.Ignite.Apache.Ignite.Core.Impl.IIgniteInternal.GetAffinity(String
cacheName)
at Apache.Ignite.Core.Impl.Ignite.GetAffinity(String cacheName)
at DotNet.Sandbox.Program.Main(String[] args) in
C:\Dev\tmp\DotNet.Sandbox\Program.cs:line 32
This exception was originally thrown at this call stack:
Apache.Ignite.Core.Impl.Unmanaged.Jni.Env.ExceptionCheck()
Apache.Ignite.Core.Impl.Unmanaged.Jni.Env.CallObjectMethod(Apache.Ignite.Core.Impl.Unmanaged.Jni.GlobalRef,
System.IntPtr, long*)
Apache.Ignite.Core.Impl.Unmanaged.UnmanagedUtils.TargetInStreamOutObject(Apache.Ignite.Core.Impl.Unmanaged.Jni.GlobalRef,
int, long)
Apache.Ignite.Core.Impl.PlatformJniTarget.InStreamOutObject(int,
System.Action)
Inner Exception 1:
JavaException: java.lang.NullPointerException
at
[jira] [Updated] (IGNITE-13760) .NET: GetAffinity fails with NullPointerException on client node
[
https://issues.apache.org/jira/browse/IGNITE-13760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-13760:
Summary: .NET: GetAffinity fails with NullPointerException on client node
(was: Ignite.NET GetAffinity fails with NullPointerException)
> .NET: GetAffinity fails with NullPointerException on client node
>
>
> Key: IGNITE-13760
> URL: https://issues.apache.org/jira/browse/IGNITE-13760
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.9
>Reporter: Alexey Kukushkin
>Assignee: Pavel Tupitsyn
>Priority: Major
> Fix For: 2.9.1
>
>
> * Given there are Ignite.NET server and client nodes
> * When the server node creates a cache and then the client node immediately
> gets affinity for the cache
> * Then getting affinity fails with NullPointerException
> {code:c#}
> IgniteConfiguration IgniteCfg(bool clientMode = false) => new
> IgniteConfiguration
> {
> ClientMode = clientMode,
> IgniteInstanceName = Guid.NewGuid().ToString(),
> DiscoverySpi = new TcpDiscoverySpi
> {
> IpFinder = new TcpDiscoveryStaticIpFinder
> {
> Endpoints = new[] { "127.0.0.1:47500" }
> }
> }
> };
> using var igniteSrv = Ignition.Start(IgniteCfg());
> using var igniteClient = Ignition.Start(IgniteCfg(true));
> var cache1 = igniteSrv.GetOrCreateCache("cache1");
> igniteClient.GetAffinity("cache1");
> {code}
> The igniteClient.GetAffinity fails with this exception:
> {code}
> Apache.Ignite.Core.Common.IgniteException
> HResult=0x80131500
> Message=Java exception occurred [class=java.lang.NullPointerException,
> message=]
> Source=Apache.Ignite.Core
> StackTrace:
>at Apache.Ignite.Core.Impl.PlatformJniTarget.InStreamOutObject(Int32 type,
> Action`1 writeAction)
>at Apache.Ignite.Core.Impl.PlatformTargetAdapter.DoOutOpObject(Int32 type,
> Action`1 action)
>at
> Apache.Ignite.Core.Impl.Ignite.Apache.Ignite.Core.Impl.IIgniteInternal.GetAffinity(String
> cacheName)
>at Apache.Ignite.Core.Impl.Ignite.GetAffinity(String cacheName)
>at DotNet.Sandbox.Program.Main(String[] args) in
> C:\Dev\tmp\DotNet.Sandbox\Program.cs:line 32
> This exception was originally thrown at this call stack:
> Apache.Ignite.Core.Impl.Unmanaged.Jni.Env.ExceptionCheck()
>
> Apache.Ignite.Core.Impl.Unmanaged.Jni.Env.CallObjectMethod(Apache.Ignite.Core.Impl.Unmanaged.Jni.GlobalRef,
> System.IntPtr, long*)
>
> Apache.Ignite.Core.Impl.Unmanaged.UnmanagedUtils.TargetInStreamOutObject(Apache.Ignite.Core.Impl.Unmanaged.Jni.GlobalRef,
> int, long)
> Apache.Ignite.Core.Impl.PlatformJniTarget.InStreamOutObject(int,
> System.Action)
> Inner Exception 1:
> JavaException: java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.platform.cache.affinity.PlatformAffinity.(PlatformAffinity.java:125)
> at
> org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.processInStreamOutObject(PlatformProcessorImpl.java:640)
> at
> org.apache.ignite.internal.processors.platform.PlatformTargetProxyImpl.inStreamOutObject(PlatformTargetProxyImpl.java:79)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13760) .NET: GetAffinity fails with NullPointerException on client node
[
https://issues.apache.org/jira/browse/IGNITE-13760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-13760:
Labels: .NET (was: )
> .NET: GetAffinity fails with NullPointerException on client node
>
>
> Key: IGNITE-13760
> URL: https://issues.apache.org/jira/browse/IGNITE-13760
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.9
>Reporter: Alexey Kukushkin
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET
> Fix For: 2.9.1
>
>
> * Given there are Ignite.NET server and client nodes
> * When the server node creates a cache and then the client node immediately
> gets affinity for the cache
> * Then getting affinity fails with NullPointerException
> {code:c#}
> IgniteConfiguration IgniteCfg(bool clientMode = false) => new
> IgniteConfiguration
> {
> ClientMode = clientMode,
> IgniteInstanceName = Guid.NewGuid().ToString(),
> DiscoverySpi = new TcpDiscoverySpi
> {
> IpFinder = new TcpDiscoveryStaticIpFinder
> {
> Endpoints = new[] { "127.0.0.1:47500" }
> }
> }
> };
> using var igniteSrv = Ignition.Start(IgniteCfg());
> using var igniteClient = Ignition.Start(IgniteCfg(true));
> var cache1 = igniteSrv.GetOrCreateCache("cache1");
> igniteClient.GetAffinity("cache1");
> {code}
> The igniteClient.GetAffinity fails with this exception:
> {code}
> Apache.Ignite.Core.Common.IgniteException
> HResult=0x80131500
> Message=Java exception occurred [class=java.lang.NullPointerException,
> message=]
> Source=Apache.Ignite.Core
> StackTrace:
>at Apache.Ignite.Core.Impl.PlatformJniTarget.InStreamOutObject(Int32 type,
> Action`1 writeAction)
>at Apache.Ignite.Core.Impl.PlatformTargetAdapter.DoOutOpObject(Int32 type,
> Action`1 action)
>at
> Apache.Ignite.Core.Impl.Ignite.Apache.Ignite.Core.Impl.IIgniteInternal.GetAffinity(String
> cacheName)
>at Apache.Ignite.Core.Impl.Ignite.GetAffinity(String cacheName)
>at DotNet.Sandbox.Program.Main(String[] args) in
> C:\Dev\tmp\DotNet.Sandbox\Program.cs:line 32
> This exception was originally thrown at this call stack:
> Apache.Ignite.Core.Impl.Unmanaged.Jni.Env.ExceptionCheck()
>
> Apache.Ignite.Core.Impl.Unmanaged.Jni.Env.CallObjectMethod(Apache.Ignite.Core.Impl.Unmanaged.Jni.GlobalRef,
> System.IntPtr, long*)
>
> Apache.Ignite.Core.Impl.Unmanaged.UnmanagedUtils.TargetInStreamOutObject(Apache.Ignite.Core.Impl.Unmanaged.Jni.GlobalRef,
> int, long)
> Apache.Ignite.Core.Impl.PlatformJniTarget.InStreamOutObject(int,
> System.Action)
> Inner Exception 1:
> JavaException: java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.platform.cache.affinity.PlatformAffinity.(PlatformAffinity.java:125)
> at
> org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.processInStreamOutObject(PlatformProcessorImpl.java:640)
> at
> org.apache.ignite.internal.processors.platform.PlatformTargetProxyImpl.inStreamOutObject(PlatformTargetProxyImpl.java:79)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13496) Java thin: Use non-blocking socket IO
[
https://issues.apache.org/jira/browse/IGNITE-13496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17238863#comment-17238863
]
Pavel Tupitsyn commented on IGNITE-13496:
-
Preliminary benchmarks with 1 NIO selector:
{code}
>>> BEFORE (master)
Benchmark Mode Cnt Score Error Units
JmhThinClientCacheBenchmark.get thrpt 10 65916.805 ± 2118.954 ops/s
JmhThinClientCacheBenchmark.put thrpt 10 62304.444 ± 2521.371 ops/s
>>> AFTER (GridNioServer)
Benchmark Mode Cnt Score Error Units
JmhThinClientCacheBenchmark.get thrpt 10 92501.557 ± 1380.384 ops/s
JmhThinClientCacheBenchmark.put thrpt 10 82907.446 ± 7572.537 ops/s
{code}
Testing with multiple selectors in progress.
> Java thin: Use non-blocking socket IO
> --
>
> Key: IGNITE-13496
> URL: https://issues.apache.org/jira/browse/IGNITE-13496
> Project: Ignite
> Issue Type: Improvement
> Components: thin client
>Affects Versions: 2.9
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Fix For: 2.10
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> IGNITE-7623 introduces async APIs to the Java thin client. However, socket
> writes still cause user thread blocking and thus reduce scalability.
> Investigate and prepare an IEP to use non-blocking IO.
> This ticket does not affect user-facing APIs, only changes the way we do IO
> internally.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13753) Non-thread-safe collection is used for the list of registered MBeans in JmxMetricExporterSpi
[
https://issues.apache.org/jira/browse/IGNITE-13753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-13753:
--
Ignite Flags: (was: Docs Required,Release Notes Required)
> Non-thread-safe collection is used for the list of registered MBeans in
> JmxMetricExporterSpi
>
>
> Key: IGNITE-13753
> URL: https://issues.apache.org/jira/browse/IGNITE-13753
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
>Priority: Major
> Fix For: 2.10
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{MetricManager}} registry creation and remove listeners can be invoked
> concurrently (the only synchronization is via {{map.computeIfAbsent}} which
> provides key-level granularity.
> As a result, some of the beans are lost and I get an occasional assertion on
> {code}
> boolean rmv = mBeans.remove(mbeanName);
> assert rmv;
> {code}
> Changing the collection to a synchronized list should suffice.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13753) Non-thread-safe collection is used for the list of registered MBeans in JmxMetricExporterSpi
[
https://issues.apache.org/jira/browse/IGNITE-13753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17238830#comment-17238830
]
Alexey Goncharuk commented on IGNITE-13753:
---
[~agura] [~nizhikov] can you take a look at the changes? The tests are failing
in master as well (.NET inspections are related to TC update and Cache5 fails
with some random errors - I will try to investigate and file a separate
ticket(s)).
> Non-thread-safe collection is used for the list of registered MBeans in
> JmxMetricExporterSpi
>
>
> Key: IGNITE-13753
> URL: https://issues.apache.org/jira/browse/IGNITE-13753
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
>Priority: Major
> Fix For: 2.10
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{MetricManager}} registry creation and remove listeners can be invoked
> concurrently (the only synchronization is via {{map.computeIfAbsent}} which
> provides key-level granularity.
> As a result, some of the beans are lost and I get an occasional assertion on
> {code}
> boolean rmv = mBeans.remove(mbeanName);
> assert rmv;
> {code}
> Changing the collection to a synchronized list should suffice.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13753) Non-thread-safe collection is used for the list of registered MBeans in JmxMetricExporterSpi
[
https://issues.apache.org/jira/browse/IGNITE-13753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17238810#comment-17238810
]
Ignite TC Bot commented on IGNITE-13753:
{panel:title=Branch: [pull/8492/head] Base: [master] : Possible Blockers
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 5{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5755989]]
{color:#d04437}Platform .NET (Inspections)*{color} [[tests 0 Failure on metric
|https://ci.ignite.apache.org/viewLog.html?buildId=5755973]]
{panel}
{panel:title=Branch: [pull/8492/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}SPI{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5755092]]
* {color:#013220}IgniteSpiTestSuite:
JmxMetricExporterSpiTest.testConcurrentRegistration - PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5755180buildTypeId=IgniteTests24Java8_RunAll]
> Non-thread-safe collection is used for the list of registered MBeans in
> JmxMetricExporterSpi
>
>
> Key: IGNITE-13753
> URL: https://issues.apache.org/jira/browse/IGNITE-13753
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
>Priority: Major
> Fix For: 2.10
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{MetricManager}} registry creation and remove listeners can be invoked
> concurrently (the only synchronization is via {{map.computeIfAbsent}} which
> provides key-level granularity.
> As a result, some of the beans are lost and I get an occasional assertion on
> {code}
> boolean rmv = mBeans.remove(mbeanName);
> assert rmv;
> {code}
> Changing the collection to a synchronized list should suffice.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-13762) MTCGA/Muted tests web page should display multiple Jira tickets in Ticket column
Maksim Timonin created IGNITE-13762:
---
Summary: MTCGA/Muted tests web page should display multiple Jira
tickets in Ticket column
Key: IGNITE-13762
URL: https://issues.apache.org/jira/browse/IGNITE-13762
Project: Ignite
Issue Type: New Feature
Reporter: Maksim Timonin
Some test ignored with multiple jira tickets, they marked as:
@Ignore("https://../IGNITE-12345;, "https://.../IGNITE-54321;)
For example:
PageEvictionTouchOrderTest.testTouchOrderWithFairFifoEvictionMvccTxReplicated
But web of MTCGA displays only first ticket in column "Ticket":
https://mtcga.gridgain.com/mutes.html
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-13761) Implement LRU-based page replacement algorithm
Aleksey Plekhanov created IGNITE-13761: -- Summary: Implement LRU-based page replacement algorithm Key: IGNITE-13761 URL: https://issues.apache.org/jira/browse/IGNITE-13761 Project: Ignite Issue Type: Improvement Reporter: Aleksey Plekhanov Assignee: Aleksey Plekhanov See IEP-62 for more details. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13760) Ignite.NET GetAffinity fails with NullPointerException
[
https://issues.apache.org/jira/browse/IGNITE-13760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-13760:
Fix Version/s: 2.9.1
> Ignite.NET GetAffinity fails with NullPointerException
> --
>
> Key: IGNITE-13760
> URL: https://issues.apache.org/jira/browse/IGNITE-13760
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.9
>Reporter: Alexey Kukushkin
>Priority: Major
> Fix For: 2.9.1
>
>
> * Given there are Ignite.NET server and client nodes
> * When the server node creates a cache and then the client node immediately
> gets affinity for the cache
> * Then getting affinity fails with NullPointerException
> {code:c#}
> IgniteConfiguration IgniteCfg(bool clientMode = false) => new
> IgniteConfiguration
> {
> ClientMode = clientMode,
> IgniteInstanceName = Guid.NewGuid().ToString(),
> DiscoverySpi = new TcpDiscoverySpi
> {
> IpFinder = new TcpDiscoveryStaticIpFinder
> {
> Endpoints = new[] { "127.0.0.1:47500" }
> }
> }
> };
> using var igniteSrv = Ignition.Start(IgniteCfg());
> using var igniteClient = Ignition.Start(IgniteCfg(true));
> var cache1 = igniteSrv.GetOrCreateCache("cache1");
> igniteClient.GetAffinity("cache1");
> {code}
> The igniteClient.GetAffinity fails with this exception:
> {code}
> Apache.Ignite.Core.Common.IgniteException
> HResult=0x80131500
> Message=Java exception occurred [class=java.lang.NullPointerException,
> message=]
> Source=Apache.Ignite.Core
> StackTrace:
>at Apache.Ignite.Core.Impl.PlatformJniTarget.InStreamOutObject(Int32 type,
> Action`1 writeAction)
>at Apache.Ignite.Core.Impl.PlatformTargetAdapter.DoOutOpObject(Int32 type,
> Action`1 action)
>at
> Apache.Ignite.Core.Impl.Ignite.Apache.Ignite.Core.Impl.IIgniteInternal.GetAffinity(String
> cacheName)
>at Apache.Ignite.Core.Impl.Ignite.GetAffinity(String cacheName)
>at DotNet.Sandbox.Program.Main(String[] args) in
> C:\Dev\tmp\DotNet.Sandbox\Program.cs:line 32
> This exception was originally thrown at this call stack:
> Apache.Ignite.Core.Impl.Unmanaged.Jni.Env.ExceptionCheck()
>
> Apache.Ignite.Core.Impl.Unmanaged.Jni.Env.CallObjectMethod(Apache.Ignite.Core.Impl.Unmanaged.Jni.GlobalRef,
> System.IntPtr, long*)
>
> Apache.Ignite.Core.Impl.Unmanaged.UnmanagedUtils.TargetInStreamOutObject(Apache.Ignite.Core.Impl.Unmanaged.Jni.GlobalRef,
> int, long)
> Apache.Ignite.Core.Impl.PlatformJniTarget.InStreamOutObject(int,
> System.Action)
> Inner Exception 1:
> JavaException: java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.platform.cache.affinity.PlatformAffinity.(PlatformAffinity.java:125)
> at
> org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.processInStreamOutObject(PlatformProcessorImpl.java:640)
> at
> org.apache.ignite.internal.processors.platform.PlatformTargetProxyImpl.inStreamOutObject(PlatformTargetProxyImpl.java:79)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-13760) Ignite.NET GetAffinity fails with NullPointerException
[
https://issues.apache.org/jira/browse/IGNITE-13760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn reassigned IGNITE-13760:
---
Assignee: Pavel Tupitsyn
> Ignite.NET GetAffinity fails with NullPointerException
> --
>
> Key: IGNITE-13760
> URL: https://issues.apache.org/jira/browse/IGNITE-13760
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.9
>Reporter: Alexey Kukushkin
>Assignee: Pavel Tupitsyn
>Priority: Major
> Fix For: 2.9.1
>
>
> * Given there are Ignite.NET server and client nodes
> * When the server node creates a cache and then the client node immediately
> gets affinity for the cache
> * Then getting affinity fails with NullPointerException
> {code:c#}
> IgniteConfiguration IgniteCfg(bool clientMode = false) => new
> IgniteConfiguration
> {
> ClientMode = clientMode,
> IgniteInstanceName = Guid.NewGuid().ToString(),
> DiscoverySpi = new TcpDiscoverySpi
> {
> IpFinder = new TcpDiscoveryStaticIpFinder
> {
> Endpoints = new[] { "127.0.0.1:47500" }
> }
> }
> };
> using var igniteSrv = Ignition.Start(IgniteCfg());
> using var igniteClient = Ignition.Start(IgniteCfg(true));
> var cache1 = igniteSrv.GetOrCreateCache("cache1");
> igniteClient.GetAffinity("cache1");
> {code}
> The igniteClient.GetAffinity fails with this exception:
> {code}
> Apache.Ignite.Core.Common.IgniteException
> HResult=0x80131500
> Message=Java exception occurred [class=java.lang.NullPointerException,
> message=]
> Source=Apache.Ignite.Core
> StackTrace:
>at Apache.Ignite.Core.Impl.PlatformJniTarget.InStreamOutObject(Int32 type,
> Action`1 writeAction)
>at Apache.Ignite.Core.Impl.PlatformTargetAdapter.DoOutOpObject(Int32 type,
> Action`1 action)
>at
> Apache.Ignite.Core.Impl.Ignite.Apache.Ignite.Core.Impl.IIgniteInternal.GetAffinity(String
> cacheName)
>at Apache.Ignite.Core.Impl.Ignite.GetAffinity(String cacheName)
>at DotNet.Sandbox.Program.Main(String[] args) in
> C:\Dev\tmp\DotNet.Sandbox\Program.cs:line 32
> This exception was originally thrown at this call stack:
> Apache.Ignite.Core.Impl.Unmanaged.Jni.Env.ExceptionCheck()
>
> Apache.Ignite.Core.Impl.Unmanaged.Jni.Env.CallObjectMethod(Apache.Ignite.Core.Impl.Unmanaged.Jni.GlobalRef,
> System.IntPtr, long*)
>
> Apache.Ignite.Core.Impl.Unmanaged.UnmanagedUtils.TargetInStreamOutObject(Apache.Ignite.Core.Impl.Unmanaged.Jni.GlobalRef,
> int, long)
> Apache.Ignite.Core.Impl.PlatformJniTarget.InStreamOutObject(int,
> System.Action)
> Inner Exception 1:
> JavaException: java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.platform.cache.affinity.PlatformAffinity.(PlatformAffinity.java:125)
> at
> org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.processInStreamOutObject(PlatformProcessorImpl.java:640)
> at
> org.apache.ignite.internal.processors.platform.PlatformTargetProxyImpl.inStreamOutObject(PlatformTargetProxyImpl.java:79)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-13760) Ignite.NET GetAffinity fails with NullPointerException
Alexey Kukushkin created IGNITE-13760:
-
Summary: Ignite.NET GetAffinity fails with NullPointerException
Key: IGNITE-13760
URL: https://issues.apache.org/jira/browse/IGNITE-13760
Project: Ignite
Issue Type: Bug
Components: platforms
Affects Versions: 2.9
Reporter: Alexey Kukushkin
* Given there are Ignite.NET server and client nodes
* When the server node creates a cache and then the client node immediately
gets affinity for the cache
* Then getting affinity fails with NullPointerException
{code:c#}
IgniteConfiguration IgniteCfg(bool clientMode = false) => new
IgniteConfiguration
{
ClientMode = clientMode,
IgniteInstanceName = Guid.NewGuid().ToString(),
DiscoverySpi = new TcpDiscoverySpi
{
IpFinder = new TcpDiscoveryStaticIpFinder
{
Endpoints = new[] { "127.0.0.1:47500" }
}
}
};
using var igniteSrv = Ignition.Start(IgniteCfg());
using var igniteClient = Ignition.Start(IgniteCfg(true));
var cache1 = igniteSrv.GetOrCreateCache("cache1");
igniteClient.GetAffinity("cache1");
{code}
The igniteClient.GetAffinity fails with this exception:
{code}
Apache.Ignite.Core.Common.IgniteException
HResult=0x80131500
Message=Java exception occurred [class=java.lang.NullPointerException,
message=]
Source=Apache.Ignite.Core
StackTrace:
at Apache.Ignite.Core.Impl.PlatformJniTarget.InStreamOutObject(Int32 type,
Action`1 writeAction)
at Apache.Ignite.Core.Impl.PlatformTargetAdapter.DoOutOpObject(Int32 type,
Action`1 action)
at
Apache.Ignite.Core.Impl.Ignite.Apache.Ignite.Core.Impl.IIgniteInternal.GetAffinity(String
cacheName)
at Apache.Ignite.Core.Impl.Ignite.GetAffinity(String cacheName)
at DotNet.Sandbox.Program.Main(String[] args) in
C:\Dev\tmp\DotNet.Sandbox\Program.cs:line 32
This exception was originally thrown at this call stack:
Apache.Ignite.Core.Impl.Unmanaged.Jni.Env.ExceptionCheck()
Apache.Ignite.Core.Impl.Unmanaged.Jni.Env.CallObjectMethod(Apache.Ignite.Core.Impl.Unmanaged.Jni.GlobalRef,
System.IntPtr, long*)
Apache.Ignite.Core.Impl.Unmanaged.UnmanagedUtils.TargetInStreamOutObject(Apache.Ignite.Core.Impl.Unmanaged.Jni.GlobalRef,
int, long)
Apache.Ignite.Core.Impl.PlatformJniTarget.InStreamOutObject(int,
System.Action)
Inner Exception 1:
JavaException: java.lang.NullPointerException
at
org.apache.ignite.internal.processors.platform.cache.affinity.PlatformAffinity.(PlatformAffinity.java:125)
at
org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.processInStreamOutObject(PlatformProcessorImpl.java:640)
at
org.apache.ignite.internal.processors.platform.PlatformTargetProxyImpl.inStreamOutObject(PlatformTargetProxyImpl.java:79)
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Reopened] (IGNITE-12380) Add event for node validation failure.
[ https://issues.apache.org/jira/browse/IGNITE-12380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov reopened IGNITE-12380: --- > Add event for node validation failure. > -- > > Key: IGNITE-12380 > URL: https://issues.apache.org/jira/browse/IGNITE-12380 > Project: Ignite > Issue Type: Improvement >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Major > Fix For: 2.10 > > Time Spent: 4h 20m > Remaining Estimate: 0h > > It's needed record an event of a special type in case a node can't join the > topology due to a failure of its validation by existing nodes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-12380) Add event for node validation failure.
[ https://issues.apache.org/jira/browse/IGNITE-12380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov resolved IGNITE-12380. --- Resolution: Fixed > Add event for node validation failure. > -- > > Key: IGNITE-12380 > URL: https://issues.apache.org/jira/browse/IGNITE-12380 > Project: Ignite > Issue Type: Improvement >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Major > Fix For: 2.10 > > Time Spent: 4h 20m > Remaining Estimate: 0h > > It's needed record an event of a special type in case a node can't join the > topology due to a failure of its validation by existing nodes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12380) Add event for node validation failure.
[ https://issues.apache.org/jira/browse/IGNITE-12380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17238758#comment-17238758 ] Anton Vinogradov commented on IGNITE-12380: --- Merged to master branch. Thanks for your contribution! > Add event for node validation failure. > -- > > Key: IGNITE-12380 > URL: https://issues.apache.org/jira/browse/IGNITE-12380 > Project: Ignite > Issue Type: Improvement >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Major > Fix For: 2.10 > > Time Spent: 4h 20m > Remaining Estimate: 0h > > It's needed record an event of a special type in case a node can't join the > topology due to a failure of its validation by existing nodes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13759) .NET: Add support for dotnet-example global tool
Pavel Tupitsyn created IGNITE-13759: --- Summary: .NET: Add support for dotnet-example global tool Key: IGNITE-13759 URL: https://issues.apache.org/jira/browse/IGNITE-13759 Project: Ignite Issue Type: Bug Components: platforms Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn Fix For: 2.10 https://github.com/patriksvensson/dotnet-example is a nice way to present and run examples. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13758) Remove IgniteFeatures and all dependent code.
Stanilovsky Evgeny created IGNITE-13758: --- Summary: Remove IgniteFeatures and all dependent code. Key: IGNITE-13758 URL: https://issues.apache.org/jira/browse/IGNITE-13758 Project: Ignite Issue Type: Improvement Components: general Affects Versions: 2.9 Reporter: Stanilovsky Evgeny I found that IgniteFeatures are useless, cause AI not support heterogeneous cluster i.e. multiple versions in one grid [1]. And code comparison with GGCE [2] highlight that there is some kind of fragments involved into rolling upgrade process. [1] http://apache-ignite-users.70518.x6.nabble.com/Platform-updates-td15998.html [2] https://github.com/gridgain/gridgain -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13755) .NET: Inspections fail after TC upgrade - unused classes detected
[
https://issues.apache.org/jira/browse/IGNITE-13755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17238733#comment-17238733
]
Pavel Tupitsyn commented on IGNITE-13755:
-
Cherry-picked to ignite-2.9.1: 1d2d76051cbf36ebdb8cbfeca0695078234d55fb
> .NET: Inspections fail after TC upgrade - unused classes detected
> -
>
> Key: IGNITE-13755
> URL: https://issues.apache.org/jira/browse/IGNITE-13755
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Minor
> Labels: .NET
> Fix For: 2.9.1
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {code}
> Enum 'CacheFlags' is never used
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (IGNITE-13755) .NET: Inspections fail after TC upgrade - unused classes detected
[
https://issues.apache.org/jira/browse/IGNITE-13755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn resolved IGNITE-13755.
-
Resolution: Fixed
> .NET: Inspections fail after TC upgrade - unused classes detected
> -
>
> Key: IGNITE-13755
> URL: https://issues.apache.org/jira/browse/IGNITE-13755
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Minor
> Labels: .NET
> Fix For: 2.9.1
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {code}
> Enum 'CacheFlags' is never used
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13755) .NET: Inspections fail after TC upgrade - unused classes detected
[
https://issues.apache.org/jira/browse/IGNITE-13755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17238730#comment-17238730
]
Pavel Tupitsyn commented on IGNITE-13755:
-
Merged to master: 92ea7634a20bb5c7248e2cbe45930bf6b17a87de
> .NET: Inspections fail after TC upgrade - unused classes detected
> -
>
> Key: IGNITE-13755
> URL: https://issues.apache.org/jira/browse/IGNITE-13755
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Minor
> Labels: .NET
> Fix For: 2.9.1
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {code}
> Enum 'CacheFlags' is never used
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13755) .NET: Inspections fail after TC upgrade - unused classes detected
[
https://issues.apache.org/jira/browse/IGNITE-13755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17238726#comment-17238726
]
Ignite TC Bot commented on IGNITE-13755:
{panel:title=Branch: [pull/8494/head] Base: [master] : Possible Blockers
(14)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Control Utility{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5755811]]
{color:#d04437}Queries 1{color} [[tests
11|https://ci.ignite.apache.org/viewLog.html?buildId=5755784]]
* IgniteBinaryCacheQueryTestSuite:
IgniteCachePartitionedSnapshotEnabledQuerySelfTest.testClientQueryExecutedEvents
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteBinaryCacheQueryTestSuite:
IgniteCacheAtomicQuerySelfTest.testClientQueryExecutedEvents - Test has low
fail rate in base branch 0,0% and is not flaky
* IgniteBinaryCacheQueryTestSuite:
IgniteCacheAtomicNearEnabledQuerySelfTest.testClientQueryExecutedEvents - Test
has low fail rate in base branch 0,0% and is not flaky
* IgniteBinaryCacheQueryTestSuite:
IgniteCachePartitionedQueryP2PDisabledSelfTest.testClientQueryExecutedEvents -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteBinaryCacheQueryTestSuite:
IgniteCachePartitionedQueryEvtsDisabledSelfTest.testClientQueryExecutedEvents -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteBinaryCacheQueryTestSuite:
IgniteCacheLocalQuerySelfTest.testClientQueryExecutedEvents - Test has low fail
rate in base branch 0,0% and is not flaky
* IgniteBinaryCacheQueryTestSuite:
IgniteCacheLocalAtomicQuerySelfTest.testClientQueryExecutedEvents - Test has
low fail rate in base branch 0,0% and is not flaky
* IgniteBinaryCacheQueryTestSuite:
IgniteCacheReplicatedQuerySelfTest.testClientQueryExecutedEvents - Test has low
fail rate in base branch 0,0% and is not flaky
* IgniteBinaryCacheQueryTestSuite:
IgniteCacheReplicatedQueryP2PDisabledSelfTest.testClientQueryExecutedEvents -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteBinaryCacheQueryTestSuite:
IgniteCacheReplicatedQueryEvtsDisabledSelfTest.testClientQueryExecutedEvents -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteBinaryCacheQueryTestSuite:
IgniteCachePartitionedQuerySelfTest.testClientQueryExecutedEvents - Test has
low fail rate in base branch 0,0% and is not flaky
... and 0 tests blockers
{color:#d04437}ZooKeeper (Discovery) 4{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5755787]]
* ZookeeperDiscoverySpiTestSuite4:
IgniteCacheReplicatedQuerySelfTest.testClientQueryExecutedEvents - Test has low
fail rate in base branch 0,0% and is not flaky
{color:#d04437}PDS (Compatibility)*{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5755771]]
* IgniteCompatibilityBasicTestSuite:
FoldersReuseCompatibilityTest.testFoldersReuseCompatibility_2_1 - Test has low
fail rate in base branch 0,0% and is not flaky
{panel}
{panel:title=Branch: [pull/8494/head] Base: [master] : New Tests
(12)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Queries 1{color} [[tests
11|https://ci.ignite.apache.org/viewLog.html?buildId=5755784]]
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
IgniteCacheLocalQuerySelfTest.testClientQueryExecutedEventsIncludeSensitive -
PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
IgniteCacheReplicatedQuerySelfTest.testClientQueryExecutedEventsIncludeSensitive
- PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
IgniteCacheLocalAtomicQuerySelfTest.testClientQueryExecutedEventsIncludeSensitive
- PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
IgniteCacheReplicatedQueryP2PDisabledSelfTest.testClientQueryExecutedEventsIncludeSensitive
- PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
IgniteCacheReplicatedQueryEvtsDisabledSelfTest.testClientQueryExecutedEventsIncludeSensitive
- PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
IgniteCachePartitionedSnapshotEnabledQuerySelfTest.testClientQueryExecutedEventsIncludeSensitive
- PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
IgniteCachePartitionedQuerySelfTest.testClientQueryExecutedEventsIncludeSensitive
- PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
IgniteCacheAtomicNearEnabledQuerySelfTest.testClientQueryExecutedEventsIncludeSensitive
- PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
IgniteCacheAtomicQuerySelfTest.testClientQueryExecutedEventsIncludeSensitive -
PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
IgniteCachePartitionedQueryEvtsDisabledSelfTest.testClientQueryExecutedEventsIncludeSensitive
- PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
IgniteCachePartitionedQueryP2PDisabledSelfTest.testClientQueryExecutedEventsIncludeSensitive
[jira] [Commented] (IGNITE-13703) Check difference between TcpDiscovery and ZookeeperDiscovery at Cellular switch
[ https://issues.apache.org/jira/browse/IGNITE-13703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17238722#comment-17238722 ] Anton Vinogradov commented on IGNITE-13703: --- Merged to ignite-ducktape > Check difference between TcpDiscovery and ZookeeperDiscovery at Cellular > switch > --- > > Key: IGNITE-13703 > URL: https://issues.apache.org/jira/browse/IGNITE-13703 > Project: Ignite > Issue Type: Improvement >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > Labels: IEP-56, ducktape > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-13703) Check difference between TcpDiscovery and ZookeeperDiscovery at Cellular switch
[ https://issues.apache.org/jira/browse/IGNITE-13703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov resolved IGNITE-13703. --- Resolution: Fixed > Check difference between TcpDiscovery and ZookeeperDiscovery at Cellular > switch > --- > > Key: IGNITE-13703 > URL: https://issues.apache.org/jira/browse/IGNITE-13703 > Project: Ignite > Issue Type: Improvement >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > Labels: IEP-56, ducktape > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13726) Add an ability to view count of hot and cold pages in page memory
[ https://issues.apache.org/jira/browse/IGNITE-13726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Plekhanov updated IGNITE-13726: --- Labels: iep-62 (was: ) > Add an ability to view count of hot and cold pages in page memory > - > > Key: IGNITE-13726 > URL: https://issues.apache.org/jira/browse/IGNITE-13726 > Project: Ignite > Issue Type: New Feature >Reporter: Aleksey Plekhanov >Assignee: Aleksey Plekhanov >Priority: Major > Labels: iep-62 > Time Spent: 20m > Remaining Estimate: 0h > > Currently, we can't determine how many hot (touched recently) and cold pages > we have in the page-memory. This information can be helpful for data region > size tuning and can show the effectiveness of the page replacement algorithm. > Such information can be represented as a histogram showing the count of pages > last touched in each time interval. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13456) Expand info collected during tracing of SQL queries.
[ https://issues.apache.org/jira/browse/IGNITE-13456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17238632#comment-17238632 ] Amelchev Nikita commented on IGNITE-13456: -- [~PetrovMikhail], Looks good to me. > Expand info collected during tracing of SQL queries. > > > Key: IGNITE-13456 > URL: https://issues.apache.org/jira/browse/IGNITE-13456 > Project: Ignite > Issue Type: Improvement >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Major > Fix For: 2.10 > > Time Spent: 0.5h > Remaining Estimate: 0h > > It's needed to expand info that collected during tracing of SQL queries. > The following info must be collected: > * partition reservation (set of reserved partitions); > * query parse info: cached query parse result or real parse. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13757) Investigate if serializers are supported with GraalVM native image.
[ https://issues.apache.org/jira/browse/IGNITE-13757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-13757: -- Labels: graalvm iep-54 ignite-3 (was: iep-54 ignite-3) > Investigate if serializers are supported with GraalVM native image. > --- > > Key: IGNITE-13757 > URL: https://issues.apache.org/jira/browse/IGNITE-13757 > Project: Ignite > Issue Type: Improvement >Reporter: Andrey Mashenkov >Priority: Major > Labels: graalvm, iep-54, ignite-3 > > GraalVM has limited support of reflection [1]. > We have to check if all serializers (see IGNITE-13618) are compatible with > GraalMV native image and/or if some additional setting are required from the > user side to make serializers work. > The goal is to have at least one compatible serializer we could fallback to. > [1] https://www.graalvm.org/reference-manual/native-image/Reflection/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13757) Investigate if serializers are supported with GraalVM native image.
[ https://issues.apache.org/jira/browse/IGNITE-13757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-13757: -- Description: GraalVM has limited support of reflection [1]. We have to check if all serializers (see IGNITE-13618) are compatible with GraalMV native image and/or if some additional setting are required from the user side to make serializers work. The goal is to have at least one compatible serializer we could fallback to. [1] https://www.graalvm.org/reference-manual/native-image/Reflection/ was: GraalVM has limited support of reflection. We have to check if all serializers (see IGNITE-13618) are compatible with GraalMV native image and/or if some additional setting are required from the user side to make serializers work. The goal is to have at least one compatible serializer we could fallback to. > Investigate if serializers are supported with GraalVM native image. > --- > > Key: IGNITE-13757 > URL: https://issues.apache.org/jira/browse/IGNITE-13757 > Project: Ignite > Issue Type: Improvement >Reporter: Andrey Mashenkov >Priority: Major > Labels: iep-54, ignite-3 > > GraalVM has limited support of reflection [1]. > We have to check if all serializers (see IGNITE-13618) are compatible with > GraalMV native image and/or if some additional setting are required from the > user side to make serializers work. > The goal is to have at least one compatible serializer we could fallback to. > [1] https://www.graalvm.org/reference-manual/native-image/Reflection/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13757) Investigate if serializers are supported with GraalVM native image.
Andrey Mashenkov created IGNITE-13757: - Summary: Investigate if serializers are supported with GraalVM native image. Key: IGNITE-13757 URL: https://issues.apache.org/jira/browse/IGNITE-13757 Project: Ignite Issue Type: Improvement Reporter: Andrey Mashenkov GraalVM has limited support of reflection. We have to check if all serializers (see IGNITE-13618) are compatible with GraalMV native image and/or if some additional setting are required from the user side to make serializers work. The goal is to have at least one compatible serializer we could fallback to. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13756) Node crash if select uses index field with wrong type
[
https://issues.apache.org/jira/browse/IGNITE-13756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Mashenkov updated IGNITE-13756:
--
Description:
Steps to reproduce:
1. Start node with cache configuration:
{code:java}
{code}
2. Insert some data using SQL thin client:
{code:java}
0: jdbc:ignite:thin://127.0.0.1:10800> insert into
"endpoint-cache".ENDPOINTCACHEVALUE (_key,
SENDTIME,CREATEDON,USERID,SRVREQID,PROCESSED) values (1, 12345, 12345,
123456789, 'POST', True);
1 row affected (0.206 seconds)
0: jdbc:ignite:thin://127.0.0.1:10800> insert into
"endpoint-cache".ENDPOINTCACHEVALUE (_key,
SENDTIME,CREATEDON,USERID,SRVREQID,PROCESSED) values (2, 12345, 12345,
123456789, 'POST', True);
1 row affected (0.016 seconds)
0: jdbc:ignite:thin://127.0.0.1:10800> insert into
"endpoint-cache".ENDPOINTCACHEVALUE (_key,
SENDTIME,CREATEDON,USERID,SRVREQID,PROCESSED) values (3, 12345, 12345,
123456789, 'POST', True);
{code}
3. Run select:
{code:java}
SELECT CREATEDON,USERID,SRVREQID,PROCESSED FROM
"endpoint-cache".ENDPOINTCACHEVALUE p where SRVREQID=123;
{code}
Actual result:
Node crushed cause of corrupted B+Tree:
{code:java}
[2019-07-25 23:37:22,734][ERROR][client-connector-#63][root] Critical system
error detected. Will be handled accordingly to configured handler
[hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet
[SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]],
failureCtx=FailureContext [type=CRITICAL_ERROR, err=class
o.a.i.i.processors.cache.persistence.tree.CorruptedTreeException: B+Tree is
corrupted [pages(groupId, pageId)=[IgniteBiTuple [val1=1739103562,
val2=844420635164677]], msg=Runtime failure on bounds: [lower=RowSimple
[vals=Value[] [null, null, null, null, null, null, 123, null, null]],
upper=RowSimple [vals=Value[] [null, null, null, null, null, null, 123, null,
null]]
class
org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
B+Tree is corrupted [pages(groupId, pageId)=[IgniteBiTuple [val1=1739103562,
val2=844420635164677]], msg=Runtime failure on bounds: [lower=RowSimple
[vals=Value[] [null, null, null, null, null, null, 123, null, null]],
upper=RowSimple [vals=Value[] [null, null, null, null, null, null, 123, null,
null
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.corruptedTreeException(BPlusTree.java:5169)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.find(BPlusTree.java:1035)
at
org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.find(H2TreeIndex.java:240)
at org.h2.index.BaseIndex.find(BaseIndex.java:128)
at org.h2.index.IndexCursor.find(IndexCursor.java:169)
at org.h2.table.TableFilter.next(TableFilter.java:468)
at org.h2.command.dml.Select$LazyResultQueryFlat.fetchNextRow(Select.java:1452)
at org.h2.result.LazyResult.hasNext(LazyResult.java:79)
at org.h2.result.LazyResult.next(LazyResult.java:59)
at org.h2.command.dml.Select.queryFlat(Select.java:519)
at org.h2.command.dml.Select.queryWithoutCache(Select.java:625)
at org.h2.command.dml.Query.queryWithoutCacheLazyCheck(Query.java:114)
at org.h2.command.dml.Query.query(Query.java:352)
at org.h2.command.dml.Query.query(Query.java:333)
at org.h2.command.CommandContainer.query(CommandContainer.java:113)
at org.h2.command.Command.executeQuery(Command.java:201)
at
org.h2.jdbc.JdbcPreparedStatement.executeQuery(JdbcPreparedStatement.java:111)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQuery(IgniteH2Indexing.java:974)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQueryWithTimer(IgniteH2Indexing.java:1047)
at
org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onQueryRequest0(GridMapQueryExecutor.java:526)
at
org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onQueryRequest(GridMapQueryExecutor.java:353)
at
org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onMessage(GridMapQueryExecutor.java:210)
at
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$1.applyx(GridReduceQueryExecutor.java:163)
at
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$1.applyx(GridReduceQueryExecutor.java:161)
at
org.apache.ignite.internal.util.lang.IgniteInClosure2X.apply(IgniteInClosure2X.java:38)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.send(IgniteH2Indexing.java:2425)
at
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.send(GridReduceQueryExecutor.java:1541)
at
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:794)
at
[jira] [Created] (IGNITE-13756) Node crash if select uses index field with wrong type
Andrey Mashenkov created IGNITE-13756:
-
Summary: Node crash if select uses index field with wrong type
Key: IGNITE-13756
URL: https://issues.apache.org/jira/browse/IGNITE-13756
Project: Ignite
Issue Type: Bug
Components: sql
Reporter: Andrey Mashenkov
Steps to reproduce:
1. Start node with cache configuration:
{code:java}
{code}
2. Insert some data using SQL thin client:
{code:java}
0: jdbc:ignite:thin://127.0.0.1:10800> insert into
"endpoint-cache".ENDPOINTCACHEVALUE (_key,
SENDTIME,CREATEDON,USERID,SRVREQID,PROCESSED) values (1, 12345, 12345,
123456789, 'POST', True);
1 row affected (0.206 seconds)
0: jdbc:ignite:thin://127.0.0.1:10800> insert into
"endpoint-cache".ENDPOINTCACHEVALUE (_key,
SENDTIME,CREATEDON,USERID,SRVREQID,PROCESSED) values (2, 12345, 12345,
123456789, 'POST', True);
1 row affected (0.016 seconds)
0: jdbc:ignite:thin://127.0.0.1:10800> insert into
"endpoint-cache".ENDPOINTCACHEVALUE (_key,
SENDTIME,CREATEDON,USERID,SRVREQID,PROCESSED) values (3, 12345, 12345,
123456789, 'POST', True);
{code}
3. Run select:
{code:java}
SELECT CREATEDON,USERID,SRVREQID,PROCESSED FROM
"endpoint-cache".ENDPOINTCACHEVALUE p where SRVREQID=123;
{code}
Actual result:
Node crushed cause of corrupted B+Tree:
{code:java}
[2019-07-25 23:37:22,734][ERROR][client-connector-#63][root] Critical system
error detected. Will be handled accordingly to configured handler
[hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet
[SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]],
failureCtx=FailureContext [type=CRITICAL_ERROR, err=class
o.a.i.i.processors.cache.persistence.tree.CorruptedTreeException: B+Tree is
corrupted [pages(groupId, pageId)=[IgniteBiTuple [val1=1739103562,
val2=844420635164677]], msg=Runtime failure on bounds: [lower=RowSimple
[vals=Value[] [null, null, null, null, null, null, 123, null, null]],
upper=RowSimple [vals=Value[] [null, null, null, null, null, null, 123, null,
null]]
class
org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
B+Tree is corrupted [pages(groupId, pageId)=[IgniteBiTuple [val1=1739103562,
val2=844420635164677]], msg=Runtime failure on bounds: [lower=RowSimple
[vals=Value[] [null, null, null, null, null, null, 123, null, null]],
upper=RowSimple [vals=Value[] [null, null, null, null, null, null, 123, null,
null
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.corruptedTreeException(BPlusTree.java:5169)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.find(BPlusTree.java:1035)
at
org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.find(H2TreeIndex.java:240)
at org.h2.index.BaseIndex.find(BaseIndex.java:128)
at org.h2.index.IndexCursor.find(IndexCursor.java:169)
at org.h2.table.TableFilter.next(TableFilter.java:468)
at org.h2.command.dml.Select$LazyResultQueryFlat.fetchNextRow(Select.java:1452)
at org.h2.result.LazyResult.hasNext(LazyResult.java:79)
at org.h2.result.LazyResult.next(LazyResult.java:59)
at org.h2.command.dml.Select.queryFlat(Select.java:519)
at org.h2.command.dml.Select.queryWithoutCache(Select.java:625)
at org.h2.command.dml.Query.queryWithoutCacheLazyCheck(Query.java:114)
at org.h2.command.dml.Query.query(Query.java:352)
at org.h2.command.dml.Query.query(Query.java:333)
at org.h2.command.CommandContainer.query(CommandContainer.java:113)
at org.h2.command.Command.executeQuery(Command.java:201)
at
org.h2.jdbc.JdbcPreparedStatement.executeQuery(JdbcPreparedStatement.java:111)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQuery(IgniteH2Indexing.java:974)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQueryWithTimer(IgniteH2Indexing.java:1047)
at
org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onQueryRequest0(GridMapQueryExecutor.java:526)
at
org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onQueryRequest(GridMapQueryExecutor.java:353)
at
org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onMessage(GridMapQueryExecutor.java:210)
at
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$1.applyx(GridReduceQueryExecutor.java:163)
at
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$1.applyx(GridReduceQueryExecutor.java:161)
at
org.apache.ignite.internal.util.lang.IgniteInClosure2X.apply(IgniteInClosure2X.java:38)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.send(IgniteH2Indexing.java:2425)
at
[jira] [Commented] (IGNITE-13572) Duplicates in select query during partition eviction for caches with 0 backups
[ https://issues.apache.org/jira/browse/IGNITE-13572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17238610#comment-17238610 ] Ivan Daschinskiy commented on IGNITE-13572: --- [~ksirotkin] No you have not. My be you forgot to push changes, but I suppose you are not subscribed to github notifications > Duplicates in select query during partition eviction for caches with 0 backups > -- > > Key: IGNITE-13572 > URL: https://issues.apache.org/jira/browse/IGNITE-13572 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.9, 2.8.1 >Reporter: Ivan Daschinskiy >Assignee: Konstantin Sirotkin >Priority: Major > Fix For: 2.9.1 > > Attachments: SqlPartitionEvictionTest.java > > Time Spent: 3h 10m > Remaining Estimate: 0h > > Scenario: > # Start 2 nodes with indexed atomic partitioned cache with 0 backups. > # Load sufficient amout of data (or emulate slow removal from idx) > # Start another node. > # Perform SELECT * FROM . > Query result contains duplicates, result size is significantly bigger than > expected cache size. > Reproducer is attached. > Reproduced on 2.8.1, ongoing 2.9 and master -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-13572) Duplicates in select query during partition eviction for caches with 0 backups
[ https://issues.apache.org/jira/browse/IGNITE-13572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17238610#comment-17238610 ] Ivan Daschinskiy edited comment on IGNITE-13572 at 11/25/20, 9:00 AM: -- [~ksirotkin] No you have not. May be you forgot to push changes, but I suppose you are not subscribed to github notifications was (Author: ivandasch): [~ksirotkin] No you have not. My be you forgot to push changes, but I suppose you are not subscribed to github notifications > Duplicates in select query during partition eviction for caches with 0 backups > -- > > Key: IGNITE-13572 > URL: https://issues.apache.org/jira/browse/IGNITE-13572 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.9, 2.8.1 >Reporter: Ivan Daschinskiy >Assignee: Konstantin Sirotkin >Priority: Major > Fix For: 2.9.1 > > Attachments: SqlPartitionEvictionTest.java > > Time Spent: 3h 10m > Remaining Estimate: 0h > > Scenario: > # Start 2 nodes with indexed atomic partitioned cache with 0 backups. > # Load sufficient amout of data (or emulate slow removal from idx) > # Start another node. > # Perform SELECT * FROM . > Query result contains duplicates, result size is significantly bigger than > expected cache size. > Reproducer is attached. > Reproduced on 2.8.1, ongoing 2.9 and master -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13572) Duplicates in select query during partition eviction for caches with 0 backups
[ https://issues.apache.org/jira/browse/IGNITE-13572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17238604#comment-17238604 ] Konstantin Sirotkin commented on IGNITE-13572: -- [~ivandasch], please review. I fixed your comments. > Duplicates in select query during partition eviction for caches with 0 backups > -- > > Key: IGNITE-13572 > URL: https://issues.apache.org/jira/browse/IGNITE-13572 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.9, 2.8.1 >Reporter: Ivan Daschinskiy >Assignee: Konstantin Sirotkin >Priority: Major > Fix For: 2.9.1 > > Attachments: SqlPartitionEvictionTest.java > > Time Spent: 3h 10m > Remaining Estimate: 0h > > Scenario: > # Start 2 nodes with indexed atomic partitioned cache with 0 backups. > # Load sufficient amout of data (or emulate slow removal from idx) > # Start another node. > # Perform SELECT * FROM . > Query result contains duplicates, result size is significantly bigger than > expected cache size. > Reproducer is attached. > Reproduced on 2.8.1, ongoing 2.9 and master -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13554) ConcurrentModificationException on node join.
[
https://issues.apache.org/jira/browse/IGNITE-13554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Sirotkin updated IGNITE-13554:
-
Reviewer: Stanilovsky Evgeny (was: Vyacheslav Koptilin)
> ConcurrentModificationException on node join.
> -
>
> Key: IGNITE-13554
> URL: https://issues.apache.org/jira/browse/IGNITE-13554
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.8
>Reporter: Stanilovsky Evgeny
>Assignee: Konstantin Sirotkin
>Priority: Major
> Attachments: id.log
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {noformat}
> java.util.ConcurrentModificationException: null
> at java.util.HashMap$HashIterator.nextNode(HashMap.java:1445)
> at java.util.HashMap$EntryIterator.next(HashMap.java:1479)
> at java.util.HashMap$EntryIterator.next(HashMap.java:1477)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.fillAffinityNodeCaches(GridDiscoveryManager.java:3278)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.createDiscoCache(GridDiscoveryManager.java:2364)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.access$3100(GridDiscoveryManager.java:171)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:723)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.lambda$onDiscovery$0(GridDiscoveryManager.java:528)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body0(GridDiscoveryManager.java:2608)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body(GridDiscoveryManager.java:2646)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13554) ConcurrentModificationException on node join.
[
https://issues.apache.org/jira/browse/IGNITE-13554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17238601#comment-17238601
]
Ignite TC Bot commented on IGNITE-13554:
{panel:title=Branch: [pull/8440/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8440/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5724100buildTypeId=IgniteTests24Java8_RunAll]
> ConcurrentModificationException on node join.
> -
>
> Key: IGNITE-13554
> URL: https://issues.apache.org/jira/browse/IGNITE-13554
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.8
>Reporter: Stanilovsky Evgeny
>Assignee: Konstantin Sirotkin
>Priority: Major
> Attachments: id.log
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {noformat}
> java.util.ConcurrentModificationException: null
> at java.util.HashMap$HashIterator.nextNode(HashMap.java:1445)
> at java.util.HashMap$EntryIterator.next(HashMap.java:1479)
> at java.util.HashMap$EntryIterator.next(HashMap.java:1477)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.fillAffinityNodeCaches(GridDiscoveryManager.java:3278)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.createDiscoCache(GridDiscoveryManager.java:2364)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.access$3100(GridDiscoveryManager.java:171)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:723)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.lambda$onDiscovery$0(GridDiscoveryManager.java:528)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body0(GridDiscoveryManager.java:2608)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body(GridDiscoveryManager.java:2646)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
