Hello Anton,
Thanks for digging into this. The logic with checking the
reservations count seems fishy to me as well, so I have no objections with
the suggested change. This "if" statement does not answer why the partition
was being destroyed during the commit, though. Does the issue reproduce in
ule this improvement to next release, I'll try to find a
> time to implement it.
>
> What do you think?
>
> On Mon, Dec 30, 2019 at 12:05 PM Alexey Goncharuk
> wrote:
> >
> > Vyacheslav, thanks for the explanation, makes sense to me.
> >
> > I was thinking thou
k on Services IEP?
> >
> > If it is a frequent use-case we definitely should implement it.
> >
> >
> > On Tue, Dec 24, 2019 at 6:55 PM Alexey Goncharuk
> > wrote:
> > >
> > > Ok, got it.
> > >
> > > I agree that this i
Here are my two cents on the topic:
* Obviously it is bad to have two different management console utilities,
so visorcmd and control.sh should be merged into a single utility
* In my personal opinion, this utility should _not_ be interactive. In the
current state it is impossible to use
eployment result and possibly fail.
>
> In this case, a reasonable timeout might be an acceptable solution.
>
> We can improve guaranties in future releases, but there is an open
> question:
> - how long taking of proxy should wait? - deployment of "heavy"
> service may take a wh
:
> T serviceProxy(String name, Class svcItf, boolean sticky, long
> timeout)
>
>
> вт, 24 дек. 2019 г. в 12:11, Alexey Goncharuk >:
>
> > Well, this is exactly the case. The service is deployed from node A, the
> > proxy is created on node B, and "service not fo
over
> comm-spi), but it shouldn't affect end-users because the failed
> request will be retried in this case
>
>
>
>
> On Mon, Dec 23, 2019 at 6:55 PM Alexey Goncharuk
> wrote:
> >
> > Nikolay,
> >
> > Yes, I've rechecked, the new service processor i
Alexey Goncharuk created IGNITE-12490:
-
Summary: Service proxy throws "Service not found" exception right
after deploy
Key: IGNITE-12490
URL: https://issues.apache.org/jira/browse/IG
Nikolay,
Yes, I've rechecked, the new service processor is being used. I'll file a
bug shortly.
пн, 23 дек. 2019 г. в 17:33, Николай Ижиков :
> Alexey, are you sure, you are testing new service framework?
>
> Is yes - you definitely should file a bug.
>
> > 23 дек. 2019 г
Igniters,
I have a question based on one of my recent tests debugging.
The test is related to Ignite services. I noticed that sometimes a proxy
invocation of a newly deployed service fails because the service cannot be
found. I managed to reduce the test to a simple "start two nodes, deploy a
Hi Ivan,
I receive such emails from time to time and I did not manage to
understand the conditions when this happens. From a quick search it looked
like it was related to the number of messages being received per certain
time interval, but I could not confirm this based on the number of messages
Anton,
Shouldn't we target IGNITE-12470 to 2.8? It kind of does not make sense to
add an ability to disable potentially dangerous change only in the next
release.
чт, 19 дек. 2019 г. в 16:18, Anton Vinogradov :
> Pavel,
> Issue created - https://issues.apache.org/jira/browse/IGNITE-12470
>
>
Alexey Goncharuk created IGNITE-12438:
-
Summary: Extend communication protocol to establish client-server
connection
Key: IGNITE-12438
URL: https://issues.apache.org/jira/browse/IGNITE-12438
Alexey Goncharuk created IGNITE-12430:
-
Summary: Move PagePool to a separate class
Key: IGNITE-12430
URL: https://issues.apache.org/jira/browse/IGNITE-12430
Project: Ignite
Issue Type
Alexey Goncharuk created IGNITE-12412:
-
Summary: Incomplete check for ABA problem in
PageMemoryImpl#PagePool
Key: IGNITE-12412
URL: https://issues.apache.org/jira/browse/IGNITE-12412
Project
Maxim,
A side note - we did not cut the 2.8 branch yet, did we?
This information is not reflected on the release page and I just realized
that it is hard to choose a fix version for a ticket that is being merged
to master when release scope is being finalized. This moment is covered
neither in
Denis, Stephen,
Running a local query in a broadcast closure won't work on changing
topology. We specifically added an affinityCall method to the compute API
in order to pin a partition to prevent its moving and eviction throughout
the task execution. Therefore, the query inside an affinityCall
+1 for Alexey Goncharuk (binding)
пн, 28 окт. 2019 г. в 21:06, Denis Magda :
> Ignite community,
>
> Please cast a vote for one of the following candidates:
>
>- Alexey Goncharuk
>- Dmitry Pavlov
>- Nikolay Izhikov
>- Pavel Tupitsyn
>
> Everyb
> > counted for the Chair election:
> >
> >- Nikolay Izhikov
> >- Alexey Goncharuk
> >- Dmitry Pavlov (confirmed)
> >- Pavel Tupitsyn
> >- Roman Shtykh
> >- Vladimir Ozerov (thinking)
> >- Yakov Zhdanov
&
edu/~vijay/papers/sosp19-recipe.pdf
[8]
https://cwiki.apache.org/confluence/display/IGNITE/IEP-16%3A+Optimization+of+rebalancing
вт, 8 окт. 2019 г. в 08:15, Alexey Goncharuk :
> Igniters,
>
> I would like to resurrect this discussion and will review the change again
> shortly. If anyone w
Igniters,
I would like to resurrect this discussion and will review the change again
shortly. If anyone want to join the review - you are welcome!
ср, 22 авг. 2018 г. в 18:49, Denis Magda :
> Hi Dmitry,
>
> That's a BSD-3-Clause license if to believe this statement
> "SPDX-License-Identifier:
Created a ticket for the first stage of this improvement. This can be a
first change towards the online mode suggested by Sergey and Anton.
https://issues.apache.org/jira/browse/IGNITE-12263
пт, 4 окт. 2019 г. в 19:38, Alexey Goncharuk :
> Maxim,
>
> Having a cluster-wide lock for a c
Alexey Goncharuk created IGNITE-12263:
-
Summary: Introduce native persistence compaction operation
Key: IGNITE-12263
URL: https://issues.apache.org/jira/browse/IGNITE-12263
Project: Ignite
trol.sh to force start
> > rebalance internally in the node with expected impact to performance.
> >
> >
> >
> > On Thu, Oct 3, 2019 at 12:08 PM Anton Vinogradov wrote:
> >
> > > Alexey,
> > > As for me, it does not matter will it be IEP, umbrella
I agree that we should have the ability to read any metric using simple
Ignite tooling. I am not sure if visor.sh is a good fit - if I
remember correctly, it will start a daemon node which will bump the
topology version with all related consequences. I believe in the long term
it will beneficial
>
> Seems, we should have different defaults and even distributions for
> different usage scenarios.
>
I still do not understand why defaults should be different for embedded and
"traditional RDBMS-like" installations. Having different defaults will
likely confuse users, not make usability easier.
is not
> true.
> > I think others may be confused in the same way.
> >
> > Denis Magda, Alexey Goncharuk, and others - please confirm that you
> > understand that `user.dir` means current directory, not user home
> > directory.
> >
> > In my opinion, this is
Anton, do you think we should file a single ticket for this or should we go
with an IEP? As of now, the change does not look big enough for an IEP for
me.
чт, 3 окт. 2019 г. в 11:18, Anton Vinogradov :
> Alexey,
>
> Sounds good to me.
>
> On Thu, Oct 3, 2019 at 10:51 AM A
vity periods, but
> even
> > in
> > >> case we found that activity was high and historical rebalance is not
> > >> suitable we may just remove the file and use regular rebalance to
> > restore
> > >> the partition (this will also lead to shrink).
>
Nikolay, Maxim,
Asking to provide a list of issues with the current H2 is pointless because
it has a fundamental architectural flow, not just a bunch of bugs:
Currently, the query execution is limited to a two-phase map-reduce task
(with an optional remote cursor when 'distributed joins' flag is
introduces addresses frequent usability and critical stability
issues
https://ignite.apache.org/releases/2.7.6/release_notes.html
Download the latest Ignite version from here:
https://ignite.apache.org/download.cgi
Please let us know [2] if you encounter any problems.
Regards,
Alexey Goncharuk
; Who can grant these permissions?
>
> Sincerely
> Dmitriy Pavlov
>
> чт, 19 сент. 2019 г. в 09:44, Artem Budnikov >:
>
> > Hi,
> >
> > I've created new versions for other projects on readme.io
> >
> > -Artem
> >
> > On 18.09.
Anton,
> >> The solution which Anton suggested does not look easy because it will
> most likely significantly hurt performance
> Mostly agree here, but what drop do we expect? What price do we ready to
> pay?
> Not sure, but seems some vendors ready to pay, for example, 5% drop for
> this.
5%
Denis,
It's not fundamental, but quite complex. In postgres, for example, this is
not maintained automatically and store compaction is performed using the
full vacuum command, which acquires exclusive table lock, so no concurrent
activities on the table are possible.
The solution which Anton
the docs
for 2.7.6?
[1] https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
ср, 11 сент. 2019 г. в 20:44, Alexey Goncharuk :
> Ivan, thank you!
>
> Will update release notes and start the build shortly.
>
> ср, 11 сент. 2019 г. в 20:41, Ivan Rakov :
>
>> Alexey,
Anton,
I looked through the presentation and the ticket but did not find any new
protocol description that you are going to implement. Can you describe the
complete protocol changes first (to save time for both you and during the
later review)?
Some questions that I have in mind:
* It looks
Folks,
I honestly tried to follow the discussion, but I think that I lost the
point of the debate. Should we try to exploit the newly introduced slack to
discuss the change and then send a follow-up here?
--AG
The vote for the new release candidate is closed now.
Vote result:
Vote passed with 7 votes +1 (5 binding +1 votes), no 0 and no -1 votes.
+1 votes:
Alexey Zinoviev
Ilya Kasnacheev (binding)
Maxim Muzafarow
Denis Magda (binding)
Pavel Tupitsyn (binding)
Alexey Kuznetsov (binding)
Andrey Gura
UTC.
https://www.timeanddate.com/countdown/to?year=2019=9=16=09=0=0=utc-1
-- Alexey Goncharuk
Ivan, thank you!
Will update release notes and start the build shortly.
ср, 11 сент. 2019 г. в 20:41, Ivan Rakov :
> Alexey,
>
> I've merged https://issues.apache.org/jira/browse/IGNITE-12163 to master
> and 2.7.6.
>
> Best Regards,
> Ivan Rakov
>
> On 11.09.2019 18
the release scope.
> >
> > PR is ready, currently waiting for a TC visa.
> >
> > Thoughts?
> >
> > [1] - https://issues.apache.org/jira/browse/IGNITE-12163
> >
> >
> > From: Alexey Goncharuk
> > Sent: Monday, September 9, 2019 5:11 PM
>
de this
> issue into the release scope.
>
> PR is ready, currently waiting for a TC visa.
>
> Thoughts?
>
> [1] - https://issues.apache.org/jira/browse/IGNITE-12163
>
>
> From: Alexey Goncharuk
> Sent: Monday, September 9, 2019 5:11 PM
> To: dev
> Cc: Dmitriy Govorukhin;
Sounds good?
>
> BTW, I'll be at GG office, you may join me via the internet or in the same
> room.
>
> On Mon, Sep 9, 2019 at 1:34 PM Alexey Goncharuk <
> alexey.goncha...@gmail.com>
> wrote:
>
> > Hello Anton,
> >
> > I doubt that Slack channel is a g
gt; > Hi Alexey,
> >
> > I think that I will finish work on the fix tomorrow. Fix already
> completed
> > but I need to get VISA from TC bot.
> >
> > On Mon, Sep 2, 2019 at 8:27 PM Alexey Goncharuk <
> > alexey.goncha...@gmail.com> wrote:
> >
> >&
Hello Anton,
I doubt that Slack channel is a good way to discuss/make decisions on such
an important topic. Changes in PME are usually the hard ones, and slack is
kind of a synchronous communication channel - with no known context it will
be hard to give appropriate feedback. Do you have
Alexey Goncharuk created IGNITE-12150:
-
Summary: Ignite javadoc contains bogus links, copyright is outdated
Key: IGNITE-12150
URL: https://issues.apache.org/jira/browse/IGNITE-12150
Project
it's ok to release 2.7.6 as it is now.
Thoughts?
сб, 31 авг. 2019 г. в 11:37, Alexey Goncharuk :
> Yes, my bad, forgot to include the link. That's the one.
>
> пт, 30 авг. 2019 г. в 15:01, Maxim Muzafarov :
>
>> Alexey,
>>
>> Does the issue [1] is related to this [
like important fixes, better to include them.
> >
> > пт, 30 авг. 2019 г. в 12:51, Alexey Goncharuk <
> alexey.goncha...@gmail.com>:
> >
> > > Igniters,
> > >
> > > Given that the RC1 vote did not succeed and we are still waiting f
Igniters,
Given that the RC1 vote did not succeed and we are still waiting for a few
minor fixes, may I suggest including these two tickest to the 2.7.6 scope?
https://issues.apache.org/jira/browse/IGNITE-12127
https://issues.apache.org/jira/browse/IGNITE-12128
The first one has been already
theless, I think that after this change it would be good enough to
> > last for a few years.
> >
> > What do you think?
> >
> > Regards,
> > --
> > Ilya Kasnacheev
> >
> >
> > вт, 27 авг. 2019 г. в 18:28, Alexey Goncharuk <
> alexey.goncha
be significantly simplified,
will create a separate ticket for this as well.
вт, 27 авг. 2019 г. в 19:06, Alexey Goncharuk :
> Got to the bottom of the issue with empty output and no JAVA_HOME.
>
> The reason is the following line in bin/control.sh:
>
> javaMajorVersion "${JAVA_HOME}
Alexey Goncharuk created IGNITE-12113:
-
Summary: control.sh terminates silently when JAVA_HOME is not set
Key: IGNITE-12113
URL: https://issues.apache.org/jira/browse/IGNITE-12113
Project: Ignite
Got to the bottom of the issue with empty output and no JAVA_HOME.
The reason is the following line in bin/control.sh:
javaMajorVersion "${JAVA_HOME}/bin/java"
Since JAVA_HOME is empty, the argument passed to the function is invalid
and terminates the script. I suggest to replace the
In the current state of the project, we cannot directly compare Ignite
setup process to the one of postgresql or another database. In many Ignite
examples, an embedded node (even with persistence) is started and it is
supposed to run without any additional FS rights grants or init steps. This
may
Dmitriy,
I confirm the first issue but did not get to the bottom of it yet; will
keep you posted.
вт, 27 авг. 2019 г. в 17:34, Dmitriy Pavlov :
> Hi Artem, thank you for your reply.
>
> Since this change is on its way, let's wait for 2.8.
>
>
> Petr Ivanov, Alexey Goncharuck, Ivan Rakov, could
+1
Checked the source compilation and release package build, node start, and a
few examples. Left a comment on the failed TC task in the discussion thread.
пт, 23 авг. 2019 г. в 18:15, Andrey Gura :
> +1
>
> On Fri, Aug 23, 2019 at 3:32 PM Anton Vinogradov wrote:
> >
> > -1 (binding)
> >
Who has created the task in the first place and can check why it fails? I
see no reason to fail the release unless somebody can reasonably explain
what exactly wrong with the provided source package.
пт, 23 авг. 2019 г. в 17:51, Alexey Goncharuk :
> I confirm that the release candidate
I confirm that the release candidate can be successfully built locally, and
it is also clear from the build log that the TC task tries to access a
wrong repository.
Who has access to the TC and can clean the .m2 cache?
пт, 23 авг. 2019 г. в 16:27, Dmitriy Pavlov :
> I suppose the issue is in TC
gt; > > > >
> > > > > > > This drawbacks make configuration complex, annoying and
> useless in most cases.
> > > > > > >
> > > > > > > Moreover, I think that:
> > > > > > >
> > >
Alexey Goncharuk created IGNITE-12019:
-
Summary: [TC Bot] PR screen resets the base branch on page refresh
Key: IGNITE-12019
URL: https://issues.apache.org/jira/browse/IGNITE-12019
Project: Ignite
for
> > > that. Or if we'd like to run faster then I'll appreciate if someone
> else
> > > steps in and prepares a list this week. I'll help to review and
> solidify it.
> > >
> > > -
> > > Denis
> > >
> > >
> > > On
gt; > feature A has to stay. It makes sense to ask about the APIs to be
> > removed
> > > > as well as integrations to go out of community support [1] in the
> same
> > > > thread.
> > > >
> > > > Has everyone expressed an opinion? If yes, I can g
en of the framework itself
> >>>>
> >>>> Yes. I planned to add `void configure(String param)` method to the
> metric API.
> >>>>
> >>>>> but change the metrics parameters in
> >>>>> runtime from JMX or comman
Hello Nikolay,
I will take a look shortly.
вт, 2 июл. 2019 г. в 14:30, Nikolay Izhikov :
> Guys.
>
> I've prepared PR to fix this issue.
> Who want to review it?
>
> https://github.com/apache/ignite/pull/6656
>
> В Пн, 01/07/2019 в 15:17 +0300, Nikolay Izhikov пишет:
> > Hello, Igniter.
> >
> >
Sorry for the duplicate - apparently, Maksim also spotted this regression.
Let's continue the discussion in the separate thread.
пт, 28 июн. 2019 г. в 19:04, Alexey Goncharuk :
> Hello Nikolay,
>
> From the latest TC runs I can see a sporadic regression
> in testParallel
Hello Nikolay,
>From the latest TC runs I can see a sporadic regression
in testParallelStartAndStop and testStartManyCaches tests. Digging deeper,
I see that stopping a single cache when there are many other started caches
now takes a significant amount of time.
Current suspect is
ully, not like a silver bullet.
> So, that's just a proposal :)
>
> Also, I'd like to propose to have some voting about full list later to gain
> "must be removed", "can be removed" and "should be kept" lists.
>
> On Thu, Jun 27, 2019 at 1:03 PM Alexey G
Nikolay,
My only concert is that we should have the metrics framework configuration
as the first-citizen of the framework itself. This way, we can configure
the metrics not only from file, but change the metrics parameters in
runtime from JMX or command-line, etc. Another concern is to have an
Anton,
I would like to pull-up the discussion regarding the near caches - I cannot
agree this is a feature that needs to be removed. Near caches provide
significant read performance improvements and, to the best of my knowledge,
are used in several cases in production. Can you elaborate on the
t; > > > > >
> > > > > > I think we should, definitely, remove concept of "client nodes"
> in
> > > the
> > > > > > future.
> > > > > > It's about product design decision, in the first place
e and drop client nodes!
>
> How does it sound?
>
>
> В Пн, 17/06/2019 в 15:52 +0300, Alexey Goncharuk пишет:
> > Nikolay,
> >
> > Local caches and scalar are already in the list :) Added the outdated
> > metrics point.
> >
> > пн, 17 июн. 2019 г. в
Nikolay,
Local caches and scalar are already in the list :) Added the outdated
metrics point.
пн, 17 июн. 2019 г. в 15:32, Nikolay Izhikov :
> * Scalar.
> * LOCAL caches.
> * Deprecated metrics.
>
> В Пн, 17/06/2019 в 15:18 +0300, Alexey Goncharuk пишет:
> > Igniters,
&
Igniters,
Even though we are still planning the Ignite 2.8 release, I would like to
kick-off a discussion related to Ignite 3.0, because the efforts for AI 3.0
will be significantly larger than for AI 2.8, better to start early.
As a first step, I would like to discuss the list of things to be
Denis,
I fully support this idea.
First, looking back, I do not think it was a good design in the first place
to build IGFS on top of Ignite caches. Second, I have never seen a case
where IGFS provided significant performance boost. Usually it's either all
data already fits buffer cache, and
Alexey Goncharuk created IGNITE-11930:
-
Summary: TcpDiscoverySpi does not close bound server socket if
discovery thread did not start
Key: IGNITE-11930
URL: https://issues.apache.org/jira/browse/IGNITE-11930
+1 (binding) - checked build from source, persistence example and basic
control.sh commands.
ср, 5 июн. 2019 г. в 17:48, Andrey Gura :
> +1 (binding)
>
> On Wed, Jun 5, 2019 at 4:39 PM Ilya Kasnacheev
> wrote:
> >
> > +1
> >
> > Built C++ and .Net successfully, started .Net <-> Java <-> C++ SSL
Hello Denis,
As for p.1 - fully agree. For p.2 - I have some ideas to be implemented in
the future in Ignite 3.0, will share some ideas later.
чт, 6 июн. 2019 г. в 13:29, Denis Magda :
> Hey Igniters,
>
> I'd like us to brainstorm how to solve the following usability issue.
>
> A user starts
Maxim,
I left response in the ticket.
пт, 17 мая 2019 г. в 12:04, Maxim Muzafarov :
> Igniters,
>
>
> I've implemented the file transfer machinery between grid nodes over
> Communication SPI covered by JIRA [1] and as the first part of IEP-28
> [3]. Please, consider my PR [2] to be reviewed and
Alexey Goncharuk created IGNITE-11750:
-
Summary: Implement locked pages info for long-running B+Tree
operations
Key: IGNITE-11750
URL: https://issues.apache.org/jira/browse/IGNITE-11750
Project
Alexey Goncharuk created IGNITE-11749:
-
Summary: Implement automatic pages history dump on
CorruptedTreeException
Key: IGNITE-11749
URL: https://issues.apache.org/jira/browse/IGNITE-11749
Project
Alexey Goncharuk created IGNITE-11732:
-
Summary: Multi-merged partitions exchange future may hang if node
left event is received last
Key: IGNITE-11732
URL: https://issues.apache.org/jira/browse/IGNITE-11732
Alexey Goncharuk created IGNITE-11725:
-
Summary: Document IGNITE_DISCOVERY_DISABLE_CACHE_METRICS_UPDATE
system property
Key: IGNITE-11725
URL: https://issues.apache.org/jira/browse/IGNITE-11725
Alexey Goncharuk created IGNITE-11707:
-
Summary: Tcp Discovery should drop pending metrics update message
when new message is received
Key: IGNITE-11707
URL: https://issues.apache.org/jira/browse/IGNITE-11707
Alexey Goncharuk created IGNITE-11704:
-
Summary: Write tombstones during rebalance to get rid of deferred
delete buffer
Key: IGNITE-11704
URL: https://issues.apache.org/jira/browse/IGNITE-11704
Alexey Goncharuk created IGNITE-11700:
-
Summary: Document disabled WAL during rebalance
Key: IGNITE-11700
URL: https://issues.apache.org/jira/browse/IGNITE-11700
Project: Ignite
Issue
Alexey Goncharuk created IGNITE-11691:
-
Summary: IgniteWalSerializerVersionTest fails in master with
NoSuchElementException
Key: IGNITE-11691
URL: https://issues.apache.org/jira/browse/IGNITE-11691
Alexey Goncharuk created IGNITE-11687:
-
Summary: Concurrent WAL replay & log may fail with CRC error on
read
Key: IGNITE-11687
URL: https://issues.apache.org/jira/browse/IGNITE-11687
Pro
Alexey Goncharuk created IGNITE-11676:
-
Summary: Clean up custom event callbacks
Key: IGNITE-11676
URL: https://issues.apache.org/jira/browse/IGNITE-11676
Project: Ignite
Issue Type
Alexey Goncharuk created IGNITE-11644:
-
Summary: Get rid of old exchange protocol
Key: IGNITE-11644
URL: https://issues.apache.org/jira/browse/IGNITE-11644
Project: Ignite
Issue Type
Alexey Goncharuk created IGNITE-11633:
-
Summary: Fix errors in WAL disabled archive mode documentation
Key: IGNITE-11633
URL: https://issues.apache.org/jira/browse/IGNITE-11633
Project: Ignite
Hello Ilya,
I do not see any issues with the mentioned test. I see the following output
in the logs:
[21:41:44] : [Step 4/5] [2019-03-22 21:41:44,970][INFO ][main][root] >>>
Stopping test:
TcpDiscoveryCoordinatorFailureTest#testCoordinatorFailedNoAddFinishedMessageStartOneNode
in 37768 ms <<<
Alexey Goncharuk created IGNITE-11626:
-
Summary: InitNewCoordinatorFuture should be reported in diagnostic
output
Key: IGNITE-11626
URL: https://issues.apache.org/jira/browse/IGNITE-11626
Project
Alexey Goncharuk created IGNITE-11622:
-
Summary: Investigate how CacheEntryRemovedException can be thrown
in onEntriesLocked
Key: IGNITE-11622
URL: https://issues.apache.org/jira/browse/IGNITE-11622
Alexey Goncharuk created IGNITE-11618:
-
Summary: Assertion got removed exception on entry with dht local
candidate on transaction timeout
Key: IGNITE-11618
URL: https://issues.apache.org/jira/browse/IGNITE
Alexey Goncharuk created IGNITE-11617:
-
Summary: New exchange coordinator skips client fast reply for
previous exchange
Key: IGNITE-11617
URL: https://issues.apache.org/jira/browse/IGNITE-11617
Alexey Goncharuk created IGNITE-11616:
-
Summary: NPE in MvccProcessorImpl when stopping a starting node
Key: IGNITE-11616
URL: https://issues.apache.org/jira/browse/IGNITE-11616
Project: Ignite
Alexey Goncharuk created IGNITE-11615:
-
Summary: IgniteBaselineAffinityTopologyActivationTest sometimes
fails due to NPE on node stop
Key: IGNITE-11615
URL: https://issues.apache.org/jira/browse/IGNITE-11615
Alexey Goncharuk created IGNITE-11613:
-
Summary: GridSpringBeanSerializationSelfTest fails in master
Key: IGNITE-11613
URL: https://issues.apache.org/jira/browse/IGNITE-11613
Project: Ignite
Alexey Goncharuk created IGNITE-11608:
-
Summary: Document static persistent caches and DDL behavior
Key: IGNITE-11608
URL: https://issues.apache.org/jira/browse/IGNITE-11608
Project: Ignite
Alexey Goncharuk created IGNITE-11604:
-
Summary: Drop column does not remove column from internal schema
Key: IGNITE-11604
URL: https://issues.apache.org/jira/browse/IGNITE-11604
Project: Ignite
201 - 300 of 980 matches
Mail list logo
