Hi Igniters, Mauricio, Ignacio, and Denis,
Thank you all for updating these pages.
I would like to stress just one thing:
should you have in mind some topic you can run talk about, please feel
absolutely free to fill submission proposal.
To submit proposal you need to fill in this form
https://d
Hello Ignite Community,
The Project Management Committee (PMC) for Apache Ignite has invited Saikat
Maitra to join the PMC as a new member and we are pleased to announce that
he has accepted.
Saikat joined the community a long time ago and earned the role of a
committer by integrating Ignite
Saikat,
Congratulations and many thanks for your efforts!
чт, 9 янв. 2020 г. в 13:20, Dmitriy Pavlov :
>
> Hello Ignite Community,
>
>
>
> The Project Management Committee (PMC) for Apache Ignite has invited Saikat
> Maitra to join the PMC as a new member and we are pleased to announce that
> he
Hello Anton,
Thanks for digging into this. The logic with checking the
reservations count seems fishy to me as well, so I have no objections with
the suggested change. This "if" statement does not answer why the partition
was being destroyed during the commit, though. Does the issue reproduce in
s
Hi, I've found a bug in pom. It will be fixed on next week in master and
release branches.
Thank for the message!
ср, 18 дек. 2019 г. в 22:11, Denis Magda :
> Alexey, Nikolay,
>
> Could you please step in and shed some light on what has changed with
> Spark? Probably, that's an issue that needs t
Maxim M. and anyone who is interested,
I suggest to include this fix to 2.8 release:
https://issues.apache.org/jira/browse/IGNITE-12225
Basically, it's a result of the following discussion:
http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-Single-point-in-API-for-changing-cluster-st
+1
чт, 9 янв. 2020 г. в 16:38, Ivan Rakov :
>
> Maxim M. and anyone who is interested,
>
> I suggest to include this fix to 2.8 release:
> https://issues.apache.org/jira/browse/IGNITE-12225
> Basically, it's a result of the following discussion:
> http://apache-ignite-developers.2346864.n4.nabble.
Folks,
Since 2.4, Ignite cluster requires baseline topology in persistent mode.
That means if user wants to scale cluster and add more nodes, data won't be
redistributed among the whole node set until manual call of
IgniteCluster#setBaselineTopology.
Surely this behavior is well-documented, but d
Hello,
I think, log
> message with something like "Current set of nodes differs from baseline
> topology, please call XXX in order to trigger rebalance and redistribute
> your data" will make the situation a bit more transparent.
Yes, this seems reasonable to me when the baseline auto-adjust feat
Vladislav Pyatkov created IGNITE-12522:
--
Summary: Extend test coverage [IGNITE-12104] Check deployment from
cache before to load it from local or version storage
Key: IGNITE-12522
URL: https://issues.apache.o
Hello again!
TC passes, review is ready.
Your last chance to act before merge!
Regards,
--
Ilya Kasnacheev
вт, 31 дек. 2019 г. в 16:01, Ilya Kasnacheev :
> Hello!
>
> I have prepared a patch, please review. It will look like this:
>
> Data Regions Started: 4
> ^-- sysMemPlc region [typ
Andrey N. Gura created IGNITE-12523:
---
Summary: Continuously generated thread dumps in failure processor
slow down the whole system
Key: IGNITE-12523
URL: https://issues.apache.org/jira/browse/IGNITE-12523
Hello!
Can we perhaps add this as a blocker to 2.8?
Perhaps by correlating with
https://issues.apache.org/jira/browse/IGNITE-12504
Regards,
--
Ilya Kasnacheev
чт, 9 янв. 2020 г. в 17:59, Вячеслав Коптилин :
> Hello,
>
> I think, log
> > message with something like "Current set of nodes diffe
+1
I'm preparing patch for 2.8 branch now. TC Bot visa for 2.8 branch will be
at 13 Jan
чт, 9 янв. 2020 г., 21:06 Ivan Pavlukhin :
> +1
>
> чт, 9 янв. 2020 г. в 16:38, Ivan Rakov :
> >
> > Maxim M. and anyone who is interested,
> >
> > I suggest to include this fix to 2.8 release:
> > https://is
+1
чт, 9 янв. 2020 г. в 18:52, Sergey Antonov :
> +1
>
> I'm preparing patch for 2.8 branch now. TC Bot visa for 2.8 branch will be
> at 13 Jan
>
> чт, 9 янв. 2020 г., 21:06 Ivan Pavlukhin :
>
> > +1
> >
> > чт, 9 янв. 2020 г. в 16:38, Ivan Rakov :
> > >
> > > Maxim M. and anyone who is intereste
Folks,
Let me remind you that we are working on the 2.8 release branch
stabilization currently (please, keep it in mind).
Do we have a really STRONG reason for adding such a change [1] to the
ignite-2.8 branch? This PR [2] doesn't look a very simple +5,517
−2,038, 111 files changed.
Do we have
Congrats, Saikat! Well deserved!
-
Denis
On Thu, Jan 9, 2020 at 2:22 AM Ivan Pavlukhin wrote:
> Saikat,
>
> Congratulations and many thanks for your efforts!
>
> чт, 9 янв. 2020 г. в 13:20, Dmitriy Pavlov :
> >
> > Hello Ignite Community,
> >
> >
> >
> > The Project Management Committee (PMC)
Agree, that we could plan 2.8.1 for bug-fixing and 2.9 for new major
changes and maybe it will help Ivan to decide move it to next releases.
Agree that scope is frozen, agree that it makes the release is hard for our
release manager.
чт, 9 янв. 2020 г. в 19:38, Maxim Muzafarov :
> Folks,
>
>
> L
Ignite dev community,
I've closed the questionary and here is raw anonymous data for
your reference:
https://docs.google.com/document/d/1Rkc82GkNlsVrwXxQgFd8RgFNV_qVwuMhmzaQV2W9ccI/edit?usp=sharing
Overall, Ignite is continued to be used heavely for caching
scenarios (services, DBs, APIs) with in
Igniters,
Some of you should have come across an article by Simon Ritter describing
how Ignite and Azul Zing JVM are used together to power low-latency use
cases:
https://www.azul.com/igniting-in-memory-performance-with-gridgain-and-zing/
Several of our community members including Pavel Vinokurov
Ivan, Igniters, thanks for starting the discussion,
How about the following a bit simplified message template? It's assumed the
user is aware of what both rebalancing and baseline topology mean.
"New server node joined the cluster, add it to the baseline topology
manually to trigger data rebalanc
Dmitry,
We've also added the reference to the form on the event's webpage. Btw,
could you remind me who will be receiving the proposals - you, I and some
other folks or all @dev list?
-
Denis
On Thu, Jan 9, 2020 at 1:53 AM Dmitriy Pavlov wrote:
> Hi Igniters, Mauricio, Ignacio, and Denis,
>
>
Hello, Maxim!
> This PR [2] doesn't look a very simple +5,517 −2,038, 111 files
changed.
Yes, PR is huge, but I wrote a lot of new tests and reworked already
presented. Changes in product code are minimal - only 30 changed files in
/src/main/ part. And most of them are new control.sh commands and
Hi Dmitriy, Denis, Ivan,
Thank you so much. I am very glad and excited to be a part of Apache Ignite
Project Member Committee.
I will try my best to assist with project management and guide the
direction of the project.
Regards,
Saikat
On Thu, Jan 9, 2020 at 10:51 AM Denis Magda wrote:
> Cong
Anton Vinogradov created IGNITE-12524:
-
Summary: Partition reserve/release symmetry should be checked on
release/destroy
Key: IGNITE-12524
URL: https://issues.apache.org/jira/browse/IGNITE-12524
P
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
>> Does the issue reproduce in
>> subsequent runs?
Unfortunately no.
We performed 30+ runs without "success".
>> I think we can add an assertion to
>> GridDhtLocalPartition#destroy() method to check that reservations is 0
Ok, I will check and merge in case of success.
Created the Issue to handle t
Hello, Igniters.
I’m -1 to include the read-only patch to 2.8.
I think we shouldn’t accept any patches to 2.8 except bug fixes for blockers
and major issues.
Guys, we don’t release Apache Ignite for 13 months!
We should focus on the release and make it ASAP.
We can’t extend the scope anymore.
Agree with Nikolay, -1 from me, too.
>Hello, Igniters.
>
>I’m -1 to include the read-only patch to 2.8.
>I think we shouldn’t accept any patches to 2.8 except bug fixes for blockers
>and major issues.
>
>Guys, we don’t release Apache Ignite for 13 months!
>We should focus on the release and ma
29 matches
Mail list logo
