4687
Best regards,
Sergey Kosarev.
Hi,
Patch is ready - no blockers, please review.
Best regards,
Sergey Kosarev.
чт, 6 мая 2021 г. в 13:57, Sergey :
> Hi, Igniters.
> I've came across JVM crush recently. And after investigations I've found
> Binary(Off)HeapOutputStream does not check correctly for overflo
+1 for option2 (only @Nullable)
Best regards,
Sergey Kosarev.
чт, 13 янв. 2022 г. в 13:25, Alexander Polovtcev :
> Dear Igniters,
>
> In this thread
> <https://lists.apache.org/thread/2l50swqd1dymf2qjgrb4wqrbmwjtj02f> we've
> discussed possible approaches to using nu
Hi,
Here is reproducer for master :
https://github.com/macrergate/ignite/commit/9a7d2d27af30018a5f6faccb39176a35243ccfa2
Best regards,
Sergey Kosarev.
вт, 17 мар. 2020 г. в 12:27, Sergey-A Kosarev :
> Classification: Public
>
> Hi Sergey,
> Ticket is here https://issues.apa
Hi,
I'm proposing to add
https://issues.apache.org/jira/browse/IGNITE-12549 (fix iterators/scan
queries for replicated caches)
to 2.8.1.
Best regards,
Sergey Kosarev.
вс, 5 апр. 2020 г. в 01:22, Saikat Maitra :
> Hi,
>
> I observed that we already have release 2.8.1
Hi!
Why should we choose between interactive and command mode?
I'd suggest that new utility doesn't matter of its name control.sh or visor
should have support of both modes.
Sergey Kosarev
чт, 24 янв. 2019 г., 23:02 Denis Magda dma...@apache.org:
> Sergey,
>
> Let's bre
tMinimum() : exp) + ".";
But now in case of error we have less information.
Hence, I suppose we should add new method ( name can be assert() ) with
old implementation returning AssertionError.
What do you think?
Best regards,
Sergey Kosarev.
пт, 26 окт. 2018 г. в 16:53, Nikita Amelchev
e, do we need to add some system property or introduce
some attribute to IgniteConfiguration to configure Scheduler thread pool
size? And what should be default value?
Best regards,
Sergey Kosarev.
чт, 10 мая 2018 г. в 20:23, Dmitry Pavlov :
> Hi Anton,
>
> Thank you for joining and re
gards,
Sergey Kosarev.
вт, 25 дек. 2018 г. в 18:19, Ilya Kasnacheev :
> Hello!
>
> I have started reviewing your pull request.
> I will expect that scheduled tasks are executed on Public pool. Is it
> possible that tasks are launched on Public pool? If Spring Scheduler
> insists
ished before new
execution:
Look at
org.apache.ignite.internal.processors.schedule.ScheduleFutureImpl#run
In this case a new task won't be executed (it just log warning message)
disregarding Cron4J or Spring is used.
Best regards,
Sergey Kosarev.
пт, 28 дек. 2018 г. в 13:51, Ilya Kasnacheev
Hi, Igniters!
I'm newbie here.
I want to become a part of ignite community and as a first step I want to pick
a simple ticket. For example, IGNITE-5823.
I think, it's a best way to get to know the contribution process.
What do you think about it?
--
Best regards, Sergey.
Hello Ignite Community!
My name is Sergey.
I want to contribute to Apache Ignite and want to start with this issue -
IGNITE-5565. Any help on this will be appreciated.
Thanks!
Best regards,
Sergey Kosarev.
my username: macrergate
Best regards,
Sergey Kosarev.
2018-01-15 19:31 GMT+03:00 Sergey :
> Hello Ignite Community!
>
> My name is Sergey.
>
> I want to contribute to Apache Ignite and want to start with this issue -
> IGNITE-5565. Any help on this will be appreciated.
Kirill,
Indeed current behavior of force rebuild API seems broken, we need to fix
it, +1 from me too.
BTW would it be useful to allow rebuilding individual indices?
On Wed, Mar 24, 2021 at 6:20 PM ткаленко кирилл
wrote:
> Hello!
>
> What do you mean by the implementation plan?
> Implement tick
Hello Igniters,
I would like to start a discussion on evolving IEP-73 [1]. Now it covers a
narrow topic about components dependencies but it makes sense to cover in
the IEP a broader question: how different components should be initialized
to support different modes of an individual node or a who
I setup 2.11 instead of 2.10.
Now RunAllNightly for "ignite-2.11" branch will be run on TeamCity.
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
He joined the
> >>>>>>> community in 2016.
> >>>>>>> He participated in the development of Ignite 1.x, 2.x and he is
> >>>>>>> actively
> >>>>>>> working on a new Apache Ignite 3.0 release.
> >>>>>>>
> >>>>>>> Being a committer enables easier contribution to the project since
> >>>>>>> there
> >>>>>>> is no need to go via the patch submission process. This should
> >>> enable
> >>>>>>> better productivity.
> >>>>>>>
> >>>>>>> Please join me in welcoming Vlad, and congratulating him on the
> >> new
> >>>>>>> role
> >>>>>>> in the Apache Ignite Community.
> >>>>>>>
> >>>>>>> -Val
> >>>>>>>
> >>>>>
> >>>>> --
> >>>>> Sincerely yours, Ivan Daschinskiy
> >>>>>
> >>>>
> >>>> --
> >>>>
> >>>> Best regards,
> >>>> Ivan Pavlukhin
> >>>>
>
--
BR, Sergey Antonov
Hello, All
I’d like to join the community and contribute to the Ignite.
Would you please grant me the contributors permissions in Jira. My account
is serge.korotkov
Thanks,
--
Sergey
Hello Igniters,
I would like to prepare the IEP for some improved loading testing
framework for Ignite.
Would you please give me a write access to
https://cwiki.apache.org/confluence
Thanks,
--
Sergey Korotkov
d you please give me more?
My teamcity user name is: serge.korotkov
Thanks,
--
Sergey
Hello Petr,
On 03.08.2022 15:39, Petr Ivanov wrote:
Hi, Sergey.
What bot?
I mean this one: https://mtcga.ignite.apache.org/
But the problem was resolved for me already.
Thanks,
--
Sergey
Regards,
Petr Ivanov
Head of IT
IT & Development Solutions | GRIDGAIN SYSTEMS
+7 (911)
Hello Igniters,
Looks like it's a flaky test and it's ok now:
https://ci2.ignite.apache.org/buildConfiguration/IgniteTests24Java8_PlatformNetCoreLinux/6564445?buildTab=tests&name=CancellationTest.TestTask&expandTestHistoryChartSection=true
Thanks,
--
Sergey
On 18.08.20
42% 2022-11-11 13:11 d3a45643 tests/__init__.py
Thanks,
--
Sergey Korotkov
On 11.11.2022 20:40, Ivan Daschinsky wrote:
Dear Igniters!
Release candidate binaries for subj are uploaded and ready for vote
You can find them here:
https://dist.apache.org/repos/dist/dev/ignite/pyignite/0.6.0
Hi, Ivan
It looks fine now. Thanks much for quick fix!
--
Sergey
On 14.11.2022 20:21, Ivan Daschinsky wrote:
Dear Igniters!
Release candidate binaries for subj are uploaded and ready for vote
You can find them here:
https://dist.apache.org/repos/dist/dev/ignite/pyignite/0.6.0.rc1
If
gt; > 5%
> > > > > drop
> > > > > > >> for
> > > > > > >> > > this.
> > > > > > >> >
> > > > > > >> > 5% may be a big drop for some use-cases, so I think we
> should
> > > look
> > > > > at
> > > > > > >> how
> > > > > > >> > to improve performance, not how to make it worse.
> > > > > > >> >
> > > > > > >> >
> > > > > > >> > >
> > > > > > >> > > >> it is hard to maintain a data structure to choose "page
> > > from
> > > > > > >> free-list
> > > > > > >> > > with enough space closest to the beginning of the file".
> > > > > > >> > > We can just split each free-list bucket to the couple and
> > use
> > > > > first
> > > > > > >> for
> > > > > > >> > > pages in the first half of the file and the second for the
> > > last.
> > > > > > >> > > Only two buckets required here since, during the file
> > shrink,
> > > > > first
> > > > > > >> > > bucket's window will be shrank too.
> > > > > > >> > > Seems, this give us the same price on put, just use the
> > first
> > > > > bucket
> > > > > > >> in
> > > > > > >> > > case it's not empty.
> > > > > > >> > > Remove price (with merge) will be increased, of course.
> > > > > > >> > >
> > > > > > >> > > The compromise solution is to have priority put (to the
> > first
> > > > path
> > > > > > of
> > > > > > >> the
> > > > > > >> > > file), with keeping removal as is, and schedulable
> per-page
> > > > > > migration
> > > > > > >> for
> > > > > > >> > > the rest of the data during the low activity period.
> > > > > > >> > >
> > > > > > >> > Free lists are large and slow by themselves, it is expensive
> > to
> > > > > > >> checkpoint
> > > > > > >> > and read them on start, so as a long-term solution I would
> > look
> > > > into
> > > > > > >> > removing them. Moreover, not sure if adding yet another
> > > background
> > > > > > >> process
> > > > > > >> > will improve the codebase reliability and simplicity.
> > > > > > >> >
> > > > > > >> > If we want to go the hard path, I would look at free page
> > > tracking
> > > > > > >> bitmap -
> > > > > > >> > a special bitmask page, where each page in an adjacent block
> > is
> > > > > marked
> > > > > > >> as 0
> > > > > > >> > if it has free space more than a certain configurable
> > threshold
> > > > > (say,
> > > > > > >> 80%)
> > > > > > >> > - free, and 1 if less (full). Some vendors have successfully
> > > > > > implemented
> > > > > > >> > this approach, which looks much more promising, but harder
> to
> > > > > > implement.
> > > > > > >> >
> > > > > > >> > --AG
> > > > > > >> >
> > > > > > >>
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > >
> > > > > > > Best regards,
> > > > > > > Alexei Scherbakov
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > >
> > > > > > Best regards,
> > > > > > Alexei Scherbakov
> > > > > >
> > > > >
> > > >
> > >
> >
>
--
Sergey Kozlov
GridGain Systems
www.gridgain.com
ough a
> > > node shutdown is expected, the procedure doesn't lead to the cluster
> > outage
> > > meaning it can be utilized for 24x7 production environments.
> > >
> > > -
> > > Denis
> > >
> > >
> > > On Mon, Oct
, Alexei Scherbakov <
alexey.scherbak...@gmail.com>:
> Sergey Antonov,
>
> The states ACTIVE, INACTIVE, READ-ONLY look confusing.
> Actually read-only cluster is active too.
>
> I would suggest adding new property to Ignite configuration like
> setActivationOptions(Activation
Ivan, thank you for documenting this functionality, agree with Pavel here.
I think this document is a good starting point and contains a lot of
low-level details and great examples but from my perspective it doesn't
show how binary objects fit into a broader picture.
It worth adding higher-level
? And if the receiver exists then who is the sender?
It seems to me that document tries to focus on details of the format itself
but other aspects of this functionality leak into the explanation and
confuses reader.
On Wed, Oct 16, 2019 at 2:52 PM Ivan Pavlukhin wrote:
> Pavel, Sergey,
>
eone could take a look at the changes and provide
any feedback on the code and/or general idea.
Thanks a lot in advance.
--
Sergey
your opinion about my points. What do you think about it?
[1] https://issues.apache.org/jira/browse/IGNITE-12225
вт, 15 окт. 2019 г. в 14:56, Sergey Antonov :
> Hi, Alexei!
>
> Thank you for reply!
>
> > The states ACTIVE, INACTIVE, READ-ONLY look confusing. Actually
> rea
k...@gmail.com
> > > > > >:
> > > > >
> > > > > > +1 for Dmitry Pavlov
> > > > > >
> > > > > > ср, 30 окт. 2019 г. в 18:22, aealexsandrov <
> > aealexsand...@gmail.com
> > > >:
> > > > > >
> > > > > > > +1 Alexey Goncharuk
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Sent from:
> > http://apache-ignite-developers.2346864.n4.nabble.com/
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > >
> > > > > > Best regards,
> > > > > > Alexei Scherbakov
> > > > > >
> > > > >
> > > >
> > >
> >
>
--
BR, Sergey Antonov
.readme.io/docs/jdbc-driver
2. https://issues.apache.org/jira/browse/IGNITE-6296
3. https://issues.apache.org/jira/browse/IGNITE-12372
--
Sergey Kozlov
GridGain Systems
www.gridgain.com
Hello Lev,
My name is Sergey, I'm from Apache Ignite community. As I can see you
successfully completed your first ticket but there are some review comments
on your second one [1].
Do you need any assistance with resolving them?
Also if you're interested in more challenging tasks,
ut it will be useful
> only for java thin client. And even with java thin client we should whether
> implement peer-class-loading for thin clients (this also requires two-way
> client-server communication) or put classes with executed closures to the
> server locally.
>
> What
ow it could be designed but without that we open the hole to
kill cluster.
>
> On Thu, Nov 21, 2019 at 11:21 AM Sergey Kozlov
> wrote:
>
> > Hi Alex
> >
> > The idea is great. But I have some concerns that probably should be taken
> > into a
Hi
On Thu, Nov 21, 2019 at 12:48 PM Denis Garus wrote:
> Hello, Sergey!
>
>
> >> 3. Ignite doesn't have roles/authorization functionality for now.
>
>
> I can't agree with you.
>
My bad, you're right. But the IEP page provided by you is limit
pdate value in cache.
User could get ClusterReadOnlyModeException in this case.
So we should return state with lower functionality from previous and
current states for avoiding unexpected behaviour.
чт, 31 окт. 2019 г. в 18:24, Alexei Scherbakov :
> Sergey Antonov,
>
> > Read-only
s may lead
to such exception. I'll file a ticket for this improvement soon.
Best regards,
Sergey
On Thu, Dec 12, 2019 at 1:27 AM Denis Magda wrote:
> I tend to agree with Mitchell that the cluster should not crash. If the
> crash is unavoidable based on the current architecture then a mes
Igniters, ticket[1] in patch available state.
Anybody want to review changes?
[1] https://issues.apache.org/jira/browse/IGNITE-12225
пн, 25 нояб. 2019 г. в 14:56, Sergey Antonov :
> Alexei Scherbakov,
>
> > After activation (in read-only mode or not) rebalancing is possible to
>
/github.com/apache/ignite-extensions).
> > >
> > > PR https://github.com/apache/ignite/pull/7222
> > >
> > > jira : IGNITE-12356 Migrate Flink module to ignite-extensions
> > >
> > > https://issues.apache.org/jira/browse/IGNITE-12356
> > >
> > > Please review and share feedback.
> > >
> > > Regards,
> > > Saikat
> > >
> >
>
--
BR, Sergey Antonov
Hi, Saikat!
The suite is green now. Thanks!
ср, 1 янв. 2020 г. в 00:08, Saikat Maitra :
> Hi Sergey,
>
> I have updated the streamers testsuite.
>
>
> https://ci.ignite.apache.org/viewLog.html?buildId=4897409&buildTypeId=IgniteTests24Java8_Streamers
>
> Regards,
butors were agreed to do
> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
> - Should you have any questions please contact
> dev@ignite.apache.org
>
> Best Regards,
> Apache Ignite TeamCity Bot
> https://github.com/apache/ignite-teamcity-bot
> Notification generated at 15:01:08 02-01-2020
>
--
BR, Sergey Antonov
Igniters, I prepared PR with fix [1].
Can someone merge it?
[1] https://github.com/apache/ignite/pull/7224/files
сб, 4 янв. 2020 г. в 12:08, Sergey Antonov :
> Hi!
>
> I'll fix failures under ticket [1].
>
> [1] https://issues.apache.org/jira/browse/IGNITE-12520
>
>
+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
che/ignite/pull/7194
> [3]
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8#ApacheIgnite2.8-Unresolvedissues(notrelatedtodocumentation)
>
> On Thu, 9 Jan 2020 at 19:01, Alexey Zinoviev
> wrote:
> >
> > +1
> >
> > чт, 9 янв. 2020 г. в 18:52, Serg
in client API and protocol and in the
> > same
> > > > > Ignite version deprecate these methods for servers and thick
> clients.
> > > > >
> > > > > [1]: https://issues.apache.org/jira/browse/IGNITE-11709
> > > > > [2]: https://issues.apache
kolay, -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 a
?serverId=apache&suiteId=IgniteTests24Java8_RunAllNightly&baseBranchForTc=ignite-2.8&branchForTc=pull%2F7239%2Fhead&action=Latest
пн, 13 янв. 2020 г., 17:51 Maxim Muzafarov :
> Sergey,
>
> Thank you. I also do not support @IgniteExperemental annotation only
> for solv
Maxim,
I will do that on monday (20/01).
пт, 17 янв. 2020 г. в 13:08, Maxim Muzafarov :
> Sergey,
>
>
> Can you, please, resolve the PR conflicts [1] [2]?
>
> [1] https://github.com/apache/ignite/pull/7238
> [2] https://issues.apache.org/jira/browse/IGNITE-11256
>
> O
Maxim,
Conflicts in pr [1] are resolved. TC Run all is started.
[1] https://github.com/apache/ignite/pull/7238
пт, 17 янв. 2020 г. в 16:04, Sergey Antonov :
> Maxim,
>
> I will do that on monday (20/01).
>
> пт, 17 янв. 2020 г. в 13:08, Maxim Muzafarov :
>
>> Sergey,
Hello community,
Recently I published a new blog post on getting started with Apache Ignite
in AWS [1]. I tried to make my example as simple as possible while keeping
it usable.
Let me know if this post is useful for you.
I plan to write several follow-up posts about AWS-specific things but base
think?
--
Thank you,
Sergey Chugunov.
On Thu, Jan 23, 2020 at 5:32 PM Emmanouil Gkatziouras
wrote:
> Hi all!
>
> Yes It seems possible to get some free quota for integration tests on AWS
> [1] however most probably they are not gonna last forever.
>
> [1]
>
> https://aws.am
Denis, Emmanouil,
Sure, I'll take a look at the code shortly.
--
Thank you,
Sergey.
On Mon, Jan 27, 2020 at 8:59 PM Denis Magda wrote:
> I support the idea of triggering such tests on demand. We can create a wiki
> page with instructions on how to run the tests. Unless ther
--
-
With best regards, Sergey Chernolyas
My jiraId is schernolyas
--
-
With best regards, Sergey Chernolyas
customer is needs to the feature and I want to implement it. I will try
to configure my developer environment as it wrote in the guide. Also ...
do you know contributors who works with Spring Data?
On Wed, 29 Jan 2020 at 08:51, Ivan Pavlukhin wrote:
> Hi Sergey,
>
> Welcome to the Apac
Hi igniters!
I have created new channel "#ignite-spring-framework" for discussion about
integration with Spring Framework.
--
-
With best regards, Sergey Chernolyas
Hi Maksim!
The link is unavailable :-( I can't open it. I think Slack is more
preferable.
On Wed, 29 Jan 2020 at 11:13, Maksim Stepachev
wrote:
> Hi,
>
> Could we use the telegram channel for it for the Russian community?
>
> https://t.me/RU_Ignite
>
> ср, 29 ян
gt; days ago Nikolay Izhikov finished the new spring boot starter.
> https://github.com/apache/ignite-extensions/tree/master/modules
>
> You may add the spring data module.
>
>
> ср, 29 янв. 2020 г. в 10:46, Sergey Chernolyas <
> sergey.chernol...@gmail.com
> >:
>
>
Do you mean channel at Telegram ?
On Wed, 29 Jan 2020 at 11:20, Maksim Stepachev
wrote:
> Okey, but our channel has 90+ active members.
>
> ср, 29 янв. 2020 г. в 11:15, Sergey Chernolyas <
> sergey.chernol...@gmail.com
> >:
>
> > Hi Maksim!
> >
> > Th
Person (id int, city_id int, name
varchar, age int, company varchar, PRIMARY KEY (id, city_id))
Other ideas ?
--
-
With best regards, Sergey Chernolyas
wrote:
> Hello, Sergey.
>
> Your proposal is not clear for me
> Can you, please, describe the issue you are trying to solve?
> And the way you want to do it.
>
>
> > 29 янв. 2020 г., в 14:53, Sergey Chernolyas
> написал(а):
> >
> > Hi!
> > It is
Hi!
It is seemed what I need.
On Wed, 29 Jan 2020 at 15:14, Nikolay Izhikov wrote:
> Hello, Sergey.
>
> What is «repository»? How it relates to the Ignite?
>
> ignite-spring-boot-autoconfigure confirms your requirements?
>
>
> https://github.com/apache/ignite-extens
, property "
*spring.data.mongodb.uri*" from spring data repository for mongodb
On Wed, 29 Jan 2020 at 15:16, Sergey Chernolyas
wrote:
> Hi!
>
> It is seemed what I need.
>
> On Wed, 29 Jan 2020 at 15:14, Nikolay Izhikov wrote:
>
>> Hello, Sergey.
>>
>
. The code will analyse type of content (clear
string or expression)
2) at new field.
I mean annotation
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/springdata20/repository/config/RepositoryConfig.html
--
-
With best regards, Sergey Chernolyas
options:
1) field "cacheName" will be able to process expression and constant
string. The code of repository factory will analyse the field.
2) create new field for expressions
What is best way?
--
-----
With best regards, Sergey Chernolyas
Hi Ivan!
https://github.com/apache/ignite/pull/7347 . It is link to PR. Criticism
is welcome :-)
On Sat, 1 Feb 2020 at 18:15, Ivan Pavlukhin wrote:
> Sergey,
>
> Could you please share your prototype, I would like to have a look.
>
> сб, 1 февр. 2020 г. в 16:59, schernolyas :
cycle to
extension project.
May we do it? When (which release for?) and how?
-
With best regards, Sergey Chernolyas
Ivan,
Thanks. I have answered.
On Tue, 4 Feb 2020 at 15:03, Ivan Pavlukhin wrote:
> Sergey,
>
> Thank you for your efforts! I left some comments in the ticket [1].
>
> [1] https://issues.apache.org/jira/browse/IGNITE-12582
>
> сб, 1 февр. 2020 г. в 18:35, Sergey Chernoly
code.
--
-
With best regards, Sergey Chernolyas
gt; >
> > [1]
> >
> https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/lang/IgniteExperimental.java
> > [2]
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Public-API-deprecation-rules-td45647.html
> >
> > Thanks,
> > --AG
>
>
>
> --
> Best Regards, Vyacheslav D.
>
--
BR, Sergey Antonov
-1 Prohibit.
To me as a developer the situation when old but stable API is deprecated
with only experimental (thus unstable/unfinished) alternative is very far
from comfortable.
And from outside folks it may look like as a sign of immature processes
inside Ignite community (which is definitely not
t; On Tue, 18 Feb 2020 at 13:51, Maxim Muzafarov <
> mmu...@apache.org>
> > >> wrote:
> > >> >> > > > >
> > >> >> > > > > Igniters,
> > >> >> > > > >
> > >> >> > > > >
> > >> >> > > > > I've prepared the issue [1] and PR [2] with removing
> @deprecate
> > >> >> > > > > annotation on DataRegionMetrics and adding
> @IgniteExperimental
> > >> to the
> > >> >> > > > > new metrics API.
> > >> >> > > > > Can anyone review my changes?
> > >> >> > > > >
> > >> >> > > > >
> > >> >> > > > > [1] https://issues.apache.org/jira/browse/IGNITE-12690
> > >> >> > > > > [2] https://github.com/apache/ignite/pull/7440
> > >> >> > > > >
> > >> >> > > > > On Tue, 18 Feb 2020 at 13:42, Ilya Kasnacheev <
> > >> ilya.kasnach...@gmail.com>
> > >> >> > > > wrote:
> > >> >> > > > > >
> > >> >> > > > > > Hello!
> > >> >> > > > > >
> > >> >> > > > > > I have just merged a fix for embarrassing issue where you
> > >> could UPDATE
> > >> >> > > > > > entries with Spring Data, but not "Update" or "update"
> them.
> > >> >> > > > > >
> > >> >> > > > > > I suggest adding this fix to the scope of 2.8, since
> Spring
> > >> Data is
> > >> >> > > > popular
> > >> >> > > > > > and it does not in any way affect code outside of its
> > >> modules.
> > >> >> > > > > >
> > >> >> > > > > > https://issues.apache.org/jira/browse/IGNITE-12672
> > >> >> > > > > >
> > >> >> > > > > > WDYT?
> > >> >> > > > > >
> > >> >> > > > > > Regards,
> > >> >> > > > > > --
> > >> >> > > > > > Ilya Kasnacheev
> > >> >> > > > > >
> > >> >> > > > > >
> > >> >> > > > > > пн, 17 февр. 2020 г. в 12:44, Maxim Muzafarov <
> > >> mmu...@apache.org>:
> > >> >> > > > > >
> > >> >> > > > > > > Alexey,
> > >> >> > > > > > >
> > >> >> > > > > > >
> > >> >> > > > > > > Yes. I will remove @deprecation according to the vote
> > >> results and
> > >> >> > > > will
> > >> >> > > > > > > go further with the release steps [1] since there no
> > >> blockers left.
> > >> >> > > > > > >
> > >> >> > > > > > >
> > >> >> > > > > > > [1]
> > >> >> > > >
> > >> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
> > >> >> > > > > > >
> > >> >> > > > > > > On Mon, 17 Feb 2020 at 11:48, Alexey Goncharuk
> > >> >> > > > > > > wrote:
> > >> >> > > > > > > >
> > >> >> > > > > > > > Folks,
> > >> >> > > > > > > >
> > >> >> > > > > > > > I have merged IGNITE-12650 (mark MVCC as
> experimental)
> > >> to master
> > >> >> > > > and
> > >> >> > > > > > > > ignite-2.8. What's left? Should we remove deprecation
> > >> from the old
> > >> >> > > > > > > metrics
> > >> >> > > > > > > > and start the vote?
> > >> >> > > > > > >
> > >> >> > > >
> > >>
> > >
>
--
BR, Sergey Antonov
Guys, can somebody check those links from TC account different from @
apache.org domain?
пт, 28 февр. 2020 г. в 11:58, Pavel Tupitsyn :
> Sergey, can't confirm, those links work for me
>
> On Thu, Feb 27, 2020 at 11:17 PM Sergey Antonov >
> wrote:
>
> > Hello, Max
Ivan,
I also don't think this issue is a blocker for 2.8 as it affects only
experimental functionality and only in special cases.
Removing key length limitations in MetaStorage seems more strategic
approach to me but depending on how we decide to approach it (as a local
fix or as part of a broade
ResultsDiv
пт, 28 февр. 2020 г. в 16:41, Maxim Muzafarov :
> Sergey,
>
>
> It seems these links ([4] Check RC: Licenses, compile, checksum) [1]
> is only accessed for users included into the release group on the
> TeamCity.
> Sorry for not mentioned it before.
>
>
> [
0.
Still can't get access to teamcity links.
пн, 2 мар. 2020 г., 17:24 Alexey Zinoviev :
> +1 (binding)
> I've downloaded the binary archive, run it, checked the ML examples and
> JavaDocs.
>
>
>
> вс, 1 мар. 2020 г. в 13:49, Ivan Pavlukhin :
>
> > +1 (binding)
> >
> > Downloaded binary distribut
created.
> >
> >
> > I propose the following dates for 2.8.1 release:
> > Scope Freeze: April 15, 2020
> > Code Freeze: April 22, 2020
> > Voting Date: April 27, 2020
> > Release Date: May 1, 2020
> >
> >
> > Please, share your thoughts.
> >
> >
> > [1]
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8.1
> > [2] https://github.com/apache/ignite/tree/ignite-2.8.1
> >
>
--
-
With best regards, Sergey Chernolyas
Hello Sergey,
Your analysis looks valid to me, we definitely need to investigate this
deadlock and find out how to fix it.
Could you create a ticket and write a test that reproduces the issue with
sufficient probability?
Thanks!
On Mon, Mar 16, 2020 at 8:22 PM Sergey-A Kosarev
wrote
Hi igniters!
I ask to review PR for issue
https://issues.apache.org/jira/browse/IGNITE-12799 . My PR is approved by
TeamCity and ready for merge.
--
-
With best regards, Sergey Chernolyas
gt; > MOVING due to counter difference on node join.
> > IGNITE-12551 Partition desync if a partition is evicted then owned again
> > and historically rebalanced
> > IGNITE-12536 Inconsistency between cache data and indexes when cache
> > operation is interrupted
> > IGNITE-12403 Throttle page difference output in PageMemoryTracker
> > IGNITE-12523 Continuously generated thread dumps in failure processor
> slow
> > down the whole system
> > IGNITE-12489 Error during purges by expiration: Unknown page type
>
--
BR, Sergey Antonov
ionKeyV2 [grpId=1544803905, grpName=default,
> >> > partId=7]
> >> > Partition instances: [PartitionHashRecordV2 [isPrimary=false,
> >> > consistentId=gridCommandHandlerTest2, updateCntr=3,
> >> partitionState=MOVING,
> >> > state=MOVING]] .. and so on
> >> >
> >> > I found this erroneous and can lead to further cluster index
> corruption,
> >> > for example in case when only command OK result checked.
> >> >
> >> > If no objections would be here, i plan to inform about moving states
> as
> >> > not OK exit code too.
> >> >
> >> >
> >>
> >>
> >>
> >> --
> >> Vladislav Pyatkov
> >> Architect-Consultant "GridGain Rus" Llc.
> >> +7-929-537-79-60
> >>
>
>
>
>
--
BR, Sergey Antonov
tNull too and to add such check to checkstyle
> > plugin too?
> >
> > [1]
> >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/Coding+Guidelines#CodingGuidelines-@Annotations
> >
>
--
BR, Sergey Antonov
with this change?
> WDYT?
>
>
> [1]
> https://cwiki.apache.org/confluence/display/IGNITE/Coding+Guidelines#CodingGuidelines-Naming
> [2]
> https://web.archive.org/web/20120911192801/developers.sun.com/sunstudio/products/archive/whitepapers/java-style.pdf
> [3] https://gith
rties.html#IGNITE_MAX_INDEX_PAYLOAD_SIZE
--
BR, Sergey Antonov
Hi Denis,
The problem could be shown when you invoke CREATE INDEX without the
INLINE_SIZE parameter. You don't face with described problem If index
creates by CREATE_INDEX with explicit INLINE SIZE value.
вт, 28 апр. 2020 г. в 02:31, Denis Magda :
> Hi Sergey,
>
> Your changes lo
t;
> Regards,
> --
> Ilya Kasnacheev
>
>
> вт, 28 апр. 2020 г. в 02:31, Denis Magda :
>
> > Hi Sergey,
> >
> > Your changes look useful from the application developer perspective.
> > However, I'm curious why would the one change some low-level
> >
recalculated. It can lead to a difference in inline sizes
without IGNITE_MAX_INDEX_PAYLOAD_SIZE option.
вт, 28 апр. 2020 г. в 14:22, Maxim Muzafarov :
> Sergey, Ilya,
>
>
> Since inline size for the `create table` clause not supported yet and
> the IGNITE_MAX_INDEX_PAYLOAD_SIZE
Maxim, I'm talking about cluster upgrade through cluster stop -> binary
update -> cluster start.
вт, 28 апр. 2020 г. в 14:37, Maxim Muzafarov :
> Sergey,
>
> Are you talking about a cluster rolling upgrade feature? AFAIK, Apache
> Ignite doesn't support this feature,
Hi, the ticket is ready for review.
[1] https://github.com/apache/ignite/pull/7728
вт, 28 апр. 2020 г. в 14:39, Sergey Antonov :
> Maxim, I'm talking about cluster upgrade through cluster stop -> binary
> update -> cluster start.
>
> вт, 28 апр. 2020 г. в 14:37, Maxim
he following:
> >
> >
> > * store binary meta and marshaller data inside db/ folder
> > * if binary meta of marshaller are found in "legacy" locations --
> > safely move them to new locations during the node startup
> >
> >
> > Kind regards,
> >
> > Semyon Danilov.
> >
>
--
BR, Sergey Antonov
debugging.
> > 2. Almost every system with transactions has timeout enabled by default.
> >
> > WDYT?
> >
> > --
> > Best Regards,
> > Ivan Rakov
> >
>
>
> --
> Best regards,
> Andrey V. Mashenkov
>
--
BR, Sergey Antonov
ilure/StopNodeOrHaltFailureHandler.html
[2]
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/failure/StopNodeFailureHandler.html
[3]
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/Ignition.html#KILL_EXIT_CODE
--
BR, Sergey Antonov
I've created the Ignite ticket for this improvement [1].
[1] https://issues.apache.org/jira/browse/IGNITE-13047
чт, 21 мая 2020 г. в 00:46, Sergey Antonov :
> Hello, Igniters!
>
> I'd like to discuss behaviour of Ignite process exit code if the node was
> stopped by fail
://issues.apache.org/jira/browse/IGNITE-13071
--
BR, Sergey Antonov
Maxim, I'd prefer to do this with a separate ticket.
вт, 26 мая 2020 г. в 19:59, Maxim Muzafarov :
> Sergey,
>
> Sounds good!
> Should we consider removing the deprecated methods `active()`,
> `active(boolean active)` from tests also?
>
> On Tue, 26 May 2020 at 12:1
Maxim, I've created a ticket [1] for this change.
[1] https://issues.apache.org/jira/browse/IGNITE-13079
вт, 26 мая 2020 г. в 20:09, Sergey Antonov :
> Maxim, I'd prefer to do this with a separate ticket.
>
> вт, 26 мая 2020 г. в 19:59, Maxim Muzafarov :
>
>&g
Hi Ivan,
I have an idea about suggested maintenance mode.
First of all, I agree with your ideas about discovery restrictions: node
should not join topology when performing defragmentation.
At the same time I haven't heard about requests for this mode from users,
so we don't know much about possi
t;
> > Dev ops/admins/anyone who admins Ignite may want to know it's value
> without
> > going to Java code.
> >
> > чт, 21 мая 2020 г. в 09:39, Zhenya Stanilovsky
> :
> >
> >> Thank you Sergey, as for me — very useful proposal huge +1 here.
> >>
&
1 - 100 of 1168 matches
Mail list logo
