ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vladimir Ozerov <voze...@gridgain.com>
Subject Re: Apache Ignite 2.7. Last Mile
Date Mon, 15 Oct 2018 08:32:46 GMT
Nikolay,

AI 2.7 will include Python thin client. TC suite is crucial part of this
feature, so we should keep the ticket in AI 2.7 scope.

On Mon, Oct 15, 2018 at 10:57 AM Nikolay Izhikov <nizhikov@apache.org>
wrote:

> Hello, Igniters.
>
> There is no progress till Friday.
> We have 14 tickets mapped to 2.7.
>
> В Пт, 12/10/2018 в 08:29 +0300, Nikolay Izhikov пишет:
> > Hello, Igniters.
> >
> > We made some progress yesterday.
> >
> > Please, note, we have 1 new ticket mapped to 2.7 "IGNITE-9852: Create
> TeamCity suite for Python thin client"
> >
> > This ticket doesn't sound like a blocker to me. Let's exclude it from
> release scope.
> > Thoughts?
> >
> > Here is the list of remaining tickets(14) mapped to 2.7.
> >
> > Peter Ivanov     - IGNITE-9852, IGNITE-9685,
> > Alexey Goncharuk   - IGNITE-9784
> > Andrey Kuznetsov   - IGNITE-9737, IGNITE-9710
> > Igor Seliverstov   - IGNITE-9749, IGNITE-9292
> > Dmitry Melnichuk   - IGNITE-7782
> > Ivan Pavlukhin     - IGNITE-5935
> > Yury Babak         - IGNITE-8670
> > Roman Kondakov     - IGNITE-7953
> > Igor Sapego      - IGNITE-9620
> > Alexey Stelmak     - IGNITE-9776
> >
> > Unassigned:
> >
> > IGNITE-9663 - MVCC: Data node failure can cause TX hanging.
> >
> >
> > В Чт, 11/10/2018 в 13:50 +0300, Nikolay Izhikov пишет:
> > > Alexey, we all agreed to merge in 2.7 blockers only.
> > >
> > > Is this a blocker?
> > >
> > > Anyway, you are more experienced Igniter that I am.
> > > If you think we should include this ticket to 2.7 - please, do it.
> > >
> > > В Чт, 11/10/2018 в 13:08 +0300, Alexey Goncharuk пишет:
> > > > Nikolay,
> > > >
> > > > I am waiting for final benchmark results for 9784, after that I will
> merge
> > > > the change.
> > > >
> > > > On the subject of Ignite 2.7 scope, our fellow Igniter Alexey
> Platonov have
> > > > found another case when a failure handler is incorrectly called on
> node
> > > > stop: https://issues.apache.org/jira/browse/IGNITE-9834. The case
> is rare,
> > > > but it is quite an unpleasant UX. Should we include it to 2.7 as
> well?
> > > >
> > > > чт, 11 окт. 2018 г. в 11:22, Nikolay Izhikov <nizhikov@apache.org>:
> > > >
> > > > > Hello, Igniters.
> > > > >
> > > > > We made a good progress yesterday.
> > > > >
> > > > > Here is the list of remaining tickets(17) mapped to 2.7:
> > > > >
> > > > > Alexey Goncharuk   - IGNITE-9784
> > > > > Taras Ledkov       - IGNITE-9171
> > > > > Andrey Kuznetsov   - IGNITE-9737, IGNITE-9710
> > > > > Peter Ivanov       - IGNITE-9583, IGNITE-9823, IGNITE-9685
> > > > > Igor Seliverstov   - IGNITE-9749, IGNITE-9292
> > > > > Dmitry Melnichuk   - IGNITE-7782
> > > > > Ivan Pavlukhin     - IGNITE-5935
> > > > > Yury Babak         - IGNITE-8670
> > > > > Roman Kondakov     - IGNITE-7953, IGNITE-9446
> > > > > Alexey Stelmak     - IGNITE-9776
> > > > >
> > > > > Unassigned:
> > > > >
> > > > > IGNITE-9620 - MVCC: select throwing `Transaction is already
> completed`> >
> > > > > > exception after mvcc missmatch
> > > > >
> > > > > IGNITE-9663 - MVCC: Data node failure can cause TX hanging.
> > > > >
> > > > >
> > > > > В Чт, 11/10/2018 в 10:40 +0300, Vladimir Ozerov пишет:
> > > > > > What kind of help is needed?
> > > > > >
> > > > > > On Wed, Oct 10, 2018 at 11:51 PM Dmitriy Setrakyan <
> > > > >
> > > > > dsetrakyan@apache.org>
> > > > > > wrote:
> > > > > >
> > > > > > > Vladimir Ozerov,
> > > > > > >
> > > > > > > Can you help with the unassigned MVCC tickets?
> > > > > > >
> > > > > > > D.
> > > > > > >
> > > > > > > On Wed, Oct 10, 2018 at 3:32 AM Nikolay Izhikov <
> nizhikov@apache.org>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Hello, Igniters.
> > > > > > > >
> > > > > > > > I list all contributors that assigned to the 2.7 tickets.
> > > > > > > > If you can help them to finish that tickets - please,
do.
> > > > > > > > Assigners, if you need any help - please, respond
to this
> thread.
> > > > > > > >
> > > > > > > > NOTE: We have 6 Unassigned tickets for 2.7. Let's
start work
> on it!
> > > > > > > >
> > > > > > > > Peter Ivanov       - IGNITE-9559, IGNITE-9583, IGNITE-9685,
> > > > >
> > > > > IGNITE-9823
> > > > > > > > Andrey Kuznetsov   - IGNITE-9737, IGNITE-9710
> > > > > > > > Taras Ledkov       - IGNITE-9171
> > > > > > > > Alexey Goncharuk   - IGNITE-9784
> > > > > > > > Dmitriy Govorukhin - IGNITE-9550
> > > > > > > > Igor Seliverstov   - IGNITE-9749
> > > > > > > > Dmitry Melnichuk   - IGNITE-7782
> > > > > > > > Alexey Platonov    - IGNITE-9726
> > > > > > > > Ivan Pavlukhin     - IGNITE-5935
> > > > > > > > Yury Babak         - IGNITE-8670
> > > > > > > > Roman Kondakov     - IGNITE-7953, IGNITE-9446
> > > > > > > > Maxim Pudov        - IGNITE-9126
> > > > > > > > Alexey Stelmak     - IGNITE-9776
> > > > > > > > Alexey Kuznetsov   - IGNITE-7926
> > > > > > > >
> > > > > > > > Unassigned tickets:
> > > > > > > >
> > > > > > > > IGNITE-9781 - JDK11: SSL handshake is failed
> > > > > > > > IGNITE-9620 - MVCC: select throwing `Transaction is
already
> > > > >
> > > > > completed`
> > > > > > > > exception after mvcc missmatch
> > > > > > > > IGNITE-9292 - MVCC SQL: Unexpected state exception
when
> updating
> > > > >
> > > > > backup
> > > > > > > > IGNITE-9663 - MVCC: Data node failure can cause TX
hanging.
> > > > > > > > IGNITE-9724 - MVCC SQL: Test
> > > > > > > >
> > > > >
> > > > >
> CacheMvccSelectForUpdateQueryAbstractTest.testSelectForUpdateDistributed
> > > > > > > > hangs sporadically.
> > > > > > > > IGNITE-9133 - MVCC: Proper empty DHT transactions
handling.
> > > > > > > >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message