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
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] https://issues.apache.org/jira/browse/
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 ha
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!
>
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]
https://ci.ignite.apache.org/view
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 pro
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, Igniters!
Can someone check why TeamCity (ci.ignite.apache.org) is currently unavailable?
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 si
>> Now we are in stabilization phase and
> >> accepting
> >>>>> only
> >>>>>>>> blockers. I
> >>>>>>>>>>>>> may be
> >>>>>>>>>>>>>>>>> wron
> > > So here is the plan:
> > > >
> > > > - revert [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)
> > > > -
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 used
gt; }
>
> class MyService implements ContextedWith {
> void doThings() {
> MyServiceContext ctx = getCtx();
>
> System.out.println("ctx.getArg1() = " + ctx.getArg1());
> }
>
> @Override public MyServiceContext getCtx() {
> return ServiceProxyContext.current();
> }
> }
&g
n this case).
> > > That 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 i
t is ok to pass additional parameters as list of
> > key-value
> > > >>>> pairs with keys as strings and values as bytearrays or strings. It
> > is
> > > >> ok
> > > >>> to
> > > >>>> allow user to set up middlewares
e the cleanest and most discoverable 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, l
separate 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
&
; compatibility).
> > 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
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 javado
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
> >
ses, the
> > user even no need to know about this new interface.
> >
> > I'm voting for option (3).
> >
> > чт, 16 дек. 2021 г. в 15:59, Pavel Tupitsyn :
> >
> > > Pavel,
> > >
> > > My vote is for option (1). Simple and clear.
> &g
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 instanc
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 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 and
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 se
t;sessionId"));
> }
> }
> }
>
>
> 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!
> >
&
; >> 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 :
> >> >
> &
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] and
e! Thank you for 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], whic
to add to 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 opini
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 th
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 part
> +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,
> shoul
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 г. в
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, Ignite
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:
>> Th
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 fo
any arguments 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
; > 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,
> >
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 st
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
hrottle.
> > - Easy 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:
>
;>>
>> >>>> I mean: serving supply requests.
>> >>>>
>> >>>> пн, 25 мая 2020 г. в 11:15, Alexei Scherbakov <
>> >>>> alexey.scherbak...@gmail.com>:
>> >>>>
>> >>>>> Nikolay,
>>
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 ca
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?
>
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 is
vice 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
> > f
s://issues.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 ca
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
to do 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 :
> >
>
e, fix this 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
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 IGNIT
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, Ily
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] https://issues.apache.org/jira/browse/IGNITE-
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!
> >
> >
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. Ba
>
>
> ср, 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:
>
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].
Perfor
[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 Igni
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]
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, et
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?
Hello Andrei,
All these metrics available through JMX (see "DataRegionMetrics" group) [1].
[1] https://apacheignite.readme.io/docs/memory-metrics
пн, 24 сент. 2018 г. в 17:58, aealexsandrov :
>
> Hi Igniters,
>
> Small notes according to these fix.
>
> As I see that all logic of calculation off-n
Andrei,
I totally agree with you and I think that "ClusterMetrics" should also
be fixed, I'm just not sure that we should include this change in the
same ticket.
пн, 24 сент. 2018 г. в 18:43, aealexsandrov :
>
> Hi,
>
> OK, the user can use it to calculate the off-heap. But I think that the
> reaso
t; > > > > That's possible, ofcourse, but solution and complexity will be
> > almost
> > > > > > equals to WAL enable/disable.
> > > > > >
> > > > > > пн, 25 июн. 2018 г. в 22:13, Denis Magda :
> > > > > >
&g
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,
Hello, Igniters.
I found that AverageTxCommitTime and AverageTxRollbackTime metrics in
CacheMetrics calculated in milliseconds instead of microseconds as
pointed in javadoc (simple reproducer [1]).
Seems that it’s happening due to incorrect time units conversion in
IgniteTxLocalStateAdapter#onT
Hello, Igniters.
For some monitoring tasks we need to access these metrics through JMX:
1. Total server nodes in cluster.
2. Current topology version.
We can’t access them via JMX for now. Do you mind if I create a ticket
to add them?
I believe, they should be added to TcpDiscoverySpiMBean.
@M
Yakov, thanks for your suggestion.
I will create such MBean to include these metrics.
2017-11-07 20:11 GMT+03:00 Yakov Zhdanov :
> This seems to be incorrect place for implementing it. I would think of
> something more generic like IgniteClusterMBean. It should also work for any
> implementation
94
[4]
https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests&tab=projectOverview&branch_Ignite20Tests=pull/3007/head
2017-11-08 15:16 GMT+03:00 Pavel Pereslegin :
> Yakov, thanks for your suggestion.
>
> I will create such MBean to include these metrics.
>
> 2017
Hello all.
In addition, I found similar closed issue about cache metrics and
client mode [1].
The ticket resolution seems strange, because it can be reproduced now.
[1] https://issues.apache.org/jira/browse/IGNITE-3605
2017-11-21 2:47 GMT+03:00 Denis Magda :
> Ignite dev community,
>
> Bring thi
Hello Igniters!
When deserializing Externalizable cache entry it's impossible to use
ObjectInput#available method for checking is there anything left to
read in buffer. This is because OptimizedObjectInputStream#available
always returns -1 (hard-coded).
Does anyone know the reasons why this metho
Hello, Igniters.
I tried to implement IgniteSet data recovery when persistence enabled
[1] using trivial cache scanning, however I cannot find optimal way to
do that because of the following reasons:
- Performing operations on IgniteSet requires completion of data
loading (restoring of setDataMap)
Hello Igniters,
I want get to work on issue [1] (Split Cache 3 TC configuration).
Could you give me permissions on TeamCity for creating new configurations?
My TeamCity login: xtern.
[1] https://issues.apache.org/jira/browse/IGNITE-9148
t; Hi Pavel,
>>
>> I support idea of granting necessary permission, but I'm not sure which
>> role I should assign.
>>
>> So let's wait for experienced TC admins to grant it.
>>
>> Sincerely,
>> Dmitriy Pavlov
>>
>> вт, 31 июл.
Hello, Dmitriy.
Yes, these tests was previously muted in another test suite.
I re-muted them again.
2018-08-01 20:15 GMT+03:00 Dmitriy Pavlov :
> Hi Ed, Pavel,
>
> Do you know, why these test were failed were failed?
>
> Is it because of new suite?
>
> Sincerely,
> Dmitriy Pavlov
>
> ср, 1 авг. 2
Hello Igniters.
It seems that "idea/ignite_inspections.xml" should be excluded from
"check-licenses" maven profile, because "_Licenses Headers_"
configuration always fails now [1] on TeamCity.
[1]
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_LicensesHeaders&tab=build
Hello, Igniters.
I assigned ticket [1] created by Denis and want to clarify how to log
committed size.
The metric offHeapSize (in DataRegionMetricsImpl) is always
calculated, but getOffHeapSize returns zero if memory metrics are
disabled for this data region.
So I see the following options:
1. Mo
Hi, Igniters!
I’m working on IGNITE-6333 [1] and I need to add two new metrics into
CacheMetrics.
As I see, versioning is not supported for now.
Do I need to care about rolling upgrades?
[1] https://issues.apache.org/jira/browse/IGNITE-6333
Ignite.
>
> —
> Denis
>
>> On Dec 13, 2017, at 8:22 AM, Pavel Pereslegin wrote:
>>
>> Hi, Igniters!
>>
>> I’m working on IGNITE-6333 [1] and I need to add two new metrics into
>> CacheMetrics.
>> As I see, versioning is not supported for now.
>&
Hello, Igniters!
We have some issues with current IgniteSet implementation ([1], [2], [3], [4]).
As was already described in this conversation, the main problem is
that current IgniteSet implementation maintains plain Java sets on
every node (see CacheDataStructuresManager.setDataMap). These sets
like an idea of creating separate cache for each data structure,
> especially for collocated ones. Can actually, I'm not sure I understand how
> that would help. It sounds like that we just need to properly persist the
> data structures cache and then reload on restart.
>
> -Va
Hello, Igniters!
I agree that solution with separate caches is not acceptable for a
large number of sets.
So, I want to suggest one more way to implement IgniteSet that will
introduce element indexes (similar to IgniteQueue). To implement this
we can add head/tail indexes to IgniteSet header and
Hello Vladimir,
> What we can do is to optionally disable on-heap caching for specific set at
> the cost of lower performance if user wants so.
I want to make sure that we are speaking about the same thing. By
"on-heap caching" I mean custom datastructure and not standard on-heap
cache, we can't
Hello Igniters.
I'm working on the implementation of the IgniteCache#asSet method [1]
and I think it should return Set (not IgniteSet). Because IgniteSet
was introduced mainly to add methods for the collocated version of
IgniteSet.
Any thoughts?
[1] https://issues.apache.org/jira/browse/IGNITE-7
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 P
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,
>
Hello.
I suggest including this task [1] in the release.
It changes the jdbc client protocol. I hope that the review of the proposed
patch will be completed today.
[1] https://issues.apache.org/jira/browse/IGNITE-24053
вт, 21 янв. 2025 г. в 20:28, Pavel Tupitsyn :
> Following an in-person di
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-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-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-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-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-12349:
-
Summary: File transmission can cause the cluster to freeze.
Key: IGNITE-12349
URL: https://issues.apache.org/jira/browse/IGNITE-12349
Project: Ignite
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-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-12683:
-
Summary:
BPlusTreeReuseListPageMemoryImplTest.testIterateConcurrentPutRemove_2 fails
with timeout on TC
Key: IGNITE-12683
URL: https://issues.apache.org/jira/browse
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-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-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
1 - 100 of 138 matches
Mail list logo
