Re: [Discussion] Apache Ignite 2.11 Scope Freeze

2021-06-08 Thread Dmitry Pavlov
Hi Folks,

Branch divergence has been completed. Sorry for the delay, it was my fault. Now 
branch for 2.11 is now available
https://github.com/apache/ignite/tree/ignite-2.11
https://gitbox.apache.org/repos/asf?p=ignite.git;a=shortlog;h=refs/heads/ignite-2.11

Who could help with updating TC bot configuration (json)?
I suggest changing tracked branch ignite-2.10-nightly to ignite-2.11-nightly 
and run 'ignite-2.11' instread. See also 
https://mtcga.gridgain.com/current.html?branch=ignite-2.10-nightly

Sincerely,
Dmitriy Pavlov


On 2021/06/04 13:51:28, Pavel Pereslegin  wrote: 
> Hopefully we'll be done by the end of next week (2021.06.11).
> 
> пт, 4 июн. 2021 г. в 16:06, Alexey Gidaspov :
> >
> > Hello, Pavel.
> >
> > Can you specify the date more precisly?
> >
> > On 2021/06/04 12:05:53, Pavel Pereslegin  wrote:
> > > Hello Alexey.
> > >
> > > We have implemented a feature to automatically restore the cache group
> > > from a snapshot [1].
> > > But this feature requires CLI management [2], which is currently on
> > > review and should also be included in 2.11. We plan to finish with it
> > > next week.
> > >
> > > [1] https://issues.apache.org/jira/browse/IGNITE-13805
> > > [2] https://issues.apache.org/jira/browse/IGNITE-14723
> > >
> > > пт, 4 июн. 2021 г. в 13:01, Dmitry Pavlov :
> > > >
> > > > I've updated the page 
> > > > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.11
> > > >
> > > >  since final freeze is technically possible only after branch 
> > > > divergence (see also 
> > > > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process)
> > > >
> > > > Sincerely
> > > >
> > > > On 2021/06/04 09:56:15, Alexey Gidaspov  wrote:
> > > > > I'm planning to diverge branch at 16:00 MSK 7 June, 2021
> > > > >
> > > > > And here is 2.11 release wiki page [1]
> > > > >
> > > > > [1] 
> > > > > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.11
> > > > >
> > > > > On 2021/06/04 09:11:49, Alexey Gidaspov  wrote:
> > > > > > Hi, Igniters!
> > > > > >
> > > > > > I'm going to start scope freeze and leave only Resolved tickets in 
> > > > > > it [1]. You are welcome to discuss.
> > > > > >
> > > > > > [1] 
> > > > > > https://lists.apache.org/thread.html/a4be115d2bd4318ae958ac91aba40294dfd62f293b3cb264c8fcf0ae%40%3Cdev.ignite.apache.org%3E
> > > > > >
> > > > >
> > >
> 


[DISCUSSION] Brand new distributed environment testing framework ready to be reviewed/merged.

2021-06-08 Thread Anton Vinogradov
Igniters,
Let me present a framework, we developed, that allows automating Apache
Ignite testing on a real cluster.
The framework was initially presented at Ignite Summit.

In brief,
The framework allows automating operations with any applications on a real
cluster using ssh in a form of a python test.

Features:
- Ignite nodes can be started/stopped on a Docker or a real cluster with
any custom configuration
- Any AI version is supported (released or compiled from sources)
- Ignite forks are also supported «out of the box»
- Any other application execution is also possible, eg. we implemented
starters for Spark and Zookeeper
- Cluster can be managed using the control.sh, we made this a part of the
test API
- Custom Java applications can be executed remotely with/without a built-in
Ignite node or a Thin client
- Any ssh command can be executed remotely, and the result will be
available locally (at the python test)
- Network can be broken by iptables change to check communication issues
- Tests can be executed in parallel when cluster size bigger than tests
requirements

As a result, seems, we may automate any testing scenario we can even
imagine.

Framework based on Ducktape [1] library from Kafka team, that's why we
called it Ducktests.

The Ducktests were developed during work on IEP-56 [2] and already were
used during the work on IEP-45 [3].
IEP-45 measurement results examples [4.1] [4.2] were demonstrated at the
HighLoad conference last month.

Code available at PR-9117 [5] and ready to be reviewed/merged.
Feel free to ask questions or make proposals.

[1] https://ducktape-docs.readthedocs.io/en/latest/index.html
[2]
https://cwiki.apache.org/confluence/display/IGNITE/IEP-56%3A+Distributed+environment+tests
[3]
https://cwiki.apache.org/confluence/display/IGNITE/IEP-45%3A+Crash+Recovery+Speed-Up
[4.1] https://youtu.be/UZsvCNjbkww?t=1065 (in Russian)
[4.2] https://youtu.be/UZsvCNjbkww?t=1609 (in Russian)
[5] https://github.com/apache/ignite/pull/9117


Re[2]: [Discussion] Apache Ignite 2.11 Scope Freeze

2021-06-08 Thread Zhenya Stanilovsky

Hi ! I found that very important issue [1] (already in master) is not planned 
to be in 2.11, may be it still possible to take it into scope ?
 
thanks !
 
[1]  https://issues.apache.org/jira/browse/IGNITE-14739
 
>Hi Folks,
>
>Branch divergence has been completed. Sorry for the delay, it was my fault. 
>Now branch for 2.11 is now available
>https://github.com/apache/ignite/tree/ignite-2.11
>https://gitbox.apache.org/repos/asf?p=ignite.git;a=shortlog;h=refs/heads/ignite-2.11
>
>Who could help with updating TC bot configuration (json)?
>I suggest changing tracked branch ignite-2.10-nightly to ignite-2.11-nightly 
>and run 'ignite-2.11' instread. See also  
>https://mtcga.gridgain.com/current.html?branch=ignite-2.10-nightly
>
>Sincerely,
>Dmitriy Pavlov
>
>
>On 2021/06/04 13:51:28, Pavel Pereslegin < xxt...@gmail.com > wrote:
>> Hopefully we'll be done by the end of next week (2021.06.11).
>>
>> пт, 4 июн. 2021 г. в 16:06, Alexey Gidaspov < olive.c...@gmail.com >:
>> >
>> > Hello, Pavel.
>> >
>> > Can you specify the date more precisly?
>> >
>> > On 2021/06/04 12:05:53, Pavel Pereslegin < xxt...@gmail.com > wrote:
>> > > Hello Alexey.
>> > >
>> > > We have implemented a feature to automatically restore the cache group
>> > > from a snapshot [1].
>> > > But this feature requires CLI management [2], which is currently on
>> > > review and should also be included in 2.11. We plan to finish with it
>> > > next week.
>> > >
>> > > [1]  https://issues.apache.org/jira/browse/IGNITE-13805
>> > > [2]  https://issues.apache.org/jira/browse/IGNITE-14723
>> > >
>> > > пт, 4 июн. 2021 г. в 13:01, Dmitry Pavlov < dpav...@apache.org >:
>> > > >
>> > > > I've updated the page  
>> > > > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.11
>> > > >
>> > > > since final freeze is technically possible only after branch 
>> > > > divergence (see also  
>> > > > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process )
>> > > >
>> > > > Sincerely
>> > > >
>> > > > On 2021/06/04 09:56:15, Alexey Gidaspov < olive.c...@gmail.com > wrote:
>> > > > > I'm planning to diverge branch at 16:00 MSK 7 June, 2021
>> > > > >
>> > > > > And here is 2.11 release wiki page [1]
>> > > > >
>> > > > > [1]  
>> > > > > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.11
>> > > > >
>> > > > > On 2021/06/04 09:11:49, Alexey Gidaspov < olive.c...@gmail.com > 
>> > > > > wrote:
>> > > > > > Hi, Igniters!
>> > > > > >
>> > > > > > I'm going to start scope freeze and leave only Resolved tickets in 
>> > > > > > it [1]. You are welcome to discuss.
>> > > > > >
>> > > > > > [1]  
>> > > > > > https://lists.apache.org/thread.html/a4be115d2bd4318ae958ac91aba40294dfd62f293b3cb264c8fcf0ae%40%3Cdev.ignite.apache.org%3E
>> > > > > >
>> > > > >
>> > >
>> 
 
 
 
 

Re: Re[2]: [Discussion] Apache Ignite 2.11 Scope Freeze

2021-06-08 Thread Dmitry Pavlov
Hi,

To my opinion it's fine, since we freezed release scope, but haven't freezed 
the code yet.

So, we're at Phase2 - Rampdown phase - 
https://cwiki.apache.org/confluence/display/IGNITE/Release+Process

Code freeze is planned to 14 June, see also 
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.11

The last word is for RM here. Alexey, WDYT?

Sincerely,
Dmitriy Pavlov

On 2021/06/08 12:54:26, Zhenya Stanilovsky  wrote: 
> 
> Hi ! I found that very important issue [1] (already in master) is not planned 
> to be in 2.11, may be it still possible to take it into scope ?
>  
> thanks !
>  
> [1]  https://issues.apache.org/jira/browse/IGNITE-14739
>  
> >Hi Folks,
> >
> >Branch divergence has been completed. Sorry for the delay, it was my fault. 
> >Now branch for 2.11 is now available
> >https://github.com/apache/ignite/tree/ignite-2.11
> >https://gitbox.apache.org/repos/asf?p=ignite.git;a=shortlog;h=refs/heads/ignite-2.11
> >
> >Who could help with updating TC bot configuration (json)?
> >I suggest changing tracked branch ignite-2.10-nightly to ignite-2.11-nightly 
> >and run 'ignite-2.11' instread. See also  
> >https://mtcga.gridgain.com/current.html?branch=ignite-2.10-nightly
> >
> >Sincerely,
> >Dmitriy Pavlov
> >
> >
> >On 2021/06/04 13:51:28, Pavel Pereslegin < xxt...@gmail.com > wrote:
> >> Hopefully we'll be done by the end of next week (2021.06.11).
> >>
> >> пт, 4 июн. 2021 г. в 16:06, Alexey Gidaspov < olive.c...@gmail.com >:
> >> >
> >> > Hello, Pavel.
> >> >
> >> > Can you specify the date more precisly?
> >> >
> >> > On 2021/06/04 12:05:53, Pavel Pereslegin < xxt...@gmail.com > wrote:
> >> > > Hello Alexey.
> >> > >
> >> > > We have implemented a feature to automatically restore the cache group
> >> > > from a snapshot [1].
> >> > > But this feature requires CLI management [2], which is currently on
> >> > > review and should also be included in 2.11. We plan to finish with it
> >> > > next week.
> >> > >
> >> > > [1]  https://issues.apache.org/jira/browse/IGNITE-13805
> >> > > [2]  https://issues.apache.org/jira/browse/IGNITE-14723
> >> > >
> >> > > пт, 4 июн. 2021 г. в 13:01, Dmitry Pavlov < dpav...@apache.org >:
> >> > > >
> >> > > > I've updated the page  
> >> > > > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.11
> >> > > >
> >> > > > since final freeze is technically possible only after branch 
> >> > > > divergence (see also  
> >> > > > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process )
> >> > > >
> >> > > > Sincerely
> >> > > >
> >> > > > On 2021/06/04 09:56:15, Alexey Gidaspov < olive.c...@gmail.com > 
> >> > > > wrote:
> >> > > > > I'm planning to diverge branch at 16:00 MSK 7 June, 2021
> >> > > > >
> >> > > > > And here is 2.11 release wiki page [1]
> >> > > > >
> >> > > > > [1]  
> >> > > > > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.11
> >> > > > >
> >> > > > > On 2021/06/04 09:11:49, Alexey Gidaspov < olive.c...@gmail.com > 
> >> > > > > wrote:
> >> > > > > > Hi, Igniters!
> >> > > > > >
> >> > > > > > I'm going to start scope freeze and leave only Resolved tickets 
> >> > > > > > in it [1]. You are welcome to discuss.
> >> > > > > >
> >> > > > > > [1]  
> >> > > > > > https://lists.apache.org/thread.html/a4be115d2bd4318ae958ac91aba40294dfd62f293b3cb264c8fcf0ae%40%3Cdev.ignite.apache.org%3E
> >> > > > > >
> >> > > > >
> >> > >
> >> 
>  
>  
>  
>  


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

2021-06-08 Thread dpavlov . tasks
Hi Igniters,

 I've detected some new issue on TeamCity to be handled. You are more than 
welcomed to help.

 *Test with high flaky rate in master 
IgniteClientReconnectMassiveShutdownSslTest.testMassiveServersShutdown2 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-4548730100558253976&branch=%3Cdefault%3E&tab=testDetails
 No changes in the build

 - Here's a reminder of what contributors were agreed to do 
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute 
 - Should you have any questions please contact dev@ignite.apache.org 

Best Regards,
Apache Ignite TeamCity Bot 
https://github.com/apache/ignite-teamcity-bot
Notification generated at 22:40:19 08-06-2021 


[DISCUSSION] Release python-0.5.0

2021-06-08 Thread Ivan Daschinsky
Hi, folks!

I suppose, that it's time to release the next version of python thin
client, because we are ready to ship new cool features.

1. Expiry policy (TTL) support (merged to master) [1]
2. Transactions (patch available) [2]
3. As part of tx api, huge performance improvement of asyncio [3]
4. Enable partition awareness by default

Also, few bugs have been fixed.

There is a full list of tickets for this release [4]. Most of them are
resolved, transactions [2] are in PA state, unresolved tickets are
trivial (documentation and enabling PA by default). I suppose
that we can freeze scope at the end of next week and prepare RC for voting.

WDYT?

[1] -- https://issues.apache.org/jira/browse/IGNITE-14595
[2] -- https://issues.apache.org/jira/browse/IGNITE-12467
[3] -- 
https://issues.apache.org/jira/browse/IGNITE-12467?focusedCommentId=17359293&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17359293
[4] -- 
https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%20python-0.5.0