tributions. I contributed to other open source projects and did <
> 10 commits to each. Because in daily work generally we use stable
> libraries and can allow ourselves to work only with bugs or
> improvements in open source libraries. And I consider it a way to go
>
I think in this discussion there should be a question - why do we still
need abbreviations for all variables and fields? What problem does it solve?
Nobody still clearly answered this question.
I saw only 2 arguments to keep abbreviations:
1) Less codebase symbols. I think it is a weak argument.
Huge +1
I guess jigsaw, "var" and VarHandle features can really improve the
codebase.
чт, 10 дек. 2020 г. в 23:41, Vladimir Steshin :
> My + for java 11
>
> On 08.12.2020 15:00, Nikolay Izhikov wrote:
> > +1 for using java 11.
> >
> >> 8 дек. 2020 г., в 13:18, ткаленко кирилл
> написал(а):
> >>
Alexey,
>> If a CDC agent is restarted, it will have to start from scratch
>> If a CDC reader does not keep up with the WAL write rate (e.g. there
is a short-term write burst and WAL archive is small), the Ignite node
will
delete WAL segments while the consumer is still reading it.
I think
This tool is also can be used to store snapshots in an external warehouse.
ср, 14 окт. 2020 г. в 14:57, Pavel Kovalenko :
> Hi Nikolay,
>
> The idea is good. But what do you think to integrate these ideas into
> WAL-G project?
> https://github.com/wal-g/wal-g
> It's
Hi Nikolay,
The idea is good. But what do you think to integrate these ideas into WAL-G
project?
https://github.com/wal-g/wal-g
It's a well-known tool that is already used to stream WAL for PostgreSQL,
MySQL, and MongoDB.
The advantages are integration with S3, GCP, Azure out of the box,
Hi Maksim,
I think your proposal is very good and useful not only for introducing new
types of storage engine but also it's a good trigger to rework the existing
storage engine to decouple its components of each other.
I have a key question that we should answer. Where we should place our
Nice job Sergey. You deserve it!
On Fri 17. Jul 2020 at 20.46, Sergey Antonov
wrote:
> Congratulations, Sergey!
>
> сб, 18 июл. 2020 г., 0:24 Andrey Mashenkov :
>
> > Congratulations, Sergey.
> >
> > пт, 17 июл. 2020 г., 15:06 Вячеслав Коптилин :
> >
> > > Hi,
> > >
> > > Well deserved! Keep it
Congratulations Slava!
On Tue 18. Feb 2020 at 22.20, Dmitriy Pavlov wrote:
> Hello Ignite Community,
>
> The Project Management Committee (PMC) for Apache Ignite has invited
> Vyacheslav Koptilin to become a committer and we are pleased to announce
> that he has accepted.
>
> Vyacheslav
Congratulations, Slava!
Don't let the bad code occupy master :)
вт, 18 февр. 2020 г. в 22:20, Dmitriy Pavlov :
> Hello Ignite Community,
>
> The Project Management Committee (PMC) for Apache Ignite has invited
> Vyacheslav Koptilin to become a committer and we are pleased to announce
> that he
Anton, Slava
I guess we should have a system property to have ability to turn off PME
free switch behavior if something goes wrong after release.
After feature battle testing we can remove it in the next release.
чт, 19 дек. 2019 г. в 15:26, Anton Vinogradov :
> Slava,
>
> >> It would be nice
Aleksei,
Congratulations! You definitely deserve it.
пн, 16 дек. 2019 г. в 14:42, Ivan Pavlukhin :
> Aleksei, my congratulations!
>
> сб, 14 дек. 2019 г. в 10:50, Zhenya Stanilovsky >:
> >
> > Big deal and huge responsibility.
> >
> > Congrats Aleksei!
> >
> > > Hello Ignite Community,
> > >
>
+1 for Dmitry Pavlov
ср, 30 окт. 2019 г. в 18:46, Alexei Scherbakov :
> +1 for Dmitry Pavlov
>
> ср, 30 окт. 2019 г. в 18:22, aealexsandrov :
>
> > +1 Alexey Goncharuk
> >
> >
> >
> > --
> > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
> >
>
>
> --
>
> Best regards,
> Alexei
Hi Nikita,
1. As I can understand, this functionality is needed if a custom message is
needed to be processed only on the coordinator node. I'm not following for
what purposes it was implemented and I see the real usage only in tests.
As far as this functionality is not used in production code, I
Pavel Kovalenko created IGNITE-12325:
Summary: GridCacheMapEntry reservation mechanism is broken with
enabled cache store
Key: IGNITE-12325
URL: https://issues.apache.org/jira/browse/IGNITE-12325
Pavel Kovalenko created IGNITE-12299:
Summary: Store tombstone links into separate BPlus tree to avoid
partition full-scan during tombstones remove
Key: IGNITE-12299
URL: https://issues.apache.org/jira/browse
Pavel Kovalenko created IGNITE-12298:
Summary: Write tombstones on incomplete baseline to get rid of
partition cleanup
Key: IGNITE-12298
URL: https://issues.apache.org/jira/browse/IGNITE-12298
Pavel Kovalenko created IGNITE-12297:
Summary: Detect lost partitions is not happened during cluster
activation
Key: IGNITE-12297
URL: https://issues.apache.org/jira/browse/IGNITE-12297
Project
Denis,
The idea of having a sandbox for running a user-defined code is useful, but
I don't fully understand the implementation approach.
There is no detailed description of the ticket about what public API
methods or configuration parameters should be covered.
There is no description of what have
Issues link is broken, because it has a filter that can't be found.
Here is correct link:
Pavel Kovalenko created IGNITE-12255:
Summary: Cache affinity fetching and calculation on client nodes
may be broken in some cases
Key: IGNITE-12255
URL: https://issues.apache.org/jira/browse/IGNITE-12255
Hi Dmitrii,
Thank you for contribution. I'll take a look at it. Could you please
describe in the ticket what changes have you done besides version update
and why they are needed?
ср, 11 сент. 2019 г. в 14:06, Dmitrii Ryabov :
> Hello, Igniters!
>
> I want to update Apachee Zookeeper version
Pavel Kovalenko created IGNITE-12088:
Summary: Cache or template name should be validated before attempt
to start
Key: IGNITE-12088
URL: https://issues.apache.org/jira/browse/IGNITE-12088
Project
I can agree that some part of javadocs we have is useless. It relates to
DTOs, getters/setters without side-effects, short self-descriptive methods.
In an ideal world, proper modularization of architecture, leading to
KISS/SOLID/DRY/etc. principles, writing self-documented code should result
in
Ivan,
> And there is also one idea (I am not fan of it but still). Can we use
> some kind of scripting for nodes filtering? In that case node filter
> is represented by script string, e.g. javascript.
I guess it can lead to the same situation as in Java NodeFilter's. We can't
control what
r forgot to implement
> .equals()
> > or did it incorrectly we can't deal anything with it.
> > All of those problems can lead to cluster instability and unpredictable
> > behavior.
>
> This is common issue to every user-provided code.
> Wrong implementation of affininty function is o
Nikolay,
Thank you for your feedback.
Could you please tell more about cases when custom node filter that not
relies on node attributes may be used?
For me, it's flexibility just for flexibility that introduces problems
described in the topic.
I don't see yet any practical cases with NodeFilter
Hello Igniters,
I would like to start a discussion about simplifying NodeFilter
functionality.
At the moment NodeFilter's are used to control Caches and Services
distribution across nodes.
In most cases, NodeFIlter implementation seeks for a specific attribute in
NodeAttributes map. If the
Hello Maxim,
Thank you for researching this.
It seems those events can be used as an interceptor for the rebalance
process to make some extra actions after the entry is rebalanced.
However, I don't see any real usages despite tests. Most likely
functionality that used such rebalance events no
cheOperationsBlockedDuration` - histogram of blocking PME durations.
>
> В Чт, 25/07/2019 в 22:40 +0300, Pavel Kovalenko пишет:
> > Nikolay,
> >
> > Okay, sounds reasonable.
> > I just want to add that currentPmeTime is also useful alerting systems,
> not
> > only
, Nikolay Izhikov wrote:
> I think exact time should be obtained from logs, isnt it?
>
>
> чт, 25 июля 2019 г., 20:00 Pavel Kovalenko :
>
> > Nikolay,
> >
> > Yes, I have a chance to see HistogramMetric and moreover reviewed it) My
> > question was mostly about
then 1000, more then
> 1000] millis.
>
> чт, 25 июля 2019 г., 18:55 Pavel Kovalenko :
>
> > Nikolay,
> >
> > Could you please explain deeper what structure will be of PME histogram?
> >
> > чт, 25 июл. 2019 г. в 11:56, Nikolay I
ates and translations on a previous topology.
> > > > > > > > > > > > 5. sendSingleMessageTime. Time when a node sent a
> single message.
> > > > > > > > > > > > 6. recieveFullMessageTime. Time when a node received
> a full message.
> > > > >
> > > > What's the reason for duration counting?
> > > > AFAIU, it's a monitoring system feature to count the durations.
> > > > Sine monitoring system checks metrics periodically it will know the
> > > > duration by its own log.
> > >
CurrentBlockingPmeDuration. But I haven't come up with a better
> name yet.
>
> пт, 19 июл. 2019 г. в 18:30, Pavel Kovalenko :
> >
> > Nikita,
> >
> > I think getCurrentPmeDuration doesn't show useful information. The main
> PME side effect for end-users i
released yet). Seems for users it
> useless in case of non-blocking PME.
> Lets name it timeSinceOperationsBlocked. It'll be timestamp when
> blocking started (minimal value of cluster nodes) and 0 if blocking
> ends (there is no running PME).
>
> WDYT?
>
> пт, 19 ию
Maxim,
Go ahead. I don't see any real usages of this functionality and seems it
obsolete and should be removed.
пт, 19 июл. 2019 г. в 08:36, Anton Vinogradov :
> Folks,
>
> To be clear, I'm going to merge the PR next Monday in case of interest lack
> (which means the feature is obsolete and can
Hi Nikita,
Thank you for working on this. What do you think if we change the boolean
value of metric to a long value that represents time in milliseconds when
operations were blocked?
Since we have not only JMX and now metrics are periodically exported to
some backend it can give a more clear
I would like to add to the list following:
1. Remove ForceKeyRequests and related code. Since we have Late affinity
assignment and primary node partitions are always up to date we don't need
to request actual data from backups.
2. Remove @CentralizedAffinityFunction and related code. I don't see
Pavel Kovalenko created IGNITE-11852:
Summary: Assertion errors when changing PME coordinator to locally
joining node
Key: IGNITE-11852
URL: https://issues.apache.org/jira/browse/IGNITE-11852
Pavel Kovalenko created IGNITE-11773:
Summary: JDBC suite hangs due to cleared non-serializable proxy
objects
Key: IGNITE-11773
URL: https://issues.apache.org/jira/browse/IGNITE-11773
Project
Hi Nikita,
Thank you for your work. This is great improvement. I'll take look on it in
next couple of days. Could you please run TC and provide MTCGA bot status
about this change?
чт, 28 мар. 2019 г. в 14:29, Nikita Amelchev :
> Hello, Igniters!
>
> I have implemented lightweight version of
Hi Roman,
I think this InvalidPartition case can be simply handled
in GridCacheTtlManager.expire method.
For workaround a custom FailureHandler can be configured that will not stop
a node in case of such exception is thrown.
пн, 25 мар. 2019 г. в 08:38, Roman Shtykh :
> Igniters,
>
> Restarting
Pavel Kovalenko created IGNITE-11455:
Summary: Introduce free lists rebuild mechanism
Key: IGNITE-11455
URL: https://issues.apache.org/jira/browse/IGNITE-11455
Project: Ignite
Issue Type
> tests.
>
> What do you think?
>
>
>
> ср, 20 февр. 2019 г. в 11:41, Pavel Kovalenko :
>
> > Vyacheslav,
> >
> > Thank you for answers!
> >
> > >> I'm not sure what is a problem here?
> > At the moment it's a little bit hard to unders
; 3) It doesn't cover the case when some code which works on the current
> version will not work on older versions due to compile/runtime
> incompatibility.
>
> Please, describe the issue in more details?
>
> On Tue, Feb 19, 2019 at 7:55 PM Pavel Kovalenko
> wrote:
> >
moval or updates.
>
> >> Each new version is represented by a single pom
> Sound not good.
> Could you please share examples for each feature you mentioned?
>
> Anyway. I don't like the idea to implement something new instead of
> improving the existing.
>
> On Tue
Igniters,
I would like to start a discussion about replacement existing
persistence compatibility test framework with the newer version.
The main purpose of that action is simplifying compatibility tests
development and support.
The current version of the test framework has 3 disadvantages:
1)
Pavel Kovalenko created IGNITE-10821:
Summary: Caching affinity with affinity similarity key is broken
Key: IGNITE-10821
URL: https://issues.apache.org/jira/browse/IGNITE-10821
Project: Ignite
Pavel Kovalenko created IGNITE-10799:
Summary: Optimize affinity initialization/re-calculation
Key: IGNITE-10799
URL: https://issues.apache.org/jira/browse/IGNITE-10799
Project: Ignite
Pavel Kovalenko created IGNITE-10771:
Summary: Print troubleshooting hint when exchange latch got stucked
Key: IGNITE-10771
URL: https://issues.apache.org/jira/browse/IGNITE-10771
Project: Ignite
Pavel Kovalenko created IGNITE-10749:
Summary: Improve speed of checkpoint finalization on binary memory
recovery
Key: IGNITE-10749
URL: https://issues.apache.org/jira/browse/IGNITE-10749
Project
+1
When I just joined the project I was really confused with the huge number
of opened PRs with poor description and cryptic reason.
This can give to newcomers a weird representation of what is
actually happening in the project.
Don't be lazy, just spend 5-10 minutes of free time and clean up
Pavel Kovalenko created IGNITE-10625:
Summary: Do first checkpoint on node start before join to topology
Key: IGNITE-10625
URL: https://issues.apache.org/jira/browse/IGNITE-10625
Project: Ignite
Pavel Kovalenko created IGNITE-10624:
Summary: Cache deployment id may be different that cluster-wide
after recovery
Key: IGNITE-10624
URL: https://issues.apache.org/jira/browse/IGNITE-10624
Pavel Kovalenko created IGNITE-10556:
Summary: Attempt to decrypt data records during read-only
metastorage recovery leads to NPE
Key: IGNITE-10556
URL: https://issues.apache.org/jira/browse/IGNITE-10556
Pavel Kovalenko created IGNITE-10493:
Summary: Refactor exchange stages time measurements
Key: IGNITE-10493
URL: https://issues.apache.org/jira/browse/IGNITE-10493
Project: Ignite
Issue
Pavel Kovalenko created IGNITE-10485:
Summary: Ability to get know more about cluster state before
NODE_JOINED event is fired cluster-wide
Key: IGNITE-10485
URL: https://issues.apache.org/jira/browse/IGNITE
Pavel Kovalenko created IGNITE-10397:
Summary: SQL Schema may be lost after cluster activation and
simple query run
Key: IGNITE-10397
URL: https://issues.apache.org/jira/browse/IGNITE-10397
Pavel Kovalenko created IGNITE-10298:
Summary: Possible deadlock between restore partition states and
checkpoint begin
Key: IGNITE-10298
URL: https://issues.apache.org/jira/browse/IGNITE-10298
Pavel Kovalenko created IGNITE-10235:
Summary: Cache registered in QueryManager twice if parallel caches
start is disabled
Key: IGNITE-10235
URL: https://issues.apache.org/jira/browse/IGNITE-10235
Pavel Kovalenko created IGNITE-10226:
Summary: Partition may restore wrong MOVING state during crash
recovery
Key: IGNITE-10226
URL: https://issues.apache.org/jira/browse/IGNITE-10226
Project
Nikolay,
JDK 1.8.0_151-b12
пн, 29 окт. 2018 г. в 15:31, Nikolay Izhikov :
> Hello, Pavel.
>
> What jdk version do you use?
>
> В Пн, 29/10/2018 в 15:30 +0300, Pavel Kovalenko пишет:
> > Hello Igniters,
> >
> > I have a problem with running TDE tests on my local
Pavel Kovalenko created IGNITE-10035:
Summary: Fix tests IgniteWalFormatFileFailoverTest
Key: IGNITE-10035
URL: https://issues.apache.org/jira/browse/IGNITE-10035
Project: Ignite
Issue
Eduard,
+1 for that topic.
I don't see any reasons to use these abbreviations at all and vote to
deprecate them.
If anybody can explain why we still need them (less number of letters in
variable names is not an argument) we can discuss and revisit the current
list.
>From my side of view, these
Pavel Kovalenko created IGNITE-9725:
---
Summary: Introduce affinity distribution prototype for equal cache
group configurations
Key: IGNITE-9725
URL: https://issues.apache.org/jira/browse/IGNITE-9725
Pavel Kovalenko created IGNITE-9683:
---
Summary: Create manual pinger for ZK client
Key: IGNITE-9683
URL: https://issues.apache.org/jira/browse/IGNITE-9683
Project: Ignite
Issue Type
Pavel Kovalenko created IGNITE-9661:
---
Summary: Improve partition states validation
Key: IGNITE-9661
URL: https://issues.apache.org/jira/browse/IGNITE-9661
Project: Ignite
Issue Type
Pavel Kovalenko created IGNITE-9649:
---
Summary: Rework logging in important places
Key: IGNITE-9649
URL: https://issues.apache.org/jira/browse/IGNITE-9649
Project: Ignite
Issue Type
Pavel Kovalenko created IGNITE-9562:
---
Summary: Destroyed cache that resurrected on a old offline node
breaks PME
Key: IGNITE-9562
URL: https://issues.apache.org/jira/browse/IGNITE-9562
Project
Pavel Kovalenko created IGNITE-9561:
---
Summary: Optimize affinity initialization for started cache groups
Key: IGNITE-9561
URL: https://issues.apache.org/jira/browse/IGNITE-9561
Project: Ignite
Pavel Kovalenko created IGNITE-9501:
---
Summary: Exclude newly joining nodes from exchange latch
Key: IGNITE-9501
URL: https://issues.apache.org/jira/browse/IGNITE-9501
Project: Ignite
Pavel Kovalenko created IGNITE-9496:
---
Summary: Add listenAsync method to GridFutureAdapter
Key: IGNITE-9496
URL: https://issues.apache.org/jira/browse/IGNITE-9496
Project: Ignite
Issue
Pavel Kovalenko created IGNITE-9494:
---
Summary: Communication error resolver may be invoked when topology
is under construction
Key: IGNITE-9494
URL: https://issues.apache.org/jira/browse/IGNITE-9494
Pavel Kovalenko created IGNITE-9493:
---
Summary: Communication error resolver shouldn't be invoked if
connection with client breaks unexpectedly
Key: IGNITE-9493
URL: https://issues.apache.org/jira/browse/IGNITE
Pavel Kovalenko created IGNITE-9492:
---
Summary: Limit number of threads which process SingleMessage with
exchangeId==null
Key: IGNITE-9492
URL: https://issues.apache.org/jira/browse/IGNITE-9492
Pavel Kovalenko created IGNITE-9491:
---
Summary: Exchange latch coordinator shouldn't be oldest node in a
cluster
Key: IGNITE-9491
URL: https://issues.apache.org/jira/browse/IGNITE-9491
Project
Pavel Kovalenko created IGNITE-9449:
---
Summary: Lazy unmarshalling of discovery events in TcpDiscovery
Key: IGNITE-9449
URL: https://issues.apache.org/jira/browse/IGNITE-9449
Project: Ignite
Dmitriy,
Congratulations. This is very nice to see such valuable community member in
PMC role.
чт, 30 авг. 2018 г. в 20:11, Dmitriy Govorukhin <
dmitriy.govoruk...@gmail.com>:
> Dmitriy,
>
> My congratulations!
> Thank you for your work!
>
> On Thu, Aug 30, 2018 at 1:58 PM Maxim Muzafarov
>
Dmitriy,
Congratulations, you finally got it :)
чт, 30 авг. 2018 г. в 20:25, Ivan Rakov :
> Dmitriy,
>
> Congratulations! Your new role is well deserved, keep going!
>
> Best Regards,
> Ivan Rakov
>
> On 30.08.2018 1:20, Dmitriy Setrakyan wrote:
> > Dmitriy, congrats! Looking forward to many
Pavel Kovalenko created IGNITE-9420:
---
Summary: Move logical recovery phase outside of PME
Key: IGNITE-9420
URL: https://issues.apache.org/jira/browse/IGNITE-9420
Project: Ignite
Issue Type
Pavel Kovalenko created IGNITE-9419:
---
Summary: Avoid saving cache configuration synchronously during PME
Key: IGNITE-9419
URL: https://issues.apache.org/jira/browse/IGNITE-9419
Project: Ignite
Pavel Kovalenko created IGNITE-9418:
---
Summary: Avoid initialize file page store manager for caches
during PME synchronously
Key: IGNITE-9418
URL: https://issues.apache.org/jira/browse/IGNITE-9418
of these cases, you need just local available CacheDescriptors to
restore binary state from WAL.
I would like also see a test when Ignite is stopped in the middle of a
checkpoint and binary recovery succeed before PME in that case also.
ср, 22 авг. 2018 г. в 15:31, Pavel Kovalenko :
> Hello Maxim,
>
&
Pavel Kovalenko created IGNITE-9398:
---
Summary: Reduce time on processing CustomDiscoveryMessage by
discovery worker
Key: IGNITE-9398
URL: https://issues.apache.org/jira/browse/IGNITE-9398
Project
Hello Steve,
I've looked at Persistent Collectors library, but don't see any big
advantages to use it inside Ignite right now.
Why do you think, that marshalling/unmarshalling process will be speeded up
with this library? As I can see there are no explicit changes in
serialization process, just
issed
> - fix abbreviations regarding IdeaAbbrPlugin
> - createDataRegionConfiguration method can be removed and simplified
> - startMemoryPolicies rename to startDataRegion
> - output messages format fix code style needed
> - fix format javadoc's
> - make inner classes private
> -
Pavel Kovalenko created IGNITE-9271:
---
Summary: Implement transaction commit using thread per partition
model
Key: IGNITE-9271
URL: https://issues.apache.org/jira/browse/IGNITE-9271
Project: Ignite
Pavel Kovalenko created IGNITE-9270:
---
Summary: Design thread per partition model
Key: IGNITE-9270
URL: https://issues.apache.org/jira/browse/IGNITE-9270
Project: Ignite
Issue Type: Sub
Igniters,
I would like to add that it would be very nice to have prepared scenarios
in packed docker images with docker-compose, to easily deploy and run it on
AWS environment. This will give the possibility to benchmark any changes
independently and fastly.
2018-08-09 18:51 GMT+03:00 Anton
Andrey,
Huge +1 for that.
"Force server mode" increases the complexity of understanding how cluster
in ring mode works without real benefits.
If a user wants to start client node first before server nodes have
started, he can adjust timeouts on connection and spin till a client is
connected.
Pavel Kovalenko created IGNITE-9206:
---
Summary: Node can't join to ring if all existing nodes have
stopped and another new node joined ahead
Key: IGNITE-9206
URL: https://issues.apache.org/jira/browse/IGNITE
ple batches to be able to
> > transfer it over the network faster.
> >
> > D.
> >
> >
> > On Fri, Aug 3, 2018 at 3:21 AM, Pavel Kovalenko
> > wrote:
> >
> > > Dmitriy,
> > >
> > > I think we don't need a separate implement
Pavel Kovalenko created IGNITE-9185:
---
Summary: Collect and check update counters visited during WAL
rebalance
Key: IGNITE-9185
URL: https://issues.apache.org/jira/browse/IGNITE-9185
Project: Ignite
Hello Maxim,
1) Yes, Discovery Manager is starting after GridCacheProcessor, which
starts GridCacheDatabaseSharedManager which invokes readMetastorage on
start.
2) Before we complete the local join future, we create and add Exchange
future on local node join to ExchangeManager. So, when local
GMT+03:00 Dmitriy Setrakyan :
> On Thu, Aug 2, 2018 at 1:08 AM, Pavel Kovalenko
> wrote:
>
> > Dmitriy,
> >
> > I still don't understand why do you think that it will be file system?
> > In all my previous messages I emphasized that this storage shouldn't be
> &g
; > 3) Just drop IGFS from the product, and do not implement any
> replacement
> > at
> > > all - personally, I am all for this decision.
> > >
> > > If you want I can guide you through IGFS architecture so that we better
> > > understand what should be done t
Hi Yakov,
Currently TC agents defended by Docker virtual network, that's why we don't
see intersection between several clusters, but in case of any step aside
(running several suites on one agent, running several tests on one machine
and so on) we will have problems and return back to this
Hello Alexey,
It's not so difficult to implement new type of indexing of data, but if you
want to reach performance in distributed environment you need to have
strong knowledge of a data you're indexing and what kind of queries you
want to execute.
Should be this index in-memory only or you want
This failure is known and happened because of missed maxSize of DataRegion.
All such problems will be fixed in
https://issues.apache.org/jira/browse/IGNITE-9157
2018-08-01 18:12 GMT+03:00 :
> Hi Ignite Developer,
>
> I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed.
> I
1 - 100 of 196 matches
Mail list logo
