Apache Ignite 2.7.6 (Time, Scope, and Release manager)

[Ivan Pavlukhina]

Zhenya, Dmitriy,

>>> hi Dmitriy, Ivan Pavlukhin suggest to exclude IGNITE-12061 from 2.7.6, i
>>> have no clue - why,

The reason here is a lack of time to ensure that everything is fine there. The 
patch is valuable but not so trivial. Honestly, I find it wrong to merge a 
changes I am not sure with (yet). Especially in a hurry.

Sent from my iPhone

> On 17 Aug 2019, at 13:13, Zhenya Stanilovsky  
> wrote:
> 
> I hope there is no data loss here, but index tree corruption can be easily 
> obtained.
> Impact: someone believe that inline_size has been changed due to index 
> recreation but that`s not so.
> 
>> Hi Evgeniy,
>> 
>> I can't review this change. We need approve of a committer, who is  SQL
>> expert,  here.
>> 
>> What would be an impact on users if we don' include it into 2.7.6?
>> 
>> Is it a critical/data loss issue? If not, I agree it can wait for 2.8
>> release.
>> 
>> Sincerely,
>> Dmitriy Pavlov
>> 
>> сб, 17 авг. 2019 г. в 12:43, Zhenya Stanilovsky :
>> 
>>> hi Dmitriy, Ivan Pavlukhin suggest to exclude IGNITE-12061 from 2.7.6, i
>>> have no clue - why, but seems i can`t merge it without his visa.
>>> thanks.
>>> 
>>> > Hi Igniters,
>>> >
>>> > I also suggest adding newly created critical bug into scope
>>> > https://issues.apache.org/jira/browse/IGNITE-12081 (already assigned
>>> > since
>>> > it was discussed before in private communication).
>>> >
>>> > It is not a regression but can cause data corruption, so I'd rather wait
>>> > for the fix.
>>> >
>>> > Eduard Shangareev, Stanilovsky Evgeny I'm going to assemble the first RC
>>> > during the weekend, so I would be grateful if fixes can be cherry-piked
>>> > to
>>> > the branch today. Also, since narrow time limit, please trigger Run All
>>> > after each commit in 2.7.6. This will allow to immediately locate which
>>> > commit caused test failure.
>>> >
>>> > Sincerely,
>>> > Dmitriy Pavlov
>>> >
>>> > пт, 16 авг. 2019 г. в 13:33, Dmitriy Pavlov :
>>> >
>>> >> Hi Ivan,
>>> >>
>>> >> yes, sure.
>>> >>
>>> >> If it is cherry-picked without conflicts, just push it.
>>> >>
>>> >>  If it contains conflicts it is better to push to 2.7.6-based branch and
>>> >> start additional run-all, example
>>> >> https://github.com/apache/ignite/pull/6781 -it is PR for ignite-9562,
>>> >> base: 2.7.6
>>> >>
>>> >> Sincerely,
>>> >> Dmitriy Pavlov
>>> >>
>>> >> пт, 16 авг. 2019 г. в 12:28, Павлухин Иван :
>>> >>
>>> >>> Dmitriy,
>>> >>>
>>> >>> We accomplished with
>>> https://issues.apache.org/jira/browse/IGNITE-12068
>>> >>>
>>> >>> Should I cherry-pick it to release branch?
>>> >>>
>>> >>> пт, 16 авг. 2019 г. в 11:28, Dmitriy Pavlov :
>>> >>> >
>>> >>> > Hi Igniters,
>>> >>> >
>>> >>> > Yesterday was a planned date of code freeze.
>>> >>> >
>>> >>> > So the scope (related both to features and to bugs) is final, we're
>>> >>> > entering to stabilization phase. Nothing can be included into scope
>>> >>> besides
>>> >>> > blockers approved by the release manager.
>>> >>> > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
>>> >>> > 
>>> >>> >
>>> >>> > Unresolved tickets are:
>>> >>> > IGNITE-12071  Eduard Shangareev
>>> >>> > IGNITE-12068 Ivan Pavlukhin
>>> >>> > IGNITE-9562 Eduard Shangareev
>>> >>> > IGNITE-12057 Anton Kalashnikov
>>> >>> > IGNITE-12061 Stanilovsky Evgeny
>>> >>> >
>>> >>> > Sincerely,
>>> >>> > Dmitriy Pavlov
>>> >>> >
>>> >>> > чт, 15 авг. 2019 г. в 20:12, Zhenya Stanilovsky >> >:
>>> >>> >
>>> >>> > > Dmitriy, review passed, plz proceed.
>>> >>> > > thanks !
>>> >>> > >
>>> >>> > > > I removed  https://issues.apache.org/jira/browse/IGNITE-12032
>>> >>> until
>>> >>> > > > nobody
>>> >>> > > > volunteer to complete the task.
>>> >>> > > >
>>> >>> > > > Evgeniy, please keep me updated about IGNITE-12061.
>>> >>> > > >
>>> >>> > > > чт, 15 авг. 2019 г. в 16:56, Zhenya Stanilovsky
>>> >>> > > > >> >>> > > >> :
>>> >>> > > >
>>> >>> > > >> yep, i`l try to call someone who probably familiar with this
>>> >>> problem.
>>> >>> > > >>
>>> >>> > > >> >
>>> >>> > > >> >
>>> >>> > > >> >Ok, I've removed Spark from the scope.
>>> >>> > > >> >
>>> >>> > > >> >What about the unassigned issue related to ODBC? It is not
>>> >>> looking like
>>> >>> > > >> >somebody will fix it before release.
>>> >>> > > >> >
>>> >>> > > >> >Evgeniy Stanilovsky, what about
>>> >>> > > >> >https://issues.apache.org/jira/browse/IGNITE-12061
>>> >>> > > >> ><
>>> >>> https://issues.apache.org/jira/browse/IGNITE-12061?src=confmacro >
>>> >>> > > >> >do you have someone to review the fix?
>>> >>> > > >> >
>>> >>> > > >> >чт, 15 авг. 2019 г. в 16:05, Denis Magda < dma...@apache.org
>>> >:
>>> >>> > > >> >
>>> >>> > > >> >> Dmitry,
>>> >>> > > >> >>
>>> >>> > > >> >> It would be better for us to put off the Spark upgrade until
>>> >>> 2.8 as
>>> >>> > > >> Nikolay
>>> >>> > > >> >> suggested. Let's release 2.7.6 as quickly as possible to let
>>> >>> roll out
>>> >>> > > >> fixes
>>> >>> >

Re: SQL query timeout: in progress or abandoned

[Saikat Maitra]

Hi Ivan, Denis

Thank you for your feedback, I am looking into the changes needed for this
issue.

I am also looking into these configurations parameters
https://apacheignite.readme.io/v2.2/docs/configuration-parameters to see if
there are similar attributes being used in  SqlFieldsQuery and SqlQuery.


Regards,

Saikat



On Thu, Aug 15, 2019 at 6:13 AM Павлухин Иван  wrote:

> Saikat, Denis,
>
> I left comments in the ticket [1].
>
> [1] https://issues.apache.org/jira/browse/IGNITE-7285
>
> вт, 13 авг. 2019 г. в 21:53, Denis Magda :
> >
> > Hi Saikat,
> >
> > Thanks for a quick turnaround! Ivan, could you please step in and do a
> > review?
> >
> > -
> > Denis
> >
> >
> > On Sun, Aug 11, 2019 at 6:26 AM Saikat Maitra 
> > wrote:
> >
> > > Hi Denis, Ivan
> > >
> > > As discussed I have updated the PR and incorporated review comments.
> > >
> > > https://github.com/apache/ignite/pull/6490/files
> > >
> > > Please take a look and share your feedback.
> > >
> > > Regard,
> > > Saikat
> > >
> > >
> > >
> > > On Sat, Aug 10, 2019 at 5:51 PM Saikat Maitra  >
> > > wrote:
> > >
> > > > Hello Denis, Ivan
> > > >
> > > > Yes, I can take up the changes for IGNITE-7825.
> > > >
> > > > I had a doubt on the usage of the Default Query Timeout.
> > > >
> > > > I had raised the PR in an assumption that Default Query Timeout will
> only
> > > > be used if user had not provided Cache Query Timeout
> > > >
> > > > https://github.com/apache/ignite/pull/6490/files
> > > >
> > > > I wanted to discuss if it is correct intended usage of Default Query
> > > > Timeout or should we reconsider?
> > > >
> > > > Regards,
> > > > Saikat
> > > >
> > > >
> > > >
> > > > On Fri, Aug 9, 2019 at 12:11 PM Denis Magda 
> wrote:
> > > >
> > > >> Ivan, thanks for sharing this discussion. Let's use it for our
> > > >> conversation.
> > > >>
> > > >> -
> > > >> Denis
> > > >>
> > > >>
> > > >> On Thu, Aug 8, 2019 at 11:15 PM Павлухин Иван 
> > > >> wrote:
> > > >>
> > > >> > Just for the protocol. There was an original dev-list discussion
> [1].
> > > >> > Added a link to the ticket as well.
> > > >> >
> > > >> > [1]
> > > >> >
> > > >>
> > >
> http://apache-ignite-developers.2346864.n4.nabble.com/IGNITE-7285-Add-default-query-timeout-td41828.html
> > > >> >
> > > >> > пт, 9 авг. 2019 г. в 01:22, Denis Magda :
> > > >> > >
> > > >> > > Hey Saikat,
> > > >> > >
> > > >> > > Are you still working on this ticket?
> > > >> > > https://issues.apache.org/jira/browse/IGNITE-7285
> > > >> > >
> > > >> > > Seems that's the last API that doesn't support timeouts - JDBC
> and
> > > >> ODBC
> > > >> > > drivers already go with it.
> > > >> > >
> > > >> > > If you don't have time to complete the changes then someone else
> > > from
> > > >> the
> > > >> > > community can take over. We see a lot of demand for this API and
> > > here
> > > >> is
> > > >> > > one example:
> > > >> > >
> > > >> >
> > > >>
> > >
> https://stackoverflow.com/questions/57275301/how-to-set-a-query-timeout-for-apache-ignite-cache
> > > >> > >
> > > >> > > -
> > > >> > > Denis
> > > >> >
> > > >> >
> > > >> >
> > > >> > --
> > > >> > Best regards,
> > > >> > Ivan Pavlukhin
> > > >> >
> > > >>
> > > >
> > >
>
>
>
> --
> Best regards,
> Ivan Pavlukhin
>

Re: .NET java thread count keeps growing

[Raymond Wilson]

We have observed a similar problem but have not characterised it well
enough to report on the list yet.

We are using IA .Net 2.7.5.

Sent from my iPhone

> On 17/08/2019, at 1:45 PM, Ilya Kasnacheev  wrote:
>
> Hello!
>
> Can we get back to this question? It rears its ugly head again:
> https://stackoverflow.com/questions/57513576/apache-ignite-spawns-too-much-threads/57523214
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> вс, 23 сент. 2018 г. в 15:20, Pavel Tupitsyn :
>
>> Denis,
>>
>> Can't say for sure, did not investigate this yet. I'll try to find time
>> next week and get back to you.
>>
>>> On Sat, Sep 22, 2018 at 4:23 AM Denis Magda  wrote:
>>>
>>> Pavel,
>>>
>>> Do you think we can get it fixed in 2.7 time frame?
>>>
>>> --
>>> Denis
>>>
>>> -- Forwarded message -
>>> From: Ilya Kasnacheev 
>>> Date: Tue, Sep 18, 2018 at 9:30 AM
>>> Subject: Re: .NET java thread count keeps growing
>>> To: 
>>>
>>>
>>> Hello!
>>>
>>> I can observe the problem that you are describing. I have created a
>> ticket
>>> https://issues.apache.org/jira/browse/IGNITE-9638
>>>
>>> Regards,
>>> --
>>> Ilya Kasnacheev
>>>
>>>
>>> пн, 17 сент. 2018 г. в 20:21, Alew :
>>>
 Hi, I found a way to reproduce the issue.

 I think it is related to .net thread identity.

 New .net thread leads to new java thread.



 On 17/09/2018 15:04, Ilya Kasnacheev wrote:

 Hello!

 You seem to have 3000 threads of form "Thread-", which is not what
 Ignite usually uses, and they're all empty.
 This is mysterious so I urge you to share the sample reproducer (or,
 barring that, code snippet) that leads to such behavior.

 By the way, do you observe any errors in the log?

 Regards,
 --
 Ilya Kasnacheev


 вс, 16 сент. 2018 г. в 4:09, Alew :

> Hi!
>
> I have growing java thread count. The application crashes with OOME.
>> The
> application is very simple, only reading values in a cache.
>
> Any suggestion to debug this issue?
>
> Ignite 2.4
>
>
>

>>

Re: .NET java thread count keeps growing

[Ilya Kasnacheev]

Hello!

Can we get back to this question? It rears its ugly head again:
https://stackoverflow.com/questions/57513576/apache-ignite-spawns-too-much-threads/57523214

Regards,
-- 
Ilya Kasnacheev


вс, 23 сент. 2018 г. в 15:20, Pavel Tupitsyn :

> Denis,
>
> Can't say for sure, did not investigate this yet. I'll try to find time
> next week and get back to you.
>
> On Sat, Sep 22, 2018 at 4:23 AM Denis Magda  wrote:
>
> > Pavel,
> >
> > Do you think we can get it fixed in 2.7 time frame?
> >
> > --
> > Denis
> >
> > -- Forwarded message -
> > From: Ilya Kasnacheev 
> > Date: Tue, Sep 18, 2018 at 9:30 AM
> > Subject: Re: .NET java thread count keeps growing
> > To: 
> >
> >
> > Hello!
> >
> > I can observe the problem that you are describing. I have created a
> ticket
> > https://issues.apache.org/jira/browse/IGNITE-9638
> >
> > Regards,
> > --
> > Ilya Kasnacheev
> >
> >
> > пн, 17 сент. 2018 г. в 20:21, Alew :
> >
> >> Hi, I found a way to reproduce the issue.
> >>
> >> I think it is related to .net thread identity.
> >>
> >> New .net thread leads to new java thread.
> >>
> >>
> >>
> >> On 17/09/2018 15:04, Ilya Kasnacheev wrote:
> >>
> >> Hello!
> >>
> >> You seem to have 3000 threads of form "Thread-", which is not what
> >> Ignite usually uses, and they're all empty.
> >> This is mysterious so I urge you to share the sample reproducer (or,
> >> barring that, code snippet) that leads to such behavior.
> >>
> >> By the way, do you observe any errors in the log?
> >>
> >> Regards,
> >> --
> >> Ilya Kasnacheev
> >>
> >>
> >> вс, 16 сент. 2018 г. в 4:09, Alew :
> >>
> >>> Hi!
> >>>
> >>> I have growing java thread count. The application crashes with OOME.
> The
> >>> application is very simple, only reading values in a cache.
> >>>
> >>> Any suggestion to debug this issue?
> >>>
> >>> Ignite 2.4
> >>>
> >>>
> >>>
> >>
>

Re: Re[4]: Apache Ignite 2.7.6 (Time, Scope, and Release manager)

[Zhenya Stanilovsky]

I hope there is no data loss here, but index tree corruption can be easily  
obtained.
Impact: someone believe that inline_size has been changed due to index  
recreation but that`s not so.



Hi Evgeniy,

I can't review this change. We need approve of a committer, who is  SQL
expert,  here.

What would be an impact on users if we don' include it into 2.7.6?

Is it a critical/data loss issue? If not, I agree it can wait for 2.8
release.

Sincerely,
Dmitriy Pavlov

сб, 17 авг. 2019 г. в 12:43, Zhenya Stanilovsky :


hi Dmitriy, Ivan Pavlukhin suggest to exclude IGNITE-12061 from 2.7.6, i
have no clue - why, but seems i can`t merge it without his visa.
thanks.

> Hi Igniters,
>
> I also suggest adding newly created critical bug into scope
> https://issues.apache.org/jira/browse/IGNITE-12081 (already assigned
> since
> it was discussed before in private communication).
>
> It is not a regression but can cause data corruption, so I'd rather  
wait

> for the fix.
>
> Eduard Shangareev, Stanilovsky Evgeny I'm going to assemble the first  
RC
> during the weekend, so I would be grateful if fixes can be  
cherry-piked

> to
> the branch today. Also, since narrow time limit, please trigger Run  
All
> after each commit in 2.7.6. This will allow to immediately locate  
which

> commit caused test failure.
>
> Sincerely,
> Dmitriy Pavlov
>
> пт, 16 авг. 2019 г. в 13:33, Dmitriy Pavlov :
>
>> Hi Ivan,
>>
>> yes, sure.
>>
>> If it is cherry-picked without conflicts, just push it.
>>
>>  If it contains conflicts it is better to push to 2.7.6-based branch  
and

>> start additional run-all, example
>> https://github.com/apache/ignite/pull/6781 -it is PR for ignite-9562,
>> base: 2.7.6
>>
>> Sincerely,
>> Dmitriy Pavlov
>>
>> пт, 16 авг. 2019 г. в 12:28, Павлухин Иван :
>>
>>> Dmitriy,
>>>
>>> We accomplished with
https://issues.apache.org/jira/browse/IGNITE-12068
>>>
>>> Should I cherry-pick it to release branch?
>>>
>>> пт, 16 авг. 2019 г. в 11:28, Dmitriy Pavlov :
>>> >
>>> > Hi Igniters,
>>> >
>>> > Yesterday was a planned date of code freeze.
>>> >
>>> > So the scope (related both to features and to bugs) is final,  
we're
>>> > entering to stabilization phase. Nothing can be included into  
scope

>>> besides
>>> > blockers approved by the release manager.
>>> > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
>>> >  


>>> >
>>> > Unresolved tickets are:
>>> > IGNITE-12071  Eduard Shangareev
>>> > IGNITE-12068 Ivan Pavlukhin
>>> > IGNITE-9562 Eduard Shangareev
>>> > IGNITE-12057 Anton Kalashnikov
>>> > IGNITE-12061 Stanilovsky Evgeny
>>> >
>>> > Sincerely,
>>> > Dmitriy Pavlov
>>> >
>>> > чт, 15 авг. 2019 г. в 20:12, Zhenya Stanilovsky  

>:
>>> >
>>> > > Dmitriy, review passed, plz proceed.
>>> > > thanks !
>>> > >
>>> > > > I removed  https://issues.apache.org/jira/browse/IGNITE-12032
>>> until
>>> > > > nobody
>>> > > > volunteer to complete the task.
>>> > > >
>>> > > > Evgeniy, please keep me updated about IGNITE-12061.
>>> > > >
>>> > > > чт, 15 авг. 2019 г. в 16:56, Zhenya Stanilovsky
>>> > > > >> > > >> :
>>> > > >
>>> > > >> yep, i`l try to call someone who probably familiar with this
>>> problem.
>>> > > >>
>>> > > >> >
>>> > > >> >
>>> > > >> >Ok, I've removed Spark from the scope.
>>> > > >> >
>>> > > >> >What about the unassigned issue related to ODBC? It is not
>>> looking like
>>> > > >> >somebody will fix it before release.
>>> > > >> >
>>> > > >> >Evgeniy Stanilovsky, what about
>>> > > >> >https://issues.apache.org/jira/browse/IGNITE-12061
>>> > > >> ><
>>> https://issues.apache.org/jira/browse/IGNITE-12061?src=confmacro >
>>> > > >> >do you have someone to review the fix?
>>> > > >> >
>>> > > >> >чт, 15 авг. 2019 г. в 16:05, Denis Magda < dma...@apache.org
>:
>>> > > >> >
>>> > > >> >> Dmitry,
>>> > > >> >>
>>> > > >> >> It would be better for us to put off the Spark upgrade  
until

>>> 2.8 as
>>> > > >> Nikolay
>>> > > >> >> suggested. Let's release 2.7.6 as quickly as possible to  
let

>>> roll out
>>> > > >> fixes
>>> > > >> >> for the critical issues from the scope.
>>> > > >> >>
>>> > > >> >>
>>> > > >> >> -
>>> > > >> >> Denis
>>> > > >> >>
>>> > > >> >>
>>> > > >> >> On Thu, Aug 15, 2019 at 3:29 PM Dmitriy Pavlov <
>>> dpav...@apache.org
>>> > > >
>>> > > >> wrote:
>>> > > >> >>
>>> > > >> >> > Nikolay, how long does it take to update? I will be
>>> traveling
>>> > > from
>>> > > >> 28
>>> > > >> Aug
>>> > > >> >> > till 16 Sept. We can select new dates for release if the
>>> majority
>>> > > >> of
>>> > > >> >> fixes
>>> > > >> >> > can be done by 16 Sept, but can't be by 20 Aug. Denis,
>>> please
>>> share
>>> > > >> your
>>> > > >> >> > vision about selecting new dates.
>>> > > >> >> >
>>> > > >> >> > *Voting Date: *Sept 18, 2019
>>> > > >> >> >
>>> > > >> >> > *Release Date: *Sept 23, 2019
>>> > > >> >> >
>>> > > >> >> > Issue   
https://issues.apache.org/jira/browse/IGNITE-12032

>>> > > >> >> > <

Re: Re[4]: Apache Ignite 2.7.6 (Time, Scope, and Release manager)

[Dmitriy Pavlov]

Hi Evgeniy,

I can't review this change. We need approve of a committer, who is  SQL
expert,  here.

What would be an impact on users if we don' include it into 2.7.6?

Is it a critical/data loss issue? If not, I agree it can wait for 2.8
release.

Sincerely,
Dmitriy Pavlov

сб, 17 авг. 2019 г. в 12:43, Zhenya Stanilovsky :

> hi Dmitriy, Ivan Pavlukhin suggest to exclude IGNITE-12061 from 2.7.6, i
> have no clue - why, but seems i can`t merge it without his visa.
> thanks.
>
> > Hi Igniters,
> >
> > I also suggest adding newly created critical bug into scope
> > https://issues.apache.org/jira/browse/IGNITE-12081 (already assigned
> > since
> > it was discussed before in private communication).
> >
> > It is not a regression but can cause data corruption, so I'd rather wait
> > for the fix.
> >
> > Eduard Shangareev, Stanilovsky Evgeny I'm going to assemble the first RC
> > during the weekend, so I would be grateful if fixes can be cherry-piked
> > to
> > the branch today. Also, since narrow time limit, please trigger Run All
> > after each commit in 2.7.6. This will allow to immediately locate which
> > commit caused test failure.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > пт, 16 авг. 2019 г. в 13:33, Dmitriy Pavlov :
> >
> >> Hi Ivan,
> >>
> >> yes, sure.
> >>
> >> If it is cherry-picked without conflicts, just push it.
> >>
> >>  If it contains conflicts it is better to push to 2.7.6-based branch and
> >> start additional run-all, example
> >> https://github.com/apache/ignite/pull/6781 -it is PR for ignite-9562,
> >> base: 2.7.6
> >>
> >> Sincerely,
> >> Dmitriy Pavlov
> >>
> >> пт, 16 авг. 2019 г. в 12:28, Павлухин Иван :
> >>
> >>> Dmitriy,
> >>>
> >>> We accomplished with
> https://issues.apache.org/jira/browse/IGNITE-12068
> >>>
> >>> Should I cherry-pick it to release branch?
> >>>
> >>> пт, 16 авг. 2019 г. в 11:28, Dmitriy Pavlov :
> >>> >
> >>> > Hi Igniters,
> >>> >
> >>> > Yesterday was a planned date of code freeze.
> >>> >
> >>> > So the scope (related both to features and to bugs) is final, we're
> >>> > entering to stabilization phase. Nothing can be included into scope
> >>> besides
> >>> > blockers approved by the release manager.
> >>> > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
> >>> > 
> >>> >
> >>> > Unresolved tickets are:
> >>> > IGNITE-12071  Eduard Shangareev
> >>> > IGNITE-12068 Ivan Pavlukhin
> >>> > IGNITE-9562 Eduard Shangareev
> >>> > IGNITE-12057 Anton Kalashnikov
> >>> > IGNITE-12061 Stanilovsky Evgeny
> >>> >
> >>> > Sincerely,
> >>> > Dmitriy Pavlov
> >>> >
> >>> > чт, 15 авг. 2019 г. в 20:12, Zhenya Stanilovsky  >:
> >>> >
> >>> > > Dmitriy, review passed, plz proceed.
> >>> > > thanks !
> >>> > >
> >>> > > > I removed  https://issues.apache.org/jira/browse/IGNITE-12032
> >>> until
> >>> > > > nobody
> >>> > > > volunteer to complete the task.
> >>> > > >
> >>> > > > Evgeniy, please keep me updated about IGNITE-12061.
> >>> > > >
> >>> > > > чт, 15 авг. 2019 г. в 16:56, Zhenya Stanilovsky
> >>> > > >  >>> > > >> :
> >>> > > >
> >>> > > >> yep, i`l try to call someone who probably familiar with this
> >>> problem.
> >>> > > >>
> >>> > > >> >
> >>> > > >> >
> >>> > > >> >Ok, I've removed Spark from the scope.
> >>> > > >> >
> >>> > > >> >What about the unassigned issue related to ODBC? It is not
> >>> looking like
> >>> > > >> >somebody will fix it before release.
> >>> > > >> >
> >>> > > >> >Evgeniy Stanilovsky, what about
> >>> > > >> >https://issues.apache.org/jira/browse/IGNITE-12061
> >>> > > >> ><
> >>> https://issues.apache.org/jira/browse/IGNITE-12061?src=confmacro >
> >>> > > >> >do you have someone to review the fix?
> >>> > > >> >
> >>> > > >> >чт, 15 авг. 2019 г. в 16:05, Denis Magda < dma...@apache.org
> >:
> >>> > > >> >
> >>> > > >> >> Dmitry,
> >>> > > >> >>
> >>> > > >> >> It would be better for us to put off the Spark upgrade until
> >>> 2.8 as
> >>> > > >> Nikolay
> >>> > > >> >> suggested. Let's release 2.7.6 as quickly as possible to let
> >>> roll out
> >>> > > >> fixes
> >>> > > >> >> for the critical issues from the scope.
> >>> > > >> >>
> >>> > > >> >>
> >>> > > >> >> -
> >>> > > >> >> Denis
> >>> > > >> >>
> >>> > > >> >>
> >>> > > >> >> On Thu, Aug 15, 2019 at 3:29 PM Dmitriy Pavlov <
> >>> dpav...@apache.org
> >>> > > >
> >>> > > >> wrote:
> >>> > > >> >>
> >>> > > >> >> > Nikolay, how long does it take to update? I will be
> >>> traveling
> >>> > > from
> >>> > > >> 28
> >>> > > >> Aug
> >>> > > >> >> > till 16 Sept. We can select new dates for release if the
> >>> majority
> >>> > > >> of
> >>> > > >> >> fixes
> >>> > > >> >> > can be done by 16 Sept, but can't be by 20 Aug. Denis,
> >>> please
> >>> share
> >>> > > >> your
> >>> > > >> >> > vision about selecting new dates.
> >>> > > >> >> >
> >>> > > >> >> > *Voting Date: *Sept 18, 2019
> >>> > > >> >> >
> >>> > > >> >> > *Release Date: *Sept 23, 2019
> >>> > > >> >> >
> >>> > > >> >> > Issue  ht

Re: Re[4]: Apache Ignite 2.7.6 (Time, Scope, and Release manager)

[Zhenya Stanilovsky]

hi Dmitriy, Ivan Pavlukhin suggest to exclude IGNITE-12061 from 2.7.6, i  
have no clue - why, but seems i can`t merge it without his visa.

thanks.


Hi Igniters,

I also suggest adding newly created critical bug into scope
https://issues.apache.org/jira/browse/IGNITE-12081 (already assigned  
since

it was discussed before in private communication).

It is not a regression but can cause data corruption, so I'd rather wait
for the fix.

Eduard Shangareev, Stanilovsky Evgeny I'm going to assemble the first RC
during the weekend, so I would be grateful if fixes can be cherry-piked  
to

the branch today. Also, since narrow time limit, please trigger Run All
after each commit in 2.7.6. This will allow to immediately locate which
commit caused test failure.

Sincerely,
Dmitriy Pavlov

пт, 16 авг. 2019 г. в 13:33, Dmitriy Pavlov :


Hi Ivan,

yes, sure.

If it is cherry-picked without conflicts, just push it.

 If it contains conflicts it is better to push to 2.7.6-based branch and
start additional run-all, example
https://github.com/apache/ignite/pull/6781 -it is PR for ignite-9562,
base: 2.7.6

Sincerely,
Dmitriy Pavlov

пт, 16 авг. 2019 г. в 12:28, Павлухин Иван :


Dmitriy,

We accomplished with https://issues.apache.org/jira/browse/IGNITE-12068

Should I cherry-pick it to release branch?

пт, 16 авг. 2019 г. в 11:28, Dmitriy Pavlov :
>
> Hi Igniters,
>
> Yesterday was a planned date of code freeze.
>
> So the scope (related both to features and to bugs) is final, we're
> entering to stabilization phase. Nothing can be included into scope
besides
> blockers approved by the release manager.
> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
> 
>
> Unresolved tickets are:
> IGNITE-12071  Eduard Shangareev
> IGNITE-12068 Ivan Pavlukhin
> IGNITE-9562 Eduard Shangareev
> IGNITE-12057 Anton Kalashnikov
> IGNITE-12061 Stanilovsky Evgeny
>
> Sincerely,
> Dmitriy Pavlov
>
> чт, 15 авг. 2019 г. в 20:12, Zhenya Stanilovsky :
>
> > Dmitriy, review passed, plz proceed.
> > thanks !
> >
> > > I removed  https://issues.apache.org/jira/browse/IGNITE-12032  
until

> > > nobody
> > > volunteer to complete the task.
> > >
> > > Evgeniy, please keep me updated about IGNITE-12061.
> > >
> > > чт, 15 авг. 2019 г. в 16:56, Zhenya Stanilovsky
> > >  > >> :
> > >
> > >> yep, i`l try to call someone who probably familiar with this
problem.
> > >>
> > >> >
> > >> >
> > >> >Ok, I've removed Spark from the scope.
> > >> >
> > >> >What about the unassigned issue related to ODBC? It is not
looking like
> > >> >somebody will fix it before release.
> > >> >
> > >> >Evgeniy Stanilovsky, what about
> > >> >https://issues.apache.org/jira/browse/IGNITE-12061
> > >> ><
https://issues.apache.org/jira/browse/IGNITE-12061?src=confmacro >
> > >> >do you have someone to review the fix?
> > >> >
> > >> >чт, 15 авг. 2019 г. в 16:05, Denis Magda < dma...@apache.org >:
> > >> >
> > >> >> Dmitry,
> > >> >>
> > >> >> It would be better for us to put off the Spark upgrade until
2.8 as
> > >> Nikolay
> > >> >> suggested. Let's release 2.7.6 as quickly as possible to let
roll out
> > >> fixes
> > >> >> for the critical issues from the scope.
> > >> >>
> > >> >>
> > >> >> -
> > >> >> Denis
> > >> >>
> > >> >>
> > >> >> On Thu, Aug 15, 2019 at 3:29 PM Dmitriy Pavlov <
dpav...@apache.org
> > >
> > >> wrote:
> > >> >>
> > >> >> > Nikolay, how long does it take to update? I will be  
traveling

> > from
> > >> 28
> > >> Aug
> > >> >> > till 16 Sept. We can select new dates for release if the
majority
> > >> of
> > >> >> fixes
> > >> >> > can be done by 16 Sept, but can't be by 20 Aug. Denis,  
please

share
> > >> your
> > >> >> > vision about selecting new dates.
> > >> >> >
> > >> >> > *Voting Date: *Sept 18, 2019
> > >> >> >
> > >> >> > *Release Date: *Sept 23, 2019
> > >> >> >
> > >> >> > Issue  https://issues.apache.org/jira/browse/IGNITE-12032
> > >> >> > <
https://issues.apache.org/jira/browse/IGNITE-12032?src=confmacro
> >
> > >> >
> > >> is
> > >> >> > still
> > >> >> > unassigned: Server node prints exception when ODBC driver
> > >> disconnects
> > >> >> > Igniters, who would like to pick up it? By default, I'm  
going

to
> > >> remove
> > >> >> it
> > >> >> > from release
> > >> >> >
> > >> >> >
> > >> >> > чт, 15 авг. 2019 г. в 14:54, Nikolay Izhikov <
nizhi...@apache.org
> >
> > >> >:
> > >> >> >
> > >> >> > > Hello, Igniters.
> > >> >> > >
> > >> >> > > I try to upgrade Spark version but failed.
> > >> >> > >
> > >> >> > > Seems, internal Spark API(External Catalog, SQL planner)
that
> > we
> > >> use
> > >> >> > > changed a lot.
> > >> >> > > So it will take some time to upgrade version.
> > >> >> > >
> > >> >> > > For now, I work hard to complete the second phase of  
IEP-35

so I
> > >> >> postpone
> > >> >> > > upgrade Spark version to Ignite 2.8.
> > >> >> > >
> > >> >> > > В Чт, 15/08/2019 в 14:51 +0300, Dmitriy Pavlov пишет:
> > >> >> > > > Hi Denis,
> > 

Re: Re[4]: Apache Ignite 2.7.6 (Time, Scope, and Release manager)

[Dmitriy Pavlov]

Hi Ivan,

Thank you so much, Ivan, for contributing this fix after hours.

We have second barrier here - 2.7.6 related to 2.7.5,
https://mtcga.gridgain.com/pr.html?serverId=apache&suiteId=IgniteTests24Java8_RunAll&branchForTc=ignite-2.7.6&action=Latest&baseBranchForTc=ignite-2.7.5

I've triggered one more run for RunAll here.

Sincerely,
Dmitriy Pavlov

сб, 17 авг. 2019 г. в 07:36, Павлухин Иван :

> Dmitriy,
>
> I cherry-picked fix for
> https://issues.apache.org/jira/browse/IGNITE-12068 to 2.7.6. Bot visa
> seems good comparing to 2.7.6 but there are some reported blockers. It
> would be great if someone can double-check it. If something is wrong
> you may consider a revert.
>
> пт, 16 авг. 2019 г. в 18:22, Dmitriy Pavlov :
> >
> > Hi Igniters,
> >
> > I also suggest adding newly created critical bug into scope
> > https://issues.apache.org/jira/browse/IGNITE-12081 (already assigned
> since
> > it was discussed before in private communication).
> >
> > It is not a regression but can cause data corruption, so I'd rather wait
> > for the fix.
> >
> > Eduard Shangareev, Stanilovsky Evgeny I'm going to assemble the first RC
> > during the weekend, so I would be grateful if fixes can be cherry-piked
> to
> > the branch today. Also, since narrow time limit, please trigger Run All
> > after each commit in 2.7.6. This will allow to immediately locate which
> > commit caused test failure.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > пт, 16 авг. 2019 г. в 13:33, Dmitriy Pavlov :
> >
> > > Hi Ivan,
> > >
> > > yes, sure.
> > >
> > > If it is cherry-picked without conflicts, just push it.
> > >
> > >  If it contains conflicts it is better to push to 2.7.6-based branch
> and
> > > start additional run-all, example
> > > https://github.com/apache/ignite/pull/6781 -it is PR for ignite-9562,
> > > base: 2.7.6
> > >
> > > Sincerely,
> > > Dmitriy Pavlov
> > >
> > > пт, 16 авг. 2019 г. в 12:28, Павлухин Иван :
> > >
> > >> Dmitriy,
> > >>
> > >> We accomplished with
> https://issues.apache.org/jira/browse/IGNITE-12068
> > >>
> > >> Should I cherry-pick it to release branch?
> > >>
> > >> пт, 16 авг. 2019 г. в 11:28, Dmitriy Pavlov :
> > >> >
> > >> > Hi Igniters,
> > >> >
> > >> > Yesterday was a planned date of code freeze.
> > >> >
> > >> > So the scope (related both to features and to bugs) is final, we're
> > >> > entering to stabilization phase. Nothing can be included into scope
> > >> besides
> > >> > blockers approved by the release manager.
> > >> > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
> > >> >  >
> > >> >
> > >> > Unresolved tickets are:
> > >> > IGNITE-12071  Eduard Shangareev
> > >> > IGNITE-12068 Ivan Pavlukhin
> > >> > IGNITE-9562 Eduard Shangareev
> > >> > IGNITE-12057 Anton Kalashnikov
> > >> > IGNITE-12061 Stanilovsky Evgeny
> > >> >
> > >> > Sincerely,
> > >> > Dmitriy Pavlov
> > >> >
> > >> > чт, 15 авг. 2019 г. в 20:12, Zhenya Stanilovsky  >:
> > >> >
> > >> > > Dmitriy, review passed, plz proceed.
> > >> > > thanks !
> > >> > >
> > >> > > > I removed  https://issues.apache.org/jira/browse/IGNITE-12032
> until
> > >> > > > nobody
> > >> > > > volunteer to complete the task.
> > >> > > >
> > >> > > > Evgeniy, please keep me updated about IGNITE-12061.
> > >> > > >
> > >> > > > чт, 15 авг. 2019 г. в 16:56, Zhenya Stanilovsky
> > >> > > >  > >> > > >> :
> > >> > > >
> > >> > > >> yep, i`l try to call someone who probably familiar with this
> > >> problem.
> > >> > > >>
> > >> > > >> >
> > >> > > >> >
> > >> > > >> >Ok, I've removed Spark from the scope.
> > >> > > >> >
> > >> > > >> >What about the unassigned issue related to ODBC? It is not
> > >> looking like
> > >> > > >> >somebody will fix it before release.
> > >> > > >> >
> > >> > > >> >Evgeniy Stanilovsky, what about
> > >> > > >> >https://issues.apache.org/jira/browse/IGNITE-12061
> > >> > > >> ><
> > >> https://issues.apache.org/jira/browse/IGNITE-12061?src=confmacro >
> > >> > > >> >do you have someone to review the fix?
> > >> > > >> >
> > >> > > >> >чт, 15 авг. 2019 г. в 16:05, Denis Magda < dma...@apache.org
> >:
> > >> > > >> >
> > >> > > >> >> Dmitry,
> > >> > > >> >>
> > >> > > >> >> It would be better for us to put off the Spark upgrade until
> > >> 2.8 as
> > >> > > >> Nikolay
> > >> > > >> >> suggested. Let's release 2.7.6 as quickly as possible to let
> > >> roll out
> > >> > > >> fixes
> > >> > > >> >> for the critical issues from the scope.
> > >> > > >> >>
> > >> > > >> >>
> > >> > > >> >> -
> > >> > > >> >> Denis
> > >> > > >> >>
> > >> > > >> >>
> > >> > > >> >> On Thu, Aug 15, 2019 at 3:29 PM Dmitriy Pavlov <
> > >> dpav...@apache.org
> > >> > > >
> > >> > > >> wrote:
> > >> > > >> >>
> > >> > > >> >> > Nikolay, how long does it take to update? I will be
> traveling
> > >> > > from
> > >> > > >> 28
> > >> > > >> Aug
> > >> > > >> >> > till 16 Sept. We can select new dates for release if the
> > >> majority
> > >> > > >> of
> > >> >