Denis, ok, I'll publish on Monday afternoon then (UTC), weekend is not the
best time.
Thanks,
Pavel
On Sat, Mar 7, 2020 at 1:25 AM Denis Magda wrote:
> Pavel,
>
> Thanks for clarifying the way partition-awareness handles topology changes.
>
> Please publish your article as soon as you're
Pavel,
Thanks for clarifying the way partition-awareness handles topology changes.
Please publish your article as soon as you're ready. I plan to finish mine
on Monday-Tuesday and will refer to yours.
-
Denis
On Fri, Mar 6, 2020 at 1:36 AM Pavel Tupitsyn wrote:
> Denis, thanks for the
Alex, thanks for monitoring various discussion threads and sharing these
problems with the rest of the dev community.
>> As a short-term solution for [2] I suggest to force reads from a primary
> node inside optimistic serializable transactions.
Totally agree on this. Anyway, consistency and
Dmitry,
Agree on the Github repository. Let me look into it. If you have any
pointers or came across any instructions earlier please let me know.
-
Denis
On Fri, Mar 6, 2020 at 8:03 AM Dmitriy Pavlov wrote:
> Hi Igniters,
>
> IMO, new design looks good, but please pay attention
> - every
Ilya,
`ignite-compress` is necessary for `wal page snapshot compression` [1]
which in turn shows very good performance results. So, I suppose, it's
better to include it to the "slim" binary.
[1] https://issues.apache.org/jira/browse/IGNITE-11336
On Fri, 6 Mar 2020 at 13:31, Ilya Kasnacheev
Hi Igniters,
I feel it worth sharing with all of you. I don't think there is something
private in this notice. JFYI
Sincerely,
Dmitriy Pavlov
-- Forwarded message -
От: Daniel Gruno
Date: ср, 4 мар. 2020 г. в 18:04
Subject: [NOTICE] Structural changes to Apache downloads
To:
Hi Igniters,
IMO, new design looks good, but please pay attention
- every mention of Apache Ignite is better to be followed by (R) mark since
it is registered trademark of the ASF in the US and other countries.
- download page is not available (as Denis mentioned it should not be an
issue).
And
Nikolai Kulagin created IGNITE-12757:
Summary: ignitevisorcmd does not connect to the cluster
Key: IGNITE-12757
URL: https://issues.apache.org/jira/browse/IGNITE-12757
Project: Ignite
Andrey N. Gura created IGNITE-12756:
---
Summary: TcpCommunicationSpi metrics implementation improvements
Key: IGNITE-12756
URL: https://issues.apache.org/jira/browse/IGNITE-12756
Project: Ignite
Anton,
Thanks for the feedback. I updated the page.
-Artem
On 05.03.2020 16:32, Anton Vinogradov wrote:
Artem, great!
Some minors:
read operations become more costly for caches with backup copies.
Since it makes sense only for cache with backups, can we say something like
"read operations
Hello!
I added these because they are infrastructural to Ignite, as opposed to
integrations. They are also both very slim.
Regards,
--
Ilya Kasnacheev
пт, 6 мар. 2020 г. в 13:25, Stephen Darlington <
stephen.darling...@gridgain.com>:
> Why ignite-jta and ignite-urideploy? Anecdotally at
Why ignite-jta and ignite-urideploy? Anecdotally at least, I know very few
people who use either.
> On 6 Mar 2020, at 11:09, Ilya Kasnacheev wrote:
>
> Hello!
>
> Re-posting from *[DISCUSSION] Release Apache Ignite 2.8.0 RC1*
>
> I have prepared assemblies for Apache Ignite slim packaging:
Hello!
Re-posting from *[DISCUSSION] Release Apache Ignite 2.8.0 RC1*
I have prepared assemblies for Apache Ignite slim packaging:
https://github.com/apache/ignite/tree/ignite-slim
It is based on ignite-2.8
You can build it with mvn initialize -Prelease,lgpl -Dignite.edition=apache-
Denis, thanks for the feedback!
When should I publish the post? Right after official release announcement,
or later?
> I would use "thick client" as a term instead of the "classic client"
Good point, fixed
> partition-awareness doesn't handle topology changes automatically
(partition map won't
Anton,
> >> In short, the root cause of this issue is that there are configurations
> >> that allow a key to be stored on primary and backup nodes with different
> >> versions.
> Faced with the same problem during ReadRepair development.
>
> >> I suggest to force reads from a primary
> >> node
Alexey,
>> In short, the root cause of this issue is that there are configurations
>> that allow a key to be stored on primary and backup nodes with different
>> versions.
Faced with the same problem during ReadRepair development.
>> I suggest to force reads from a primary
>> node inside
16 matches
Mail list logo
