Hi,
When you are working with TRANSACTIONAL cache you should be aware that
deadlocks might happen. I see the following options to prevent
deadlocks to happen:
1. Explicitly order all keys involved in any transaction using the
same comparator.
2. Use OPTIMISTIC transactions.
Also, in many database
Alexander Kalinin created IGNITE-11556:
--
Summary: Add color legend into series selection panel
Key: IGNITE-11556
URL: https://issues.apache.org/jira/browse/IGNITE-11556
Project: Ignite
I
Hi Igniters,
I heard that It could lead to DeadLocked when I pass non sorted collection
into putAll method. Is it true ?
>From document i see that method requires a IEnumerable> as input. I think pass a sorted collection into API is just a
workaround way. Should it be handle natively in Ignite Co
Alexey Goncharuk created IGNITE-11555:
-
Summary: Unable to await partitions release latch caused by
coordinator failover
Key: IGNITE-11555
URL: https://issues.apache.org/jira/browse/IGNITE-11555
P
Hi Igniters,
Recently I created 2 PRs with simple changes related our testing framework.
1. Remove several @RunWith(JUnit4.class) lines left after migration to
junit 4 [1].
2. Remove custom assumption handler in order to improve reporting on
TC for tests skipped by failed assumption [2]. See the t
Hi Dmitriy,
It is a pitty that we have to guess here. Some comments:
1. The usage scenario is not very complex and erything might work well
with aforementioned patch. Unfortunately some tradeoff and extra
transformations are involved and consequently it is hard to predict
how many users will be tr
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
If your changes can lead to this failure(s): We're grateful that you were a
volunteer to make the contribution to this project, but things change and you
may no longer be able to finalize
