[jira] [Created] (IGNITE-12086) Ignite pod keeps crashing and failed to recover the node

2019-08-20 Thread radhakrupa (Jira)
radhakrupa created IGNITE-12086: --- Summary: Ignite pod keeps crashing and failed to recover the node Key: IGNITE-12086 URL: https://issues.apache.org/jira/browse/IGNITE-12086 Project: Ignite Is

Re: Asynchronous registration of binary metadata

2019-08-20 Thread Denis Mekhanikov
Sergey, Currently metadata is written to disk sequentially on every node. Only one node at a time is able to write metadata to its storage. Slowness accumulates when you add more nodes. A delay required to write one piece of metadata may be not that big, but if you multiply it by say 200, then

Re: Asynchronous registration of binary metadata

2019-08-20 Thread Eduard Shangareev
Denis, How would we deal with races between registration and metadata usages with such fast-fix? I believe, that we need to move it to distributed metastorage, and await registration completeness if we can't find it (wait for work in progress). Discovery shouldn't wait for anything here. On Tue,

Re: Asynchronous registration of binary metadata

2019-08-20 Thread Denis Mekhanikov
Eduard, Usages will wait for the metadata to be registered and written to disk. No races should occur with such flow. Or do you have some specific case on your mind? I agree, that using a distributed meta storage would be nice here. But this way we will kind of move to the previous scheme with

Re: Apache Ignite 2.7.6 (Time, Scope, and Release manager)

2019-08-20 Thread Artem Budnikov
Hi Dmitry, The release notes reviewed. Please see my comment in the pull request. -Artem On 19.08.2019 14:20, Dmitriy Pavlov wrote: Hi Andrey, could you please take a look at https://issues.apache.org/jira/browse/IGNITE-12061 ? Are you comfortable with merging it to release (in rush mode)?

[jira] [Created] (IGNITE-12087) Transactional putAll - significant performance drop on big batches of entries.

2019-08-20 Thread Pavel Pereslegin (Jira)
Pavel Pereslegin created IGNITE-12087: - Summary: Transactional putAll - significant performance drop on big batches of entries. Key: IGNITE-12087 URL: https://issues.apache.org/jira/browse/IGNITE-12087

[jira] [Created] (IGNITE-12088) Cache or template name should be validated before attempt to start

2019-08-20 Thread Pavel Kovalenko (Jira)
Pavel Kovalenko created IGNITE-12088: Summary: Cache or template name should be validated before attempt to start Key: IGNITE-12088 URL: https://issues.apache.org/jira/browse/IGNITE-12088 Project:

Ignite pod keeps crashing and failed to recover the node

2019-08-20 Thread radha jai
Ignite has been deployed on the kubernets , there are 3 replicas of server pod. The pods were up and running fine for 9 days. We have created 180 inventory tables and 204 transactional tables. The data has been inserted using the PyIgnite client using the cache.put() method. This is a very slow o

Re: SQL query timeout: in progress or abandoned

2019-08-20 Thread Павлухин Иван
Hi Saikat, I left a comment in JIRA ticket [1]. Also, I invited Andrey to help with a further review. Andrey, could you please step in and continue the review? Unfortunately, for a couple of weeks I have limited access to my computer and cannot do a review in a timely manner. [1] https://issues.

[jira] [Created] (IGNITE-12089) JVM is halted after this error during rolling restart of a cluster

2019-08-20 Thread temp2 (Jira)
temp2 created IGNITE-12089: -- Summary: JVM is halted after this error during rolling restart of a cluster Key: IGNITE-12089 URL: https://issues.apache.org/jira/browse/IGNITE-12089 Project: Ignite Is