Congratulations, Iurii!
ср, 14 февр. 2024 г. в 09:29, Pavel Tupitsyn :
>
> Congratulations Iurii!
>
> On Wed, Feb 14, 2024 at 8:17 AM Roman Puchkovskiy <
> roman.puchkovs...@gmail.com> wrote:
>
> > Congratulations!
> >
> > вт, 13 февр. 2024 г. в 23:51, Dmitriy Pavlov :
> > >
> > > Dear Igniters,
Congratulations, Nikita!
ср, 22 нояб. 2023 г. в 13:11, Aleksandr Pakhomov :
>
> Congratulations!
>
>
> > On 21 Nov 2023, at 18:18, Dmitriy Pavlov wrote:
> >
> > Hello Igniters,
> >
> > The Project Management Committee (PMC) for Apache Ignite
> > has invited Nikita Amelchev to become a member of
Great news!
Congratulations, Ivan!
сб, 17 сент. 2022 г. в 16:33, Dmitriy Pavlov :
>
> Hi Igniters!
>
> The Project Management Committee (PMC) for Apache Ignite has invited
> Ivan Daschinsky to become a member of the PMC and we are pleased to
> announce that he has accepted.
>
> Ivan contributed
the default log config.
> >
> > вт, 6 сент. 2022 г. в 13:20, Pavel Tupitsyn :
> > >
> > > Thanks for the explanation.
> > >
> > > Yes, I think we can apply the same color scheme everywhere, but let's
> > hear
> > > more opinions.
> >
r the enhancement!
> >
> > вт, 6 сент. 2022 г. в 10:37, Pavel Pereslegin :
> >
> > > Hello Igniters!
> > >
> > > Recently completed Ignite migration to use log4j2 [1].
> > > Log4j2 supports ANSI colorization in the console [2], which can help
>
Hello Igniters!
Recently completed Ignite migration to use log4j2 [1].
Log4j2 supports ANSI colorization in the console [2], which can help
in parsing log output.
As an experiment, I would like to colorize the test console output [3].
The color palette is similar to spring boot, see light [4]
gt; Pavel, I think we can delegate interceptors as a chain. The last
> >> delegate calls the service method. In this way, multiple ordered
> >> interceptors can be configured.
> >>
> >> ср, 29 июн. 2022 г. в 12:13, Pavel Pereslegin :
> >> >
> >> &g
sionId"));
> }
> }
> }
>
>
> As you can see, this way the user has full control over all aspects of the
> service call.
>
> Thoughts?
>
> On Tue, Jun 28, 2022 at 6:33 PM Pavel Pereslegin wrote:
>
> > Hello Igniters!
> >
> &
Hello Igniters!
I want to continue discussing a feature that allows users to create
their own middleware for Ignite services [1].
Earlier was added the ability to implicitly pass a set of user
parameters (ServiceCallContext) to the service [2].
This feature allows users to track the origin of a
Hi Mikalai!
We faced the same problem.
I created a "reproducer" and filled a ticket [1].
I did an initial analysis and from my point of view, the problem is in
the incorrect exception handling (detailed description inside the
ticket) without impact.
I plan to look into the issue in more detail
gt; > On Thu, Feb 10, 2022 at 6:16 PM Maxim Muzafarov
> > > wrote:
> > > >
> > > >> The Project Management Committee (PMC) for Apache Ignite has invited
> > > >> Pavel Pereslegin to become a committer and we are pleased to
> announce
> > > t
Hi!
Agree with Maxim.
It seems to me quite normal to return a proxy for a local instance in
the case when the user has explicitly enabled statistics collection in
the service settings. Those. by default, we do not change the behavior
and if the collection of metrics is not needed, a local
interface.
> >
> > I'm voting for option (3).
> >
> > чт, 16 дек. 2021 г. в 15:59, Pavel Tupitsyn :
> >
> > > Pavel,
> > >
> > > My vote is for option (1). Simple and clear.
> > >
> > > As you noted, with (2) it is not clear whi
reServices), which
contains only methods that use the service call context.
WDYT?
пт, 22 окт. 2021 г. в 14:36, Pavel Pereslegin :
>
> > 1. Add init/execute/cancel methods without parameters.
> > 2. Add default no-op implementations for the new methods (this is required
> >
Hello, Slava!
Thanks for pointing this out.
The fix has been merged [1].
[1] https://issues.apache.org/jira/browse/IGNITE-15895
ср, 10 нояб. 2021 г. в 12:31, Вячеслав Коптилин :
>
> Hello Pavel,
>
> It seems that your commit https://issues.apache.org/jira/browse/IGNITE-15801
> broke the
patibility).
> > 6. Finally, add a @ServiceContextResource annotation to inject
> > ServiceContext.
> >
> > If I haven't missed anything, this is not a breaking change, and it fully
> > switches to annotation-based injection.
> >
> > I'm not sure this is po
ticket for that?
> We can discuss and implement Java changes first.
>
> On Tue, Oct 19, 2021 at 8:27 PM Pavel Pereslegin wrote:
>
> > Thanks a lot for your suggestions.
> >
> > > We might consider injecting the ServiceContext instead of passing it to
>
iscoverable to me,
> > > > also simpler to implement (no reflection necessary).
> > > >
> > > > But existing ServiceContext properties are for the entire instance, not
> > > for
> > > > the current call.
> > > > So, to make it clear and obvious, let's do
> > > &g
s with keys as strings and values as bytearrays or strings. It
> > is
> > > >> ok
> > > >>> to
> > > >>>> allow user to set up middlewares for services and allow to enrich
> > > >> request
> > > >>>> context
hat leads to a situation when Java can use TypedContext but other
> > clients
> > > can't. I believe that the majority of services users are using Java and
> > it
> > > should be taken in accordance.
> > >
> > > P.S. I think it is possible to send plain ob
> class MyService implements ContextedWith {
> void doThings() {
> MyServiceContext ctx = getCtx();
>
> System.out.println("ctx.getArg1() = " + ctx.getArg1());
> }
>
> @Override public MyServiceContext getCtx() {
> return ServiceProxyContext.current();
> }
> }
>
>
Hello Igniters!
I want to implement a feature to support a custom "caller" context in
ignite services (see example in ticket description [1]).
Sometimes, when using Ignite services, it becomes necessary to pass
custom parameters from the "request source" to the service. This is
most commonly
evert [1] from the release 2.11 branch (I'll do it tomorrow)
> > > > - commit the [1] to the master branch (success build is enough
> > > > verification for this at this moment)
> > > > - create and configure TC with a technical azure account to test such
> > module
in stabilization phase and
> >> accepting
> >>>>> only
> >>>>>>>> blockers. I
> >>>>>>>>>>>>> may be
> >>>>>>>>>>>>>>>>> wrong, but this ticket d
Hello, Igniters!
I think the patch is ready [1].
Ilya, Atri,
could you help with the review?
[1] https://issues.apache.org/jira/browse/IGNITE-15388
пт, 27 авг. 2021 г. в 15:29, Maxim Muzafarov :
>
> Folks,
>
> I've created an issue to fix this. I think this is a blocker for the
> 2.11 release
Hello, Igniters!
Can someone check why TeamCity (ci.ignite.apache.org) is currently unavailable?
Hello, Slava.
This fix is required to fix the problem described in the ticket
description ("Cache group re-encryption does not start after cluster
secondary activation").
As for handling the exception in this case, from my point of view, the
impossibility of starting re-encryption is not critical
Hello, Alexey!
Is it possible to include a hotfix that corrects the command syntax
output in the control script? [1]
This bug can significantly complicate the use of the snapshot restore
function (one of the important features of 2.11). In addition, this
may raise a number of questions to the
Hello Petr,
we currently have many errors "Failed to start build" on TeamCity
due to "Unexpected error: java.lang.RuntimeException:
java.io.FileNotFoundException: /opt/buildagent/work/directory.map
(Read-only file system) " .[1]
Can you check what is wrong?
[1]
Hello Ilya,
thanks for pointing that out. It seems to be my fault.
We will fix this shortly or revert the patch that is likely causing this issue.
I created a blocker for this [1].
[1] https://issues.apache.org/jira/browse/IGNITE-14894
чт, 10 июн. 2021 г. в 18:05, Ilya Kasnacheev :
>
> Hello!
Hopefully we'll be done by the end of next week (2021.06.11).
пт, 4 июн. 2021 г. в 16:06, Alexey Gidaspov :
>
> Hello, Pavel.
>
> Can you specify the date more precisly?
>
> On 2021/06/04 12:05:53, Pavel Pereslegin wrote:
> > Hello Alexey.
> >
> > We have im
Hello Alexey.
We have implemented a feature to automatically restore the cache group
from a snapshot [1].
But this feature requires CLI management [2], which is currently on
review and should also be included in 2.11. We plan to finish with it
next week.
[1]
Hello Ilya.
Could you please add me to "Contributors 1" too?
Thank you.
вт, 27 апр. 2021 г. в 18:51, Ilya Kasnacheev :
>
> Hello!
>
> I think that role names are per-JIRA global, we can't rename them on a per
> project basis.
>
> It exists for very large projects to put more contributors on, we
Pavel Pereslegin created IGNITE-14424:
-
Summary: Cache group re-encryption does not start after cluster
secondary activation.
Key: IGNITE-14424
URL: https://issues.apache.org/jira/browse/IGNITE-14424
Pavel Pereslegin created IGNITE-14352:
-
Summary: Added the ability to check the consistency of individual
cache groups in a snapshot.
Key: IGNITE-14352
URL: https://issues.apache.org/jira/browse/IGNITE-14352
Pavel Pereslegin created IGNITE-14305:
-
Summary: Snapshot check command for indexed cache ends with
exceptions.
Key: IGNITE-14305
URL: https://issues.apache.org/jira/browse/IGNITE-14305
Project
Pavel Pereslegin created IGNITE-14227:
-
Summary: Partition map exchange may hang if the cluster is
deactivated during cache start failure handling.
Key: IGNITE-14227
URL: https://issues.apache.org/jira/browse
Pavel Pereslegin created IGNITE-14222:
-
Summary:
CacheGroupReencryptionTest.testPartitionFileDestroyAndRecreate is flaky
Key: IGNITE-14222
URL: https://issues.apache.org/jira/browse/IGNITE-14222
Pavel Pereslegin created IGNITE-14044:
-
Summary: Cache with node filter is not destroyed properly on the
filtered node.
Key: IGNITE-14044
URL: https://issues.apache.org/jira/browse/IGNITE-14044
Hello, Kirill!
Personally, I see no problem with this improvement. Please check my
comment in IGNITE-13831 [1] on the implementation of this change.
[1] https://issues.apache.org/jira/browse/IGNITE-13831
пт, 11 дек. 2020 г. в 13:23, ткаленко кирилл :
>
> Hello to all!
>
> When implementing
Pavel Pereslegin created IGNITE-13807:
-
Summary: testClientNodeJoinInactiveClusterWithNewStaticCacheConfig
and testClientNodeJoinActiveClusterWithNewStaticCacheConfig fails in master
Key: IGNITE-13807
URL
Pavel Pereslegin created IGNITE-13805:
-
Summary: Add support for cache group restore from a snapshot on
the same topology (inactive cluster)
Key: IGNITE-13805
URL: https://issues.apache.org/jira/browse/IGNITE
Pavel Pereslegin created IGNITE-13659:
-
Summary: TDE - Phase 3. Documentation
Key: IGNITE-13659
URL: https://issues.apache.org/jira/browse/IGNITE-13659
Project: Ignite
Issue Type: Task
s problem and be more careful in the future.
>
> On Fri, Oct 23, 2020 at 12:46 PM Pavel Pereslegin wrote:
> >
> > Hello folks,
> >
> > thanks to everyone who joined the review, greatly appreciate your
> > helpful comments.
> >
> > If there is no obje
Pavel Pereslegin created IGNITE-13626:
-
Summary: Add EncryptionConfiguration to .Net client
Key: IGNITE-13626
URL: https://issues.apache.org/jira/browse/IGNITE-13626
Project: Ignite
o it.
>
> сб, 3 окт. 2020 г. в 21:47, Alex Plehanov :
>
> > Hello guys,
> >
> > I've finished the review and approved the patch.
> > Anybody else would like to review it?
> >
> > пн, 28 сент. 2020 г. в 11:38, Pavel Pereslegin :
> >
> > >
Pavel Pereslegin created IGNITE-13520:
-
Summary: Client node with a static encrypted cache configuration
cannot join a cluster without EncryptionSPI configured.
Key: IGNITE-13520
URL: https
Pavel Pereslegin created IGNITE-13509:
-
Summary: Support encrypted caches in ducktape tests
Key: IGNITE-13509
URL: https://issues.apache.org/jira/browse/IGNITE-13509
Project: Ignite
BLE". Is this ticket finished?
>
> чт, 13 авг. 2020 г. в 13:49, Pavel Pereslegin :
>
> > Hello all.
> >
> > I'm working on TDE cache group key rotation [1] and I have a couple of
> > questions about partition re-encryption.
> >
> > As described in
Pavel Pereslegin created IGNITE-13390:
-
Summary: CLI (control.sh) "get_master_key_name" command should
display the current master key name.
Key: IGNITE-13390
URL: https://issues.apache.org/jira/bro
.apache.org/jira/browse/IGNITE-12843
[2]
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=95652384#TDE.Phase3.Cachekeyrotation.-Backgroundre-encryption
пт, 31 июл. 2020 г. в 11:09, Pavel Pereslegin :
>
> Hello,
>
> I'll expand the answer a bit about calculating CRC,
Pavel Pereslegin created IGNITE-13324:
-
Summary: Create NoOp version of GridEncryptionManager for
in-memory grid.
Key: IGNITE-13324
URL: https://issues.apache.org/jira/browse/IGNITE-13324
Project
Pavel Pereslegin created IGNITE-13320:
-
Summary: TDE - Phase-3. CLI management
Key: IGNITE-13320
URL: https://issues.apache.org/jira/browse/IGNITE-13320
Project: Ignite
Issue Type: Sub
versa - the lower (delegated) FileIO should check the
physical integrity and EncryptedFileIO should check the correctness of
the encryption key.
пт, 31 июл. 2020 г. в 10:40, Pavel Pereslegin :
>
> Hello,
>
> > 10. Question - CRC is read in two places encryptionFileIO and
> > filePa
Hello,
> 10. Question - CRC is read in two places encryptionFileIO and
> filePageStore - what should we do with this?
We need to calculate the CRC of encrypted data, because we may be
using the wrong encryption key to decrypt data, in which case we will
not understand if the physical integrity
tes about this issue? What types of implementations
> have you chosen (in-place, offline, or in the background)? I know that we
> want to add a partition defragmentation function, we can add a hole to
> integrate the re-encryption scheme. Could you update your IEP with your
> plans?
>
Pavel Pereslegin created IGNITE-13127:
-
Summary: Master key change can produce exception in discovery
notyfier worker when WAL is disabled.
Key: IGNITE-13127
URL: https://issues.apache.org/jira/browse/IGNITE
Hello Igniters.
If type of binary field does not match query entity field type we
still able to insert such entry into cache, but can't query it.
In the following example we have query entity with the UUID field
"name", but we insert String field "name" using binary object.
IgniteCache
gt;> >>>> I mean: serving supply requests.
>> >>>>
>> >>>> пн, 25 мая 2020 г. в 11:15, Alexei Scherbakov <
>> >>>> alexey.scherbak...@gmail.com>:
>> >>>>
>> >>>>> Nikolay,
>> >>>>
to continue.
> > - Design compatible with the multi-key architecture.
> > - It can be optimized to use own WAL buffer and to re-encrypt pages without
> > restoring them to on-heap.
> >
> > On Thu, May 14, 2020 at 1:54 AM Pavel Pereslegin wrote:
> >
> > > Hell
Folks,
Now, it seems that the problem has been fixed.
вт, 12 мая 2020 г. в 13:57, Pavel Pereslegin :
>
> Ivan,
>
> unfortunately this did not help, I left a comment about it in the
> latest INFRA ticket on this subject [1].
>
> [1] https://issues.apache.org/jira/browse/INFRA
Hello Igniters.
Recently, master key rotation for Apache Ignite Transparent Data
Encryption was implemented [1], but some security standards (PCI DSS
at least) require rotation of all encryption keys [2]. Currently,
encryption occurs when reading/writing pages to disk, cache encryption
keys are
; > Thank you! I merged the PR.
> >
> > Let's see that PR linking to JIRA and everything else work fine.
> >
> > Best regards,
> > Ivan Pavlukhin
> >
> > пт, 8 мая 2020 г. в 14:45, Pavel Pereslegin :
> > >
> > > Igniters,
> > >
rguments about the proposal.
> >
> > Best regards,
> > Ivan Pavlukhin
> >
> > чт, 7 мая 2020 г. в 17:39, Pavel Pereslegin :
> > >
> > > Igniters,
> > >
> > > recent github pull requests are not automatically linked to the jira
>
Pavel Pereslegin created IGNITE-12993:
-
Summary: Github notification integrations on new ASF infra feature
Key: IGNITE-12993
URL: https://issues.apache.org/jira/browse/IGNITE-12993
Project: Ignite
Igniters,
recent github pull requests are not automatically linked to the jira
tickets.
Infra advises creating a yaml configuration in the root of the repository
with the settings for the github bot [1].
Examples of such configuration in Hive [2] and HBase [3].
I suggest the following settings
Pavel Pereslegin created IGNITE-12977:
-
Summary: Document the ability to add non-primitive objects via
REST.
Key: IGNITE-12977
URL: https://issues.apache.org/jira/browse/IGNITE-12977
Project
Maxim,
> But what exactly is `constant` means?! I'd suggest applying this rule
> to all class fields with `static final` modifiers without any clauses.
> (check Java Naming convention [2] paragraph 3.3).
I disagree with this and want to clarify what exactly the Java naming
convention says:
>>
Hello, Nikolay.
This has been fixed by increasing the test timeout in IGNITE-12683 [1][2].
[1] https://issues.apache.org/jira/browse/IGNITE-12683
[2]
https://github.com/apache/ignite/commit/bf394a77e1de6432e493eb2818243a82b577f11e
вт, 21 апр. 2020 г. в 18:28, Nikolay Izhikov :
>
> Hello,
Hello,
I plan to implement cache key rotation for TDE (phase 3) [1][2].
(At the moment, the design is very draft and will be changed soon).
[1] https://issues.apache.org/jira/browse/IGNITE-12843
[2] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=95652384
сб, 11 апр. 2020 г. в
Pavel Pereslegin created IGNITE-12843:
-
Summary: TDE Phase-3. Cache key rotation.
Key: IGNITE-12843
URL: https://issues.apache.org/jira/browse/IGNITE-12843
Project: Ignite
Issue Type
Pavel Pereslegin created IGNITE-12703:
-
Summary: Remove misleading references to the currently missing
G.grid(null) method from public and internal javadocs.
Key: IGNITE-12703
URL: https://issues.apache.org
Pavel Pereslegin created IGNITE-12683:
-
Summary:
BPlusTreeReuseListPageMemoryImplTest.testIterateConcurrentPutRemove_2 fails
with timeout on TC
Key: IGNITE-12683
URL: https://issues.apache.org/jira/browse
> +1 to deprecate rebalanceOrder and remove related functionality,
Meant to "rework related functionality" not "remove".
чт, 13 февр. 2020 г. в 12:47, Pavel Pereslegin :
>
> Hello,
>
> +1 to deprecate rebalanceOrder and remove related functionality,
&
Hello,
+1 to deprecate rebalanceOrder and remove related functionality,
should we create a separate ticket for this?
Btw, as I understand, SYNC mode is only useful for in-memory caches,
because when persistence is enabled (and WAL is disabled during
rebalancing), even "ignite-sys-cache" owns
Pavel Pereslegin created IGNITE-12605:
-
Summary: Historical (WAL) rebalance can start on a cleared
partition if some baseline node leaves the cluster and then joins back.
Key: IGNITE-12605
URL: https
Pavel Pereslegin created IGNITE-12370:
-
Summary: WAL history reservation may fail due to an incorrect
determination of the availability of the WAL segment index (under race
condition).
Key: IGNITE-12370
URL
Pavel Pereslegin created IGNITE-12349:
-
Summary: File transmission can cause the cluster to freeze.
Key: IGNITE-12349
URL: https://issues.apache.org/jira/browse/IGNITE-12349
Project: Ignite
Igniters,
Many builds are stuck now due to “no compatible agent” (JCache TCK
1.1, MVCC Cache, MVCC PDS, Cassandra store) can anyone take a look?
Or instead of a WARNING, we can add a suggestion with a recommendation
for the production environment.
вт, 27 авг. 2019 г. в 11:41, Petr Ivanov :
>
> /opt is either does not exist on fresh system, or has the same restriction:
> no user access without admin intervention.
> /usr/local, /var/lib,
Pavel Pereslegin created IGNITE-12097:
-
Summary: Code cleanup: useless GridDhtInvalidPartitionException
handling that cannot be thrown on demander (preloadEntry).
Key: IGNITE-12097
URL: https
Pavel Pereslegin created IGNITE-12087:
-
Summary: Transactional putAll - significant performance drop on
big batches of entries.
Key: IGNITE-12087
URL: https://issues.apache.org/jira/browse/IGNITE-12087
Igniters,
Will someone else look at these changes [1]?
[1] https://github.com/apache/ignite/pull/6364
[2] https://issues.apache.org/jira/browse/IGNITE-11584
чт, 1 авг. 2019 г. в 18:53, Pavel Pereslegin :
>
> Igniters,
>
> Maxim Muzafarov and Anton Vinogradov reviewed my PR [1]
[2] https://issues.apache.org/jira/browse/IGNITE-11584
пт, 14 июн. 2019 г. в 17:37, Maxim Muzafarov :
>
> Pavel,
>
> Thank you for your efforts!
>
> I'll take a look, shortly.
>
> On Fri, 14 Jun 2019 at 15:53, Pavel Pereslegin wrote:
> >
> > Hello Igniters!
Hello Igniters!
I'm working on implementing batch updates in PageMemory [1] to improve
the performance of batch operations. Details can be found in IEP-32
[2].
As the first step, I have prepared PR [3] with the implementation of
batch insertion of several data rows into the free list [4].
Pavel Pereslegin created IGNITE-11584:
-
Summary: Implement batch insertion of new cache entries in
FreeList to improve rebalancing
Key: IGNITE-11584
URL: https://issues.apache.org/jira/browse/IGNITE-11584
>
> ср, 6 мар. 2019 г. в 10:57, Vladimir Ozerov :
>
> > Hi Pavel,
> >
> > As far as I know batch tree updates already being developed. Alex, could
> > you please elaborate?
> >
> > On Tue, Mar 5, 2019 at 5:05 PM Pavel Pereslegin
> wrote:
>
Hi Igniters!
I am working on implementing batch updates in PageMemory [1] to
improve the performance of preloader, datastreamer and putAll.
This task consists of two major related improvements:
1. Batch writing to PageMemory via FreeList - store several values at
once to single memory page.
2.
Thank you, Dmitriy.
чт, 28 февр. 2019 г. в 15:43, Dmitriy Pavlov :
>
> Hi Pavel,
>
> Please check now, I've added permissions.
>
> Sincerely,
> Dmitriy Pavlov
>
> ср, 27 февр. 2019 г. в 11:26, Pavel Pereslegin :
>
> > Hi, Igniters!
> >
> > I'm
Hi, Igniters!
I'm starting work on IGNITE-7935 (add a batch update operation to
PageMemory and Persistence) [1], this task is big enough to create an
IEP for it.
Could you grant me permsissions to create it?
My wiki login is 'xtern'.
Thank you.
[1]
Hi, Ilya,
thank you for pointing this out.
I am the author of this fix [1], and from my point of view, if changes
in TcpDiscoveryIpFinderAdapter may violate public API, we definitely
should rolling them back.
[1] https://issues.apache.org/jira/browse/IGNITE-9858
сб, 19 янв. 2019 г. в 01:38,
Pavel Pereslegin created IGNITE-10183:
-
Summary: [Test Failed]
IgniteClientReconnectCacheTest.testReconnectOperationInProgress flaky fails on
TC.
Key: IGNITE-10183
URL: https://issues.apache.org/jira/browse
Pavel Pereslegin created IGNITE-10080:
-
Summary: IgniteCacheTestSuite6 (Cache 6) contains some
long-running tests that should be optimized.
Key: IGNITE-10080
URL: https://issues.apache.org/jira/browse/IGNITE
Nikita,
personally, I don’t like that "check()" throws an AssertionError, but in
the case of a composite listener, it will indicate which of the conditions
did not work.
Btw, your case can be solved with custom listener, but I think it's good
improvement, let's do it.
чт, 25 окт. 2018 г. в 21:31,
Pavel Pereslegin created IGNITE-9976:
Summary: [Test Failed]
BinaryMetadataUpdatesFlowTest.testFlowNoConflicts flaky fails on TC.
Key: IGNITE-9976
URL: https://issues.apache.org/jira/browse/IGNITE-9976
Pavel Pereslegin created IGNITE-9935:
Summary: [Test Failed]
GridCacheBinaryObjectMetadataExchangeMultinodeTest.testReadRequestBlockedOnUpdatingMetadata
flaky fails on TC.
Key: IGNITE-9935
URL: https
Pavel Pereslegin created IGNITE-9858:
Summary: [Test Failed] SystemCacheNotConfiguredTest#test flaky
fails on TC (timeout).
Key: IGNITE-9858
URL: https://issues.apache.org/jira/browse/IGNITE-9858
Pavel Pereslegin created IGNITE-9756:
Summary: [Test Failed]
IgniteCacheIncrementTxTest.testIncrementTxTopologyChange2 fails sometimes in
master (timeout).
Key: IGNITE-9756
URL: https://issues.apache.org
possible, ofcourse, but solution and complexity will be
> > almost
> > > > > > equals to WAL enable/disable.
> > > > > >
> > > > > > пн, 25 июн. 2018 г. в 22:13, Denis Magda :
> > > > > >
> > > > > > > Fo
Pavel Pereslegin created IGNITE-9677:
Summary: [TC Bot] Automatic build trigger should track all
branches defined in configuration.
Key: IGNITE-9677
URL: https://issues.apache.org/jira/browse/IGNITE-9677
1 - 100 of 136 matches
Mail list logo
