[jira] [Assigned] (IGNITE-2649) Ignition.localIgnite() unreliable under Gateways and cause wrong components deserialization.
[
https://issues.apache.org/jira/browse/IGNITE-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ershov reassigned IGNITE-2649:
---
Assignee: Vladimir Ozerov (was: Vladimir Ershov)
> Ignition.localIgnite() unreliable under Gateways and cause wrong components
> deserialization.
>
>
> Key: IGNITE-2649
> URL: https://issues.apache.org/jira/browse/IGNITE-2649
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ershov
>Assignee: Vladimir Ozerov
>Priority: Critical
> Labels: 1.6, community
> Fix For: 1.6
>
> Original Estimate: 8h
> Remaining Estimate: 8h
>
> We can get something like this:
> {noformat}
> java.lang.IllegalArgumentException: This method should be accessed under
> org.apache.ignite.thread.IgniteThread
> at org.apache.ignite.internal.IgnitionEx.localIgnite(IgnitionEx.java:1252)
> at org.apache.ignite.Ignition.localIgnite(Ignition.java:531)
> at org.project.MyPojo.readResolve(MyPojo.java:123)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:746)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1448)
> at
> org.apache.ignite.internal.binary.BinaryUtils.doReadObject(BinaryUtils.java:1564)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readObject(BinaryReaderExImpl.java:1086)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.readFixedType(BinaryFieldAccessor.java:827)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read(BinaryFieldAccessor.java:643)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:734)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1448)
> at
> org.apache.ignite.internal.binary.BinaryUtils.doReadObject(BinaryUtils.java:1564)
> at
> org.apache.ignite.internal.binary.BinaryUtils.deserializeOrUnmarshal(BinaryUtils.java:1908)
> at
> org.apache.ignite.internal.binary.BinaryUtils.doReadMap(BinaryUtils.java:1892)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1595)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readField(BinaryReaderExImpl.java:1644)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read(BinaryFieldAccessor.java:643)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:734)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1448)
> at
> org.apache.ignite.internal.binary.BinaryObjectImpl.deserializeValue(BinaryObjectImpl.java:537)
> at
> org.apache.ignite.internal.binary.BinaryObjectImpl.value(BinaryObjectImpl.java:117)
> at
> org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinary(CacheObjectContext.java:257)
> at
> org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinaryIfNeeded(CacheObjectContext.java:148)
> at
> org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinaryIfNeeded(CacheObjectContext.java:135)
> at
> org.apache.ignite.internal.processors.cache.GridCacheContext.unwrapBinaryIfNeeded(GridCacheContext.java:1757)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.setResult(GridPartitionedSingleGetFuture.java:629)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.localGet(GridPartitionedSingleGetFuture.java:421)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.mapKeyToNode(GridPartitionedSingleGetFuture.java:337)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.map(GridPartitionedSingleGetFuture.java:204)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.init(GridPartitionedSingleGetFuture.java:196)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedCache.getAsync(GridDhtColocatedCache.java:266)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4774)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4758)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1391)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:865)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2483) Cache metrics functionality for client nodes should be developed.
[ https://issues.apache.org/jira/browse/IGNITE-2483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15148760#comment-15148760 ] Vladimir Ershov commented on IGNITE-2483: - PR https://github.com/apache/ignite/pull/479/files is available for a review. Please consider two moments: 1) C# cache.metrics().getSize shows 0 for cache.size=1 on configuration, which works perfectly at pure java. 2) C# doesn't support cache.metrics(ClusterGroup) call. This is important, since default behavior changed and as for now client couldn't get cache.metrics(forLocal) from c#. > Cache metrics functionality for client nodes should be developed. > - > > Key: IGNITE-2483 > URL: https://issues.apache.org/jira/browse/IGNITE-2483 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Valentin Kulichenko >Assignee: Vladimir Ershov > Labels: community > Fix For: 1.6 > > > User list discussion: > http://apache-ignite-users.70518.x6.nabble.com/Is-there-a-way-to-get-cache-metrics-for-all-the-nodes-in-cluster-combined-td2674.html > Currently there are at least three issues with cache metrics: > # When metrics are acquired on client, average put times are always zero. > This happens because timings are calculated on the client, but puts are > counted on servers. > # Size and keySize are always zero even if cache is not empty. > # Default metrics() method that doesn't take a cluster group provides metrics > for local node only. So if it's called on client, they are always empty. It > should calculate metrics for the whole cluster instead. > Also looks like this code is very undertested. Coverage should be > significantly improved. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2649) Ignition.localIgnite() unreliable under Gateways and cause wrong components deserialization.
[
https://issues.apache.org/jira/browse/IGNITE-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ershov updated IGNITE-2649:
Labels: 1.6 community (was: 1.6)
> Ignition.localIgnite() unreliable under Gateways and cause wrong components
> deserialization.
>
>
> Key: IGNITE-2649
> URL: https://issues.apache.org/jira/browse/IGNITE-2649
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ershov
>Assignee: Vladimir Ershov
>Priority: Critical
> Labels: 1.6, community
> Fix For: 1.6
>
> Original Estimate: 8h
> Remaining Estimate: 8h
>
> We can get something like this:
> {noformat}
> java.lang.IllegalArgumentException: This method should be accessed under
> org.apache.ignite.thread.IgniteThread
> at org.apache.ignite.internal.IgnitionEx.localIgnite(IgnitionEx.java:1252)
> at org.apache.ignite.Ignition.localIgnite(Ignition.java:531)
> at org.project.MyPojo.readResolve(MyPojo.java:123)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:746)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1448)
> at
> org.apache.ignite.internal.binary.BinaryUtils.doReadObject(BinaryUtils.java:1564)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readObject(BinaryReaderExImpl.java:1086)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.readFixedType(BinaryFieldAccessor.java:827)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read(BinaryFieldAccessor.java:643)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:734)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1448)
> at
> org.apache.ignite.internal.binary.BinaryUtils.doReadObject(BinaryUtils.java:1564)
> at
> org.apache.ignite.internal.binary.BinaryUtils.deserializeOrUnmarshal(BinaryUtils.java:1908)
> at
> org.apache.ignite.internal.binary.BinaryUtils.doReadMap(BinaryUtils.java:1892)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1595)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readField(BinaryReaderExImpl.java:1644)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read(BinaryFieldAccessor.java:643)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:734)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1448)
> at
> org.apache.ignite.internal.binary.BinaryObjectImpl.deserializeValue(BinaryObjectImpl.java:537)
> at
> org.apache.ignite.internal.binary.BinaryObjectImpl.value(BinaryObjectImpl.java:117)
> at
> org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinary(CacheObjectContext.java:257)
> at
> org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinaryIfNeeded(CacheObjectContext.java:148)
> at
> org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinaryIfNeeded(CacheObjectContext.java:135)
> at
> org.apache.ignite.internal.processors.cache.GridCacheContext.unwrapBinaryIfNeeded(GridCacheContext.java:1757)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.setResult(GridPartitionedSingleGetFuture.java:629)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.localGet(GridPartitionedSingleGetFuture.java:421)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.mapKeyToNode(GridPartitionedSingleGetFuture.java:337)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.map(GridPartitionedSingleGetFuture.java:204)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.init(GridPartitionedSingleGetFuture.java:196)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedCache.getAsync(GridDhtColocatedCache.java:266)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4774)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4758)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1391)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:865)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-10) Fix ignite components [de]serialization
[ https://issues.apache.org/jira/browse/IGNITE-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15147372#comment-15147372 ] Vladimir Ershov commented on IGNITE-10: --- Will be fixed under: https://issues.apache.org/jira/browse/IGNITE-2649 > Fix ignite components [de]serialization > --- > > Key: IGNITE-10 > URL: https://issues.apache.org/jira/browse/IGNITE-10 > Project: Ignite > Issue Type: Task > Components: general >Reporter: Yakov Zhdanov >Assignee: Vladimir Ershov > Labels: Muted_test > Fix For: 1.6 > > > Current solution: serialize grid name, then find comp by name on peer. > Current solution not working: in our internal unit tests, in distributed > topology when user gives different names to nodes > New solution: each grid thread should know its node. So, on deserialization > we cast thread to e.g. IgniteThread and take its holding component from it. > If it is not IgniteThread then exception should be thrown since it is anyway > impossible to deserialize component outside of context. > Suggestion from IGNITE-553: > As we moving to java8 lambdas, it is impossible to use > @IgniteInstanceResource in lambdas. As a result, single-jvm ping-pong test > does not work. > Suggested fix: > Introduce a static thread-local field which will be set before processing a > message and will be nullified after message is processed. IgniteKernal should > check this thread-local in readResolve and return this instance. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2649) Ignition.localIgnite() unreliable under Gateways and cause wrong components deserialization.
Vladimir Ershov created IGNITE-2649:
---
Summary: Ignition.localIgnite() unreliable under Gateways and
cause wrong components deserialization.
Key: IGNITE-2649
URL: https://issues.apache.org/jira/browse/IGNITE-2649
Project: Ignite
Issue Type: Bug
Components: general
Affects Versions: 1.5.0.final
Reporter: Vladimir Ershov
Assignee: Vladimir Ershov
Priority: Critical
Fix For: 1.6
We can get something like this:
{noformat}
java.lang.IllegalArgumentException: This method should be accessed under
org.apache.ignite.thread.IgniteThread
at org.apache.ignite.internal.IgnitionEx.localIgnite(IgnitionEx.java:1252)
at org.apache.ignite.Ignition.localIgnite(Ignition.java:531)
at org.project.MyPojo.readResolve(MyPojo.java:123)
at
org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:746)
at
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1448)
at
org.apache.ignite.internal.binary.BinaryUtils.doReadObject(BinaryUtils.java:1564)
at
org.apache.ignite.internal.binary.BinaryReaderExImpl.readObject(BinaryReaderExImpl.java:1086)
at
org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.readFixedType(BinaryFieldAccessor.java:827)
at
org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read(BinaryFieldAccessor.java:643)
at
org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:734)
at
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1448)
at
org.apache.ignite.internal.binary.BinaryUtils.doReadObject(BinaryUtils.java:1564)
at
org.apache.ignite.internal.binary.BinaryUtils.deserializeOrUnmarshal(BinaryUtils.java:1908)
at
org.apache.ignite.internal.binary.BinaryUtils.doReadMap(BinaryUtils.java:1892)
at
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1595)
at
org.apache.ignite.internal.binary.BinaryReaderExImpl.readField(BinaryReaderExImpl.java:1644)
at
org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read(BinaryFieldAccessor.java:643)
at
org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:734)
at
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1448)
at
org.apache.ignite.internal.binary.BinaryObjectImpl.deserializeValue(BinaryObjectImpl.java:537)
at
org.apache.ignite.internal.binary.BinaryObjectImpl.value(BinaryObjectImpl.java:117)
at
org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinary(CacheObjectContext.java:257)
at
org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinaryIfNeeded(CacheObjectContext.java:148)
at
org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinaryIfNeeded(CacheObjectContext.java:135)
at
org.apache.ignite.internal.processors.cache.GridCacheContext.unwrapBinaryIfNeeded(GridCacheContext.java:1757)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.setResult(GridPartitionedSingleGetFuture.java:629)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.localGet(GridPartitionedSingleGetFuture.java:421)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.mapKeyToNode(GridPartitionedSingleGetFuture.java:337)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.map(GridPartitionedSingleGetFuture.java:204)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.init(GridPartitionedSingleGetFuture.java:196)
at
org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedCache.getAsync(GridDhtColocatedCache.java:266)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4774)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4758)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1391)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:865)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (IGNITE-10) Fix ignite components [de]serialization
[ https://issues.apache.org/jira/browse/IGNITE-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ershov closed IGNITE-10. - Assignee: Vladimir Ershov (was: Valentin Kulichenko) > Fix ignite components [de]serialization > --- > > Key: IGNITE-10 > URL: https://issues.apache.org/jira/browse/IGNITE-10 > Project: Ignite > Issue Type: Task > Components: general >Reporter: Yakov Zhdanov >Assignee: Vladimir Ershov > Labels: Muted_test > Fix For: 1.6 > > > Current solution: serialize grid name, then find comp by name on peer. > Current solution not working: in our internal unit tests, in distributed > topology when user gives different names to nodes > New solution: each grid thread should know its node. So, on deserialization > we cast thread to e.g. IgniteThread and take its holding component from it. > If it is not IgniteThread then exception should be thrown since it is anyway > impossible to deserialize component outside of context. > Suggestion from IGNITE-553: > As we moving to java8 lambdas, it is impossible to use > @IgniteInstanceResource in lambdas. As a result, single-jvm ping-pong test > does not work. > Suggested fix: > Introduce a static thread-local field which will be set before processing a > message and will be nullified after message is processed. IgniteKernal should > check this thread-local in readResolve and return this instance. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-10) Fix ignite components [de]serialization
[ https://issues.apache.org/jira/browse/IGNITE-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ershov resolved IGNITE-10. --- Resolution: Done (was: Fixed) > Fix ignite components [de]serialization > --- > > Key: IGNITE-10 > URL: https://issues.apache.org/jira/browse/IGNITE-10 > Project: Ignite > Issue Type: Task > Components: general >Reporter: Yakov Zhdanov >Assignee: Valentin Kulichenko > Labels: Muted_test > Fix For: 1.6 > > > Current solution: serialize grid name, then find comp by name on peer. > Current solution not working: in our internal unit tests, in distributed > topology when user gives different names to nodes > New solution: each grid thread should know its node. So, on deserialization > we cast thread to e.g. IgniteThread and take its holding component from it. > If it is not IgniteThread then exception should be thrown since it is anyway > impossible to deserialize component outside of context. > Suggestion from IGNITE-553: > As we moving to java8 lambdas, it is impossible to use > @IgniteInstanceResource in lambdas. As a result, single-jvm ping-pong test > does not work. > Suggested fix: > Introduce a static thread-local field which will be set before processing a > message and will be nullified after message is processed. IgniteKernal should > check this thread-local in readResolve and return this instance. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-10) Fix ignite components [de]serialization
[ https://issues.apache.org/jira/browse/IGNITE-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15147178#comment-15147178 ] Vladimir Ershov commented on IGNITE-10: --- Ok, I suppose it's due to calling from Gateway. I'will create a separate ticket for it, since it's a separate task. > Fix ignite components [de]serialization > --- > > Key: IGNITE-10 > URL: https://issues.apache.org/jira/browse/IGNITE-10 > Project: Ignite > Issue Type: Task > Components: general >Reporter: Yakov Zhdanov >Assignee: Valentin Kulichenko > Labels: Muted_test > Fix For: 1.6 > > > Current solution: serialize grid name, then find comp by name on peer. > Current solution not working: in our internal unit tests, in distributed > topology when user gives different names to nodes > New solution: each grid thread should know its node. So, on deserialization > we cast thread to e.g. IgniteThread and take its holding component from it. > If it is not IgniteThread then exception should be thrown since it is anyway > impossible to deserialize component outside of context. > Suggestion from IGNITE-553: > As we moving to java8 lambdas, it is impossible to use > @IgniteInstanceResource in lambdas. As a result, single-jvm ping-pong test > does not work. > Suggested fix: > Introduce a static thread-local field which will be set before processing a > message and will be nullified after message is processed. IgniteKernal should > check this thread-local in readResolve and return this instance. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-10) Fix ignite components [de]serialization
[
https://issues.apache.org/jira/browse/IGNITE-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15147086#comment-15147086
]
Vladimir Ershov commented on IGNITE-10:
---
The fix here is intends to fix case with {code}IgniteInstanceResource{code}
injection. Could you please point any case where we put those entities in
lambdas or smth?
> Fix ignite components [de]serialization
> ---
>
> Key: IGNITE-10
> URL: https://issues.apache.org/jira/browse/IGNITE-10
> Project: Ignite
> Issue Type: Task
> Components: general
>Reporter: Yakov Zhdanov
>Assignee: Vladimir Ershov
> Labels: Muted_test
> Fix For: 1.6
>
>
> Current solution: serialize grid name, then find comp by name on peer.
> Current solution not working: in our internal unit tests, in distributed
> topology when user gives different names to nodes
> New solution: each grid thread should know its node. So, on deserialization
> we cast thread to e.g. IgniteThread and take its holding component from it.
> If it is not IgniteThread then exception should be thrown since it is anyway
> impossible to deserialize component outside of context.
> Suggestion from IGNITE-553:
> As we moving to java8 lambdas, it is impossible to use
> @IgniteInstanceResource in lambdas. As a result, single-jvm ping-pong test
> does not work.
> Suggested fix:
> Introduce a static thread-local field which will be set before processing a
> message and will be nullified after message is processed. IgniteKernal should
> check this thread-local in readResolve and return this instance.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-10) Fix ignite components [de]serialization
[ https://issues.apache.org/jira/browse/IGNITE-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ershov reassigned IGNITE-10: - Assignee: Valentin Kulichenko (was: Vladimir Ershov) > Fix ignite components [de]serialization > --- > > Key: IGNITE-10 > URL: https://issues.apache.org/jira/browse/IGNITE-10 > Project: Ignite > Issue Type: Task > Components: general >Reporter: Yakov Zhdanov >Assignee: Valentin Kulichenko > Labels: Muted_test > Fix For: 1.6 > > > Current solution: serialize grid name, then find comp by name on peer. > Current solution not working: in our internal unit tests, in distributed > topology when user gives different names to nodes > New solution: each grid thread should know its node. So, on deserialization > we cast thread to e.g. IgniteThread and take its holding component from it. > If it is not IgniteThread then exception should be thrown since it is anyway > impossible to deserialize component outside of context. > Suggestion from IGNITE-553: > As we moving to java8 lambdas, it is impossible to use > @IgniteInstanceResource in lambdas. As a result, single-jvm ping-pong test > does not work. > Suggested fix: > Introduce a static thread-local field which will be set before processing a > message and will be nullified after message is processed. IgniteKernal should > check this thread-local in readResolve and return this instance. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-2565) TCK fails when client nodes are particapating in the cluster.
[ https://issues.apache.org/jira/browse/IGNITE-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144314#comment-15144314 ] Vladimir Ershov commented on IGNITE-2565: - Thanks Andrey and Semen for solving this one! I'm seriously, thanks. > TCK fails when client nodes are particapating in the cluster. > - > > Key: IGNITE-2565 > URL: https://issues.apache.org/jira/browse/IGNITE-2565 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 1.5.0.final >Reporter: Anton Vinogradov >Assignee: Semen Boikov >Priority: Critical > Labels: important > Fix For: 1.6 > > > TCK suite fail periodically fails with assetrions about CacheHitPercentage. > I see that a lot of changes was made last two months where added logic with > invoking of metrics.onRead(); possible this affects statictic counting. > Typical stacktrace: > java.lang.AssertionError: expected:<100.0> but was:<50.0> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:743) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:144) > at > org.jsr107.tck.management.CacheMBStatisticsBeanTest.testCacheStatisticsInvokeEntryProcessorRemove(CacheMBStatisticsBeanTest.java:424) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2636) Server cache metrics for put-get-remove avg time are incorrect for case when request sent from client
Vladimir Ershov created IGNITE-2636: --- Summary: Server cache metrics for put-get-remove avg time are incorrect for case when request sent from client Key: IGNITE-2636 URL: https://issues.apache.org/jira/browse/IGNITE-2636 Project: Ignite Issue Type: Bug Components: cache Affects Versions: 1.5.0.final Reporter: Vladimir Ershov Server cache metrics for put-get-remove avg time are incorrect for case when request sent from client. We should add methods like CacheMetrics#addPutAndGetTimeNanos for all flows, when requests for cache modifications are processed. For all type of caches. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2483) Cache metrics functionality for client nodes should be developed.
[ https://issues.apache.org/jira/browse/IGNITE-2483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ershov updated IGNITE-2483: Summary: Cache metrics functionality for client nodes should be developed. (was: Cache metrics bugs) > Cache metrics functionality for client nodes should be developed. > - > > Key: IGNITE-2483 > URL: https://issues.apache.org/jira/browse/IGNITE-2483 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Valentin Kulichenko >Assignee: Vladimir Ershov > Labels: community > Fix For: 1.6 > > > User list discussion: > http://apache-ignite-users.70518.x6.nabble.com/Is-there-a-way-to-get-cache-metrics-for-all-the-nodes-in-cluster-combined-td2674.html > Currently there are at least three issues with cache metrics: > # When metrics are acquired on client, average put times are always zero. > This happens because timings are calculated on the client, but puts are > counted on servers. > # Size and keySize are always zero even if cache is not empty. > # Default metrics() method that doesn't take a cluster group provides metrics > for local node only. So if it's called on client, they are always empty. It > should calculate metrics for the whole cluster instead. > Also looks like this code is very undertested. Coverage should be > significantly improved. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2636) Server cache metrics for put-get-remove avg time are incorrect for case when request sent from client
[ https://issues.apache.org/jira/browse/IGNITE-2636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ershov updated IGNITE-2636: Description: Server cache metrics for put-get-remove avg time are incorrect for case when request sent from client. We should add methods like CacheMetrics#addPutAndGetTimeNanos for all flows, when requests for cache modifications are processed. For all type of caches. This will fix CacheMetricsForClusterGroupSelfTest was: Server cache metrics for put-get-remove avg time are incorrect for case when request sent from client. We should add methods like CacheMetrics#addPutAndGetTimeNanos for all flows, when requests for cache modifications are processed. For all type of caches. > Server cache metrics for put-get-remove avg time are incorrect for case when > request sent from client > - > > Key: IGNITE-2636 > URL: https://issues.apache.org/jira/browse/IGNITE-2636 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 1.5.0.final >Reporter: Vladimir Ershov > Original Estimate: 120h > Remaining Estimate: 120h > > Server cache metrics for put-get-remove avg time are incorrect for case when > request sent from client. > We should add methods like CacheMetrics#addPutAndGetTimeNanos for all flows, > when requests for cache modifications are processed. For all type of caches. > This will fix CacheMetricsForClusterGroupSelfTest -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2509) Broken eviction and metrics for OFFHEAP_VALUES cache mode
[
https://issues.apache.org/jira/browse/IGNITE-2509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ershov updated IGNITE-2509:
Assignee: Alexey Goncharuk (was: Vladimir Ershov)
> Broken eviction and metrics for OFFHEAP_VALUES cache mode
> -
>
> Key: IGNITE-2509
> URL: https://issues.apache.org/jira/browse/IGNITE-2509
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5.0.final
>Reporter: Denis Magda
>Assignee: Alexey Goncharuk
>Priority: Blocker
> Fix For: 1.6
>
> Attachments: EvictionBug.java, eviction_fix.patch
>
>
> In case when {{OFFHEAP_VALUES}} mode is used {{EvictionPolicy}} calculates
> values size wrongly which leads to the fact that data is evicted only when
> either the limit on number of entries is reached or size of keys is bigger
> than max allowed size.
> To reproduce set the following cache configuration
> {noformat}
> FifoEvictionPolicy plc = new FifoEvictionPolicy();
> plc.setMaxMemorySize(2 * 1024 * 1024);
> cacheCfg.setEvictionPolicy(plc);
> cacheCfg.setMemoryMode(CacheMemoryMode.OFFHEAP_VALUES);
> cacheCfg.setSwapEnabled(true);
> {noformat}
> Test that reproduces the issue is attached.
> Also attached a patch that fixes the issue. However we should validate that
> the fix is full and add additional tests to the test suites.
> Finally, {{cache.metrics().getOffHeapAllocatedSize()}} always returns 0 for
> this cache mode. Has to be fixed as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2405) Ignite is blocking the thread in case it can't connect to the node
[
https://issues.apache.org/jira/browse/IGNITE-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144701#comment-15144701
]
Vladimir Ershov commented on IGNITE-2405:
-
Well, logs are fine, I've ran your code locally and everything also works fine.
Let's try this fast check:
In separated package create and run IgniteTest code:
{noformat}
public class IgniteTest {
public static void main(String... args) throws UnknownHostException {
String nodeHost = InetAddress.getLocalHost().getHostName();
IgniteConfiguration configuration = getClusterConfiguration(nodeHost,
47500);
Ignite igniteNode = Ignition.start(configuration);
int numberOfNodes = igniteNode.cluster().nodes().size();
System.out.println(1 == numberOfNodes);
}
private static IgniteConfiguration getClusterConfiguration(String nodeHost,
int port) {
TcpDiscoverySpi spi = new TcpDiscoverySpi();
TcpDiscoveryVmIpFinder ipFinder = new TcpDiscoveryVmIpFinder();
ipFinder.setAddresses(Arrays.asList(nodeHost+ ":47500..47600"));
//ipFinder.setAddresses(Collections.singletonList(nodeHost + ':' +
port));
spi.setIpFinder(ipFinder);
IgniteConfiguration configuration = new IgniteConfiguration();
configuration.setDiscoverySpi(spi);
configuration.setIncludeEventTypes(EventType.EVTS_DISCOVERY);
return configuration;
}
}
{noformat}
And be sure you are given at least *5min* for node to print *true*
> Ignite is blocking the thread in case it can't connect to the node
> --
>
> Key: IGNITE-2405
> URL: https://issues.apache.org/jira/browse/IGNITE-2405
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5.0.final
>Reporter: Miron Aseev
> Labels: community, newbie
> Attachments: log.out, log.out
>
>
> It seems that Apache Ignite runs an infinite loop if it can't connect to the
> resolved hostname.
> For example, if you specify the hostname of the local machine as an address
> for the TCPSpi, then Apache Ignite resolves it
> [here|https://github.com/apache/ignite/blob/b3d347e35a254928fd1c4a0473f1b17d642c72f3/modules/core/src/main/java/org/apache/ignite/spi/discovery/tcp/ServerImpl.java#L915].
>
> But after that, for some reasons, it fails to connect to the resolved address
> [here|https://github.com/apache/ignite/blob/b3d347e35a254928fd1c4a0473f1b17d642c72f3/modules/core/src/main/java/org/apache/ignite/spi/discovery/tcp/ServerImpl.java#L925].
>
> As a result, the control flow goes to the catch block where the exception is
> logged (It's an IgniteSpiException. It seems it can't get acces to the host
> according to the exception message - "Network operation timed out. Increase
> 'failureDetectionTimeout' configuration property
> [failureDetectionTimeout=1]").
> In the end, we get an infinite loop.
> On the other hand, If I set an ip address (127.0.0.1) instead of the
> hostname, Ignite gets an empty list
> [here|https://github.com/apache/ignite/blob/b3d347e35a254928fd1c4a0473f1b17d642c72f3/modules/core/src/main/java/org/apache/ignite/spi/discovery/tcp/ServerImpl.java#L915]
> and the control flow breaks the loop
> [here|https://github.com/apache/ignite/blob/b3d347e35a254928fd1c4a0473f1b17d642c72f3/modules/core/src/main/java/org/apache/ignite/spi/discovery/tcp/ServerImpl.java#L918]
> and goes forward.
> Here's a log information which Ignite produces during its work.
> {code}
> Jan 19, 2016 7:33:02 PM java.util.logging.LogManager$RootLogger log
> SEVERE: Failed to resolve default logging config file:
> config/java.util.logging.properties
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO:
> >>>__
> >>> / _/ ___/ |/ / _/_ __/ __/
> >>> _/ // (7 7// / / / / _/
> >>> /___/\___/_/|_/___/ /_/ /___/
> >>>
> >>> ver. 1.5.0-final#20151229-sha1:f1f8cda2
> >>> 2015 Copyright(C) Apache Software Foundation
> >>>
> >>> Ignite documentation: http://ignite.apache.org
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO: Config URL: n/a
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO: Daemon mode: off
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO: OS: Linux 3.13.0-74-generic amd64
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO: OS user: maseev
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO: Language runtime: Java Platform API Specification ver. 1.8
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO: VM information: Java(TM) SE Runtime Environment 1.8.0_40-b26 Oracle
> Corporation Java HotSpot(TM) 64-Bit Server VM 25.40-b25
> Jan 19, 2016 7:33:03
[jira] [Commented] (IGNITE-2565) TCK suite fail periodically
[
https://issues.apache.org/jira/browse/IGNITE-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15142459#comment-15142459
]
Vladimir Ershov commented on IGNITE-2565:
-
I've take a look on some of that typical issues and it looks like they are
actually not typical and have different reasons. The last one:
{noformat}
java.lang.AssertionError: expected:<0> but was:<1>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:743)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at
org.jsr107.tck.management.CacheMBStatisticsBeanTest.testCacheStatistics(CacheMBStatisticsBeanTest.java:104)
{noformat}
Most likely to be related with counting miss logic on the server side, which is
not linked to IGNITE-2483, and should be fixed at separated ticket.
> TCK suite fail periodically
> ---
>
> Key: IGNITE-2565
> URL: https://issues.apache.org/jira/browse/IGNITE-2565
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.5.0.final
>Reporter: Anton Vinogradov
>Assignee: Vladimir Ershov
>Priority: Critical
> Labels: important
> Fix For: 1.6
>
>
> TCK suite fail periodically fails with assetrions about CacheHitPercentage.
> I see that a lot of changes was made last two months where added logic with
> invoking of metrics.onRead(); possible this affects statictic counting.
> Typical stacktrace:
> java.lang.AssertionError: expected:<100.0> but was:<50.0>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:743)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at org.junit.Assert.assertEquals(Assert.java:144)
> at
> org.jsr107.tck.management.CacheMBStatisticsBeanTest.testCacheStatisticsInvokeEntryProcessorRemove(CacheMBStatisticsBeanTest.java:424)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2565) TCK fails when client nodes are particapating in the cluster.
[ https://issues.apache.org/jira/browse/IGNITE-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ershov updated IGNITE-2565: Summary: TCK fails when client nodes are particapating in the cluster. (was: TCK suite fail periodically) > TCK fails when client nodes are particapating in the cluster. > - > > Key: IGNITE-2565 > URL: https://issues.apache.org/jira/browse/IGNITE-2565 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 1.5.0.final >Reporter: Anton Vinogradov >Assignee: Vladimir Ershov >Priority: Critical > Labels: important > Fix For: 1.6 > > > TCK suite fail periodically fails with assetrions about CacheHitPercentage. > I see that a lot of changes was made last two months where added logic with > invoking of metrics.onRead(); possible this affects statictic counting. > Typical stacktrace: > java.lang.AssertionError: expected:<100.0> but was:<50.0> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:743) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:144) > at > org.jsr107.tck.management.CacheMBStatisticsBeanTest.testCacheStatisticsInvokeEntryProcessorRemove(CacheMBStatisticsBeanTest.java:424) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-2509) Broken eviction and metrics for OFFHEAP_VALUES cache mode
[
https://issues.apache.org/jira/browse/IGNITE-2509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15142470#comment-15142470
]
Vladimir Ershov commented on IGNITE-2509:
-
Found out separated problem with it. Would be fixed under IGNITE-2483. This
ticket is ready, please review this PR :
https://github.com/apache/ignite/pull/470/files
> Broken eviction and metrics for OFFHEAP_VALUES cache mode
> -
>
> Key: IGNITE-2509
> URL: https://issues.apache.org/jira/browse/IGNITE-2509
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5.0.final
>Reporter: Denis Magda
>Assignee: Vladimir Ershov
>Priority: Blocker
> Fix For: 1.6
>
> Attachments: EvictionBug.java, eviction_fix.patch
>
>
> In case when {{OFFHEAP_VALUES}} mode is used {{EvictionPolicy}} calculates
> values size wrongly which leads to the fact that data is evicted only when
> either the limit on number of entries is reached or size of keys is bigger
> than max allowed size.
> To reproduce set the following cache configuration
> {noformat}
> FifoEvictionPolicy plc = new FifoEvictionPolicy();
> plc.setMaxMemorySize(2 * 1024 * 1024);
> cacheCfg.setEvictionPolicy(plc);
> cacheCfg.setMemoryMode(CacheMemoryMode.OFFHEAP_VALUES);
> cacheCfg.setSwapEnabled(true);
> {noformat}
> Test that reproduces the issue is attached.
> Also attached a patch that fixes the issue. However we should validate that
> the fix is full and add additional tests to the test suites.
> Finally, {{cache.metrics().getOffHeapAllocatedSize()}} always returns 0 for
> this cache mode. Has to be fixed as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2565) TCK suite fail periodically
[ https://issues.apache.org/jira/browse/IGNITE-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15140850#comment-15140850 ] Vladimir Ershov commented on IGNITE-2565: - Most likely due to client nodes in the cluster. > TCK suite fail periodically > --- > > Key: IGNITE-2565 > URL: https://issues.apache.org/jira/browse/IGNITE-2565 > Project: Ignite > Issue Type: Bug >Affects Versions: 1.5.0.final >Reporter: Anton Vinogradov > Fix For: 1.6 > > > TCK suite fail periodically fails with assetrions about CacheHitPercentage. > I see that a lot of changes was made last two months where added logic with > invoking of metrics.onRead(); possible this affects statictic counting. > Typical stacktrace: > java.lang.AssertionError: expected:<100.0> but was:<50.0> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:743) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:144) > at > org.jsr107.tck.management.CacheMBStatisticsBeanTest.testCacheStatisticsInvokeEntryProcessorRemove(CacheMBStatisticsBeanTest.java:424) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2616) NonHeap memory usage metrics don't work as expected.
[
https://issues.apache.org/jira/browse/IGNITE-2616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ershov updated IGNITE-2616:
Attachment: ClusterMetricsOnCacheSelfTest.java
This test should be included, after offHeap metrics is fixed.
> NonHeap memory usage metrics don't work as expected.
>
>
> Key: IGNITE-2616
> URL: https://issues.apache.org/jira/browse/IGNITE-2616
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ershov
>Priority: Minor
> Attachments: ClusterMetricsOnCacheSelfTest.java
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> This simple code:
> {noformat}
> public static void main(String ... args) {
> MemoryMXBean mxBean = ManagementFactory.getMemoryMXBean();
> System.out.println(mxBean.getNonHeapMemoryUsage());
> GridUnsafeMemory uMem = new GridUnsafeMemory(1024L * 1024 * 1024 *
> 3); //3GB
> System.out.println(mxBean.getNonHeapMemoryUsage());
> uMem.allocate(1024 * 1024 * 1024, true, false);
> System.out.println(mxBean.getNonHeapMemoryUsage());
> uMem.allocate(1024 * 1024 * 1024, true, true);
> System.out.println(mxBean.getNonHeapMemoryUsage());
> }
> {noformat}
> shows:
> {noformat}
> init = 2555904(2496K) used = 4783352(4671K) committed = 8060928(7872K) max =
> -1(-1K)
> init = 2555904(2496K) used = 5018704(4901K) committed = 8060928(7872K) max =
> -1(-1K)
> init = 2555904(2496K) used = 5018960(4901K) committed = 8060928(7872K) max =
> -1(-1K)
> init = 2555904(2496K) used = 5018960(4901K) committed = 8060928(7872K) max =
> -1(-1K)
> {noformat}
> which means: offHeap metrics are incorrect. The problem is: Apache Ignite
> uses that MemoryMXBean for collecting metrics, thus Apache Ignite offHeap
> metrics are incorrect too. We should find the way to fix this, if there are
> any.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-2616) NonHeap memory usage metrics don't work as expected.
Vladimir Ershov created IGNITE-2616:
---
Summary: NonHeap memory usage metrics don't work as expected.
Key: IGNITE-2616
URL: https://issues.apache.org/jira/browse/IGNITE-2616
Project: Ignite
Issue Type: Bug
Components: general
Affects Versions: 1.5.0.final
Reporter: Vladimir Ershov
Priority: Minor
This simple code:
{noformat}
public static void main(String ... args) {
MemoryMXBean mxBean = ManagementFactory.getMemoryMXBean();
System.out.println(mxBean.getNonHeapMemoryUsage());
GridUnsafeMemory uMem = new GridUnsafeMemory(1024L * 1024 * 1024 * 3);
//3GB
System.out.println(mxBean.getNonHeapMemoryUsage());
uMem.allocate(1024 * 1024 * 1024, true, false);
System.out.println(mxBean.getNonHeapMemoryUsage());
uMem.allocate(1024 * 1024 * 1024, true, true);
System.out.println(mxBean.getNonHeapMemoryUsage());
}
{noformat}
shows:
{noformat}
init = 2555904(2496K) used = 4783352(4671K) committed = 8060928(7872K) max =
-1(-1K)
init = 2555904(2496K) used = 5018704(4901K) committed = 8060928(7872K) max =
-1(-1K)
init = 2555904(2496K) used = 5018960(4901K) committed = 8060928(7872K) max =
-1(-1K)
init = 2555904(2496K) used = 5018960(4901K) committed = 8060928(7872K) max =
-1(-1K)
{noformat}
which means: offHeap metrics are incorrect. The problem is: Apache Ignite uses
that MemoryMXBean for collecting metrics, thus Apache Ignite offHeap metrics
are incorrect too. We should find the way to fix this, if there are any.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2509) Broken eviction and metrics for OFFHEAP_VALUES cache mode
[
https://issues.apache.org/jira/browse/IGNITE-2509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15138557#comment-15138557
]
Vladimir Ershov commented on IGNITE-2509:
-
Denis,
Thanks for checking! Could you please take a look at the test
GridCacheOffHeapValuesEvictionSelfTest that was added for preventing such cases
and advise about conf permutation for reproduction?
> Broken eviction and metrics for OFFHEAP_VALUES cache mode
> -
>
> Key: IGNITE-2509
> URL: https://issues.apache.org/jira/browse/IGNITE-2509
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5.0.final
>Reporter: Denis Magda
>Assignee: Denis Magda
>Priority: Blocker
> Fix For: 1.6
>
> Attachments: EvictionBug.java, eviction_fix.patch
>
>
> In case when {{OFFHEAP_VALUES}} mode is used {{EvictionPolicy}} calculates
> values size wrongly which leads to the fact that data is evicted only when
> either the limit on number of entries is reached or size of keys is bigger
> than max allowed size.
> To reproduce set the following cache configuration
> {noformat}
> FifoEvictionPolicy plc = new FifoEvictionPolicy();
> plc.setMaxMemorySize(2 * 1024 * 1024);
> cacheCfg.setEvictionPolicy(plc);
> cacheCfg.setMemoryMode(CacheMemoryMode.OFFHEAP_VALUES);
> cacheCfg.setSwapEnabled(true);
> {noformat}
> Test that reproduces the issue is attached.
> Also attached a patch that fixes the issue. However we should validate that
> the fix is full and add additional tests to the test suites.
> Finally, {{cache.metrics().getOffHeapAllocatedSize()}} always returns 0 for
> this cache mode. Has to be fixed as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Reopened] (IGNITE-2509) Broken eviction and metrics for OFFHEAP_VALUES cache mode
[
https://issues.apache.org/jira/browse/IGNITE-2509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ershov reopened IGNITE-2509:
-
Assignee: Vladimir Ershov (was: Denis Magda)
testPutOnHeap misses getOffHeapAllocatedSize check.
> Broken eviction and metrics for OFFHEAP_VALUES cache mode
> -
>
> Key: IGNITE-2509
> URL: https://issues.apache.org/jira/browse/IGNITE-2509
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5.0.final
>Reporter: Denis Magda
>Assignee: Vladimir Ershov
>Priority: Blocker
> Fix For: 1.6
>
> Attachments: EvictionBug.java, eviction_fix.patch
>
>
> In case when {{OFFHEAP_VALUES}} mode is used {{EvictionPolicy}} calculates
> values size wrongly which leads to the fact that data is evicted only when
> either the limit on number of entries is reached or size of keys is bigger
> than max allowed size.
> To reproduce set the following cache configuration
> {noformat}
> FifoEvictionPolicy plc = new FifoEvictionPolicy();
> plc.setMaxMemorySize(2 * 1024 * 1024);
> cacheCfg.setEvictionPolicy(plc);
> cacheCfg.setMemoryMode(CacheMemoryMode.OFFHEAP_VALUES);
> cacheCfg.setSwapEnabled(true);
> {noformat}
> Test that reproduces the issue is attached.
> Also attached a patch that fixes the issue. However we should validate that
> the fix is full and add additional tests to the test suites.
> Finally, {{cache.metrics().getOffHeapAllocatedSize()}} always returns 0 for
> this cache mode. Has to be fixed as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2509) Broken eviction and metrics for OFFHEAP_VALUES cache mode
[
https://issues.apache.org/jira/browse/IGNITE-2509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15138911#comment-15138911
]
Vladimir Ershov commented on IGNITE-2509:
-
Got the point, will do.
Thanks!
> Broken eviction and metrics for OFFHEAP_VALUES cache mode
> -
>
> Key: IGNITE-2509
> URL: https://issues.apache.org/jira/browse/IGNITE-2509
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5.0.final
>Reporter: Denis Magda
>Assignee: Vladimir Ershov
>Priority: Blocker
> Fix For: 1.6
>
> Attachments: EvictionBug.java, eviction_fix.patch
>
>
> In case when {{OFFHEAP_VALUES}} mode is used {{EvictionPolicy}} calculates
> values size wrongly which leads to the fact that data is evicted only when
> either the limit on number of entries is reached or size of keys is bigger
> than max allowed size.
> To reproduce set the following cache configuration
> {noformat}
> FifoEvictionPolicy plc = new FifoEvictionPolicy();
> plc.setMaxMemorySize(2 * 1024 * 1024);
> cacheCfg.setEvictionPolicy(plc);
> cacheCfg.setMemoryMode(CacheMemoryMode.OFFHEAP_VALUES);
> cacheCfg.setSwapEnabled(true);
> {noformat}
> Test that reproduces the issue is attached.
> Also attached a patch that fixes the issue. However we should validate that
> the fix is full and add additional tests to the test suites.
> Finally, {{cache.metrics().getOffHeapAllocatedSize()}} always returns 0 for
> this cache mode. Has to be fixed as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-1783) Remove GridBoundedConcurrentLinkedHashMap and replace its usages with ConcurrentLinkedHashMap
[
https://issues.apache.org/jira/browse/IGNITE-1783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ershov reassigned IGNITE-1783:
---
Assignee: (was: Vladimir Ershov)
> Remove GridBoundedConcurrentLinkedHashMap and replace its usages with
> ConcurrentLinkedHashMap
> -
>
> Key: IGNITE-1783
> URL: https://issues.apache.org/jira/browse/IGNITE-1783
> Project: Ignite
> Issue Type: Task
>Reporter: Yakov Zhdanov
>Priority: Trivial
> Labels: newbie
>
> From what I see {{GridBoundedConcurrentLinkedHashMap}} is redundant and the
> only difference from {{ConcurrentLinkedHashMap}} is in order of constructor
> arguments.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2539) NPE at RendezvousAffinityFunction
[ https://issues.apache.org/jira/browse/IGNITE-2539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15136745#comment-15136745 ] Vladimir Ershov commented on IGNITE-2539: - PR is ready, please, review. > NPE at RendezvousAffinityFunction > - > > Key: IGNITE-2539 > URL: https://issues.apache.org/jira/browse/IGNITE-2539 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 1.5.0.final >Reporter: Vladimir Ershov >Assignee: Vladimir Ershov >Priority: Critical > Attachments: ignite.log > > Original Estimate: 4h > Remaining Estimate: 4h > > RendezvousAffinityFunction#assignPartition throws NPE, probably due to > simultaneous topology change and cache stop. We should write a test and fix > this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2585) Force Unit tests to fail in case of NPE in logs.
Vladimir Ershov created IGNITE-2585: --- Summary: Force Unit tests to fail in case of NPE in logs. Key: IGNITE-2585 URL: https://issues.apache.org/jira/browse/IGNITE-2585 Project: Ignite Issue Type: Improvement Components: build Reporter: Vladimir Ershov As for now NPE could be thrown from separated threads, without affecting the test result, but still appears in logs. Since it's not possible for one to review thousands of logs after his commit, we can inject in our GridAbstractTest special FailOnMessageLogger logger, that will fail test in case NPE appears in log. Though this change could affect tests, that expects NPE to be thrown. FailOnMessageLogger should be switch off for that tests. Expected amount of such test: 16. Should not take a lot of time. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-2405) Ignite is blocking the thread in case it can't connect to the node
[
https://issues.apache.org/jira/browse/IGNITE-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15136984#comment-15136984
]
Vladimir Ershov commented on IGNITE-2405:
-
Good.
I've looked through logs and spotted those messages:
{noformat}
2016-02-04 22:58:21,839 [main] DEBUG
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi - Failed to send join
request message [addr=evilmachine/127.0.1.1:47500, msg=Failed to send message
to address [addr=evilmachine/127.0.1.1:47500,
msg=TcpDiscoveryJoinRequestMessage [node=TcpDiscoveryNode
[id=7950709d-5888-44a0-b06e-d596b39f6211, addrs=[0:0:0:0:0:0:0:1%lo, 127.0.0.1,
172.17.0.1, 192.168.88.252], sockAddrs=[/172.17.0.1:47500,
/0:0:0:0:0:0:0:1%lo:47500, /192.168.88.252:47500, /127.0.0.1:47500,
/172.17.0.1:47500, /192.168.88.252:47500], discPort=47500, order=0, intOrder=0,
lastExchangeTime=1454605091735, loc=true, ver=1.5.0#20151229-sha1:f1f8cda2,
isClient=false], super=TcpDiscoveryAbstractMessage [sndNodeId=null,
id=2a1483da251-7950709d-5888-44a0-b06e-d596b39f6211, verifierNodeId=null,
topVer=0, pendingIdx=0, failedNodes=null, isClient=false
2016-02-04 22:58:21,839 [main] DEBUG
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi - Failed to send join
request message [addr=evilmachine/127.0.1.1:47500, msg=Failed to send message
to address [addr=evilmachine/127.0.1.1:47500,
msg=TcpDiscoveryJoinRequestMessage [node=TcpDiscoveryNode
[id=7950709d-5888-44a0-b06e-d596b39f6211, addrs=[0:0:0:0:0:0:0:1%lo, 127.0.0.1,
172.17.0.1, 192.168.88.252], sockAddrs=[/172.17.0.1:47500,
/0:0:0:0:0:0:0:1%lo:47500, /192.168.88.252:47500, /127.0.0.1:47500,
/172.17.0.1:47500, /192.168.88.252:47500], discPort=47500, order=0, intOrder=0,
lastExchangeTime=1454605091735, loc=true, ver=1.5.0#20151229-sha1:f1f8cda2,
isClient=false], super=TcpDiscoveryAbstractMessage [sndNodeId=null,
id=2a1483da251-7950709d-5888-44a0-b06e-d596b39f6211, verifierNodeId=null,
topVer=0, pendingIdx=0, failedNodes=null, isClient=false
{noformat}
{quote}
evilmachine/127.0.1.1:47500,
{quote}
It looks like typo in ignite confs or in your host env somewhere. Could you
check this one please?
> Ignite is blocking the thread in case it can't connect to the node
> --
>
> Key: IGNITE-2405
> URL: https://issues.apache.org/jira/browse/IGNITE-2405
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5.0.final
>Reporter: Miron Aseev
> Labels: community, newbie
> Attachments: log.out
>
>
> It seems that Apache Ignite runs an infinite loop if it can't connect to the
> resolved hostname.
> For example, if you specify the hostname of the local machine as an address
> for the TCPSpi, then Apache Ignite resolves it
> [here|https://github.com/apache/ignite/blob/b3d347e35a254928fd1c4a0473f1b17d642c72f3/modules/core/src/main/java/org/apache/ignite/spi/discovery/tcp/ServerImpl.java#L915].
>
> But after that, for some reasons, it fails to connect to the resolved address
> [here|https://github.com/apache/ignite/blob/b3d347e35a254928fd1c4a0473f1b17d642c72f3/modules/core/src/main/java/org/apache/ignite/spi/discovery/tcp/ServerImpl.java#L925].
>
> As a result, the control flow goes to the catch block where the exception is
> logged (It's an IgniteSpiException. It seems it can't get acces to the host
> according to the exception message - "Network operation timed out. Increase
> 'failureDetectionTimeout' configuration property
> [failureDetectionTimeout=1]").
> In the end, we get an infinite loop.
> On the other hand, If I set an ip address (127.0.0.1) instead of the
> hostname, Ignite gets an empty list
> [here|https://github.com/apache/ignite/blob/b3d347e35a254928fd1c4a0473f1b17d642c72f3/modules/core/src/main/java/org/apache/ignite/spi/discovery/tcp/ServerImpl.java#L915]
> and the control flow breaks the loop
> [here|https://github.com/apache/ignite/blob/b3d347e35a254928fd1c4a0473f1b17d642c72f3/modules/core/src/main/java/org/apache/ignite/spi/discovery/tcp/ServerImpl.java#L918]
> and goes forward.
> Here's a log information which Ignite produces during its work.
> {code}
> Jan 19, 2016 7:33:02 PM java.util.logging.LogManager$RootLogger log
> SEVERE: Failed to resolve default logging config file:
> config/java.util.logging.properties
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO:
> >>>__
> >>> / _/ ___/ |/ / _/_ __/ __/
> >>> _/ // (7 7// / / / / _/
> >>> /___/\___/_/|_/___/ /_/ /___/
> >>>
> >>> ver. 1.5.0-final#20151229-sha1:f1f8cda2
> >>> 2015 Copyright(C) Apache Software Foundation
> >>>
> >>> Ignite documentation: http://ignite.apache.org
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO: Config URL: n/a
> Jan 19, 2016 7:33:03 PM
[jira] [Created] (IGNITE-2569) Ignite GridComponent used incorrectly during IgniteStart. Could cause NPE
Vladimir Ershov created IGNITE-2569:
---
Summary: Ignite GridComponent used incorrectly during IgniteStart.
Could cause NPE
Key: IGNITE-2569
URL: https://issues.apache.org/jira/browse/IGNITE-2569
Project: Ignite
Issue Type: Task
Components: general
Affects Versions: 1.5.0.final
Reporter: Vladimir Ershov
Priority: Minor
IgniteKernal could stop GridComponents during start without calling stopKernal
before it. Showcase:
{noformat}
19:09:58,301][ERROR][async-runner-1][IgniteClientReconnectCacheTest3] Failed to
pre-stop processor: GridProcessorAdapter []
java.lang.AssertionError
at
org.apache.ignite.internal.processors.cache.GridCacheSharedManagerAdapter.onKernalStop(GridCacheSharedManagerAdapter.java:109)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStop(GridCacheProcessor.java:884)
at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:1814)
at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:1760)
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:932)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1687)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1546)
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1002)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:533)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:514)
at org.apache.ignite.Ignition.start(Ignition.java:322)
at
org.apache.ignite.internal.IgniteClientReconnectCacheTest$8.call(IgniteClientReconnectCacheTest.java:700)
at
org.apache.ignite.internal.IgniteClientReconnectCacheTest$8.call(IgniteClientReconnectCacheTest.java:697)
at org.apache.ignite.testframework.GridTestUtils$6.run(GridTestUtils.java:758)
at
org.apache.ignite.testframework.GridTestUtils$8.call(GridTestUtils.java:1054)
at org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
{noformat}
This can cause different NPE.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-172) [Test] [Rare] GridTcpCommunicationSpiRecoveryAckSelfTest and IgniteTcpCommunicationRecoveryAckClosureSelfTest
[ https://issues.apache.org/jira/browse/IGNITE-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ershov updated IGNITE-172: --- Summary: [Test] [Rare] GridTcpCommunicationSpiRecoveryAckSelfTest and IgniteTcpCommunicationRecoveryAckClosureSelfTest (was: GridTcpCommunicationSpiRecoveryAckSelfTest and IgniteTcpCommunicationRecoveryAckClosureSelfTest) > [Test] [Rare] GridTcpCommunicationSpiRecoveryAckSelfTest and > IgniteTcpCommunicationRecoveryAckClosureSelfTest > - > > Key: IGNITE-172 > URL: https://issues.apache.org/jira/browse/IGNITE-172 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 1.5.0.final >Reporter: Irina Vasilinets > Labels: Muted_test > > GridTcpCommunicationSpiRecoveryAckSelfTest.testQueueOverflow and > GridTcpCommunicationSpiTcpNoDelayOffSelfTest.testSendToManyNodes > fail sometimes. > IgniteTcpCommunicationRecoveryAckClosureSelfTest.testQueueOverflow - 1 from 10 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2372) [Test] [Rare] GridCacheAbstractDataStructuresFailoverSelfTest.testQueueConstant* fail sometimes
[ https://issues.apache.org/jira/browse/IGNITE-2372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ershov updated IGNITE-2372: Summary: [Test] [Rare] GridCacheAbstractDataStructuresFailoverSelfTest.testQueueConstant* fail sometimes (was: GridCacheAbstractDataStructuresFailoverSelfTest.testQueueConstant* fail sometimes) > [Test] [Rare] > GridCacheAbstractDataStructuresFailoverSelfTest.testQueueConstant* fail > sometimes > --- > > Key: IGNITE-2372 > URL: https://issues.apache.org/jira/browse/IGNITE-2372 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak >Assignee: Denis Magda > Fix For: 1.6 > > Attachments: > Ignite_Tests_Ignite_Binary_Objects_Data_Strucutures_327_artifacts.zip > > > The following tests fail on TC sometimes: > - > GridCachePartitionedDataStructuresFailoverSelfTest.testQueueConstantMultipleTopologyChange > > - > GridCachePartitionedOffheapDataStructuresFailoverSelfTest.testQueueConstantMultipleTopologyChange > > TC build: > http://ci.ignite.apache.org/viewLog.html?buildId=95910=buildResultsDiv=IgniteTests_IgniteDataStrucutures > Test testQueueConstantMultipleTopologyChange failed on my laptop too. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-2509) Broken eviction for OFFHEAP_VALUES cache mode
[
https://issues.apache.org/jira/browse/IGNITE-2509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15131999#comment-15131999
]
Vladimir Ershov commented on IGNITE-2509:
-
Patch applied. Tests added.
As for the cache.metrics().getOffHeapAllocatedSize() - it works fine after the
patch. Check for it was included into the test. Case, when we request it from
client is developed under https://issues.apache.org/jira/browse/IGNITE-2483
> Broken eviction for OFFHEAP_VALUES cache mode
> -
>
> Key: IGNITE-2509
> URL: https://issues.apache.org/jira/browse/IGNITE-2509
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5.0.final
>Reporter: Denis Magda
>Assignee: Vladimir Ershov
>Priority: Blocker
> Fix For: 1.6
>
> Attachments: EvictionBug.java, eviction_fix.patch
>
>
> In case when {{OFFHEAP_VALUES}} mode is used {{EvictionPolicy}} calculates
> values size wrongly which leads to the fact that data is evicted only when
> either the limit on number of entries is reached or size of keys is bigger
> than max allowed size.
> To reproduce set the following cache configuration
> {noformat}
> FifoEvictionPolicy plc = new FifoEvictionPolicy();
> plc.setMaxMemorySize(2 * 1024 * 1024);
> cacheCfg.setEvictionPolicy(plc);
> cacheCfg.setMemoryMode(CacheMemoryMode.OFFHEAP_VALUES);
> cacheCfg.setSwapEnabled(true);
> {noformat}
> Test that reproduces the issue is attached.
> Also attached a patch that fixes the issue. However we should validate that
> the fix is full and add additional tests to the test suites.
> Finally, {{cache.metrics().getOffHeapAllocatedSize()}} always returns 0 for
> this cache mode. Has to be fixed as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2509) Broken eviction for OFFHEAP_VALUES cache mode
[
https://issues.apache.org/jira/browse/IGNITE-2509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15132019#comment-15132019
]
Vladimir Ershov commented on IGNITE-2509:
-
Please, review: https://github.com/apache/ignite/pull/452
> Broken eviction for OFFHEAP_VALUES cache mode
> -
>
> Key: IGNITE-2509
> URL: https://issues.apache.org/jira/browse/IGNITE-2509
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5.0.final
>Reporter: Denis Magda
>Assignee: Vladimir Ershov
>Priority: Blocker
> Fix For: 1.6
>
> Attachments: EvictionBug.java, eviction_fix.patch
>
>
> In case when {{OFFHEAP_VALUES}} mode is used {{EvictionPolicy}} calculates
> values size wrongly which leads to the fact that data is evicted only when
> either the limit on number of entries is reached or size of keys is bigger
> than max allowed size.
> To reproduce set the following cache configuration
> {noformat}
> FifoEvictionPolicy plc = new FifoEvictionPolicy();
> plc.setMaxMemorySize(2 * 1024 * 1024);
> cacheCfg.setEvictionPolicy(plc);
> cacheCfg.setMemoryMode(CacheMemoryMode.OFFHEAP_VALUES);
> cacheCfg.setSwapEnabled(true);
> {noformat}
> Test that reproduces the issue is attached.
> Also attached a patch that fixes the issue. However we should validate that
> the fix is full and add additional tests to the test suites.
> Finally, {{cache.metrics().getOffHeapAllocatedSize()}} always returns 0 for
> this cache mode. Has to be fixed as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-2539) NPE at RendezvousAffinityFunction
Vladimir Ershov created IGNITE-2539: --- Summary: NPE at RendezvousAffinityFunction Key: IGNITE-2539 URL: https://issues.apache.org/jira/browse/IGNITE-2539 Project: Ignite Issue Type: Bug Components: cache Affects Versions: 1.5.0.final Reporter: Vladimir Ershov Priority: Critical RendezvousAffinityFunction#assignPartition throws NPE, probably due to simultaneous topology change and cache stop. We should write a test and fix this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-2405) Ignite is blocking the thread in case it can't connect to the node
[
https://issues.apache.org/jira/browse/IGNITE-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15130163#comment-15130163
]
Vladimir Ershov commented on IGNITE-2405:
-
Hi,
Take a look at the config/ignite-log4j.xml in your ignite folder. Here you can
set any log level per class or package, since it is typical log4j props file.
> Ignite is blocking the thread in case it can't connect to the node
> --
>
> Key: IGNITE-2405
> URL: https://issues.apache.org/jira/browse/IGNITE-2405
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5.0.final
>Reporter: Miron Aseev
> Labels: community, newbie
>
> It seems that Apache Ignite runs an infinite loop if it can't connect to the
> resolved hostname.
> For example, if you specify the hostname of the local machine as an address
> for the TCPSpi, then Apache Ignite resolves it
> [here|https://github.com/apache/ignite/blob/b3d347e35a254928fd1c4a0473f1b17d642c72f3/modules/core/src/main/java/org/apache/ignite/spi/discovery/tcp/ServerImpl.java#L915].
>
> But after that, for some reasons, it fails to connect to the resolved address
> [here|https://github.com/apache/ignite/blob/b3d347e35a254928fd1c4a0473f1b17d642c72f3/modules/core/src/main/java/org/apache/ignite/spi/discovery/tcp/ServerImpl.java#L925].
>
> As a result, the control flow goes to the catch block where the exception is
> logged (It's an IgniteSpiException. It seems it can't get acces to the host
> according to the exception message - "Network operation timed out. Increase
> 'failureDetectionTimeout' configuration property
> [failureDetectionTimeout=1]").
> In the end, we get an infinite loop.
> On the other hand, If I set an ip address (127.0.0.1) instead of the
> hostname, Ignite gets an empty list
> [here|https://github.com/apache/ignite/blob/b3d347e35a254928fd1c4a0473f1b17d642c72f3/modules/core/src/main/java/org/apache/ignite/spi/discovery/tcp/ServerImpl.java#L915]
> and the control flow breaks the loop
> [here|https://github.com/apache/ignite/blob/b3d347e35a254928fd1c4a0473f1b17d642c72f3/modules/core/src/main/java/org/apache/ignite/spi/discovery/tcp/ServerImpl.java#L918]
> and goes forward.
> Here's a log information which Ignite produces during its work.
> {code}
> Jan 19, 2016 7:33:02 PM java.util.logging.LogManager$RootLogger log
> SEVERE: Failed to resolve default logging config file:
> config/java.util.logging.properties
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO:
> >>>__
> >>> / _/ ___/ |/ / _/_ __/ __/
> >>> _/ // (7 7// / / / / _/
> >>> /___/\___/_/|_/___/ /_/ /___/
> >>>
> >>> ver. 1.5.0-final#20151229-sha1:f1f8cda2
> >>> 2015 Copyright(C) Apache Software Foundation
> >>>
> >>> Ignite documentation: http://ignite.apache.org
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO: Config URL: n/a
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO: Daemon mode: off
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO: OS: Linux 3.13.0-74-generic amd64
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO: OS user: maseev
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO: Language runtime: Java Platform API Specification ver. 1.8
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO: VM information: Java(TM) SE Runtime Environment 1.8.0_40-b26 Oracle
> Corporation Java HotSpot(TM) 64-Bit Server VM 25.40-b25
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO: VM total memory: 3.5GB
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO: Remote Management [restart: off, REST: on, JMX (remote: off)]
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO: IGNITE_HOME=null
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO: VM arguments:
> [-agentlib:jdwp=transport=dt_socket,address=127.0.0.1:51947,suspend=y,server=n,
> -ea, -DIGNITE_QUIET=false, -Didea.junit.sm_runner, -Dfile.encoding=UTF-8]
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO: Configured caches ['ignite-marshaller-sys-cache', 'ignite-sys-cache',
> 'ignite-atomics-sys-cache']
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger warning
> WARNING: Initial heap size is 250MB (should be no less than 512MB, use
> -Xms512m -Xmx512m).
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO: Non-loopback local IPs: 172.17.0.1, 192.168.88.252,
> fe80:0:0:0:42:2aff:feff:fe3d%docker0, fe80:0:0:0:f2de:f1ff:feb6:5301%eth0
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
[jira] [Assigned] (IGNITE-2539) NPE at RendezvousAffinityFunction
[ https://issues.apache.org/jira/browse/IGNITE-2539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ershov reassigned IGNITE-2539: --- Assignee: Vladimir Ershov > NPE at RendezvousAffinityFunction > - > > Key: IGNITE-2539 > URL: https://issues.apache.org/jira/browse/IGNITE-2539 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 1.5.0.final >Reporter: Vladimir Ershov >Assignee: Vladimir Ershov >Priority: Critical > Original Estimate: 4h > Remaining Estimate: 4h > > RendezvousAffinityFunction#assignPartition throws NPE, probably due to > simultaneous topology change and cache stop. We should write a test and fix > this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-2405) Ignite is blocking the thread in case it can't connect to the node
[
https://issues.apache.org/jira/browse/IGNITE-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15130163#comment-15130163
]
Vladimir Ershov edited comment on IGNITE-2405 at 2/3/16 10:35 AM:
--
Hi,
Please, take a look at the config/ignite-log4j.xml in your ignite folder. Here
you can set any log level per class or package, since it is typical log4j props
file.
was (Author: vershov):
Hi,
Take a look at the config/ignite-log4j.xml in your ignite folder. Here you can
set any log level per class or package, since it is typical log4j props file.
> Ignite is blocking the thread in case it can't connect to the node
> --
>
> Key: IGNITE-2405
> URL: https://issues.apache.org/jira/browse/IGNITE-2405
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5.0.final
>Reporter: Miron Aseev
> Labels: community, newbie
>
> It seems that Apache Ignite runs an infinite loop if it can't connect to the
> resolved hostname.
> For example, if you specify the hostname of the local machine as an address
> for the TCPSpi, then Apache Ignite resolves it
> [here|https://github.com/apache/ignite/blob/b3d347e35a254928fd1c4a0473f1b17d642c72f3/modules/core/src/main/java/org/apache/ignite/spi/discovery/tcp/ServerImpl.java#L915].
>
> But after that, for some reasons, it fails to connect to the resolved address
> [here|https://github.com/apache/ignite/blob/b3d347e35a254928fd1c4a0473f1b17d642c72f3/modules/core/src/main/java/org/apache/ignite/spi/discovery/tcp/ServerImpl.java#L925].
>
> As a result, the control flow goes to the catch block where the exception is
> logged (It's an IgniteSpiException. It seems it can't get acces to the host
> according to the exception message - "Network operation timed out. Increase
> 'failureDetectionTimeout' configuration property
> [failureDetectionTimeout=1]").
> In the end, we get an infinite loop.
> On the other hand, If I set an ip address (127.0.0.1) instead of the
> hostname, Ignite gets an empty list
> [here|https://github.com/apache/ignite/blob/b3d347e35a254928fd1c4a0473f1b17d642c72f3/modules/core/src/main/java/org/apache/ignite/spi/discovery/tcp/ServerImpl.java#L915]
> and the control flow breaks the loop
> [here|https://github.com/apache/ignite/blob/b3d347e35a254928fd1c4a0473f1b17d642c72f3/modules/core/src/main/java/org/apache/ignite/spi/discovery/tcp/ServerImpl.java#L918]
> and goes forward.
> Here's a log information which Ignite produces during its work.
> {code}
> Jan 19, 2016 7:33:02 PM java.util.logging.LogManager$RootLogger log
> SEVERE: Failed to resolve default logging config file:
> config/java.util.logging.properties
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO:
> >>>__
> >>> / _/ ___/ |/ / _/_ __/ __/
> >>> _/ // (7 7// / / / / _/
> >>> /___/\___/_/|_/___/ /_/ /___/
> >>>
> >>> ver. 1.5.0-final#20151229-sha1:f1f8cda2
> >>> 2015 Copyright(C) Apache Software Foundation
> >>>
> >>> Ignite documentation: http://ignite.apache.org
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO: Config URL: n/a
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO: Daemon mode: off
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO: OS: Linux 3.13.0-74-generic amd64
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO: OS user: maseev
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO: Language runtime: Java Platform API Specification ver. 1.8
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO: VM information: Java(TM) SE Runtime Environment 1.8.0_40-b26 Oracle
> Corporation Java HotSpot(TM) 64-Bit Server VM 25.40-b25
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO: VM total memory: 3.5GB
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO: Remote Management [restart: off, REST: on, JMX (remote: off)]
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO: IGNITE_HOME=null
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO: VM arguments:
> [-agentlib:jdwp=transport=dt_socket,address=127.0.0.1:51947,suspend=y,server=n,
> -ea, -DIGNITE_QUIET=false, -Didea.junit.sm_runner, -Dfile.encoding=UTF-8]
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO: Configured caches ['ignite-marshaller-sys-cache', 'ignite-sys-cache',
> 'ignite-atomics-sys-cache']
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger warning
> WARNING: Initial heap size is 250MB (should be no less than 512MB, use
> -Xms512m -Xmx512m).
> Jan 19, 2016 7:33:03 PM
[jira] [Updated] (IGNITE-2539) NPE at RendezvousAffinityFunction
[ https://issues.apache.org/jira/browse/IGNITE-2539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ershov updated IGNITE-2539: Attachment: ignite.log > NPE at RendezvousAffinityFunction > - > > Key: IGNITE-2539 > URL: https://issues.apache.org/jira/browse/IGNITE-2539 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 1.5.0.final >Reporter: Vladimir Ershov >Assignee: Vladimir Ershov >Priority: Critical > Attachments: ignite.log > > Original Estimate: 4h > Remaining Estimate: 4h > > RendezvousAffinityFunction#assignPartition throws NPE, probably due to > simultaneous topology change and cache stop. We should write a test and fix > this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2537) Cache metrics missing implementation.
Vladimir Ershov created IGNITE-2537:
---
Summary: Cache metrics missing implementation.
Key: IGNITE-2537
URL: https://issues.apache.org/jira/browse/IGNITE-2537
Project: Ignite
Issue Type: Improvement
Components: cache
Affects Versions: 1.5.0.final
Reporter: Vladimir Ershov
Looking at CacheMetricsImple all those methods are stubbed with return 0:
{noformat}
getTxCommitQueueSizegetTxCommitQueueSize
getTxPrepareQueueSize
getTxStartVersionCountsSize
getTxDhtCommitQueueSize
getTxDhtPrepareQueueSize
getTxDhtStartVersionCountsSize
{noformat}
This should be improved.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2509) Broken eviction for OFFHEAP_VALUES cache mode
[
https://issues.apache.org/jira/browse/IGNITE-2509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15125988#comment-15125988
]
Vladimir Ershov commented on IGNITE-2509:
-
Ok, will care this one.
> Broken eviction for OFFHEAP_VALUES cache mode
> -
>
> Key: IGNITE-2509
> URL: https://issues.apache.org/jira/browse/IGNITE-2509
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5.0.final
>Reporter: Denis Magda
>Assignee: Vladimir Ershov
>Priority: Blocker
> Fix For: 1.6
>
> Attachments: EvictionBug.java, eviction_fix.patch
>
>
> In case when {{OFFHEAP_VALUES}} mode is used {{EvictionPolicy}} calculates
> values size wrongly which leads to the fact that data is evicted only when
> either the limit on number of entries is reached or size of keys is bigger
> than max allowed size.
> To reproduce set the following cache configuration
> {noformat}
> FifoEvictionPolicy plc = new FifoEvictionPolicy();
> plc.setMaxMemorySize(2 * 1024 * 1024);
> cacheCfg.setEvictionPolicy(plc);
> cacheCfg.setMemoryMode(CacheMemoryMode.OFFHEAP_VALUES);
> cacheCfg.setSwapEnabled(true);
> {noformat}
> Test that reproduces the issue is attached.
> Also attached a patch that fixes the issue. However we should validate that
> the fix is full and add additional tests to the test suites.
> Finally, {{cache.metrics().getOffHeapAllocatedSize()}} always returns 0 for
> this cache mode. Has to be fixed as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2453) GridCacheStopSelfTest reveal NPE at GridNearTxFinishFuture for backup node is null
[
https://issues.apache.org/jira/browse/IGNITE-2453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121126#comment-15121126
]
Vladimir Ershov commented on IGNITE-2453:
-
Also, we should add a specific test here for case:
1) One client node, one primary node, one backup node
2) During transaction primary node failed, code execution should reach
GridNearTxFinishFuture#checkBackup at client side, but didn't obtain backup
link yet.
3) Backup node failed
4) resuming of GridNearTxFinishFuture#checkBackup should cause "failed commit
transaction" without any other errors or exceptions.
> GridCacheStopSelfTest reveal NPE at GridNearTxFinishFuture for backup node is
> null
> --
>
> Key: IGNITE-2453
> URL: https://issues.apache.org/jira/browse/IGNITE-2453
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Reporter: Vladimir Ershov
>Assignee: Vladimir Ershov
>Priority: Critical
> Attachments:
> Ignite_Tests_Ignite_Binary_Objects_Cache_300_artifacts.zip
>
>
> We have to fix case with backup == null here
> GridNearTxFinishFuture#checkBackup()
> to prevent this:
> {noformat}
> [02:11:50,554][ERROR][disco-event-worker-#70746%cache.GridCacheStopSelfTest0%][GridEventStorageManager]
> Unexpected exception in listener notification for event: DiscoveryEvent
> [evtNode=TcpDiscoveryNode [id=81c3f225-1185-487a-8b28-c48afd32,
> addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47502], discPort=47502, order=3,
> intOrder=3, lastExchangeTime=1453774307067, loc=false,
> ver=1.5.1#19700101-sha1:, isClient=false], topVer=7,
> nodeId8=92550fcc, msg=Node left: TcpDiscoveryNode
> [id=81c3f225-1185-487a-8b28-c48afd32, addrs=[127.0.0.1],
> sockAddrs=[/127.0.0.1:47502], discPort=47502, order=3, intOrder=3,
> lastExchangeTime=1453774307067, loc=false, ver=1.5.1#19700101-sha1:,
> isClient=false], type=NODE_LEFT, tstamp=1453774310538]
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxFinishFuture$CheckBackupMiniFuture.onNodeLeft(GridNearTxFinishFuture.java:883)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxFinishFuture.onNodeLeft(GridNearTxFinishFuture.java:139)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMvccManager$3.onEvent(GridCacheMvccManager.java:217)
> at
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.notifyListeners(GridEventStorageManager.java:770)
> at
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.notifyListeners(GridEventStorageManager.java:755)
> at
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.record(GridEventStorageManager.java:295)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.recordEvent(GridDiscoveryManager.java:1974)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body0(GridDiscoveryManager.java:2181)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body(GridDiscoveryManager.java:2014)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2372) GridCacheAbstractDataStructuresFailoverSelfTest.testQueueConstant* fail sometimes
[
https://issues.apache.org/jira/browse/IGNITE-2372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121181#comment-15121181
]
Vladimir Ershov commented on IGNITE-2372:
-
Also: testQueueConstantMultipleTopologyChange
{noformat}
junit.framework.AssertionFailedError: expected:<5546> but was:<5547>
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.failNotEquals(Assert.java:329)
at junit.framework.Assert.assertEquals(Assert.java:78)
at junit.framework.Assert.assertEquals(Assert.java:234)
at junit.framework.Assert.assertEquals(Assert.java:241)
at junit.framework.TestCase.assertEquals(TestCase.java:409)
at
org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest.doTestQueue(GridCacheAbstractDataStructuresFailoverSelfTest.java:729)
at
org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest.testQueueConstantMultipleTopologyChange(GridCacheAbstractDataStructuresFailoverSelfTest.java:683)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at junit.framework.TestCase.runTest(TestCase.java:176)
at
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1699)
at
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:116)
at
org.apache.ignite.testframework.junits.GridAbstractTest$4.run(GridAbstractTest.java:1637)
at java.lang.Thread.run(Thread.java:745)
{noformat}
> GridCacheAbstractDataStructuresFailoverSelfTest.testQueueConstant* fail
> sometimes
> -
>
> Key: IGNITE-2372
> URL: https://issues.apache.org/jira/browse/IGNITE-2372
> Project: Ignite
> Issue Type: Bug
>Reporter: Artem Shutak
>Assignee: Denis Magda
> Fix For: 1.6
>
>
> The following tests fail on TC sometimes:
> -
> GridCachePartitionedDataStructuresFailoverSelfTest.testQueueConstantMultipleTopologyChange
>
> -
> GridCachePartitionedOffheapDataStructuresFailoverSelfTest.testQueueConstantMultipleTopologyChange
>
> TC build:
> http://ci.ignite.apache.org/viewLog.html?buildId=95910=buildResultsDiv=IgniteTests_IgniteDataStrucutures
> Test testQueueConstantMultipleTopologyChange failed on my laptop too.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (IGNITE-2453) GridCacheStopSelfTest reveal NPE at GridNearTxFinishFuture for backup node is null
[
https://issues.apache.org/jira/browse/IGNITE-2453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ershov resolved IGNITE-2453.
-
Resolution: Resolved
Fix Version/s: 1.6
> GridCacheStopSelfTest reveal NPE at GridNearTxFinishFuture for backup node is
> null
> --
>
> Key: IGNITE-2453
> URL: https://issues.apache.org/jira/browse/IGNITE-2453
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Reporter: Vladimir Ershov
>Assignee: Vladimir Ershov
>Priority: Critical
> Fix For: 1.6
>
> Attachments:
> Ignite_Tests_Ignite_Binary_Objects_Cache_300_artifacts.zip
>
>
> We have to fix case with backup == null here
> GridNearTxFinishFuture#checkBackup()
> to prevent this:
> {noformat}
> [02:11:50,554][ERROR][disco-event-worker-#70746%cache.GridCacheStopSelfTest0%][GridEventStorageManager]
> Unexpected exception in listener notification for event: DiscoveryEvent
> [evtNode=TcpDiscoveryNode [id=81c3f225-1185-487a-8b28-c48afd32,
> addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47502], discPort=47502, order=3,
> intOrder=3, lastExchangeTime=1453774307067, loc=false,
> ver=1.5.1#19700101-sha1:, isClient=false], topVer=7,
> nodeId8=92550fcc, msg=Node left: TcpDiscoveryNode
> [id=81c3f225-1185-487a-8b28-c48afd32, addrs=[127.0.0.1],
> sockAddrs=[/127.0.0.1:47502], discPort=47502, order=3, intOrder=3,
> lastExchangeTime=1453774307067, loc=false, ver=1.5.1#19700101-sha1:,
> isClient=false], type=NODE_LEFT, tstamp=1453774310538]
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxFinishFuture$CheckBackupMiniFuture.onNodeLeft(GridNearTxFinishFuture.java:883)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxFinishFuture.onNodeLeft(GridNearTxFinishFuture.java:139)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMvccManager$3.onEvent(GridCacheMvccManager.java:217)
> at
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.notifyListeners(GridEventStorageManager.java:770)
> at
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.notifyListeners(GridEventStorageManager.java:755)
> at
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.record(GridEventStorageManager.java:295)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.recordEvent(GridDiscoveryManager.java:1974)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body0(GridDiscoveryManager.java:2181)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body(GridDiscoveryManager.java:2014)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (IGNITE-2453) GridCacheStopSelfTest reveal NPE at GridNearTxFinishFuture for backup node is null
[
https://issues.apache.org/jira/browse/IGNITE-2453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ershov closed IGNITE-2453.
---
This is covered by existing tests and should be covered by separated JUnit test
in future.
> GridCacheStopSelfTest reveal NPE at GridNearTxFinishFuture for backup node is
> null
> --
>
> Key: IGNITE-2453
> URL: https://issues.apache.org/jira/browse/IGNITE-2453
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Reporter: Vladimir Ershov
>Assignee: Vladimir Ershov
>Priority: Critical
> Fix For: 1.6
>
> Attachments:
> Ignite_Tests_Ignite_Binary_Objects_Cache_300_artifacts.zip
>
>
> We have to fix case with backup == null here
> GridNearTxFinishFuture#checkBackup()
> to prevent this:
> {noformat}
> [02:11:50,554][ERROR][disco-event-worker-#70746%cache.GridCacheStopSelfTest0%][GridEventStorageManager]
> Unexpected exception in listener notification for event: DiscoveryEvent
> [evtNode=TcpDiscoveryNode [id=81c3f225-1185-487a-8b28-c48afd32,
> addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47502], discPort=47502, order=3,
> intOrder=3, lastExchangeTime=1453774307067, loc=false,
> ver=1.5.1#19700101-sha1:, isClient=false], topVer=7,
> nodeId8=92550fcc, msg=Node left: TcpDiscoveryNode
> [id=81c3f225-1185-487a-8b28-c48afd32, addrs=[127.0.0.1],
> sockAddrs=[/127.0.0.1:47502], discPort=47502, order=3, intOrder=3,
> lastExchangeTime=1453774307067, loc=false, ver=1.5.1#19700101-sha1:,
> isClient=false], type=NODE_LEFT, tstamp=1453774310538]
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxFinishFuture$CheckBackupMiniFuture.onNodeLeft(GridNearTxFinishFuture.java:883)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxFinishFuture.onNodeLeft(GridNearTxFinishFuture.java:139)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMvccManager$3.onEvent(GridCacheMvccManager.java:217)
> at
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.notifyListeners(GridEventStorageManager.java:770)
> at
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.notifyListeners(GridEventStorageManager.java:755)
> at
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.record(GridEventStorageManager.java:295)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.recordEvent(GridDiscoveryManager.java:1974)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body0(GridDiscoveryManager.java:2181)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body(GridDiscoveryManager.java:2014)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-2488) Investigate possible Hibernate Ignite L2 Cache performance issues
[ https://issues.apache.org/jira/browse/IGNITE-2488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ershov reassigned IGNITE-2488: --- Assignee: Vladimir Ershov > Investigate possible Hibernate Ignite L2 Cache performance issues > - > > Key: IGNITE-2488 > URL: https://issues.apache.org/jira/browse/IGNITE-2488 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 1.5.0.final >Reporter: Denis Magda >Assignee: Vladimir Ershov > Labels: community > > The ticket is opened as a part of the discussion happened on StackOverflow > [1]. > There is a suspicion that Ignite L2 cache has some performance bottlenecks. > Need to reproduce and investigate. > [1] > http://stackoverflow.com/questions/34534251/ignite-for-hibernate-l2-is-extremely-slow/34551411#34551411 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-2483) Cache metrics bugs
[ https://issues.apache.org/jira/browse/IGNITE-2483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ershov reassigned IGNITE-2483: --- Assignee: Vladimir Ershov > Cache metrics bugs > -- > > Key: IGNITE-2483 > URL: https://issues.apache.org/jira/browse/IGNITE-2483 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Valentin Kulichenko >Assignee: Vladimir Ershov > Labels: community > Fix For: 1.6 > > > User list discussion: > http://apache-ignite-users.70518.x6.nabble.com/Is-there-a-way-to-get-cache-metrics-for-all-the-nodes-in-cluster-combined-td2674.html > Currently there are at least three issues with cache metrics: > # When metrics are acquired on client, average put times are always zero. > This happens because timings are calculated on the client, but puts are > counted on servers. > # Size and keySize are always zero even if cache is not empty. > # Default metrics() method that doesn't take a cluster group provides metrics > for local node only. So if it's called on client, they are always empty. It > should calculate metrics for the whole cluster instead. > Also looks like this code is very undertested. Coverage should be > significantly improved. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2406) [Test] [Rare] GridEventStorageCheckAllEventsSelfTest.testSuccessTask AND GridEventStorageCheckAllEventsSelfTest.testFailTask
[
https://issues.apache.org/jira/browse/IGNITE-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ershov updated IGNITE-2406:
Attachment:
Ignite_Tests_Ignite_Binary_Objects_Compute_Grid_297_artifacts.zip
Failed 2.
> [Test] [Rare] GridEventStorageCheckAllEventsSelfTest.testSuccessTask AND
> GridEventStorageCheckAllEventsSelfTest.testFailTask
>
>
> Key: IGNITE-2406
> URL: https://issues.apache.org/jira/browse/IGNITE-2406
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ershov
> Attachments:
> Ignite_Tests_Ignite_Binary_Objects_Compute_Grid_297_artifacts.zip
>
>
> Rare fail of GridEventStorageCheckAllEventsSelfTest testSuccessTask
> log:
> {noformat}
> --- Stderr: ---
> [13:06:47,647][WARN ][main][GridEventStorageCheckAllEventsSelfTest] Peer
> class loading is enabled (disable it in production for performance and
> deployment consistency reasons)
> [13:06:47,659][WARN ][main][GridCollisionManager] Collision resolution is
> disabled (all jobs will be activated upon arrival).
> [13:06:47,660][WARN ][main][NoopSwapSpaceSpi] Swap space is disabled. To
> enable use FileSwapSpaceSpi.
> [13:06:48,966][ERROR][main][root] Test failed.
> java.lang.AssertionError: Invalid event [evtType=45, expectedType=41,
> evts=[TaskEvent
> [taskName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
>
> taskClsName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
> sesId=e53ddf95251-af0890dd-f87e-4dca-8b22-bab1b6a13404, internal=false,
> subjId=af0890dd-f87e-4dca-8b22-bab1b6a13404, nodeId8=af0890dd, msg=Task
> started., type=TASK_STARTED, tstamp=1453208808959], JobEvent
> [taskName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
>
> taskClsName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
> sesId=e53ddf95251-af0890dd-f87e-4dca-8b22-bab1b6a13404,
> jobId=063ddf95251-af0890dd-f87e-4dca-8b22-bab1b6a13404,
> taskNode=TcpDiscoveryNode [id=af0890dd-f87e-4dca-8b22-bab1b6a13404,
> addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1,
> intOrder=1, lastExchangeTime=1453208807679, loc=true,
> ver=1.5.1#20160119-sha1:09c1d5e4, isClient=false],
> taskSubjId=af0890dd-f87e-4dca-8b22-bab1b6a13404, nodeId8=af0890dd, msg=Job
> got mapped., type=JOB_MAPPED, tstamp=1453208808959], JobEvent
> [taskName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
>
> taskClsName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
> sesId=e53ddf95251-af0890dd-f87e-4dca-8b22-bab1b6a13404,
> jobId=063ddf95251-af0890dd-f87e-4dca-8b22-bab1b6a13404,
> taskNode=TcpDiscoveryNode [id=af0890dd-f87e-4dca-8b22-bab1b6a13404,
> addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1,
> intOrder=1, lastExchangeTime=1453208807679, loc=true,
> ver=1.5.1#20160119-sha1:09c1d5e4, isClient=false],
> taskSubjId=af0890dd-f87e-4dca-8b22-bab1b6a13404, nodeId8=af0890dd, msg=Job
> got queued for computation., type=JOB_QUEUED, tstamp=1453208808959], JobEvent
> [taskName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
>
> taskClsName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
> sesId=e53ddf95251-af0890dd-f87e-4dca-8b22-bab1b6a13404,
> jobId=063ddf95251-af0890dd-f87e-4dca-8b22-bab1b6a13404,
> taskNode=TcpDiscoveryNode [id=af0890dd-f87e-4dca-8b22-bab1b6a13404,
> addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1,
> intOrder=1, lastExchangeTime=1453208807679, loc=true,
> ver=1.5.1#20160119-sha1:09c1d5e4, isClient=false],
> taskSubjId=af0890dd-f87e-4dca-8b22-bab1b6a13404, nodeId8=af0890dd, msg=null,
> type=JOB_STARTED, tstamp=1453208808959], CheckpointEvent
> [cpKey=testCheckpoint, nodeId8=af0890dd, msg=Checkpoint saved:
> testCheckpoint, type=CHECKPOINT_SAVED, tstamp=1453208808959], CheckpointEvent
> [cpKey=testCheckpoint, nodeId8=af0890dd, msg=Checkpoint removed:
> testCheckpoint, type=CHECKPOINT_REMOVED, tstamp=1453208808959], JobEvent
> [taskName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
>
> taskClsName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
> sesId=e53ddf95251-af0890dd-f87e-4dca-8b22-bab1b6a13404,
> jobId=063ddf95251-af0890dd-f87e-4dca-8b22-bab1b6a13404,
> taskNode=TcpDiscoveryNode [id=af0890dd-f87e-4dca-8b22-bab1b6a13404,
> addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1,
> intOrder=1,
[jira] [Commented] (IGNITE-2406) [Test] [Rare] GridEventStorageCheckAllEventsSelfTest.testSuccessTask AND GridEventStorageCheckAllEventsSelfTest.testFailTask
[
https://issues.apache.org/jira/browse/IGNITE-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15117003#comment-15117003
]
Vladimir Ershov commented on IGNITE-2406:
-
Failed again
{noformat}
java.lang.AssertionError: Invalid event [evtType=45, expectedType=41,
evts=[TaskEvent
[taskName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
taskClsName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
sesId=4ad917b7251-351d5cbd-8248-4fd8-9f42-eff057d84a66, internal=false,
subjId=351d5cbd-8248-4fd8-9f42-eff057d84a66, nodeId8=351d5cbd, msg=Task
started., type=TASK_STARTED, tstamp=1453770058221], JobEvent
[taskName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
taskClsName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
sesId=4ad917b7251-351d5cbd-8248-4fd8-9f42-eff057d84a66,
jobId=6ad917b7251-351d5cbd-8248-4fd8-9f42-eff057d84a66,
taskNode=TcpDiscoveryNode [id=351d5cbd-8248-4fd8-9f42-eff057d84a66,
addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1,
intOrder=1, lastExchangeTime=1453770056930, loc=true,
ver=1.5.1#19700101-sha1:, isClient=false],
taskSubjId=351d5cbd-8248-4fd8-9f42-eff057d84a66, nodeId8=351d5cbd, msg=Job got
mapped., type=JOB_MAPPED, tstamp=1453770058221], JobEvent
[taskName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
taskClsName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
sesId=4ad917b7251-351d5cbd-8248-4fd8-9f42-eff057d84a66,
jobId=6ad917b7251-351d5cbd-8248-4fd8-9f42-eff057d84a66,
taskNode=TcpDiscoveryNode [id=351d5cbd-8248-4fd8-9f42-eff057d84a66,
addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1,
intOrder=1, lastExchangeTime=1453770056930, loc=true,
ver=1.5.1#19700101-sha1:, isClient=false],
taskSubjId=351d5cbd-8248-4fd8-9f42-eff057d84a66, nodeId8=351d5cbd, msg=Job got
queued for computation., type=JOB_QUEUED, tstamp=1453770058221], JobEvent
[taskName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
taskClsName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
sesId=4ad917b7251-351d5cbd-8248-4fd8-9f42-eff057d84a66,
jobId=6ad917b7251-351d5cbd-8248-4fd8-9f42-eff057d84a66,
taskNode=TcpDiscoveryNode [id=351d5cbd-8248-4fd8-9f42-eff057d84a66,
addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1,
intOrder=1, lastExchangeTime=1453770056930, loc=true,
ver=1.5.1#19700101-sha1:, isClient=false],
taskSubjId=351d5cbd-8248-4fd8-9f42-eff057d84a66, nodeId8=351d5cbd, msg=null,
type=JOB_STARTED, tstamp=1453770058221], CheckpointEvent [cpKey=testCheckpoint,
nodeId8=351d5cbd, msg=Checkpoint saved: testCheckpoint, type=CHECKPOINT_SAVED,
tstamp=1453770058221], CheckpointEvent [cpKey=testCheckpoint, nodeId8=351d5cbd,
msg=Checkpoint removed: testCheckpoint, type=CHECKPOINT_REMOVED,
tstamp=1453770058221], JobEvent
[taskName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
taskClsName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
sesId=4ad917b7251-351d5cbd-8248-4fd8-9f42-eff057d84a66,
jobId=6ad917b7251-351d5cbd-8248-4fd8-9f42-eff057d84a66,
taskNode=TcpDiscoveryNode [id=351d5cbd-8248-4fd8-9f42-eff057d84a66,
addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1,
intOrder=1, lastExchangeTime=1453770056930, loc=true,
ver=1.5.1#19700101-sha1:, isClient=false],
taskSubjId=351d5cbd-8248-4fd8-9f42-eff057d84a66, nodeId8=351d5cbd, msg=null,
type=JOB_FINISHED, tstamp=1453770058221], JobEvent
[taskName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
taskClsName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
sesId=4ad917b7251-351d5cbd-8248-4fd8-9f42-eff057d84a66,
jobId=6ad917b7251-351d5cbd-8248-4fd8-9f42-eff057d84a66,
taskNode=TcpDiscoveryNode [id=351d5cbd-8248-4fd8-9f42-eff057d84a66,
addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1,
intOrder=1, lastExchangeTime=1453770056930, loc=true,
ver=1.5.1#19700101-sha1:, isClient=false],
taskSubjId=351d5cbd-8248-4fd8-9f42-eff057d84a66, nodeId8=351d5cbd, msg=Job got
resulted with: WAIT, type=JOB_RESULTED, tstamp=1453770058231], TaskEvent
[taskName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
taskClsName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
sesId=4ad917b7251-351d5cbd-8248-4fd8-9f42-eff057d84a66, internal=false,
subjId=351d5cbd-8248-4fd8-9f42-eff057d84a66, nodeId8=351d5cbd, msg=Task
reduced., type=TASK_REDUCED,
[jira] [Issue Comment Deleted] (IGNITE-2406) [Test] [Rare] GridEventStorageCheckAllEventsSelfTest.testSuccessTask AND GridEventStorageCheckAllEventsSelfTest.testFailTask
[
https://issues.apache.org/jira/browse/IGNITE-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ershov updated IGNITE-2406:
Comment: was deleted
(was: Failed 2.)
> [Test] [Rare] GridEventStorageCheckAllEventsSelfTest.testSuccessTask AND
> GridEventStorageCheckAllEventsSelfTest.testFailTask
>
>
> Key: IGNITE-2406
> URL: https://issues.apache.org/jira/browse/IGNITE-2406
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ershov
> Attachments:
> Ignite_Tests_Ignite_Binary_Objects_Compute_Grid_297_artifacts.zip
>
>
> Rare fail of GridEventStorageCheckAllEventsSelfTest testSuccessTask
> log:
> {noformat}
> --- Stderr: ---
> [13:06:47,647][WARN ][main][GridEventStorageCheckAllEventsSelfTest] Peer
> class loading is enabled (disable it in production for performance and
> deployment consistency reasons)
> [13:06:47,659][WARN ][main][GridCollisionManager] Collision resolution is
> disabled (all jobs will be activated upon arrival).
> [13:06:47,660][WARN ][main][NoopSwapSpaceSpi] Swap space is disabled. To
> enable use FileSwapSpaceSpi.
> [13:06:48,966][ERROR][main][root] Test failed.
> java.lang.AssertionError: Invalid event [evtType=45, expectedType=41,
> evts=[TaskEvent
> [taskName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
>
> taskClsName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
> sesId=e53ddf95251-af0890dd-f87e-4dca-8b22-bab1b6a13404, internal=false,
> subjId=af0890dd-f87e-4dca-8b22-bab1b6a13404, nodeId8=af0890dd, msg=Task
> started., type=TASK_STARTED, tstamp=1453208808959], JobEvent
> [taskName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
>
> taskClsName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
> sesId=e53ddf95251-af0890dd-f87e-4dca-8b22-bab1b6a13404,
> jobId=063ddf95251-af0890dd-f87e-4dca-8b22-bab1b6a13404,
> taskNode=TcpDiscoveryNode [id=af0890dd-f87e-4dca-8b22-bab1b6a13404,
> addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1,
> intOrder=1, lastExchangeTime=1453208807679, loc=true,
> ver=1.5.1#20160119-sha1:09c1d5e4, isClient=false],
> taskSubjId=af0890dd-f87e-4dca-8b22-bab1b6a13404, nodeId8=af0890dd, msg=Job
> got mapped., type=JOB_MAPPED, tstamp=1453208808959], JobEvent
> [taskName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
>
> taskClsName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
> sesId=e53ddf95251-af0890dd-f87e-4dca-8b22-bab1b6a13404,
> jobId=063ddf95251-af0890dd-f87e-4dca-8b22-bab1b6a13404,
> taskNode=TcpDiscoveryNode [id=af0890dd-f87e-4dca-8b22-bab1b6a13404,
> addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1,
> intOrder=1, lastExchangeTime=1453208807679, loc=true,
> ver=1.5.1#20160119-sha1:09c1d5e4, isClient=false],
> taskSubjId=af0890dd-f87e-4dca-8b22-bab1b6a13404, nodeId8=af0890dd, msg=Job
> got queued for computation., type=JOB_QUEUED, tstamp=1453208808959], JobEvent
> [taskName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
>
> taskClsName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
> sesId=e53ddf95251-af0890dd-f87e-4dca-8b22-bab1b6a13404,
> jobId=063ddf95251-af0890dd-f87e-4dca-8b22-bab1b6a13404,
> taskNode=TcpDiscoveryNode [id=af0890dd-f87e-4dca-8b22-bab1b6a13404,
> addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1,
> intOrder=1, lastExchangeTime=1453208807679, loc=true,
> ver=1.5.1#20160119-sha1:09c1d5e4, isClient=false],
> taskSubjId=af0890dd-f87e-4dca-8b22-bab1b6a13404, nodeId8=af0890dd, msg=null,
> type=JOB_STARTED, tstamp=1453208808959], CheckpointEvent
> [cpKey=testCheckpoint, nodeId8=af0890dd, msg=Checkpoint saved:
> testCheckpoint, type=CHECKPOINT_SAVED, tstamp=1453208808959], CheckpointEvent
> [cpKey=testCheckpoint, nodeId8=af0890dd, msg=Checkpoint removed:
> testCheckpoint, type=CHECKPOINT_REMOVED, tstamp=1453208808959], JobEvent
> [taskName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
>
> taskClsName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
> sesId=e53ddf95251-af0890dd-f87e-4dca-8b22-bab1b6a13404,
> jobId=063ddf95251-af0890dd-f87e-4dca-8b22-bab1b6a13404,
> taskNode=TcpDiscoveryNode [id=af0890dd-f87e-4dca-8b22-bab1b6a13404,
> addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1,
> intOrder=1, lastExchangeTime=1453208807679, loc=true,
>
[jira] [Updated] (IGNITE-2378) Data loss Part 2. Add flexible DataLoss Policy. Improve dataLoss event with batch.
[ https://issues.apache.org/jira/browse/IGNITE-2378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ershov updated IGNITE-2378: Description: Next steps for the data loss check functionality development: # Introduce new DataLossPolicy, like read-only and others. # Think of data restoration and implement if needed. # Design solution for the reduce of the amount of EVT_CACHE_REBALANCE_PART_DATA_LOST. (Now it is possible to implement batching for those events). One has to be careful with backward compatibility here. # ResetLostPartsMsg should affect only topology with specified version. was: Next steps for the data loss check functionality development: # Introduce new DataLossPolicy, like read-only and others. # Think of data restoration and implement if needed. # Design solution for the reduce of the amount of EVT_CACHE_REBALANCE_PART_DATA_LOST. (Now it is possible to implement batching for those events). One has to be careful with backward compatibility here. > Data loss Part 2. Add flexible DataLoss Policy. Improve dataLoss event with > batch. > -- > > Key: IGNITE-2378 > URL: https://issues.apache.org/jira/browse/IGNITE-2378 > Project: Ignite > Issue Type: Improvement >Affects Versions: 1.6 >Reporter: Vladimir Ershov >Assignee: Vladimir Ershov > Labels: 1.6 > Original Estimate: 40h > Remaining Estimate: 40h > > Next steps for the data loss check functionality development: > # Introduce new DataLossPolicy, like read-only and others. > # Think of data restoration and implement if needed. > # Design solution for the reduce of the amount of > EVT_CACHE_REBALANCE_PART_DATA_LOST. (Now it is possible to implement batching > for those events). One has to be careful with backward compatibility here. > # ResetLostPartsMsg should affect only topology with specified version. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1802) Ignite.countDownLatch() can return null if latch has been already created.
[
https://issues.apache.org/jira/browse/IGNITE-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15115491#comment-15115491
]
Vladimir Ershov commented on IGNITE-1802:
-
Also muted: IgnitePartitionedCountDownLatchSelfTest.testLatchMultinode2
> Ignite.countDownLatch() can return null if latch has been already created.
> --
>
> Key: IGNITE-1802
> URL: https://issues.apache.org/jira/browse/IGNITE-1802
> Project: Ignite
> Issue Type: Test
>Reporter: Artem Shutak
>Priority: Blocker
> Labels: Muted_test
> Fix For: 1.6
>
>
> IgnitePartitionedCountDownLatchSelfTest.testLatchMultinode1test fails on
> TC sometimes.
> According to stack trace Ignite.countDownLatch(,,,false) can return null if
> latch has been already created.
> Logs:
> {noformat}
> junit.framework.AssertionFailedError: null
> at junit.framework.Assert.fail(Assert.java:55)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.Assert.assertNotNull(Assert.java:256)
> at junit.framework.Assert.assertNotNull(Assert.java:248)
> at junit.framework.TestCase.assertNotNull(TestCase.java:417)
> at
> org.apache.ignite.internal.processors.cache.datastructures.IgniteCountDownLatchAbstractSelfTest$3.call(IgniteCountDownLatchAbstractSelfTest.java:306)
> at
> org.apache.ignite.internal.processors.cache.datastructures.IgniteCountDownLatchAbstractSelfTest$3.call(IgniteCountDownLatchAbstractSelfTest.java:300)
> at
> org.apache.ignite.testframework.GridTestUtils$5.run(GridTestUtils.java:671)
> at
> org.apache.ignite.testframework.GridTestUtils$7.call(GridTestUtils.java:967)
> at
> org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
> --- Stdout: ---
> [13:22:46,287][INFO ][main][root] >>> Starting test: testLatchMultinode1 <<<
> [13:22:46,502][INFO ][main][root] >>> Stopping test: testLatchMultinode1 in
> 215 ms <<<
> --- Stderr: ---
> [13:22:46,501][ERROR][main][root] Test failed.
> junit.framework.AssertionFailedError
> at junit.framework.Assert.fail(Assert.java:55)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.Assert.assertNotNull(Assert.java:256)
> at junit.framework.Assert.assertNotNull(Assert.java:248)
> at junit.framework.TestCase.assertNotNull(TestCase.java:417)
> at
> org.apache.ignite.internal.processors.cache.datastructures.IgniteCountDownLatchAbstractSelfTest$3.call(IgniteCountDownLatchAbstractSelfTest.java:306)
> at
> org.apache.ignite.internal.processors.cache.datastructures.IgniteCountDownLatchAbstractSelfTest$3.call(IgniteCountDownLatchAbstractSelfTest.java:300)
> at
> org.apache.ignite.testframework.GridTestUtils$5.run(GridTestUtils.java:671)
> at
> org.apache.ignite.testframework.GridTestUtils$7.call(GridTestUtils.java:967)
> at
> org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2428) [Test] [Rare] IgniteClientReconnectFailoverTest.testReconnectComputeApi
[
https://issues.apache.org/jira/browse/IGNITE-2428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ershov updated IGNITE-2428:
Attachment: Ignite_Tests_Ignite_Client_Nodes_250.log.zip
> [Test] [Rare] IgniteClientReconnectFailoverTest.testReconnectComputeApi
> ---
>
> Key: IGNITE-2428
> URL: https://issues.apache.org/jira/browse/IGNITE-2428
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5
>Reporter: Vladimir Ershov
> Labels: test-fail
> Attachments: Ignite_Tests_Ignite_Client_Nodes_250.log.zip
>
>
> Test fails rarely.
> {noformat}
> org.apache.ignite.IgniteCheckedException: Failed to connect to node (is node
> still alive?). Make sure that each GridComputeTask and GridCacheTransaction
> has a timeout set in order to prevent parties from waiting forever in case of
> network issues [nodeId=e2965abc-87ff-4f55-8c80-9c68fe30,
> addrs=[/127.0.0.1:47100]]
> at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:2464)
> at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createNioClient(TcpCommunicationSpi.java:2105)
> at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.reserveClient(TcpCommunicationSpi.java:1999)
> at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(TcpCommunicationSpi.java:1935)
> at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage(TcpCommunicationSpi.java:1901)
> at
> org.apache.ignite.internal.IgniteClientReconnectAbstractTest$BlockTpcCommunicationSpi.sendMessage(IgniteClientReconnectAbstractTest.java:435)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1077)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1146)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.sendRequest(GridTaskWorker.java:1240)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.processMappedJobs(GridTaskWorker.java:609)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.body(GridTaskWorker.java:501)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at
> org.apache.ignite.internal.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:678)
> at
> org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:403)
> at
> org.apache.ignite.internal.processors.closure.GridClosureProcessor.callAsync(GridClosureProcessor.java:406)
> at
> org.apache.ignite.internal.processors.closure.GridClosureProcessor.callAsync(GridClosureProcessor.java:379)
> at
> org.apache.ignite.internal.IgniteComputeImpl.broadcast(IgniteComputeImpl.java:267)
> at
> org.apache.ignite.internal.IgniteClientReconnectFailoverTest$3.call(IgniteClientReconnectFailoverTest.java:191)
> at
> org.apache.ignite.internal.IgniteClientReconnectFailoverTest$3.call(IgniteClientReconnectFailoverTest.java:187)
> at
> org.apache.ignite.internal.IgniteClientReconnectFailoverAbstractTest$1.call(IgniteClientReconnectFailoverAbstractTest.java:103)
> at
> org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-2428) [Test] [Rare] IgniteClientReconnectFailoverTest.testReconnectComputeApi
Vladimir Ershov created IGNITE-2428:
---
Summary: [Test] [Rare]
IgniteClientReconnectFailoverTest.testReconnectComputeApi
Key: IGNITE-2428
URL: https://issues.apache.org/jira/browse/IGNITE-2428
Project: Ignite
Issue Type: Bug
Affects Versions: 1.5
Reporter: Vladimir Ershov
Test fails rarely.
{noformat}
org.apache.ignite.IgniteCheckedException: Failed to connect to node (is node
still alive?). Make sure that each GridComputeTask and GridCacheTransaction has
a timeout set in order to prevent parties from waiting forever in case of
network issues [nodeId=e2965abc-87ff-4f55-8c80-9c68fe30,
addrs=[/127.0.0.1:47100]]
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:2464)
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createNioClient(TcpCommunicationSpi.java:2105)
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.reserveClient(TcpCommunicationSpi.java:1999)
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(TcpCommunicationSpi.java:1935)
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage(TcpCommunicationSpi.java:1901)
at
org.apache.ignite.internal.IgniteClientReconnectAbstractTest$BlockTpcCommunicationSpi.sendMessage(IgniteClientReconnectAbstractTest.java:435)
at
org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1077)
at
org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1146)
at
org.apache.ignite.internal.processors.task.GridTaskWorker.sendRequest(GridTaskWorker.java:1240)
at
org.apache.ignite.internal.processors.task.GridTaskWorker.processMappedJobs(GridTaskWorker.java:609)
at
org.apache.ignite.internal.processors.task.GridTaskWorker.body(GridTaskWorker.java:501)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at
org.apache.ignite.internal.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:678)
at
org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:403)
at
org.apache.ignite.internal.processors.closure.GridClosureProcessor.callAsync(GridClosureProcessor.java:406)
at
org.apache.ignite.internal.processors.closure.GridClosureProcessor.callAsync(GridClosureProcessor.java:379)
at
org.apache.ignite.internal.IgniteComputeImpl.broadcast(IgniteComputeImpl.java:267)
at
org.apache.ignite.internal.IgniteClientReconnectFailoverTest$3.call(IgniteClientReconnectFailoverTest.java:191)
at
org.apache.ignite.internal.IgniteClientReconnectFailoverTest$3.call(IgniteClientReconnectFailoverTest.java:187)
at
org.apache.ignite.internal.IgniteClientReconnectFailoverAbstractTest$1.call(IgniteClientReconnectFailoverAbstractTest.java:103)
at
org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-802) [Test] GridCachePartitionedQueueEntryMoveSelfTest.testQueue
[ https://issues.apache.org/jira/browse/IGNITE-802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ershov updated IGNITE-802: --- Labels: Muted_test (was: Muted_test Rare) > [Test] GridCachePartitionedQueueEntryMoveSelfTest.testQueue > --- > > Key: IGNITE-802 > URL: https://issues.apache.org/jira/browse/IGNITE-802 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak >Assignee: Denis Magda > Labels: Muted_test > Fix For: ignite-1.4 > > Attachments: ignite-802.patch > > > The test had been already fixed (see GG-5620), but it was not uncommented > after. Now it fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-802) [Test] GridCachePartitionedQueueEntryMoveSelfTest.testQueue
[ https://issues.apache.org/jira/browse/IGNITE-802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ershov updated IGNITE-802: --- Labels: Muted_test Rare (was: Muted_test) > [Test] GridCachePartitionedQueueEntryMoveSelfTest.testQueue > --- > > Key: IGNITE-802 > URL: https://issues.apache.org/jira/browse/IGNITE-802 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak >Assignee: Denis Magda > Labels: Muted_test, Rare > Fix For: ignite-1.4 > > Attachments: ignite-802.patch > > > The test had been already fixed (see GG-5620), but it was not uncommented > after. Now it fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-802) [Test] [Rare] GridCachePartitionedQueueEntryMoveSelfTest.testQueue
[ https://issues.apache.org/jira/browse/IGNITE-802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ershov updated IGNITE-802: --- Summary: [Test] [Rare] GridCachePartitionedQueueEntryMoveSelfTest.testQueue (was: [Test] GridCachePartitionedQueueEntryMoveSelfTest.testQueue) > [Test] [Rare] GridCachePartitionedQueueEntryMoveSelfTest.testQueue > -- > > Key: IGNITE-802 > URL: https://issues.apache.org/jira/browse/IGNITE-802 > Project: Ignite > Issue Type: Bug >Affects Versions: 1.5 >Reporter: Artem Shutak >Assignee: Denis Magda > Labels: Muted_test > Fix For: ignite-1.4 > > Attachments: > Ignite_Tests_Ignite_Binary_Objects_Data_Strucutures_268_artifacts.zip, > ignite-802.patch > > > The test had been already fixed (see GG-5620), but it was not uncommented > after. Now it fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-802) [Test] GridCachePartitionedQueueEntryMoveSelfTest.testQueue
[
https://issues.apache.org/jira/browse/IGNITE-802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15110364#comment-15110364
]
Vladimir Ershov commented on IGNITE-802:
Observing rare fail:
{noformat}
[root] Finished waiting for topology map update
[grid=partitioned.GridCachePartitionedQueueEntryMoveSelfTest6, p=0,
duration=4415ms]
[06:48:09,870][ERROR][main][root] Test failed.
class org.apache.ignite.IgniteCheckedException: Unable to move the queue to a
new primary node
at
org.apache.ignite.internal.processors.cache.datastructures.partitioned.GridCachePartitionedQueueEntryMoveSelfTest.startAdditionalNodes(GridCachePartitionedQueueEntryMoveSelfTest.java:206)
at
org.apache.ignite.internal.processors.cache.datastructures.partitioned.GridCachePartitionedQueueEntryMoveSelfTest.testQueue(GridCachePartitionedQueueEntryMoveSelfTest.java:133)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at junit.framework.TestCase.runTest(TestCase.java:176)
at
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1699)
at
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:116)
at
org.apache.ignite.testframework.junits.GridAbstractTest$4.run(GridAbstractTest.java:1637)
at java.lang.Thread.run(Thread.java:745)
[06:48:09,871][WARN ][main][root] Interrupting threads started so far: 1
{noformat}
See the attachment for details.
> [Test] GridCachePartitionedQueueEntryMoveSelfTest.testQueue
> ---
>
> Key: IGNITE-802
> URL: https://issues.apache.org/jira/browse/IGNITE-802
> Project: Ignite
> Issue Type: Bug
>Reporter: Artem Shutak
>Assignee: Denis Magda
> Labels: Muted_test
> Fix For: ignite-1.4
>
> Attachments: ignite-802.patch
>
>
> The test had been already fixed (see GG-5620), but it was not uncommented
> after. Now it fails.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2427) [Test] [Rare] CacheSerializableTransactionsTest.testGetRemoveTxNearCache2
[
https://issues.apache.org/jira/browse/IGNITE-2427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ershov updated IGNITE-2427:
Description:
Test fails very rare:
{noformat}
junit.framework.AssertionFailedError: expected:<3> but was:<1>
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.failNotEquals(Assert.java:329)
at junit.framework.Assert.assertEquals(Assert.java:78)
at junit.framework.Assert.assertEquals(Assert.java:86)
at junit.framework.TestCase.assertEquals(TestCase.java:253)
at
org.apache.ignite.internal.processors.cache.CacheSerializableTransactionsTest.checkValue(CacheSerializableTransactionsTest.java:4187)
at
org.apache.ignite.internal.processors.cache.CacheSerializableTransactionsTest.checkValue(CacheSerializableTransactionsTest.java:4171)
at
org.apache.ignite.internal.processors.cache.CacheSerializableTransactionsTest.getRemoveTx(CacheSerializableTransactionsTest.java:3308)
at
org.apache.ignite.internal.processors.cache.CacheSerializableTransactionsTest.testGetRemoveTxNearCache2(CacheSerializableTransactionsTest.java:3205)
{nofrormat}
was:
Test fails very rare:
{noformat}
junit.framework.AssertionFailedError: expected:<3> but was:<1>
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.failNotEquals(Assert.java:329)
at junit.framework.Assert.assertEquals(Assert.java:78)
at junit.framework.Assert.assertEquals(Assert.java:86)
at junit.framework.TestCase.assertEquals(TestCase.java:253)
at
org.apache.ignite.internal.processors.cache.CacheSerializableTransactionsTest.checkValue(CacheSerializableTransactionsTest.java:4187)
at
org.apache.ignite.internal.processors.cache.CacheSerializableTransactionsTest.checkValue(CacheSerializableTransactionsTest.java:4171)
at
org.apache.ignite.internal.processors.cache.CacheSerializableTransactionsTest.getRemoveTx(CacheSerializableTransactionsTest.java:3308)
at
org.apache.ignite.internal.processors.cache.CacheSerializableTransactionsTest.testGetRemoveTxNearCache2(CacheSerializableTransactionsTest.java:3205)
{nofromat}
> [Test] [Rare] CacheSerializableTransactionsTest.testGetRemoveTxNearCache2
> -
>
> Key: IGNITE-2427
> URL: https://issues.apache.org/jira/browse/IGNITE-2427
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5
>Reporter: Vladimir Ershov
> Labels: test-fail
>
> Test fails very rare:
> {noformat}
> junit.framework.AssertionFailedError: expected:<3> but was:<1>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:86)
> at junit.framework.TestCase.assertEquals(TestCase.java:253)
> at
> org.apache.ignite.internal.processors.cache.CacheSerializableTransactionsTest.checkValue(CacheSerializableTransactionsTest.java:4187)
> at
> org.apache.ignite.internal.processors.cache.CacheSerializableTransactionsTest.checkValue(CacheSerializableTransactionsTest.java:4171)
> at
> org.apache.ignite.internal.processors.cache.CacheSerializableTransactionsTest.getRemoveTx(CacheSerializableTransactionsTest.java:3308)
> at
> org.apache.ignite.internal.processors.cache.CacheSerializableTransactionsTest.testGetRemoveTxNearCache2(CacheSerializableTransactionsTest.java:3205)
> {nofrormat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-2427) [Test] [Rare] CacheSerializableTransactionsTest.testGetRemoveTxNearCache2
Vladimir Ershov created IGNITE-2427:
---
Summary: [Test] [Rare]
CacheSerializableTransactionsTest.testGetRemoveTxNearCache2
Key: IGNITE-2427
URL: https://issues.apache.org/jira/browse/IGNITE-2427
Project: Ignite
Issue Type: Bug
Affects Versions: 1.5
Reporter: Vladimir Ershov
Test fails very rare:
{noformat}
junit.framework.AssertionFailedError: expected:<3> but was:<1>
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.failNotEquals(Assert.java:329)
at junit.framework.Assert.assertEquals(Assert.java:78)
at junit.framework.Assert.assertEquals(Assert.java:86)
at junit.framework.TestCase.assertEquals(TestCase.java:253)
at
org.apache.ignite.internal.processors.cache.CacheSerializableTransactionsTest.checkValue(CacheSerializableTransactionsTest.java:4187)
at
org.apache.ignite.internal.processors.cache.CacheSerializableTransactionsTest.checkValue(CacheSerializableTransactionsTest.java:4171)
at
org.apache.ignite.internal.processors.cache.CacheSerializableTransactionsTest.getRemoveTx(CacheSerializableTransactionsTest.java:3308)
at
org.apache.ignite.internal.processors.cache.CacheSerializableTransactionsTest.testGetRemoveTxNearCache2(CacheSerializableTransactionsTest.java:3205)
{nofromat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2427) [Test] [Rare] CacheSerializableTransactionsTest.testGetRemoveTxNearCache2
[
https://issues.apache.org/jira/browse/IGNITE-2427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ershov updated IGNITE-2427:
Description:
Test fails very rare:
{noformat}
junit.framework.AssertionFailedError: expected:<3> but was:<1>
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.failNotEquals(Assert.java:329)
at junit.framework.Assert.assertEquals(Assert.java:78)
at junit.framework.Assert.assertEquals(Assert.java:86)
at junit.framework.TestCase.assertEquals(TestCase.java:253)
at
org.apache.ignite.internal.processors.cache.CacheSerializableTransactionsTest.checkValue(CacheSerializableTransactionsTest.java:4187)
at
org.apache.ignite.internal.processors.cache.CacheSerializableTransactionsTest.checkValue(CacheSerializableTransactionsTest.java:4171)
at
org.apache.ignite.internal.processors.cache.CacheSerializableTransactionsTest.getRemoveTx(CacheSerializableTransactionsTest.java:3308)
at
org.apache.ignite.internal.processors.cache.CacheSerializableTransactionsTest.testGetRemoveTxNearCache2(CacheSerializableTransactionsTest.java:3205)
{noformat}
was:
Test fails very rare:
{noformat}
junit.framework.AssertionFailedError: expected:<3> but was:<1>
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.failNotEquals(Assert.java:329)
at junit.framework.Assert.assertEquals(Assert.java:78)
at junit.framework.Assert.assertEquals(Assert.java:86)
at junit.framework.TestCase.assertEquals(TestCase.java:253)
at
org.apache.ignite.internal.processors.cache.CacheSerializableTransactionsTest.checkValue(CacheSerializableTransactionsTest.java:4187)
at
org.apache.ignite.internal.processors.cache.CacheSerializableTransactionsTest.checkValue(CacheSerializableTransactionsTest.java:4171)
at
org.apache.ignite.internal.processors.cache.CacheSerializableTransactionsTest.getRemoveTx(CacheSerializableTransactionsTest.java:3308)
at
org.apache.ignite.internal.processors.cache.CacheSerializableTransactionsTest.testGetRemoveTxNearCache2(CacheSerializableTransactionsTest.java:3205)
{nofrormat}
> [Test] [Rare] CacheSerializableTransactionsTest.testGetRemoveTxNearCache2
> -
>
> Key: IGNITE-2427
> URL: https://issues.apache.org/jira/browse/IGNITE-2427
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5
>Reporter: Vladimir Ershov
> Labels: test-fail
>
> Test fails very rare:
> {noformat}
> junit.framework.AssertionFailedError: expected:<3> but was:<1>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:86)
> at junit.framework.TestCase.assertEquals(TestCase.java:253)
> at
> org.apache.ignite.internal.processors.cache.CacheSerializableTransactionsTest.checkValue(CacheSerializableTransactionsTest.java:4187)
> at
> org.apache.ignite.internal.processors.cache.CacheSerializableTransactionsTest.checkValue(CacheSerializableTransactionsTest.java:4171)
> at
> org.apache.ignite.internal.processors.cache.CacheSerializableTransactionsTest.getRemoveTx(CacheSerializableTransactionsTest.java:3308)
> at
> org.apache.ignite.internal.processors.cache.CacheSerializableTransactionsTest.testGetRemoveTxNearCache2(CacheSerializableTransactionsTest.java:3205)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-802) [Test] GridCachePartitionedQueueEntryMoveSelfTest.testQueue
[ https://issues.apache.org/jira/browse/IGNITE-802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ershov updated IGNITE-802: --- Attachment: Ignite_Tests_Ignite_Binary_Objects_Data_Strucutures_268_artifacts.zip > [Test] GridCachePartitionedQueueEntryMoveSelfTest.testQueue > --- > > Key: IGNITE-802 > URL: https://issues.apache.org/jira/browse/IGNITE-802 > Project: Ignite > Issue Type: Bug >Affects Versions: 1.5 >Reporter: Artem Shutak >Assignee: Denis Magda > Labels: Muted_test > Fix For: ignite-1.4 > > Attachments: > Ignite_Tests_Ignite_Binary_Objects_Data_Strucutures_268_artifacts.zip, > ignite-802.patch > > > The test had been already fixed (see GG-5620), but it was not uncommented > after. Now it fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-802) [Test] GridCachePartitionedQueueEntryMoveSelfTest.testQueue
[ https://issues.apache.org/jira/browse/IGNITE-802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ershov updated IGNITE-802: --- Affects Version/s: 1.5 > [Test] GridCachePartitionedQueueEntryMoveSelfTest.testQueue > --- > > Key: IGNITE-802 > URL: https://issues.apache.org/jira/browse/IGNITE-802 > Project: Ignite > Issue Type: Bug >Affects Versions: 1.5 >Reporter: Artem Shutak >Assignee: Denis Magda > Labels: Muted_test > Fix For: ignite-1.4 > > Attachments: > Ignite_Tests_Ignite_Binary_Objects_Data_Strucutures_268_artifacts.zip, > ignite-802.patch > > > The test had been already fixed (see GG-5620), but it was not uncommented > after. Now it fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2427) [Test] [Rare] CacheSerializableTransactionsTest.testGetRemoveTxNearCache2
[
https://issues.apache.org/jira/browse/IGNITE-2427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ershov updated IGNITE-2427:
Attachment: logs(5).zip
> [Test] [Rare] CacheSerializableTransactionsTest.testGetRemoveTxNearCache2
> -
>
> Key: IGNITE-2427
> URL: https://issues.apache.org/jira/browse/IGNITE-2427
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5
>Reporter: Vladimir Ershov
> Labels: test-fail
> Attachments: logs(5).zip
>
>
> Test fails very rare:
> {noformat}
> junit.framework.AssertionFailedError: expected:<3> but was:<1>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:86)
> at junit.framework.TestCase.assertEquals(TestCase.java:253)
> at
> org.apache.ignite.internal.processors.cache.CacheSerializableTransactionsTest.checkValue(CacheSerializableTransactionsTest.java:4187)
> at
> org.apache.ignite.internal.processors.cache.CacheSerializableTransactionsTest.checkValue(CacheSerializableTransactionsTest.java:4171)
> at
> org.apache.ignite.internal.processors.cache.CacheSerializableTransactionsTest.getRemoveTx(CacheSerializableTransactionsTest.java:3308)
> at
> org.apache.ignite.internal.processors.cache.CacheSerializableTransactionsTest.testGetRemoveTxNearCache2(CacheSerializableTransactionsTest.java:3205)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-2420) [Test] Ignite AWS lacks amazon credentials.
Vladimir Ershov created IGNITE-2420: --- Summary: [Test] Ignite AWS lacks amazon credentials. Key: IGNITE-2420 URL: https://issues.apache.org/jira/browse/IGNITE-2420 Project: Ignite Issue Type: Task Components: aws Affects Versions: 1.5 Reporter: Vladimir Ershov Priority: Minor There is an issue with amazon credentials. We have to invent a secure way to apply it for AWS tests. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2420) [Test] Ignite AWS lacks amazon credentials.
[ https://issues.apache.org/jira/browse/IGNITE-2420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ershov updated IGNITE-2420: Labels: Muted_test (was: ) > [Test] Ignite AWS lacks amazon credentials. > --- > > Key: IGNITE-2420 > URL: https://issues.apache.org/jira/browse/IGNITE-2420 > Project: Ignite > Issue Type: Task > Components: aws >Affects Versions: 1.5 >Reporter: Vladimir Ershov >Priority: Minor > Labels: Muted_test > Original Estimate: 8h > Remaining Estimate: 8h > > There is an issue with amazon credentials. We have to invent a secure way to > apply it for AWS tests. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2406) [Test] [Rare] GridEventStorageCheckAllEventsSelfTest.testSuccessTask AND GridEventStorageCheckAllEventsSelfTest.testFailTask
[
https://issues.apache.org/jira/browse/IGNITE-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ershov updated IGNITE-2406:
Affects Version/s: 1.5
> [Test] [Rare] GridEventStorageCheckAllEventsSelfTest.testSuccessTask AND
> GridEventStorageCheckAllEventsSelfTest.testFailTask
>
>
> Key: IGNITE-2406
> URL: https://issues.apache.org/jira/browse/IGNITE-2406
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5
>Reporter: Vladimir Ershov
>Priority: Minor
>
> Rare fail of GridEventStorageCheckAllEventsSelfTest testSuccessTask
> log:
> {noformat}
> --- Stderr: ---
> [13:06:47,647][WARN ][main][GridEventStorageCheckAllEventsSelfTest] Peer
> class loading is enabled (disable it in production for performance and
> deployment consistency reasons)
> [13:06:47,659][WARN ][main][GridCollisionManager] Collision resolution is
> disabled (all jobs will be activated upon arrival).
> [13:06:47,660][WARN ][main][NoopSwapSpaceSpi] Swap space is disabled. To
> enable use FileSwapSpaceSpi.
> [13:06:48,966][ERROR][main][root] Test failed.
> java.lang.AssertionError: Invalid event [evtType=45, expectedType=41,
> evts=[TaskEvent
> [taskName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
>
> taskClsName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
> sesId=e53ddf95251-af0890dd-f87e-4dca-8b22-bab1b6a13404, internal=false,
> subjId=af0890dd-f87e-4dca-8b22-bab1b6a13404, nodeId8=af0890dd, msg=Task
> started., type=TASK_STARTED, tstamp=1453208808959], JobEvent
> [taskName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
>
> taskClsName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
> sesId=e53ddf95251-af0890dd-f87e-4dca-8b22-bab1b6a13404,
> jobId=063ddf95251-af0890dd-f87e-4dca-8b22-bab1b6a13404,
> taskNode=TcpDiscoveryNode [id=af0890dd-f87e-4dca-8b22-bab1b6a13404,
> addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1,
> intOrder=1, lastExchangeTime=1453208807679, loc=true,
> ver=1.5.1#20160119-sha1:09c1d5e4, isClient=false],
> taskSubjId=af0890dd-f87e-4dca-8b22-bab1b6a13404, nodeId8=af0890dd, msg=Job
> got mapped., type=JOB_MAPPED, tstamp=1453208808959], JobEvent
> [taskName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
>
> taskClsName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
> sesId=e53ddf95251-af0890dd-f87e-4dca-8b22-bab1b6a13404,
> jobId=063ddf95251-af0890dd-f87e-4dca-8b22-bab1b6a13404,
> taskNode=TcpDiscoveryNode [id=af0890dd-f87e-4dca-8b22-bab1b6a13404,
> addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1,
> intOrder=1, lastExchangeTime=1453208807679, loc=true,
> ver=1.5.1#20160119-sha1:09c1d5e4, isClient=false],
> taskSubjId=af0890dd-f87e-4dca-8b22-bab1b6a13404, nodeId8=af0890dd, msg=Job
> got queued for computation., type=JOB_QUEUED, tstamp=1453208808959], JobEvent
> [taskName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
>
> taskClsName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
> sesId=e53ddf95251-af0890dd-f87e-4dca-8b22-bab1b6a13404,
> jobId=063ddf95251-af0890dd-f87e-4dca-8b22-bab1b6a13404,
> taskNode=TcpDiscoveryNode [id=af0890dd-f87e-4dca-8b22-bab1b6a13404,
> addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1,
> intOrder=1, lastExchangeTime=1453208807679, loc=true,
> ver=1.5.1#20160119-sha1:09c1d5e4, isClient=false],
> taskSubjId=af0890dd-f87e-4dca-8b22-bab1b6a13404, nodeId8=af0890dd, msg=null,
> type=JOB_STARTED, tstamp=1453208808959], CheckpointEvent
> [cpKey=testCheckpoint, nodeId8=af0890dd, msg=Checkpoint saved:
> testCheckpoint, type=CHECKPOINT_SAVED, tstamp=1453208808959], CheckpointEvent
> [cpKey=testCheckpoint, nodeId8=af0890dd, msg=Checkpoint removed:
> testCheckpoint, type=CHECKPOINT_REMOVED, tstamp=1453208808959], JobEvent
> [taskName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
>
> taskClsName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
> sesId=e53ddf95251-af0890dd-f87e-4dca-8b22-bab1b6a13404,
> jobId=063ddf95251-af0890dd-f87e-4dca-8b22-bab1b6a13404,
> taskNode=TcpDiscoveryNode [id=af0890dd-f87e-4dca-8b22-bab1b6a13404,
> addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1,
> intOrder=1, lastExchangeTime=1453208807679, loc=true,
> ver=1.5.1#20160119-sha1:09c1d5e4, isClient=false],
> taskSubjId=af0890dd-f87e-4dca-8b22-bab1b6a13404,
[jira] [Commented] (IGNITE-2405) Ignite is blocking the thread in case it can't connect to the node
[
https://issues.apache.org/jira/browse/IGNITE-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15108459#comment-15108459
]
Vladimir Ershov commented on IGNITE-2405:
-
Miron,
Thank you for a well formed request and an attached test! I've run this test on
my side and it is not reproduced. I've also check the code you've mentioned and
here are some thoughts and steps I can suggest to proceed with this issue:
# Before any further reproduction, please check, that there is no any other
Ignite nodes in your net, and all java processes for Ignite cluster are
terminated.
# Then, please, set DEBUG level for TcpDiscoverySpi and ServerImpl, reproduce
this issue and attach all logs including full stack trace for an exception.
Than I can provide you with further assistance.
> Ignite is blocking the thread in case it can't connect to the node
> --
>
> Key: IGNITE-2405
> URL: https://issues.apache.org/jira/browse/IGNITE-2405
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5
>Reporter: Miron Aseev
> Labels: community, newbie
>
> It seems that Apache Ignite runs an infinite loop if it can't connect to the
> resolved hostname.
> For example, if you specify the hostname of the local machine as an address
> for the TCPSpi, then Apache Ignite resolves it
> [here|https://github.com/apache/ignite/blob/b3d347e35a254928fd1c4a0473f1b17d642c72f3/modules/core/src/main/java/org/apache/ignite/spi/discovery/tcp/ServerImpl.java#L915].
>
> But after that, for some reasons, it fails to connect to the resolved address
> [here|https://github.com/apache/ignite/blob/b3d347e35a254928fd1c4a0473f1b17d642c72f3/modules/core/src/main/java/org/apache/ignite/spi/discovery/tcp/ServerImpl.java#L925].
>
> As a result, the control flow goes to the catch block where the exception is
> logged (It's an IgniteSpiException. It seems it can't get acces to the host
> according to the exception message - "Network operation timed out. Increase
> 'failureDetectionTimeout' configuration property
> [failureDetectionTimeout=1]").
> In the end, we get an infinite loop.
> On the other hand, If I set an ip address (127.0.0.1) instead of the
> hostname, Ignite gets an empty list
> [here|https://github.com/apache/ignite/blob/b3d347e35a254928fd1c4a0473f1b17d642c72f3/modules/core/src/main/java/org/apache/ignite/spi/discovery/tcp/ServerImpl.java#L915]
> and the control flow breaks the loop
> [here|https://github.com/apache/ignite/blob/b3d347e35a254928fd1c4a0473f1b17d642c72f3/modules/core/src/main/java/org/apache/ignite/spi/discovery/tcp/ServerImpl.java#L918]
> and goes forward.
> Here's a log information which Ignite produces during its work.
> {code}
> Jan 19, 2016 7:33:02 PM java.util.logging.LogManager$RootLogger log
> SEVERE: Failed to resolve default logging config file:
> config/java.util.logging.properties
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO:
> >>>__
> >>> / _/ ___/ |/ / _/_ __/ __/
> >>> _/ // (7 7// / / / / _/
> >>> /___/\___/_/|_/___/ /_/ /___/
> >>>
> >>> ver. 1.5.0-final#20151229-sha1:f1f8cda2
> >>> 2015 Copyright(C) Apache Software Foundation
> >>>
> >>> Ignite documentation: http://ignite.apache.org
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO: Config URL: n/a
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO: Daemon mode: off
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO: OS: Linux 3.13.0-74-generic amd64
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO: OS user: maseev
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO: Language runtime: Java Platform API Specification ver. 1.8
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO: VM information: Java(TM) SE Runtime Environment 1.8.0_40-b26 Oracle
> Corporation Java HotSpot(TM) 64-Bit Server VM 25.40-b25
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO: VM total memory: 3.5GB
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO: Remote Management [restart: off, REST: on, JMX (remote: off)]
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO: IGNITE_HOME=null
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO: VM arguments:
> [-agentlib:jdwp=transport=dt_socket,address=127.0.0.1:51947,suspend=y,server=n,
> -ea, -DIGNITE_QUIET=false, -Didea.junit.sm_runner, -Dfile.encoding=UTF-8]
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO: Configured caches ['ignite-marshaller-sys-cache', 'ignite-sys-cache',
> 'ignite-atomics-sys-cache']
> Jan 19,
[jira] [Comment Edited] (IGNITE-2405) Ignite is blocking the thread in case it can't connect to the node
[
https://issues.apache.org/jira/browse/IGNITE-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15108459#comment-15108459
]
Vladimir Ershov edited comment on IGNITE-2405 at 1/20/16 12:37 PM:
---
Miron,
Thank you for a well formed request and an attached test! I've run this test on
my side and it is not reproduced. I've also check the code you've mentioned and
here are some thoughts and steps I can suggest to proceed with this issue:
# Before any further reproduction, please check, that there is no any other
Ignite nodes in your net, and all java processes for Ignite cluster are
terminated.
# Then, please, set DEBUG level for TcpDiscoverySpi and ServerImpl, reproduce
this issue and attach all logs including full stack trace for an exception.
Then I can provide you with further assistance.
was (Author: vershov):
Miron,
Thank you for a well formed request and an attached test! I've run this test on
my side and it is not reproduced. I've also check the code you've mentioned and
here are some thoughts and steps I can suggest to proceed with this issue:
# Before any further reproduction, please check, that there is no any other
Ignite nodes in your net, and all java processes for Ignite cluster are
terminated.
# Then, please, set DEBUG level for TcpDiscoverySpi and ServerImpl, reproduce
this issue and attach all logs including full stack trace for an exception.
Than I can provide you with further assistance.
> Ignite is blocking the thread in case it can't connect to the node
> --
>
> Key: IGNITE-2405
> URL: https://issues.apache.org/jira/browse/IGNITE-2405
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5
>Reporter: Miron Aseev
> Labels: community, newbie
>
> It seems that Apache Ignite runs an infinite loop if it can't connect to the
> resolved hostname.
> For example, if you specify the hostname of the local machine as an address
> for the TCPSpi, then Apache Ignite resolves it
> [here|https://github.com/apache/ignite/blob/b3d347e35a254928fd1c4a0473f1b17d642c72f3/modules/core/src/main/java/org/apache/ignite/spi/discovery/tcp/ServerImpl.java#L915].
>
> But after that, for some reasons, it fails to connect to the resolved address
> [here|https://github.com/apache/ignite/blob/b3d347e35a254928fd1c4a0473f1b17d642c72f3/modules/core/src/main/java/org/apache/ignite/spi/discovery/tcp/ServerImpl.java#L925].
>
> As a result, the control flow goes to the catch block where the exception is
> logged (It's an IgniteSpiException. It seems it can't get acces to the host
> according to the exception message - "Network operation timed out. Increase
> 'failureDetectionTimeout' configuration property
> [failureDetectionTimeout=1]").
> In the end, we get an infinite loop.
> On the other hand, If I set an ip address (127.0.0.1) instead of the
> hostname, Ignite gets an empty list
> [here|https://github.com/apache/ignite/blob/b3d347e35a254928fd1c4a0473f1b17d642c72f3/modules/core/src/main/java/org/apache/ignite/spi/discovery/tcp/ServerImpl.java#L915]
> and the control flow breaks the loop
> [here|https://github.com/apache/ignite/blob/b3d347e35a254928fd1c4a0473f1b17d642c72f3/modules/core/src/main/java/org/apache/ignite/spi/discovery/tcp/ServerImpl.java#L918]
> and goes forward.
> Here's a log information which Ignite produces during its work.
> {code}
> Jan 19, 2016 7:33:02 PM java.util.logging.LogManager$RootLogger log
> SEVERE: Failed to resolve default logging config file:
> config/java.util.logging.properties
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO:
> >>>__
> >>> / _/ ___/ |/ / _/_ __/ __/
> >>> _/ // (7 7// / / / / _/
> >>> /___/\___/_/|_/___/ /_/ /___/
> >>>
> >>> ver. 1.5.0-final#20151229-sha1:f1f8cda2
> >>> 2015 Copyright(C) Apache Software Foundation
> >>>
> >>> Ignite documentation: http://ignite.apache.org
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO: Config URL: n/a
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO: Daemon mode: off
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO: OS: Linux 3.13.0-74-generic amd64
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO: OS user: maseev
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO: Language runtime: Java Platform API Specification ver. 1.8
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO: VM information: Java(TM) SE Runtime Environment 1.8.0_40-b26 Oracle
> Corporation Java HotSpot(TM) 64-Bit Server VM 25.40-b25
> Jan 19, 2016 7:33:03 PM org.apache.ignite.logger.java.JavaLogger info
> INFO: VM total memory: 3.5GB
>
[jira] [Updated] (IGNITE-2400) [Test] [Rare] GridCacheReplicatedDataStructuresFailoverSelfTest.testQueueTopologyChange
[
https://issues.apache.org/jira/browse/IGNITE-2400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ershov updated IGNITE-2400:
Component/s: cache
> [Test] [Rare]
> GridCacheReplicatedDataStructuresFailoverSelfTest.testQueueTopologyChange
> ---
>
> Key: IGNITE-2400
> URL: https://issues.apache.org/jira/browse/IGNITE-2400
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.5
>Reporter: Vladimir Ershov
>Priority: Minor
>
> Very rare Failed. Log:
> {noformat}
> [19:09:22,500][INFO
> ][grid-starter-testQueueTopologyChange-2][GridCacheReplicatedDataStructuresFailoverSelfTest1]
>
> >>>__
> >>> / _/ ___/ |/ / _/_ __/ __/
> >>> _/ // (7 7// / / / / _/
> >>> /___/\___/_/|_/___/ /_/ /___/
> >>>
> >>> ver. 1.5.1-final-SNAPSHOT#20160118-sha1:67791457
> >>> 2016 Copyright(C) Apache Software Foundation
> >>>
> >>> Ignite documentation: http://ignite.apache.org
> [19:09:22,500][INFO
> ][grid-starter-testQueueTopologyChange-2][GridCacheReplicatedDataStructuresFailoverSelfTest1]
> Config URL: n/a
> [19:09:22,500][INFO
> ][grid-starter-testQueueTopologyChange-2][GridCacheReplicatedDataStructuresFailoverSelfTest1]
> Daemon mode: off
> [19:09:22,500][INFO
> ][grid-starter-testQueueTopologyChange-2][GridCacheReplicatedDataStructuresFailoverSelfTest1]
> OS: Linux 2.6.32-573.12.1.el6.x86_64 amd64
> [19:09:22,500][INFO
> ][grid-starter-testQueueTopologyChange-2][GridCacheReplicatedDataStructuresFailoverSelfTest1]
> OS user: teamcity
> [19:09:22,500][INFO
> ][grid-starter-testQueueTopologyChange-2][GridCacheReplicatedDataStructuresFailoverSelfTest1]
> Language runtime: Java Platform API Specification ver. 1.7
> [19:09:22,500][INFO
> ][grid-starter-testQueueTopologyChange-2][GridCacheReplicatedDataStructuresFailoverSelfTest1]
> VM information: Java(TM) SE Runtime Environment 1.7.0_80-b15 Oracle
> Corporation Java HotSpot(TM) 64-Bit Server VM 24.80-b11
> [19:09:22,500][INFO
> ][grid-starter-testQueueTopologyChange-2][GridCacheReplicatedDataStructuresFailoverSelfTest1]
> VM total memory: 2.7GB
> [19:09:22,500][INFO
> ][grid-starter-testQueueTopologyChange-2][GridCacheReplicatedDataStructuresFailoverSelfTest1]
> Remote Management [restart: off, REST: off, JMX (remote: off)]
> [19:09:22,500][INFO
> ][grid-starter-testQueueTopologyChange-2][GridCacheReplicatedDataStructuresFailoverSelfTest1]
> IGNITE_HOME=/mnt/tc_disk/work/b9d877891a53d8fe
> [19:09:22,500][INFO
> ][grid-starter-testQueueTopologyChange-2][GridCacheReplicatedDataStructuresFailoverSelfTest1]
> VM arguments: [-DJAVA_HOME=/usr/lib/jvm/java-7-oracle,
> -Dagent.home.dir=/home/teamcity/agent, -Dagent.name=a_228_44,
> -Dagent.ownPort=9044, -Dagent.work.dir=/mnt/tc_disk/work, -Dbuild.number=251,
> -Dbuild.vcs.number=67791457f87097469f0efadcea6c6d13dd2ed37f,
> -Dbuild.vcs.number.1=67791457f87097469f0efadcea6c6d13dd2ed37f,
> -Dbuild.vcs.number.IgniteTests_ApacheIgniteMirrorOnGitHub1=67791457f87097469f0efadcea6c6d13dd2ed37f,
> -Dclassworlds.conf=/mnt/tc_disk/temp/buildTmp/teamcity.m2.conf,
> -Dcom.jetbrains.maven.watcher.report.file=/mnt/tc_disk/temp/buildTmp/maven-build-info.xml,
> -Djava.io.tmpdir=/mnt/tc_disk/temp/buildTmp,
> -Dmaven.home=/home/teamcity/agent/tools/maven3,
> -Dmaven.repo.local=/home/teamcity/.m2/repository,
> -Dteamcity.agent.cpuBenchmark=612,
> -Dteamcity.agent.dotnet.agent_url=http://localhost:9044/RPC2,
> -Dteamcity.agent.dotnet.build_id=98493,
> -Dteamcity.auth.password=CbDuHJH3Q2dmVXRjeYzMbVejOZZDeEDb,
> -Dteamcity.auth.userId=TeamCityBuildId=98493,
> -Dteamcity.build.changedFiles.file=/mnt/tc_disk/temp/buildTmp/changedFiles6971648059137154933.txt,
> -Dteamcity.build.checkoutDir=/mnt/tc_disk/work/b9d877891a53d8fe,
> -Dteamcity.build.id=98493,
> -Dteamcity.build.properties.file=/mnt/tc_disk/temp/buildTmp/teamcity.build685147608221190172.properties,
> -Dteamcity.build.tempDir=/mnt/tc_disk/temp/buildTmp,
> -Dteamcity.build.workingDir=/mnt/tc_disk/work/b9d877891a53d8fe,
> -Dteamcity.buildConfName=Ignite Binary Objects Data Strucutures,
> -Dteamcity.buildType.id=IgniteTests_IgniteBinaryObjectsDataStrucutures,
> -Dteamcity.configuration.properties.file=/mnt/tc_disk/temp/buildTmp/teamcity.config3300810008320663426.properties,
>
> -Dteamcity.maven.watcher.home=/home/teamcity/agent/plugins/mavenPlugin/maven-watcher,
> -Dteamcity.projectName=Ignite Tests,
> -Dteamcity.runner.properties.file=/mnt/tc_disk/temp/buildTmp/teamcity.runner8006302695410654754.properties,
>
> -Dteamcity.tests.recentlyFailedTests.file=/mnt/tc_disk/temp/buildTmp/testsToRunFirst5887954035965893252.txt,
> -Dteamcity.version=8.1.5 (build 30240), -ea, -XX:MaxPermSize=1g, -Xms1g,
> -Xmx3g,
[jira] [Updated] (IGNITE-172) GridTcpCommunicationSpiRecoveryAckSelfTest and IgniteTcpCommunicationRecoveryAckClosureSelfTest
[ https://issues.apache.org/jira/browse/IGNITE-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ershov updated IGNITE-172: --- Affects Version/s: 1.5 > GridTcpCommunicationSpiRecoveryAckSelfTest and > IgniteTcpCommunicationRecoveryAckClosureSelfTest > --- > > Key: IGNITE-172 > URL: https://issues.apache.org/jira/browse/IGNITE-172 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 1.5 >Reporter: Irina Vasilinets > Labels: Muted_test > > GridTcpCommunicationSpiRecoveryAckSelfTest.testQueueOverflow and > GridTcpCommunicationSpiTcpNoDelayOffSelfTest.testSendToManyNodes > fail sometimes. > IgniteTcpCommunicationRecoveryAckClosureSelfTest.testQueueOverflow - 1 from 10 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1611) [Test Failed] GridNearCacheTxNodeFailureSelfTest.testPrimaryNodeFailureBackupCommitImplicit
[
https://issues.apache.org/jira/browse/IGNITE-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15106487#comment-15106487
]
Vladimir Ershov commented on IGNITE-1611:
-
Fails repeatedly on other TC.
{noformat}
junit.framework.AssertionFailedError: near=GridNearCacheEntry [topVer=4,
dhtVer=GridCacheVersion [topVer=64633417, nodeOrderDrId=1,
globalTime=1453153417753, order=1453153413071], part=5, evictReservations=0,
super=GridDistributedCacheEntry [super=GridCacheMapEntry
[key=KeyCacheObjectImpl [val=5, hasValBytes=true], val=CacheObjectImpl [val=5,
hasValBytes=true], startVer=1453153413072, ver=GridCacheVersion
[topVer=64633417, nodeOrderDrId=1, globalTime=1453153417753,
order=1453153413071], hash=-1056306330, extras=null, flags=0]]]
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.assertTrue(Assert.java:22)
at junit.framework.Assert.assertNull(Assert.java:277)
at junit.framework.TestCase.assertNull(TestCase.java:447)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridCacheTxNodeFailureSelfTest.dataCheck(GridCacheTxNodeFailureSelfTest.java:353)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridCacheTxNodeFailureSelfTest.checkPrimaryNodeFailureBackupCommit(GridCacheTxNodeFailureSelfTest.java:313)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridCacheTxNodeFailureSelfTest.testPrimaryNodeFailureBackupCommitOptimistic(GridCacheTxNodeFailureSelfTest.java:115)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at junit.framework.TestCase.runTest(TestCase.java:176)
at
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1699)
at
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:116)
at
org.apache.ignite.testframework.junits.GridAbstractTest$4.run(GridAbstractTest.java:1637)
at java.lang.Thread.run(Thread.java:745)
--- Stdout: ---
{noformat}
> [Test Failed]
> GridNearCacheTxNodeFailureSelfTest.testPrimaryNodeFailureBackupCommitImplicit
> ---
>
> Key: IGNITE-1611
> URL: https://issues.apache.org/jira/browse/IGNITE-1611
> Project: Ignite
> Issue Type: Test
>Affects Versions: 1.5
>Reporter: Anton Vinogradov
>Priority: Blocker
> Labels: Muted_test
> Fix For: 1.5
>
>
> There is no guarantee that test failure will be produced each test run,
> please analyze logs in case of reproduction problem:
> {noformat}
> junit.framework.AssertionFailedError: near=GridNearCacheEntry [topVer=4,
> dhtVer=GridCacheVersion [topVer=55263880, nodeOrderDrId=1,
> globalTime=1443783881869, order=1443783876675], part=2,
> super=GridDistributedCacheEntry [super=GridCacheMapEntry
> [key=KeyCacheObjectImpl [val=2, hasValBytes=true], val=CacheObjectImpl
> [val=2, hasValBytes=true], startVer=1443783876676, ver=GridCacheVersion
> [topVer=55263880, nodeOrderDrId=1, globalTime=1443783881869,
> order=1443783876675], hash=821347078, extras=null, flags=0]]]
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.Assert.assertNull(Assert.java:277)
> at junit.framework.TestCase.assertNull(TestCase.java:447)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridCacheTxNodeFailureSelfTest.dataCheck(GridCacheTxNodeFailureSelfTest.java:342)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridCacheTxNodeFailureSelfTest.checkPrimaryNodeFailureBackupCommit(GridCacheTxNodeFailureSelfTest.java:302)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridCacheTxNodeFailureSelfTest.testPrimaryNodeFailureBackupCommitImplicit(GridCacheTxNodeFailureSelfTest.java:161)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1665)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:111)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:1603)
> --- Stdout: ---
>
[jira] [Updated] (IGNITE-2384) Notification missed in continuous query
[ https://issues.apache.org/jira/browse/IGNITE-2384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ershov updated IGNITE-2384: Labels: 1.5.4 (was: ) > Notification missed in continuous query > --- > > Key: IGNITE-2384 > URL: https://issues.apache.org/jira/browse/IGNITE-2384 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Valentin Kulichenko >Assignee: Nikolay Tikhonov >Priority: Critical > Labels: 1.5.4 > Fix For: 1.6 > > Attachments: ListenerTest.java > > > Test reproducing the issue is attached, fails on assertion on line 76. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2365) Cache inconsistency: concurrent preloading from a storage when OFF HEAP is used
[
https://issues.apache.org/jira/browse/IGNITE-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ershov updated IGNITE-2365:
Labels: 1.5.4 important (was: important)
> Cache inconsistency: concurrent preloading from a storage when OFF HEAP is
> used
> ---
>
> Key: IGNITE-2365
> URL: https://issues.apache.org/jira/browse/IGNITE-2365
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Alexey Goncharuk
>Priority: Blocker
> Labels: 1.5.4, important
> Fix For: 1.6
>
> Attachments: TwoNodesEviction.java
>
>
> Start two server nodes in parallel using {{TwoNodesEviction}} example
> attached.
> Both nodes start preloading the full set of data from an underlying storage
> considering that in a cache only data for which a node is primary will reside.
> However the node that joins the topology later will have much more entries in
> the on-heap part of the cache than expected ignoring eviction policy settings.
> If to disable the eviction policy and off-heap then the example works fine.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2359) Race in MarshallerContextImpl when working with files that store "id->clsName" mapping
[
https://issues.apache.org/jira/browse/IGNITE-2359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ershov updated IGNITE-2359:
Labels: 1.5.4 (was: )
> Race in MarshallerContextImpl when working with files that store
> "id->clsName" mapping
> --
>
> Key: IGNITE-2359
> URL: https://issues.apache.org/jira/browse/IGNITE-2359
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Priority: Critical
> Labels: 1.5.4
> Fix For: 1.6
>
>
> There is a possible race that happens when several nodes are being started on
> the same box and try to preload 'clsName' for 'id' from a file stored in a
> work directory.
> {noformat}
> Caused by: javax.cache.integration.CacheLoaderException:
> java.lang.NullPointerException: Ouch! Argument cannot be null: val
> at
> org.apache.ignite.internal.processors.cache.store.GridCacheStoreManagerAdapter.loadCache(GridCacheStoreManagerAdapter.java:509)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.localLoadCache(GridCacheAdapter.java:3442)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter.localLoadCache(GridDhtCacheAdapter.java:448)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.localLoadCache(IgniteCacheProxy.java:372)
> at
> com.jefco.portfoliotrading.gets.loader.GGLifecycleBean.loadCache(GGLifecycleBean.java:69)
> at
> com.jefco.portfoliotrading.gets.loader.GGLifecycleBean.onLifecycleEvent(GGLifecycleBean.java:48)
> at
> org.apache.ignite.internal.IgniteKernal.notifyLifecycleBeans(IgniteKernal.java:620)
> ... 8 more
> Caused by: java.lang.NullPointerException: Ouch! Argument cannot be null: val
> at
> org.apache.ignite.internal.util.GridArgumentCheck.notNull(GridArgumentCheck.java:48)
> at
> org.apache.ignite.internal.util.GridArgumentCheck.notNull(GridArgumentCheck.java:61)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.tryPutIfAbsent(GridDhtAtomicCache.java:394)
> at
> org.apache.ignite.internal.MarshallerContextImpl.registerClassName(MarshallerContextImpl.java:114)
> at
> org.apache.ignite.internal.MarshallerContextImpl.className(MarshallerContextImpl.java:165)
> at
> org.apache.ignite.internal.MarshallerContextAdapter.getClass(MarshallerContextAdapter.java:174)
> at
> org.apache.ignite.marshaller.optimized.OptimizedMarshallerUtils.classDescriptor(OptimizedMarshallerUtils.java:256)
> at
> org.apache.ignite.marshaller.optimized.OptimizedObjectInputStream.readObjectOverride(OptimizedObjectInputStream.java:309)
> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:365)
> at
> org.apache.ignite.marshaller.optimized.OptimizedObjectInputStream.readArrayList(OptimizedObjectInputStream.java:602)
> at
> org.apache.ignite.marshaller.optimized.OptimizedObjectInputStream.readObjectOverride(OptimizedObjectInputStream.java:281)
> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:365)
> at
> com.jefco.portfoliotrading.gets.common.CumExec.readExternal(CumExec.java:273)
> at
> org.apache.ignite.marshaller.optimized.OptimizedObjectInputStream.readExternalizable(OptimizedObjectInputStream.java:514)
> at
> org.apache.ignite.marshaller.optimized.OptimizedClassDescriptor.read(OptimizedClassDescriptor.java:803)
> at
> org.apache.ignite.marshaller.optimized.OptimizedObjectInputStream.readObjectOverride(OptimizedObjectInputStream.java:315)
> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:365)
> at
> org.apache.ignite.lang.IgniteBiTuple.readExternal(IgniteBiTuple.java:276)
> at
> org.apache.ignite.marshaller.optimized.OptimizedObjectInputStream.readExternalizable(OptimizedObjectInputStream.java:514)
> at
> org.apache.ignite.marshaller.optimized.OptimizedClassDescriptor.read(OptimizedClassDescriptor.java:803)
> at
> org.apache.ignite.marshaller.optimized.OptimizedObjectInputStream.readObjectOverride(OptimizedObjectInputStream.java:315)
> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:365)
> at
> org.apache.ignite.marshaller.optimized.OptimizedMarshaller.unmarshal(OptimizedMarshaller.java:240)
> at
> org.gridgain.grid.internal.processors.cache.store.local.CacheFileLocalStoreFileManager$3.apply(CacheFileLocalStoreFileManager.java:1041)
> at
> org.gridgain.grid.internal.processors.cache.store.local.CacheFileLocalStoreMap.iterate(CacheFileLocalStoreMap.java:450)
> at
>
[jira] [Updated] (IGNITE-2386) affinityCall() execution hangs
[
https://issues.apache.org/jira/browse/IGNITE-2386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ershov updated IGNITE-2386:
Labels: 1.5.4 (was: )
> affinityCall() execution hangs
> --
>
> Key: IGNITE-2386
> URL: https://issues.apache.org/jira/browse/IGNITE-2386
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Reporter: Valentin Kulichenko
>Priority: Critical
> Labels: 1.5.4
> Fix For: 1.6
>
> Attachments: AffinityTest.java
>
>
> Test reproducing the issue is attached. affinityCall() invocation hangs with
> the following trace:
> {noformat}
> "main" prio=5 tid=0x7f8b1b001800 nid=0x1703 waiting on condition
> [0x70218000]
>java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0x0007ab170eb8> (a
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache$AffinityReadyFuture)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:157)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:115)
> at
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.awaitTopologyVersion(GridAffinityAssignmentCache.java:477)
> at
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.cachedAffinity(GridAffinityAssignmentCache.java:435)
> at
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.assignments(GridAffinityAssignmentCache.java:306)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.assignments(GridCacheAffinityManager.java:159)
> at
> org.apache.ignite.internal.processors.affinity.GridAffinityProcessor.affinityCache(GridAffinityProcessor.java:333)
> at
> org.apache.ignite.internal.processors.affinity.GridAffinityProcessor.affinityKey(GridAffinityProcessor.java:238)
> at
> org.apache.ignite.internal.processors.closure.GridClosureProcessor.affinityCall(GridClosureProcessor.java:442)
> at
> org.apache.ignite.internal.IgniteComputeImpl.affinityCall(IgniteComputeImpl.java:130)
> at AffinityTest.main(AffinityTest.java:42)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2099) Binary marshaller writes any map as a HashMap
[ https://issues.apache.org/jira/browse/IGNITE-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ershov updated IGNITE-2099: Labels: 1.5.4 (was: ) > Binary marshaller writes any map as a HashMap > - > > Key: IGNITE-2099 > URL: https://issues.apache.org/jira/browse/IGNITE-2099 > Project: Ignite > Issue Type: Bug > Components: general, interop >Reporter: Valentin Kulichenko >Assignee: Alexey Goncharuk >Priority: Critical > Labels: 1.5.4 > Fix For: 1.5 > > > Bug is described and discussed in this user@ thread: > http://apache-ignite-users.70518.x6.nabble.com/Serialization-issue-with-Ignite-1-5-built-from-master-357d791-td2149.html > In general, we need to make sure that binary marshaller fully supports Java > serialization and behaves consistently with optimized marshaller. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2032) Filters passed to ScanQuery are not redeployed when originating from a client node
[ https://issues.apache.org/jira/browse/IGNITE-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ershov updated IGNITE-2032: Labels: 1.5.4 important (was: important) > Filters passed to ScanQuery are not redeployed when originating from a client > node > -- > > Key: IGNITE-2032 > URL: https://issues.apache.org/jira/browse/IGNITE-2032 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: ignite-1.4 >Reporter: Denis Magda >Assignee: Alexey Goncharuk >Priority: Critical > Labels: 1.5.4, important > Fix For: 1.6 > > Attachments: ScanQueryFailure.java, test-config.xml > > > The following case doesn't work: > - start a standalone server node with peer class loading enabled; > - start a client node, populate a cache with data, perform a scan query using > a filter; > - since the server doesn't have the filter in its classpath it will load it > from the client. Everything works fine here; > - stop the client, the server will undeploy the filter. No issue here so far; > - modify the filter a bit and start the client one more time. The server > won't deploy the new version of the filter and will be using the old > regardless of the fact that it was undeployed before according to the logs. > The server can be started using ignite.bat and test-config.xml (attached). > The source of the client is located in attached ScanQueryFailure.java. > BTW, everything works fine if to use the server mode instead of the client > one. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1811) Get from backup in Dht cache can be optimized
[ https://issues.apache.org/jira/browse/IGNITE-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ershov updated IGNITE-1811: Labels: 1.5.4 (was: ) > Get from backup in Dht cache can be optimized > - > > Key: IGNITE-1811 > URL: https://issues.apache.org/jira/browse/IGNITE-1811 > Project: Ignite > Issue Type: Sub-task >Reporter: Yakov Zhdanov >Priority: Blocker > Labels: 1.5.4 > Fix For: 1.6 > > Attachments: Screenshot 2015-10-29 18.04.07.png > > > Reproducible example: https://gist.github.com/aboudnik/3419fdc3872cc3051a1d > See attached screenshot for sampling info. > Issues found: > # entry is created with putIfObsoleteOrAbsent() even if store and swap are > disabled > # no need to create DhtGetFuture on primary when there is no ongoing > rebalancing > Make sure the performance is fixed for ATOMIC and TRANSACTIONAL REPLICATED & > PARTITIONED caches. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2400) [Test] [Rare] GridCacheReplicatedDataStructuresFailoverSelfTest.testQueueTopologyChange
Vladimir Ershov created IGNITE-2400:
---
Summary: [Test] [Rare]
GridCacheReplicatedDataStructuresFailoverSelfTest.testQueueTopologyChange
Key: IGNITE-2400
URL: https://issues.apache.org/jira/browse/IGNITE-2400
Project: Ignite
Issue Type: Bug
Reporter: Vladimir Ershov
Priority: Minor
Very rare Failed. Log:
{noformat}
[19:09:22,500][INFO
][grid-starter-testQueueTopologyChange-2][GridCacheReplicatedDataStructuresFailoverSelfTest1]
>>>__
>>> / _/ ___/ |/ / _/_ __/ __/
>>> _/ // (7 7// / / / / _/
>>> /___/\___/_/|_/___/ /_/ /___/
>>>
>>> ver. 1.5.1-final-SNAPSHOT#20160118-sha1:67791457
>>> 2016 Copyright(C) Apache Software Foundation
>>>
>>> Ignite documentation: http://ignite.apache.org
[19:09:22,500][INFO
][grid-starter-testQueueTopologyChange-2][GridCacheReplicatedDataStructuresFailoverSelfTest1]
Config URL: n/a
[19:09:22,500][INFO
][grid-starter-testQueueTopologyChange-2][GridCacheReplicatedDataStructuresFailoverSelfTest1]
Daemon mode: off
[19:09:22,500][INFO
][grid-starter-testQueueTopologyChange-2][GridCacheReplicatedDataStructuresFailoverSelfTest1]
OS: Linux 2.6.32-573.12.1.el6.x86_64 amd64
[19:09:22,500][INFO
][grid-starter-testQueueTopologyChange-2][GridCacheReplicatedDataStructuresFailoverSelfTest1]
OS user: teamcity
[19:09:22,500][INFO
][grid-starter-testQueueTopologyChange-2][GridCacheReplicatedDataStructuresFailoverSelfTest1]
Language runtime: Java Platform API Specification ver. 1.7
[19:09:22,500][INFO
][grid-starter-testQueueTopologyChange-2][GridCacheReplicatedDataStructuresFailoverSelfTest1]
VM information: Java(TM) SE Runtime Environment 1.7.0_80-b15 Oracle
Corporation Java HotSpot(TM) 64-Bit Server VM 24.80-b11
[19:09:22,500][INFO
][grid-starter-testQueueTopologyChange-2][GridCacheReplicatedDataStructuresFailoverSelfTest1]
VM total memory: 2.7GB
[19:09:22,500][INFO
][grid-starter-testQueueTopologyChange-2][GridCacheReplicatedDataStructuresFailoverSelfTest1]
Remote Management [restart: off, REST: off, JMX (remote: off)]
[19:09:22,500][INFO
][grid-starter-testQueueTopologyChange-2][GridCacheReplicatedDataStructuresFailoverSelfTest1]
IGNITE_HOME=/mnt/tc_disk/work/b9d877891a53d8fe
[19:09:22,500][INFO
][grid-starter-testQueueTopologyChange-2][GridCacheReplicatedDataStructuresFailoverSelfTest1]
VM arguments: [-DJAVA_HOME=/usr/lib/jvm/java-7-oracle,
-Dagent.home.dir=/home/teamcity/agent, -Dagent.name=a_228_44,
-Dagent.ownPort=9044, -Dagent.work.dir=/mnt/tc_disk/work, -Dbuild.number=251,
-Dbuild.vcs.number=67791457f87097469f0efadcea6c6d13dd2ed37f,
-Dbuild.vcs.number.1=67791457f87097469f0efadcea6c6d13dd2ed37f,
-Dbuild.vcs.number.IgniteTests_ApacheIgniteMirrorOnGitHub1=67791457f87097469f0efadcea6c6d13dd2ed37f,
-Dclassworlds.conf=/mnt/tc_disk/temp/buildTmp/teamcity.m2.conf,
-Dcom.jetbrains.maven.watcher.report.file=/mnt/tc_disk/temp/buildTmp/maven-build-info.xml,
-Djava.io.tmpdir=/mnt/tc_disk/temp/buildTmp,
-Dmaven.home=/home/teamcity/agent/tools/maven3,
-Dmaven.repo.local=/home/teamcity/.m2/repository,
-Dteamcity.agent.cpuBenchmark=612,
-Dteamcity.agent.dotnet.agent_url=http://localhost:9044/RPC2,
-Dteamcity.agent.dotnet.build_id=98493,
-Dteamcity.auth.password=CbDuHJH3Q2dmVXRjeYzMbVejOZZDeEDb,
-Dteamcity.auth.userId=TeamCityBuildId=98493,
-Dteamcity.build.changedFiles.file=/mnt/tc_disk/temp/buildTmp/changedFiles6971648059137154933.txt,
-Dteamcity.build.checkoutDir=/mnt/tc_disk/work/b9d877891a53d8fe,
-Dteamcity.build.id=98493,
-Dteamcity.build.properties.file=/mnt/tc_disk/temp/buildTmp/teamcity.build685147608221190172.properties,
-Dteamcity.build.tempDir=/mnt/tc_disk/temp/buildTmp,
-Dteamcity.build.workingDir=/mnt/tc_disk/work/b9d877891a53d8fe,
-Dteamcity.buildConfName=Ignite Binary Objects Data Strucutures,
-Dteamcity.buildType.id=IgniteTests_IgniteBinaryObjectsDataStrucutures,
-Dteamcity.configuration.properties.file=/mnt/tc_disk/temp/buildTmp/teamcity.config3300810008320663426.properties,
-Dteamcity.maven.watcher.home=/home/teamcity/agent/plugins/mavenPlugin/maven-watcher,
-Dteamcity.projectName=Ignite Tests,
-Dteamcity.runner.properties.file=/mnt/tc_disk/temp/buildTmp/teamcity.runner8006302695410654754.properties,
-Dteamcity.tests.recentlyFailedTests.file=/mnt/tc_disk/temp/buildTmp/testsToRunFirst5887954035965893252.txt,
-Dteamcity.version=8.1.5 (build 30240), -ea, -XX:MaxPermSize=1g, -Xms1g,
-Xmx3g, -XX:+HeapDumpOnOutOfMemoryError, -XX:+AggressiveOpts,
-DIGNITE_TEST_HOME=/mnt/tc_disk/work/b9d877891a53d8fe,
-DIGNITE_UPDATE_NOTIFIER=false, -DIGNITE_NO_DISCO_ORDER=true,
-DIGNITE_QUIET=false]
[19:09:22,501][INFO
][grid-starter-testQueueTopologyChange-2][GridCacheReplicatedDataStructuresFailoverSelfTest1]
Configured caches ['ignite-marshaller-sys-cache', 'ignite-sys-cache',
'ignite-atomics-sys-cache', 'tx_cache']
[19:09:22,501][INFO
[jira] [Commented] (IGNITE-1611) [Test Failed] GridNearCacheTxNodeFailureSelfTest.testPrimaryNodeFailureBackupCommitImplicit
[
https://issues.apache.org/jira/browse/IGNITE-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15106503#comment-15106503
]
Vladimir Ershov commented on IGNITE-1611:
-
Muted on other TC.
> [Test Failed]
> GridNearCacheTxNodeFailureSelfTest.testPrimaryNodeFailureBackupCommitImplicit
> ---
>
> Key: IGNITE-1611
> URL: https://issues.apache.org/jira/browse/IGNITE-1611
> Project: Ignite
> Issue Type: Test
>Affects Versions: 1.5
>Reporter: Anton Vinogradov
>Priority: Blocker
> Labels: Muted_test
> Fix For: 1.5
>
>
> There is no guarantee that test failure will be produced each test run,
> please analyze logs in case of reproduction problem:
> {noformat}
> junit.framework.AssertionFailedError: near=GridNearCacheEntry [topVer=4,
> dhtVer=GridCacheVersion [topVer=55263880, nodeOrderDrId=1,
> globalTime=1443783881869, order=1443783876675], part=2,
> super=GridDistributedCacheEntry [super=GridCacheMapEntry
> [key=KeyCacheObjectImpl [val=2, hasValBytes=true], val=CacheObjectImpl
> [val=2, hasValBytes=true], startVer=1443783876676, ver=GridCacheVersion
> [topVer=55263880, nodeOrderDrId=1, globalTime=1443783881869,
> order=1443783876675], hash=821347078, extras=null, flags=0]]]
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.Assert.assertNull(Assert.java:277)
> at junit.framework.TestCase.assertNull(TestCase.java:447)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridCacheTxNodeFailureSelfTest.dataCheck(GridCacheTxNodeFailureSelfTest.java:342)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridCacheTxNodeFailureSelfTest.checkPrimaryNodeFailureBackupCommit(GridCacheTxNodeFailureSelfTest.java:302)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridCacheTxNodeFailureSelfTest.testPrimaryNodeFailureBackupCommitImplicit(GridCacheTxNodeFailureSelfTest.java:161)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1665)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:111)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:1603)
> --- Stdout: ---
> [14:04:36,650][INFO ][main][root] >>> Starting test:
> testPrimaryNodeFailureBackupCommitImplicit <<<
> [14:04:36,661][INFO ][test-runner][GridNearCacheTxNodeFailureSelfTest0]
> >>>__
> >>> / _/ ___/ |/ / _/_ __/ __/
> >>> _/ // (7 7// / / / / _/
> >>> /___/\___/_/|_/___/ /_/ /___/
> >>>
> >>> ver. 1.5.0-SNAPSHOT#19700101-sha1:DEV
> >>> 2015 Copyright(C) Apache Software Foundation
> >>>
> >>> Ignite documentation: http://ignite.apache.org
> [14:04:36,664][INFO ][test-runner][GridNearCacheTxNodeFailureSelfTest0]
> Config URL: n/a
> [14:04:36,664][INFO ][test-runner][GridNearCacheTxNodeFailureSelfTest0]
> Daemon mode: off
> [14:04:36,664][INFO ][test-runner][GridNearCacheTxNodeFailureSelfTest0] OS:
> Linux 2.6.32-38-generic amd64
> [14:04:36,664][INFO ][test-runner][GridNearCacheTxNodeFailureSelfTest0] OS
> user: teamcity
> [14:04:36,664][INFO ][test-runner][GridNearCacheTxNodeFailureSelfTest0]
> Language runtime: Java Platform API Specification ver. 1.7
> [14:04:36,664][INFO ][test-runner][GridNearCacheTxNodeFailureSelfTest0] VM
> information: Java(TM) SE Runtime Environment 1.7.0_80-b15 Oracle Corporation
> Java HotSpot(TM) 64-Bit Server VM 24.80-b11
> [14:04:36,664][INFO ][test-runner][GridNearCacheTxNodeFailureSelfTest0] VM
> total memory: 2.7GB
> [14:04:36,664][INFO ][test-runner][GridNearCacheTxNodeFailureSelfTest0]
> Remote Management [restart: off, REST: off, JMX (remote: off)]
> [14:04:36,664][INFO ][test-runner][GridNearCacheTxNodeFailureSelfTest0]
> IGNITE_HOME=/usr/local/TeamCityAgent/work/871ff4a46e450b13
> [14:04:36,664][INFO ][test-runner][GridNearCacheTxNodeFailureSelfTest0] VM
> arguments: [-DJAVA_HOME=/usr/lib/jvm/java-7-oracle, -DMCAST_GRP=229.13.1.2,
> -Dagent.home.dir=/usr/local/TeamCityAgent, -Dagent.name=teamcity-3,
> -Dagent.ownPort=9090, -Dagent.work.dir=/usr/local/TeamCityAgent/work,
> -Dbuild.number=3390,
> -Dbuild.vcs.number=7b54cbd7499cd498b04e821dfa3b572bd94debec,
>
[jira] [Created] (IGNITE-2401) [Test] [Rare] IgniteCacheCreatePutTest.testStartNodes
Vladimir Ershov created IGNITE-2401:
---
Summary: [Test] [Rare] IgniteCacheCreatePutTest.testStartNodes
Key: IGNITE-2401
URL: https://issues.apache.org/jira/browse/IGNITE-2401
Project: Ignite
Issue Type: Bug
Reporter: Vladimir Ershov
Priority: Minor
Rare:
{noformat}
org.apache.ignite.IgniteCheckedException: null
at
org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryManager.onKernalStart0(CacheContinuousQueryManager.java:134)
at
org.apache.ignite.internal.processors.cache.GridCacheManagerAdapter.onKernalStart(GridCacheManagerAdapter.java:98)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStart(GridCacheProcessor.java:1155)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStart(GridCacheProcessor.java:802)
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:909)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1688)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1547)
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1003)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:534)
at
org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:735)
at
org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:719)
at
org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:696)
at
org.apache.ignite.internal.processors.cache.distributed.IgniteCacheCreatePutTest.access$000(IgniteCacheCreatePutTest.java:37)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-2406) [Test] [Rare] GridEventStorageCheckAllEventsSelfTest.testSuccessTask
Vladimir Ershov created IGNITE-2406:
---
Summary: [Test] [Rare]
GridEventStorageCheckAllEventsSelfTest.testSuccessTask
Key: IGNITE-2406
URL: https://issues.apache.org/jira/browse/IGNITE-2406
Project: Ignite
Issue Type: Bug
Reporter: Vladimir Ershov
Priority: Minor
Rare fail of GridEventStorageCheckAllEventsSelfTest testSuccessTask
log:
{noformat}
--- Stderr: ---
[13:06:47,647][WARN ][main][GridEventStorageCheckAllEventsSelfTest] Peer class
loading is enabled (disable it in production for performance and deployment
consistency reasons)
[13:06:47,659][WARN ][main][GridCollisionManager] Collision resolution is
disabled (all jobs will be activated upon arrival).
[13:06:47,660][WARN ][main][NoopSwapSpaceSpi] Swap space is disabled. To enable
use FileSwapSpaceSpi.
[13:06:48,966][ERROR][main][root] Test failed.
java.lang.AssertionError: Invalid event [evtType=45, expectedType=41,
evts=[TaskEvent
[taskName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
taskClsName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
sesId=e53ddf95251-af0890dd-f87e-4dca-8b22-bab1b6a13404, internal=false,
subjId=af0890dd-f87e-4dca-8b22-bab1b6a13404, nodeId8=af0890dd, msg=Task
started., type=TASK_STARTED, tstamp=1453208808959], JobEvent
[taskName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
taskClsName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
sesId=e53ddf95251-af0890dd-f87e-4dca-8b22-bab1b6a13404,
jobId=063ddf95251-af0890dd-f87e-4dca-8b22-bab1b6a13404,
taskNode=TcpDiscoveryNode [id=af0890dd-f87e-4dca-8b22-bab1b6a13404,
addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1,
intOrder=1, lastExchangeTime=1453208807679, loc=true,
ver=1.5.1#20160119-sha1:09c1d5e4, isClient=false],
taskSubjId=af0890dd-f87e-4dca-8b22-bab1b6a13404, nodeId8=af0890dd, msg=Job got
mapped., type=JOB_MAPPED, tstamp=1453208808959], JobEvent
[taskName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
taskClsName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
sesId=e53ddf95251-af0890dd-f87e-4dca-8b22-bab1b6a13404,
jobId=063ddf95251-af0890dd-f87e-4dca-8b22-bab1b6a13404,
taskNode=TcpDiscoveryNode [id=af0890dd-f87e-4dca-8b22-bab1b6a13404,
addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1,
intOrder=1, lastExchangeTime=1453208807679, loc=true,
ver=1.5.1#20160119-sha1:09c1d5e4, isClient=false],
taskSubjId=af0890dd-f87e-4dca-8b22-bab1b6a13404, nodeId8=af0890dd, msg=Job got
queued for computation., type=JOB_QUEUED, tstamp=1453208808959], JobEvent
[taskName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
taskClsName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
sesId=e53ddf95251-af0890dd-f87e-4dca-8b22-bab1b6a13404,
jobId=063ddf95251-af0890dd-f87e-4dca-8b22-bab1b6a13404,
taskNode=TcpDiscoveryNode [id=af0890dd-f87e-4dca-8b22-bab1b6a13404,
addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1,
intOrder=1, lastExchangeTime=1453208807679, loc=true,
ver=1.5.1#20160119-sha1:09c1d5e4, isClient=false],
taskSubjId=af0890dd-f87e-4dca-8b22-bab1b6a13404, nodeId8=af0890dd, msg=null,
type=JOB_STARTED, tstamp=1453208808959], CheckpointEvent [cpKey=testCheckpoint,
nodeId8=af0890dd, msg=Checkpoint saved: testCheckpoint, type=CHECKPOINT_SAVED,
tstamp=1453208808959], CheckpointEvent [cpKey=testCheckpoint, nodeId8=af0890dd,
msg=Checkpoint removed: testCheckpoint, type=CHECKPOINT_REMOVED,
tstamp=1453208808959], JobEvent
[taskName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
taskClsName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
sesId=e53ddf95251-af0890dd-f87e-4dca-8b22-bab1b6a13404,
jobId=063ddf95251-af0890dd-f87e-4dca-8b22-bab1b6a13404,
taskNode=TcpDiscoveryNode [id=af0890dd-f87e-4dca-8b22-bab1b6a13404,
addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1,
intOrder=1, lastExchangeTime=1453208807679, loc=true,
ver=1.5.1#20160119-sha1:09c1d5e4, isClient=false],
taskSubjId=af0890dd-f87e-4dca-8b22-bab1b6a13404, nodeId8=af0890dd, msg=null,
type=JOB_FINISHED, tstamp=1453208808959], JobEvent
[taskName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
taskClsName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
sesId=e53ddf95251-af0890dd-f87e-4dca-8b22-bab1b6a13404,
jobId=063ddf95251-af0890dd-f87e-4dca-8b22-bab1b6a13404,
taskNode=TcpDiscoveryNode [id=af0890dd-f87e-4dca-8b22-bab1b6a13404,
addrs=[127.0.0.1],
[jira] [Updated] (IGNITE-2406) [Test] [Rare] GridEventStorageCheckAllEventsSelfTest.testSuccessTask AND GridEventStorageCheckAllEventsSelfTest.testFailTask
[
https://issues.apache.org/jira/browse/IGNITE-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ershov updated IGNITE-2406:
Description:
Rare fail of GridEventStorageCheckAllEventsSelfTest testSuccessTask
log:
{noformat}
--- Stderr: ---
[13:06:47,647][WARN ][main][GridEventStorageCheckAllEventsSelfTest] Peer class
loading is enabled (disable it in production for performance and deployment
consistency reasons)
[13:06:47,659][WARN ][main][GridCollisionManager] Collision resolution is
disabled (all jobs will be activated upon arrival).
[13:06:47,660][WARN ][main][NoopSwapSpaceSpi] Swap space is disabled. To enable
use FileSwapSpaceSpi.
[13:06:48,966][ERROR][main][root] Test failed.
java.lang.AssertionError: Invalid event [evtType=45, expectedType=41,
evts=[TaskEvent
[taskName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
taskClsName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
sesId=e53ddf95251-af0890dd-f87e-4dca-8b22-bab1b6a13404, internal=false,
subjId=af0890dd-f87e-4dca-8b22-bab1b6a13404, nodeId8=af0890dd, msg=Task
started., type=TASK_STARTED, tstamp=1453208808959], JobEvent
[taskName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
taskClsName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
sesId=e53ddf95251-af0890dd-f87e-4dca-8b22-bab1b6a13404,
jobId=063ddf95251-af0890dd-f87e-4dca-8b22-bab1b6a13404,
taskNode=TcpDiscoveryNode [id=af0890dd-f87e-4dca-8b22-bab1b6a13404,
addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1,
intOrder=1, lastExchangeTime=1453208807679, loc=true,
ver=1.5.1#20160119-sha1:09c1d5e4, isClient=false],
taskSubjId=af0890dd-f87e-4dca-8b22-bab1b6a13404, nodeId8=af0890dd, msg=Job got
mapped., type=JOB_MAPPED, tstamp=1453208808959], JobEvent
[taskName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
taskClsName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
sesId=e53ddf95251-af0890dd-f87e-4dca-8b22-bab1b6a13404,
jobId=063ddf95251-af0890dd-f87e-4dca-8b22-bab1b6a13404,
taskNode=TcpDiscoveryNode [id=af0890dd-f87e-4dca-8b22-bab1b6a13404,
addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1,
intOrder=1, lastExchangeTime=1453208807679, loc=true,
ver=1.5.1#20160119-sha1:09c1d5e4, isClient=false],
taskSubjId=af0890dd-f87e-4dca-8b22-bab1b6a13404, nodeId8=af0890dd, msg=Job got
queued for computation., type=JOB_QUEUED, tstamp=1453208808959], JobEvent
[taskName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
taskClsName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
sesId=e53ddf95251-af0890dd-f87e-4dca-8b22-bab1b6a13404,
jobId=063ddf95251-af0890dd-f87e-4dca-8b22-bab1b6a13404,
taskNode=TcpDiscoveryNode [id=af0890dd-f87e-4dca-8b22-bab1b6a13404,
addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1,
intOrder=1, lastExchangeTime=1453208807679, loc=true,
ver=1.5.1#20160119-sha1:09c1d5e4, isClient=false],
taskSubjId=af0890dd-f87e-4dca-8b22-bab1b6a13404, nodeId8=af0890dd, msg=null,
type=JOB_STARTED, tstamp=1453208808959], CheckpointEvent [cpKey=testCheckpoint,
nodeId8=af0890dd, msg=Checkpoint saved: testCheckpoint, type=CHECKPOINT_SAVED,
tstamp=1453208808959], CheckpointEvent [cpKey=testCheckpoint, nodeId8=af0890dd,
msg=Checkpoint removed: testCheckpoint, type=CHECKPOINT_REMOVED,
tstamp=1453208808959], JobEvent
[taskName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
taskClsName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
sesId=e53ddf95251-af0890dd-f87e-4dca-8b22-bab1b6a13404,
jobId=063ddf95251-af0890dd-f87e-4dca-8b22-bab1b6a13404,
taskNode=TcpDiscoveryNode [id=af0890dd-f87e-4dca-8b22-bab1b6a13404,
addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1,
intOrder=1, lastExchangeTime=1453208807679, loc=true,
ver=1.5.1#20160119-sha1:09c1d5e4, isClient=false],
taskSubjId=af0890dd-f87e-4dca-8b22-bab1b6a13404, nodeId8=af0890dd, msg=null,
type=JOB_FINISHED, tstamp=1453208808959], JobEvent
[taskName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
taskClsName=org.apache.ignite.internal.GridEventStorageCheckAllEventsSelfTest$GridAllEventsTestTask,
sesId=e53ddf95251-af0890dd-f87e-4dca-8b22-bab1b6a13404,
jobId=063ddf95251-af0890dd-f87e-4dca-8b22-bab1b6a13404,
taskNode=TcpDiscoveryNode [id=af0890dd-f87e-4dca-8b22-bab1b6a13404,
addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1,
intOrder=1, lastExchangeTime=1453208807679, loc=true,
ver=1.5.1#20160119-sha1:09c1d5e4, isClient=false],
[jira] [Commented] (IGNITE-1611) [Test Failed] GridNearCacheTxNodeFailureSelfTest.testPrimaryNodeFailureBackupCommitImplicit
[
https://issues.apache.org/jira/browse/IGNITE-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15106893#comment-15106893
]
Vladimir Ershov commented on IGNITE-1611:
-
One which is not public.
> [Test Failed]
> GridNearCacheTxNodeFailureSelfTest.testPrimaryNodeFailureBackupCommitImplicit
> ---
>
> Key: IGNITE-1611
> URL: https://issues.apache.org/jira/browse/IGNITE-1611
> Project: Ignite
> Issue Type: Test
>Affects Versions: 1.5
>Reporter: Anton Vinogradov
>Priority: Blocker
> Labels: Muted_test
> Fix For: 1.6
>
>
> There is no guarantee that test failure will be produced each test run,
> please analyze logs in case of reproduction problem:
> {noformat}
> junit.framework.AssertionFailedError: near=GridNearCacheEntry [topVer=4,
> dhtVer=GridCacheVersion [topVer=55263880, nodeOrderDrId=1,
> globalTime=1443783881869, order=1443783876675], part=2,
> super=GridDistributedCacheEntry [super=GridCacheMapEntry
> [key=KeyCacheObjectImpl [val=2, hasValBytes=true], val=CacheObjectImpl
> [val=2, hasValBytes=true], startVer=1443783876676, ver=GridCacheVersion
> [topVer=55263880, nodeOrderDrId=1, globalTime=1443783881869,
> order=1443783876675], hash=821347078, extras=null, flags=0]]]
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.Assert.assertNull(Assert.java:277)
> at junit.framework.TestCase.assertNull(TestCase.java:447)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridCacheTxNodeFailureSelfTest.dataCheck(GridCacheTxNodeFailureSelfTest.java:342)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridCacheTxNodeFailureSelfTest.checkPrimaryNodeFailureBackupCommit(GridCacheTxNodeFailureSelfTest.java:302)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridCacheTxNodeFailureSelfTest.testPrimaryNodeFailureBackupCommitImplicit(GridCacheTxNodeFailureSelfTest.java:161)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1665)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:111)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:1603)
> --- Stdout: ---
> [14:04:36,650][INFO ][main][root] >>> Starting test:
> testPrimaryNodeFailureBackupCommitImplicit <<<
> [14:04:36,661][INFO ][test-runner][GridNearCacheTxNodeFailureSelfTest0]
> >>>__
> >>> / _/ ___/ |/ / _/_ __/ __/
> >>> _/ // (7 7// / / / / _/
> >>> /___/\___/_/|_/___/ /_/ /___/
> >>>
> >>> ver. 1.5.0-SNAPSHOT#19700101-sha1:DEV
> >>> 2015 Copyright(C) Apache Software Foundation
> >>>
> >>> Ignite documentation: http://ignite.apache.org
> [14:04:36,664][INFO ][test-runner][GridNearCacheTxNodeFailureSelfTest0]
> Config URL: n/a
> [14:04:36,664][INFO ][test-runner][GridNearCacheTxNodeFailureSelfTest0]
> Daemon mode: off
> [14:04:36,664][INFO ][test-runner][GridNearCacheTxNodeFailureSelfTest0] OS:
> Linux 2.6.32-38-generic amd64
> [14:04:36,664][INFO ][test-runner][GridNearCacheTxNodeFailureSelfTest0] OS
> user: teamcity
> [14:04:36,664][INFO ][test-runner][GridNearCacheTxNodeFailureSelfTest0]
> Language runtime: Java Platform API Specification ver. 1.7
> [14:04:36,664][INFO ][test-runner][GridNearCacheTxNodeFailureSelfTest0] VM
> information: Java(TM) SE Runtime Environment 1.7.0_80-b15 Oracle Corporation
> Java HotSpot(TM) 64-Bit Server VM 24.80-b11
> [14:04:36,664][INFO ][test-runner][GridNearCacheTxNodeFailureSelfTest0] VM
> total memory: 2.7GB
> [14:04:36,664][INFO ][test-runner][GridNearCacheTxNodeFailureSelfTest0]
> Remote Management [restart: off, REST: off, JMX (remote: off)]
> [14:04:36,664][INFO ][test-runner][GridNearCacheTxNodeFailureSelfTest0]
> IGNITE_HOME=/usr/local/TeamCityAgent/work/871ff4a46e450b13
> [14:04:36,664][INFO ][test-runner][GridNearCacheTxNodeFailureSelfTest0] VM
> arguments: [-DJAVA_HOME=/usr/lib/jvm/java-7-oracle, -DMCAST_GRP=229.13.1.2,
> -Dagent.home.dir=/usr/local/TeamCityAgent, -Dagent.name=teamcity-3,
> -Dagent.ownPort=9090, -Dagent.work.dir=/usr/local/TeamCityAgent/work,
> -Dbuild.number=3390,
> -Dbuild.vcs.number=7b54cbd7499cd498b04e821dfa3b572bd94debec,
>
[jira] [Created] (IGNITE-2410) Ignite Platform .NET JVM crashed on TC
Vladimir Ershov created IGNITE-2410: --- Summary: Ignite Platform .NET JVM crashed on TC Key: IGNITE-2410 URL: https://issues.apache.org/jira/browse/IGNITE-2410 Project: Ignite Issue Type: Bug Reporter: Vladimir Ershov Assignee: Pavel Tupitsyn Result: JVM crashed (new); tests passed: 107; NUnit runner failure (new) Agent: w_box_02 (Default pool) Time: 18 Jan 16 22:12 - 22:25 (13m:08s) T riggered by:Git on 18 Jan 16 16:22 Branch: refs/heads/master -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2410) Ignite Platform .NET JVM crashed on TC
[ https://issues.apache.org/jira/browse/IGNITE-2410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ershov updated IGNITE-2410: Attachment: Ignite_Tests_Ignite_Platform_.NET_224_artifacts.zip > Ignite Platform .NET JVM crashed on TC > -- > > Key: IGNITE-2410 > URL: https://issues.apache.org/jira/browse/IGNITE-2410 > Project: Ignite > Issue Type: Bug >Reporter: Vladimir Ershov >Assignee: Pavel Tupitsyn > Attachments: Ignite_Tests_Ignite_Platform_.NET_224_artifacts.zip > > > Result: JVM crashed (new); > tests passed: 107; > NUnit runner failure (new)Agent: w_box_02 (Default pool) > Time: 18 Jan 16 22:12 - 22:25 (13m:08s) T > riggered by: Git on 18 Jan 16 16:22 > Branch: refs/heads/master -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2410) Ignite Platform .NET JVM crashed on TC
[
https://issues.apache.org/jira/browse/IGNITE-2410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ershov updated IGNITE-2410:
Description:
Result: JVM crashed (new);
tests passed: 107;
NUnit runner failure (new) Agent: w_box_02 (Default pool)
Time: 18 Jan 16 22:12 - 22:25 (13m:08s) T
riggered by:Git on 18 Jan 16 16:22
Branch: refs/heads/master
Artifacts are in the attachment.
{noformat}
[22:25:18][Step 8/11] #
[22:25:18][Step 8/11] # A fatal error has been detected by the Java Runtime
Environment:
[22:25:18][Step 8/11] #
[22:25:18][Step 8/11] # Internal Error (safepoint.cpp:692), pid=9052, tid=4356
[22:25:18][Step 8/11] # fatal error: Deadlock in safepoint code. Should have
called back to the VM before blocking.
[22:25:18][Step 8/11] #
[22:25:18][Step 8/11] # JRE version: Java(TM) SE Runtime Environment
(7.0_80-b15) (build 1.7.0_80-b15)
[22:25:18][Step 8/11] # Java VM: Java HotSpot(TM) 64-Bit Server VM (24.80-b11
mixed mode windows-amd64 compressed oops)
[22:25:18][Step 8/11] # Failed to write core dump. Minidumps are not enabled by
default on client versions of Windows
[22:25:18][Step 8/11] #
[22:25:18][Step 8/11] # An error report file with more information is saved as:
[22:25:18][Step 8/11] #
C:\BuildAgent\work\b9d877891a53d8fe\modules\platforms\dotnet\Apache.Ignite.Core.Tests\bin\x64\Debug\hs_err_pid9052.log
[22:25:18][Step 8/11] 2016-01-18 22:25:18,794 [4356] ERROR
JetBrains.TeamCity.NUnitLauncher.ErrorLoggerImpl - Unhandled exception in
remote appdomain: System.AccessViolationException: Attempted to read or write
protected memory. This is often an indication that other memory is corrupt.
[22:25:18][Step 8/11]at
Apache.Ignite.Core.Impl.Unmanaged.IgniteJniNativeMethods.Release(Void* target)
[22:25:18][Step 8/11]at
Apache.Ignite.Core.Impl.Unmanaged.UnmanagedUtils.Release(IUnmanagedTarget
target) in
c:\BuildAgent\work\b9d877891a53d8fe\modules\platforms\dotnet\Apache.Ignite.Core\Impl\Unmanaged\UnmanagedUtils.cs:line
702
[22:25:18][Step 8/11]at
Apache.Ignite.Core.Impl.Unmanaged.UnmanagedTarget.ReleaseHandle() in
c:\BuildAgent\work\b9d877891a53d8fe\modules\platforms\dotnet\Apache.Ignite.Core\Impl\Unmanaged\UnmanagedTarget.cs:line
66
[22:25:18][Step 8/11]at
System.Runtime.InteropServices.CriticalHandle.Cleanup()
[22:25:18][Step 8/11]at
System.Runtime.InteropServices.CriticalHandle.Finalize()
[22:25:18][Step 8/11] 2016-01-18 22:25:18,794 [4356] WARN
JetBrains.Container.Log4netDefaultLoggerInitializer - Unhandled exception in
current domain: System.AccessViolationException: Attempted to read or write
protected memory. This is often an indication that other memory is corrupt.
[22:25:18][Step 8/11]at
Apache.Ignite.Core.Impl.Unmanaged.IgniteJniNativeMethods.Release(Void* target)
[22:25:18][Step 8/11]at
Apache.Ignite.Core.Impl.Unmanaged.UnmanagedUtils.Release(IUnmanagedTarget
target) in
c:\BuildAgent\work\b9d877891a53d8fe\modules\platforms\dotnet\Apache.Ignite.Core\Impl\Unmanaged\UnmanagedUtils.cs:line
702
[22:25:18][Step 8/11]at
Apache.Ignite.Core.Impl.Unmanaged.UnmanagedTarget.ReleaseHandle() in
c:\BuildAgent\work\b9d877891a53d8fe\modules\platforms\dotnet\Apache.Ignite.Core\Impl\Unmanaged\UnmanagedTarget.cs:line
66
[22:25:18][Step 8/11]at
System.Runtime.InteropServices.CriticalHandle.Cleanup()
[22:25:18][Step 8/11]at
System.Runtime.InteropServices.CriticalHandle.Finalize(),at
Apache.Ignite.Core.Impl.Unmanaged.IgniteJniNativeMethods.Release(Void* target)
[22:25:18][Step 8/11]at
Apache.Ignite.Core.Impl.Unmanaged.UnmanagedUtils.Release(IUnmanagedTarget
target) in
c:\BuildAgent\work\b9d877891a53d8fe\modules\platforms\dotnet\Apache.Ignite.Core\Impl\Unmanaged\UnmanagedUtils.cs:line
702
[22:25:18][Step 8/11]at
Apache.Ignite.Core.Impl.Unmanaged.UnmanagedTarget.ReleaseHandle() in
c:\BuildAgent\work\b9d877891a53d8fe\modules\platforms\dotnet\Apache.Ignite.Core\Impl\Unmanaged\UnmanagedTarget.cs:line
66
[22:25:18][Step 8/11]at
System.Runtime.InteropServices.CriticalHandle.Cleanup()
[22:25:18][Step 8/11]at
System.Runtime.InteropServices.CriticalHandle.Finalize(), (null)
[22:25:18][Step 8/11] 2016-01-18 22:25:18,794 [4356] ERROR
JetBrains.TeamCity.NUnitLauncher.ErrorLoggerImpl - Unhandled exception in
remote appdomain: System.AccessViolationException: Attempted to read or write
protected memory. This is often an indication that other memory is corrupt.
[22:25:18][Step 8/11]at
Apache.Ignite.Core.Impl.Unmanaged.IgniteJniNativeMethods.Release(Void* target)
[22:25:18][Step 8/11]at
Apache.Ignite.Core.Impl.Unmanaged.UnmanagedUtils.Release(IUnmanagedTarget
target) in
c:\BuildAgent\work\b9d877891a53d8fe\modules\platforms\dotnet\Apache.Ignite.Core\Impl\Unmanaged\UnmanagedUtils.cs:line
702
[22:25:18][Step 8/11]at
Apache.Ignite.Core.Impl.Unmanaged.UnmanagedTarget.ReleaseHandle() in
[jira] [Updated] (IGNITE-2401) [Test] [Rare] IgniteCacheCreatePutTest.testStartNodes
[
https://issues.apache.org/jira/browse/IGNITE-2401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ershov updated IGNITE-2401:
Attachment: Ignite_Tests_Ignite_Binary_Objects_Cache_4_242_artifacts.zip
> [Test] [Rare] IgniteCacheCreatePutTest.testStartNodes
> -
>
> Key: IGNITE-2401
> URL: https://issues.apache.org/jira/browse/IGNITE-2401
> Project: Ignite
> Issue Type: Bug
>Reporter: Vladimir Ershov
>Priority: Minor
> Attachments:
> Ignite_Tests_Ignite_Binary_Objects_Cache_4_242_artifacts.zip
>
>
> Rare:
> {noformat}
> org.apache.ignite.IgniteCheckedException: null
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryManager.onKernalStart0(CacheContinuousQueryManager.java:134)
> at
> org.apache.ignite.internal.processors.cache.GridCacheManagerAdapter.onKernalStart(GridCacheManagerAdapter.java:98)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStart(GridCacheProcessor.java:1155)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStart(GridCacheProcessor.java:802)
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:909)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1688)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1547)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1003)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:534)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:735)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:719)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:696)
> at
> org.apache.ignite.internal.processors.cache.distributed.IgniteCacheCreatePutTest.access$000(IgniteCacheCreatePutTest.java:37)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-172) GridTcpCommunicationSpiRecoveryAckSelfTest and IgniteTcpCommunicationRecoveryAckClosureSelfTest
[ https://issues.apache.org/jira/browse/IGNITE-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ershov updated IGNITE-172: --- Labels: Muted-test (was: ) > GridTcpCommunicationSpiRecoveryAckSelfTest and > IgniteTcpCommunicationRecoveryAckClosureSelfTest > --- > > Key: IGNITE-172 > URL: https://issues.apache.org/jira/browse/IGNITE-172 > Project: Ignite > Issue Type: Bug > Components: general >Reporter: Irina Vasilinets > Labels: Muted_test > > GridTcpCommunicationSpiRecoveryAckSelfTest.testQueueOverflow and > GridTcpCommunicationSpiTcpNoDelayOffSelfTest.testSendToManyNodes > fail sometimes. > IgniteTcpCommunicationRecoveryAckClosureSelfTest.testQueueOverflow - 1 from 10 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-172) GridTcpCommunicationSpiRecoveryAckSelfTest and IgniteTcpCommunicationRecoveryAckClosureSelfTest
[ https://issues.apache.org/jira/browse/IGNITE-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ershov updated IGNITE-172: --- Labels: Muted_test (was: Muted-test) > GridTcpCommunicationSpiRecoveryAckSelfTest and > IgniteTcpCommunicationRecoveryAckClosureSelfTest > --- > > Key: IGNITE-172 > URL: https://issues.apache.org/jira/browse/IGNITE-172 > Project: Ignite > Issue Type: Bug > Components: general >Reporter: Irina Vasilinets > Labels: Muted_test > > GridTcpCommunicationSpiRecoveryAckSelfTest.testQueueOverflow and > GridTcpCommunicationSpiTcpNoDelayOffSelfTest.testSendToManyNodes > fail sometimes. > IgniteTcpCommunicationRecoveryAckClosureSelfTest.testQueueOverflow - 1 from 10 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1393) [Test] AssertionError when stop node executing transaction - GridCacheStopSelfTest
[
https://issues.apache.org/jira/browse/IGNITE-1393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ershov updated IGNITE-1393:
Summary: [Test] AssertionError when stop node executing transaction -
GridCacheStopSelfTest (was: AssertionError when stop node executing
transaction)
> [Test] AssertionError when stop node executing transaction -
> GridCacheStopSelfTest
> ---
>
> Key: IGNITE-1393
> URL: https://issues.apache.org/jira/browse/IGNITE-1393
> Project: Ignite
> Issue Type: Sub-task
> Components: cache
>Reporter: Semen Boikov
> Labels: Muted_test
>
> I fixed GridCacheStopSelfTest which was disabled for long time, now it fails
> because of asserts:
> {noformat}
> [10:53:02,362][ERROR][async-runner-1][GridNearTxLocal] Heuristic transaction
> failure.
> class
> org.apache.ignite.internal.transactions.IgniteTxHeuristicCheckedException:
> Failed to locally write to cache (all transaction entries will be
> invalidated, however there was a window when entries for this transaction
> were visible to others): GridNearTxLocal [nearLocallyMapped=false,
> colocatedLocallyMapped=true, hasRemoteLocks=false,
> mappings=[009f5238-db3d-426f-b787-9a4a156e8000], super=GridDhtTxLocalAdapter
> [dhtThreadId=101, needsCompletedVers=false, nearNodes=[], dhtNodes=[],
> explicitLock=false, super=IgniteTxLocalAdapter [txMap={IgniteTxKey
> [key=KeyCacheObjectImpl [val=22, hasValBytes=true], cacheId=1]=IgniteTxEntry
> [key=KeyCacheObjectImpl [val=22, hasValBytes=true], cacheId=1,
> txKey=IgniteTxKey [key=KeyCacheObjectImpl [val=22, hasValBytes=true],
> cacheId=1], val=[op=CREATE, val=UserCacheObjectImpl [val=22,
> hasValBytes=true]], prevVal=[op=CREATE, val=UserCacheObjectImpl [val=22,
> hasValBytes=true]], entryProcessorsCol=null, entryProcessorCalcVal=null,
> ttl=-1, conflictExpireTime=-1, conflictVer=null, explicitVer=null,
> dhtVer=GridCacheVersion [topVer=53261582, nodeOrderDrId=1,
> globalTime=1441781582327, order=1441781581691], filters=[],
> filtersPassed=false, filtersSet=true, entry=GridDhtColocatedCacheEntry
> [super=GridDhtCacheEntry [rdrs=[], locPart=GridDhtLocalPartition [id=22,
> mapPubSize=1, rmvQueue=GridCircularBuffer [sizeMask=31, idxGen=0],
> state=OWNING, reservations=0, empty=false, createTime=09/09/2015 10:53:02,
> mapPubSize=1], super=GridDistributedCacheEntry [super=GridCacheMapEntry
> [key=KeyCacheObjectImpl [val=22, hasValBytes=true], val=CacheObjectImpl
> [val=22, hasValBytes=true], startVer=1441781581658, ver=GridCacheVersion
> [topVer=53261582, nodeOrderDrId=1, globalTime=1441781582327,
> order=1441781581691], hash=2018242870, extras=null, flags=2,
> prepared=false, locked=true, nodeId=009f5238-db3d-426f-b787-9a4a156e8000,
> locMapped=false, expiryPlc=null, transferExpiryPlc=false, flags=0,
> xidVer=GridCacheVersion [topVer=53261582, nodeOrderDrId=1,
> globalTime=1441781582217, order=1441781581591]]}, completedBase=null,
> sndTransformedVals=false, super=IgniteTxAdapter [xidVer=GridCacheVersion
> [topVer=53261582, nodeOrderDrId=1, globalTime=1441781582217,
> order=1441781581591], writeVer=GridCacheVersion [topVer=53261582,
> nodeOrderDrId=1, globalTime=1441781582327, order=1441781581691],
> implicit=false, implicitSingle=false, loc=true, threadId=101,
> startTime=1441781582212, nodeId=009f5238-db3d-426f-b787-9a4a156e8000,
> startVer=GridCacheVersion [topVer=53261582, nodeOrderDrId=1,
> globalTime=1441781582218, order=1441781581611], endVer=GridCacheVersion
> [topVer=53261582, nodeOrderDrId=1, globalTime=1441781582336,
> order=1441781581738], isolation=REPEATABLE_READ, concurrency=PESSIMISTIC,
> timeout=0, sysInvalidate=false, sys=false, plc=2, commitVer=GridCacheVersion
> [topVer=53261582, nodeOrderDrId=1, globalTime=1441781582217,
> order=1441781581591], finalizing=NONE, preparing=false, state=COMMITTED,
> timedOut=false, topVer=AffinityTopologyVersion [topVer=1, minorTopVer=0],
> duration=138ms, onePhaseCommit=true], size=1]]]
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter.userCommit(IgniteTxLocalAdapter.java:1036)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.finish(GridNearTxLocal.java:654)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal$3.apply(GridNearTxLocal.java:749)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal$3.apply(GridNearTxLocal.java:741)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:262)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:225)
> at
>
[jira] [Comment Edited] (IGNITE-172) GridTcpCommunicationSpiRecoveryAckSelfTest and IgniteTcpCommunicationRecoveryAckClosureSelfTest
[
https://issues.apache.org/jira/browse/IGNITE-172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15105212#comment-15105212
]
Vladimir Ershov edited comment on IGNITE-172 at 1/18/16 12:22 PM:
--
TC build:
http://204.14.53.153/project.html?projectId=IgniteTests=-4500142517104203631=testDetails
Local trace:
{noformat}
C:\java\jdk8\bin\java -ea -Didea.launcher.port=7564
"-Didea.launcher.bin.path=C:\Program Files (x86)\JetBrains\IntelliJ IDEA
Community Edition 14.1.5\bin" -Dfile.encoding=windows-1251 -classpath
"C:\Program Files (x86)\JetBrains\IntelliJ IDEA Community Edition
14.1.5\lib\idea_rt.jar;C:\Program Files (x86)\JetBrains\IntelliJ IDEA Community
Edition
[jira] [Commented] (IGNITE-172) GridTcpCommunicationSpiRecoveryAckSelfTest and IgniteTcpCommunicationRecoveryAckClosureSelfTest
[
https://issues.apache.org/jira/browse/IGNITE-172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15105212#comment-15105212
]
Vladimir Ershov commented on IGNITE-172:
TC build:
http://204.14.53.153/project.html?projectId=IgniteTests=-4500142517104203631=testDetails
Local trace:
{quote}
C:\java\jdk8\bin\java -ea -Didea.launcher.port=7564
"-Didea.launcher.bin.path=C:\Program Files (x86)\JetBrains\IntelliJ IDEA
Community Edition 14.1.5\bin" -Dfile.encoding=windows-1251 -classpath
"C:\Program Files (x86)\JetBrains\IntelliJ IDEA Community Edition
14.1.5\lib\idea_rt.jar;C:\Program Files (x86)\JetBrains\IntelliJ IDEA Community
Edition
[jira] [Updated] (IGNITE-647) org.apache.ignite.IgniteCacheAffinitySelfTest.testAffinity() hangs
[ https://issues.apache.org/jira/browse/IGNITE-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ershov updated IGNITE-647: --- Attachment: log.txt dump3456.txt dump2.txt dump1.txt Actual log of failed test 2016. > org.apache.ignite.IgniteCacheAffinitySelfTest.testAffinity() hangs > -- > > Key: IGNITE-647 > URL: https://issues.apache.org/jira/browse/IGNITE-647 > Project: Ignite > Issue Type: Sub-task >Reporter: Yakov Zhdanov >Assignee: Semen Boikov >Priority: Blocker > Labels: Muted_test > Fix For: 1.6 > > Attachments: FairAffinityDynamicCacheSelfTest.testStartStopCache.txt, > dump1.txt, dump2.txt, dump3456.txt, log.txt, threaddump.txt > > > 1-2 runs out of ~10 local runs hanged for me -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-172) GridTcpCommunicationSpiRecoveryAckSelfTest and IgniteTcpCommunicationRecoveryAckClosureSelfTest
[ https://issues.apache.org/jira/browse/IGNITE-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ershov updated IGNITE-172: --- Summary: GridTcpCommunicationSpiRecoveryAckSelfTest and IgniteTcpCommunicationRecoveryAckClosureSelfTest (was: GridTcpCommunicationSpiRecoveryAckSelfTest) > GridTcpCommunicationSpiRecoveryAckSelfTest and > IgniteTcpCommunicationRecoveryAckClosureSelfTest > --- > > Key: IGNITE-172 > URL: https://issues.apache.org/jira/browse/IGNITE-172 > Project: Ignite > Issue Type: Bug > Components: general >Reporter: Irina Vasilinets > > GridTcpCommunicationSpiRecoveryAckSelfTest.testQueueOverflow and > GridTcpCommunicationSpiTcpNoDelayOffSelfTest.testSendToManyNodes > fail sometimes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-172) GridTcpCommunicationSpiRecoveryAckSelfTest and IgniteTcpCommunicationRecoveryAckClosureSelfTest
[ https://issues.apache.org/jira/browse/IGNITE-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ershov updated IGNITE-172: --- Description: GridTcpCommunicationSpiRecoveryAckSelfTest.testQueueOverflow and GridTcpCommunicationSpiTcpNoDelayOffSelfTest.testSendToManyNodes fail sometimes. IgniteTcpCommunicationRecoveryAckClosureSelfTest.testQueueOverflow - 1 from 10 was: GridTcpCommunicationSpiRecoveryAckSelfTest.testQueueOverflow and GridTcpCommunicationSpiTcpNoDelayOffSelfTest.testSendToManyNodes fail sometimes. > GridTcpCommunicationSpiRecoveryAckSelfTest and > IgniteTcpCommunicationRecoveryAckClosureSelfTest > --- > > Key: IGNITE-172 > URL: https://issues.apache.org/jira/browse/IGNITE-172 > Project: Ignite > Issue Type: Bug > Components: general >Reporter: Irina Vasilinets > > GridTcpCommunicationSpiRecoveryAckSelfTest.testQueueOverflow and > GridTcpCommunicationSpiTcpNoDelayOffSelfTest.testSendToManyNodes > fail sometimes. > IgniteTcpCommunicationRecoveryAckClosureSelfTest.testQueueOverflow - 1 from 10 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-2368) Performance optimization for an IgnitCache.query execution.
[ https://issues.apache.org/jira/browse/IGNITE-2368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ershov reassigned IGNITE-2368: --- Assignee: Yakov Zhdanov > Performance optimization for an IgnitCache.query execution. > --- > > Key: IGNITE-2368 > URL: https://issues.apache.org/jira/browse/IGNITE-2368 > Project: Ignite > Issue Type: Improvement > Components: SQL >Affects Versions: ignite-1.4 >Reporter: Vladimir Ershov >Assignee: Yakov Zhdanov > Labels: optimization > Original Estimate: 24h > Remaining Estimate: 24h > > Current solution of an sql query executed from client node for replicated > cache could be improved. > As for now we split initial query into map and reduce steps on a client > node, but it would be more effective just to send initial query to a data > node and execute it there without splitting since cache is replicated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2367) Preparation for the SQL DML design. Investiation of the current SQL processing.
Vladimir Ershov created IGNITE-2367: --- Summary: Preparation for the SQL DML design. Investiation of the current SQL processing. Key: IGNITE-2367 URL: https://issues.apache.org/jira/browse/IGNITE-2367 Project: Ignite Issue Type: Task Components: SQL Reporter: Vladimir Ershov Assignee: Vladimir Ershov In order to design an effective and precise solution for the support of an SQL DML clauses we have to: # Make an overview of an existing sql-supporting code. # Put a brief description of the current solution in the design page at wiki. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2367) Preparation for the SQL DML design. Investiation of the current SQL processing.
[ https://issues.apache.org/jira/browse/IGNITE-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ershov updated IGNITE-2367: Remaining Estimate: 8h (was: 24h) Original Estimate: 8h (was: 24h) > Preparation for the SQL DML design. Investiation of the current SQL > processing. > --- > > Key: IGNITE-2367 > URL: https://issues.apache.org/jira/browse/IGNITE-2367 > Project: Ignite > Issue Type: Task > Components: SQL >Reporter: Vladimir Ershov >Assignee: Vladimir Ershov > Labels: sql > Original Estimate: 8h > Remaining Estimate: 8h > > In order to design an effective and precise solution for the support of an > SQL DML clauses we have to: > # Make an overview of an existing sql-supporting code. > # Put a brief description of the current solution in the design page at wiki. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
