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
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
Hi Sergey,
Thanks for doing this.
It looks like PR #5 is already under review, so I guess it will be merged
soon. I would really love to see that, because the configuration framework
is one of the foundational components - we need it to continue building
Ignite 3.0.
As for PR #6, it looks a
Hi Kirill,
I've played with the tool a little bit and it looks great! I definitely
like the overall approach of a single script responsible for all the
operations. This should significantly improve the usability of the product.
Looks like there is a significant amount of functionality already
Nikita, thanks for fixing the issue:
https://github.com/apache/ignite/pull/8570
I've merged the changes and republished the docs on the website. Thanks for
contributing to our documentation!
-
Denis
On Wed, Dec 9, 2020 at 1:22 AM Sumit Deshinge
wrote:
> Great, thanks Denis.
>
> On Tue, Dec
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
*New Critical Failure in master-nightly MVCC Cache 9
https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_MvccCache9?branch=%3Cdefault%3E
No changes in the build
Ilya,
I think common sense is our only friend here :) The low number of
dependencies is indeed one of the advantages of Ignite. On the other hand,
the "zero dependency" approach we've been trying to follow for the last
several years sometimes forces us to implement, stabilize and maintain a
whole
Amelchev Nikita created IGNITE-13845:
Summary: Add checkpoint lock hold metrics
Key: IGNITE-13845
URL: https://issues.apache.org/jira/browse/IGNITE-13845
Project: Ignite
Issue Type: New
Hello Igniters,
I would like to present two pull requests [1], [2] with basic
implementation of IEP-55 for Unified Configuration [3] and IEP-63 REST API
for Unified Configuration [4].
The main goal of these PRs is to present and discuss a new approach for
preparing and managing Ignite
Hi, everyone.
I want to propose for discussion the PoC cli tool, which was born to check
and demonstrate approaches explained in [0] and [1].
This tool will be the all-in-one cli tool for ignite cluster management and
ignite installation/update.
One unified tool will:
- lower the entry threshold
Stanilovsky Evgeny created IGNITE-13844:
---
Summary: Calcite improvements. Append additional dependencies.
Key: IGNITE-13844
URL: https://issues.apache.org/jira/browse/IGNITE-13844
Project: Ignite
sergey-chugunov-1985 opened a new pull request #6:
URL: https://github.com/apache/ignite-3/pull/6
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
Hello, Kirill!
Personally, I see no problem with this improvement. Please check my
comment in IGNITE-13831 [1] on the implementation of this change.
[1] https://issues.apache.org/jira/browse/IGNITE-13831
пт, 11 дек. 2020 г. в 13:23, ткаленко кирилл :
>
> Hello to all!
>
> When implementing
Anton Kalashnikov created IGNITE-13843:
--
Summary: Wrapper/Converter for primitive configuration
Key: IGNITE-13843
URL: https://issues.apache.org/jira/browse/IGNITE-13843
Project: Ignite
Anton Kalashnikov created IGNITE-13842:
--
Summary: Creating the new configuration on old cluster
Key: IGNITE-13842
URL: https://issues.apache.org/jira/browse/IGNITE-13842
Project: Ignite
Anton Kalashnikov created IGNITE-13841:
--
Summary: Cluster bootstrapping
Key: IGNITE-13841
URL: https://issues.apache.org/jira/browse/IGNITE-13841
Project: Ignite
Issue Type: Sub-task
Anton Kalashnikov created IGNITE-13840:
--
Summary: Rething API of Init*, change* classes
Key: IGNITE-13840
URL: https://issues.apache.org/jira/browse/IGNITE-13840
Project: Ignite
Issue
Hello!
I think it is a strong side of Apache Ignite that it has a low number of
JARs and minimal dependencies. It may be less relevant now than 10 years
ago, but it's still a plus.
Not sure how fast it would evaporate as the number of JARs and dependencies
grows.
Regards,
--
Ilya Kasnacheev
Hello! I also have an issue in progress regarding WAL archive:
https://issues.apache.org/jira/browse/IGNITE-12892. In this ticket I tried
clarifying WAL archive size configuration, removing usage of the deprecated
walHistSize property. Also, IGNITE_PDS_MAX_CHECKPOINT_MEMORY_HISTORY_SIZE is
now
That will require time and some research.
A will try to do it today, in urgent case — can introduce half-hack for now and
improve later.
> On 11 Dec 2020, at 13:17, Maxim Muzafarov wrote:
>
> Petr,
>
> Will you fix the issue [1] soon or we can proceed with the 2.9.1
> release manually?
>
>
Hello to all!
When implementing IGNITE-13831 I was faced with deadlock.
When execute FileWriteAheadLogManager#rollOver, begin to clean WAL archive
since we have reached the DataStorageConfiguration#maxWalArchiveSize, after
deleting a segment, execute the
Petr,
Will you fix the issue [1] soon or we can proceed with the 2.9.1
release manually?
[1] https://issues.apache.org/jira/browse/IGNITE-13839
On Thu, 10 Dec 2020 at 20:59, Yaroslav Molochkov wrote:
>
> Thanks, Petr!
>
> I've created a ticket
22 matches
Mail list logo
