ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Anton Vinogradov ...@apache.org>
Subject Re: Apache Ignite 2.8 RELEASE [Time, Scope, Manager]
Date Wed, 22 Jan 2020 09:09:19 GMT
Good Idea, this will also check that the release process is alive.

On Wed, Jan 22, 2020 at 12:04 PM Alexey Goncharuk <
alexey.goncharuk@gmail.com> wrote:

> Folks, Maxim,
>
> Do you mind if I build the current state of ignite-2.8 branch and upload a
> maven staging as rc0 (step 4.3.2 of the release process)? I want run some
> tests for the fixes that are already included to the branch.
>
> вт, 21 янв. 2020 г. в 14:28, Maxim Muzafarov <mmuzaf@apache.org>:
>
> > Folks,
> >
> >
> > I think both of these issues [1] [2] are critical to 2.8 release and
> > we must include them.
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-12547
> > Excessive AtomicLong instantiations lead to GC pressure.
> >
> > [2] https://issues.apache.org/jira/browse/IGNITE-12530
> > Pages list caching can cause IgniteOOME when the checkpoint is
> > triggered by "too many dirty pages" reason.
> >
> >
> > On Mon, 20 Jan 2020 at 19:00, Alex Plehanov <plehanov.alex@gmail.com>
> > wrote:
> > >
> > > Guys,
> > >
> > > There is an issue [1] caused by page list caching [2], which also
> affects
> > > 2.8 release. IgniteOutOfMemoryException can be thrown in some cases
> (data
> > > region is small, a checkpoint is triggered by "too many dirty pages"
> > reason
> > > and pages list cache is rather big).
> > > The fix is ready and merged to master, I suggest to include this fix to
> > 2.8
> > > release. What do you think?
> > >
> > > [1]: https://issues.apache.org/jira/browse/IGNITE-12530
> > > [2]: https://issues.apache.org/jira/browse/IGNITE-6930
> > >
> > > пн, 20 янв. 2020 г. в 12:57, Alexey Goncharuk <
> > alexey.goncharuk@gmail.com>:
> > >
> > > > Maxim,
> > > >
> > > > I took a quick look at IGNITE-12456 and I am not sure it's about data
> > > > corruption. In the attached logs blocked system threads are reported,
> > > > however, there is no enough information to investigate the issue (the
> > full
> > > > thread dump was not attached). I asked the ticket creator to attach
> > missing
> > > > pieces.
> > > >
> > > > Should we consider moving this ticket to a next release?
> > > >
> > > > пн, 20 янв. 2020 г. в 08:54, Zhenya Stanilovsky
> > <arzamas123@mail.ru.invalid
> > > > >:
> > > >
> > > > >
> > > > > Maxim, performance fix issue [1] already in master, if no
> > objections, can
> > > > > u merge it into 2.8 ? Thanks !
> > > > > [1] https://issues.apache.org/jira/browse/IGNITE-12547
> > > > >
> > > > > >Igniters,
> > > > > >
> > > > > >
> > > > > >Here is the actual list of BLOCKER release issues:
> > > > > >
> > > > > >IGNITE-12456 Cluster Data Store grid gets Corrupted for Load
test
> > > > > >*[Unassigned]* OPEN
> > > > > >IGNITE-12489 Error during purges by expiration: Unknown page
type*
> > > > > >[Unassigned]* OPEN
> > > > > >IGNITE-8641 SpringDataExample should use example-ignite.xml config
> > > > > >*[Unassigned]* OPEN
> > > > > >
> > > > > >IGNITE-12398 Apache Ignite Cluster(Amazon S3 Based Discovery)
> Nodes
> > > > > getting
> > > > > >down [Emmanouil Gkatziouras] OPEN
> > > > > >IGNITE-9184 Cluster hangs during concurrent node client and server
> > nodes
> > > > > >restart [Dmitriy Sorokin] IN PROGRESS
> > > > > >IGNITE-12553 [IEP-35] public Java metric API Improvement [Nikolay
> > > > Izhikov]
> > > > > >Blocker IN PROGRESS
> > > > > >
> > > > > >IGNITE-12227 Default auto-adjust baseline enabled flag calculated
> > > > > >incorrectly [Anton Kalashnikov] PATCH AVAILABLE
> > > > > >IGNITE-12470 Pme-free switch feature should be deactivatable
> [Sergei
> > > > > >Ryzhov] PATCH AVAILABLE
> > > > > >IGNITE-12552 [IEP-35] Expose MetricRegistry to the public API
> > > > Improvement
> > > > > >[Nikolay Izhikov] PATCH AVAILABLE
> > > > > >
> > > > > >
> > > > > >[1]  https://issues.apache.org/jira/browse/IGNITE-12456
> > > > > >[2]  https://issues.apache.org/jira/browse/IGNITE-12489
> > > > > >[3]  https://issues.apache.org/jira/browse/IGNITE-8641
> > > > > >[8]  https://issues.apache.org/jira/browse/IGNITE-12398
> > > > > >[3]  https://issues.apache.org/jira/browse/IGNITE-9184
> > > > > >[6]  https://issues.apache.org/jira/browse/IGNITE-12553
> > > > > >[7]  https://issues.apache.org/jira/browse/IGNITE-12227
> > > > > >[9]  https://issues.apache.org/jira/browse/IGNITE-12470
> > > > > >[5]  https://issues.apache.org/jira/browse/IGNITE-12552
> > > > > >
> > > > > >
> > > > > >On Sat, 18 Jan 2020 at 19:11, Sergey Antonov <
> > > > antonovsergey93@gmail.com
> > > > > >
> > > > > >wrote:
> > > > > >
> > > > > >> Maxim,
> > > > > >>
> > > > > >> Conflicts in pr [1] are resolved. TC Run all is started.
> > > > > >>
> > > > > >> [1]  https://github.com/apache/ignite/pull/7238
> > > > > >>
> > > > > >> пт, 17 янв. 2020 г. в 16:04, Sergey Antonov <
> > > > antonovsergey93@gmail.com
> > > > > >:
> > > > > >>
> > > > > >>> Maxim,
> > > > > >>>
> > > > > >>> I will do that on monday (20/01).
> > > > > >>>
> > > > > >>> пт, 17 янв. 2020 г. в 13:08, Maxim Muzafarov
<
> mmuzaf@apache.org
> > >:
> > > > > >>>
> > > > > >>>> Sergey,
> > > > > >>>>
> > > > > >>>>
> > > > > >>>> Can you, please, resolve the PR conflicts [1] [2]?
> > > > > >>>>
> > > > > >>>> [1]  https://github.com/apache/ignite/pull/7238
> > > > > >>>> [2]  https://issues.apache.org/jira/browse/IGNITE-11256
> > > > > >>>>
> > > > > >>>> On Thu, 16 Jan 2020 at 16:59, Ilya Kasnacheev <
> > > > > ilya.kasnacheev@gmail.com >
> > > > > >>>> wrote:
> > > > > >>>> >
> > > > > >>>> > Hello!
> > > > > >>>> >
> > > > > >>>> > I have bumped beanutils and re-ran Cassandra
Store tests.
> Can
> > you
> > > > > >>>> please
> > > > > >>>> > comment on the ticket?
> > > > > >>>> >
> > > > > >>>> > I think that fixing ZooKeeper is too much effort
(there's
> > chaos
> > > > with
> > > > > >>>> > jackson vs. jackson-asl), maybe it should be
split up as a
> > > > separate
> > > > > >>>> ticket
> > > > > >>>> > to be done later.
> > > > > >>>> >
> > > > > >>>> > Regards,
> > > > > >>>> > --
> > > > > >>>> > Ilya Kasnacheev
> > > > > >>>> >
> > > > > >>>> >
> > > > > >>>> > ср, 15 янв. 2020 г. в 18:31, Vladimir
Pligin <
> > > > vova199107@yandex.ru
> > > > > >:
> > > > > >>>> >
> > > > > >>>> > > Thanks, Ilya. It would be really great
to have your patch
> > > > included
> > > > > >>>> into 2.8
> > > > > >>>> > > scope.
> > > > > >>>> > > I'd like to give my two cent as well.
For example we have
> > > > > vulnerable
> > > > > >>>> > > dependencies here:
> > > > > >>>> > > modules/cassandra/store/pom.xml - commons-beanutils
> > > > > >>>> > > modules/zookeeper/pom.xml - transitive
Jackson from
> Curator
> > > > > >>>> > >
> > > > > >>>> > > I'd suggest to uprgrade
> commons-beanutils:commons-beanutils
> > to
> > > > > 1.9.4
> > > > > >>>> and
> > > > > >>>> > > override com.fasterxml.jackson.core:jackson-databind
to
> our
> > > > common
> > > > > >>>> jackson
> > > > > >>>> > > version from other modules.
> > > > > >>>> > >
> > > > > >>>> > >
> > > > > >>>> > >
> > > > > >>>> > > --
> > > > > >>>> > > Sent from:
> > > > > http://apache-ignite-developers.2346864.n4.nabble.com/
> > > > > >>>> > >
> > > > > >>>>
> > > > > >>>
> > > > > >>>
> > > > > >>> --
> > > > > >>> BR, Sergey Antonov
> > > > > >>>
> > > > > >>
> > > > > >>
> > > > > >> --
> > > > > >> BR, Sergey Antonov
> > > > > >>
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> >
>

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