Dmitriy, as far as I understand, Denis have adviced user to "disable"
archiving by setting wal and wal archive path to the same value. I tried to
explain that this measure doesn't prevent from storing wal segments needed
for recovery but bring additional performance penalty.
> In older versions
Maxim,
2.x and 3.x will have to coexist for some time - I don't see how we can
avoid this considering the set of proposed changes. That said, we
effectively will need to have two "masters" - one for each major version.
Master for 3.x can technically be a branch in the existing repo, but having
a
In older versions of Apache Ignite, WAL archive could contain valid records
needed for recovery. If something was changed since then, my comment may be
not valid.
We've discussed that before, that naming this directory as 'archive' was
not the best possible option. The archive is often considered
ok, I see, I supposed this list is somehow automatically being built or
related to announcements.
ср, 11 нояб. 2020 г. в 01:48, Denis Magda :
> You also need to add a release to the reporter manually just for tracking
> purposes. I used to do this once a quarter when the board was requesting a
>
You also need to add a release to the reporter manually just for tracking
purposes. I used to do this once a quarter when the board was requesting a
report and I would add all the missing releases into that system while
preparing the report.
-
Denis
On Tue, Nov 10, 2020 at 1:27 PM Dmitriy
Looks good to me. Thanks for sharing the draft.
-
Denis
On Tue, Nov 10, 2020 at 1:55 PM Dmitriy Pavlov wrote:
> Hi Igniters,
>
> The report for the Board meeting on Nov 18 is due today.
>
> I've appended the current version of the report at the end of the email.
> The same report has been
Isn't the discussion here related to the WAL archive? If you disable that
don't you still have the WAL containing un-checkpointed changes?
On Wed, Nov 11, 2020 at 11:01 AM Dmitriy Pavlov wrote:
> Hi Denis,
>
> the short answer here, Apache Ignite guarantees ACID, and for D-Durability
> it is
Hi Denis,
the short answer here, Apache Ignite guarantees ACID, and for D-Durability
it is required to save all changes in some WAL/Redo Log to have a safe way
to recover from any hardware failures/disk outage.
Should the user disable WAL, he/she could potentially lose durability.
Sincerely,
Ok, thanks for sharing the link.
ср, 11 нояб. 2020 г. в 00:35, Alex Plehanov :
> Dmitriy,
>
> Yes, the release was announced at announce@. See [1].
>
> [1] :
>
> https://lists.apache.org/thread.html/r2e3dbf7a055fdbc57f47c1180afea59dd8a335c8dde7a5e53885e861%40%3Cannounce.apache.org%3E
>
>
> ср,
Hi Igniters,
The report for the Board meeting on Nov 18 is due today.
I've appended the current version of the report at the end of the email.
The same report has been filed to the agenda.
If you feel that we can add some crucial points to the report, please let
me know. I guess I still can do
Dmitriy,
Yes, the release was announced at announce@. See [1].
[1] :
https://lists.apache.org/thread.html/r2e3dbf7a055fdbc57f47c1180afea59dd8a335c8dde7a5e53885e861%40%3Cannounce.apache.org%3E
ср, 11 нояб. 2020 г. в 00:27, Dmitriy Pavlov :
> Hi Alex,
>
> Thank you for driving this release and
Hi Alex,
Thank you for driving this release and this post.
Was the release announced at announce@ ?
Denis, Ignite veterans,
The reason I'm asking: this release was not available at
https://reporter.apache.org/addrelease.html?ignite ? I've added it now. Is
it always required to add it there
Sergey,
Your summary makes sense to me.
However, how we come up from *Development transparency* to *create a
separate public repository dedicated for 3.0*? For me *development
transparency* is about making changes in the master branch. These
changes will definitely be seen by all the Ignite
Makes sense to me.
вт, 10 нояб. 2020 г. в 18:47, Sergey Chugunov :
> Igniters,
>
> I thought over Friday meeting ideas and concerns and summarized them in
> these three points:
>
>
>1. *Components design unification approach.* New proposed components
>will be developed by different
Pavel Tupitsyn created IGNITE-13692:
---
Summary: .NET: Default query timeout
Key: IGNITE-13692
URL: https://issues.apache.org/jira/browse/IGNITE-13692
Project: Ignite
Issue Type: Improvement
Igniters,
I thought over Friday meeting ideas and concerns and summarized them in
these three points:
1. *Components design unification approach.* New proposed components
will be developed by different contributors, but they need to be unified
and should integrate with each other
Yury Gerzhedovich created IGNITE-13691:
--
Summary: Calcite Integration. Support of EXCEPT operator
Key: IGNITE-13691
URL: https://issues.apache.org/jira/browse/IGNITE-13691
Project: Ignite
Folks,
I've created the release page on the Confluence. Feel free to mail in
case of any errors.
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.10
On Fri, 6 Nov 2020 at 17:56, Maxim Muzafarov wrote:
>
> Igniters,
>
>
> Let's finalize the discussion [1] about the next
Igniters,
It seems that we came to decision on change of Ignite dependency scopes
to "provided". Don't we?
The corresponding ticket [1] is ready to final review. Saikat Maitra
have already reviewed and approved PR [2].
Could some committer take a final look?
[1] -
Ivan Daschinskiy created IGNITE-13690:
-
Summary: Failed to init coordinator caches on concurrent start of
nodes with different cache configurations.
Key: IGNITE-13690
URL:
20 matches
Mail list logo
