Congrats, Maxim. Well deserved!
-
Denis
On Thu, May 7, 2020 at 4:47 AM Dmitriy Pavlov wrote:
> The Project Management Committee (PMC) for Apache Ignite
>
> has invited Maxim Muzafarov to become new PMC member and we are pleased to
> announce that he has accepted.
>
>
>
> Maxim is active dev
Maxim,
Congratulations!!!
Regards
Saikat
On Thu, 7 May 2020 at 3:20 PM, Дмитрий Сорокин
wrote:
> Maxim, congrats!
> Great job, respect!
>
> чт, 7 мая 2020 г. в 23:04, Vyacheslav Daradur :
>
> > Great job! My congratulations!
> >
> > чт, 7 мая 2020 г. в 16:09, Alex Plehanov :
> >
> > > Maxim,
Hello Mikhail,
Most likely that didn't get in the scope when those commands were being
added to Ignite. @Taras Ledkov , @Ivan Pavlukhin
, @Yuriy Gerzhedovich ,
could you please share your thoughts on this?
-
Denis
On Fri, May 8, 2020 at 2:19 AM Mikhail Petrov wrote:
> Hello, Igniters.
>
> At
Dmitry, thanks for the details.
Then I agree with the proposal of moving the tool to a separate repo and
officially discontinuing its support. The question is should we keep it in
the ASF repo or move to an independent GitHub repo and forget about it?
-
Denis
On Thu, May 7, 2020 at 4:53 AM
Hi Anton,
Generally, it means that Ignite will keep executing operations/transactions
that are mapped into the partitions of those cells that won't be
rebalanced, is that correct?
-
Denis
On Wed, May 6, 2020 at 3:24 AM Anton Vinogradov wrote:
> Igniters,
>
> PME-free switch [1] (since 2.8)
Maxim, Folks,
Speaking of Ignite 2.9 release time, I would encourage us to wait for all
those contributors who plan to finish their tasks in June-July. The roadmap
page shows that we should get ~8 more significant improvements added by
August. Combining those features with what's already in the
Can you, please, send us
1. Detailed error message(stack trace, etc)
2. Ignite configuration.
Any other details that can be usefull.
> 8 мая 2020 г., в 22:08, C Ravikiran написал(а):
>
> Last 2 years there is no code changes.
> Our application is running in only one node.
>
> Our daily data
Last 2 years there is no code changes.
Our application is running in only one node.
Our daily data is around 10GB, as our scheduler is removing old data.
Our application users also less.
Why we got suddenly, these memory leakage problem, when there is no
application code change.
Problem we are
You need to get to the bottom of why JVM fails with the OOM on your cluster
nodes. An ignite node is no more than a Java application and you can start
investigating the issue using standard methods. For now, I can only share
some useful pointers:
-
I am new to ignite, if you need any details please let me know, I will
check and provide those details.
I need proper justification, if I need to upgrade to new version.
Suddenly we are getting OOM error, after 2 years.
Every day we are removing all old cache ids and adding new cache ids
Our
You just stated that experienced OOM issues with no details for suggestions
or help with troubleshooting. Take heap dumps, analyze GC logs, etc:
https://apacheignite.readme.io/docs/jvm-and-system-tuning#debugging-memory-usage-issues-and-gc-pauses
-
Denis
On Fri, May 8, 2020 at 11:31 AM C
Is this problem will be solved, if I upgraded to 2.8 version.
On Fri 8 May, 2020, 10:02 PM Ilya Kasnacheev,
wrote:
> Hello!
>
> I don't think you will find much expertise on Ignite 1.x here. I recommend
> upgrading it to 2.8 eventually.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> пт, 8 мая 2020
Hello!
I don't think you will find much expertise on Ignite 1.x here. I recommend
upgrading it to 2.8 eventually.
Regards,
--
Ilya Kasnacheev
пт, 8 мая 2020 г. в 09:57, C Ravikiran :
> Hi Team,
>
> Our application is running past 2 year onwards, there was no problem with
> ignite.
> Suddenly
Hello Nikita,
Welcome to Apache Ignite Community!
I added your account to the contributors list. Now you can assign
tickets to yourself. Do not hesitate to ask if you need any
assistance.
Please check this page out for commonly asked questions pertaining to
the contribution process
Denis Garus created IGNITE-12996:
Summary: Remote listener of IgniteEvents has to run inside the
Ignite Sandbox.
Key: IGNITE-12996
URL: https://issues.apache.org/jira/browse/IGNITE-12996
Project:
Stepachev Maksim created IGNITE-12995:
-
Summary: Transactions hang up if node fails
Key: IGNITE-12995
URL: https://issues.apache.org/jira/browse/IGNITE-12995
Project: Ignite
Issue Type:
Igniters,
ticket created [1], please take a look at the proposed changes [2].
[1] https://issues.apache.org/jira/browse/IGNITE-12993
[2] https://github.com/apache/ignite/pull/7784/files
пт, 8 мая 2020 г. в 12:02, Maxim Muzafarov :
>
> Pavel,
>
>
> I have no objections. Let's file a ticket.
>
>
Semyon Danilov created IGNITE-12994:
---
Summary: Move binary metadata to PDS storage folder
Key: IGNITE-12994
URL: https://issues.apache.org/jira/browse/IGNITE-12994
Project: Ignite
Issue
Hello Ignite Community!
I would like to start contributing, could you please add me to contributors
list? My login for https://issues.apache.org/ is Nikita T.
Thanks!
Pavel Pereslegin created IGNITE-12993:
-
Summary: Github notification integrations on new ASF infra feature
Key: IGNITE-12993
URL: https://issues.apache.org/jira/browse/IGNITE-12993
Project: Ignite
Maxim,
I am super excited that we start discussing Ignite 3.0, but I think that
leaving only half a year for all the 3.0 changes is overly optimistic.
Moving to a major release allows us to significantly change APIs and
default behavior, storage formats, etc. Honestly, I think just discussions
I suggest to release more often, but I disagree with dates for 2.9. I've
planned to add a few features to 2.9 for ML module (model export/import)
and so on.
If it will be possible to merge in 2.9 branch in June for separate modules,
it's ok for me.
пт, 8 мая 2020 г. в 13:06, Nikolay Izhikov :
>
+1 to release 2.9 right after 2.8.1
> 8 мая 2020 г., в 12:53, Maxim Muzafarov написал(а):
>
> Folks, Denis,
>
>
> I think no one will argue against that frequent releases is good. The
> last major 2.8 release scope was frozen the last December, so having
> the next 2.9 release in September
Folks, Denis,
I think no one will argue against that frequent releases is good. The
last major 2.8 release scope was frozen the last December, so having
the next 2.9 release in September sounds not so good in general. We
already have a lot of major features to release, for instance:
- Sandbox
Hello, Igniters.
At the moment execution of the following SQL queries via JDBC requires
no security permissions:
ALTER TABLE ADD
ALTER TABLE DROP COLUMN
CREATE INDEX
DROP INDEX
Could someone clarify does this behavior considered desired or it is
needed to be fixed?
Tests that shows
Pavel,
I have no objections. Let's file a ticket.
On Fri, 8 May 2020 at 08:04, Ivan Pavlukhin wrote:
>
> Pavel,
>
> Thank you for starting this discussion!
>
> Controlling all this repo options on our side sounds very attractive.
>
> Personally I do not have any arguments about the proposal.
>
Ivan Daschinskiy created IGNITE-12992:
-
Summary: Fix multijvm failing tests in
ZookeeperDiscoverySpiTestSuite3
Key: IGNITE-12992
URL: https://issues.apache.org/jira/browse/IGNITE-12992
Project:
Hi Team,
Our application is running past 2 year onwards, there was no problem with
ignite.
Suddenly last 2 week onwards, we are getting out of memory error in ignite.
There was no code changes in last 2 years.
If we restart the ignite, our memory gradually increasing and we are
getting out of
29 matches
Mail list logo
