o see the difference and the DB is much smaller. I was
> searching
> >>>> to see if someone has the same issue. This is also killing
> performance.
> >>>>
> >>>> Founds this:
> >>>>
> >>>>
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-47%3A+Native+persistence+defragmentation
> >>>>
> >>>> Apparently, there is no auto-rebalancing of pages? or cleanup of
> pages?
> >>>>
> >>>> Has anyone implemented a workaround to rebuild the cache and indexes
> >>>> say on a weekly basis to get it to behave reasonably?
> >>>>
> >>>> Thanks
> >>>>
> >>>
>
--
Sincerely yours,
Ivan Bessonov
)
> >> >> that have not appeared;
> >> >>
> >> >> 2)After adding a DurableBackgroundCleanupIndexTreeTask node crashes,
> >> after
> >> >> restarting the node, the task will clean the index trees and there
> >> will be
> >> >> errors when using the index;
> >> >>
> >> >> 3)etc.
> >> >>
> >> >> Suggested solution:
> >> >>
> >> >> Rename the root index trees and write about this with a logical
> entry
> >> in
> >> >> the WAL and do this at the first start of
> >> >> DurableBackgroundCleanupIndexTreeTask.
> >> >> Thus, if we find the renamed root pages in task 1, we can clear the
> >> index
> >> >> trees to the end, otherwise the task can be completed.
> >> >> Also, if we find that rename pages are present, and the step 2 has
> not
> >> >> been completed, then we can start rebuilding the indexes.
> >> >>
> >> >> WDYT?
> >> >
> >> > --
> >> >
> >> > Best regards,
> >> > Alexei Scherbakov
> >
> > --
> >
> > Best regards,
> > Alexei Scherbakov
>
--
Sincerely yours,
Ivan Bessonov
> One can argue about performance differences in real-world scenarios,
> but increasing GC pressure just to make the code a little bit nicer is
> unacceptable.
>
> I propose to ban streams usage in the codebase (except for the tests).
>
> Thoughts, objections?
>
> [1] https://gist.github.com/ptupitsyn/5934bbbf8f92ac4937e534af9386da97
>
--
Sincerely yours,
Ivan Bessonov
> >>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>> чт, 28 окт. 2021 г. в 10:39, Nikita Amelchev <
> > >>>>>>>>>>>>>> namelc...@apache.org>:
> > >>>>>>>>>>>>>>>>>>>> Maksim, ok.
> > >>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>> Ivan,
> > >>>>>>>>>>>>>>>>>>>> The minor issues can be considered if they will be
> > >>>>>>>>>> merged
> > >>>>>>>>>>>>>> before
> > >>>>>>>>>>>>>>>> the
> > >>>>>>>>>>>>>>>>>>>> code freeze.
> > >>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>> ср, 27 окт. 2021 г. в 14:55, Pavel Tupitsyn <
> > >>>>>>>>>>>>>> ptupit...@apache.org
> > >>>>>>>>>>>>>>>>> :
> > >>>>>>>>>>>>>>>>>>>>> Ivan, every additional ticket potentially moves the
> > >>>>>>>>>> release
> > >>>>>>>>>>>>>> date
> > >>>>>>>>>>>>>>>>>>> further.
> > >>>>>>>>>>>>>>>>>>>>> Also, AFAIK, Igor is on vacation and can't do a
> > >>>>>>>>>> review this
> > >>>>>>>>>>>>>> week.
> > >>>>>>>>>>>>>>>>>>>>> On Wed, Oct 27, 2021 at 2:32 PM Ivan Daschinsky <
> > >>>>>>>>>>>>>>>> ivanda...@gmail.com>
> > >>>>>>>>>>>>>>>>>>>> wrote:
> > >>>>>>>>>>>>>>>>>>>>>> Pavel, but what is the problem to include a minor
> > >>>>>>>>>>>>>> refactoring?
> > >>>>>>>>>>>>>>>>>>>> Especially
> > >>>>>>>>>>>>>>>>>>>>>> before code freeze?
> > >>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>>> ср, 27 окт. 2021 г. в 14:25, Pavel Tupitsyn <
> > >>>>>>>>>>>>>>>> ptupit...@apache.org>:
> > >>>>>>>>>>>>>>>>>>>>>>> Ivan, IGNITE-15806 seems to be a minor
> > >>>>>>>>>> refactoring, not
> > >>>>>>>>>>>>>> sure
> > >>>>>>>>>>>>>>>> we
> > >>>>>>>>>>>>>>>>>>>> should
> > >>>>>>>>>>>>>>>>>>>>>>> inflate the scope with this.
> > >>>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>>>> On Wed, Oct 27, 2021 at 2:13 PM Ivan Daschinsky
> > >>>>>>>>>> <
> > >>>>>>>>>>>>>>>>>>> ivanda...@gmail.com
> > >>>>>>>>>>>>>>>>>>>>>>> wrote:
> > >>>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>>>>> Nikita, can we add
> > >>>>>>>>>>>>>>>>>>>> https://issues.apache.org/jira/browse/IGNITE-15806
> > >>>>>>>>>>>>>>>>>>>>>>> this
> > >>>>>>>>>>>>>>>>>>>>>>>> ticket for release?
> > >>>>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>>>>> ср, 27 окт. 2021 г. в 13:40, Maksim Timonin <
> > >>>>>>>>>>>>>>>>>>>> timonin.ma...@gmail.com>:
> > >>>>>>>>>>>>>>>>>>>>>>>>> Hi,
> > >>>>>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>>>>>> I'd like to include the ticket in 2.12.
> > >>>>>>>>>> There was a
> > >>>>>>>>>>>>>>>> performance
> > >>>>>>>>>>>>>>>>>>>>>> issue,
> > >>>>>>>>>>>>>>>>>>>>>>> I
> > >>>>>>>>>>>>>>>>>>>>>>>>> spent some time trying to figure it out. I
> > >>>>>>>>>> prepared
> > >>>>>>>>>>>>>> some
> > >>>>>>>>>>>>>>>> fixes
> > >>>>>>>>>>>>>>>>>>>> and I
> > >>>>>>>>>>>>>>>>>>>>>> am
> > >>>>>>>>>>>>>>>>>>>>>>>>> going to submit a patch this week.
> > >>>>>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>>>>>> I think this issue is critical to include
> > >>>>>>>>>> to 2.12
> > >>>>>>>>>>>>>>>> together with
> > >>>>>>>>>>>>>>>>>>>> basic
> > >>>>>>>>>>>>>>>>>>>>>>>>> IndexQuery functionality, because this
> > >>>>>>>>>> ticket
> > >>>>>>>>>>>>>> provides
> > >>>>>>>>>>>>>>>> expected
> > >>>>>>>>>>>>>>>>>>>>>>> behavior
> > >>>>>>>>>>>>>>>>>>>>>>>> of
> > >>>>>>>>>>>>>>>>>>>>>>>>> querying indexes - sorted over all nodes
> > >>>>>>>>>> results.
> > >>>>>>>>>>>>>>>>>>>>>>>>> - IGNITE-15530: IndexQuery has to use
> > >>>>>>>>>> MergeSort
> > >>>>>>>>>>>>>> reducer
> > >>>>>>>>>>>>>>>> [1]
> > >>>>>>>>>>>>>>>>>>>>>>>>> [1]
> > >>>>>>>>>>>>>> https://issues.apache.org/jira/browse/IGNITE-15530
> > >>>>>>>>>>>>>>>>>>>>>>>>> On Wed, Oct 27, 2021 at 1:23 PM Nikita
> > >>>>>>>>>> Amelchev <
> > >>>>>>>>>>>>>>>>>>>>>> namelc...@apache.org>
> > >>>>>>>>>>>>>>>>>>>>>>>>> wrote:
> > >>>>>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>>>>>>> Hello.
> > >>>>>>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>>>>>>> Code freeze is planned for Friday,
> > >>>>>>>>>> October 29.
> > >>>>>>>>>>>>>>>>>>>>>>>>>> There are 40 unresolved issues [1] in the
> > >>>>>>>>>> release
> > >>>>>>>>>>>>>>>> scope. I
> > >>>>>>>>>>>>>>>>>>>> suggest
> > >>>>>>>>>>>>>>>>>>>>>>>>>> bumping up the fix version if they will
> > >>>>>>>>>> not be
> > >>>>>>>>>>>>>>>> resolved till
> > >>>>>>>>>>>>>>>>>>>> the
> > >>>>>>>>>>>>>>>>>>>>>> code
> > >>>>>>>>>>>>>>>>>>>>>>>>>> freeze.
> > >>>>>>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>>>>>>> Please, feel free to write if some of
> > >>>>>>>>>> them are
> > >>>>>>>>>>>>>>>> critical to be
> > >>>>>>>>>>>>>>>>>>>> in
> > >>>>>>>>>>>>>>>>>>>>>> the
> > >>>>>>>>>>>>>>>>>>>>>>>>> 2.12.
> > >>>>>>>>>>>>>>>>>>>>>>>>>> Also, please, pay attention to unresolved
> > >>>>>>>>>>>>>> documentation
> > >>>>>>>>>>>>>>>>>>>> issues. [2]
> > >>>>>>>>>>>>>>>>>>>>>>>>>> Sergey, Petr, thanks for helping with TC.
> > >>>>>>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>>>>>>> [1]
> > >>>>>>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>
> > >>>>
> > >>>
> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.12%27))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20%20and%20status%20not%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20
> > >>>>>>>>>>>>>>>>>>>>>>>>>> [2]
> > >>>>>>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>
> > >>>>
> > >>>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.12%27)%20AND%20status%20NOT%20IN%20(Resolved%2C%20Closed)%20AND%20component%20in%20(documentation)%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20
> > >>>>>>>>>>>>>>>>>>>>>>>>>> вт, 26 окт. 2021 г. в 12:50, Petr Ivanov <
> > >>>>>>>>>>>>>>>>>>> mr.wei...@gmail.com
> > >>>>>>>>>>>>>>>>>>>>> :
> > >>>>>>>>>>>>>>>>>>>>>>>>>>> Thanks, Sergey.
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>> I've also reconfigured nightly builds
> > >>>>>>>>>> for
> > >>>>>>>>>>>>>> ignite-2.12
> > >>>>>>>>>>>>>>>>>>> branch.
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>> On 22 Oct 2021, at 17:32, Сергей
> > >>>>>>>>>> Утцель <
> > >>>>>>>>>>>>>>>>>>> utt...@gmail.com>
> > >>>>>>>>>>>>>>>>>>>>>>> wrote:
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>> I configured TC bot to 'ignite-2.12'
> > >>>>>>>>>> instead
> > >>>>>>>>>>>>> of
> > >>>>>>>>>>>>>>>>>>>> 'ignite-2.11'
> > >>>>>>>>>>>>>>>>>>>>>>>>>> --
> > >>>>>>>>>>>>>>>>>>>>>>>>>> Best wishes,
> > >>>>>>>>>>>>>>>>>>>>>>>>>> Amelchev Nikita
> > >>>>>>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>>>>> --
> > >>>>>>>>>>>>>>>>>>>>>>>> Sincerely yours, Ivan Daschinskiy
> > >>>>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>>> --
> > >>>>>>>>>>>>>>>>>>>>>> Sincerely yours, Ivan Daschinskiy
> > >>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>> --
> > >>>>>>>>>>>>>>>>>>>> Best wishes,
> > >>>>>>>>>>>>>>>>>>>> Amelchev Nikita
> > >>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> --
> > >>>>>>>>>>>>>>>> Best wishes,
> > >>>>>>>>>>>>>>>> Amelchev Nikita
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>> --
> > >>>>>>>>>>>>>>> Sincerely yours, Ivan Daschinskiy
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>> --
> > >>>>>>>>>>>>>> Best wishes,
> > >>>>>>>>>>>>>> Amelchev Nikita
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>> --
> > >>>>>>>>>>>>> Sincerely yours, Ivan Daschinskiy
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>> --
> > >>>>>>>>>>> Best wishes,
> > >>>>>>>>>>> Amelchev Nikita
> > >>>>>>
> > >>>>>>
> > >>>>>> --
> > >>>>>> Best wishes,
> > >>>>>> Amelchev Nikita
> > >>>>
> > >>>
> > >>
> > >>
> > >> --
> > >> Sincerely yours, Ivan Daschinskiy
> > >
> > >
> > >
> > > --
> > > Best wishes,
> > > Amelchev Nikita
> >
>
>
> --
> Best wishes,
> Amelchev Nikita
>
--
Sincerely yours,
Ivan Bessonov
t; > > > >
> > > > > > > > > - Why no nested exceptions? Sometimes an error
> handler
> > is
> > > > > > > > interested
> > > > > > > > > only in high level exceptions (like Invalid
> > > Configuration)
> > > > > and
> > > > > > > > > sometimes
> > > > > > > > > details are needed (like specific configuration
> parser
> > > > > > > exceptions).
> > > > > > > > >
> > > > > > > >
> > > > > > > > Nested exceptions are not forbidden to use. They can provide
> > > > > additional
> > > > > > > > details on the error for debug purposes, but not strictly
> > > required,
> > > > > > > because
> > > > > > > > error code + message should provide enough information to the
> > > user.
> > > > > > > >
> > > > > > > >
> > > > > > > > >- For async methods returning a Future we may have a
> > > universal
> > > > > > rule
> > > > > > > on
> > > > > > > > >how to handle exceptions. For example, we may specify
> that
> > > any
> > > > > > async
> > > > > > > > > method
> > > > > > > > >can throw only invalid argument exceptions. All other
> > errors
> > > > are
> > > > > > > > > reported
> > > > > > > > >via the exceptionally(IgniteException -> {}) callback
> even
> > > if
> > > > > the
> > > > > > > > async
> > > > > > > > >method was executed synchronously.
> > > > > > > > >
> > > > > > > >
> > > > > > > > This is ok to me.
> > > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > вт, 13 апр. 2021 г. в 12:08, Alexei Scherbakov <
> > > > > > > > > alexey.scherbak...@gmail.com
> > > > > > > > > >:
> > > > > > > > >
> > > > > > > > > > Igniters,
> > > > > > > > > >
> > > > > > > > > > I would like to start the discussion about error handling
> > in
> > > > > > Ignite 3
> > > > > > > > and
> > > > > > > > > > how we can improve it compared to Ignite 2.
> > > > > > > > > >
> > > > > > > > > > The error handling in Ignite 2 was not very good because
> of
> > > > > generic
> > > > > > > > > > CacheException thrown on almost any occasion, having
> deeply
> > > > > nested
> > > > > > > root
> > > > > > > > > > cause and often containing no useful information on
> further
> > > > steps
> > > > > > to
> > > > > > > > fix
> > > > > > > > > > the issue.
> > > > > > > > > >
> > > > > > > > > > I aim to fix it by introducing some rules on error
> > handling.
> > > > > > > > > >
> > > > > > > > > > *Public exception structure.*
> > > > > > > > > >
> > > > > > > > > > A public exception must have an error code, a cause, and
> an
> > > > > action.
> > > > > > > > > >
> > > > > > > > > > * The code - the combination of 2 byte scope id and 2
> byte
> > > > error
> > > > > > > number
> > > > > > > > > > within the module. This allows up to 2^16 errors for each
> > > > scope,
> > > > > > > which
> > > > > > > > > > should be enough. The error code string representation
> can
> > > look
> > > > > > like
> > > > > > > > > > RFT-0001 or TBL-0001
> > > > > > > > > > * The cause - short string description of an issue,
> > readable
> > > by
> > > > > > user.
> > > > > > > > > This
> > > > > > > > > > can have dynamic parameters depending on the error type
> for
> > > > > better
> > > > > > > user
> > > > > > > > > > experience, like "Can't write a snapshot, no space left
> on
> > > > device
> > > > > > > {0}"
> > > > > > > > > > * The action - steps for a user to resolve error
> situation
> > > > > > described
> > > > > > > in
> > > > > > > > > the
> > > > > > > > > > documentation in the corresponding error section, for
> > example
> > > > > > "Clean
> > > > > > > up
> > > > > > > > > > disk space and retry the operation".
> > > > > > > > > >
> > > > > > > > > > Common errors should have their own scope, for example
> > > IGN-0001
> > > > > > > > > >
> > > > > > > > > > All public methods throw only unchecked
> > > > > > > > > > org.apache.ignite.lang.IgniteException containing
> > > > aforementioned
> > > > > > > > fields.
> > > > > > > > > > Each public method must have a section in the javadoc
> with
> > a
> > > > list
> > > > > > of
> > > > > > > > all
> > > > > > > > > > possible error codes for this method.
> > > > > > > > > >
> > > > > > > > > > A good example with similar structure can be found here
> [1]
> > > > > > > > > >
> > > > > > > > > > *Async timeouts.*
> > > > > > > > > >
> > > > > > > > > > Because almost all API methods in Ignite 3 are async,
> they
> > > all
> > > > > will
> > > > > > > > have
> > > > > > > > > a
> > > > > > > > > > configurable default timeout and can complete with
> timeout
> > > > error
> > > > > > if a
> > > > > > > > > > computation is not finished in time, for example if a
> > > response
> > > > > has
> > > > > > > not
> > > > > > > > > been
> > > > > > > > > > yet received.
> > > > > > > > > > I suggest to complete the async op future with
> > > TimeoutException
> > > > > in
> > > > > > > this
> > > > > > > > > > case to make it on par with synchronous execution using
> > > > > future.get,
> > > > > > > > which
> > > > > > > > > > will throw java.util.concurrent.TimeoutException on
> > timeout.
> > > > > > > > > > For reference, see
> > > > > java.util.concurrent.CompletableFuture#orTimeout
> > > > > > > > > > No special error code should be used for this scenario.
> > > > > > > > > >
> > > > > > > > > > *Internal exceptions hierarchy.*
> > > > > > > > > >
> > > > > > > > > > All internal exceptions should extend
> > > > > > > > > > org.apache.ignite.internal.lang.IgniteInternalException
> for
> > > > > checked
> > > > > > > > > > exceptions and
> > > > > > > > > >
> > > org.apache.ignite.internal.lang.IgniteInternalCheckedException
> > > > > for
> > > > > > > > > > unchecked exceptions.
> > > > > > > > > >
> > > > > > > > > > Thoughts ?
> > > > > > > > > >
> > > > > > > > > > [1]
> > > > > > >
> > https://docs.oracle.com/cd/B10501_01/server.920/a96525/preface.htm
> > > > > > > > > >
> > > > > > > > > > --
> > > > > > > > > >
> > > > > > > > > > Best regards,
> > > > > > > > > > Alexei Scherbakov
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > Best regards,
> > > > > > > > > Alexey
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > >
> > > > > > > > Best regards,
> > > > > > > > Alexei Scherbakov
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Vladislav Pyatkov
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > >
> > > > > Best regards,
> > > > > Alexei Scherbakov
> > > > >
> > > >
> > > >
> > > > --
> > > > Best regards,
> > > > Andrey V. Mashenkov
> > > >
> > >
> > >
> > > --
> > >
> > > Best regards,
> > > Alexei Scherbakov
> > >
> >
>
>
> --
>
> Best regards,
> Alexei Scherbakov
>
--
Sincerely yours,
Ivan Bessonov
inspired by some existing implementation?
> > What should I study beside source code to better understand Ignite b+
> tree
> > and how it can be improved?
> >
> >
>
--
Sincerely yours,
Ivan Bessonov
t; Release 2.14 has been delayed due to performance issues (compare with
> 2.13) for IgniteSqlQueryBenchmark in in-memory mode. We're looking.
>
> Any suggestions and support are welcome.
>
--
Sincerely yours,
Ivan Bessonov
the release candidate
> is verified and ready to be voted on. What do you think about the 2.14.1
> release, or can the fix wait until 2.15?
> I'm going to start VOTE just now.
>
> [1]. https://issues.apache.org/jira/browse/IGNITE-17764
>
--
Sincerely yours,
Ivan Bessonov
gt; > doesn't like that.
> >
> > I've created a PR [2] with a demonstration how this library can be used
> in
> > the existing code base.
> >
> > [1] https://github.com/google/auto/tree/main/service
> > [2] https://github.com/apache/ignite-3/pull/1415
> >
> > --
> > With regards,
> > Aleksandr Polovtsev
> >
>
--
Sincerely yours,
Ivan Bessonov
; [1]
> > > > > >
> > > >
> > >
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8#ApacheIgnite2.8-Benchmarks
> > > > > >
> > > > > > do we need some bisect or other work here ?
> > > > > >
> > > > > > >
> > > > > > >
> > > > > > >--- Forwarded message ---
> > > > > > >From: "Maxim Muzafarov" < mmu...@apache.org >
> > > > > > >To: dev@ignite.apache.org
> > > > > > >Cc:
> > > > > > >Subject: Apache Ignite 2.8 RELEASE [Time, Scope, Manager]
> > > > > > >Date: Fri, 20 Sep 2019 14:44:31 +0300
> > > > > > >
> > > > > > >Igniters,
> > > > > > >
> > > > > > >
> > > > > > >It's almost a year has passed since the last major Apache
> Ignite 2.7
> > > > > > >has been released. We've accumulated a lot of performance
> > > improvements
> > > > > > >and a lot of new features which are waiting for their release
> date.
> > > > > > >Here is my list of the most interesting things from my point
> since
> > > the
> > > > > > >last major release:
> > > > > > >
> > > > > > >Service Grid,
> > > > > > >Monitoring,
> > > > > > >Recovery Read
> > > > > > >BLT auto-adjust,
> > > > > > >PDS compression,
> > > > > > >WAL page compression,
> > > > > > >Thin client: best effort affinity,
> > > > > > >Thin client: transactions support (not yet)
> > > > > > >SQL query history
> > > > > > >SQL statistics
> > > > > > >
> > > > > > >I think we should no longer wait and freeze the master branch
> > > anymore
> > > > > > >and prepare the next major release by the end of the year.
> > > > > > >
> > > > > > >
> > > > > > >I propose to discuss Time, Scope of Apache Ignite 2.8 release
> and
> > > also
> > > > > > >I want to propose myself to be the release manager of the
> planning
> > > > > > >release.
> > > > > > >
> > > > > > >Scope Freeze: November 4, 2019
> > > > > > >Code Freeze: November 18, 2019
> > > > > > >Voting Date: December 10, 2019
> > > > > > >Release Date: December 17, 2019
> > > > > > >
> > > > > > >
> > > > > > >WDYT?
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > >
> > >
>
--
Sincerely yours,
Ivan Bessonov
> > > > > > > >> [1] https://github.com/apache/ignite/pull/7238
> > > > > > > > > >>
> > > > > > > > > >> пт, 17 янв. 2020 г. в 16:04, Sergey Antonov <
> > > > > > > > antonovserge...@gmail.com
> > > > > > > > > >:
> > > > > > > > > >>
> > > > > > > > > >>> Maxim,
> > > > > > > > > >>>
> > > > > > > > > >>> I will do that on monday (20/01).
> > > > > > > > > >>>
> > > > > > > > > >>> пт, 17 янв. 2020 г. в 13:08, Maxim Muzafarov <
> > > > > mmu...@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.kasnach...@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 <
> > > > > > > > vova199...@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
> > > > > > > > > >>
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > >
> > > > >
> > >
> >
>
--
Sincerely yours,
Ivan Bessonov
ls).
> > > > I'll try to reproduce in another test environment.
> > > >
> > > >
> > > > Will keep you posted.
> > > >
> > > >
> > > > [1] https://issues.apache.org/jira/browse/IGNITE-12593
> > > > [2] https://issues.apache.org/jira/browse/IGNITE-12594
> > > > [3] https://issues.apache.org/jira/browse/IGNITE-12398
> > > > [4] https://issues.apache.org/jira/browse/IGNITE-12489
> > > > [5]
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8#ApacheIgnite2.8-Benchmarks(LATEST)
> > > >
> > > > On Thu, 30 Jan 2020 at 15:02, Alexey Goncharuk
> > > > wrote:
> > > > >
> > > > > Sounds good, will do!
> >
> >
> >
> > --
> > Best regards,
> > Ivan Pavlukhin
>
--
Sincerely yours,
Ivan Bessonov
jira/browse/IGNITE-12726
--
Sincerely yours,
Ivan Bessonov
full read to unlock the GridH2Table. (#7551)
> - bcaae8deef IGNITE-12734 Fixed scan query over evicted partition - Fixes
> #7494.
> - 683f22e64f IGNITE-12756 TcpCommunication SPI metrics improvement
>
> Denis Garus,
> Taras Ledkov,
> Alexey Plekhanov,
> Ivan Bessonov,
Exception from gauge which invoke communication
> >> IGNITE-12568 - MessageFactory implementations refactoring
> >>
> >> Ivan,
> >> Personally, I’m against any refactoring improvements in bug fix release.
> >> So, I propose to exclude IGNITE-12756 from 2.
Tests24Java8=__all_branches__&itemsCount=50
> >
> > [2]
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&buildTypeId=&tab=testDetails&testNameId=-3485591522651012009&order=TEST_STATUS_DESC&branch_IgniteTests24Java8=__all_branches__&itemsCou
lay/IGNITE/Apache+Ignite+Roadmap
--
Sincerely yours,
Ivan Bessonov
nections like
client-to-client or server-to-server
will be implemented in separate tickets.
[1] https://issues.apache.org/jira/browse/IGNITE-12438
[2] https://issues.apache.org/jira/browse/IGNITE-13013
--
Sincerely yours,
Ivan Bessonov
/display/IGNITE/IEP-47%3A+Native+persistence+defragmentation
[2]
http://apache-ignite-developers.2346864.n4.nabble.com/How-to-free-up-space-on-disc-after-removing-entries-from-IgniteCache-with-enabled-PDS-td39839.html
--
Sincerely yours,
Ivan Bessonov
7;t have a mechanism (like watcher) to perform a "safe restart"
> (by
> > safe I mean Ignite restart without OS-level process restart) we cannot
> > finish maintenance mode without another manual restart but I think it is
> a
> > reasonable restriction as maintenance m
ed by Alex Plekhanov sounds reasonable to me. I'd
> like
> > only to hear inputs of @Ivan Rakov , who is about
> to
> > finish with the tracing support, and @Ivan Bessonov
> > , who is fixing a serious limitation for K8
> > deployments [1]. Most likely, both features
ery
> > > > > connection is used for communication in a single direction only.
> Why
> > > does
> > > > > it matter which node initiates the connection? Why can't one of the
> > > nodes
> > > > > (e.g., a client) initiate both co
t work on K8s, which
> does
> not agree with our experience of it working. I'd also like to understand
> better the bounds of the issue with CQ: When does it not work and what are
> the symptoms we would see if there was an issue with the way we are using
> it, or the K8s infrastructure we deploy to?
>
> Thanks,
> Raymond.
>
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>
--
Sincerely yours,
Ivan Bessonov
ages in both directions. Could
> you please provide an example case in which servers have to initiate
> new connections to clients?
>
> 2020-06-29 13:08 GMT+03:00, Ivan Bessonov :
> > Hi igniters, Hi Raymond,
> >
> > that was a really good point. I will try to addres
gt; client cannot be used anymore then the server can expect that the
> client will establish a new one. Is it just out of current iteration
> scope? Or are there still other fundamental problems?
>
> 2020-06-29 16:32 GMT+03:00, Ivan Bessonov :
> > Hi Ivan,
> >
> > s
nite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_CheckCodeStyle&tab=buildTypeStatusDiv&branch_IgniteTests24Java8=%3Cdefault%3E
[2] https://issues.apache.org/jira/browse/IGNITE-13142
--
Sincerely yours,
Ivan Bessonov
Ignite 2.9 this issue:
> >>> https://issues.apache.org/jira/browse/IGNITE-13246 ?
> >>>
> >>> This issue is about BASELINE events and it is very useful for
> notification
> >>> external tools about changes in baseline.
> >>>
> >>> Thank you!
> >>>
> >>> ---
> >>> Alexey Kuznetsov
> >>>
> >>
>
>
>
>
--
Sincerely yours,
Ivan Bessonov
3.0.
> >
> > Also, I would try to deliver the following two changes in Ignite 2.9:
> >
> >- Communication SPI changes [1] and serverless functions support.
> @Ivan
> >Bessonov , the first is completed but no
> >merged. The second should be already solved t
ist&branch_IgniteTests24Java8=%3Cdefault%3E&state=failed
[3] https://issues.apache.org/jira/browse/IGNITE-13266
[4] https://issues.apache.org/jira/browse/IGNITE-13263
[5]
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_PdsIndexing&tab=buildTypeHistoryList&branch_IgniteTests24Java8=pull%2F8051%2Fhead
--
Sincerely yours,
Ivan Bessonov
nvoke mmap/munmap with it and it works
> fine.
> May be we can create module (similar to direct-io) that use mmap/munap on
> platforms, that support them
> and fallback to Unsafe if not?
>
> чт, 23 июл. 2020 г. в 13:31, Ivan Bessonov :
>
> > Hello Igniters,
> >
>
com/testing-memory-allocators-ptmalloc2-tcmalloc-hoard-jemalloc-while-trying-to-simulate-real-world-loads/
>
>
>
> чт, 23 июл. 2020 г. в 14:19, Ivan Bessonov :
>
> > Hello Ivan,
> >
> > It feels like the problem is more about new starting threads rather than
>
to the solution that I already tested or should we update
> TC
> >> agents? :)
> >
> >
> > Yes, if you want to use jemalloc, you should install it and configure a
> > specific env variable.
> > This is just an option to consider, nothing more. I suppose that your
ple just delete one of the IgniteLinkTaglet files,
> this works for me too but is quite inconvenient.
> Is there any trick to this?
>
--
Sincerely yours,
Ivan Bessonov
Two modules in a project cannot share the same content root.`
>
> Clearly I'm doing something wrong - maybe I'm importing the project into
> Idea in a wrong way?
> Or should I use a different JDK? Which version is best for Ignite
> development right now?
> (I'm using OpenJDK
hank you!
[0]
https://cwiki.apache.org/confluence/display/IGNITE/IEP-47%3A+Native+persistence+defragmentation
[1] https://issues.apache.org/jira/browse/IGNITE-13190
[2] https://github.com/apache/ignite/pull/7984/files
[3] https://issues.apache.org/jira/browse/IGNITE-13697
--
Sincerely yours,
Ivan Bessonov
gt; Denis
>
>
> On Thu, Nov 12, 2020 at 7:11 AM Ivan Bessonov
> wrote:
>
> > Hi Igniters,
> >
> > Core functionality of defragmentation is finally implemented in [1].
> > There's no public API in it
> > for now, patch is already very big and had to
But maybe I just don't know the date. To be short - right now
defragmentation is my first priority.
вт, 17 нояб. 2020 г. в 15:18, Ivan Bessonov :
> Denis,
>
> chances that feature will be fully complete is a bit low. We still make
> adjustments to the API
> and we need a
elp us here, but maybe we will be ok with just
> more
> >>>> strict java access modifiers usage :) The idea here is that a module
> should
> >>>> never touch a dependent module's private classes, ever. The exported
> >>>> classes and interfaces are still free to be modified between
> releases, as
> >>>> long as it is not a user public API.
> >>>> - A module should be logically complete, thus it may be beneficial if
> >>>> module name matches with the code package it provides (e.g.
> configuration
> >>>> -> org.apache.ignite.configuration, replication ->
> >>>> org.apache.ignite.replication, raft->org.apache.ignite.raft, etc)
> >>>>
> >>>> Any other principles/rules we can apply to make the code structure
> more
> >>>> concise? Thoughts?
> >>>>
> >>>> --AG
> >>>>
> >>>> [1] https://issues.apache.org/jira/browse/IGNITE-12552
> >>>> [2] https://issues.apache.org/jira/browse/IGNITE-13513
> >>>> [3] https://issues.apache.org/jira/browse/IGNITE-13220
> >>
> >>
> >>
> >>
--
Sincerely yours,
Ivan Bessonov
s) and GraalVM.
> Such a
> >>>> > > situation could be described as bad user experience and we
> should fix
> >>>> > > it. Var handles [2] could be used for solving described
> problems.
> >>>> > >
> >>>> > > * Java 9+ introduces Flight Recorder API [3] which could be
> used in
> >>>> > > the Ignite project for lightweight profiling of internal
> processes.
> >>>> > >
> >>>> > > Please, share your opinions, objections and ideas about this
> topic. I
> >>>> > > hope we will not have serious disagreements and the consensus
> will be
> >>>> > > reached quickly.
> >>>> > >
> >>>> > >
> >>>> > > 1.
> >>>> > >
> >>>> >
> >>>>
> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Ignite-3-0-development-approach-tp49922p50295.html
> >>>> > > 2.
> >>>> > >
> >>>> >
> >>>>
> https://docs.oracle.com/javase/9/docs/api/java/lang/invoke/VarHandle.html
> >>>> > > 3.
> >>>> > >
> >>>> >
> >>>>
> https://docs.oracle.com/en/java/javase/11/docs/api/jdk.jfr/jdk/jfr/FlightRecorder.html
> >>>> > >
> >>>> >
>
--
Sincerely yours,
Ivan Bessonov
in addition to MD5/SHA1?
>
> Can anyone shed some light on this?
>
> [1] https://infra.apache.org/release-signing.html#basic-facts
> [2]
>
> https://repository.apache.org/content/repositories/orgapacheignite-1490/org/apache/ignite/ignite-core/2.9.1/
> [3] https://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html
>
> -Val
>
--
Sincerely yours,
Ivan Bessonov
> romanova.ks@gmail.com>:
> >> > Ivan, my congratulations!
> >> >
> >> > вт, 12 янв. 2021 г. в 13:32, Andrey Gura :
> >> >
> >> >> Igniters,
> >> >>
> >> >> The Apache Ignite Project Ma
d for String.getBytes(). It is a
> > common
> > > convention to set ut to UTF-8, for example, IDEA will do that.
> > >
> > > WDYT?
> > >
> > > There's a pull request: https://github.com/apache/ignite/pull/5725
> > > If somebody could contribute C++ and .Net tests I would be also
> grateful.
> > >
> > > Regards,
> > > --
> > > Ilya Kasnacheev
> > >
> >
>
--
Sincerely yours,
Ivan Bessonov
acheev
>
>
> чт, 10 янв. 2019 г. в 17:11, Ivan Bessonov :
>
> > Hello!
> >
> > I have a concern about MetaStorage - it uses default system encoding to
> > serialize keys. This means that after this change Windows nodes won't be
> > able to read previous M
x27;m working on them right now.
See package "org.apache.ignite.internal.processors.metastorage" for the new
interfaces and comment your opinion or questions. Thank you!
[1] https://issues.apache.org/jira/browse/IGNITE-10640
[2]
https://cwiki.apache.org/confluence/display/IGNITE/IEP-4+Baseline+topology+for+caches
[3] https://issues.apache.org/jira/browse/IGNITE-8717
--
Sincerely yours,
Ivan Bessonov
ribution is changed (node join/leave, baseline changes, late
> affinity assignment)
> long sqlSchemaVer; // Incremented every time SQL schema changes
> }
>
> Vladimir.
>
>
> On Fri, Jan 25, 2019 at 11:45 AM Ivan Bessonov
> wrote:
>
> > Hello, Igniters!
> >
n of annotation processing and a few migrated tests. If you
like
the idea then I will migrate all the other tests on the same mechanism.
What do you think?
[1] https://issues.apache.org/jira/browse/IGNITE-11323
[2] https://github.com/apache/ignite/pull/6109
--
Sincerely yours,
Ivan Bessonov
Count on my support if you will need any assistance with applying this
> > patch.
> >
> > чт, 14 февр. 2019 г. в 18:53, Ivan Bessonov :
> >
> > > Hello Igniters,
> > >
> > > I'd like to discuss the way we treat system proper
> >
> > Best Regards,
> > Apache Ignite TeamCity Bot
> > https://github.com/apache/ignite-teamcity-bot
> > Notification generated at 03:57:01 04-07-2019
>
>
>
> --
> Best regards,
> Ivan Pavlukhin
>
--
Sincerely yours,
Ivan Bessonov
orker
> got a message from the queue?
>
> On Fri, Dec 14, 2018 at 6:53 PM Dmitriy Pavlov wrote:
>
> > Looks cool, I will try
> >
> > пт, 14 дек. 2018 г. в 16:46, Павлухин Иван :
> >
> > > Hi Igniters,
> > >
> > > I would lik
I'm new to Ignite and I would like to join Apache Ignite development.
My JIRA's login is ibessonov
Hello Igniters!
I prepared an IEP for Ignite 3 disaster recovery basic features and API,
please take a look.
[1]
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=315493878
--
Sincerely yours,
Ivan Bessonov
described in IEP is
quite
tricky from the implementation point of view.
сб, 10 авг. 2024 г. в 14:37, jh w :
> 请问提交多少代码有希望成为apache commit呢？
>
> jh w 于2024年8月10日周六 19:34写道：
>
> > You mean I can develop this requirement?
> >
> >
> > Ivan Bessonov 于2024年8月8日周四 16:2
it @Nullable on collection types.
> >
> > It is also proposed to add new checks for existing rules. This is
> included
> > mostly for illustration purposes—the proposed process does not require a
> > dev list discussion for enforcing an existing rule with a static check.
> >
> > - **New check, existing rule:** var usage
> > Enforce the var keyword usage as described in the code style.
> >
> > - **New check, existing rule:** Async methods
> > Enforce the *Async suffix in methods returning CompletableFuture as
> > described in the code style.
> >
> > I will be creating tickets for the new checks above shortly.
> >
> > Thanks,
> > Stan
> >
>
--
Sincerely yours,
Ivan Bessonov
Ivan Bessonov created IGNITE-14145:
--
Summary: ConfigurationUtil should be moved to internal package,
visitor should be refactored.
Key: IGNITE-14145
URL: https://issues.apache.org/jira/browse/IGNITE-14145
Ivan Bessonov created IGNITE-14193:
--
Summary: Initialize configuration tree with default values on
first start
Key: IGNITE-14193
URL: https://issues.apache.org/jira/browse/IGNITE-14193
Project
Ivan Bessonov created IGNITE-14194:
--
Summary: Multiple storages support for configuration
Key: IGNITE-14194
URL: https://issues.apache.org/jira/browse/IGNITE-14194
Project: Ignite
Issue
Ivan Bessonov created IGNITE-14230:
--
Summary: Port DynamicConfiguration to new underlying configuration
framework.
Key: IGNITE-14230
URL: https://issues.apache.org/jira/browse/IGNITE-14230
Project
Ivan Bessonov created IGNITE-14279:
--
Summary: Introduce "sendWithResponse" into network API
Key: IGNITE-14279
URL: https://issues.apache.org/jira/browse/IGNITE-14279
Project: Ignite
Ivan Bessonov created IGNITE-14302:
--
Summary: Generated configuration classes break PMD suite in REST
module
Key: IGNITE-14302
URL: https://issues.apache.org/jira/browse/IGNITE-14302
Project: Ignite
Ivan Bessonov created IGNITE-14371:
--
Summary: Fix REST json representation for configuration
Key: IGNITE-14371
URL: https://issues.apache.org/jira/browse/IGNITE-14371
Project: Ignite
Issue
Ivan Bessonov created IGNITE-14372:
--
Summary: Fix REST json configuration update requests
Key: IGNITE-14372
URL: https://issues.apache.org/jira/browse/IGNITE-14372
Project: Ignite
Issue
Ivan Bessonov created IGNITE-14442:
--
Summary: IgniteRunner fails with NPE after REST module was broken
by incompatible changes.
Key: IGNITE-14442
URL: https://issues.apache.org/jira/browse/IGNITE-14442
Ivan Bessonov created IGNITE-14447:
--
Summary: Invalid meta page can be used after index re-creation
Key: IGNITE-14447
URL: https://issues.apache.org/jira/browse/IGNITE-14447
Project: Ignite
Ivan Bessonov created IGNITE-12485:
--
Summary: DiscoveryEvent make event message lazy initialization
Key: IGNITE-12485
URL: https://issues.apache.org/jira/browse/IGNITE-12485
Project: Ignite
Ivan Bessonov created IGNITE-12486:
--
Summary: Truncation of archived WAL segments doesn't work
Key: IGNITE-12486
URL: https://issues.apache.org/jira/browse/IGNITE-12486
Project: I
Ivan Bessonov created IGNITE-12487:
--
Summary: Inconsistent GridIoManager API for
sendToGridTopic(Collection nodes) and sendToGridTopic(UUID nodeId)
Key: IGNITE-12487
URL: https://issues.apache.org/jira/browse
Ivan Bessonov created IGNITE-12488:
--
Summary: Fix JavaDocs in DistributedMetaStorage
Key: IGNITE-12488
URL: https://issues.apache.org/jira/browse/IGNITE-12488
Project: Ignite
Issue Type
Ivan Bessonov created IGNITE-12491:
--
Summary: Eliminate contention on ConcurrentHashMap.size()
Key: IGNITE-12491
URL: https://issues.apache.org/jira/browse/IGNITE-12491
Project: Ignite
Ivan Bessonov created IGNITE-12499:
--
Summary: Node took a long time to start after kill
Key: IGNITE-12499
URL: https://issues.apache.org/jira/browse/IGNITE-12499
Project: Ignite
Issue Type
Ivan Bessonov created IGNITE-12506:
--
Summary: Deadlock in
DistributedMetaStoragePersistentTest.testUnstableTopology
Key: IGNITE-12506
URL: https://issues.apache.org/jira/browse/IGNITE-12506
Project
Ivan Bessonov created IGNITE-12514:
--
Summary: WAL don't flush several last records in LOG-ONLY/FSYNC
mode if flush ptr=null
Key: IGNITE-12514
URL: https://issues.apache.org/jira/browse/IGNITE-
Ivan Bessonov created IGNITE-12515:
--
Summary: GridMultinodeRedeploySharedModeSelfTest.testSharedMode
fails sometimes
Key: IGNITE-12515
URL: https://issues.apache.org/jira/browse/IGNITE-12515
Project
Ivan Bessonov created IGNITE-12542:
--
Summary: Some tests failed after due to incompatible changes in
IGNITE-12108 and IGNITE-11987
Key: IGNITE-12542
URL: https://issues.apache.org/jira/browse/IGNITE-12542
Ivan Bessonov created IGNITE-12576:
--
Summary: [IEP-35] TCP communication metrics use node ID instead of
consistent ID
Key: IGNITE-12576
URL: https://issues.apache.org/jira/browse/IGNITE-12576
Ivan Bessonov created IGNITE-12638:
--
Summary: Classes persisted by DistributedMetaStorage are not
IgniteDTO
Key: IGNITE-12638
URL: https://issues.apache.org/jira/browse/IGNITE-12638
Project: Ignite
Ivan Bessonov created IGNITE-12726:
--
Summary: Cache names can't be used as part of
DistributedMetaStorage keys
Key: IGNITE-12726
URL: https://issues.apache.org/jira/browse/IGNITE-12726
Pr
Ivan Bessonov created IGNITE-12789:
--
Summary: Tracking page repairing has no WAL record associated with
it
Key: IGNITE-12789
URL: https://issues.apache.org/jira/browse/IGNITE-12789
Project: Ignite
Ivan Bessonov created IGNITE-12839:
--
Summary: IGNITE-12789 broke WALRecordSerializationTest
Key: IGNITE-12839
URL: https://issues.apache.org/jira/browse/IGNITE-12839
Project: Ignite
Issue
Ivan Bessonov created IGNITE-12874:
--
Summary: Possible NPE in
GridDiscoveryManager#cacheGroupAffinityNode
Key: IGNITE-12874
URL: https://issues.apache.org/jira/browse/IGNITE-12874
Project: Ignite
Ivan Bessonov created IGNITE-12875:
--
Summary: Implement "EVT_CLUSTER_STATE_CHANGE_STARTED" event
Key: IGNITE-12875
URL: https://issues.apache.org/jira/browse/IGNITE-12875
Proje
Ivan Bessonov created IGNITE-12877:
--
Summary: "restorePartitionStates" always logs all meta pages into
WAL
Key: IGNITE-12877
URL: https://issues.apache.org/jira/browse/IGNITE-12877
Proje
Ivan Bessonov created IGNITE-12885:
--
Summary: Checkpoint thread executes partitions fsync in single
thread
Key: IGNITE-12885
URL: https://issues.apache.org/jira/browse/IGNITE-12885
Project: Ignite
Ivan Bessonov created IGNITE-13048:
--
Summary: WAL FSYNC mode doesn't work with disabled archiver
Key: IGNITE-13048
URL: https://issues.apache.org/jira/browse/IGNITE-13048
Project: I
Ivan Bessonov created IGNITE-13050:
--
Summary: ClusterGroup that is recomputed on topology change
Key: IGNITE-13050
URL: https://issues.apache.org/jira/browse/IGNITE-13050
Project: Ignite
Ivan Bessonov created IGNITE-13058:
--
Summary: GridCommandHandlerTest.testKillHangingRemoteTransactions
failed
Key: IGNITE-13058
URL: https://issues.apache.org/jira/browse/IGNITE-13058
Project
Ivan Bessonov created IGNITE-13062:
--
Summary:
DistributedMetaStoragePersistentTest.testJoinNodeWithLongerHistory failed
Key: IGNITE-13062
URL: https://issues.apache.org/jira/browse/IGNITE-13062
Ivan Bessonov created IGNITE-13156:
--
Summary: Continuous query filter deployment hungs discovery thread
Key: IGNITE-13156
URL: https://issues.apache.org/jira/browse/IGNITE-13156
Project: Ignite
Ivan Bessonov created IGNITE-13235:
--
Summary: Deadlock in IgniteServiceProcessor
Key: IGNITE-13235
URL: https://issues.apache.org/jira/browse/IGNITE-13235
Project: Ignite
Issue Type: Bug
Ivan Bessonov created IGNITE-13242:
--
Summary:
LocalWalModeChangeDuringRebalancingSelfTest.testDataClearedAfterRestartWithDisabledWal
fails
Key: IGNITE-13242
URL: https://issues.apache.org/jira/browse/IGNITE
Ivan Bessonov created IGNITE-13246:
--
Summary: Implement EVT_BASELINE_XXX events
Key: IGNITE-13246
URL: https://issues.apache.org/jira/browse/IGNITE-13246
Project: Ignite
Issue Type
Ivan Bessonov created IGNITE-13266:
--
Summary: PDS (Indexing) fails with 'Exit code 137"
Key: IGNITE-13266
URL: https://issues.apache.org/jira/browse/IGNITE-13266
Project: Ignite
Ivan Bessonov created IGNITE-13597:
--
Summary: Execution timeout in PDS 2
Key: IGNITE-13597
URL: https://issues.apache.org/jira/browse/IGNITE-13597
Project: Ignite
Issue Type: Test
Ivan Bessonov created IGNITE-13697:
--
Summary: Control.sh API - schedule & cancel
Key: IGNITE-13697
URL: https://issues.apache.org/jira/browse/IGNITE-13697
Project: Ignite
Issue Type:
Ivan Bessonov created IGNITE-13709:
--
Summary: Control.sh API - status
Key: IGNITE-13709
URL: https://issues.apache.org/jira/browse/IGNITE-13709
Project: Ignite
Issue Type: Sub-task
Ivan Bessonov created IGNITE-13742:
--
Summary: Fix failed
WalModeChangeAdvancedSelfTest.testMaintenanceIsSkippedIfWasFixedManuallyOnDowntime
Key: IGNITE-13742
URL: https://issues.apache.org/jira/browse/IGNITE
Ivan Bessonov created IGNITE-13743:
--
Summary: Defragmentation JMX API for schedule/cancel/status
Key: IGNITE-13743
URL: https://issues.apache.org/jira/browse/IGNITE-13743
Project: Ignite
Ivan Bessonov created IGNITE-13786:
--
Summary: PDS defragmentation can inflate index size
Key: IGNITE-13786
URL: https://issues.apache.org/jira/browse/IGNITE-13786
Project: Ignite
Issue Type
Ivan Bessonov created IGNITE-13795:
--
Summary: java.nio.file.InvalidPathException: Illegal char <:> at
lock page on windows
Key: IGNITE-13795
URL: https://issues.apache.org/jira/browse/IGNITE
Ivan Bessonov created IGNITE-13802:
--
Summary: GridCacheOffheapManager#addPartitions ignores candidate
pages count for index partition
Key: IGNITE-13802
URL: https://issues.apache.org/jira/browse/IGNITE-13802
Ivan Bessonov created IGNITE-13808:
--
Summary: Control.sh validate_indexes throws CorruptedTreeException
and fails server node during check
Key: IGNITE-13808
URL: https://issues.apache.org/jira/browse/IGNITE
1 - 100 of 171 matches
Mail list logo
