s) and making sure all the checks pass. And any closed PR can be
brought back
Yakov
On Thu, Mar 4, 2021, 05:19 Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> Petr,
>
> Any suggestions on how to fix this? One of the ideas that come to my mind
> is to unify the pro
the
serialized processor is of smaller size then we can send it instead of the
delta. This can sound like an overcomplication, but still good to measure.
Regards,
Yakov
Hey Valentin!
Any design docs/wiki for 1, 4 and 5 so far?
Yakov Zhdanov
ot work as users may expect them to and some look
just weird.
Ready to discuss the above and other points.
Thanks!
Yakov
I think there should be a link on the page - Suggest edits
--Yakov
Lukas, would you be so kind as to suggest edits for the mentioned
documentation page. Your suggesions will be reviewed and incorporated.
Thanks!
--Yakov
We still need to differentiate between nulls and empty strings.
--Yakov
other. Agree?
--Yakov
allow people new to Ignite to quickly start the cluster.
As far as I remember hazelcast has multicast enabled by default. Can
anybody check this?
--Yakov
Guys, I remember we did this to
--Yakov
ср, 27 февр. 2019 г. в 14:46, Dmitrii Ryabov :
> Hello, Igniters!
>
> Code is ready and reviewed, tests are passed.
>
> Can we make final decision about this change? Do we really need it? [1]
>
> Pros:
>
> * Multicast ipFinder
ould fire a special event and then kill
itself. Thoughts?
--Yakov
t lap message and latest 2nd lap
message and process metrics message in message worker thread in queue order
if they are latest and skip the otherwise.
Does this make sense?
--Yakov
Yakov Zhdanov created IGNITE-10698:
--
Summary: Get rid of @MXBeanParametersNames and
@MXBeanParametersDescriptions
Key: IGNITE-10698
URL: https://issues.apache.org/jira/browse/IGNITE-10698
Project
performance of the system. If this is hard to support in 2.x then let's do
it in 3.0. Vladimir, what do you think?
-- Yakov
Vladimir, can you please take a look at
https://issues.apache.org/jira/browse/IGNITE-10376?
--Yakov
Max, correct link to ticket is
https://issues.apache.org/jira/browse/IGNITE-10258
I would agree with you and Vladimir that parameters in mentioned case may
appear in any order.
--Yakov
tests. 2nd step should not start
(except manually) if 1st step results in any build failure.
--Yakov
Nikolay, let me take a look at the changes. I will do it possibly over
weekend.
Thanks!
--Yakov
2018-11-08 17:20 GMT+03:00 Nikolay Izhikov :
> Hello, Igniters.
>
> Please, respond if anyone wish to do the additional review of this
> improvement.
>
> I think it's ready to
Wayne, can you please share a reproducer for this problem that can be
launched from IDE?
--Yakov
Wayne, can you please share a reproducer for this problem that can be
launched from IDE?
--Yakov
No, I meant under Ignite's git so any change to resource file arrives with
project workspace updates and gets automatically picked up by plugin.
Makes sense?
--Yakov
returns with
more contributions then he or she should account all the changes made on
review and, again, come to a point where all project requirements are
staisfied.
Btw, Vyacheslav, can we have abbreviations.properties in the project under
git and have plugin use it?
--Yakov
Denis, there were email notifications from wiki on corresponding edits =)
--Yakov
ok for future in case it does not
bring confusion and does not hurt readability.
Let's keep using abbreviations and treat them as mandatory requirement.
This is important for keeping our codebase consistent and tidy.
--Yakov
and those that are
Ignite domain specific.
I would also suggest that we treat names mentioned in the table on the page
as names that are required to be abbreviated. Please take this into account
when conducting code reviews.
Thanks!
--Yakov
et's split this dump into 5 chunks and send them with 100 ms delays.
This should fail before fix is applied, and should pass with proper message
parsed after we have the issue fixed.
Thanks!
--Yakov
!
--Yakov
Michael, can you please share a reproducer? Is it possible to snapshot a
packet that causes the error and just emulate packet send with manually
opened socket bypassing Redis client lib?
--Yakov
if we have TC build failing if there is any.
Thanks!
--Yakov
pretouch for offheap may be helpful in many cases.
--Yakov
last question
> - the new configuration ignite_inspections_teamcity.xml added to PR;
Can this be installed locally by every contributor to check the code? Can
we add this to setup steps we have on wiki?
--Yakov
Config option + mbean access. Does that make sense?
Yakov
On Fri, Sep 28, 2018, 17:17 Vladimir Ozerov wrote:
> Then it should be config option.
>
> пт, 28 сент. 2018 г. в 13:15, Andrey Gura :
>
> > Guys,
> >
> > why we need both config option and system
Agree with David. We need to have an opporunity set backups count threshold
(at runtime also!) that will not allow any automatic stop if there will be
a data loss. Andrey, what do you think?
--Yakov
Yes, and you should suggest solution, e.g. throttle rebalancing threads
more to produce less load.
What you suggesting kills the idea of this enhancement.
--Yakov
2018-09-07 19:03 GMT+03:00 Andrey Kuznetsov :
> Yakov,
>
> Thanks for reply. Indeed, initial design assumed node termina
ad to
increasing latency in cluster till its full unavailability.
So, killing node hanging on fsync may be reasonable. Agree?
You may implement the approach when you have warning messages in logs by
default, but termination option should also be available.
Thanks!
--Yakov
2018-09-06 17:02 GMT+
Great news, Vladimir! Congratulations!
--Yakov
2018-08-30 15:15 GMT+03:00 Vladimir Ozerov :
> Igniters,
>
> I am glad to announce that we finally merged MVCC and transactional SQL
> support to master branch.
>
> This long journey started more than a year ago with multiple d
Nikolay,
I think we should have 2 weeks after code freeze which by the way may
include RC1 voting stage. This way I would like us to agree that release
candidate should be sent to vote on Oct, 11th and we can release on Oct,
15th.
What do you think?
--Yakov
fixed. Then Nikolay will process the ones that are not
assigned yet. Nikolay, can you take a look please?
--Yakov
2018-08-24 12:58 GMT+03:00 Nikolay Izhikov :
> Hello, Dmitriy.
>
> Release page - [1]
>
> > I think it is important to include the links to all important Jira
> ti
es? I believe this should
speed up review process very much.
--Yakov
Guys, what time in % does crc calculation take in WAL logging process?
--Yakov
2018-08-14 13:37 GMT+03:00 Dmitriy Pavlov :
> Hi Alex, thank you for this idea.
>
> Evgeniy, Alex, would you like to submit the patch with bypassing
> implementation differences to keep compatibility?
&
Hi Yriy!
Go ahead! You were added!
--Yakov
2018-08-07 17:19 GMT+03:00 Юрий :
> Hello, Ignite Community!
>
> My name is Iurii. I want to contribute to Apache Ignite.
> my JIRA user name is jooger. Any help on this will be appreciated.
>
> Thanks!
>
> --
> Live with a smile! :D
>
Sergei, you are welcome! I have added you to contributors. Please go ahead!
--Yakov
2018-08-07 16:18 GMT+03:00 s v :
> Hello, Ignite Community!
>
> My name is Sergei. I want to contribute to Apache Ignite and want to start
> with this issue - https://issues.apache.org/jira/browse
Well, I tend to agree. Can you try applying it on some suite and share the
results in terms of run time decrease and decreasing number of random
failures due to improper tests stop or cleanup?
--Yakov
2018-08-02 16:37 GMT+03:00 Denis Mekhanikov :
> Yakov,
>
> Almost every test in th
Maxim, did we have .net tests failing before merge? If yes, how come we
merged it?
--Yakov
2018-08-02 18:03 GMT+03:00 Maxim Muzafarov :
> Folks,
>
> Seems like rebalancing changes leads us to hanging TestRebalance() test for
> .NET.
> Created issue [1], I will try to investi
It should be true, otherwise we would have nodes from all agents
intersecting. No?
And multicast IP finder is the defailt one, so I would not reduce its test
volume.
Yakov Zhdanov
www.gridgain.com
2018-08-02 0:32 GMT+03:00 Dmitriy Pavlov :
> Hi Yakov,
>
> Regarding Each TC agen
I disagree. Probably, no change required. Each TC agent use own multicast
group so nodes do not intersect. If any of the test does not properly clean
up and leaves nodes running this dhould be flagged as test fail which is
the case.
Please provide strong reasons to start with this.
--Yakov
Agree with Dmitry P.
Guys! Even if you file a ticket on yourself please spend additional 5 mins
to add minimal description to provide idea on the intended changes for the
rest of our community or those who will have to deal with your changes in
future.
--Yakov
several clusters in the same
network.
--Yakov
2018-07-18 17:30 GMT+03:00 Dmitry Pavlov :
> Hi Stanislav,
>
> I wish this push will have effect.
>
> Just two proposals that will help Igniters to easily jump into such emails:
> 1. Include ticket short description into subject, no
Yes! Just deprecate getAll() and change default keepAll for scans to false.
--Yakov
2018-07-18 13:39 GMT+03:00 Alexey Goncharuk :
> Folks,
>
> There is no need to add getNext() method because the object we are
> discussing is already an iterator. Then, to summarize the solution, we
Maxim, I checked and it seems that send retry count is used only in cache
IO manager and the usage is semantically very far from what I suggest.
Resend count limits the attempts count, while I meant successfull send but
possible problems on supplier side.
--Yakov
2018-07-17 19:01 GMT+03:00 Maxim
Dmitry, it hink we can do this change right away. All we need is to add
proper error message on cache config validation in order to tell user that
default changed and manual configuration is needed for compatibility.
--Yakov
2018-07-16 15:47 GMT+03:00 Dmitry Karachentsev :
> Created a tic
the 1st one.
You can use the following message
Failed to wait for supply message from node within 30 secs [cache=C,
partId=XX]
Alex Goncharuk do you have comments here?
Yakov Zhdanov
www.gridgain.com
2018-07-14 19:45 GMT+03:00 Maxim Muzafarov :
> Yakov,
>
> Yes, you're right. Who
I think you need to signup to Apache jira and let us know your user ID so
we can add you to contributors. Dmitry Pavlov, can you please help.
--Yakov
2018-07-12 18:54 GMT+03:00 vgrigorev :
> Hi colleges!
>
> I would like move topic to suitable place.
>
> Please only clarify how t
Dmitry, let's have only getNext() same as jdbc. All other shortcuts seem to
overload API without adding much value.
--Yakov
2018-07-16 17:33 GMT+03:00 Dmitriy Setrakyan :
> Well, instead of getFirst(), I would have getNext(). This way we do not
> have to keep the first entry for
instantiation. I am pretty sure none needs getAll() in scans.
Alex?
--
Yakov
Maxim, I do not understand the problem. Imagine I do not have any ordering
but rebalancing of some cache fails to start - so in my understanding
overall rebalancing progress becomes blocked. Is that true?
Can you pleaes provide reproducer for your problem?
--Yakov
2018-07-09 16:42 GMT+03:00
If events are working when grid is not active and adding/removing listeners
is also possible then I agree/
--Yakov
Hi!
Can you please move you proposal to Apache Ignite Wiki as new IEP? So that
community can discuss and comment? Eventually we will end up with a plan on
creating the guide. What do you think?
--Yakov
2018-07-12 12:24 GMT+03:00 vgrigorev :
> Very many developers have desire to participate
Its counter event on_after_deactivated cannot be fired through event
notification support. Therefore, it is better to gather such events in
LifeCycleEventType.
--Yakov
Ivan, yes. We can go with reflection through configuration and SPIs and,
you are rigth, suppressed list should be manually defined.
--Yakov
Ivan, I would think of some test that will randomly generate configs for
nodes and run some logic.
--Yakov
Stan, feel free to file the ticket. Just make sure to add detailed
description to it. Your suggestion seems to make sense.
--Yakov
cle/LifecycleEventType.html
--Yakov
aring your thoughts on this. Question is pretty
important for us.
--Yakov
Guys, I created ticket for config params validation -
https://issues.apache.org/jira/browse/IGNITE-8951. Feel free to comment.
Yakov Zhdanov
www.gridgain.com
2018-07-04 10:51 GMT+03:00 Andrew Medvedev :
> Hi Nikolay
>
> No, we have been beaten by
> https://issues.apache.org/jira/b
Yakov Zhdanov created IGNITE-8951:
-
Summary: Need to validate nodes configuration across cluster and
warn on different parameters value
Key: IGNITE-8951
URL: https://issues.apache.org/jira/browse/IGNITE-8951
We can start with separate discussion on dev list. Or can you point to
existing one? I think I need some details here.
--Yakov
changes we may want to do in 3.0, I think we
need to file tickets for 3.0 and label them as "breaking change" to reflect
in release notes those that will be implemented.
Thoughs?
--Yakov
2018-06-07 19:36 GMT+03:00 Ilya Kasnacheev :
> Hello!
>
> Do we have an official subj list? S
from other vendors?
--Yakov
Andrey, your suggestions look good to me. Let maintainer review your patch.
--Yakov
, i.e.
we should return completed future, ignoring the fact that user expected us
to be async.
I would like to have very strong reasons to start reapproaching this.
--Yakov
Ok, then it probably might have been created before this PR. Anyway, I
would not bother too much about pt 3.
--Yakov
2018-05-21 16:15 GMT+03:00 Dmitry Pavlov :
> Hi Yakov,
>
> I've checked this code and IgniteCacheTestSuite6 includes TxLabelTest, so
> point 3 can be con
before changing anything in transactional logic.
Thanks!
--Yakov
(BL)AT modes in 2.6. I think that adding messages makes sense and
should be clear for users which is not the case for 2.4.
--Yakov
Guys,
How do we update counter right now?
If we move to fair thread-per-partition we can update counter only if we
add new key and skip if we add or remove a version. Thoughts?
--Yakov
2018-04-25 12:07 GMT+03:00 Vladimir Ozerov :
> This is interesting question. Full-scan size may
Alexey Goncharuk, Vladimir Ozerov, what do you think about these tests?
I believe they were created as a part of variuos optimization and profiling
activities. I also think we can remove them since nobody cares about them
for too long.
Thoughts?
Yakov Zhdanov
ср, 18 апр. 2018 г., 16:42 Ilya
Of course, no guarantees, but at least an effort.
--Yakov
message to log - "Critical
system thread failed on node XXX [details=...]". This should help a lot
with investigations.
Andrey Gura, Alex Goncharuk what do you think?
--Yakov
[1]
https://cwiki.apache.org/confluence/display/IGNITE/IEP-14+Ignite+failures+handling
+1 here
Always wanted to remove ForceKeysRequest =)
--Yakov
How about skipWalOnRebalancing or disableWalOnRebalancing? I like the first
one better and both are shorter.
--Yakov
2018-04-09 19:55 GMT+03:00 Denis Magda :
> I would enable this option only after we confirm it's stable. Until it
> happens it should be treated as an experimental f
Guys, has anybody checked with INFRA if we can have module structure? Denis?
--Yakov
Dmitry, I think Anton meant AtomicsConfiguration, not atomic caches.
However, I would make sure we validate all conf parameters.
Anton, can you please share junit test that shows the problem?
Yakov Zhdanov
сб, 7 апр. 2018 г., 6:12 Dmitriy Setrakyan :
> I would say absolutely YES - we need
Cross posting to dev.
Vladimir Ozerov, can you please take a look at NPE from query processor
(see below - GridQueryProcessor.typeByValue(GridQueryProcessor.java:1901))?
--Yakov
2018-03-29 0:19 GMT+03:00 smurphy :
> Code works in Ignite 2.1.0. Upgrading to 2.4.0 produces the stack tr
Andrey, I understand your point but you are trying to build one more
mechanism and introduce abstractions that are already here. Again, please
take a look at segmentation policy and event types we already have.
Thanks!
Yakov
If java runs oome then you cannot guarantee anything. Including calling
runtime.halt().
My point is about consistent approach throughout the project. I think
developing new mechanism with separate interface is incorrect.
Yakov
Awesome article, Dmitry!
Denis Magda, should we put a link to it from apacheignite.readme.io?
--Yakov
org.apache.ignite.plugin.segmentation.SegmentationPolicy
and
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.DiscoveryWorker#onSegmentation.
Discovery manager records the event (allowing user to get notification on
it) and executes internal logic in case segmentation policy is not NOOP.
Thanks!
--Yakov
Great progress, guys! Keep going!
--Yakov
Alexey, generally I agree. However, I don't understand what exactly you
suggest. Can you please list the list of parameters you want to deprecate
(1), internal logic changes (2) and updates to the javadocs/description of
the params you want to keep (3)?
--Yakov
them are already fsynced.
Correct?
Yakov Zhdanov,
www.gridgain.com
2018-02-13 21:29 GMT+03:00 Ivan Rakov :
> Yakov,
>
> I see the only one problem with your suggestion - number of
> "uncheckpointed" segments is potentially unlimited.
> Right now we have limited number (
I meant we still will be copying segment once and then will be moving it to
archive which should not affect file system much.
Thoughts?
--Yakov
2018-02-13 21:19 GMT+03:00 Yakov Zhdanov :
> Alex,
>
> I remember we had some confusing behavior for WAL archive when archived
> s
oint? Will this
work?
Thanks!
--Yakov
Alex, you can alter ServerImpl and insert a latch or thread.sleep(xxx)
anywhere you like to show the incorrect behavior you describe.
--Yakov
+1 for deprecation
--Yakov
2018-01-30 1:06 GMT+03:00 Valentin Kulichenko :
> +1
>
> On Mon, Jan 29, 2018 at 8:31 AM, Andrey Mashenkov <
> andrey.mashen...@gmail.com> wrote:
>
> > Vyacheslav,
> >
> > +1 for dropping @CacheLocalStore.
> > Ignite
move the plugins to extdata project similar to
PlatformTestPlugin and configure them only when needed. This is not correct
that each test we run for Ignite runs with plugins configured. By default
Ignite does not have any plugin.
--Yakov
Apache.Ignite.Core.Tests.Client.Cache.CacheTest.TestAsyncCompletionOrder()
in
/home/yzhdanov/projects/incubator-ignite/modules/platforms/dotnet/Apache.Ignite.Core.Tests/Client/Cache/CacheTest.cs:line
855
If you need logs just let me know.
--Yakov
Vlad and Tim, thanks for working on this!
Tim, please assign ticket to yourself to follow community process.
Currently I see it is unassigned.
--Yakov
2018-01-25 8:53 GMT-08:00 Vladisav Jelisavcic :
> Hi Tim,
>
> thank you for delving deeper into the problem,
> I left you a comment
Did we add what Pavel suggested to README.txt and readme.io documentation?
Yakov Zhdanov,
www.gridgain.com
2018-01-25 14:27 GMT-08:00 Denis Magda :
> Pavel, it’s a good point.
>
> Peter, could you ensure that all Ignite scripts (ignite.sh/bat,
> control.sh/bat, etc.) perform this au
dle of the
query and return result for cache.get(key); if partition for that key is
still in the grid.
--Yakov
I'm still not sure on what Val has suggested. Dmitry, Val, Do you have any
concrete API/algorithm in mind?
--Yakov
1 - 100 of 739 matches
Mail list logo
