Re: Contribution

2018-07-27 Thread Dmitry Pavlov
Hi Pankaj,

Welcome to the Apache Ignite community. I've added you to contributor list,
so now you can assign ticket to yourself.

Looking forward to your contributions!

Sincerely,
Dmitriy Pavlov

P.S. Additional references for you that should boost your onboarding.

Please subscribe to both dev and user lists:
https://ignite.apache.org/community/resources.html#mail-lists

Get familiar with Ignite development process described here:
https://cwiki.apache.org/confluence/display/IGNITE/Development+Process

Instructions on how to contribute can be found here:
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute

Project setup in Intellij IDEA:
https://cwiki.apache.org/confluence/display/IGNITE/Project+Setup

пт, 27 июл. 2018 г. в 18:22, pankaj kumar :

> Hello,
>
> I want to contribute to Ignite. My JIRA id is pankaj024.
> Please add me to the contributor list.
>
> Thank you
> Pankaj
>


Re: GridCacheReplicatedFullApiMultithreadedSelfTest1 not used, not compile. Remove?

2018-07-27 Thread Dmitry Pavlov
Merged to master. Thank you, Maxim.

пт, 27 июл. 2018 г. в 11:17, Maxim Muzafarov :

> Folks,
>
> I've found issue related to this test [1] (created 2016).
> Looks like it not used, I've prepared PR [2].
>
> If you have time, please, review changes.
>
>
> [1] https://issues.apache.org/jira/browse/IGNITE-3499
> [2] https://github.com/apache/ignite/pull/4443
>
>
> On Fri, 20 Jul 2018 at 13:27 Dmitry Pavlov  wrote:
>
> > Hi Maxim,
> >
> > I think we should remove such code. And if nobody objects I can apply PR
> on
> > Monday.
> >
> > Ilya, please confirm you're agree.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > пт, 20 июл. 2018 г. в 13:16, Maxim Muzafarov :
> >
> > > Ignites,
> > >
> > > I've faced with test in Ignite code base that is fully commented. You
> can
> > > check it
> > > by yoursefl [1]. As it not used since 2014 and not even compile I'm
> > > suggesting
> > > to remove it.
> > >
> > > What do you think about it? Please, share your thoughts.
> > >
> > > Full name:
> > >
> > >
> >
> org.apache.ignite.internal.processors.cache.distributed.replicated.GridCacheReplicatedFullApiMultithreadedSelfTest1
> > >
> > > [1]
> > >
> > >
> >
> https://github.com/apache/ignite/blob/master/modules/core/src/test/java/org/apache/ignite/internal/processors/cache/distributed/replicated/GridCacheReplicatedFullApiMultithreadedSelfTest1.java
> > > --
> > > --
> > > Maxim Muzafarov
> > >
> >
> --
> --
> Maxim Muzafarov
>


Re: Data regions on client nodes

2018-07-27 Thread Dmitry Pavlov
Maxim, thank you.

If it seems it is technically possible, we can file ticket for this change.

I find this proposal reasonable, change makes perfectly sense to me.

We can wait Alex G. feedback on this change before starting actual
implementation. It can take for a while, because he is travelling now.

пт, 27 июл. 2018 г. в 14:35, Maxim Muzafarov :

> Guys,
>
> I can miss some details, but at the first glance we have everething we need
> to defer
> region memory allocation if it has no cache groups assignments. And it
> doesn't matter
> where it happens on client or server nodes.
>
> Currently region memory allocation happens at exchange future init method.
> At the
> node startup method initCachesOnLocalJoin executes. This method resposnible
> for
> memory allocation (through initiating cache managers) and it also starts
> caches.
> So, at this point we have all existing caches descriptors and can find out
> which
> cache matches which region to defer some regions initialization to the
> moment when
> newly cache assings to this region (happend at onCacheChangeRequest).
>
> Please, сorrect me if I'm wrong and missing something.
>
>
>
> On Wed, 25 Jul 2018 at 19:32 Dmitry Pavlov  wrote:
>
> > Hi Maxim,
> >
> > thank you for stepping in. How do you think, is it possible to check
> cache
> > assignment to region at stage of memory allocation?
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > ср, 25 июл. 2018 г. в 18:22, Maxim Muzafarov :
> >
> > > Folks,
> > >
> > > I've checked memory allocation. It looks like we are allocating memory
> > only
> > > on the first exchange future init on local join occurs on node. Also,
> > seems
> > > like we are allocating only the first chunk of memory (not the whole
> > bunch)
> > > and it calculates as:
> > >
> > > Math.max((maxSize - startSize) / (SEG_CNT - 1), 256L * 1024 * 1024)
> > >
> > > But, I'm agree with Val. It's better to allocate memory only when when
> > > the first cache assigned to this region.
> > >
> > >
> > >
> > > Also, It seems like we have some problem with user notification about
> > > available
> > > physical resources. For client nodes method requiredOffheap() returns
> > > always
> > > zero [1]. That's why WARN message shown here [2] would be not not quite
> > > right
> > > if we have a lot of client nodes in cluster.
> > >
> > >
> > > [1]
> > >
> > >
> >
> https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/managers/discovery/GridDiscoveryManager.java#L1501
> > > [2]
> > >
> > >
> >
> https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/IgniteKernal.java#L1489
> > >
> > > сб, 21 июл. 2018 г. в 14:15, Dmitriy Setrakyan  >:
> > >
> > > > On Sat, Jul 21, 2018 at 5:22 AM, Valentin Kulichenko <
> > > > valentin.kuliche...@gmail.com> wrote:
> > > >
> > > > > Actually, I would go even further: only allocate a data region on a
> > > node
> > > > > when the first cache assigned to this region is deployed on that
> > node.
> > > > > Because issue is broader than client nodes and local caches. One
> can
> > > have
> > > > > server nodes without any caches as well - running only services,
> for
> > > > > example.
> > > > >
> > > >
> > > > It would be great if this was possible, but to my knowledge, regions
> > need
> > > > to be allocated on startup.
> > > >
> > > > Alexey Goncharuk, do you have any suggestions on this?
> > > >
> > > > D.
> > > >
> > > --
> > > --
> > > Maxim Muzafarov
> > >
> >
> --
> --
> Maxim Muzafarov
>


Re: Deprecating LOCAL cache

2018-07-27 Thread Dmitry Pavlov
Hi Dmitriy,

I would like to stress this: I'm not saying local cache it useless. I'm
supposing it is not used widely. I want to figure out if I'm mistaking.

All folks involved into user list says it is not used, so why not to
deprecate? If we make a mistake, somebody will come to user list and say,
'Hey, why did you deprecate this, it is used for... in my project'

Being very experienced Igniter you probably know real life usage examples.
And I appreciate if you or somebody else in community could share it.

Sincerely,
Dmitriy Pavlov

пт, 27 июл. 2018 г. в 1:04, Dmitriy Setrakyan :

> Guys,
>
> I just want to make sure we are all on the same page. The main use case for
> LOCAL caches is to have a local hash map querable with SQL and
> automatically persisted to a 3rd party DB.
>
> I want to discourage people from saying "nobody needs some feature". None
> of the people in this discussion are users of any features - we are all
> developers of the features. Instead of guessing whether to deprecate
> something or not, I would actually see if it is even worth a discussion.
> How much effort is required to fix the bug found in the LOCAL cache?
>
> D.
>
> On Thu, Jul 26, 2018 at 12:19 PM, Dmitry Pavlov 
> wrote:
>
> > Hi Alexey,
> >
> > There is nothing to be sorry about :) Сommunity appreciates an
> alternative
> > vision, this allows us to make as informed decisions as it possible.
> >
> > Thank you for finding this fact, it is very interesting.
> >
> > I'm not sure all these examples were prepared by experienced Ignite
> users.
> > So idea of deprecation may have one more argument. Deprecation will help
> us
> > to inform users about LOCAL cache: Probably local cache is not what they
> > need.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > чт, 26 июл. 2018 г. в 16:57, Alexey Zinoviev :
> >
> > > Sorry, guys, I'll put my 1 cent
> > >
> > > I'd like this idea  "Implement LOCAL caches as PARTITIONED caches over
> > the
> > > local node."
> > > It make sense for examples/testing in pseudo-distributed mode and so
> far.
> > >
> > > But I think that the deprecation based on user-list mentions is a wrong
> > > way. Please look here
> > > https://github.com/search?q=%22CacheMode.LOCAL%22+%26+ignite=Code
> > > There a lot of hello world examples with LOCAL mode.
> > >
> > > And of course, we can ask about that on user-list, not here, to vote
> for
> > > the deprecation like this.
> > >
> > > 2018-07-26 11:23 GMT+03:00 Vladimir Ozerov :
> > >
> > > > I meant LOCAL + non-LOCAL transactions of course.
> > > >
> > > > On Wed, Jul 25, 2018 at 10:42 PM Dmitriy Setrakyan <
> > > dsetrak...@apache.org>
> > > > wrote:
> > > >
> > > > > Vladimir,
> > > > >
> > > > > Are you suggesting that a user cannot span more than one local
> cache
> > > in a
> > > > > cross cache LOCAL transactions. This is extremely surprising to me,
> > as
> > > it
> > > > > would require almost no effort to support it. As far as mixing the
> > > local
> > > > > caches with distributed caches, then I agree, cross-cache
> > transactions
> > > do
> > > > > not make sense.
> > > > >
> > > > > I am not sure why deprecating local caches has become a pressing
> > > issue. I
> > > > > can see that there are a few bugs, but why not just fix them and
> move
> > > on?
> > > > > Can someone explain why supporting LOCAL caches is such a burden?
> > > > >
> > > > > Having said that, I am not completely opposed to deprecating LOCAL
> > > > caches.
> > > > > I just want to know why.
> > > > >
> > > > > D.
> > > > >
> > > > > On Wed, Jul 25, 2018 at 10:55 AM, Vladimir Ozerov <
> > > voze...@gridgain.com>
> > > > > wrote:
> > > > >
> > > > > > Dima,
> > > > > >
> > > > > > LOCAL cache adds very little value to the product. It doesn't
> > support
> > > > > > cross-cache transactions, consumes a lot of memory, much slower
> > than
> > > > any
> > > > > > widely-used concurrent hash map. Let's go the same way as Java -
> > mark
> > > > > LOCAL
> > > > > > cache as "deprecated for removal", and then remove it in 3

Re: Deprecating LOCAL cache

2018-07-26 Thread Dmitry Pavlov
Hi Alexey,

There is nothing to be sorry about :) Сommunity appreciates an alternative
vision, this allows us to make as informed decisions as it possible.

Thank you for finding this fact, it is very interesting.

I'm not sure all these examples were prepared by experienced Ignite users.
So idea of deprecation may have one more argument. Deprecation will help us
to inform users about LOCAL cache: Probably local cache is not what they
need.

Sincerely,
Dmitriy Pavlov

чт, 26 июл. 2018 г. в 16:57, Alexey Zinoviev :

> Sorry, guys, I'll put my 1 cent
>
> I'd like this idea  "Implement LOCAL caches as PARTITIONED caches over the
> local node."
> It make sense for examples/testing in pseudo-distributed mode and so far.
>
> But I think that the deprecation based on user-list mentions is a wrong
> way. Please look here
> https://github.com/search?q=%22CacheMode.LOCAL%22+%26+ignite=Code
> There a lot of hello world examples with LOCAL mode.
>
> And of course, we can ask about that on user-list, not here, to vote for
> the deprecation like this.
>
> 2018-07-26 11:23 GMT+03:00 Vladimir Ozerov :
>
> > I meant LOCAL + non-LOCAL transactions of course.
> >
> > On Wed, Jul 25, 2018 at 10:42 PM Dmitriy Setrakyan <
> dsetrak...@apache.org>
> > wrote:
> >
> > > Vladimir,
> > >
> > > Are you suggesting that a user cannot span more than one local cache
> in a
> > > cross cache LOCAL transactions. This is extremely surprising to me, as
> it
> > > would require almost no effort to support it. As far as mixing the
> local
> > > caches with distributed caches, then I agree, cross-cache transactions
> do
> > > not make sense.
> > >
> > > I am not sure why deprecating local caches has become a pressing
> issue. I
> > > can see that there are a few bugs, but why not just fix them and move
> on?
> > > Can someone explain why supporting LOCAL caches is such a burden?
> > >
> > > Having said that, I am not completely opposed to deprecating LOCAL
> > caches.
> > > I just want to know why.
> > >
> > > D.
> > >
> > > On Wed, Jul 25, 2018 at 10:55 AM, Vladimir Ozerov <
> voze...@gridgain.com>
> > > wrote:
> > >
> > > > Dima,
> > > >
> > > > LOCAL cache adds very little value to the product. It doesn't support
> > > > cross-cache transactions, consumes a lot of memory, much slower than
> > any
> > > > widely-used concurrent hash map. Let's go the same way as Java - mark
> > > LOCAL
> > > > cache as "deprecated for removal", and then remove it in 3.0.
> > > >
> > > > On Wed, Jul 25, 2018 at 12:10 PM Dmitrii Ryabov <
> somefire...@gmail.com
> > >
> > > > wrote:
> > > >
> > > > > +1 to make LOCAL as filtered PARTITIONED cache. I think it would be
> > > much
> > > > > easier and faster than fixing all bugs.
> > > > >
> > > > > 2018-07-25 11:51 GMT+03:00 Dmitriy Setrakyan <
> dsetrak...@apache.org
> > >:
> > > > >
> > > > > > I would stay away from deprecating such huge pieces as a whole
> > LOCAL
> > > > > cache.
> > > > > > In retrospect, we should probably not even have LOCAL caches, but
> > > now I
> > > > > am
> > > > > > certain that it is used by many users.
> > > > > >
> > > > > > I would do one of the following, whichever one is easier:
> > > > > >
> > > > > >- Fix the issues found with LOCAL caches, including
> persistence
> > > > > support
> > > > > >- Implement LOCAL caches as PARTITIONED caches over the local
> > > node.
> > > > In
> > > > > >this case, we would have to hide any distribution-related
> config
> > > > from
> > > > > >users, like affinity function, for example.
> > > > > >
> > > > > > D.
> > > > > >
> > > > > > On Wed, Jul 25, 2018 at 9:05 AM, Valentin Kulichenko <
> > > > > > valentin.kuliche...@gmail.com> wrote:
> > > > > >
> > > > > > > It sounds like the main drawback of LOCAL cache is that it's
> > > > > implemented
> > > > > > > separately and therefore has to be maintained separately. If
> > that's
> > > > the
> > > > > > > only issue, why not keep LOCAL cache mode on public API, but
> > > > implement
> > > > > it
> > > > > > > as a PARTITIONED cache with a node filter forcefully set?
> That's
> > > > > similar
> > > > > > to
> > > > > > > what we do with REPLICATED caches which are actually
> PARTITIONED
> > > with
> > > > > > > infinite number of backups.
> > > > > > >
> > > > > > > This way we fix the issues described by Stan and don't have to
> > > > > deprecate
> > > > > > > anything.
> > > > > > >
> > > > > > > -Val
> > > > > > >
> > > > > > > On Wed, Jul 25, 2018 at 12:53 AM Stanislav Lukyanov <
> > > > > > > stanlukya...@gmail.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Hi Igniters,
> > > > > > > >
> > > > > > > > I’d like to start a discussion about the deprecation of the
> > LOCAL
> > > > > > caches.
> > > > > > > >
> > > > > > > > LOCAL caches are an edge-case functionality
> > > > > > > > I haven’t done any formal analysis, but from my experience
> > LOCAL
> > > > > caches
> > > > > > > > are needed very rarely, if ever.
> > > > > > > > I think most usages of LOCAL 

Re: iep-6 metrics ticket review

2018-07-26 Thread Dmitry Pavlov
Hi Ilya,

We all agreed change is good, but we'd like to be absolutely sure there is
no performance drop. Dmitriy G. was one from reviewer, so I hope he would
provide any additional info about change.

Could you please assist here?

Sincerely,
Dmitriy Pavlov

чт, 26 июл. 2018 г. в 18:25, Aleksey Kuznetsov :

> Hi, Igniters!
>
> I have the ticket [1] reviewed, it introduce large changes to cache.
>
> How can I assure it causes no performance drop ?
>
> [1] : https://issues.apache.org/jira/browse/IGNITE-6846
>
> ср, 11 апр. 2018 г. в 3:32, Valentin Kulichenko <
> valentin.kuliche...@gmail.com>:
>
> > This is on my plate, will try to take a look this week.
> >
> > -Val
> >
> > On Mon, Apr 9, 2018 at 10:28 AM, Denis Magda  wrote:
> >
> > > Val,
> > >
> > > As an initial reviewer and reporter, could you have a look and sign the
> > > contribution off?
> > >
> > > --
> > > Denis
> > >
> > > On Mon, Apr 9, 2018 at 12:56 AM, Aleksey Kuznetsov <
> > > alkuznetsov...@gmail.com
> > > > wrote:
> > >
> > > > Hi ,Igniters!
> > > >
> > > > Do we still need this ticket, about invoke metrics : [1] ?
> > > >
> > > > If yes, than could somebody review it ?
> > > >
> > > > If no, should we close this ticket ?
> > > >
> > > > [1] : https://issues.apache.org/jira/browse/IGNITE-6846
> > > > --
> > > >
> > > > *Best Regards,*
> > > >
> > > > *Kuznetsov Aleksey*
> > > >
> > >
> >
>


Re: [MTCGA]: new failures in builds [1532575] needs to be handled

2018-07-26 Thread Dmitry Pavlov
Hi Sergey, thank you. I hope community members will pick up this issue.

чт, 26 июл. 2018 г. в 14:21, Sergey Chugunov :

> No functionality was broken, the problem is in the test itself. I created a
> ticket [1] to fix it and going to mute it on TC.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-9087
>
> On Wed, Jul 25, 2018 at 8:42 PM Sergey Chugunov  >
> wrote:
>
> > I'll take a look at this test as I'm an author of it.
> >
> > On Wed, Jul 25, 2018 at 6:56 PM  wrote:
> >
> >> Hi Ignite Developer,
> >>
> >> I am MTCGA.Bot, and I've detected some issue on TeamCity to be
> addressed.
> >> I hope you can help.
> >>
> >>  *New test failure in master
> >>
> IgniteCacheClientReconnectTest.testClientInForceServerModeStopsOnExchangeHistoryExhaustion
> >>
> >>
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=2977382929811006222=%3Cdefault%3E=testDetails
> >>  Changes may led to failure were done by
> >>  - somefireone
> >>
> http://ci.ignite.apache.org/viewModification.html?modId=826273=false
> >>  - vinokurov.pasha
> >>
> http://ci.ignite.apache.org/viewModification.html?modId=826253=false
> >>  - dmitriy.govorukhin
> >>
> http://ci.ignite.apache.org/viewModification.html?modId=826250=false
> >>  - kaa.dev
> >>
> http://ci.ignite.apache.org/viewModification.html?modId=826246=false
> >>  - vanen31
> >>
> http://ci.ignite.apache.org/viewModification.html?modId=826242=false
> >>  - garus.d.g
> >>
> http://ci.ignite.apache.org/viewModification.html?modId=826234=false
> >>  - ivandasch
> >>
> http://ci.ignite.apache.org/viewModification.html?modId=826229=false
> >>  - av
> >>
> http://ci.ignite.apache.org/viewModification.html?modId=826218=false
> >>  - estanilovskiy
> >>
> http://ci.ignite.apache.org/viewModification.html?modId=826197=false
> >>  - dmitriy.govorukhin
> >>
> http://ci.ignite.apache.org/viewModification.html?modId=826195=false
> >>
> >> - If your changes can led to this failure(s), please create
> issue
> >> with label MakeTeamCityGreenAgain and assign it to you.
> >> -- If you have fix, please set ticket to PA state and write to
> >> dev list fix is ready
> >> -- For case fix will require some time please mute test and set
> >> label Muted_Test to issue
> >> - If you know which change caused failure please contact change
> >> author directly
> >> - If you don't know which change caused failure please send
> >> message to dev list to find out
> >> Should you have any questions please contact dpav...@apache.org or
> write
> >> to dev.list
> >> Best Regards,
> >> MTCGA.Bot
> >> Notification generated at Wed Jul 25 18:02:09 MSK 2018
> >>
> >
>


Re: Need review IGNITE-9050

2018-07-25 Thread Dmitry Pavlov
Hi, Igniters, especially Native Persistence Experts, please step in.

Tests are still running, so I suggest to avoid merge until we'll get
run-all results.

Sincerely,
Dmitriy Pavlov

ср, 25 июл. 2018 г. в 16:24, Dmitriy Govorukhin <
dmitriy.govoruk...@gmail.com>:

> Igniters,
>
> I completed work on
> IGNITE-9050 
> (WALIterator
> should throw an exception if iterator stopped in the WAL archive but not in
> WAL work).
>
> review link - CR-697
> 
>


Re: Data regions on client nodes

2018-07-25 Thread Dmitry Pavlov
Hi Maxim,

thank you for stepping in. How do you think, is it possible to check cache
assignment to region at stage of memory allocation?

Sincerely,
Dmitriy Pavlov

ср, 25 июл. 2018 г. в 18:22, Maxim Muzafarov :

> Folks,
>
> I've checked memory allocation. It looks like we are allocating memory only
> on the first exchange future init on local join occurs on node. Also, seems
> like we are allocating only the first chunk of memory (not the whole bunch)
> and it calculates as:
>
> Math.max((maxSize - startSize) / (SEG_CNT - 1), 256L * 1024 * 1024)
>
> But, I'm agree with Val. It's better to allocate memory only when when
> the first cache assigned to this region.
>
>
>
> Also, It seems like we have some problem with user notification about
> available
> physical resources. For client nodes method requiredOffheap() returns
> always
> zero [1]. That's why WARN message shown here [2] would be not not quite
> right
> if we have a lot of client nodes in cluster.
>
>
> [1]
>
> https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/managers/discovery/GridDiscoveryManager.java#L1501
> [2]
>
> https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/IgniteKernal.java#L1489
>
> сб, 21 июл. 2018 г. в 14:15, Dmitriy Setrakyan :
>
> > On Sat, Jul 21, 2018 at 5:22 AM, Valentin Kulichenko <
> > valentin.kuliche...@gmail.com> wrote:
> >
> > > Actually, I would go even further: only allocate a data region on a
> node
> > > when the first cache assigned to this region is deployed on that node.
> > > Because issue is broader than client nodes and local caches. One can
> have
> > > server nodes without any caches as well - running only services, for
> > > example.
> > >
> >
> > It would be great if this was possible, but to my knowledge, regions need
> > to be allocated on startup.
> >
> > Alexey Goncharuk, do you have any suggestions on this?
> >
> > D.
> >
> --
> --
> Maxim Muzafarov
>


Re: Deprecating LOCAL cache

2018-07-25 Thread Dmitry Pavlov
Hi Igniters,

I've never seen the LOCAL cache in the user list for 1 year. I've tried to
search in archives and found only that mention
http://apache-ignite-users.70518.x6.nabble.com/LOCAL-cache-and-EntryProcessor-td7419.html
in
2016.

Who can provide any additional usage examples?

My vote goes to deprecate until it is not clear for everyone, that LOCAL
cache is widely used feature.

Sincerely,
Dmitriy Pavlov

ср, 25 июл. 2018 г. в 12:10, Dmitrii Ryabov :

> +1 to make LOCAL as filtered PARTITIONED cache. I think it would be much
> easier and faster than fixing all bugs.
>
> 2018-07-25 11:51 GMT+03:00 Dmitriy Setrakyan :
>
> > I would stay away from deprecating such huge pieces as a whole LOCAL
> cache.
> > In retrospect, we should probably not even have LOCAL caches, but now I
> am
> > certain that it is used by many users.
> >
> > I would do one of the following, whichever one is easier:
> >
> >- Fix the issues found with LOCAL caches, including persistence
> support
> >- Implement LOCAL caches as PARTITIONED caches over the local node. In
> >this case, we would have to hide any distribution-related config from
> >users, like affinity function, for example.
> >
> > D.
> >
> > On Wed, Jul 25, 2018 at 9:05 AM, Valentin Kulichenko <
> > valentin.kuliche...@gmail.com> wrote:
> >
> > > It sounds like the main drawback of LOCAL cache is that it's
> implemented
> > > separately and therefore has to be maintained separately. If that's the
> > > only issue, why not keep LOCAL cache mode on public API, but implement
> it
> > > as a PARTITIONED cache with a node filter forcefully set? That's
> similar
> > to
> > > what we do with REPLICATED caches which are actually PARTITIONED with
> > > infinite number of backups.
> > >
> > > This way we fix the issues described by Stan and don't have to
> deprecate
> > > anything.
> > >
> > > -Val
> > >
> > > On Wed, Jul 25, 2018 at 12:53 AM Stanislav Lukyanov <
> > > stanlukya...@gmail.com>
> > > wrote:
> > >
> > > > Hi Igniters,
> > > >
> > > > I’d like to start a discussion about the deprecation of the LOCAL
> > caches.
> > > >
> > > > LOCAL caches are an edge-case functionality
> > > > I haven’t done any formal analysis, but from my experience LOCAL
> caches
> > > > are needed very rarely, if ever.
> > > > I think most usages of LOCAL caches I’ve seen were misuses: the users
> > > > actually needed a simple HashMap, or an actual PARTITIONED cache.
> > > >
> > > > LOCAL caches are easy to implement on top of PARTITIONED
> > > > If one requires a LOCAL cache (which is itself questionable, as
> > discussed
> > > > above) it is quite easy to implement one on top of PARTITIONED cache.
> > > > A node filter of form `node -> node.id().equals(localNodeId)` is
> > enough
> > > > to make the cache to be stored on the node that created it.
> > > > Locality of access to the cache (i.e. making it unavailable from
> other
> > > > nodes) can be achieved on the application level.
> > > >
> > > > LOCAL caches are hard to maintain
> > > > A quick look at the open issues mentioning “local cache” suggests
> that
> > > > this is a corner case for implementation of many Ignite features:
> > > >
> > > > https://issues.apache.org/jira/issues/?jql=text%20~%20%
> > > 22local%20cache%22%20and%20%20project%20%3D%20IGNITE%
> > > 20and%20status%20%3D%20open
> > > > In particular, a recent SO question brought up the fact that LOCAL
> > caches
> > > > don’t support native persistence:
> > > >
> > > > https://stackoverflow.com/questions/51511892/how-to-
> > > configure-persistent-storage-for-apache-ignite-cache
> > > > Having to ask ourselves “how does it play with LOCAL caches” every
> time
> > > we
> > > > write any code in Ignite seems way to much for the benefits we gain
> > from
> > > it.
> > > >
> > > > Proposal
> > > > Let’s deprecate LOCAL caches in 2.x and remove them in 3.0.
> > > > As a part of deprecation let’s do the following:
> > > > - Put @Deprecated on the CacheMode.LOCAL
> > > > - Print a warning every time a LOCAL cache is created
> > > > - Remove all mentions of LOCAL caches from readme.io, if any, except
> > for
> > > > the page about cache modes
> > > > - On the page about cache modes explain that LOCAL is deprecated and
> > can
> > > > be replaced with a PARTITIONED cache with a node filter
> > > >
> > > > Thanks,
> > > > Stan
> > > >
> > >
> >
>


Re: Documenting Ignite

2018-07-25 Thread Dmitry Pavlov
Hi Artem,

Could you please check if you can edit now.

Sincerely,
Dmitriy Pavlov

ср, 25 июл. 2018 г. в 14:03, Artem Budnikov :

> Hi Dmitry,
>
> I've added a comment to the issue.
>
> My Confluence ID is a.budnikov. Could you please grant me permissions
> required to edit pages. Thanks!
>
>
> Artem
>
> On 24.07.2018 16:58, Dmitry Pavlov wrote:
>
> I've noticed now INFRA asks for feedback from us.
>
> Artem, will you provide feedback on done change in
> https://issues.apache.org/jira/browse/INFRA-16803
>
> вт, 24 июл. 2018 г. в 11:01, Dmitry Pavlov :
>
>> Hi Artem,
>>
>> This is page in Ignite space, so you could do updates. Of course, if you
>> have access to Ignite space in wiki. If not, please sign up and share your
>> wiki login (id).
>>
>> Sincerely,
>> Dmitriy Pavlov
>>
>> вт, 24 июл. 2018 г. в 10:25, Artem Budnikov > >:
>>
>>> Hi everyone,
>>>
>>> Despite what I've been told about INFRA, it responded exceptionally
>>> quickly and added the field :-)
>>>
>>> I think the page describing the process of creating IGNITE issues
>>> <https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-TicketCreation>
>>> needs to be updated to reflect the changes related to documentation
>>> process. Could someone do this?
>>>
>>> Cheers,
>>>
>>> Artem
>>> On 23.07.2018 18:00, Artem Budnikov wrote:
>>>
>>> Hi everyone,
>>>
>>> I created an issue in the Apache INFRA project:
>>> https://issues.apache.org/jira/browse/INFRA-16803
>>>
>>> Cheers,
>>>
>>> Artem
>>>
>>>
>>> On 19.07.2018 22:58, Dmitry Pavlov wrote:
>>>
>>> I appologize, initially I misundersood proposal. I've concluded that new
>>> doc issue will be created automatically by closing original ticket, -
>>> this
>>> can be done by plugin only.
>>>
>>> If we just introduce flag or combobox for indicate doc is required,
>>> there
>>> is no technical issues, it is defenetely possible. So +1 from my side
>>> without concerns.
>>>
>>> чт, 19 июл. 2018 г. в 22:02, Denis Magda 
>>> :
>>>
>>> Ok, if all our doc writers are in the agreement then let's give a couple
>>> of
>>> days to our fellow Igniters to share alternate opinions.
>>>
>>> Artem, if you don't hear back by Monday then feel free to create an
>>> INFRA
>>> ticket.
>>>
>>> --
>>> Denis
>>>
>>> On Thu, Jul 19, 2018 at 10:43 AM Prachi Garg 
>>>  wrote:
>>>
>>> I totally agree with Denis's point -
>>>
>>> "Another benefit of having "Docs Required" flag enabled by default, is
>>>
>>> that
>>>
>>> Artem and Prachi can see all such tickets months and weeks before a
>>> release, figure out details from source code contributors and complete
>>>
>>> the
>>>
>>> docs in advance."
>>>
>>> On Wed, Jul 18, 2018 at 2:49 PM, Dmitry Pavlov 
>>> 
>>> wrote:
>>>
>>> Yes, I agree. My concern is related only to process implementation
>>>
>>> aspect,
>>>
>>> I wonder if it is technically possible.
>>>
>>> Generally I like idea of automatic control.
>>>
>>> ср, 18 июл. 2018 г. в 23:21, Denis Magda 
>>> :
>>>
>>> Hi folks,
>>>
>>> Artem's proposal might simplify and make our doc tickets tracking less
>>> error-prone. The current approach implies that a contributor keeps in
>>>
>>> mind
>>>
>>> what needs to go to the docs. If he/she has a good memory, a doc JIRA
>>> counterpart will be created once the contribution is accepted. But the
>>> practice shows that the memory lets us down :)
>>>
>>> Another benefit of having "Docs Required" flag enabled by default, is
>>>
>>> that
>>>
>>> Artem and Prachi can see all such tickets months and weeks before a
>>> release, figure out details from source code contributors and complete
>>>
>>> the
>>>
>>> docs in advance.
>>>
>>> --
>>> Denis
>>>
>>> On Wed, Jul 18, 2018 at 8:39 AM Artem Budnikov <
>>> a.budnikov.ign...@gmail.com> wrote:
>>>
>>> Dmitry,
>>>
>>> The goal I had in mind by pro

Re: [MTCGA]: new failures in builds [1532044] needs to be handled

2018-07-24 Thread Dmitry Pavlov
Great, thanks! I hope all TC failures would be fixed as fast as this one.

вт, 24 июл. 2018 г. в 17:41, Alexey Goncharuk :

> Thanks, merged to master.
>
> вт, 24 июл. 2018 г. в 16:28, Anton Vinogradov :
>
>> Seems, it works.
>> Cancelled hanged suites, they hangs because of problems fixed at master.
>>
>> вт, 24 июл. 2018 г. в 15:20, Anton Vinogradov :
>>
>> > Started more [1] Data Structures tasks to make sure fix works.
>> >
>> > [1]
>> >
>> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_DataStructures_IgniteTests24Java8=pull%2F4415%2Fhead=buildTypeStatusDiv
>> >
>> > вт, 24 июл. 2018 г. в 14:59, Alexey Goncharuk <
>> alexey.goncha...@gmail.com
>> > >:
>> >
>> >> I will merge the fix once the TC passes for the new PR.
>> >>
>> >> вт, 24 июл. 2018 г. в 13:13, Andrey Mashenkov <
>> andrey.mashen...@gmail.com
>> >> >:
>> >>
>> >> > Hi Dmitry,
>> >> >
>> >> > Looks like DataStructure sute timeouts is caused by IGNITE-8892 fix
>> [1].
>> >> > The issue here is IgniteSetImpl uses internal CacheQueryFuture in
>> wrong
>> >> > way.
>> >> >
>> >> > I've already run PR branch with a fix on TC and it looks fine [2].
>> >> >
>> >> > [1] issues.apache.org/jira/browse/IGNITE-8892
>> >> > [2]
>> >> >
>> >> >
>> >>
>> https://ci.ignite.apache.org/viewLog.html?buildId=1534153=queuedBuildOverviewTab
>> >> >
>> >> > On Tue, Jul 24, 2018 at 12:53 PM Dmitry Pavlov <
>> dpavlov@gmail.com>
>> >> > wrote:
>> >> >
>> >> > > Hi Igniters,
>> >> > >
>> >> > > Test caused suite timeout 3 times in a row
>> >> > > ⚠ IgniteDataStructureWithJobTest.testJobWithRestart (last started)
>> >> > > ⚠ IgniteDataStructureWithJobTest.testJobWithRestart (last started)
>> >> > > ⚠ IgniteDataStructureWithJobTest.testJobWithRestart (last started)
>> >> > > History -
>> >> > >
>> >> > >
>> >> >
>> >>
>> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_DataStructures=%3Cdefault%3E=buildTypeStatusDiv
>> >> > >
>> >> > > Could it be related to IGNITE-8783 change?
>> >> > >
>> >> > > Test seems to be waiting for all job responses from worker nodes
>> >> before
>> >> > > stopping grid.
>> >> > >
>> >> > > Anton, please step in.
>> >> > >
>> >> > > Sincerely,
>> >> > > Dmitriy Pavlov
>> >> > >
>> >> > > вт, 24 июл. 2018 г. в 3:17, :
>> >> > >
>> >> > > > Hi Ignite Developer,
>> >> > > >
>> >> > > > I am MTCGA.Bot, and I've detected some issue on TeamCity to be
>> >> > addressed.
>> >> > > > I hope you can help.
>> >> > > >
>> >> > > >  *New Critical Failure in master Data Structures
>> >> > > >
>> >> > >
>> >> >
>> >>
>> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_DataStructures=%3Cdefault%3E=buildTypeStatusDiv
>> >> > > >  Changes may led to failure were done by
>> >> > > >  - somefireone
>> >> > > >
>> >> > >
>> >> >
>> >>
>> http://ci.ignite.apache.org/viewModification.html?modId=826273=false
>> >> > > >  - vinokurov.pasha
>> >> > > >
>> >> > >
>> >> >
>> >>
>> http://ci.ignite.apache.org/viewModification.html?modId=826253=false
>> >> > > >  - dmitriy.govorukhin
>> >> > > >
>> >> > >
>> >> >
>> >>
>> http://ci.ignite.apache.org/viewModification.html?modId=826250=false
>> >> > > >  - kaa.dev
>> >> > > >
>> >> > >
>> >> >
>> >>
>> http://ci.ignite.apache.org/viewModification.html?modId=826246=false
>> >> > > >  - vanen31
>> >> > > >
>> >> > >
>> >

Re: Documenting Ignite

2018-07-24 Thread Dmitry Pavlov
I've noticed now INFRA asks for feedback from us.

Artem, will you provide feedback on done change in
https://issues.apache.org/jira/browse/INFRA-16803

вт, 24 июл. 2018 г. в 11:01, Dmitry Pavlov :

> Hi Artem,
>
> This is page in Ignite space, so you could do updates. Of course, if you
> have access to Ignite space in wiki. If not, please sign up and share your
> wiki login (id).
>
> Sincerely,
> Dmitriy Pavlov
>
> вт, 24 июл. 2018 г. в 10:25, Artem Budnikov :
>
>> Hi everyone,
>>
>> Despite what I've been told about INFRA, it responded exceptionally
>> quickly and added the field :-)
>>
>> I think the page describing the process of creating IGNITE issues
>> <https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-TicketCreation>
>> needs to be updated to reflect the changes related to documentation
>> process. Could someone do this?
>>
>> Cheers,
>>
>> Artem
>> On 23.07.2018 18:00, Artem Budnikov wrote:
>>
>> Hi everyone,
>>
>> I created an issue in the Apache INFRA project:
>> https://issues.apache.org/jira/browse/INFRA-16803
>>
>> Cheers,
>>
>> Artem
>>
>>
>> On 19.07.2018 22:58, Dmitry Pavlov wrote:
>>
>> I appologize, initially I misundersood proposal. I've concluded that new
>> doc issue will be created automatically by closing original ticket, -
>> this
>> can be done by plugin only.
>>
>> If we just introduce flag or combobox for indicate doc is required, there
>> is no technical issues, it is defenetely possible. So +1 from my side
>> without concerns.
>>
>> чт, 19 июл. 2018 г. в 22:02, Denis Magda 
>> :
>>
>> Ok, if all our doc writers are in the agreement then let's give a couple
>> of
>> days to our fellow Igniters to share alternate opinions.
>>
>> Artem, if you don't hear back by Monday then feel free to create an INFRA
>> ticket.
>>
>> --
>> Denis
>>
>> On Thu, Jul 19, 2018 at 10:43 AM Prachi Garg 
>>  wrote:
>>
>> I totally agree with Denis's point -
>>
>> "Another benefit of having "Docs Required" flag enabled by default, is
>>
>> that
>>
>> Artem and Prachi can see all such tickets months and weeks before a
>> release, figure out details from source code contributors and complete
>>
>> the
>>
>> docs in advance."
>>
>> On Wed, Jul 18, 2018 at 2:49 PM, Dmitry Pavlov 
>> 
>> wrote:
>>
>> Yes, I agree. My concern is related only to process implementation
>>
>> aspect,
>>
>> I wonder if it is technically possible.
>>
>> Generally I like idea of automatic control.
>>
>> ср, 18 июл. 2018 г. в 23:21, Denis Magda 
>> :
>>
>> Hi folks,
>>
>> Artem's proposal might simplify and make our doc tickets tracking less
>> error-prone. The current approach implies that a contributor keeps in
>>
>> mind
>>
>> what needs to go to the docs. If he/she has a good memory, a doc JIRA
>> counterpart will be created once the contribution is accepted. But the
>> practice shows that the memory lets us down :)
>>
>> Another benefit of having "Docs Required" flag enabled by default, is
>>
>> that
>>
>> Artem and Prachi can see all such tickets months and weeks before a
>> release, figure out details from source code contributors and complete
>>
>> the
>>
>> docs in advance.
>>
>> --
>> Denis
>>
>> On Wed, Jul 18, 2018 at 8:39 AM Artem Budnikov <
>> a.budnikov.ign...@gmail.com> wrote:
>>
>> Dmitry,
>>
>> The goal I had in mind by proposing that suggestion was to rectify
>>
>> the
>>
>> fact that JIRA issues for documentation are created on an ad-hoc
>>
>> basis,
>>
>> and often issues are created when the lack of documentation becomes
>>
>> an
>>
>> issue for somebody. So we need to be more proactive.
>>
>> I think manual tracking of issues is possible but as efficient as the
>> current situation with the docs. Manual tracking will have to be
>>
>> shared
>>
>> between multiple contributors and performed outside of JIRA, which
>>
>> has
>>
>> its own limitation. If you have any suggestions for improvement
>>
>> without
>>
>> creating fields in JIRA, please share your thoughts.
>>
>> If you are concerned that it's not possible to add a field, then we
>> should contact Apache Infra and

Re: Hello

2018-07-24 Thread Dmitry Pavlov
Hi Nikolai,

I've added you to the list of contributors, so you could assign issues to
yourself.

Looking forward to your contributions!

Sincerely,
Dmitriy Pavlov

P.S. Additional references for you that should boost your onboarding.

Please subscribe to both dev and user lists:
https://ignite.apache.org/community/resources.html#mail-lists

Get familiar with Ignite development process described here:
https://cwiki.apache.org/confluence/display/IGNITE/Development+Process

Instructions on how to contribute can be found here:
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute

Project setup in Intellij IDEA:
https://cwiki.apache.org/confluence/display/IGNITE/Project+Setup

вт, 24 июл. 2018 г. в 12:44, Nikolai Kulagin :

> I'm new to Ignite and I would like to join apache ignite development.
>
> My JIRA's login is zzzadruga.
>
> Going to start from IGNITE-9044 and IGNITE-9046


Re: Hello

2018-07-24 Thread Dmitry Pavlov
Sure, I'd be happy to help.

вт, 24 июл. 2018 г. в 12:47, Vyacheslav Daradur :

> Welcome to the community, Nikolai!
>
> Dmitry, could you help with contributor permissions in Jira?
>
> On Tue, Jul 24, 2018 at 12:44 PM Nikolai Kulagin
>  wrote:
> >
> > I'm new to Ignite and I would like to join apache ignite development.
> >
> > My JIRA's login is zzzadruga.
> >
> > Going to start from IGNITE-9044 and IGNITE-9046
>
>
>
> --
> Best Regards, Vyacheslav D.
>


Re: [MTCGA]: new failures in builds [1532044] needs to be handled

2018-07-24 Thread Dmitry Pavlov
Hi Igniters,

Test caused suite timeout 3 times in a row
⚠ IgniteDataStructureWithJobTest.testJobWithRestart (last started)
⚠ IgniteDataStructureWithJobTest.testJobWithRestart (last started)
⚠ IgniteDataStructureWithJobTest.testJobWithRestart (last started)
History -
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_DataStructures=%3Cdefault%3E=buildTypeStatusDiv

Could it be related to IGNITE-8783 change?

Test seems to be waiting for all job responses from worker nodes before
stopping grid.

Anton, please step in.

Sincerely,
Dmitriy Pavlov

вт, 24 июл. 2018 г. в 3:17, :

> Hi Ignite Developer,
>
> I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed.
> I hope you can help.
>
>  *New Critical Failure in master Data Structures
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_DataStructures=%3Cdefault%3E=buildTypeStatusDiv
>  Changes may led to failure were done by
>  - somefireone
> http://ci.ignite.apache.org/viewModification.html?modId=826273=false
>  - vinokurov.pasha
> http://ci.ignite.apache.org/viewModification.html?modId=826253=false
>  - dmitriy.govorukhin
> http://ci.ignite.apache.org/viewModification.html?modId=826250=false
>  - kaa.dev
> http://ci.ignite.apache.org/viewModification.html?modId=826246=false
>  - vanen31
> http://ci.ignite.apache.org/viewModification.html?modId=826242=false
>  - garus.d.g
> http://ci.ignite.apache.org/viewModification.html?modId=826234=false
>  - ivandasch
> http://ci.ignite.apache.org/viewModification.html?modId=826229=false
>  - av
> http://ci.ignite.apache.org/viewModification.html?modId=826218=false
>  - estanilovskiy
> http://ci.ignite.apache.org/viewModification.html?modId=826197=false
>  - dmitriy.govorukhin
> http://ci.ignite.apache.org/viewModification.html?modId=826195=false
>
> - If your changes can led to this failure(s), please create issue
> with label MakeTeamCityGreenAgain and assign it to you.
> -- If you have fix, please set ticket to PA state and write to dev
> list fix is ready
> -- For case fix will require some time please mute test and set
> label Muted_Test to issue
> - If you know which change caused failure please contact change
> author directly
> - If you don't know which change caused failure please send
> message to dev list to find out
> Should you have any questions please contact dpav...@apache.org or write
> to dev.list
> Best Regards,
> MTCGA.Bot
> Notification generated at Tue Jul 24 03:17:09 MSK 2018
>


Re: Documenting Ignite

2018-07-24 Thread Dmitry Pavlov
Hi Artem,

This is page in Ignite space, so you could do updates. Of course, if you
have access to Ignite space in wiki. If not, please sign up and share your
wiki login (id).

Sincerely,
Dmitriy Pavlov

вт, 24 июл. 2018 г. в 10:25, Artem Budnikov :

> Hi everyone,
>
> Despite what I've been told about INFRA, it responded exceptionally
> quickly and added the field :-)
>
> I think the page describing the process of creating IGNITE issues
> <https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-TicketCreation>
> needs to be updated to reflect the changes related to documentation
> process. Could someone do this?
>
> Cheers,
>
> Artem
> On 23.07.2018 18:00, Artem Budnikov wrote:
>
> Hi everyone,
>
> I created an issue in the Apache INFRA project:
> https://issues.apache.org/jira/browse/INFRA-16803
>
> Cheers,
>
> Artem
>
>
> On 19.07.2018 22:58, Dmitry Pavlov wrote:
>
> I appologize, initially I misundersood proposal. I've concluded that new
> doc issue will be created automatically by closing original ticket, - this
> can be done by plugin only.
>
> If we just introduce flag or combobox for indicate doc is required, there
> is no technical issues, it is defenetely possible. So +1 from my side
> without concerns.
>
> чт, 19 июл. 2018 г. в 22:02, Denis Magda 
> :
>
> Ok, if all our doc writers are in the agreement then let's give a couple
> of
> days to our fellow Igniters to share alternate opinions.
>
> Artem, if you don't hear back by Monday then feel free to create an INFRA
> ticket.
>
> --
> Denis
>
> On Thu, Jul 19, 2018 at 10:43 AM Prachi Garg 
>  wrote:
>
> I totally agree with Denis's point -
>
> "Another benefit of having "Docs Required" flag enabled by default, is
>
> that
>
> Artem and Prachi can see all such tickets months and weeks before a
> release, figure out details from source code contributors and complete
>
> the
>
> docs in advance."
>
> On Wed, Jul 18, 2018 at 2:49 PM, Dmitry Pavlov 
> 
> wrote:
>
> Yes, I agree. My concern is related only to process implementation
>
> aspect,
>
> I wonder if it is technically possible.
>
> Generally I like idea of automatic control.
>
> ср, 18 июл. 2018 г. в 23:21, Denis Magda 
> :
>
> Hi folks,
>
> Artem's proposal might simplify and make our doc tickets tracking less
> error-prone. The current approach implies that a contributor keeps in
>
> mind
>
> what needs to go to the docs. If he/she has a good memory, a doc JIRA
> counterpart will be created once the contribution is accepted. But the
> practice shows that the memory lets us down :)
>
> Another benefit of having "Docs Required" flag enabled by default, is
>
> that
>
> Artem and Prachi can see all such tickets months and weeks before a
> release, figure out details from source code contributors and complete
>
> the
>
> docs in advance.
>
> --
> Denis
>
> On Wed, Jul 18, 2018 at 8:39 AM Artem Budnikov <
> a.budnikov.ign...@gmail.com> wrote:
>
> Dmitry,
>
> The goal I had in mind by proposing that suggestion was to rectify
>
> the
>
> fact that JIRA issues for documentation are created on an ad-hoc
>
> basis,
>
> and often issues are created when the lack of documentation becomes
>
> an
>
> issue for somebody. So we need to be more proactive.
>
> I think manual tracking of issues is possible but as efficient as the
> current situation with the docs. Manual tracking will have to be
>
> shared
>
> between multiple contributors and performed outside of JIRA, which
>
> has
>
> its own limitation. If you have any suggestions for improvement
>
> without
>
> creating fields in JIRA, please share your thoughts.
>
> If you are concerned that it's not possible to add a field, then we
> should contact Apache Infra and find out.
>
>
> Best regards,
>
> Artem Budnikov
>
>
> On 18.07.2018 16:14, Dmitry Pavlov wrote:
>
> Hi Artem,
>
> I sometimes receive feedback that Ignite docs has potential for
> improvement, while I found our docs quite intuitive and simple to
> understand. So if experienced tech writer will join community it
>
> could
>
> benefit all of us, and users, of course. So you're very welcome to
>
> the
>
> community!
>
> About idea of fields introduction I guess we will need assistance
>
> of
>
> Apache
>
> Infra team, because Ignite shares JIRA with all other Apache
>
> project.
>
> And
>
> I'm not sure that technical implementation of proposed process is
>
> even
>
> possible without plu

Re: Implementing custom affinity logic

2018-07-23 Thread Dmitry Pavlov
Hi,

 In case these questions are not related to some PR/Issue or contribution,
than user list probably is better place to ask these questions.

Sincerely,
Dmitriy Pavlov

пн, 23 июл. 2018 г. в 13:24, kotamrajuyashasvi :

> Hi
>
> I m working on an ignite project where I want to have certain records to be
> collocated based
> on a custom calculated value which is obtained from the fields of the
> primary key object.
>
> For example the Primary key pojos have fields a,b,c. I want all records
> having same value of (a+b)/c
> collocated on same node/partition.
>
> I have gone through the ignite documentation and found that custom
> AffinityKeyMapper is the
> one that can be used. Also there is an option to use custom Affinity
> function but extra logic has to be added for partition to node mapping
> etc..
>
> 1. How can I achieve my above requirement? What are the correct options and
> where can
> I get a working example of custom AffinityKeyMapper or AffinityFunction
> ?
>
> 2. Once after achieving custom affinity how to test if all records are
> getting collocated as expected. One
> option that I found was to use scan query and scan a particular
> partition and test each record if it
> should actually belong to the scanned partition. But if there are huge
> number of records I'm facing
> OOM while running scan query for a partition. So I would like to know
> how to achieve this/ test to
> confirm for sure the collocation is as expected.
>
> 3. What is the performance impact of using custom affinity logic when
> compared to using no affinity and
> using @AffinityKeyMapped annotation to achieve affinity where the
> scenario is to collocate based on
> a single field.
>
> 4. When using @AffinityKeyMapped or no affinity is used, is
>
>
> org.apache.ignite.internal.processors.cache.GridCacheDefaultAffinityKeyMapper
> is used as default
> AffinityKeyMapper ? or there is any other default module that is used
> for calculating affinity ?
>
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>


Re: Apache Ignite 2.7: scope, time and release manager

2018-07-23 Thread Dmitry Pavlov
Hi Denis, Nikolay,

I've issued a number of tickets to update dependencies versions. I would
like all these updates are available within 2.7.

Sincerely,
Dmitriy Pavlov

сб, 21 июл. 2018 г. в 3:28, Pavel Petroshenko :

> Hi Denis, Nikolay,
>
> The proposed 2.7 release timing sounds reasonable to me.
> Python [1], PHP [2], and Node.js [3] thin clients should take the train.
>
> p.
>
> [1] https://jira.apache.org/jira/browse/IGNITE-7782
> [2] https://jira.apache.org/jira/browse/IGNITE-7783
> [3] https://jira.apache.org/jira/browse/IGNITE-
>
>
> On Fri, Jul 20, 2018 at 2:35 PM, Denis Magda  wrote:
>
> > Igniters,
> >
> > Let's agree on the time and the scope of 2.7. As for the release manager,
> > we had a conversation with Nikolay Izhikov and he decided to try the role
> > out. Thanks, Nikolay!
> >
> > Nikolay, we need to prepare a page like that [1] once the release terms
> are
> > defined.
> >
> > I propose us to roll Ignite 2.7 at the end of September. Folks who are
> > working on SQL, core, C++/NET, thin clients, ML, service grid
> > optimizations, data structures please enlist what you're ready to
> deliver.
> >
> >
> > [1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.6
> >
>


Re: Code duplicates in ssh tests

2018-07-20 Thread Dmitry Pavlov
Ok, I agree here, that we can remove one test. Feel free to create an issue
and PR if nobody else mind. Let us wait at least until Mon 23 Jul before
merge.

пт, 20 июл. 2018 г. в 17:57, Иван Федотов :

> Hi, Dmitry.
>
> I thought about elements order, but if we go deeper in
> ignite.cluster().stopNodes() method, we can see that in ClusterIgniteImpl
> [1] all nodes id will be collected in HashSet in forNodesIds method [2].
>
> So I think that in this case it's not important what use initially, HashSet
>  or ArrayList.
>
> [1]
>
> https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/cluster/IgniteClusterImpl.java#L250
> [2]
>
> https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/cluster/ClusterGroupAdapter.java#L454
>
>
> 2018-07-20 16:52 GMT+03:00 Dmitry Pavlov :
>
> > Hi Ivan,
> >
> > I can suppose that it is related to elements order. Is it reasonable to
> > keep 2 tests with 1 common mehod? One test will call this method with
> > HashSet, and other with ArrayList.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > пт, 20 июл. 2018 г. в 15:01, Иван Федотов :
> >
> > > Hi, Igniters!
> > >
> > > I’m working on ssh module and found some code duplicates in
> > > IgniteProjectionStartStopRestartSelfTest.
> > >
> > > 1. Tests testRestartNodesByIds and testRestartNodesByIdsC are fully
> > > duplicate themself [1]. I tried to found what differences should they
> > have
> > > and looked at similar tests: testStopNodesByIds and testStopNodesByIdsC
> > > [2]. It relates to the second point.
> > >
> > > 2. The only difference is that in testStopNodesByIds we stop nodes by
> > > passing HashSet of Ids and in testStopNodesByIdsC we stop by passing
> > > ArrayList of Ids. In my opinion it does not matter, because stopNodes
> > > methods have Collection as argument and we can pass to it both HashSet
> > and
> > > ArrayList. So, I think that code in these tests are also duplicate each
> > > other.
> > >
> > > What do you think? Can we remove one of these tests in both cases?
> > >
> > >
> > > [1]
> > >
> > > https://github.com/apache/ignite/blob/master/modules/
> > ssh/src/test/java/org/apache/ignite/internal/
> > IgniteProjectionStartStopRestartSelfTest.java#L878
> > >
> > > [2]
> > >
> > > https://github.com/apache/ignite/blob/master/modules/
> > ssh/src/test/java/org/apache/ignite/internal/
> > IgniteProjectionStartStopRestartSelfTest.java#L659
> > >
> > >
> > > --
> > > Ivan Fedotov.
> > >
> > > ivanan...@gmail.com
> > >
> >
>
>
>
> --
> Ivan Fedotov.
>
> ivanan...@gmail.com
>


Re: Code duplicates in ssh tests

2018-07-20 Thread Dmitry Pavlov
Hi Ivan,

I can suppose that it is related to elements order. Is it reasonable to
keep 2 tests with 1 common mehod? One test will call this method with
HashSet, and other with ArrayList.

Sincerely,
Dmitriy Pavlov

пт, 20 июл. 2018 г. в 15:01, Иван Федотов :

> Hi, Igniters!
>
> I’m working on ssh module and found some code duplicates in
> IgniteProjectionStartStopRestartSelfTest.
>
> 1. Tests testRestartNodesByIds and testRestartNodesByIdsC are fully
> duplicate themself [1]. I tried to found what differences should they have
> and looked at similar tests: testStopNodesByIds and testStopNodesByIdsC
> [2]. It relates to the second point.
>
> 2. The only difference is that in testStopNodesByIds we stop nodes by
> passing HashSet of Ids and in testStopNodesByIdsC we stop by passing
> ArrayList of Ids. In my opinion it does not matter, because stopNodes
> methods have Collection as argument and we can pass to it both HashSet and
> ArrayList. So, I think that code in these tests are also duplicate each
> other.
>
> What do you think? Can we remove one of these tests in both cases?
>
>
> [1]
>
> https://github.com/apache/ignite/blob/master/modules/ssh/src/test/java/org/apache/ignite/internal/IgniteProjectionStartStopRestartSelfTest.java#L878
>
> [2]
>
> https://github.com/apache/ignite/blob/master/modules/ssh/src/test/java/org/apache/ignite/internal/IgniteProjectionStartStopRestartSelfTest.java#L659
>
>
> --
> Ivan Fedotov.
>
> ivanan...@gmail.com
>


Re: Desynchronization of true repo and github repo

2018-07-20 Thread Dmitry Pavlov
Yes, very strange thing, I've also checked this commit in mirror before,
and it is appeared only now. I have no clue about reasons.

пт, 20 июл. 2018 г. в 15:02, Nikolay Izhikov :

> When I'm try to push 8633d34e to master, GitHub repo doesn't contain Yury
> commit.
>
> It appear on GitHub only after my merge and push.
>
> пт, 20 июля 2018 г., 14:53 Dmitry Pavlov :
>
> > Hi Yury,
> >
> > it seems commit has appeared now:
> >
> >
> https://github.com/apache/ignite/commit/26e405281792d38b5505cde22b5c6a91749c4990
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > пт, 20 июл. 2018 г. в 14:02, Yury Babak :
> >
> > > Igniters,
> > >
> > > Few hours ago I pushed the  commit
> > > <
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=commit;h=26e405281792d38b5505cde22b5c6a91749c4990
> > >
> > >
> > > into https://git-wip-us.apache.org/repos/asf/ignite
> > >
> > > But I dont see this commit in github repo, may be we have some problem
> > with
> > > synchronization between those two repos?
> > >
> > > Can someone check it?
> > >
> > > Regards,
> > > Yury
> > >
> > >
> > >
> > > --
> > > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
> > >
> >
>


Re: Desynchronization of true repo and github repo

2018-07-20 Thread Dmitry Pavlov
Hi Yury,

it seems commit has appeared now:
https://github.com/apache/ignite/commit/26e405281792d38b5505cde22b5c6a91749c4990

Sincerely,
Dmitriy Pavlov

пт, 20 июл. 2018 г. в 14:02, Yury Babak :

> Igniters,
>
> Few hours ago I pushed the  commit
> <
> https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=commit;h=26e405281792d38b5505cde22b5c6a91749c4990>
>
> into https://git-wip-us.apache.org/repos/asf/ignite
>
> But I dont see this commit in github repo, may be we have some problem with
> synchronization between those two repos?
>
> Can someone check it?
>
> Regards,
> Yury
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>


Re: GridCacheReplicatedFullApiMultithreadedSelfTest1 not used, not compile. Remove?

2018-07-20 Thread Dmitry Pavlov
Hi Maxim,

I think we should remove such code. And if nobody objects I can apply PR on
Monday.

Ilya, please confirm you're agree.

Sincerely,
Dmitriy Pavlov

пт, 20 июл. 2018 г. в 13:16, Maxim Muzafarov :

> Ignites,
>
> I've faced with test in Ignite code base that is fully commented. You can
> check it
> by yoursefl [1]. As it not used since 2014 and not even compile I'm
> suggesting
> to remove it.
>
> What do you think about it? Please, share your thoughts.
>
> Full name:
>
> org.apache.ignite.internal.processors.cache.distributed.replicated.GridCacheReplicatedFullApiMultithreadedSelfTest1
>
> [1]
>
> https://github.com/apache/ignite/blob/master/modules/core/src/test/java/org/apache/ignite/internal/processors/cache/distributed/replicated/GridCacheReplicatedFullApiMultithreadedSelfTest1.java
> --
> --
> Maxim Muzafarov
>


Fwd: The Apache Ignite Book

2018-07-20 Thread Dmitry Pavlov
Hi Igniters,

We somethimes mention lack of overall view and documentaion about Ignite,
and I guess it could be changed soon.

FYI, please find forwarded message below, and I hope you will have a free
minute to review.

At least I can see free book sample available and I find deep technical
details about the product.

Sincerely,
Dmitriy Pavlov

-- Forwarded message -
From: srecon 
Date: пт, 20 июл. 2018 г. в 11:06
Subject: The Apache Ignite Book
To: 


Dear Igniters,
  we are happy to announce that a free sample chapter of our new title "The
Apache Ignite book" has been published on  leanpub
  . The full table of contents of the book
also available at leanpub.
  This is an agile-published book and the first portion of the book will be
published soon. We want this book to be the perfect guide for the Ignite
users. So, any suggestions, comments, ideas, and critics are welcome.

Best regards
  Shamim



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/


Re: Documenting Ignite

2018-07-19 Thread Dmitry Pavlov
I appologize, initially I misundersood proposal. I've concluded that new
doc issue will be created automatically by closing original ticket, - this
can be done by plugin only.

If we just introduce flag or combobox for indicate doc is required, there
is no technical issues, it is defenetely possible. So +1 from my side
without concerns.

чт, 19 июл. 2018 г. в 22:02, Denis Magda :

> Ok, if all our doc writers are in the agreement then let's give a couple of
> days to our fellow Igniters to share alternate opinions.
>
> Artem, if you don't hear back by Monday then feel free to create an INFRA
> ticket.
>
> --
> Denis
>
> On Thu, Jul 19, 2018 at 10:43 AM Prachi Garg  wrote:
>
> > I totally agree with Denis's point -
> >
> > "Another benefit of having "Docs Required" flag enabled by default, is
> that
> > Artem and Prachi can see all such tickets months and weeks before a
> > release, figure out details from source code contributors and complete
> the
> > docs in advance."
> >
> > On Wed, Jul 18, 2018 at 2:49 PM, Dmitry Pavlov 
> > wrote:
> >
> >> Yes, I agree. My concern is related only to process implementation
> aspect,
> >> I wonder if it is technically possible.
> >>
> >> Generally I like idea of automatic control.
> >>
> >> ср, 18 июл. 2018 г. в 23:21, Denis Magda :
> >>
> >> > Hi folks,
> >> >
> >> > Artem's proposal might simplify and make our doc tickets tracking less
> >> > error-prone. The current approach implies that a contributor keeps in
> >> mind
> >> > what needs to go to the docs. If he/she has a good memory, a doc JIRA
> >> > counterpart will be created once the contribution is accepted. But the
> >> > practice shows that the memory lets us down :)
> >> >
> >> > Another benefit of having "Docs Required" flag enabled by default, is
> >> that
> >> > Artem and Prachi can see all such tickets months and weeks before a
> >> > release, figure out details from source code contributors and complete
> >> the
> >> > docs in advance.
> >> >
> >> > --
> >> > Denis
> >> >
> >> > On Wed, Jul 18, 2018 at 8:39 AM Artem Budnikov <
> >> > a.budnikov.ign...@gmail.com> wrote:
> >> >
> >> >> Dmitry,
> >> >>
> >> >> The goal I had in mind by proposing that suggestion was to rectify
> the
> >> >> fact that JIRA issues for documentation are created on an ad-hoc
> basis,
> >> >> and often issues are created when the lack of documentation becomes
> an
> >> >> issue for somebody. So we need to be more proactive.
> >> >>
> >> >> I think manual tracking of issues is possible but as efficient as the
> >> >> current situation with the docs. Manual tracking will have to be
> shared
> >> >> between multiple contributors and performed outside of JIRA, which
> has
> >> >> its own limitation. If you have any suggestions for improvement
> without
> >> >> creating fields in JIRA, please share your thoughts.
> >> >>
> >> >> If you are concerned that it's not possible to add a field, then we
> >> >> should contact Apache Infra and find out.
> >> >>
> >> >>
> >> >> Best regards,
> >> >>
> >> >> Artem Budnikov
> >> >>
> >> >>
> >> >> On 18.07.2018 16:14, Dmitry Pavlov wrote:
> >> >> > Hi Artem,
> >> >> >
> >> >> > I sometimes receive feedback that Ignite docs has potential for
> >> >> > improvement, while I found our docs quite intuitive and simple to
> >> >> > understand. So if experienced tech writer will join community it
> >> could
> >> >> > benefit all of us, and users, of course. So you're very welcome to
> >> the
> >> >> > community!
> >> >> >
> >> >> > About idea of fields introduction I guess we will need assistance
> of
> >> >> Apache
> >> >> > Infra team, because Ignite shares JIRA with all other Apache
> project.
> >> >> And
> >> >> > I'm not sure that technical implementation of proposed process is
> >> even
> >> >> > possible without plugins. Could we consider some manual processing
> of
> >> >> > co

Re: TC issue. Spring Data build.

2018-07-19 Thread Dmitry Pavlov
Hi Nikolay,

There was an issue in spring data when we were migrating to spring data
2.0. And if you PR is based on old master branch issue can happen.

Is this PR's base quite fresh?

Sincerely,
Dmitriy Pavlov

чт, 19 июл. 2018 г. в 14:32, Nikolay Izhikov :

> Hello, Igniters.
>
> I faced with TC issue for my PR [1]
> Seems like some TC misconfiguration.
> Locally, all runs OK.
>
> AFAIK, other Igniters also gets this error on TC.
>
> Please, help me with TC configuration.
>
>
> https://ci.ignite.apache.org/viewLog.html?buildId=1512664=buildResultsDiv=IgniteTests24Java8_SpringData#testNameId-4044715836195573554
>
> Caused by: org.springframework.beans.BeanInstantiationException: Failed to
> instantiate [org.apache.ignite.Ignite]: Factory method 'igniteInstance'
> threw exception; nested exception is
> java.lang.NoClassDefFoundError: Could not initialize class
> org.apache.ignite.internal.IgniteVersionUtils
> at
> org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:185)
> at
> org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:579)
> ... 61 more
> Caused by: java.lang.NoClassDefFoundError: Could not initialize class
> org.apache.ignite.internal.IgniteVersionUtils
> at
> org.apache.ignite.internal.IgniteKernal.ackAsciiLogo(IgniteKernal.java:1892)
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:843)
>
>
> [1] https://github.com/apache/ignite/pull/4378


Re: Place Ignite Abbrev Plugin to ASF Ignite supplementary git repo

2018-07-19 Thread Dmitry Pavlov
Hi Vyacheslav,

For Abbrev plugin I also thought that ASF git repo as primary and
https://github.com/apacheignite mirror would cover all cases.

Thank you for sharing your vision.

Sincerely,
Dmitriy Pavlov

чт, 19 июл. 2018 г. в 9:08, Vyacheslav Daradur :

> I vote for a separate repo for the Ignite Abbrev Plugin project.
>
> The reason is:
> Ignite Abbrev Plugin - build on top of IntelliJ Platform SDK [1] and
> can't be easily packaged without it, moreover, it doesn't depend on
> Ignite internals (unlike .NET/C++ clients).
>
> One more place where we could place the project (if this repo
> maintained by Ignite's commiters) [2].
>
> [1] http://www.jetbrains.org/intellij/sdk/docs/welcome.html
> [2] https://github.com/apacheignite
> On Thu, Jul 19, 2018 at 12:48 AM Dmitry Pavlov 
> wrote:
> >
> > Hi Denis,
> >
> > This option can be considered also. I have no arguments against this
> > solution.
> >
> > In the same time I think Ignite developer will need pre-build
> distributive
> > (Jar) of plugin, probably in /idea subfolder.
> >
> > So standalone ASF repo & [build/link to build] in main repo can be still
> > considered. This option can save checkout time, and reduce main repo
> size.
> >
> > I hope this make sense. I would appreciate Igniter's opinion on this
> topic.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > ср, 18 июл. 2018 г. в 23:05, Denis Magda :
> >
> > > Hi Dmitriy,
> > >
> > > Yes, I would have this tool at hands soon as I check out Ignite repo
> and
> > > start setting it up. However, instead of a new repo let's place it
> under
> > > {ignite}/dev-tools folder. What do you think?
> > >
> > > --
> > > Denis
> > >
> > > On Wed, Jul 18, 2018 at 4:37 AM Dmitry Pavlov 
> > > wrote:
> > >
> > > > Hi Igniters,
> > > >
> > > > There is one mode widely used tool in Apache Ignite, abbreviation
> plugin
> > > > for Intelli J Idea. This plugin is used by almost all experienced
> Ignite
> > > > contributors.
> > > >
> > > > I would like to say thanks to all contributors which created this
> plugin:
> > > > vkazakov, sevdokimov, daradurvs, agoncharuk. And because this plugin
> is
> > > > also a part of our process I also want to place plugin code to ASF
> > > > repository.
> > > >
> > > > What do you think about placing plugin code to supplementary Apache
> > > > repository? Please share your vision till 24 July.
> > > >
> > > > Sincerely,
> > > > Dmitriy Pavlov
> > > >
> > > >
> > > >
> > >
> https://cwiki.apache.org/confluence/display/IGNITE/Abbreviation+Rules#AbbreviationRules-IntelliJIdeaPlugin
> > > >
> > > >
> > > > https://github.com/dspavlov/ignite-abbrev-plugin
> > > >
> > >
>
>
>
> --
> Best Regards, Vyacheslav D.
>


Re: Place Ignite TC helper to ASF Ignite supplementary git repo

2018-07-19 Thread Dmitry Pavlov
Hi Dmitriy,

Yes, I'm going to create INFRA ticket for new ASF supplementary repository
for project, I just want to be absolutely sure, that Community supports my
plan.

Or do you mean I need to create ticket to find out if domain
mtcga.ignite.apache.org is possible to create?

Sincerely,
Dmitriy Pavlov

чт, 19 июл. 2018 г. в 1:43, Dmitriy Setrakyan :

> Dmitriy,
>
> I think you should file an INFRA ticket and ask if this is possible.
>
> D.
>
> On Wed, Jul 18, 2018 at 3:12 PM, Denis Magda  wrote:
>
> > Dmitriy,
> >
> > Things for clearing the things out. No objections from my side then.
> >
> > Let's see what other Ignite fellows think on your proposal. Someone might
> > have a different perspective.
> >
> > --
> > Denis
> >
> > On Wed, Jul 18, 2018 at 1:58 PM Dmitry Pavlov 
> > wrote:
> >
> > > Hi Denis,
> > >
> > > It will made things simple.
> > >
> > > 1) For example any comitter will be able to change rules of
> notification
> > > and fix the Bot if something goes wrong. Now it is my github repo. ASF
> > repo
> > > will guarantee that code will be always accessible by community
> members.
> > >
> > > 2) Being a part of ASF repo the Bot will be simple thing that less
> > > experienced developer can start with. The Bot uses latest AI release as
> > DB
> > > with persistence enabled, so bot developer became at least Apache
> Ignite
> > > user, and as most - new contributor.
> > >
> > > If we agree to place this bot to ASF, next step could be asking Infra
> > Team
> > > to provide 2nd level apache domain, e.g. mtcga.ignite.apache.org for
> web
> > > UI. I guess it would be plus if our tool code is available in ASF repo,
> > but
> > > not in some private git repo.
> > >
> > > Sincerely,
> > > Dmitriy Pavlov
> > >
> > > ср, 18 июл. 2018 г. в 23:03, Denis Magda :
> > >
> > > > Hi Dmitriy,
> > > >
> > > > The whole year has passed since this initiative launch, hell, the
> times
> > > > passes by :)
> > > >
> > > > What would be the benefits of having the tool in the Apache repo?
> Does
> > it
> > > > simplify the things for us.
> > > >
> > > > --
> > > > Denis
> > > >
> > > > On Wed, Jul 18, 2018 at 3:59 AM Dmitry Pavlov  >
> > > > wrote:
> > > >
> > > > > Hi Igniters,
> > > > >
> > > > > Almost 1 year has passed since Make Teamcity Green Again was
> > initially
> > > > > proposed. During this process we managed to get almost successful
> Run
> > > > Alls
> > > > > in master, but currently regressions still occur. We all tried a
> lot
> > of
> > > > > things: careful examination of PR tests, continuous monitoring of
> > > master,
> > > > > suite responsible contributor, tickets creation and so on.
> > > > >
> > > > > According to Igniter's feedback most productive thing was master
> > > > monitoring
> > > > > and timely fix of new failures. But contributor’s enthusiasm is
> > limited
> > > > and
> > > > > monitoring is not most enjoyable thing, so it's time to automate
> this
> > > > > activity. I’ve created MTCGA.Bot which sends emails about new
> > failures
> > > > and
> > > > > in addition has a couple of useful features.
> > > > >
> > > > > The Bot is being developed only based on your feedback. 30 Ignite
> > > > > developers already tried it. I'm going to run short
> > > webinar/presentation
> > > > at
> > > > > Mon 23 July and tell more about Bot capabilites, so everyone can
> make
> > > an
> > > > > impression.
> > > > >
> > > > > I would like to continue development and I propose to place TC
> Helper
> > > > code
> > > > > to Apache Ignite supplementary repository (same as ignite-release).
> > > What
> > > > do
> > > > > you think about it? Please share your vision till 24 July.
> > > > >
> > > > > Sincerely,
> > > > > Dmitriy Pavlov
> > > > >
> > > > > References:
> > > > >
> > > > >
> > > >
> > > https://cwiki.apache.org/confluence/display/IGNITE/
> > Make+Teamcity+Green+Again#MakeTeamcityGreenAgain-MTCGABot
> > > > >
> > > > > https://github.com/dspavlov/ignite-teamcity-helper
> > > > >
> > > >
> > >
> >
>


Re: Place Ignite TC helper to ASF Ignite supplementary git repo

2018-07-19 Thread Dmitry Pavlov
Hi Vyacheslav,

Thank you for your feedback.

https://github.com/apacheignite will have mirror from ASF repository, as
docs or main repo have.

Sincerely,
Dmitriy Pavlov

чт, 19 июл. 2018 г. в 8:54, Vyacheslav Daradur :

> I vote for a separate repo for the TC helper project.
>
> IMO TC Helper - is an application project and a separate repo is a
> more convenient way to the project developing.
>
> One more place where we could place the project (if the place
> maintained by Ignite's commiters):
> https://github.com/apacheignite
>
> On Thu, Jul 19, 2018 at 1:43 AM Dmitriy Setrakyan 
> wrote:
> >
> > Dmitriy,
> >
> > I think you should file an INFRA ticket and ask if this is possible.
> >
> > D.
> >
> > On Wed, Jul 18, 2018 at 3:12 PM, Denis Magda  wrote:
> >
> > > Dmitriy,
> > >
> > > Things for clearing the things out. No objections from my side then.
> > >
> > > Let's see what other Ignite fellows think on your proposal. Someone
> might
> > > have a different perspective.
> > >
> > > --
> > > Denis
> > >
> > > On Wed, Jul 18, 2018 at 1:58 PM Dmitry Pavlov 
> > > wrote:
> > >
> > > > Hi Denis,
> > > >
> > > > It will made things simple.
> > > >
> > > > 1) For example any comitter will be able to change rules of
> notification
> > > > and fix the Bot if something goes wrong. Now it is my github repo.
> ASF
> > > repo
> > > > will guarantee that code will be always accessible by community
> members.
> > > >
> > > > 2) Being a part of ASF repo the Bot will be simple thing that less
> > > > experienced developer can start with. The Bot uses latest AI release
> as
> > > DB
> > > > with persistence enabled, so bot developer became at least Apache
> Ignite
> > > > user, and as most - new contributor.
> > > >
> > > > If we agree to place this bot to ASF, next step could be asking Infra
> > > Team
> > > > to provide 2nd level apache domain, e.g. mtcga.ignite.apache.org
> for web
> > > > UI. I guess it would be plus if our tool code is available in ASF
> repo,
> > > but
> > > > not in some private git repo.
> > > >
> > > > Sincerely,
> > > > Dmitriy Pavlov
> > > >
> > > > ср, 18 июл. 2018 г. в 23:03, Denis Magda :
> > > >
> > > > > Hi Dmitriy,
> > > > >
> > > > > The whole year has passed since this initiative launch, hell, the
> times
> > > > > passes by :)
> > > > >
> > > > > What would be the benefits of having the tool in the Apache repo?
> Does
> > > it
> > > > > simplify the things for us.
> > > > >
> > > > > --
> > > > > Denis
> > > > >
> > > > > On Wed, Jul 18, 2018 at 3:59 AM Dmitry Pavlov <
> dpavlov@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Hi Igniters,
> > > > > >
> > > > > > Almost 1 year has passed since Make Teamcity Green Again was
> > > initially
> > > > > > proposed. During this process we managed to get almost
> successful Run
> > > > > Alls
> > > > > > in master, but currently regressions still occur. We all tried a
> lot
> > > of
> > > > > > things: careful examination of PR tests, continuous monitoring of
> > > > master,
> > > > > > suite responsible contributor, tickets creation and so on.
> > > > > >
> > > > > > According to Igniter's feedback most productive thing was master
> > > > > monitoring
> > > > > > and timely fix of new failures. But contributor’s enthusiasm is
> > > limited
> > > > > and
> > > > > > monitoring is not most enjoyable thing, so it's time to automate
> this
> > > > > > activity. I’ve created MTCGA.Bot which sends emails about new
> > > failures
> > > > > and
> > > > > > in addition has a couple of useful features.
> > > > > >
> > > > > > The Bot is being developed only based on your feedback. 30 Ignite
> > > > > > developers already tried it. I'm going to run short
> > > > webinar/presentation
> > > > > at
> > > > > > Mon 23 July and tell more about Bot capabilites, so everyone can
> make
> > > > an
> > > > > > impression.
> > > > > >
> > > > > > I would like to continue development and I propose to place TC
> Helper
> > > > > code
> > > > > > to Apache Ignite supplementary repository (same as
> ignite-release).
> > > > What
> > > > > do
> > > > > > you think about it? Please share your vision till 24 July.
> > > > > >
> > > > > > Sincerely,
> > > > > > Dmitriy Pavlov
> > > > > >
> > > > > > References:
> > > > > >
> > > > > >
> > > > >
> > > > https://cwiki.apache.org/confluence/display/IGNITE/
> > > Make+Teamcity+Green+Again#MakeTeamcityGreenAgain-MTCGABot
> > > > > >
> > > > > > https://github.com/dspavlov/ignite-teamcity-helper
> > > > > >
> > > > >
> > > >
> > >
>
>
>
> --
> Best Regards, Vyacheslav D.
>


Re: Documenting Ignite

2018-07-18 Thread Dmitry Pavlov
Yes, I agree. My concern is related only to process implementation aspect,
I wonder if it is technically possible.

Generally I like idea of automatic control.

ср, 18 июл. 2018 г. в 23:21, Denis Magda :

> Hi folks,
>
> Artem's proposal might simplify and make our doc tickets tracking less
> error-prone. The current approach implies that a contributor keeps in mind
> what needs to go to the docs. If he/she has a good memory, a doc JIRA
> counterpart will be created once the contribution is accepted. But the
> practice shows that the memory lets us down :)
>
> Another benefit of having "Docs Required" flag enabled by default, is that
> Artem and Prachi can see all such tickets months and weeks before a
> release, figure out details from source code contributors and complete the
> docs in advance.
>
> --
> Denis
>
> On Wed, Jul 18, 2018 at 8:39 AM Artem Budnikov <
> a.budnikov.ign...@gmail.com> wrote:
>
>> Dmitry,
>>
>> The goal I had in mind by proposing that suggestion was to rectify the
>> fact that JIRA issues for documentation are created on an ad-hoc basis,
>> and often issues are created when the lack of documentation becomes an
>> issue for somebody. So we need to be more proactive.
>>
>> I think manual tracking of issues is possible but as efficient as the
>> current situation with the docs. Manual tracking will have to be shared
>> between multiple contributors and performed outside of JIRA, which has
>> its own limitation. If you have any suggestions for improvement without
>> creating fields in JIRA, please share your thoughts.
>>
>> If you are concerned that it's not possible to add a field, then we
>> should contact Apache Infra and find out.
>>
>>
>> Best regards,
>>
>> Artem Budnikov
>>
>>
>> On 18.07.2018 16:14, Dmitry Pavlov wrote:
>> > Hi Artem,
>> >
>> > I sometimes receive feedback that Ignite docs has potential for
>> > improvement, while I found our docs quite intuitive and simple to
>> > understand. So if experienced tech writer will join community it could
>> > benefit all of us, and users, of course. So you're very welcome to the
>> > community!
>> >
>> > About idea of fields introduction I guess we will need assistance of
>> Apache
>> > Infra team, because Ignite shares JIRA with all other Apache project.
>> And
>> > I'm not sure that technical implementation of proposed process is even
>> > possible without plugins. Could we consider some manual processing of
>> > completed issues in relation to doc requrement?
>> >
>> > Sincerely,
>> > Dmitriy Pavlov
>> >
>> > ср, 18 июл. 2018 г. в 15:06, Artem Budnikov <
>> a.budnikov.ign...@gmail.com>:
>> >
>> >> Hi Igniters,
>> >>
>> >> Being a technical writer, I'm going to contribute to Ignite's
>> >> documentation, and I believe documentation is an important part of
>> every
>> >> product, especially such a complex product as Apache Ignite.
>> >>
>> >> I'd like to put forward a suggestion on how to increase our chances of
>> >> making Ignite documentation more comprehensive. The basic idea is to
>> >> have a Jira issue with the Component field set to "Documentation" for
>> >> every feature that needs to be documented. This will ensure that there
>> >> are documentation issues that cover the entire product functionality.
>> >> Then someone can take on an issue and contribute an article on the
>> subject.
>> >>
>> >> This is how I envision it to work technically. A new field (checkbox)
>> is
>> >> added to the Apache Ignite Jira project. The checkbox indicates that
>> the
>> >> feature requested in this issue needs to be documented. The checkbox is
>> >> selected by default. If the feature does not require documentation,
>> then
>> >> the author unchecks the checkbox. If it does require documentation, the
>> >> author creates a related Jira issue selecting "Documentation" in the
>> >> Component field, providing details on what exactly should be
>> documented.
>> >>
>> >> The field is called "Requires documentation" or similarly. It could be
>> >> also useful to create a new issue type for documentation issues
>> >> exclusively.
>> >>
>> >> Once this is done, we'll be able to filter out
>> >>
>> >>   1. issues that do not require documentation,
>> >>   2. issues that have related documentation tickets, and
>> >>   3. issues that require documentation but have no related issues
>> (which
>> >>  means that the author forgot to create a documentation issue for
>> it).
>> >>
>> >>
>> >> Please share your thoughts about this.
>> >>
>> >>
>> >> Best regards,
>> >>
>> >> Artem Budnikov
>> >>
>> >>
>>
>>


Re: Place Ignite Abbrev Plugin to ASF Ignite supplementary git repo

2018-07-18 Thread Dmitry Pavlov
Hi Denis,

This option can be considered also. I have no arguments against this
solution.

In the same time I think Ignite developer will need pre-build distributive
(Jar) of plugin, probably in /idea subfolder.

So standalone ASF repo & [build/link to build] in main repo can be still
considered. This option can save checkout time, and reduce main repo size.

I hope this make sense. I would appreciate Igniter's opinion on this topic.

Sincerely,
Dmitriy Pavlov

ср, 18 июл. 2018 г. в 23:05, Denis Magda :

> Hi Dmitriy,
>
> Yes, I would have this tool at hands soon as I check out Ignite repo and
> start setting it up. However, instead of a new repo let's place it under
> {ignite}/dev-tools folder. What do you think?
>
> --
> Denis
>
> On Wed, Jul 18, 2018 at 4:37 AM Dmitry Pavlov 
> wrote:
>
> > Hi Igniters,
> >
> > There is one mode widely used tool in Apache Ignite, abbreviation plugin
> > for Intelli J Idea. This plugin is used by almost all experienced Ignite
> > contributors.
> >
> > I would like to say thanks to all contributors which created this plugin:
> > vkazakov, sevdokimov, daradurvs, agoncharuk. And because this plugin is
> > also a part of our process I also want to place plugin code to ASF
> > repository.
> >
> > What do you think about placing plugin code to supplementary Apache
> > repository? Please share your vision till 24 July.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/Abbreviation+Rules#AbbreviationRules-IntelliJIdeaPlugin
> >
> >
> > https://github.com/dspavlov/ignite-abbrev-plugin
> >
>


Re: Place Ignite TC helper to ASF Ignite supplementary git repo

2018-07-18 Thread Dmitry Pavlov
Hi Denis,

It will made things simple.

1) For example any comitter will be able to change rules of notification
and fix the Bot if something goes wrong. Now it is my github repo. ASF repo
will guarantee that code will be always accessible by community members.

2) Being a part of ASF repo the Bot will be simple thing that less
experienced developer can start with. The Bot uses latest AI release as DB
with persistence enabled, so bot developer became at least Apache Ignite
user, and as most - new contributor.

If we agree to place this bot to ASF, next step could be asking Infra Team
to provide 2nd level apache domain, e.g. mtcga.ignite.apache.org for web
UI. I guess it would be plus if our tool code is available in ASF repo, but
not in some private git repo.

Sincerely,
Dmitriy Pavlov

ср, 18 июл. 2018 г. в 23:03, Denis Magda :

> Hi Dmitriy,
>
> The whole year has passed since this initiative launch, hell, the times
> passes by :)
>
> What would be the benefits of having the tool in the Apache repo? Does it
> simplify the things for us.
>
> --
> Denis
>
> On Wed, Jul 18, 2018 at 3:59 AM Dmitry Pavlov 
> wrote:
>
> > Hi Igniters,
> >
> > Almost 1 year has passed since Make Teamcity Green Again was initially
> > proposed. During this process we managed to get almost successful Run
> Alls
> > in master, but currently regressions still occur. We all tried a lot of
> > things: careful examination of PR tests, continuous monitoring of master,
> > suite responsible contributor, tickets creation and so on.
> >
> > According to Igniter's feedback most productive thing was master
> monitoring
> > and timely fix of new failures. But contributor’s enthusiasm is limited
> and
> > monitoring is not most enjoyable thing, so it's time to automate this
> > activity. I’ve created MTCGA.Bot which sends emails about new failures
> and
> > in addition has a couple of useful features.
> >
> > The Bot is being developed only based on your feedback. 30 Ignite
> > developers already tried it. I'm going to run short webinar/presentation
> at
> > Mon 23 July and tell more about Bot capabilites, so everyone can make an
> > impression.
> >
> > I would like to continue development and I propose to place TC Helper
> code
> > to Apache Ignite supplementary repository (same as ignite-release). What
> do
> > you think about it? Please share your vision till 24 July.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > References:
> >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/Make+Teamcity+Green+Again#MakeTeamcityGreenAgain-MTCGABot
> >
> > https://github.com/dspavlov/ignite-teamcity-helper
> >
>


Re: [MTCGA]: new failures in builds [1499957] needs to be handled

2018-07-18 Thread Dmitry Pavlov
Hi Maxim,

Sure, thank you for this idea.

I've accumulated notification types and rules here:
https://cwiki.apache.org/confluence/display/IGNITE/Make+Teamcity+Green+Again#MakeTeamcityGreenAgain-NotificationTypes

Sincerely,
Dmitriy Pavlov


ср, 18 июл. 2018 г. в 13:59, Maxim Muzafarov :

> Dmitry,
>
> Got it. Thanks!
>
> I've found brief MTCGABot description here [1].
> Can we also add there this notification rules?
>
> [1]
>
> https://cwiki.apache.org/confluence/display/IGNITE/Make+Teamcity+Green+Again#MakeTeamcityGreenAgain-MTCGABot
>
> ср, 18 июл. 2018 г. в 12:52, Dmitry Pavlov :
>
> > Hi Maxim,
> >
> > Notification will be send for each sequential group of builds having
> > failures 3+ times in a row. Let's define 0 as success, 1 as failure.
> >
> > So history 01110111 will generate two notifications. First
> > transition 0->1 can be bug introduced test failure. This bug can be fixed
> > with some changes after 111->0. And second transition can be potentially
> > new problem, and test failure would be re-notified.
> >
> > But if transition 0->1 ocurred only once, and failure continues to
> happen,
> > than no new notifcation will be generated.
> >
> > As always, I appreciate feedback and proposals.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > ср, 18 июл. 2018 г. в 12:45, Maxim Muzafarov :
> >
> > > Dmitry,
> > >
> > > Will this notification continously send on new failure fot particular
> > > test-case if we already have JIRA ticket for investigation? Should we
> > mute
> > > this test on TC to stop notifications?
> > >
> > > вт, 17 июл. 2018 г. в 22:30, Dmitry Pavlov :
> > >
> > > > Odd flaky tests notifications were fixed.
> > > >
> > > > If test changes its status more than 6 times in last 50 runs, than it
> > is
> > > > required to fail 7 times in a row to be considered as new failure.
> > Normal
> > > > test can be considered as new failure if it fails 3 times.
> > > >
> > > > I would appreciate any feedback and proposals of rules change to make
> > > > MTCGA.Bot as useful as it humanly possible.
> > > >
> > > > вт, 17 июл. 2018 г. в 10:26, Dmitry Pavlov :
> > > >
> > > > > Hi Igniters,
> > > > >
> > > > > Seems this test is flaky: it has frequent changes of its status.
> This
> > > can
> > > > > be detected in Bot. and I'll update Bot once issue
> > > > > https://github.com/dspavlov/ignite-teamcity-helper/issues/14 is
> > > > completed.
> > > > >
> > > > > So please ignore this failure for now, as it is not new. Of course
> if
> > > you
> > > > > know how to fix flakiness, fix is always preferred.
> > > > >
> > > > > Sincerely,
> > > > > Dmitriy Pavlov
> > > > >
> > > > >
> > > > > вт, 17 июл. 2018 г. в 2:06, :
> > > > >
> > > > >> Hi Ignite Developer,
> > > > >>
> > > > >> I am MTCGA.Bot, and I've detected some issue on TeamCity to be
> > > > addressed.
> > > > >> I hope you can help.
> > > > >>
> > > > >>  *New test failure in master
> > > > >> CacheStopAndDestroySelfTest.testTckStyleCreateDestroyClose
> > > > >>
> > > >
> > >
> >
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=139506597706397620=%3Cdefault%3E=testDetails
> > > > >>  Changes may led to failure were done by - ivandasch
> > > > >>
> > > >
> > >
> >
> http://ci.ignite.apache.org/viewModification.html?modId=825683=false
> > > > >>
> > > > >> - If your changes can led to this failure(s), please
> create
> > > > issue
> > > > >> with label MakeTeamCityGreenAgain and assign it to you.
> > > > >> -- If you have fix, please set ticket to PA state and
> write
> > to
> > > > >> dev list fix is ready
> > > > >> -- For case fix will require some time please mute test
> and
> > > set
> > > > >> label Muted_Test to issue
> > > > >> - If you know which change caused failure please contact
> > > change
> > > > >> author directly
> > > > >> - If you don't know which change caused failure please
> send
> > > > >> message to dev list to find out
> > > > >> Should you have any questions please contact dpav...@apache.org
> or
> > > > write
> > > > >> to dev.list
> > > > >> Best Regards,
> > > > >> MTCGA.Bot
> > > > >> Notification generated at Tue Jul 17 02:06:49 MSK 2018
> > > > >>
> > > > >
> > > >
> > > --
> > > --
> > > Maxim Muzafarov
> > >
> >
> --
> --
> Maxim Muzafarov
>


Re: Pushing IGNITE-6826 forward

2018-07-18 Thread 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, not only number.
2. Include link to JIRA issue into body so it could be easily clicked to
find out details.
It can seem not important, but saves a minute for everyone.

Sincerely,
Dmitriy Pavlov

ср, 18 июл. 2018 г. в 16:32, Stanislav Lukyanov :

> Hi Igniters,
>
> There is a small but annoying issue with examples using MulticastIpFinder
> by default.
> The JIRA is  IGNITE-6826.
>
> AntonK and DmitriiR have suggested PRs to fix this, but PavelT had some
> concerns and the fix stuck as the result.
>
> Pavel, could you please suggest necessary changes to the PRs so that guys
> can move forward with integration?
>
> Thanks,
> Stan
>


Re: [RESULT] [VOTE] Apache Ignite 2.6.0 Release (RC1)

2018-07-18 Thread Dmitry Pavlov
Hi Ilya,

Thank you for noticing this.

We should somehow update https://ignite.apache.org/latest data. I guess
PMCs or site admin can do this update.

Sincerely,
Dmitriy Pavlov

ср, 18 июл. 2018 г. в 16:31, Ilya Kasnacheev :

> Hello!
>
> Since we have releases 2.6.0, can we perhaps prop up the node start
> message, which is currently still:
>
> [16:28:05] New version is available at ignite.apache.org: 2.4.0
>
> Regards,
>
> --
> Ilya Kasnacheev
>
> 2018-07-17 21:59 GMT+03:00 Denis Magda :
>
> > Andrey G.,
> >
> > As a PMC member and release manager of 2.6, could you please help the
> folks
> > to finish this step?
> >
> > --
> > Denis
> >
> > On Tue, Jul 17, 2018 at 9:58 AM Pavel Tupitsyn 
> > wrote:
> >
> > > I think it makes sense that only PMCs have rights to do so,
> > > especially because publishing a package can not be undone of re-done,
> > only
> > > a new version can be published if there is some issue.
> > > Also, restricted SVN area is the only feasible way to share secrets
> with
> > > the team that I know of.
> > >
> > > Another approach could be NuGet Organizations, where membership is
> > managed
> > > on NuGet website.
> > > What do you think?
> > >
> > > On Tue, Jul 17, 2018 at 7:32 PM Petr Ivanov 
> wrote:
> > >
> > > > Oh, I see.
> > > >
> > > >
> > > > I have no access there. I guess only PMC can upload packages to
> > > nuget.org
> > > > …
> > > >
> > > >
> > > > > On 17 Jul 2018, at 18:21, Pavel Tupitsyn 
> > wrote:
> > > > >
> > > > > Oh sorry I missed the question.
> > > > > * The build script '[Prepare Vote #3] Build NuGet packages'
> produces
> > > the
> > > > > artifacts (.nupkg files).
> > > > > * Then we have to manually upload them to NuGet org, which requires
> > an
> > > > API
> > > > > key or an account with access to these packages
> > > > >
> > > > > API key can be found in [1] (which is linked in [2])
> > > > >
> > > > > Upload can be done with a command like 'ls *.nupkg | % { nuget push
> > > > > $_.FullName APIKEY }' (Powershell),
> > > > > or a similar one on Linux/Mac with .NET Core or Mono.
> > > > >
> > > > > Let me know if you need more details.
> > > > >
> > > > > [1]
> > > >
> https://svn.apache.org/repos/private/pmc/ignite/credentials/nuget.org
> > > > > [2] https://cwiki.apache.org/confluence/display/IGNITE/
> > Release+Process
> > > > >
> > > > > On Tue, Jul 17, 2018 at 5:55 PM Petr Ivanov 
> > > wrote:
> > > > >
> > > > >> Just tell us please HOW it should be done, please.
> > > > >>
> > > > >> With what build or script or other procedure?
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >>> On 17 Jul 2018, at 17:44, Pavel Tupitsyn 
> > > wrote:
> > > > >>>
> > > > >>> Peter,
> > > > >>>
> > > > >>> I can do it anytime when we confirm the right Artifacts build.
> > > > >>> Can you please clarify what " Before uploading, please check this
> > [1]
> > > > >> build.
> > > > >>> " is about?
> > > > >>>
> > > > >>> Thanks,
> > > > >>> Pavel
> > > > >>>
> > > > >>> On Tue, Jul 17, 2018 at 8:36 AM Peter Ivanov <
> mr.wei...@gmail.com>
> > > > >> wrote:
> > > > >>>
> > > >  Pavel,
> > > > 
> > > > 
> > > >  Can you give a cue where can be uploaded Nuget packages found?
> > > > 
> > > >  On Mon, 16 Jul 2018 at 23:37, Pavel Tupitsyn <
> > ptupit...@apache.org>
> > > > >> wrote:
> > > > 
> > > > > Petr,
> > > > >
> > > > > This is the same build that I have linked. Is there anything I
> > > should
> > > > >> pay
> > > > > attention to?
> > > > >
> > > > > On Mon, Jul 16, 2018 at 11:05 PM Petr Ivanov <
> > mr.wei...@gmail.com>
> > > >  wrote:
> > > > >
> > > > >> Pavel,
> > > > >>
> > > > >>
> > > > >> Before uploading, please check this [1] build.
> > > > >>
> > > > >>
> > > > >> [1]
> > > > >>
> > > > >
> > > > 
> > > > >>
> > > >
> > > https://ci.ignite.apache.org/viewLog.html?buildId=1502954=
> > ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages
> > =buildLog&_focus=230#_state=230
> > > > >> <
> > > > >>
> > > > >
> > > > 
> > > > >>
> > > >
> > > https://ci.ignite.apache.org/viewLog.html?buildId=1502954=
> > ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages
> > =buildLog&_focus=230#_state=230
> > > > >>>
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >>> On 16 Jul 2018, at 22:56, Pavel Tupitsyn <
> ptupit...@apache.org
> > >
> > > >  wrote:
> > > > >>>
> > > > >>> I will upload NuGet packages. Is this the right TC build?
> > > > >>>
> > > > >>
> > > > >
> > > > 
> > > > >>
> > > >
> > > https://ci.ignite.apache.org/viewLog.html?buildId=1502954=
> > ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages
> > =buildResultsDiv
> > > > >>>
> > > > >>> On Mon, Jul 16, 2018 at 8:43 PM Andrey Gura <
> ag...@apache.org>
> > > >  wrote:
> > > > >>>
> > > >  Ignite site is updated. Most artifacts are published.
> > > > 
> > > >  

Re: Documenting Ignite

2018-07-18 Thread Dmitry Pavlov
Hi Artem,

I sometimes receive feedback that Ignite docs has potential for
improvement, while I found our docs quite intuitive and simple to
understand. So if experienced tech writer will join community it could
benefit all of us, and users, of course. So you're very welcome to the
community!

About idea of fields introduction I guess we will need assistance of Apache
Infra team, because Ignite shares JIRA with all other Apache project. And
I'm not sure that technical implementation of proposed process is even
possible without plugins. Could we consider some manual processing of
completed issues in relation to doc requrement?

Sincerely,
Dmitriy Pavlov

ср, 18 июл. 2018 г. в 15:06, Artem Budnikov :

> Hi Igniters,
>
> Being a technical writer, I'm going to contribute to Ignite's
> documentation, and I believe documentation is an important part of every
> product, especially such a complex product as Apache Ignite.
>
> I'd like to put forward a suggestion on how to increase our chances of
> making Ignite documentation more comprehensive. The basic idea is to
> have a Jira issue with the Component field set to "Documentation" for
> every feature that needs to be documented. This will ensure that there
> are documentation issues that cover the entire product functionality.
> Then someone can take on an issue and contribute an article on the subject.
>
> This is how I envision it to work technically. A new field (checkbox) is
> added to the Apache Ignite Jira project. The checkbox indicates that the
> feature requested in this issue needs to be documented. The checkbox is
> selected by default. If the feature does not require documentation, then
> the author unchecks the checkbox. If it does require documentation, the
> author creates a related Jira issue selecting "Documentation" in the
> Component field, providing details on what exactly should be documented.
>
> The field is called "Requires documentation" or similarly. It could be
> also useful to create a new issue type for documentation issues
> exclusively.
>
> Once this is done, we'll be able to filter out
>
>  1. issues that do not require documentation,
>  2. issues that have related documentation tickets, and
>  3. issues that require documentation but have no related issues (which
> means that the author forgot to create a documentation issue for it).
>
>
> Please share your thoughts about this.
>
>
> Best regards,
>
> Artem Budnikov
>
>


Place Ignite Abbrev Plugin to ASF Ignite supplementary git repo

2018-07-18 Thread Dmitry Pavlov
Hi Igniters,

There is one mode widely used tool in Apache Ignite, abbreviation plugin
for Intelli J Idea. This plugin is used by almost all experienced Ignite
contributors.

I would like to say thanks to all contributors which created this plugin:
vkazakov, sevdokimov, daradurvs, agoncharuk. And because this plugin is
also a part of our process I also want to place plugin code to ASF
repository.

What do you think about placing plugin code to supplementary Apache
repository? Please share your vision till 24 July.

Sincerely,
Dmitriy Pavlov

https://cwiki.apache.org/confluence/display/IGNITE/Abbreviation+Rules#AbbreviationRules-IntelliJIdeaPlugin


https://github.com/dspavlov/ignite-abbrev-plugin


Place Ignite TC helper to ASF Ignite supplementary git repo

2018-07-18 Thread Dmitry Pavlov
Hi Igniters,

Almost 1 year has passed since Make Teamcity Green Again was initially
proposed. During this process we managed to get almost successful Run Alls
in master, but currently regressions still occur. We all tried a lot of
things: careful examination of PR tests, continuous monitoring of master,
suite responsible contributor, tickets creation and so on.

According to Igniter's feedback most productive thing was master monitoring
and timely fix of new failures. But contributor’s enthusiasm is limited and
monitoring is not most enjoyable thing, so it's time to automate this
activity. I’ve created MTCGA.Bot which sends emails about new failures and
in addition has a couple of useful features.

The Bot is being developed only based on your feedback. 30 Ignite
developers already tried it. I'm going to run short webinar/presentation at
Mon 23 July and tell more about Bot capabilites, so everyone can make an
impression.

I would like to continue development and I propose to place TC Helper code
to Apache Ignite supplementary repository (same as ignite-release). What do
you think about it? Please share your vision till 24 July.

Sincerely,
Dmitriy Pavlov

References:
https://cwiki.apache.org/confluence/display/IGNITE/Make+Teamcity+Green+Again#MakeTeamcityGreenAgain-MTCGABot

https://github.com/dspavlov/ignite-teamcity-helper


Re: [MTCGA]: new failures in builds [1499957] needs to be handled

2018-07-18 Thread Dmitry Pavlov
Hi Maxim,

Notification will be send for each sequential group of builds having
failures 3+ times in a row. Let's define 0 as success, 1 as failure.

So history 01110111 will generate two notifications. First
transition 0->1 can be bug introduced test failure. This bug can be fixed
with some changes after 111->0. And second transition can be potentially
new problem, and test failure would be re-notified.

But if transition 0->1 ocurred only once, and failure continues to happen,
than no new notifcation will be generated.

As always, I appreciate feedback and proposals.

Sincerely,
Dmitriy Pavlov

ср, 18 июл. 2018 г. в 12:45, Maxim Muzafarov :

> Dmitry,
>
> Will this notification continously send on new failure fot particular
> test-case if we already have JIRA ticket for investigation? Should we mute
> this test on TC to stop notifications?
>
> вт, 17 июл. 2018 г. в 22:30, Dmitry Pavlov :
>
> > Odd flaky tests notifications were fixed.
> >
> > If test changes its status more than 6 times in last 50 runs, than it is
> > required to fail 7 times in a row to be considered as new failure. Normal
> > test can be considered as new failure if it fails 3 times.
> >
> > I would appreciate any feedback and proposals of rules change to make
> > MTCGA.Bot as useful as it humanly possible.
> >
> > вт, 17 июл. 2018 г. в 10:26, Dmitry Pavlov :
> >
> > > Hi Igniters,
> > >
> > > Seems this test is flaky: it has frequent changes of its status. This
> can
> > > be detected in Bot. and I'll update Bot once issue
> > > https://github.com/dspavlov/ignite-teamcity-helper/issues/14 is
> > completed.
> > >
> > > So please ignore this failure for now, as it is not new. Of course if
> you
> > > know how to fix flakiness, fix is always preferred.
> > >
> > > Sincerely,
> > > Dmitriy Pavlov
> > >
> > >
> > > вт, 17 июл. 2018 г. в 2:06, :
> > >
> > >> Hi Ignite Developer,
> > >>
> > >> I am MTCGA.Bot, and I've detected some issue on TeamCity to be
> > addressed.
> > >> I hope you can help.
> > >>
> > >>  *New test failure in master
> > >> CacheStopAndDestroySelfTest.testTckStyleCreateDestroyClose
> > >>
> >
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=139506597706397620=%3Cdefault%3E=testDetails
> > >>  Changes may led to failure were done by - ivandasch
> > >>
> >
> http://ci.ignite.apache.org/viewModification.html?modId=825683=false
> > >>
> > >> - If your changes can led to this failure(s), please create
> > issue
> > >> with label MakeTeamCityGreenAgain and assign it to you.
> > >> -- If you have fix, please set ticket to PA state and write to
> > >> dev list fix is ready
> > >> -- For case fix will require some time please mute test and
> set
> > >> label Muted_Test to issue
> > >> - If you know which change caused failure please contact
> change
> > >> author directly
> > >> - If you don't know which change caused failure please send
> > >> message to dev list to find out
> > >> Should you have any questions please contact dpav...@apache.org or
> > write
> > >> to dev.list
> > >> Best Regards,
> > >> MTCGA.Bot
> > >> Notification generated at Tue Jul 17 02:06:49 MSK 2018
> > >>
> > >
> >
> --
> --
> Maxim Muzafarov
>


Re: [MTCGA]: new failures in builds [1499957] needs to be handled

2018-07-17 Thread Dmitry Pavlov
Odd flaky tests notifications were fixed.

If test changes its status more than 6 times in last 50 runs, than it is
required to fail 7 times in a row to be considered as new failure. Normal
test can be considered as new failure if it fails 3 times.

I would appreciate any feedback and proposals of rules change to make
MTCGA.Bot as useful as it humanly possible.

вт, 17 июл. 2018 г. в 10:26, Dmitry Pavlov :

> Hi Igniters,
>
> Seems this test is flaky: it has frequent changes of its status. This can
> be detected in Bot. and I'll update Bot once issue
> https://github.com/dspavlov/ignite-teamcity-helper/issues/14 is completed.
>
> So please ignore this failure for now, as it is not new. Of course if you
> know how to fix flakiness, fix is always preferred.
>
> Sincerely,
> Dmitriy Pavlov
>
>
> вт, 17 июл. 2018 г. в 2:06, :
>
>> Hi Ignite Developer,
>>
>> I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed.
>> I hope you can help.
>>
>>  *New test failure in master
>> CacheStopAndDestroySelfTest.testTckStyleCreateDestroyClose
>> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=139506597706397620=%3Cdefault%3E=testDetails
>>  Changes may led to failure were done by - ivandasch
>> http://ci.ignite.apache.org/viewModification.html?modId=825683=false
>>
>> - If your changes can led to this failure(s), please create issue
>> with label MakeTeamCityGreenAgain and assign it to you.
>> -- If you have fix, please set ticket to PA state and write to
>> dev list fix is ready
>> -- For case fix will require some time please mute test and set
>> label Muted_Test to issue
>> - If you know which change caused failure please contact change
>> author directly
>> - If you don't know which change caused failure please send
>> message to dev list to find out
>> Should you have any questions please contact dpav...@apache.org or write
>> to dev.list
>> Best Regards,
>> MTCGA.Bot
>> Notification generated at Tue Jul 17 02:06:49 MSK 2018
>>
>


Re: [MTCGA]: new failures in builds [1464083] needs to be handled

2018-07-17 Thread Dmitry Pavlov
Same as for previous notification, this is another 3 timeouts in a row
occurred. I hope soon we will be able to fix all timeouts, so such
notifications will not appear.

вт, 17 июл. 2018 г. в 22:17, :

> Hi Ignite Developer,
>
> I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed.
> I hope you can help.
>
>  *New Critical Failure in master Data Structures
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_DataStructures=%3Cdefault%3E=buildTypeStatusDiv
>  Changes may led to failure were done by
>  - jokserfn
> http://ci.ignite.apache.org/viewModification.html?modId=825129=false
>  - irakov
> http://ci.ignite.apache.org/viewModification.html?modId=825127=false
>  - irakov
> http://ci.ignite.apache.org/viewModification.html?modId=825126=false
>  - ivandasch
> http://ci.ignite.apache.org/viewModification.html?modId=825120=false
>  - dmitriy.govorukhin
> http://ci.ignite.apache.org/viewModification.html?modId=825119=false
>  - polyakov.alexandr.alexandrovich
> http://ci.ignite.apache.org/viewModification.html?modId=825110=false
>  - vpyatkov
> http://ci.ignite.apache.org/viewModification.html?modId=825105=false
>  - akuznetsov
> http://ci.ignite.apache.org/viewModification.html?modId=825014=false
>  - dmitriyff
> http://ci.ignite.apache.org/viewModification.html?modId=825013=false
>
> - If your changes can led to this failure(s), please create issue
> with label MakeTeamCityGreenAgain and assign it to you.
> -- If you have fix, please set ticket to PA state and write to dev
> list fix is ready
> -- For case fix will require some time please mute test and set
> label Muted_Test to issue
> - If you know which change caused failure please contact change
> author directly
> - If you don't know which change caused failure please send
> message to dev list to find out
> Should you have any questions please contact dpav...@apache.org or write
> to dev.list
> Best Regards,
> MTCGA.Bot
> Notification generated at Tue Jul 17 22:17:10 MSK 2018
>


Re: [MTCGA]: new failures in builds [1492273] needs to be handled

2018-07-17 Thread Dmitry Pavlov
Hi Igniters,

The Bot was updated to handle timeouts & JVM crashes in suites in a special
way. These type of failures are named Critical.  If 3 or more (timeouts/JMV
crashes) occured several times in a row, such notification will be send.
Also it is required that last run was completed with timeout.

As for DS failure: I think fix is ready for this situation, I saw issue in
PA state.

Sincerely,
Dmitriy Pavlov

вт, 17 июл. 2018 г. в 22:03, :

> Hi Ignite Developer,
>
> I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed.
> I hope you can help.
>
>  *New Critical Failure in master Data Structures
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_DataStructures=%3Cdefault%3E=buildTypeStatusDiv
>  No changes in build
>
> - If your changes can led to this failure(s), please create issue
> with label MakeTeamCityGreenAgain and assign it to you.
> -- If you have fix, please set ticket to PA state and write to dev
> list fix is ready
> -- For case fix will require some time please mute test and set
> label Muted_Test to issue
> - If you know which change caused failure please contact change
> author directly
> - If you don't know which change caused failure please send
> message to dev list to find out
> Should you have any questions please contact dpav...@apache.org or write
> to dev.list
> Best Regards,
> MTCGA.Bot
> Notification generated at Tue Jul 17 22:03:32 MSK 2018
>


Re: [MTCGA]: new failures in builds [1507197] needs to be handled

2018-07-17 Thread Dmitry Pavlov
These tests were intentionally failed with link to
https://issues.apache.org/jira/browse/IGNITE-9004 ticket. This avoids suite
timeout.

вт, 17 июл. 2018 г. в 16:36, :

> Hi Ignite Developer,
>
> I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed.
> I hope you can help.
>
>  *New test failure in master
> IgniteChangeGlobalStateTest.testStopPrimaryAndActivateFromServerNode
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-2989101115659545850=%3Cdefault%3E=testDetails
>
>  *New test failure in master
> IgniteChangeGlobalStateTest.testDeActivateFromServerNode
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=7926906195866783751=%3Cdefault%3E=testDetails
>
>  *New test failure in master
> IgniteChangeGlobalStateTest.testTryUseDataStructureInActiveCluster
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=1237675547622950789=%3Cdefault%3E=testDetails
>
>  *New test failure in master
> IgniteChangeGlobalStateTest.testDeActivateFromClientNode
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=5257935054027107459=%3Cdefault%3E=testDetails
>
>  *New test failure in master
> IgniteChangeGlobalStateTest.testStopPrimaryAndActivateFromClientNode
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-1121005557998407806=%3Cdefault%3E=testDetails
>
>  *New test failure in master
> IgniteChangeGlobalStateTest.testActiveAndInActiveAtTheSameTimeCluster
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-5091897751321880348=%3Cdefault%3E=testDetails
>
>  *New test failure in master
> IgniteChangeGlobalStateTest.testDeActivateCheckCacheDestroy
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-5133427611595249025=%3Cdefault%3E=testDetails
>
>  *New test failure in master
> IgniteChangeGlobalStateTest.testTryUseServiceInActiveCluster
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-8663243603806743793=%3Cdefault%3E=testDetails
>
>  *New test failure in master
> IgniteChangeGlobalStateTest.testTryUseCacheInActiveCluster
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-5647678860514408799=%3Cdefault%3E=testDetails
>
>  *New test failure in master
> IgniteChangeGlobalStateTest.testActivateOnAlreadyActivatedCluster
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-1285441177699096481=%3Cdefault%3E=testDetails
>  Changes may led to failure were done by - dpavlov
> http://ci.ignite.apache.org/viewModification.html?modId=825785=false
>  - garus.d.g
> http://ci.ignite.apache.org/viewModification.html?modId=825781=false
>  - slava.koptilin
> http://ci.ignite.apache.org/viewModification.html?modId=825780=false
>  - slava.koptilin
> http://ci.ignite.apache.org/viewModification.html?modId=825779=false
>  - isapego
> http://ci.ignite.apache.org/viewModification.html?modId=825778=false
>  - nizhikov
> http://ci.ignite.apache.org/viewModification.html?modId=825776=false
>  - ivandasch
> http://ci.ignite.apache.org/viewModification.html?modId=825775=false
>  - isapego
> http://ci.ignite.apache.org/viewModification.html?modId=825774=false
>  - dmitriy.govorukhin
> http://ci.ignite.apache.org/viewModification.html?modId=825773=false
>  - dmitriy.govorukhin
> http://ci.ignite.apache.org/viewModification.html?modId=825772=false
>  - dmitriy.govorukhin
> http://ci.ignite.apache.org/viewModification.html?modId=825771=false
>  - dmitriy.govorukhin
> http://ci.ignite.apache.org/viewModification.html?modId=825770=false
>  - andrey.mashenkov
> http://ci.ignite.apache.org/viewModification.html?modId=825769=false
>  - vozerov
> http://ci.ignite.apache.org/viewModification.html?modId=825768=false
>  - dmitriy.govorukhin
> http://ci.ignite.apache.org/viewModification.html?modId=825767=false
>  - garus.d.g
> http://ci.ignite.apache.org/viewModification.html?modId=825766=false
>  - maxmuzaf
> http://ci.ignite.apache.org/viewModification.html?modId=825765=false
>  - nizhikov
> http://ci.ignite.apache.org/viewModification.html?modId=825764=false
>  - nizhikov
> http://ci.ignite.apache.org/viewModification.html?modId=825763=false
>  - d.w.sorokin
> http://ci.ignite.apache.org/viewModification.html?modId=825762=false
>  - andrey.mashenkov
> http://ci.ignite.apache.org/viewModification.html?modId=825761=false
>  - vozerov
> http://ci.ignite.apache.org/viewModification.html?modId=825760=false
>  - mcherkasov
> http://ci.ignite.apache.org/viewModification.html?modId=825759=false
>  - ilantukh
> http://ci.ignite.apache.org/viewModification.html?modId=825758=false
>  - alexey.goncharuk
> http://ci.ignite.apache.org/viewModification.html?modId=825757=false
>  - ilantukh
> 

Re: [MTCGA]: new failures in builds [1490762] needs to be handled

2018-07-17 Thread Dmitry Pavlov
Hi Igniters,

this test was intentionally failed with link to
https://issues.apache.org/jira/browse/IGNITE-9004 ticket.

I hope Igniters will figure out why it was failing suite.

Sincerely,
Dmitriy Pavlov

вт, 17 июл. 2018 г. в 16:22, :

> Hi Ignite Developer,
>
> I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed.
> I hope you can help.
>
>  *New test failure in master
> IgniteChangeGlobalStateTest.testConcurrentActivateFromClientNodeAndServerNode
>
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-2144060973300403257=%3Cdefault%3E=testDetails
>  No changes in build
>
> - If your changes can led to this failure(s), please create issue
> with label MakeTeamCityGreenAgain and assign it to you.
> -- If you have fix, please set ticket to PA state and write to dev
> list fix is ready
> -- For case fix will require some time please mute test and set
> label Muted_Test to issue
> - If you know which change caused failure please contact change
> author directly
> - If you don't know which change caused failure please send
> message to dev list to find out
> Should you have any questions please contact dpav...@apache.org or write
> to dev.list
> Best Regards,
> MTCGA.Bot
> Notification generated at Tue Jul 17 16:21:52 MSK 2018
>


Re: MTCGA: new failures in builds [1485687] needs to be handled

2018-07-17 Thread Dmitry Pavlov
Hi, Stanislav L. replied in ticket
https://issues.apache.org/jira/browse/IGNITE-9005

пн, 16 июл. 2018 г. в 18:15, kcheng.mvp :

> I checked the source code and found that this issue may be caused by this
> line
>
> org.apache.ignite.internal.processors.cache.GridCacheProcessor #1452
>
> CacheEvictionManager evictMgr = (nearEnabled || cfg.isOnheapCacheEnabled())
> ? new GridCacheEvictionManager() : new CacheOffheapEvictionManager();
>
> as in this case a new CacheOffheapEvictionManager() will return, but this
> implementation does not do any eviction bean register/unregister, as there
> are no any policy.
>
> are my findings wrong?
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>


Re: [MTCGA]: new failures in builds [1499957] needs to be handled

2018-07-17 Thread Dmitry Pavlov
Hi Igniters,

Seems this test is flaky: it has frequent changes of its status. This can
be detected in Bot. and I'll update Bot once issue
https://github.com/dspavlov/ignite-teamcity-helper/issues/14 is completed.

So please ignore this failure for now, as it is not new. Of course if you
know how to fix flakiness, fix is always preferred.

Sincerely,
Dmitriy Pavlov


вт, 17 июл. 2018 г. в 2:06, :

> Hi Ignite Developer,
>
> I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed.
> I hope you can help.
>
>  *New test failure in master
> CacheStopAndDestroySelfTest.testTckStyleCreateDestroyClose
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=139506597706397620=%3Cdefault%3E=testDetails
>  Changes may led to failure were done by - ivandasch
> http://ci.ignite.apache.org/viewModification.html?modId=825683=false
>
> - If your changes can led to this failure(s), please create issue
> with label MakeTeamCityGreenAgain and assign it to you.
> -- If you have fix, please set ticket to PA state and write to dev
> list fix is ready
> -- For case fix will require some time please mute test and set
> label Muted_Test to issue
> - If you know which change caused failure please contact change
> author directly
> - If you don't know which change caused failure please send
> message to dev list to find out
> Should you have any questions please contact dpav...@apache.org or write
> to dev.list
> Best Regards,
> MTCGA.Bot
> Notification generated at Tue Jul 17 02:06:49 MSK 2018
>


Re: Ignite guide for community developes

2018-07-16 Thread Dmitry Pavlov
Sure, I will do. Sign up to JIRA and wiki, it is open for everyone. Then I
need username(s) to add appropriate contributor role.

пн, 16 июл. 2018 г. в 20:53, Yakov Zhdanov :

> 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 to do it:
> > In a page about creating IEP
> > link
> > <https://cwiki.apache.org/confluence/display/IGNITE/
> > Ignite+Enhancement+Proposal?showChildren=false>
> > There are no appropriate information.
> >
> > If you can do it please do.
> >
> >
> >
> > --
> > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
> >
>


Re: TeamCity: Mass run-all during weekend

2018-07-14 Thread Dmitry Pavlov
Hi Igniters,

Unfortunately current run seems to show a more regress than previous:
- tests 512 suites 41 failed during current run all
- versus tests 433 suites 23 was at the end of may.

Such a significiant difference seemed to come not from randomized nature of
failures but from newly introduced issues.

I've attached full report:
https://cwiki.apache.org/confluence/pages/viewpageattachments.action?pageId=73631266

Failures that looks as new are marked with red crossed icon in the report.

Sincerely,
Dmitriy Pavlov

пт, 13 июл. 2018 г. в 18:33, Dmitry Pavlov :

> Hi Igniters,
>
> I am going to start mass run-all during weekend and will shedule 30 builds
> at 20.30 MSK today, if nobody minds.
>
> Sincerely,
> Dmitriy Pavlov
>


Re: [MTCGA]: new failures in builds [1490510, 1490413] needs to be handled

2018-07-13 Thread Dmitry Pavlov
Please ignore this also.

These failures came from mass weekend tests master run and flaky tests
which unluckily failed simultaneously 3 times a row, so bot considered it
as new failures.

сб, 14 июл. 2018 г., 0:22 :

> Hi Ignite Developer,
>
> I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed.
> I hope you can help.
>
>  *New test failure in master
> IgnitePdsCorruptedStoreTest.testCacheMetaCorruption
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=6523479222827749257=%3Cdefault%3E=testDetails
>  No changes in build
>
>  *New test failure in master
> IgnitePdsAtomicCacheHistoricalRebalancingTest.testTopologyChangesWithConstantLoad
>
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=7534554859858291194=%3Cdefault%3E=testDetails
>
>  *New test failure in master
> IgnitePdsTxCacheRebalancingTest.testTopologyChangesWithConstantLoad
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-3769512162483462816=%3Cdefault%3E=testDetails
>  Changes may led to failure were done by - ilya.kasnacheev
> http://ci.ignite.apache.org/viewModification.html?modId=825627=false
>  - vinokurov.pasha
> http://ci.ignite.apache.org/viewModification.html?modId=825609=false
>  - agura
> http://ci.ignite.apache.org/viewModification.html?modId=825604=false
>  - ezagumennov
> http://ci.ignite.apache.org/viewModification.html?modId=825579=false
>  - amedvedev
> http://ci.ignite.apache.org/viewModification.html?modId=825566=false
>
> - If your changes can led to this failure(s), please create issue
> with label MakeTeamCityGreenAgain and assign it to you.
> -- If you have fix, please set ticket to PA state and write to dev
> list fix is ready
> -- For case fix will require some time please mute test and set
> label Muted_Test to issue
> - If you know which change caused failure please contact change
> author directly
> - If you don't know which change caused failure please send
> message to dev list to find out
> Should you have any questions please contact dpav...@apache.org or write
> to dev.list
> Best Regards,
> MTCGA.Bot
> Notification generated at Sat Jul 14 00:21:58 MSK 2018
>


Re: [MTCGA]: new failures in builds [1398134] needs to be handled

2018-07-13 Thread Dmitry Pavlov
Hi, it seems it is duplicate, so please ignore.

I will find out how duplicate notification ocurred.

пт, 13 июл. 2018 г. в 22:51, :

> Hi Ignite Developer,
>
> I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed.
> I hope you can help.
>
>  *New test failure in master
> IgniteNativeIoPdsRecoveryAfterFileCorruptionTest.testPageRecoveryAfterFileCorruption
>
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-7843429397229340143=%3Cdefault%3E=testDetails
>  No changes in build
>
> - If your changes can led to this failure(s), please create issue
> with label MakeTeamCityGreenAgain and assign it to you.
> -- If you have fix, please set ticket to PA state and write to dev
> list fix is ready
> -- For case fix will require some time please mute test and set
> label Muted_Test to issue
> - If you know which change caused failure please contact change
> author directly
> - If you don't know which change caused failure please send
> message to dev list to find out
> Should you have any questions please contact dpav...@apache.org or write
> to dev.list
> Best Regards,
> MTCGA.Bot
> Notification generated at Fri Jul 13 22:51:51 MSK 2018
>


Re: MTCGA: new failures in builds [1485687] needs to be handled

2018-07-13 Thread Dmitry Pavlov
I've created https://issues.apache.org/jira/browse/IGNITE-9005 to fix

Stanislav L. kindly agreed to fix this failure.

пт, 13 июл. 2018 г. в 12:09, Dmitry Pavlov :

> I suspect this change may case this failure:
> kcheng.mvp (kcheng.mvp) IGNITE-8776  Eviction policy MBeans are never
> registered if
> so I'm going to take a look.
>
> пт, 13 июл. 2018 г. в 10:59, :
>
>> Hi Ignite Developer,
>>
>> I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed.
>> I hope you can help.
>>
>>  *New test failure in master
>> GridCacheLifecycleAwareSelfTest.testLifecycleAware
>> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=7246907407546697403=%3Cdefault%3E=testDetails
>>  Changes may led to failure were done by dpavlov
>> http://ci.ignite.apache.org/viewModification.html?modId=825539=false,
>> eduard.shangareev
>> http://ci.ignite.apache.org/viewModification.html?modId=825536=false,
>> kcheng.mvp
>> http://ci.ignite.apache.org/viewModification.html?modId=825531=false,
>> dmitriyff
>> http://ci.ignite.apache.org/viewModification.html?modId=825495=false,
>> alexey.scherbakoff
>> http://ci.ignite.apache.org/viewModification.html?modId=825466=false,
>> anovikov
>> http://ci.ignite.apache.org/viewModification.html?modId=825458=false,
>> akuznetsov
>> http://ci.ignite.apache.org/viewModification.html?modId=825455=falseIf
>> your changes can led to this failure(s), please create issue with label
>> MakeTeamCityGreenAgain and assign it to you.If you have fix, please
>> set ticket to PA state and write to dev list fix is readyFor case
>> fix will require some time please mute test and set label Muted_Test to
>> issueIf you know which change caused failure please
>> contact change author directlyIf you don't know which change
>> caused failure please send message to dev list to find
>> outShould you have any questions please contact
>> dpav...@apache.org or write to dev.listBest
>> Regards,MTCGA.BotNotification generated at Fri Jul 13 10:58:57 MSK
>> 2018
>
>


TeamCity: Mass run-all during weekend

2018-07-13 Thread Dmitry Pavlov
Hi Igniters,

I am going to start mass run-all during weekend and will shedule 30 builds
at 20.30 MSK today, if nobody minds.

Sincerely,
Dmitriy Pavlov


Re: MTCGA: new failures in builds [1479951] needs to be handled

2018-07-13 Thread Dmitry Pavlov
Hi Maxim,

Q1, always dev list. I've asked Igniters to add match before VCS username &
TC user, but it was not always done. So it is only one option currently to
notify developers.

Q2. there is such plans
https://github.com/dspavlov/ignite-teamcity-helper/issues/9 - It will be
done in very nearest future. I will do my absolute best to find a time slot
to finish this feature.

Sincerely,
Dmitriy Pavlov

пт, 13 июл. 2018 г. в 10:14, Maxim Muzafarov :

> Dmity,
>
> Nice idea for such notification. Can you, please, clarify few questions:
>
> * Q1 *:  For such failures (5 times ok than 3 times fail) this notification
> would be sent to whole developer list or just for authous of problem
> commits?
>
> * Q2 *:  Can we also add notification about new "execution timeouts" for
> important Ignite test suites? (e.g. Caches, Activate\Deactivate, PDS)
>
> чт, 12 июл. 2018 г. в 19:29, Dmitry Pavlov :
>
> > I've pushed fix of failure to master.
> >
> > чт, 12 июл. 2018 г. в 16:25, Dmitry Pavlov :
> >
> > > Hi Igniters,
> > >
> > > this notification was generated because this test was stable passing
> (at
> > > least 5 ok) in master and became stable failed (at least 3 failures).
> > >
> > > Such notifications would not be generated for each case of flaky
> > failures,
> > > so I hope this feature will help us to identify and fix new failures.
> > >
> > > I'll fix message format to be more readable soon.
> > >
> > > It would be pleasure to me to run short talk (webinar) about tests,
> > MTCGA,
> > > and MTCGA.Bot (Ignite TC helper). Please reply if you are interested.
> > >
> > > I would also highly appreciate any kind of feedback.
> > >
> > > Sincerely,
> > > Dmitriy Pavlov
> > >
> > > чт, 12 июл. 2018 г. в 16:14, :
> > >
> > >> Hi Ignite Developer,
> > >>
> > >> I am MTCGA.Bot, and I've detected some issue on TeamCity to be
> > addressed.
> > >> I hope you can help.
> > >>
> > >>  *New test failure in master
> > >>
> >
> IgnitePdsCheckpointSimulationWithRealCpDisabledTest.testCheckpointSimulationMultiThreaded
> > >>
> > >>
> >
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-1615751728537497724=%3Cdefault%3E=testDetails
> > >>  Changes may led to failure were done by alexey.goncharuk
> > >>
> >
> http://ci.ignite.apache.org/viewModification.html?modId=825445=false
> > ,
> > >> eshangareev
> > >>
> >
> http://ci.ignite.apache.org/viewModification.html?modId=825442=false
> > ,
> > >> sergey.chugunov
> > >>
> >
> http://ci.ignite.apache.org/viewModification.html?modId=825439=false
> > ,
> > >> irakov
> > >>
> >
> http://ci.ignite.apache.org/viewModification.html?modId=825436=false
> > ,
> > >> irakov
> > >>
> >
> http://ci.ignite.apache.org/viewModification.html?modId=825428=false
> > ,
> > >> ivandasch
> > >>
> >
> http://ci.ignite.apache.org/viewModification.html?modId=825411=false
> > ,
> > >> sbt-pereslegin-pa1
> > >>
> >
> http://ci.ignite.apache.org/viewModification.html?modId=825407=false
> > ,
> > >> alexey.scherbakoff
> > >>
> >
> http://ci.ignite.apache.org/viewModification.html?modId=825404=false
> > ,
> > >> akuznetsov
> > >>
> >
> http://ci.ignite.apache.org/viewModification.html?modId=825396=false
> > ,
> > >> vsisko
> > >>
> >
> http://ci.ignite.apache.org/viewModification.html?modId=825371=false
> > ,
> > >> pivanov
> > >>
> >
> http://ci.ignite.apache.org/viewModification.html?modId=825366=false
> > ,
> > >> dmitriyff
> > >>
> >
> http://ci.ignite.apache.org/viewModification.html?modId=825351=false
> > ,
> > >> dmitriyff
> > >>
> >
> http://ci.ignite.apache.org/viewModification.html?modId=825348=false
> > If
> > >> your changes can led to this failure(s), please create issue with
> label
> > >> MakeTeamCityGreenAgain and assign it to you.If you have fix,
> > please
> > >> set ticket to PA state and write to dev list fix is readyFor
> > case
> > >> fix will require some time please mute test and set label Muted_Test
> to
> > >> issueIf you know which change caused failure please
> > >> contact change author directlyIf you don't know which change
> > >> caused failure please send message to dev list to find
> > >> outShould you have any questions please contact
> > >> dpav...@apache.org or write to dev.listBest
> > >> Regards,MTCGA.BotNotification generated at Thu Jul 12 16:14:23
> > MSK
> > >> 2018
> > >
> > >
> >
>


Re: RDD spark 2.10 version upgrade & TC suites

2018-07-13 Thread Dmitry Pavlov
Hi Petr, Nikolay, thank you!

пт, 13 июл. 2018 г. в 10:33, Petr Ivanov :

> Marked build type obsolete and removed from build chain.
>
>
>
> > On 13 Jul 2018, at 10:13, Nikolay Izhikov  wrote:
> >
> > Hello, Igniters.
> >
> > 1. There is no spark_2.10 module in master and ignite-2.6.
> >
> > 2. We don't need "RDD (Spark 2.10)" build. Please, delete it from Team
> City.
> >
> > В Чт, 12/07/2018 в 23:19 +0300, Dmitry Pavlov пишет:
> >> I guess related topic is
> >>
> http://apache-ignite-developers.2346864.n4.nabble.com/Review-request-for-IGNITE-8534-Upgrade-Ignite-Spark-Module-s-Spark-version-to-2-3-td30979.html
> >> Review request for IGNITE-8534 Upgrade Ignite Spark Module's Spark
> version to 2.3.
> >> and ticket https://issues.apache.org/jira/browse/IGNITE-8534
> >>
> >>
> >> чт, 12 июл. 2018 г. в 19:35, Denis Magda :
> >>> Nikolay,
> >>>
> >>> Please step in. I still see spark-2.10 module which means we fully
> support
> >>> this version.
> >>>
> >>> --
> >>> Denis
> >>>
> >>> On Thu, Jul 12, 2018 at 9:31 AM Dmitry Pavlov 
> wrote:
> >>>
> >>>> Hi Igniters,
> >>>>
> >>>> Do we need
> >>>>
> >>>>
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_RddSpark210=%3Cdefault%3E=buildTypeStatusDiv
> >>>> suite is always fails with exit code 1 and I think I saw discussion
> about
> >>>> version change.
> >>>>
> >>>> Could I remove this suite from RunAll?
> >>>>
> >>>> Sincerely,
> >>>> Dmitriy Pavlov
>
>


Re: MTCGA: new failures in builds [1485687] needs to be handled

2018-07-13 Thread Dmitry Pavlov
I suspect this change may case this failure:
kcheng.mvp (kcheng.mvp) IGNITE-8776  Eviction policy MBeans are never
registered if
so I'm going to take a look.

пт, 13 июл. 2018 г. в 10:59, :

> Hi Ignite Developer,
>
> I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed.
> I hope you can help.
>
>  *New test failure in master
> GridCacheLifecycleAwareSelfTest.testLifecycleAware
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=7246907407546697403=%3Cdefault%3E=testDetails
>  Changes may led to failure were done by dpavlov
> http://ci.ignite.apache.org/viewModification.html?modId=825539=false,
> eduard.shangareev
> http://ci.ignite.apache.org/viewModification.html?modId=825536=false,
> kcheng.mvp
> http://ci.ignite.apache.org/viewModification.html?modId=825531=false,
> dmitriyff
> http://ci.ignite.apache.org/viewModification.html?modId=825495=false,
> alexey.scherbakoff
> http://ci.ignite.apache.org/viewModification.html?modId=825466=false,
> anovikov
> http://ci.ignite.apache.org/viewModification.html?modId=825458=false,
> akuznetsov
> http://ci.ignite.apache.org/viewModification.html?modId=825455=falseIf
> your changes can led to this failure(s), please create issue with label
> MakeTeamCityGreenAgain and assign it to you.If you have fix, please
> set ticket to PA state and write to dev list fix is readyFor case
> fix will require some time please mute test and set label Muted_Test to
> issueIf you know which change caused failure please
> contact change author directlyIf you don't know which change
> caused failure please send message to dev list to find
> outShould you have any questions please contact
> dpav...@apache.org or write to dev.listBest
> Regards,MTCGA.BotNotification generated at Fri Jul 13 10:58:57 MSK
> 2018


Re: Cache 6 Suite Execution timeouts

2018-07-12 Thread Dmitry Pavlov
Suite is still sometimes timed out but now by
CacheExchangeMergeTest.testConcurrentStartServersAndClients.

чт, 24 мая 2018 г. в 16:24, Alexei Scherbakov :

> Hi, guys.
>
> Thanks for pointing this out.
>
> I'll look at this then I'll have available time.
>
> Possibly next week.
>
> Meanwhile I suggest not to use async rollbacks for transactions on near
> caches.
>
> чт, 24 мая 2018 г. в 14:09, Dmitry Pavlov :
>
>> Alexey? Could I hope you will pick up
>> https://issues.apache.org/jira/browse/IGNITE-8509?
>>
>> чт, 24 мая 2018 г. в 14:00, Maxim Muzafarov :
>>
>>> Hello,
>>>
>>> Just bump this topic up.
>>>
>>> 6/10 execution timeouts for the last 10 build in master!
>>>
>>> Will anyone help?
>>>
>>> [1]
>>>
>>> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Cache6=1=buildTypeHistoryList_IgniteTests24Java8=%3Cdefault%3E
>>>
>>> пн, 21 мая 2018 г. в 12:58, Dmitry Pavlov :
>>>
>>> > Hi Maxim,
>>> >
>>> > I observe the same, Cache 6 critical recent fails: 18,0% [9 fails / 50
>>> > runs]
>>> >
>>> > I hope Aleksei Scherbakov can help here. Alexey, please step in.
>>> >
>>> > Sincerely,
>>> > Dmitriy Pavlov
>>> >
>>> > вс, 20 мая 2018 г. в 20:37, Maxim Muzafarov :
>>> >
>>> > > Hello Igniters,
>>> > >
>>> > > Have anyone noticed a lot of execution timeouts for Cache 6 Suite?
>>> > > Since recently it fails too much on TxRollbackOnTimeoutNearCacheTest
>>> with
>>> > > "Found long running transaction".
>>> > >
>>> > > Please refer to TC [1]. It has 4/10 execution timeouts for the last
>>> 10
>>> > > builds in master.
>>> > >
>>> > > I've created IGNITE-8509 [2]. Will someone have time to look at? Or
>>> I'll
>>> > > try when I'm get free.
>>> > >
>>> > > [1]
>>> > >
>>> > >
>>> >
>>> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Cache6_IgniteTests24Java8=%3Cdefault%3E=buildTypeStatusDiv
>>> > > [2] https://issues.apache.org/jira/browse/IGNITE-8509
>>> > >
>>> >
>>>
>>
>
> --
>
> Best regards,
> Alexei Scherbakov
>


Re: RDD spark 2.10 version upgrade & TC suites

2018-07-12 Thread Dmitry Pavlov
I guess related topic is
http://apache-ignite-developers.2346864.n4.nabble.com/Review-request-for-IGNITE-8534-Upgrade-Ignite-Spark-Module-s-Spark-version-to-2-3-td30979.html
 Review request for IGNITE-8534 Upgrade Ignite Spark Module's Spark version
to 2.3.
and ticket https://issues.apache.org/jira/browse/IGNITE-8534


чт, 12 июл. 2018 г. в 19:35, Denis Magda :

> Nikolay,
>
> Please step in. I still see spark-2.10 module which means we fully support
> this version.
>
> --
> Denis
>
> On Thu, Jul 12, 2018 at 9:31 AM Dmitry Pavlov 
> wrote:
>
> > Hi Igniters,
> >
> > Do we need
> >
> >
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_RddSpark210=%3Cdefault%3E=buildTypeStatusDiv
> > suite is always fails with exit code 1 and I think I saw discussion about
> > version change.
> >
> > Could I remove this suite from RunAll?
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
>


Re: Delete ticket - issues.apache.org

2018-07-12 Thread Dmitry Pavlov
Hi, I'm not sure it is possible to delete issue in Apache JIRA.

I can suggest to resolve it as Wont' fix.

Sincerely,
Dmitriy Pavlov

ср, 20 июн. 2018 г. в 11:15, Puviarasu S :

> Hi Team,
>
> I have created a ticket in https://issues.apache.org/jira. I am in a
> situation to delete the ticket such that it is not accessible over the
> Internet.
>
> Kindly requesting you to help me in deleting the ticket from Apache JIRA.
>
> Thanks in advance!!!
>
> Regards,
> Puviarasu
>


Re: Quick questions on segments and page map buckets

2018-07-12 Thread Dmitry Pavlov
Hi, I've double checked code regarding question 1:

PageMemoryImpl#segments segments count (len) comes from sizes array len.
Sizes array come to page memory from
GridCacheDatabaseSharedManager.calculateFragmentSizes(). This method which
gets availableProcessors from runtime (CPU count). I didn't find any shift
to SEG_BITS.

It can be chaged by DataStorageConfiguration.setConcurrencyLevel() but by
default is the same with #CPU.

Which is why I mentioned segments count = CPU count by default in wiki.

Recenly some member of community proposed update to offical doc about
segments count. So now it states #segments=#CPU.

So I guess for 8 CPU we will have 8 segments.

Please correct me if I missing something.

Sincerely,
Dmitriy Pavlov

ср, 27 июн. 2018 г. в 15:30, Eduard Shangareev :

> Dmitry,
>
> I mean Chugunov, but I have questioned him. His answer was the A. Goncharuk
> should now the answer.
>
> On Wed, Jun 27, 2018 at 2:58 PM, Dmitry Pavlov 
> wrote:
>
> > John, is this question still actual?
> >
> > пт, 22 июн. 2018 г. в 15:18, Dmitry Pavlov :
> >
> > > Hi Ed,
> > >
> > > Which Sergey do you mean? I know a number of contributors.
> > >
> > > Sincerely,
> > >
> > >
> > > вт, 19 июн. 2018 г. в 22:15, Eduard Shangareev <
> > > eduard.shangar...@gmail.com>:
> > >
> > >> Hi,
> > >>
> > >> 1. It looks weird, yeah. Need to ask Sergey, who has changed it last
> > time.
> > >>
> > >> 2. Because we could reuse memory. For example, after cache destroy or
> > >> something like that.
> > >>
> > >> On Tue, Jun 19, 2018 at 9:58 PM, John Wilson  >
> > >> wrote:
> > >>
> > >> > Hi,
> > >> >
> > >> > Two quick questions:
> > >> >
> > >> >
> > >> >1. The design documentation here,
> > >> >https://cwiki.apache.org/confluence/display/IGNITE/
> > >> > Ignite+Durable+Memory+-+under+the+hood,
> > >> >states that the default segment count is equal to the number of
> > >> logical
> > >> >cores available in the underlying machine. However, the segments
> > >> array
> > >> > in
> > >> >PageMemory indicates that the maximum number of segments is: 1 <<
> > >> > SEG_BITS.
> > >> >Since SEG_BITS = 4, the max # segments is 16. Did I miss
> something
> > >> here?
> > >> >2. Reading the code in PageMemoryNoStoreImp, it looks like pages
> > are
> > >> >allocated segment sequentially in a bump-the-pointer strategy
> where
> > >> the
> > >> >first 8 bytes of a segment hold a pointer to the index of the
> last
> > >> >allocated page. If this is true, then I don't understand the
> point
> > of
> > >> >having a page map buckets. Why not use a simple arithmetic index
> *
> > >> > pageSize
> > >> >to get the offset of a page?
> > >> >
> > >> > Thanks.
> > >> > John
> > >> >
> > >>
> > >
> >
>


Re: Async cache groups rebalance not started with rebalanceOrder ZERO

2018-07-12 Thread Dmitry Pavlov
Hi Ilya,

Do you know, what is correct: behaviour or javadoc?

Sincerely,
Dmitriy Pavlov

пн, 9 июл. 2018 г. в 16:43, Maxim Muzafarov :

> Hello Igniters,
>
> Each cache group has “rebalance order” property. As javadoc for
> getRebalanceOrder() says: “Note that cache with order {@code 0} does not
> participate in ordering. This means that cache with rebalance order {@code
> 0} will never wait for any other caches. All caches with order {@code 0}
> will be rebalanced right away concurrently with each other and ordered
> rebalance processes. If not set, cache order is 0, i.e. rebalancing is not
> ordered.”
>
> In fact GridCachePartitionExchangeManager always build the chain of
> rebalancing cache groups to start (even for cache order ZERO):
>
> ignite-sys-cache -> cacheR -> cacheR3 -> cacheR2 -> cacheR5 -> cacheR1.
>
> If one of these groups will fail to start further groups will never be run.
>
> * Question 1*: Should we fix javadoc description or create a bug for fixing
> such rebalance behavior?
>
> [1]
>
> https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/GridCachePartitionExchangeManager.java#L2630
>


RDD spark 2.10 version upgrade & TC suites

2018-07-12 Thread Dmitry Pavlov
Hi Igniters,

Do we need
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_RddSpark210=%3Cdefault%3E=buildTypeStatusDiv
suite is always fails with exit code 1 and I think I saw discussion about
version change.

Could I remove this suite from RunAll?

Sincerely,
Dmitriy Pavlov


Re: MTCGA: new failures in builds [1479951] needs to be handled

2018-07-12 Thread Dmitry Pavlov
I've pushed fix of failure to master.

чт, 12 июл. 2018 г. в 16:25, Dmitry Pavlov :

> Hi Igniters,
>
> this notification was generated because this test was stable passing (at
> least 5 ok) in master and became stable failed (at least 3 failures).
>
> Such notifications would not be generated for each case of flaky failures,
> so I hope this feature will help us to identify and fix new failures.
>
> I'll fix message format to be more readable soon.
>
> It would be pleasure to me to run short talk (webinar) about tests, MTCGA,
> and MTCGA.Bot (Ignite TC helper). Please reply if you are interested.
>
> I would also highly appreciate any kind of feedback.
>
> Sincerely,
> Dmitriy Pavlov
>
> чт, 12 июл. 2018 г. в 16:14, :
>
>> Hi Ignite Developer,
>>
>> I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed.
>> I hope you can help.
>>
>>  *New test failure in master
>> IgnitePdsCheckpointSimulationWithRealCpDisabledTest.testCheckpointSimulationMultiThreaded
>>
>> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-1615751728537497724=%3Cdefault%3E=testDetails
>>  Changes may led to failure were done by alexey.goncharuk
>> http://ci.ignite.apache.org/viewModification.html?modId=825445=false,
>> eshangareev
>> http://ci.ignite.apache.org/viewModification.html?modId=825442=false,
>> sergey.chugunov
>> http://ci.ignite.apache.org/viewModification.html?modId=825439=false,
>> irakov
>> http://ci.ignite.apache.org/viewModification.html?modId=825436=false,
>> irakov
>> http://ci.ignite.apache.org/viewModification.html?modId=825428=false,
>> ivandasch
>> http://ci.ignite.apache.org/viewModification.html?modId=825411=false,
>> sbt-pereslegin-pa1
>> http://ci.ignite.apache.org/viewModification.html?modId=825407=false,
>> alexey.scherbakoff
>> http://ci.ignite.apache.org/viewModification.html?modId=825404=false,
>> akuznetsov
>> http://ci.ignite.apache.org/viewModification.html?modId=825396=false,
>> vsisko
>> http://ci.ignite.apache.org/viewModification.html?modId=825371=false,
>> pivanov
>> http://ci.ignite.apache.org/viewModification.html?modId=825366=false,
>> dmitriyff
>> http://ci.ignite.apache.org/viewModification.html?modId=825351=false,
>> dmitriyff
>> http://ci.ignite.apache.org/viewModification.html?modId=825348=falseIf
>> your changes can led to this failure(s), please create issue with label
>> MakeTeamCityGreenAgain and assign it to you.If you have fix, please
>> set ticket to PA state and write to dev list fix is readyFor case
>> fix will require some time please mute test and set label Muted_Test to
>> issueIf you know which change caused failure please
>> contact change author directlyIf you don't know which change
>> caused failure please send message to dev list to find
>> outShould you have any questions please contact
>> dpav...@apache.org or write to dev.listBest
>> Regards,MTCGA.BotNotification generated at Thu Jul 12 16:14:23 MSK
>> 2018
>
>


Re: PR Reivew https://github.com/apache/ignite/pull/4300

2018-07-12 Thread Dmitry Pavlov
Hi,

Yes, correct. In the same time I've checked branch state with custom tool,
so we can be pretty sure change does not introduce new failures.

I merged your changes, in the same time I needed to do several updates in
code (see details in ticket comments).

Looking forward to your contributions!

Sincerely,
Dmitriy Pavlov

P.S. Additional references for you that should boost your onboarding.

https://cwiki.apache.org/confluence/display/IGNITE/Coding+Guidelines

https://cwiki.apache.org/confluence/display/IGNITE/Abbreviation+Rules

https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute


чт, 12 июл. 2018 г. в 13:32, Ken Cheng :

> Thank you very much!
>
> If it's the case of what you said, a merge from latest main to this branch
> will fix this issue?
>
> Thanks,
> Ken Cheng
>
>
> On Thu, Jul 12, 2018 at 6:16 PM Dmitry Pavlov 
> wrote:
>
> > Hi,
> >
> > I've checked this results and I guess branch was created at some unlucky
> > moment, and currently most of timeouts were fixed in master.
> >
> > "No changes" mean Teamcity does not detected changes between runs.
> Probably
> > I've scheduled re-run for some particular suites more than one time.
> >
> > I'll take a look to PR itself.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > чт, 12 июл. 2018 г. в 11:39, kcheng.mvp :
> >
> > > Here is the latest TC result
> > >
> > >
> > > The high-lighted part shows as  "no changes", which mean my changes
> would
> > > not cause the failure, right?
> > >
> > >
> > >
> > >
> > >
> >
> https://ci.ignite.apache.org/viewLog.html?buildId=1480732=buildResultsDiv=IgniteTests24Java8_RunAll
> > > <http://apache-ignite-developers.2346864.n4.nabble.com/file/t85/tc.png
> >
> > >
> > >
> > >
> > > --
> > > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
> > >
> >
>


Re: Start contributing to Apache Ignite

2018-07-12 Thread Dmitry Pavlov
Hi Igniters,

bumping up. Issue is still in PA.

Ed has looked to patch and add some changes. Who could pick up this review?

Sincerely,
Dmitriy Pavlov

вт, 12 сент. 2017 г. в 11:43, Mikhail Lipkovich :

> Thanks a lot Denis!
>
> Will try to do something useful
>
> Mikhail
>
> 2017-09-12 3:41 GMT+03:00 Denis Magda :
>
> > Mikhail, welcome!
> >
> > Granted you required permissions! Look forward to your contributions!
> >
> > —
> > Denis
> >
> > > On Sep 11, 2017, at 4:33 AM, Mikhail Lipkovich <
> > lipkovich.mikh...@gmail.com> wrote:
> > >
> > > Hello,
> > >
> > > I would like to start contributing to Ignite.
> > > This issue seems suitable for me
> > > https://issues.apache.org/jira/browse/IGNITE-6284
> > >
> > > Can I get permissions to assign issues to myself?
> > >
> > > My username at issues.apache.org is mlipkovich
> > > Full name is Mikhail Lipkovich
> > >
> > >
> > >
> > > Thanks,
> > >
> > > Mikhail
> >
> >
>


Re: Ignite guide for community developes

2018-07-12 Thread Dmitry Pavlov
Hi Igniters,

I totally agree with Yakov and vgrigorev.

Could you share wiki ID so you can contribute these proposals at least as
Ignite Enhancement Proposal (IEP)?

You can share your apache wiki ID to add contibutor permission, so you will
be able to create wiki page.

Would you like to contribute some from proposed topics as wiki pages or
separate guide?

Sincerely,
Dmitriy Pavlov

чт, 12 июл. 2018 г. в 15:13, Yakov Zhdanov :

> 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 in Ignite development but
> > tries of this is typically not successful due to big barrier to begin
> > develop to such a complex project.During Moscow Ignite Meetup #3  we were
> > discussed with GridGain presenters that for attracting community to
> > development process  creating a good guide can be crucial and I want to
> > propose create such a guide.For the proposal to be more concrete and
> > substantial I write document with my vision of basic organization,
> problem
> > aspects that stops developers, sample of such documentation from really
> > successful community.File is attached.Please consider and discuss
> > Proposal_for_Ignite_development_guide.docx
> >  > com/file/t544/Proposal_for_Ignite_development_guide.docx>
> > this proposal.
> >
> >
> >
> > --
> > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>


Re: MTCGA: new failures in builds [1479951] needs to be handled

2018-07-12 Thread Dmitry Pavlov
Hi Igniters,

this notification was generated because this test was stable passing (at
least 5 ok) in master and became stable failed (at least 3 failures).

Such notifications would not be generated for each case of flaky failures,
so I hope this feature will help us to identify and fix new failures.

I'll fix message format to be more readable soon.

It would be pleasure to me to run short talk (webinar) about tests, MTCGA,
and MTCGA.Bot (Ignite TC helper). Please reply if you are interested.

I would also highly appreciate any kind of feedback.

Sincerely,
Dmitriy Pavlov

чт, 12 июл. 2018 г. в 16:14, :

> Hi Ignite Developer,
>
> I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed.
> I hope you can help.
>
>  *New test failure in master
> IgnitePdsCheckpointSimulationWithRealCpDisabledTest.testCheckpointSimulationMultiThreaded
>
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-1615751728537497724=%3Cdefault%3E=testDetails
>  Changes may led to failure were done by alexey.goncharuk
> http://ci.ignite.apache.org/viewModification.html?modId=825445=false,
> eshangareev
> http://ci.ignite.apache.org/viewModification.html?modId=825442=false,
> sergey.chugunov
> http://ci.ignite.apache.org/viewModification.html?modId=825439=false,
> irakov
> http://ci.ignite.apache.org/viewModification.html?modId=825436=false,
> irakov
> http://ci.ignite.apache.org/viewModification.html?modId=825428=false,
> ivandasch
> http://ci.ignite.apache.org/viewModification.html?modId=825411=false,
> sbt-pereslegin-pa1
> http://ci.ignite.apache.org/viewModification.html?modId=825407=false,
> alexey.scherbakoff
> http://ci.ignite.apache.org/viewModification.html?modId=825404=false,
> akuznetsov
> http://ci.ignite.apache.org/viewModification.html?modId=825396=false,
> vsisko
> http://ci.ignite.apache.org/viewModification.html?modId=825371=false,
> pivanov
> http://ci.ignite.apache.org/viewModification.html?modId=825366=false,
> dmitriyff
> http://ci.ignite.apache.org/viewModification.html?modId=825351=false,
> dmitriyff
> http://ci.ignite.apache.org/viewModification.html?modId=825348=falseIf
> your changes can led to this failure(s), please create issue with label
> MakeTeamCityGreenAgain and assign it to you.If you have fix, please
> set ticket to PA state and write to dev list fix is readyFor case
> fix will require some time please mute test and set label Muted_Test to
> issueIf you know which change caused failure please
> contact change author directlyIf you don't know which change
> caused failure please send message to dev list to find
> outShould you have any questions please contact
> dpav...@apache.org or write to dev.listBest
> Regards,MTCGA.BotNotification generated at Thu Jul 12 16:14:23 MSK
> 2018


Re: Contribution

2018-07-12 Thread Dmitry Pavlov
Hi Ivan,

Welcome to the Ignite Community.

I've added you to contributors list, so you can now assign issue to
yourself.

Looking forward to your contributions!

Sincerely,
Dmitriy Pavlov

P.S. Additional references for you that should boost your onboarding.

Please subscribe to both dev and user lists:
https://ignite.apache.org/community/resources.html#mail-lists

Get familiar with Ignite development process described here:
https://cwiki.apache.org/confluence/display/IGNITE/Development+Process

Instructions on how to contribute can be found here:
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute

Project setup in Intellij IDEA:
https://cwiki.apache.org/confluence/display/IGNITE/Project+Setup


чт, 12 июл. 2018 г. в 16:08, Павлухин Иван :

> Hi Igniters,
>
> I would like to start working on
> https://issues.apache.org/jira/browse/IGNITE-8581
> My name in Jira is Pavlukhin
>
> --
> Best regards,
> Ivan Pavlukhin
>


Re: Cases of using AffinityAssignment.clientEventChange method

2018-07-12 Thread Dmitry Pavlov
Sute. I like this idea, let's wait.

чт, 12 июл. 2018 г. в 14:48, Maxim Muzafarov :

> Dmity,
>
> Thank you for reply. I've maked this ticket with "newbie" tag.
>
> I would like to keep this ticket for our new community members. Change is
> really simple, so we can easily guide new mebers the development processes
> adopted by our community.
>
> Hope this issue will find its author.
> If not I'll do it by myself.
>
>
> пт, 6 июл. 2018 г. в 16:09, Dmitry Pavlov :
>
> > Hi Maxim,
> >
> > Thank you for your efforts to finding this out. I also didn't find any
> > usages, so I agree here.
> >
> > I'm going to commit this by lazy consensus if no-one objects within the
> > next three days.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > чт, 5 июл. 2018 г. в 12:56, Maxim Muzafarov :
> >
> > > Hello everyone,
> > >
> > > Suppose clientEventChange method is useless and have confusing name.
> > >
> > > I'm suggesting to remove it as not used. I've filed issue for it:
> > >
> > > https://issues.apache.org/jira/browse/IGNITE-8936
> > >
> > >
> > > чт, 28 июн. 2018 г. в 16:53, Maxim Muzafarov :
> > >
> > > > Hi Igniters,
> > > >
> > > > Recently I've faced with AffinityAssignment.clientEventChange()
> method
> > > and
> > > > not completly sure about the range of its applicability. The javadoc
> > says
> > > > "return {@code True} if related discovery event did not cause
> affinity
> > > > assignment change and this assignment is just reference to the
> previous
> > > > one."
> > > >
> > > > Three facts about it:
> > > > 1) Method is the part of internal Ignite API
> > > > 2) It​ is​ not used anywhere in Ignite project code
> > > > 3) "clientEventChage" confusing name for this method. "true" value
> can
> > be
> > > > set not only by client-related events (e.g. cacheChangeRequest,
> > > > affinityChangeRequest etc.).
> > > >
> > > > I've prepared diagram when it has "TRUE" value [1].
> > > >
> > > > * Question #1 * When and for what cases we can use returned value of
> > this
> > > > method?
> > > > * Question #2 * Can it be removed? My suggestion is to keep internal
> > API
> > > > as simple as possible.
> > > >
> > > >
> > > > [1] https://image.ibb.co/cW6Mx8/Client_Event_Change_1.png
> > > >
> > >
> >
>


Re: PR Reivew https://github.com/apache/ignite/pull/4300

2018-07-12 Thread Dmitry Pavlov
Hi,

I've checked this results and I guess branch was created at some unlucky
moment, and currently most of timeouts were fixed in master.

"No changes" mean Teamcity does not detected changes between runs. Probably
I've scheduled re-run for some particular suites more than one time.

I'll take a look to PR itself.

Sincerely,
Dmitriy Pavlov

чт, 12 июл. 2018 г. в 11:39, kcheng.mvp :

> Here is the latest TC result
>
>
> The high-lighted part shows as  "no changes", which mean my changes would
> not cause the failure, right?
>
>
>
>
> https://ci.ignite.apache.org/viewLog.html?buildId=1480732=buildResultsDiv=IgniteTests24Java8_RunAll
> 
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>


Re: PR Reivew https://github.com/apache/ignite/pull/4300

2018-07-11 Thread Dmitry Pavlov
Hi,

Thanks to Stanislav L. for review. In the same time TC was not re-runned
after changes and there is several suspicious failures in PR, so I've
retriggered run-all. Let's wait for results and I'll check it one more time.

Sincerely,
Dmitriy Pavlov

вт, 10 июл. 2018 г. в 20:52, kcheng.mvp :

> Dear igniters,
>
> please help do the code review for jira
> https://issues.apache.org/jira/browse/IGNITE-8776
> https://github.com/apache/ignite/pull/4300
>
> Thanks,
> kcheng.mvp
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>


Re: [VOTE] Apache Ignite 2.6.0 RC1

2018-07-11 Thread Dmitry Pavlov
+1, checked RC   ver. 2.6.0#20180710-sha1:669feacc  as new DB for Ignite TC
helper (MTCGA.Bot). Data was sucessfully restored from 2.5, tool is
operational.

I suggest to publish link to staging in vote threads. It is very convinient
as I can add to gradle only

maven {
url 
"https://repository.apache.org/content/repositories/orgapacheignite-1426/;
}

and check RC.

ср, 11 июл. 2018 г. в 19:48, Andrey Gura :

> +1 (binding)
>
> Checked:
>
> - build from sources;
> - artifacts' hashes;
> - examples.
>
>
> On Wed, Jul 11, 2018 at 5:06 PM Dmitry Pavlov 
> wrote:
> >
> > Anton, I totally agree it is needed, but not sure I'll have free time to
> do
> > it soon. I will keep community posted.
> >
> > ср, 11 июл. 2018 г. в 17:01, Anton Vinogradov :
> >
> > > Ilya,
> > >
> > > thanks for detailed explanation.
> > >
> > > +1 now (binding).
> > >
> > > Dmitry Pavlov,
> > >
> > > could you please accumulate discussed and prepare documentation about
> "how
> > > to release Apache Ignite step by step"?
> > >
> > >
> > > ср, 11 июл. 2018 г. в 16:57, Ilya Suntsov :
> > >
> > > > Anton,
> > > >
> > > > Module spark-2.10 and optional lib ignite-spark_2.10 were removed
> during
> > > > the work on IGNITE-8534 <
> > > https://issues.apache.org/jira/browse/IGNITE-8534
> > > > >
> > > >
> > > > IGNITE-8768 <https://issues.apache.org/jira/browse/IGNITE-8768>:
> > > >
> > > > +
> > > >
> > >
> modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/dht/EvictionContext.java
> > > >
> > > > IGNITE-8804 <https://issues.apache.org/jira/browse/IGNITE-8804>:
> > > >
> > > > + config/wsl-default-config.xml
> > > >
> > > > IGNITE-8685 <
> > > > https://issues.apache.org/jira/browse/IGNITE-8685?src=confmacro>:
> > > >
> > > > -
> > > >
> > >
> modules/core/src/main/java/org/apache/ignite/internal/pagemem/wal/record/BaselineTopologyRecord.java
> > > >
> > > > -
> > > >
> > >
> modules/core/src/main/java/org/apache/ignite/internal/processors/cache/persistence/wal/serializer/BaselineTopologyRecordSerializer.java
> > > >
> > > >
> > > > Other changes are tests that were added.
> > > >
> > > >
> > > > 2018-07-11 16:28 GMT+03:00 Anton Vinogradov :
> > > >
> > > > > Ilya,
> > > > >
> > > > > Please confirm that all changes [1] expected
> > > > > [1]
> > > > >
> > > >
> > >
> https://ci.ignite.apache.org/repository/download/ApacheIgniteReleaseJava8_
> > > > > IgniteRelease72CheckFileConsistency/1478134:id/results/result.log
> > > > >
> > > > > ср, 11 июл. 2018 г. в 16:23, Ilya Suntsov :
> > > > >
> > > > > > Anton,
> > > > > >
> > > > > > Please take a look at:
> > > > > >
> > > > > > https://ci.ignite.apache.org/viewLog.html?buildId=1478134;
> > > > > tab=buildResultsDiv=ApacheIgniteReleaseJava8_
> > > > > IgniteRelease72CheckFileConsistency
> > > > > >
> > > > > > https://ci.ignite.apache.org/viewLog.html?buildId=1478557;
> > > > > tab=buildResultsDiv=ApacheIgniteReleaseJava8_
> > > > > PrepareVote4CheckRcLicensesChecksum
> > > > > >
> > > > > > Dmitry,
> > > > > >
> > > > > > These steps should be outside the chain.
> > > > > >
> > > > > > 2018-07-11 14:49 GMT+03:00 Anton Vinogradov :
> > > > > >
> > > > > > > Automation possible, but it's hard to determine previous
> version
> > > > > > > automatically (especially when you have 2.x and 3.x releasing
> > > > > > concurrently)
> > > > > > > for API check [1],
> > > > > > > but RC check [1] can be chained.
> > > > > > >
> > > > > > > [1]
> > > > > > > https://ci.ignite.apache.org/viewType.html?buildTypeId=
> > > > > > >
> ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency=
> > > > > > >
> > > buildTypeHistoryList_ApacheIgniteRele

Re: [VOTE] Apache Ignite 2.6.0 RC1

2018-07-11 Thread Dmitry Pavlov
Anton, I totally agree it is needed, but not sure I'll have free time to do
it soon. I will keep community posted.

ср, 11 июл. 2018 г. в 17:01, Anton Vinogradov :

> Ilya,
>
> thanks for detailed explanation.
>
> +1 now (binding).
>
> Dmitry Pavlov,
>
> could you please accumulate discussed and prepare documentation about "how
> to release Apache Ignite step by step"?
>
>
> ср, 11 июл. 2018 г. в 16:57, Ilya Suntsov :
>
> > Anton,
> >
> > Module spark-2.10 and optional lib ignite-spark_2.10 were removed during
> > the work on IGNITE-8534 <
> https://issues.apache.org/jira/browse/IGNITE-8534
> > >
> >
> > IGNITE-8768 <https://issues.apache.org/jira/browse/IGNITE-8768>:
> >
> > +
> >
> modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/dht/EvictionContext.java
> >
> > IGNITE-8804 <https://issues.apache.org/jira/browse/IGNITE-8804>:
> >
> > + config/wsl-default-config.xml
> >
> > IGNITE-8685 <
> > https://issues.apache.org/jira/browse/IGNITE-8685?src=confmacro>:
> >
> > -
> >
> modules/core/src/main/java/org/apache/ignite/internal/pagemem/wal/record/BaselineTopologyRecord.java
> >
> > -
> >
> modules/core/src/main/java/org/apache/ignite/internal/processors/cache/persistence/wal/serializer/BaselineTopologyRecordSerializer.java
> >
> >
> > Other changes are tests that were added.
> >
> >
> > 2018-07-11 16:28 GMT+03:00 Anton Vinogradov :
> >
> > > Ilya,
> > >
> > > Please confirm that all changes [1] expected
> > > [1]
> > >
> >
> https://ci.ignite.apache.org/repository/download/ApacheIgniteReleaseJava8_
> > > IgniteRelease72CheckFileConsistency/1478134:id/results/result.log
> > >
> > > ср, 11 июл. 2018 г. в 16:23, Ilya Suntsov :
> > >
> > > > Anton,
> > > >
> > > > Please take a look at:
> > > >
> > > > https://ci.ignite.apache.org/viewLog.html?buildId=1478134;
> > > tab=buildResultsDiv=ApacheIgniteReleaseJava8_
> > > IgniteRelease72CheckFileConsistency
> > > >
> > > > https://ci.ignite.apache.org/viewLog.html?buildId=1478557;
> > > tab=buildResultsDiv=ApacheIgniteReleaseJava8_
> > > PrepareVote4CheckRcLicensesChecksum
> > > >
> > > > Dmitry,
> > > >
> > > > These steps should be outside the chain.
> > > >
> > > > 2018-07-11 14:49 GMT+03:00 Anton Vinogradov :
> > > >
> > > > > Automation possible, but it's hard to determine previous version
> > > > > automatically (especially when you have 2.x and 3.x releasing
> > > > concurrently)
> > > > > for API check [1],
> > > > > but RC check [1] can be chained.
> > > > >
> > > > > [1]
> > > > > https://ci.ignite.apache.org/viewType.html?buildTypeId=
> > > > > ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency=
> > > > >
> buildTypeHistoryList_ApacheIgniteReleaseJava8=__all_branches__
> > > > > [2]
> > > > > https://ci.ignite.apache.org/viewType.html?buildTypeId=
> > > > > ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum=
> > > > >
> buildTypeHistoryList_ApacheIgniteReleaseJava8=__all_branches__
> > > > >
> > > > > ср, 11 июл. 2018 г. в 14:44, Dmitry Pavlov  >:
> > > > >
> > > > > > No, I just wondering if it could be in chain. If manual run is
> > > > requires I
> > > > > > guess we could document it somewhere, so everyone in community
> will
> > > be
> > > > > > aware what should be done.
> > > > > >
> > > > > > ср, 11 июл. 2018 г. в 14:41, Petr Ivanov :
> > > > > >
> > > > > > > Currently, I have no knowledge about this build types and
> theirs
> > > > > purpose.
> > > > > > >
> > > > > > > I guess release engineer has to run them manually with
> ignite-2.6
> > > > > branch
> > > > > > > or with 2.6.0-rc1 build result.
> > > > > > > Should I do it?
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On 11 Jul 2018, at 14:36, Dmitry Pavlov  >
> > > > wrote:
> > > 

Re: [VOTE] Apache Ignite 2.6.0 RC1

2018-07-11 Thread Dmitry Pavlov
No, I just wondering if it could be in chain. If manual run is requires I
guess we could document it somewhere, so everyone in community will be
aware what should be done.

ср, 11 июл. 2018 г. в 14:41, Petr Ivanov :

> Currently, I have no knowledge about this build types and theirs purpose.
>
> I guess release engineer has to run them manually with ignite-2.6 branch
> or with 2.6.0-rc1 build result.
> Should I do it?
>
>
>
>
> On 11 Jul 2018, at 14:36, Dmitry Pavlov  wrote:
>
> I thought these steps are to be run automatically within chain and no
> manual steps are required.
>
> Petr, please step in.
>
> ср, 11 июл. 2018 г. в 14:30, Anton Vinogradov :
>
>> I do NOT see that API was checked [1] and automated check [2] performed
>>
>> [1]
>>
>> https://ci.ignite.apache.org/viewType.html?buildTypeId=ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency=buildTypeHistoryList_ApacheIgniteReleaseJava8=__all_branches__
>> [2]
>>
>> https://ci.ignite.apache.org/viewType.html?buildTypeId=ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum=buildTypeHistoryList_ApacheIgniteReleaseJava8=__all_branches__
>>
>> ср, 11 июл. 2018 г. в 14:25, Alexey Kuznetsov :
>>
>> > +1 (binding)
>> >
>> > Download sources:   OK
>> > Build from sources: OK
>> > Run ignite.bat: OK
>> >
>> > --
>> > Alexey Kuznetsov
>> >
>>
>
>


Re: [VOTE] Apache Ignite 2.6.0 RC1

2018-07-11 Thread Dmitry Pavlov
I thought these steps are to be run automatically within chain and no
manual steps are required.

Petr, please step in.

ср, 11 июл. 2018 г. в 14:30, Anton Vinogradov :

> I do NOT see that API was checked [1] and automated check [2] performed
>
> [1]
>
> https://ci.ignite.apache.org/viewType.html?buildTypeId=ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency=buildTypeHistoryList_ApacheIgniteReleaseJava8=__all_branches__
> [2]
>
> https://ci.ignite.apache.org/viewType.html?buildTypeId=ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum=buildTypeHistoryList_ApacheIgniteReleaseJava8=__all_branches__
>
> ср, 11 июл. 2018 г. в 14:25, Alexey Kuznetsov :
>
> > +1 (binding)
> >
> > Download sources:   OK
> > Build from sources: OK
> > Run ignite.bat: OK
> >
> > --
> > Alexey Kuznetsov
> >
>


Re: Subscription

2018-07-11 Thread Dmitry Pavlov
Hi Ivan,

it seems you've already subscribed.

To subscribe it is sufficient to send emal to
dev-subscr...@ignite.apache.org

https://ignite.apache.org/community/resources.html#mail-lists

Sincerely,
Dmitriy Pavlov

ср, 11 июл. 2018 г. в 4:20, Павлухин Иван :

> Hi,
>
> Please subscribe me.
>
> --
> Best regards,
> Ivan Pavlukhin
>


Re: About readme.io's latest docs

2018-07-10 Thread Dmitry Pavlov
Great, thanks for letting me know.

вт, 10 июл. 2018 г. в 4:01, 李玉珏@163 <18624049...@163.com>:

> I have received the attachments.
>
> 在 2018/7/10 上午6:23, Prachi Garg 写道:
> > I already sent him the export, but the attachments were huge. I think
> > that's why the email reply was not received by the dev list.
> >
> > -P
> >
> > On Mon, Jul 9, 2018 at 2:33 PM, Dmitry Pavlov 
> wrote:
> >
> >> Igniters, was this question solved? Is it possible to do such export?
> >>
> >> пт, 1 июн. 2018 г. в 19:40, 李玉珏@163 <18624049...@163.com>:
> >>
> >>> Prachi,
> >>>
> >>>
> >>> Can you help to export all the latest version of all documents to me?
> >>> I am ready to make a synchronization of the chinese version of the
> >>> document.
> >>>
> >>> thanks!
> >>>
> >>>
> >>> 在 2017/11/24 下午1:33, Prachi Garg 写道:
> >>>> Attached.
> >>>>
> >>>> On Wed, Nov 15, 2017 at 4:41 AM, 李玉珏@163 <18624049...@163.com
> >>>> <mailto:18624049...@163.com>> wrote:
> >>>>
> >>>>  Prachi,
> >>>>
> >>>>
> >>>>  Can you help me to export all the latest version of all documents
> >>>>  to me?
> >>>>  I am ready to make a synchronization of the chinese version of
> the
> >>>>  document.
> >>>>
> >>>>  thanks!
> >>>>
> >>>>  在 2017/8/17 上午2:05, Prachi Garg 写道:
> >>>>>  Please see attached.
> >>>>>
> >>>>>  -P
> >>>>>
> >>>>>  On Wed, Aug 9, 2017 at 11:19 AM, Denis Magda <
> dma...@gridgain.com
> >>>>>  <mailto:dma...@gridgain.com>> wrote:
> >>>>>
> >>>>>  Hi!
> >>>>>
> >>>>>  Prachi is on vacation and will send you the latest version
> as
> >>>>>  soon as she is back to work.
> >>>>>
> >>>>>  —
> >>>>>  Denis
> >>>>>
> >>>>>>  On Aug 7, 2017, at 5:33 AM, 李玉珏@163 <18624049...@163.com
> >>>>>>  <mailto:18624049...@163.com>> wrote:
> >>>>>>
> >>>>>>
> >>>>>>  Prachi,
> >>>>>>
> >>>>>>
> >>>>>>  Can you help me to export all the latest version of all
> >>>>>>  documents to me?
> >>>>>>  I am ready to make a synchronization of the chinese version
> >>>>>>  of the document.
> >>>>>>
> >>>>>>  thanks!
> >>>>>>
> >>>>>>
> >>>>>>  在 2017/5/13 上午12:48, Prachi Garg 写道:
> >>>>>>>  See attached for cpp, .net and integrations documentation.
> >>>>>>>
> >>>>>>>  -P
> >>>>>>>
> >>>>>>>  On Fri, May 12, 2017 at 9:47 AM, Prachi Garg
> >>>>>>>  mailto:pg...@gridgain.com>> wrote:
> >>>>>>>
> >>>>>>>  See attached for java, file-system, and tools
> >>>>>>>  documentation.
> >>>>>>>
> >>>>>>>  -P
> >>>>>>>
> >>>>>>>  On Fri, May 12, 2017 at 5:39 AM, 李玉珏@163
> >>>>>>>  <18624049...@163.com <mailto:18624049...@163.com>>
> >>> wrote:
> >>>>>>>  Prachi,
> >>>>>>>
> >>>>>>>
> >>>>>>>  Can you help me to export all the latest version
> of
> >>>>>>>  all documents to me?
> >>>>>>>  I am ready to make a synchronization of the
> chinese
> >>>>>>>  version of the document.
> >>>>>>>
> >>>>>>>  thanks!
> >>>>>>>
> >>>>>>>
> >>>>>>>  在 2017/3/18 04:54, Prachi 

Re: About readme.io's latest docs

2018-07-09 Thread Dmitry Pavlov
Igniters, was this question solved? Is it possible to do such export?

пт, 1 июн. 2018 г. в 19:40, 李玉珏@163 <18624049...@163.com>:

> Prachi,
>
>
> Can you help to export all the latest version of all documents to me?
> I am ready to make a synchronization of the chinese version of the
> document.
>
> thanks!
>
>
> 在 2017/11/24 下午1:33, Prachi Garg 写道:
> > Attached.
> >
> > On Wed, Nov 15, 2017 at 4:41 AM, 李玉珏@163 <18624049...@163.com
> > > wrote:
> >
> > Prachi,
> >
> >
> > Can you help me to export all the latest version of all documents
> > to me?
> > I am ready to make a synchronization of the chinese version of the
> > document.
> >
> > thanks!
> >
> > 在 2017/8/17 上午2:05, Prachi Garg 写道:
> >> Please see attached.
> >>
> >> -P
> >>
> >> On Wed, Aug 9, 2017 at 11:19 AM, Denis Magda  >> > wrote:
> >>
> >> Hi!
> >>
> >> Prachi is on vacation and will send you the latest version as
> >> soon as she is back to work.
> >>
> >> —
> >> Denis
> >>
> >>> On Aug 7, 2017, at 5:33 AM, 李玉珏@163 <18624049...@163.com
> >>> > wrote:
> >>>
> >>>
> >>> Prachi,
> >>>
> >>>
> >>> Can you help me to export all the latest version of all
> >>> documents to me?
> >>> I am ready to make a synchronization of the chinese version
> >>> of the document.
> >>>
> >>> thanks!
> >>>
> >>>
> >>> 在 2017/5/13 上午12:48, Prachi Garg 写道:
>  See attached for cpp, .net and integrations documentation.
> 
>  -P
> 
>  On Fri, May 12, 2017 at 9:47 AM, Prachi Garg
>  mailto:pg...@gridgain.com>> wrote:
> 
>  See attached for java, file-system, and tools
>  documentation.
> 
>  -P
> 
>  On Fri, May 12, 2017 at 5:39 AM, 李玉珏@163
>  <18624049...@163.com > wrote:
> 
>  Prachi,
> 
> 
>  Can you help me to export all the latest version of
>  all documents to me?
>  I am ready to make a synchronization of the chinese
>  version of the document.
> 
>  thanks!
> 
> 
>  在 2017/3/18 04:54, Prachi Garg 写道:
> > Hi,
> >
> > Please see attached.
> >
> > -P
> >
> > On Fri, Mar 17, 2017 at 4:56 AM, 李玉珏@163
> > <18624049...@163.com >
> > wrote:
> >
> > Prachi,
> >
> >
> > Can you help me to export all the latest
> > version of all documents to me?
> > I am ready to make a synchronization of the
> > chinese version of the document.
> >
> >
> > 在 2016/12/21 00:55, Prachi Garg 写道:
> >> Hi,
> >> I have attached the documentation for
> >> Hadoop/Spark and Integrations.
> >>
> >> -Prachi
> >>
> >> On Tue, Dec 20, 2016 at 6:50 AM, 李玉珏@163
> >> <18624049...@163.com
> >> > wrote:
> >>
> >> Hi,
> >>
> >>
> >> Hadoop Accelerator,about MapR env's
> >> install and config,is this part of the
> >> document missing?
> >>
> >>
> >> 在 2016/12/19 11:24, Denis Magda 写道:
> >>> Hi,
> >>>
> >>> Yes, the documentation is stable.
> >>> Prachi, could you help out with the
> >>> exporting?
> >>>
> >>> —
> >>> Denis
> >>>
>  On Dec 18, 2016, at 7:09 AM, 李玉珏@163
>  <18624049...@163.com
>  > wrote:
> 
>  Prachi,
> 
>  I would like to ask, 1.8 version of the
>  document, is now in a stable state?
>  If it is stable, can you help me to
>  export the latest version of all
>  documents to me?
>  I am ready to make a synchronization of
>  the chinese version of the document.
> 
>   

Re: PR for https://issues.apache.org/jira/browse/IGNITE-8956

2018-07-09 Thread Dmitry Pavlov
Done. Thank you for contribution and for review.

пн, 9 июл. 2018 г. в 12:37, Vyacheslav Daradur :

> Now changes look good to me.
>
> Dmitry, could you help with a final review and merge, please?
> On Mon, Jul 9, 2018 at 9:30 AM Vyacheslav Daradur 
> wrote:
> >
> > Hi,
> >
> > I've commented your PR on the GitHub.
> >
> >
> > On Mon, Jul 9, 2018 at 5:21 AM kcheng.mvp  wrote:
> > >
> > > Dear igniters,
> > >
> > > does anyone can help do the code review?
> > >
> > > As this ticket is created by myself, I need someone else to help me do
> the
> > > code review.
> > >
> > >
> > > Thanks,
> > > kcmvp
> > >
> > >
> > >
> > > --
> > > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
> >
> >
> >
> > --
> > Best Regards, Vyacheslav D.
>
>
>
> --
> Best Regards, Vyacheslav D.
>


Re: Ticket review checklist

2018-07-09 Thread Dmitry Pavlov
I also tend to agree about updating checklist

About suite timeouts, I suspect there is one problem introduced recently
within 3 days, which caused this mass timeouts.

I hope Igniters will find out reason soon. In relation to compute we have
only 2 possible cause:
Ivan Daschinskiy (idaschinskiy) 2 files  IGNITE-8869   Fixed
PartitionsExchangeOnDiscoveryHistoryOverflowTest hanging
Signed-off-by: Andrey Gura  ···

Dmitriy Govorukhin (dgovorukhin) 12 files IGNITE-8827  Disable WAL during
apply updates on recovery

I guess if we fix this reason we will fix 10 suites more
References:
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_ComputeGrid=buildTypeHistoryList_IgniteTests24Java8=%3Cdefault%3E


пн, 9 июл. 2018 г. в 22:29, Anton Vinogradov :

> Sounds reasonable.
> I've satrted Data Structures suite hang investigation [1].
>
> Igniters, especially commiters,
> I know, you're busy, but it will be a great help to the project in case you
> fix at least one hang per person.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-8783
>
> пн, 9 июл. 2018 г. в 19:24, Maxim Muzafarov :
>
> > Hi Igniters,
> >
> > Let's back to discussion of review checklist. Can we add more
> clarification
> > about running all suites on TeamCity?
> >
> > My suggestion is: “All test suites MUST be run on TeamCity [3] before
> merge
> > to master, there MUST NOT be any test failures * and any tests\suites
> with
> > “execution timeouts” *. Not important test failures should be muted and
> > handled according to [4] process.”
> >
> > As you can see we have stable “Execution timeouts” for
> > “Activate\Deactiveate Cluster” test suite since 16-th June. How can we be
> > sure in this case that new changes would not break up old functionality?
> >
> > From my point, all new changes MUST NOT be merged to master util we will
> > fix all execution timeouts for suites. Even if current changes are not
> > related to these timeouts.
> >
> > [1]
> >
> >
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_ActivateDeactivateCluster=buildTypeHistoryList_IgniteTests24Java8=%3Cdefault%3E
> >
> >
> > пн, 4 июн. 2018 г. в 15:56, Dmitry Pavlov :
> >
> > > Requirement of green TC for each PR is community rule, not my.
> > >
> > > I'll answer ro another question, what should we do with test failure:
> > > "Ideally - fix, but at least mute test and create ticket. "
> > >
> > > May be it's time to formalize Make TC Green Again process in details,
> so
> > > let me share my draft.
> > >
> > > If Igniter see test failure (in master, in release bracnh, etc), he
> > should
> > > consider following steps:
> > >
> > >- If your changes can led to this failure(s), please create issue
> with
> > >label MakeTeamCityGreenAgain and assign it to you.
> > >   - If you have fix, please set ticket to PA state and write to dev
> > >   list fix is ready.
> > >   - For case fix will require some time please mute test and set
> > label
> > >   Muted_Test to issue
> > >- If you know which change caused failure please contact change
> author
> > >directly.
> > >- If you don't know which change caused failure please send message
> to
> > >dev list to find out
> > >
> > >
> > >
> > >
> > > пн, 4 июн. 2018 г. в 15:27, Vladimir Ozerov :
> > >
> > > > Dmitry,
> > > >
> > > > My question was how to proceed with your rules. Could you please
> > clarify?
> > > >
> > > > On Mon, Jun 4, 2018 at 2:52 PM, Dmitry Pavlov  >
> > > > wrote:
> > > >
> > > > > Vladimir, I mean strict definition, how much previous runs should
> > > > > contributor consider? What if test was failed by infrastructure
> > reason
> > > in
> > > > > master previously, how can contributor be sure test failure !=
> broken
> > > > code
> > > > > in PR? In this case it should be double checked by
> > > contributor/reviewer.
> > > > > I'm sure nobody can give strict definition of 'new' failure.
> > > > >
> > > > > Flaky tests detected by TC may be taken into account in check-list,
> > > > because
> > > > > contributor can check if failure is flaky. But again, not all tests
> > > with
> > > > > floating failure is detected by TC as flaky.
> > > > >
> > > > >

Re: Hello!

2018-07-09 Thread Dmitry Pavlov
Hi Ilya,

Welcome to the Apache Ignite Сommunity. I added you to the list of
contributord, so you could assign issue to yourself.

Looking forward to your contributions!

Sincerely,
Dmitriy Pavlov

P.S. Additional references for you that should boost your onboarding.

Please subscribe to both dev and user lists:
https://ignite.apache.org/community/resources.html#mail-lists

Get familiar with Ignite development process described here:
https://cwiki.apache.org/confluence/display/IGNITE/Development+Process

Instructions on how to contribute can be found here:
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute

Project setup in Intellij IDEA:
https://cwiki.apache.org/confluence/display/IGNITE/Project+Setup


пн, 9 июл. 2018 г. в 13:27, M. Ilya :

> Hello everyone!
>
> My name is Ilya. I want to contribute to Apache Ignite and want to start
> with this issue - IGNITE-8923.
>
> My JIRA ID is imurchenko. Any help on this will be appreciated.
>
> Thanks!
>


Re: Stable/experimental releases

2018-07-06 Thread Dmitry Pavlov
Hi Igniters,

here I will extremely appreciate vision from community members invoved into
release. What is simpler, support 2.7-EA- or 2.7.x?

Taking into account Teamcity state, it is quite honest to have experimental
releases to underline that
- a lot of new code introduced
- and probably new feateure will be more stable in later release.

WDYT?

Sincerely,
Dmitriy Pavlov

чт, 5 июл. 2018 г. в 17:53, Vladimir Ozerov :

> Hi Dmitriy,
>
> AFAIK we have an idea to introduce maintenance releases for Ignite. E.g.
> 2.6.0 - features, 2.6.1+ - stabilization.
>
> This seems to be more standard and flexible approach.
>
> чт, 5 июля 2018 г. в 17:39, Dmitry Karachentsev <
> dkarachent...@gridgain.com
> >:
>
> > Hi igniters!
> >
> > Following our discussions about emergency releases I see that here might
> > be applied new way for doing releases. Like it was for Linux or like it
> > is for Ubuntu. I mean do interleaving releases: first is experimental
> > with newest features and second - with bug fixes ONLY.
> >
> > For example, odd version number is unstable and even is stable: 2.5
> > introduces a lot of new features, when 2.6 brings more stability to
> > product.
> >
> > Pros:
> >
> > 1. User always has a choice what to choose: cutting edge technology or
> > release that has less problems.
> >
> > 2. It will be much easier to add more effort to make TC green again, as
> > fixes are not mixed with features.
> >
> > 3. We may spend more time on prepare stable release and do more rigorous
> > testing.
> >
> > 4. Stable release may keep 100% compatibility to previous release (not
> > always, of course) to make it easier to migrate and take important bug
> > fixes without introducing a new ones.
> >
> > 5. Not all users will fall in critical issues, in other words, only some
> > group of users will try to use unstable release with experimental
> features.
> >
> > Cons:
> >
> > 1. Necessity of keeping two branches simultaneous: master and stable
> > release. Migrate fixes between branches.
> >
> > 2. Less users could report about found issues, as consequence of item #5
> > from pros.
> >
> > 3. A bit more complex release procedure???
> >
> > I think it's common and right way to create a less buggy product.
> >
> > What do you think?
> >
> > Thanks!
> >
> >
> >
>


Re: Why GridCacheEvictionManager always use cfg.getEvictionPolicy/cfg.getEvictionPolicyFactory even there is NearEvictionPolicy configured?

2018-07-06 Thread Dmitry Pavlov
Hi,

Is this question related to some contribution? If not, probably user@ list
is better place to ask, even if question is advanced. Community members
monitors user list, so even advanced question can find asnwer there.

Dev@ list is intended for discussions related to particular contributions,
PRs, tickests, test failures, proposed changes, development infra, etc.

Sincerely,
Dmitriy Pavlov

чт, 5 июл. 2018 г. в 7:21, kcheng.mvp :

> As the method
> *org.apache.ignite.internal.processors.cache.GridCacheAdapter#isNear*
> always
> returns false, it will make the near cache eviction policy don't take
> effect. Here is the code from
>
> *org.apache.ignite.internal.processors.cache.GridCacheEvictionManager#start0*.
> is this an expected behavior ?
> ==
> CacheConfiguration cfg = cctx.config();
>
> if (cctx.isNear()) {
> plc =
> (cfg.getNearConfiguration().getNearEvictionPolicyFactory()
> != null) ?
>
>
> (EvictionPolicy)cfg.getNearConfiguration().getNearEvictionPolicyFactory().create()
> :
> cfg.getNearConfiguration().getNearEvictionPolicy();
> }
> else if (cfg.getEvictionPolicyFactory() != null)
> plc = (EvictionPolicy)cfg.getEvictionPolicyFactory().create();
> else
> plc = cfg.getEvictionPolicy();
>
> plcEnabled = plc != null;
>
> filter = cfg.getEvictionFilter();
> ==
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>


Re: Move CacheStore::loadCache to a separate interface

2018-07-06 Thread Dmitry Pavlov
As far as I understand we should to wait 3.0, shouldn't we?

пт, 6 июл. 2018 г. в 16:17, Stanislav Lukyanov :

> Hi Igniters,
>
> I’ve just created a ticket to move CacheStore::loadCache to a separate
> interface:
> https://issues.apache.org/jira/browse/IGNITE-8952
> In short, this is to provide a way to only implement loadCache without
> messing with other methods CacheStore implements. More details are in the
> JIRA.
> I believe this would make the API a bit cleaner than it is right now.
>
> This is a small change, I just wanted to highlight it on the dev-list as
> it’s a proposed adjustment to a very old core API.
> Feel free to comment here or in JIRA.
>
> Thanks,
> Stan
>


Re: Cases of using AffinityAssignment.clientEventChange method

2018-07-06 Thread Dmitry Pavlov
Hi Maxim,

Thank you for your efforts to finding this out. I also didn't find any
usages, so I agree here.

I'm going to commit this by lazy consensus if no-one objects within the
next three days.

Sincerely,
Dmitriy Pavlov

чт, 5 июл. 2018 г. в 12:56, Maxim Muzafarov :

> Hello everyone,
>
> Suppose clientEventChange method is useless and have confusing name.
>
> I'm suggesting to remove it as not used. I've filed issue for it:
>
> https://issues.apache.org/jira/browse/IGNITE-8936
>
>
> чт, 28 июн. 2018 г. в 16:53, Maxim Muzafarov :
>
> > Hi Igniters,
> >
> > Recently I've faced with AffinityAssignment.clientEventChange() method
> and
> > not completly sure about the range of its applicability. The javadoc says
> > "return {@code True} if related discovery event did not cause affinity
> > assignment change and this assignment is just reference to the previous
> > one."
> >
> > Three facts about it:
> > 1) Method is the part of internal Ignite API
> > 2) It​ is​ not used anywhere in Ignite project code
> > 3) "clientEventChage" confusing name for this method. "true" value can be
> > set not only by client-related events (e.g. cacheChangeRequest,
> > affinityChangeRequest etc.).
> >
> > I've prepared diagram when it has "TRUE" value [1].
> >
> > * Question #1 * When and for what cases we can use returned value of this
> > method?
> > * Question #2 * Can it be removed? My suggestion is to keep internal API
> > as simple as possible.
> >
> >
> > [1] https://image.ibb.co/cW6Mx8/Client_Event_Change_1.png
> >
>


Re: Platform .NET (Core Linux) Exit code 1 (new) On TeamCity

2018-07-06 Thread Dmitry Pavlov
Hi Pavel,

Sure, I didn't understood that problem is the same with already discussed.

пт, 6 июл. 2018 г. в 12:01, Pavel Tupitsyn :

> Dmitry, see my reply above. I will provide steps to Petr in that other
> thread.
>
> On Fri, Jul 6, 2018 at 12:00 PM Dmitry Pavlov 
> wrote:
>
> > Hi,
> >
> > Unfortunately this problem also occurs in master, so for now everything
> we
> > can do now it is to Ignore it for PR and handle it as part of Make
> TeamCity
> > Green Again activity.
> >
> > Igniters, who can assist in fixing this issue:
> > Testhost process exited with error: Unhandled Exception:
> > System.BadImageFormatException: Could not load file or assembly
> > 'Newtonsoft.Json, Version=9.0.0.0, Culture=neutral,
> > PublicKeyToken=30ad4fe6b2a6aeed'. An attempt was made to load a program
> > with an incorrect format.
> >at Microsoft.VisualStudio.TestPlatform.TestHost.Program.Main(String[]
> > args)
> >   Test Run Aborted.
> > ..Process exited with code 1
> > ?
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > пт, 6 июл. 2018 г. в 8:52, kcheng.mvp :
> >
> > > I have triggered my tests many times on TeamCity. every time I get the
> > same
> > > result.
> > >
> > > Platform .NET (Core Linux)  pull/4300/head  #1109   Exit code 1
> (new)
> > >
> > >
> > >
> >
> https://ci.ignite.apache.org/viewLog.html?buildId=1460429=buildResultsDiv=IgniteTests24Java8_RunBasicTests
> > > .
> > >
> > > I checked the history of 'Platform .NET (Core Linux) ' and found there
> > are
> > > many other build also runs into the same result.
> > >
> > >
> > >
> > >
> > >
> > > --
> > > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
> > >
> >
>


Re: Platform .NET (Core Linux) Exit code 1 (new) On TeamCity

2018-07-06 Thread Dmitry Pavlov
Hi,

Unfortunately this problem also occurs in master, so for now everything we
can do now it is to Ignore it for PR and handle it as part of Make TeamCity
Green Again activity.

Igniters, who can assist in fixing this issue:
Testhost process exited with error: Unhandled Exception:
System.BadImageFormatException: Could not load file or assembly
'Newtonsoft.Json, Version=9.0.0.0, Culture=neutral,
PublicKeyToken=30ad4fe6b2a6aeed'. An attempt was made to load a program
with an incorrect format.
   at Microsoft.VisualStudio.TestPlatform.TestHost.Program.Main(String[]
args)
  Test Run Aborted.
..Process exited with code 1
?

Sincerely,
Dmitriy Pavlov

пт, 6 июл. 2018 г. в 8:52, kcheng.mvp :

> I have triggered my tests many times on TeamCity. every time I get the same
> result.
>
> Platform .NET (Core Linux)  pull/4300/head  #1109   Exit code 1 (new)
>
>
> https://ci.ignite.apache.org/viewLog.html?buildId=1460429=buildResultsDiv=IgniteTests24Java8_RunBasicTests
> .
>
> I checked the history of 'Platform .NET (Core Linux) ' and found there are
> many other build also runs into the same result.
>
>
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>


Re: Ignite as distributed file storage

2018-06-30 Thread Dmitry Pavlov
I defenetely support adding this functionality.

As Ignite user I develop MTCGA Bot, this tool stores test results from
previous TC runs. In addition to test result it also stores thread dump
and, sometimes, logs. It would be very convenient and more productive to
store this data in such file store over Ignite. Of course, if API is
convenient enough.

So, it is perfectly ok if such donation would be made to the product.

сб, 30 июн. 2018 г. в 17:24, Pavel Kovalenko :

> Igniters,
>
> I would like to start a discussion about designing a new feature because I
> think it's time to start making steps towards it.
> I noticed, that some of our users have tried to store large homogenous
> entries (> 1, 10, 100 Mb/Gb/Tb) to our caches, but without big success.
>
> IGFS project has the possibility to do it, but as for me it has one big
> disadvantage - it's in-memory only, so users have a strict size limit of
> their data and have data loss problem.
>
> Our durable memory has a possibility to persist a data that doesn't fit to
> RAM to disk, but page structure of it is not supposed to store large pieces
> of data.
>
> There are a lot of projects of distributed file systems like HDFS,
> GlusterFS, etc. But all of them concentrate to implement high-grade file
> protocol, rather than user-friendly API which leads to high entry threshold
> to start implementing something over it.
> We shouldn't go in this way. Our main goal should be providing to user easy
> and fast way to use file storage and processing here and now.
>
> If take HDFS as closest possible by functionality project, we have one big
> advantage against it. We can use our caches as files metadata storage and
> have the infinite possibility to scale it, while HDFS is bounded by
> Namenode capacity and has big problems with keeping a large number of files
> in the system.
>
> We achieved very good experience with persistence when we developed our
> durable memory, and we can couple together it and experience with services,
> binary protocol, I/O and start to design a new IEP.
>
> Use cases and features of the project:
> 1) Storing XML, JSON, BLOB, CLOB, images, videos, text, etc without
> overhead and data loss possibility.
> 2) Easy, pluggable, fast and distributed file processing, transformation
> and analysis. (E.g. ImageMagick processor for images transformation,
> LuceneIndex for texts, whatever, it's bounded only by your imagination).
> 3) Scalability out of the box.
> 4) User-friendly API and minimal steps to start using this storage in
> production.
>
> I repeated again, this project is not supposed to be a high-grade
> distributed file system with full file protocol support.
> This project should primarily focus on target users, which would like to
> use it without complex preparation.
>
> As for example, a user can deploy Ignite with such storage and web-server
> with REST API as Ignite service and get scalable, performant image server
> out of the box which can be accessed using any programming language.
>
> As a far target goal, we should focus on storing and processing a very
> large amount of the data like movies, streaming, which is the big trend
> today.
>
> I would like to say special thanks to our community members Alexey Stelmak
> and Dmitriy Govorukhin which significantly helped me to put together all
> pieces of that puzzle.
>
> So, I want to hear your opinions about this proposal.
>


Re: Ignite contibutors page

2018-06-28 Thread Dmitry Pavlov
I know at least Akmal & Prachi. Akmal does a great job to popularize Ignite
in the society, Prachi helps all of us a lot with docs.

I guess it is not complete list.

чт, 28 июн. 2018 г. в 16:21, Denis Magda :

> Evgeniy,
>
> It's even better that GitHub shows top 100 contributors. If someone wants
> to get to the list, then a gateway is obvious - contribute more. I've
> updated the sentence on the website to reflect that.
>
> Dmitriy P.,
>
> The previous version looked bad - the table was too long and never
> up-to-date. There is little sense to spend our efforts redesigning it and
> keeping on track. For those who contribute the other way we can create a
> special table. It will be small and manageable. Can you put together a list
> of such contributors?
>
> --
> Denis
>
> On Thu, Jun 28, 2018 at 8:49 AM Dmitry Pavlov 
> wrote:
>
> > I personally prefer old version of page.
> >
> > Moreover, if we use github list this means we limit contributions by only
> > code contributions.
> >
> > чт, 28 июн. 2018 г. в 14:59, Evgeniy Ignatiev <
> yevgeniy.ignat...@gmail.com
> > >:
> >
> > > "Contributors" tab on github only lists top 100 accounts by
> contribution
> > > (unless GitHub Enterprise is used), so maybe "to see a full list of
> > > contributors" the word full should not be put here?
> > >
> > > Best regards,
> > > Evgeniy Ignatiev
> > >
> > > On 6/28/2018 3:32 PM, Denis Magda wrote:
> > > > We reworked the contributors' section. There are so many contributors
> > > that
> > > > there is little sense to try to enlist all of them on Ignite
> website. A
> > > > reference to GitHub was provided instead. The committers table was
> left
> > > > untouched: https://ignite.apache.org/community/resources.html#people
> > > >
> > > > --
> > > > Denis
> > > >
> > > > On Wed, Jun 27, 2018 at 1:07 PM Denis Magda 
> wrote:
> > > >
> > > >> Anton,
> > > >>
> > > >> It's easy to maintain committers/PMC list for now. I would leave it
> as
> > > is.
> > > >> The changes rarely happen there. But I do agree that it's hard to
> > track
> > > >> changes related to the contributor's list. Makes sense to provide a
> > > link to
> > > >> that GitHub page instead.
> > > >>
> > > >> Prachi, could you please prepare a version of the page where the
> > > >> contributor's table is replaced with the link to this page and some
> > nice
> > > >> picture:
> > > >> https://github.com/apache/ignite/graphs/contributors
> > > >>
> > > >> Pavel, you were demoted, now you're among contributors :)
> > > >>
> > > >> --
> > > >> Denis
> > > >>
> > > >>
> > > >> On Wed, Jun 27, 2018 at 5:12 AM Anton Vinogradov 
> > wrote:
> > > >>
> > > >>>>> I see that I was added to the Commiters table, but I'm not
> > commiter,
> > > >>> just
> > > >>>>> contributor :)
> > > >>> One more reason to prodive commiters/PMC list using generated url
> [1]
> > > >>>
> > > >>> [1] http://people.apache.org/phonebook.html?pmc=ignite
> > > >>>
> > > >>> ср, 27 июн. 2018 г. в 12:07, Pavel Kovalenko :
> > > >>>
> > > >>>> I see that I was added to the Commiters table, but I'm not
> commiter,
> > > >>> just
> > > >>>> contributor :)
> > > >>>>
> > > >>>> ср, 27 июн. 2018 г. в 12:02, Anton Vinogradov :
> > > >>>>
> > > >>>>> Denis,
> > > >>>>>
> > > >>>>> I'm bad at html :)
> > > >>>>> But my idea is to, at least, have such url [1] published at
> > > >>> contributors
> > > >>>>> page.
> > > >>>>> In case we have non-code contributors, we can mention them at
> > special
> > > >>>>> table, but code contributors can be mentioned just by this url.
> > > >>>>>
> > > >>>>> [1] https://github.com/apache/ignite/graphs/contributors
> > > >>>>>
> > > >>>>> ср, 27 июн. 2018 г. в 6:09, Denis Magda :
> > > >>&

Re: Ignite contibutors page

2018-06-28 Thread Dmitry Pavlov
I personally prefer old version of page.

Moreover, if we use github list this means we limit contributions by only
code contributions.

чт, 28 июн. 2018 г. в 14:59, Evgeniy Ignatiev :

> "Contributors" tab on github only lists top 100 accounts by contribution
> (unless GitHub Enterprise is used), so maybe "to see a full list of
> contributors" the word full should not be put here?
>
> Best regards,
> Evgeniy Ignatiev
>
> On 6/28/2018 3:32 PM, Denis Magda wrote:
> > We reworked the contributors' section. There are so many contributors
> that
> > there is little sense to try to enlist all of them on Ignite website. A
> > reference to GitHub was provided instead. The committers table was left
> > untouched: https://ignite.apache.org/community/resources.html#people
> >
> > --
> > Denis
> >
> > On Wed, Jun 27, 2018 at 1:07 PM Denis Magda  wrote:
> >
> >> Anton,
> >>
> >> It's easy to maintain committers/PMC list for now. I would leave it as
> is.
> >> The changes rarely happen there. But I do agree that it's hard to track
> >> changes related to the contributor's list. Makes sense to provide a
> link to
> >> that GitHub page instead.
> >>
> >> Prachi, could you please prepare a version of the page where the
> >> contributor's table is replaced with the link to this page and some nice
> >> picture:
> >> https://github.com/apache/ignite/graphs/contributors
> >>
> >> Pavel, you were demoted, now you're among contributors :)
> >>
> >> --
> >> Denis
> >>
> >>
> >> On Wed, Jun 27, 2018 at 5:12 AM Anton Vinogradov  wrote:
> >>
> >>>>> I see that I was added to the Commiters table, but I'm not commiter,
> >>> just
> >>>>> contributor :)
> >>> One more reason to prodive commiters/PMC list using generated url [1]
> >>>
> >>> [1] http://people.apache.org/phonebook.html?pmc=ignite
> >>>
> >>> ср, 27 июн. 2018 г. в 12:07, Pavel Kovalenko :
> >>>
> >>>> I see that I was added to the Commiters table, but I'm not commiter,
> >>> just
> >>>> contributor :)
> >>>>
> >>>> ср, 27 июн. 2018 г. в 12:02, Anton Vinogradov :
> >>>>
> >>>>> Denis,
> >>>>>
> >>>>> I'm bad at html :)
> >>>>> But my idea is to, at least, have such url [1] published at
> >>> contributors
> >>>>> page.
> >>>>> In case we have non-code contributors, we can mention them at special
> >>>>> table, but code contributors can be mentioned just by this url.
> >>>>>
> >>>>> [1] https://github.com/apache/ignite/graphs/contributors
> >>>>>
> >>>>> ср, 27 июн. 2018 г. в 6:09, Denis Magda :
> >>>>>
> >>>>>> Let's try your approach if you can embed it nicely into the site.
> >>>>>>
> >>>>>> --
> >>>>>> Denis
> >>>>>>
> >>>>>> On Tue, Jun 26, 2018 at 3:55 PM Anton Vinogradov 
> >>>> wrote:
> >>>>>>> Anyway,
> >>>>>>>
> >>>>>>> I see 166 code contributors, event in case some persons have more
> >>>> than
> >>>>>> one
> >>>>>>> account (like me) it definitely more that we have at contributors
> >>>> page.
> >>>>>>> вт, 26 июн. 2018 г. в 19:55, Dmitry Pavlov  >>>> :
> >>>>>>>> Hi Anton,
> >>>>>>>>
> >>>>>>>> IMO we can't limit contribution from community member only by
> >>>>>>> contribution
> >>>>>>>> of code (it may be wiki, documenation, examples, popularization
> >>> of
> >>>>>>> Ignite,
> >>>>>>>> etc, - literally any contribution), so it is more general way to
> >>>>>> maintain
> >>>>>>>> contributors list as is.
> >>>>>>>>
> >>>>>>>> Sincerely,
> >>>>>>>>
> >>>>>>>> вт, 26 июн. 2018 г. в 15:24, Anton Vinogradov :
> >>>>>>>>
> >>>>>>>>> Why we cant just use this page?
> >>>>>>>>> https://

Re: Ignite 2.6 emergency release suggestion

2018-06-27 Thread Dmitry Pavlov
Nikolay, thank you for such fast reaction. Tests are passing now.

ср, 27 июн. 2018 г. в 17:28, Nikolay Izhikov :

> Hello, Dmitriy.
>
> I fixed this issue, already.
> Please, check it.
>
> В Ср, 27/06/2018 в 16:55 +0300, Dmitry Pavlov пишет:
> > Hi Denis,
> >
> > currently anyway we have TC issue came from spark version migrations.
> >
> > I also currently experiencing challenges with my local environment setup.
> > So I guess we have day or two to wait this fix.
> >
> > Sincerely.
> > Dmitriy Pavlov
> >
> > ср, 27 июн. 2018 г. в 16:05, Denis Magda :
> >
> > > May I ask when? The current status of the ticket is not clear.
> > >
> > > --
> > > Denis
> > >
> > > On Wed, Jun 27, 2018 at 7:27 AM Spider (Alexey) <
> spiderru5...@gmail.com>
> > > wrote:
> > >
> > > > Yes, it will be in the release 2.6
> > > >
> > > > > 27 июня 2018 г., в 14:15, Dmitry Pavlov 
> > > >
> > > > написал(а):
> > > > >
> > > > > Hi Igniters,
> > > > >
> > > > > I've returned https://issues.apache.org/jira/browse/IGNITE-8780
> to the
> > > > > scope because it was initially discussed to be in this reselase.
> > > > >
> > > > > Alexey Stelmak, could you please confirm fix could be ready soon?
> > > > >
> > > > > Also I've cherry-picked javadoc fix.
> > > > >
> > > > > Sincerely,
> > > > > Dmitriy Pavlov
> > > > >
> > > > > вт, 26 июн. 2018 г. в 20:33, Denis Magda :
> > > >
> > > >


Ignite master: OOMEs and test failure rate raised

2018-06-27 Thread Dmitry Pavlov
Hi Igniters,

I've noticed in latest run we have ~ 985 test failures and 3 suites with
OOME in master.

Who knows if it is temporary or infra problem or we have some bug in code?
Could you please share ticket numbers?

https://ci.ignite.apache.org/viewLog.html?buildId=1429088
https://ci.ignite.apache.org/viewLog.html?buildId=1429108
https://ci.ignite.apache.org/viewLog.html?buildId=1428437

Sincerely,
Dmitriy Pavlov


Re: TDE: Upgrade Team City JDK

2018-06-27 Thread Dmitry Pavlov
Hi Nikolay,

 can we add option enables AES 128 for test mode? This should work well
without update env.

Sincerely,

ср, 27 июн. 2018 г. в 18:43, Petr Ivanov :

>
>
> > On 27 Jun 2018, at 18:06, Nikolay Izhikov  wrote:
> >
> > Hello, Eduard.
> >
> >> We should make suites which are restricted by agents to make as small
> as> possible.
> >
> > Agree. That means we should enable java cryptography on all agents.
> Isn't it?
> >
> >> So, I strictly against adding such test (therefore restriction) to
> these> suites.>
> >
> > What is wrong with tests?
>
> Tests in current configuration require specific environment.
> I guess we should update environment to meet test requirements prior
> putting changes to master.
>
>
> > Do you looked at it or something?
> >
> >
> > В Ср, 27/06/2018 в 14:24 +0300, Eduard Shangareev пишет:
> >> Nikolay, Petr,
> >>
> >> We should make suites which are restricted by agents to make as small as
> >> possible.
> >>
> >> So, I strictly against adding such test (therefore restriction) to these
> >> suites.
> >>
> >> On Wed, Jun 27, 2018 at 11:39 AM, Petr Ivanov 
> wrote:
> >>
> >>> IgniteSpiTestSuite is called from ’SPI’ build type and I’ve added agent
> >>> filter there.
> >>> IgniteKernalSelfTestSuite is not found in build types.
> >>>
> >>>
> >>>
>  On 27 Jun 2018, at 11:26, Nikolay Izhikov 
> wrote:
> 
>  Well, it's a good question :)
> 
>  I've added encryption tests in `IgniteKernalSelfTestSuite` and in
> >>>
> >>> `IgniteSpiTestSuite`.
>  Not sure, what builds on Team City runs these suites.
> 
>  В Ср, 27/06/2018 в 11:18 +0300, Petr Ivanov пишет:
> > Nikolay,
> >
> >
> > What is “core” module?
> >
> >
> >> On 27 Jun 2018, at 00:42, Nikolay Izhikov 
> wrote:
> >>
> >> Hello, Petr.
> >>
> >> Thanks a lot!
> >> I see success spring encryption tests now [1]
> >>
> >> I've added encryption tests to core module also.
> >> Can we set same rule for a core module?
> >>
> >> [1] https://ci.ignite.apache.org/project.html?projectId=
> >>>
> >>> IgniteTests24Java8=-2290193573767653560=testDetails
> >>
> >> В Вт, 26/06/2018 в 23:38 +0300, Petr Ivanov пишет:
> >>> I’ve added JCE as it is described in documentation, but for some
> >>>
> >>> unknown reason it won’t work on 1.8.0_u151.
> >>> So I’ve fix agent filter rule to run Spring build type only on
> >>>
> >>> 1.8.0_u171 (49 agents) and run it on all enabled compatible agents.
> >>> Looks like it fixed the issue.
> >>>
> >>>
> >>>
>  On 26 Jun 2018, at 19:27, Nikolay Izhikov 
> >>>
> >>> wrote:
> 
>  Petr, can you make suggested jdk upgrade?
> 
>  В Пн, 25/06/2018 в 14:28 +0300, Nikolay Izhikov пишет:
> > Petr.
> >
> > One more thing:
> >
> > We need to install "Java Cryptography Extension (JCE) Unlimited
> >>>
> >>> Strength Jurisdiction Policy Files" [1] to enable usage of JDK provided
> >>> crypto algorithmes.
> > Otherwise it fails with "java.security.InvalidKeyException:
> >>>
> >>> Illegal key size at
> javax.crypto.Cipher.checkCryptoPerm(Cipher.java:1039)"
> >>> [2]
> >
> > Can you do it for Team City agents?
> >
> > [1] http://www.oracle.com/technetwork/java/javase/
> >>>
> >>> downloads/jce8-download-2133166.html
> > [2] https://ci.ignite.apache.org/viewLog.html?tab=buildLog;;
> >>>
> >>> logTab=tree=debug=all=1421337&_focus=30899
> >
> > В Пн, 25/06/2018 в 13:24 +0300, Petr Ivanov пишет:
> >> I’ve modified filter requirements for JDK for Spring build
> >>>
> >>> configuration to run only on u151/u171 of JDK-1.8.0 (it will be 55
> agent).
> >> Hope this will be enough.
> >>
> >>
> >>
> >>> On 25 Jun 2018, at 12:54, Nikolay Izhikov  >
> >>>
> >>> wrote:
> >>>
> >>> Hello, Petr.
> >>>
>  I can temporarily assign special rule for agent JDK and fix
> >>>
> >>> theirs Java later.
> >>>
> >>> I'm not Team City guru, so I'm don't understand your proposal
> :)
> >>>
> >>> All I need is make sure Core and Spring suites for my branch
> [1]
> >>>
> >>> are executed with latest jdk.
> >>>
> >>> Can you make it for me?
> >>>
> >>> [1] https://github.com/apache/ignite/pull/4167
> >>>
> >>>
> >>> В Пн, 25/06/2018 в 11:21 +0300, Petr Ivanov пишет:
>  Nokolay,
> 
> 
>  Agents prior publicagent10 has u77 inded, while
> publicagent10-17
> >>>
> >>> has already u171.
>  I can temporarily assign special rule for agent JDK and fix
> >>>
> >>> theirs Java later.
> 
> 
> 
> > On 25 Jun 2018, at 10:33, Nikolay Izhikov <
> nizhi...@apache.org>
> >>>
> >>> wrote:
> >
> > Hello, Igniters.

Re: Ignite 2.6 emergency release suggestion

2018-06-27 Thread Dmitry Pavlov
Hi Denis,

currently anyway we have TC issue came from spark version migrations.

I also currently experiencing challenges with my local environment setup.
So I guess we have day or two to wait this fix.

Sincerely.
Dmitriy Pavlov

ср, 27 июн. 2018 г. в 16:05, Denis Magda :

> May I ask when? The current status of the ticket is not clear.
>
> --
> Denis
>
> On Wed, Jun 27, 2018 at 7:27 AM Spider (Alexey) 
> wrote:
>
> > Yes, it will be in the release 2.6
> >
> > > 27 июня 2018 г., в 14:15, Dmitry Pavlov 
> > написал(а):
> > >
> > > Hi Igniters,
> > >
> > > I've returned https://issues.apache.org/jira/browse/IGNITE-8780 to the
> > > scope because it was initially discussed to be in this reselase.
> > >
> > > Alexey Stelmak, could you please confirm fix could be ready soon?
> > >
> > > Also I've cherry-picked javadoc fix.
> > >
> > > Sincerely,
> > > Dmitriy Pavlov
> > >
> > > вт, 26 июн. 2018 г. в 20:33, Denis Magda :
> >
> >
>


Re: Quick questions on segments and page map buckets

2018-06-27 Thread Dmitry Pavlov
John, is this question still actual?

пт, 22 июн. 2018 г. в 15:18, Dmitry Pavlov :

> Hi Ed,
>
> Which Sergey do you mean? I know a number of contributors.
>
> Sincerely,
>
>
> вт, 19 июн. 2018 г. в 22:15, Eduard Shangareev <
> eduard.shangar...@gmail.com>:
>
>> Hi,
>>
>> 1. It looks weird, yeah. Need to ask Sergey, who has changed it last time.
>>
>> 2. Because we could reuse memory. For example, after cache destroy or
>> something like that.
>>
>> On Tue, Jun 19, 2018 at 9:58 PM, John Wilson 
>> wrote:
>>
>> > Hi,
>> >
>> > Two quick questions:
>> >
>> >
>> >1. The design documentation here,
>> >https://cwiki.apache.org/confluence/display/IGNITE/
>> > Ignite+Durable+Memory+-+under+the+hood,
>> >states that the default segment count is equal to the number of
>> logical
>> >cores available in the underlying machine. However, the segments
>> array
>> > in
>> >PageMemory indicates that the maximum number of segments is: 1 <<
>> > SEG_BITS.
>> >Since SEG_BITS = 4, the max # segments is 16. Did I miss something
>> here?
>> >2. Reading the code in PageMemoryNoStoreImp, it looks like pages are
>> >allocated segment sequentially in a bump-the-pointer strategy where
>> the
>> >first 8 bytes of a segment hold a pointer to the index of the last
>> >allocated page. If this is true, then I don't understand the point of
>> >having a page map buckets. Why not use a simple arithmetic index *
>> > pageSize
>> >to get the offset of a page?
>> >
>> > Thanks.
>> > John
>> >
>>
>


Re: Ignite 2.6 emergency release suggestion

2018-06-27 Thread Dmitry Pavlov
Hi Igniters,

I've returned https://issues.apache.org/jira/browse/IGNITE-8780 to the
scope because it was initially discussed to be in this reselase.

 Alexey Stelmak, could you please confirm fix could be ready soon?

Also I've cherry-picked javadoc fix.

Sincerely,
Dmitriy Pavlov

вт, 26 июн. 2018 г. в 20:33, Denis Magda :

> +1 to Dmitriy's stance.
>
> IGNITE-6055 doesn't look like something that needs to halt this release.
> Plus, let me remind us that it's an emergency release that has to solve
> severe problems at the persistence layer. What planned to be released
> within 2 weeks got stuck for almost a month.
>
> Dmitriy, as a release manager, please announce official code freeze (send a
> separate message) and pass the release to the QA members of the community
> for final testing.
>
> --
> Denis
>
>
> On Tue, Jun 26, 2018 at 12:49 PM Dmitry Pavlov 
> wrote:
>
> > Hi Nikolay,
> >
> > why this ticket should be included into emergency release?
> >
> > I agree in case
> > 1) Vladimir has time to review it now,
> > 2) we have clear motivation why it is emergency change.
> >
> > We are still going to do 2.7 release as normal Ignite release later.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > вт, 26 июн. 2018 г. в 19:30, Nikolay Izhikov :
> >
> > > Hello, Igniters.
> > >
> > > We have private discussion with Vladimir Ozerov and Dmitry Pavlov.
> > >
> > > IGNITE-6055 has to be included in 2.6, also.
> > > Final review from Vladimir required to merge this ticket.
> > >
> > > Do we have a chance to include this ticket to 2.6?
> > >
> > > В Вт, 26/06/2018 в 19:26 +0300, Dmitry Pavlov пишет:
> > > > Hi Igniters,
> > > >
> > > > I've prepared wiki page
> > > > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.6
> > and
> > > > started to reassign existing issues to 2.7.
> > > >
> > > > Sincerely,
> > > > Dmitriy Pavlov
> > > >
> > > > сб, 23 июн. 2018 г. в 2:58, Denis Magda :
> > > >
> > > > > Thanks folks!
> > > > >
> > > > > Dmitriy P., please proceed with the release finalization. Don't
> > accept
> > > any
> > > > > other commits to 2.6.
> > > > >
> > > > > --
> > > > > Denis
> > > > >
> > > > > On Fri, Jun 22, 2018 at 4:32 PM Valentin Kulichenko <
> > > > > valentin.kuliche...@gmail.com> wrote:
> > > > >
> > > > > > After a conversation with Amir, IGNITE-8740 is merged to master
> and
> > > 2.6.
> > > > > >
> > > > > > -Val
> > > > > >
> > > > > > On Fri, Jun 22, 2018 at 2:52 PM Valentin Kulichenko <
> > > > > > valentin.kuliche...@gmail.com> wrote:
> > > > > >
> > > > > > > Guys,
> > > > > > >
> > > > > > > I reviewed changes in IGNITE-8740, but I'm not sure the fix is
> > > > >
> > > > > correct. I
> > > > > > > left a more detailed comment in the ticket. Hopefully, Mair
> will
> > be
> > > > >
> > > > > able
> > > > > > to
> > > > > > > respond shortly and clarify.
> > > > > > >
> > > > > > > -Val
> > > > > > >
> > > > > > > On Fri, Jun 22, 2018 at 10:58 AM Denis Magda <
> dma...@apache.org>
> > > > >
> > > > > wrote:
> > > > > > >
> > > > > > > > Dmitriy,
> > > > > > > >
> > > > > > > > No, that's an honor for us to see you in this role ;) Both
> > Andrey
> > > > >
> > > > > Gura,
> > > > > > > > Anton Vinogradov are our release-management veterans. Please
> > > feel free
> > > > > >
> > > > > > to
> > > > > > > > contact them directly.
> > > > > > > >
> > > > > > > > Could you take over this ticket review and include it in the
> > > release:
> > > > > > > > https://issues.apache.org/jira/browse/IGNITE-8740
> > > > > > > >
> > > > > > > > It's not good that we have spring integration broken in some
> > > places in
>

Ignite 2.6 E.R. Code freeze

2018-06-26 Thread Dmitry Pavlov
Hi Folks,


I hope you’re doing absolutely well.

Apache Ignite 2.6 (emergency release) code freezed with 14 following
changes (see below). Issues merged to master were migrated to 2.7 version,
same for not closed issues.


Please double check if there is any missed issue on the release page
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.6

Sincerely,

Dmitriy Pavlov

[IGNITE-8530] Exchange hangs during start/stop stress test

[IGNITE-8476] AssertionError exception occurs when trying to remove node
from baseline under loading

[IGNITE-8565] Arbitrary code execution from GridClientJdkMarshaller

[IGNITE-8804] Windows WSL configuration has to be added to Ignite configs

[IGNITE-8807] Apache Ignite Linux packages 2.6 update

[IGNITE-8740] Support reuse of already initialized Ignite in
IgniteSpringBean

[IGNITE-8768] JVM crash in PDS1 suite in master branch

[IGNITE-8685] Incorrect size for switch segment record

[IGNITE-8561] SinglSegmentLogicalRecordsIterator is broken

[IGNITE-7896] Files of evicted partitions are not removed from disk storage

[IGNITE-8682] Attempt to configure IGFS in persistent mode without specific
data region ends with AssertionError

[IGNITE-8713] Security vulnerabilities in
spring-data-commons-1.13.1.RELEASE.jar

[IGNITE-8722] Issue in REST API 2.5

[IGNITE-8534] Upgrade Ignite Spark Module's Spark version to 2.3.0


Re: Ignite contibutors page

2018-06-26 Thread Dmitry Pavlov
Hi Anton,

IMO we can't limit contribution from community member only by contribution
of code (it may be wiki, documenation, examples, popularization of Ignite,
etc, - literally any contribution), so it is more general way to maintain
contributors list as is.

Sincerely,

вт, 26 июн. 2018 г. в 15:24, Anton Vinogradov :

> Why we cant just use this page?
> https://github.com/apache/ignite/graphs/contributors
>
> вт, 26 июн. 2018 г. в 15:20, Denis Magda :
>
> > Only static code is allowed on the site. The downloads' code snippets are
> > prepared and enabled by INFRA.
> >
> > --
> > Denis
> >
> > On Tue, Jun 26, 2018 at 5:18 AM Anton Vinogradov  wrote:
> >
> > > Can we generate contributors page automatically?
> > > Git history tells me we missed more than one contributor :)
> > >
> > > вт, 26 июн. 2018 г. в 15:14, Pavel Kovalenko :
> > >
> > > > Igniters,
> > > >
> > > > I've just noticed that I also not mentioned in Contributors table.
> > > >
> > > > вт, 26 июн. 2018 г. в 12:11, Anton Vinogradov :
> > > >
> > > > > Denis, could you please also fix Committers table?
> > > > > Seems it was broken on last append.
> > > > >
> > > > > пн, 25 июн. 2018 г. в 22:18, Denis Magda :
> > > > >
> > > > > > Done, thanks for your contributions!
> > > > > >
> > > > > > --
> > > > > > Denis
> > > > > >
> > > > > > On Mon, Jun 25, 2018 at 6:13 AM Иван Федоров <
> ivanan...@gmail.com>
> > > > > wrote:
> > > > > >
> > > > > > > Hi, Igniters!
> > > > > > > I'm contributor and I'm not mentioned on contributor page -
> > > > > > > https://ignite.apache.org/community/resources.html
> > > > > > > Could you mention me, please?
> > > > > > > Ivan Fedotov.
> > > > > > >
> > > > > > > 2018-06-25 13:09 GMT+03:00 Maxim Muzafarov  >:
> > > > > > >
> > > > > > > > Hello Denis,
> > > > > > > >
> > > > > > > > Could you, please, add to the list of Ignite contributors:
> > > Prabhat
> > > > > > Ranjan
> > > > > > > > (rprabhat)
> > > > > > > > https://ignite.apache.org/community/resources.html
> > > > > > > >
> > > > > > > > He has got his first commit into Ignite.
> > > > > > > > https://issues.apache.org/jira/browse/IGNITE-8436
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > вт, 29 мая 2018 г. в 20:19, Denis Magda :
> > > > > > > >
> > > > > > > > > Hello Aleksei, done!
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > Denis
> > > > > > > > >
> > > > > > > > > On Mon, May 28, 2018 at 2:46 PM, Aleksei Zaitsev <
> > > > > > > ign...@alexzaitzev.pro
> > > > > > > > >
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Hello Denis,
> > > > > > > > > >
> > > > > > > > > > Could you, please, add me to the list too: alexzaitzev
> > > (Aleksei
> > > > > > > > Zaitsev).
> > > > > > > > > > https://ignite.apache.org/community/resources.html
> > > > > > > > > > Thanks.
> > > > > > > > > >
> > > > > > > > > > Best regards,
> > > > > > > > > > Alex.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > 15.03.2018, 21:03, "Denis Magda" :
> > > > > > > > > > > Dmitriy, Alexey,
> > > > > > > > > > >
> > > > > > > > > > > Done, now your names are engraved on the page ;)
> > > > > > > > > > >
> > > > > > > > > > > --
> > > > > > > > > > > Denis
> > > > > > > > > > >
> > > > > > > > > > > On Thu, Mar 15, 2018 at 2:34 AM, Dmitriy Shabalin <
> > > > > > > > dmitri...@gmail.com
> > > > > > > > > >
> > > > > > > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > >>  I'm not mentioned on the community contributors page:
> > > > > > > > > > >>  https://ignite.apache.org/community/resources.html
> > > > > > > > > > >>
> > > > > > > > > > >>  pls add me, dmitriyff (Dmitriy Shabalin)
> > > > > > > > > > >>
> > > > > > > > > > >>  --
> > > > > > > > > > >>  Sent from:
> > > > > > > http://apache-ignite-developers.2346864.n4.nabble.com/
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Ivan Fedotov.
> > > > > > >
> > > > > > > ivanan...@gmail.com
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>


Re: Ignite 2.6 emergency release suggestion

2018-06-26 Thread Dmitry Pavlov
Hi Nikolay,

why this ticket should be included into emergency release?

I agree in case
1) Vladimir has time to review it now,
2) we have clear motivation why it is emergency change.

We are still going to do 2.7 release as normal Ignite release later.

Sincerely,
Dmitriy Pavlov

вт, 26 июн. 2018 г. в 19:30, Nikolay Izhikov :

> Hello, Igniters.
>
> We have private discussion with Vladimir Ozerov and Dmitry Pavlov.
>
> IGNITE-6055 has to be included in 2.6, also.
> Final review from Vladimir required to merge this ticket.
>
> Do we have a chance to include this ticket to 2.6?
>
> В Вт, 26/06/2018 в 19:26 +0300, Dmitry Pavlov пишет:
> > Hi Igniters,
> >
> > I've prepared wiki page
> > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.6 and
> > started to reassign existing issues to 2.7.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > сб, 23 июн. 2018 г. в 2:58, Denis Magda :
> >
> > > Thanks folks!
> > >
> > > Dmitriy P., please proceed with the release finalization. Don't accept
> any
> > > other commits to 2.6.
> > >
> > > --
> > > Denis
> > >
> > > On Fri, Jun 22, 2018 at 4:32 PM Valentin Kulichenko <
> > > valentin.kuliche...@gmail.com> wrote:
> > >
> > > > After a conversation with Amir, IGNITE-8740 is merged to master and
> 2.6.
> > > >
> > > > -Val
> > > >
> > > > On Fri, Jun 22, 2018 at 2:52 PM Valentin Kulichenko <
> > > > valentin.kuliche...@gmail.com> wrote:
> > > >
> > > > > Guys,
> > > > >
> > > > > I reviewed changes in IGNITE-8740, but I'm not sure the fix is
> > >
> > > correct. I
> > > > > left a more detailed comment in the ticket. Hopefully, Mair will be
> > >
> > > able
> > > > to
> > > > > respond shortly and clarify.
> > > > >
> > > > > -Val
> > > > >
> > > > > On Fri, Jun 22, 2018 at 10:58 AM Denis Magda 
> > >
> > > wrote:
> > > > >
> > > > > > Dmitriy,
> > > > > >
> > > > > > No, that's an honor for us to see you in this role ;) Both Andrey
> > >
> > > Gura,
> > > > > > Anton Vinogradov are our release-management veterans. Please
> feel free
> > > >
> > > > to
> > > > > > contact them directly.
> > > > > >
> > > > > > Could you take over this ticket review and include it in the
> release:
> > > > > > https://issues.apache.org/jira/browse/IGNITE-8740
> > > > > >
> > > > > > It's not good that we have spring integration broken in some
> places in
> > > > > > several releases. I would treat is as a usability blocker and
> > > >
> > > > regression.
> > > > > >
> > > > > > --
> > > > > > Denis
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Fri, Jun 22, 2018 at 3:06 AM Dmitry Pavlov <
> dpavlov@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > > Hi Alexey,
> > > > > > >
> > > > > > > Sure, it will be honor for me.
> > > > > > >
> > > > > > > In the same time I relatevely new in this area, so I would
> highly
> > > > > > > appreciate any assistance of experienced community members to
> make
> > > >
> > > > this
> > > > > > > happen.
> > > > > > >
> > > > > > > Sincerely,
> > > > > > >
> > > > > > > пт, 22 июн. 2018 г. в 12:18, Alexey Goncharuk <
> > > > > >
> > > > > > alexey.goncha...@gmail.com
> > > > > > > > :
> > > > > > > > Denis,
> > > > > > > >
> > > > > > > > Currently, I am not aware of anybody who can immediately
> review
> > >
> > > and
> > > > > > > > sign-off the suggested patch. The original scope of tickets
> have
> > > >
> > > > been
> > > > > > > > resolved, so I suggest to move on with what we have now.
> > > > > > > >
> > > > > > > > I will not be able to continue with 

Re: Ignite 2.6 emergency release suggestion

2018-06-26 Thread Dmitry Pavlov
Hi Igniters,

I've prepared wiki page
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.6 and
started to reassign existing issues to 2.7.

Sincerely,
Dmitriy Pavlov

сб, 23 июн. 2018 г. в 2:58, Denis Magda :

> Thanks folks!
>
> Dmitriy P., please proceed with the release finalization. Don't accept any
> other commits to 2.6.
>
> --
> Denis
>
> On Fri, Jun 22, 2018 at 4:32 PM Valentin Kulichenko <
> valentin.kuliche...@gmail.com> wrote:
>
> > After a conversation with Amir, IGNITE-8740 is merged to master and 2.6.
> >
> > -Val
> >
> > On Fri, Jun 22, 2018 at 2:52 PM Valentin Kulichenko <
> > valentin.kuliche...@gmail.com> wrote:
> >
> > > Guys,
> > >
> > > I reviewed changes in IGNITE-8740, but I'm not sure the fix is
> correct. I
> > > left a more detailed comment in the ticket. Hopefully, Mair will be
> able
> > to
> > > respond shortly and clarify.
> > >
> > > -Val
> > >
> > > On Fri, Jun 22, 2018 at 10:58 AM Denis Magda 
> wrote:
> > >
> > >> Dmitriy,
> > >>
> > >> No, that's an honor for us to see you in this role ;) Both Andrey
> Gura,
> > >> Anton Vinogradov are our release-management veterans. Please feel free
> > to
> > >> contact them directly.
> > >>
> > >> Could you take over this ticket review and include it in the release:
> > >> https://issues.apache.org/jira/browse/IGNITE-8740
> > >>
> > >> It's not good that we have spring integration broken in some places in
> > >> several releases. I would treat is as a usability blocker and
> > regression.
> > >>
> > >> --
> > >> Denis
> > >>
> > >>
> > >>
> > >> On Fri, Jun 22, 2018 at 3:06 AM Dmitry Pavlov 
> > >> wrote:
> > >>
> > >> > Hi Alexey,
> > >> >
> > >> > Sure, it will be honor for me.
> > >> >
> > >> > In the same time I relatevely new in this area, so I would highly
> > >> > appreciate any assistance of experienced community members to make
> > this
> > >> > happen.
> > >> >
> > >> > Sincerely,
> > >> >
> > >> > пт, 22 июн. 2018 г. в 12:18, Alexey Goncharuk <
> > >> alexey.goncha...@gmail.com
> > >> > >:
> > >> >
> > >> > > Denis,
> > >> > >
> > >> > > Currently, I am not aware of anybody who can immediately review
> and
> > >> > > sign-off the suggested patch. The original scope of tickets have
> > been
> > >> > > resolved, so I suggest to move on with what we have now.
> > >> > >
> > >> > > I will not be able to continue with the release process until
> > Thursday
> > >> > > next week.
> > >> > >
> > >> > > Dmitriy Pavlov, do you mind taking over and finishing the release?
> > >> > >
> > >> > > чт, 21 июн. 2018 г. в 23:02, Denis Magda :
> > >> > >
> > >> > >> Folks,
> > >> > >>
> > >> > >> This release no longer reminds an emergency one :) Are we done
> with
> > >> the
> > >> > >> scope, who is a release manager?
> > >> > >>
> > >> > >> From my side, I'd like us to review and add the fix for broken
> > Spring
> > >> > >> integration which is a significant regression:
> > >> > >> https://issues.apache.org/jira/browse/IGNITE-8740
> > >> > >>
> > >> > >> --
> > >> > >> Denis
> > >> > >>
> > >> > >> On Mon, Jun 18, 2018 at 5:16 AM Alexey Goncharuk <
> > >> > >> alexey.goncha...@gmail.com>
> > >> > >> wrote:
> > >> > >>
> > >> > >> > Hi Petr,
> > >> > >> >
> > >> > >> > Who will be able to make the review for the suggested patch? I
> > >> would
> > >> > >> like
> > >> > >> > to freeze the branch and start preparing the release.
> > >> > >> >
> > >> > >> > пт, 15 июн. 2018 г. в 11:45, Petr Ivanov  >:
> > >> > >> >
> > >> > >> >

  1   2   3   4   5   6   7   >