[jira] [Created] (IGNITE-11855) Need to reduce log message in case: Topology projection is empty. Cluster group is empty.

[Denis Chudov (JIRA)]

Denis Chudov created IGNITE-11855:
-

 Summary: Need to reduce log message in case: Topology projection 
is empty. Cluster group is empty.
 Key: IGNITE-11855
 URL: https://issues.apache.org/jira/browse/IGNITE-11855
 Project: Ignite
  Issue Type: Bug
Reporter: Denis Chudov
Assignee: Denis Chudov


In some cases - there is a lot of stack trace in logs


{code:java}
[18:53:00,811][SEVERE][grid-timeout-worker-#39][diagnostic] Could not get 
thread dump from transaction owner near node:
class org.apache.ignite.cluster.ClusterGroupEmptyException: Cluster group is 
empty.
 at org.apache.ignite.internal.util.IgniteUtils$6.apply(IgniteUtils.java:853)
 at org.apache.ignite.internal.util.IgniteUtils$6.apply(IgniteUtils.java:851)
 at 
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:991)
 at 
org.apache.ignite.internal.util.future.IgniteFutureImpl.convertException(IgniteFutureImpl.java:168)
 at 
org.apache.ignite.internal.util.future.IgniteFutureImpl.get(IgniteFutureImpl.java:137)
 at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$8.apply(GridCachePartitionExchangeManager.java:2112)
 at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$8.apply(GridCachePartitionExchangeManager.java:2107)
 at 
org.apache.ignite.internal.util.future.IgniteFutureImpl$InternalFutureListener.apply(IgniteFutureImpl.java:215)
 at 
org.apache.ignite.internal.util.future.IgniteFutureImpl$InternalFutureListener.apply(IgniteFutureImpl.java:179)
 at 
org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:385)
 at 
org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:355)
 at 
org.apache.ignite.internal.util.future.IgniteFutureImpl.listen(IgniteFutureImpl.java:71)
 at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.dumpLongRunningTransaction(GridCachePartitionExchangeManager.java:2107)
 at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.dumpLongRunningOperations0(GridCachePartitionExchangeManager.java:2009)
 at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.dumpLongRunningOperations(GridCachePartitionExchangeManager.java:2163)
 at org.apache.ignite.internal.IgniteKernal$4.run(IgniteKernal.java:1344)
 at 
org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor$CancelableTask.onTimeout(GridTimeoutProcessor.java:365)
 at 
org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor$TimeoutWorker.body(GridTimeoutProcessor.java:234)
 at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
 at java.lang.Thread.run(Thread.java:748)
Caused by: class 
org.apache.ignite.internal.cluster.ClusterGroupEmptyCheckedException: Cluster 
group is empty.
 at 
org.apache.ignite.internal.util.IgniteUtils.emptyTopologyException(IgniteUtils.java:4811)
 at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor.callAsync(GridClosureProcessor.java:670)
 at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor.callAsync(GridClosureProcessor.java:479)
 at 
org.apache.ignite.internal.IgniteComputeImpl.callAsync0(IgniteComputeImpl.java:809)
 at 
org.apache.ignite.internal.IgniteComputeImpl.callAsync(IgniteComputeImpl.java:794)
 at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.dumpLongRunningTransaction(GridCachePartitionExchangeManager.java:2106)
 ... 7 more
{code}


{code:java}
[18:53:00,809][SEVERE][grid-timeout-worker-#39][diagnostic] Could not get 
thread dump from transaction owner near node:
class org.apache.ignite.cluster.ClusterGroupEmptyException: Topology projection 
is empty.
 at org.apache.ignite.internal.util.IgniteUtils$6.apply(IgniteUtils.java:853)
 at org.apache.ignite.internal.util.IgniteUtils$6.apply(IgniteUtils.java:851)
 at 
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:991)
 at 
org.apache.ignite.internal.util.future.IgniteFutureImpl.convertException(IgniteFutureImpl.java:168)
 at 
org.apache.ignite.internal.util.future.IgniteFutureImpl.get(IgniteFutureImpl.java:137)
 at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$8.apply(GridCachePartitionExchangeManager.java:2112)
 at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$8.apply(GridCachePartitionExchangeManager.java:2107)
 at 
org.apache.ignite.internal.util.future.IgniteFutureImpl$InternalFutureListener.apply(IgniteFutureImpl.java:215)
 at 
org.apache.ignite.internal.util.future.IgniteFutureImpl$InternalFutureListener.apply(IgniteFutureImpl.java:179)
 at 
org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:385)
 at 

[jira] [Created] (IGNITE-11854) Serialization of arrays of primitives in python thin client is not optimal

[Denis Mekhanikov (JIRA)]

Denis Mekhanikov created IGNITE-11854:
-

 Summary: Serialization of arrays of primitives in python thin 
client is not optimal
 Key: IGNITE-11854
 URL: https://issues.apache.org/jira/browse/IGNITE-11854
 Project: Ignite
  Issue Type: Bug
  Components: thin client
Affects Versions: 2.7
Reporter: Denis Mekhanikov


The following code hangs indefinitely inside of invocation to {{my_cache.put()}}
{code:java}
from pyignite import Client

arr_len = 3_000_000

content = bytearray(arr_len)

for i in range(arr_len):
content[i] = i % 256

client = Client()
client.connect('127.0.0.1', 10800)
my_cache = client.get_or_create_cache('my cache')
my_cache.put("key_bin", content){code}
While the value is only 3MB in size. Implementation of serialization of 
primitive arrays seems to be quadratic in length of the array.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-11853) [TC Bot] Add special mode/flag for threating failures of licenses/javadoc and some other stable suites

[Dmitriy Pavlov (JIRA)]

Dmitriy Pavlov created IGNITE-11853:
---

 Summary: [TC Bot] Add special mode/flag for threating failures of 
licenses/javadoc and some other stable suites
 Key: IGNITE-11853
 URL: https://issues.apache.org/jira/browse/IGNITE-11853
 Project: Ignite
  Issue Type: Improvement
Reporter: Dmitriy Pavlov
Assignee: Dmitriy Pavlov


As the simplest solution, we could add suite IDs into branches.json



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)