Access to Apache Ignite Wiki

Hi, igniters! Please grant me access to Ignite Wiki to help with editing and updating info. It is my JIRA account v.pyatkov -- Vladislav Pyatkov

Re: Access to Apache Ignite Wiki

t; > Regards, > -- > Ilya Kasnacheev > > > пн, 12 апр. 2021 г. в 11:44, Vladislav Pyatkov : > > > Hi, igniters! > > Please grant me access to Ignite Wiki to help with editing and updating > > info. > > It is my JIRA account v.pyatkov > > > > -- > > Vladislav Pyatkov > > > -- Vladislav Pyatkov

Re: [DISCUSSION] Error handling in Ignite 3

are async, they all will > have > > a > > > configurable default timeout and can complete with timeout error if a > > > computation is not finished in time, for example if a response has not > > been > > > yet received. > > > I suggest to complete the async op future with TimeoutException in this > > > case to make it on par with synchronous execution using future.get, > which > > > will throw java.util.concurrent.TimeoutException on timeout. > > > For reference, see java.util.concurrent.CompletableFuture#orTimeout > > > No special error code should be used for this scenario. > > > > > > *Internal exceptions hierarchy.* > > > > > > All internal exceptions should extend > > > org.apache.ignite.internal.lang.IgniteInternalException for checked > > > exceptions and > > > org.apache.ignite.internal.lang.IgniteInternalCheckedException for > > > unchecked exceptions. > > > > > > Thoughts ? > > > > > > [1] https://docs.oracle.com/cd/B10501_01/server.920/a96525/preface.htm > > > > > > -- > > > > > > Best regards, > > > Alexei Scherbakov > > > > > > > > > -- > > Best regards, > > Alexey > > > > > -- > > Best regards, > Alexei Scherbakov > -- Vladislav Pyatkov

Re: [VOTE] @Nullable/@NotNull annotation usage in Ignite 3

I am sure the shorter, the better. +1 to option 4. On Thu, Jan 13, 2022 at 2:06 PM ткаленко кирилл wrote: > +1 to option 2 > -- Vladislav Pyatkov

Re: [ANNOUNCE] SCOPE FREEZE for Apache Ignite 3.0.0 beta 1 RELEASE

a/browse/IGNITE-17813 - related to > >> >>>> support > >> >>>>>> indexes by SQL > >> >>>>>> https://issues.apache.org/jira/browse/IGNITE-17655 - related to > >> >>>> support > >> >>>>>> indexes by SQL > >> >>>>>> > >> >>>>>> ср, 19 окт. 2022 г. в 12:11, Вячеслав Коптилин < > >> >>>> slava.kopti...@gmail.com > >> >>>>>> : > >> >>>>>> > >> >>>>>>> Hello Alexander, > >> >>>>>>> > >> >>>>>>> Thank you for pointing this out. I fully support including RO > >> >>>>>> transactions > >> >>>>>>> into the scope of Ignite 3.0.0-beta1 release. > >> >>>>>>> > >> >>>>>>> Thanks, > >> >>>>>>> S. > >> >>>>>>> > >> >>>>>>> > >> >>>>>>> ср, 19 окт. 2022 г. в 11:42, Alexander Lapin < > lapin1...@gmail.com > >> >: > >> >>>>>>> > >> >>>>>>>> Igniters, > >> >>>>>>>> > >> >>>>>>>> I would like to add following tickets to ignite-3.0.0-beta1 > >> >>>>>>>> https://issues.apache.org/jira/browse/IGNITE-17806 > >> >>>>>>>> https://issues.apache.org/jira/browse/IGNITE-17759 > >> >>>>>>>> https://issues.apache.org/jira/browse/IGNITE-17637 > >> >>>>>>>> https://issues.apache.org/jira/browse/IGNITE-17263 > >> >>>>>>>> https://issues.apache.org/jira/browse/IGNITE-17260 > >> >>>>>>>> > >> >>>>>>>> It's all about read-only transactions. > >> >>>>>>>> > >> >>>>>>>> Best regards, > >> >>>>>>>> Alexander > >> >>>>>>>> > >> >>>>>>>> пт, 14 окт. 2022 г. в 19:45, Andrey Gura : > >> >>>>>>>> > >> >>>>>>>>> Igniters, > >> >>>>>>>>> > >> >>>>>>>>> The 'ignite-3.0.0-beta1' branch was created (the latest commit > >> is > >> >>>>>>>>> 8160ef31ecf8d49f227562b6f0ab090c6b4438c1). > >> >>>>>>>>> > >> >>>>>>>>> The scope for the release is frozen. > >> >>>>>>>>> > >> >>>>>>>>> It means the following: > >> >>>>>>>>> > >> >>>>>>>>> - Any issue could be added to the release (fixVersion == > >> >>>>> 3.0.0-beta1) > >> >>>>>>>>> only after discussion with the community and a release manager > >> in > >> >>>>>> this > >> >>>>>>>>> thread. > >> >>>>>>>>> - Any commit to the release branch must be also applied to the > >> >>>>> 'main' > >> >>>>>>>>> branch. > >> >>>>>>>>> > >> >>>>>>>> > >> >>>>>>> > >> >>>>>> > >> >>>>>> > >> >>>>>> -- > >> >>>>>> Живи с улыбкой! :D > >> >>>>>> > >> >>>>> > >> >>>> > >> >>>> > >> >>>> -- > >> >>>> Живи с улыбкой! :D > >> >>>> > >> >> > >> >> > >> > >> > -- Vladislav Pyatkov Architect-Consultant "GridGain Rus" Llc. +7-929-537-79-60

Re: [VOTE] Release Apache Ignite 3.0.0-beta1 RC2

g: > > > > > > https://repository.apache.org/content/repositories/orgapacheignite-1556/ > > > > Tag: https://github.com/apache/ignite-3/tree/3.0.0-beta1-rc2 > > > > > > > > +1 - accept Apache Ignite 3.0.0-beta1 RC2 > > > > 0 - don't care either way > > > > -1 - DO NOT accept Apache Ignite 3.0.0-beta1 RC2 (explain why) > > > > > > > > Voting guidelines: https://www.apache.org/foundation/voting.html > > > > How to verify the release: > > https://www.apache.org/info/verification.html > > > > > > > > The vote will be closed on Wednesday, 16 November 2022, 18:00:00 (UTC > > > time) > > > > > > > > > > > > > https://www.timeanddate.com/countdown/generic?iso=20221116T18&p0=1440&msg=Apache+Ignite+3.0.0-beta1+RC2&font=cursive&csz=1 > > > > > > > > Thanks, > > > > S. > > > > > > > > > -- Vladislav Pyatkov

Re: Discuss idle_verify with moving partitions changes.

f no objections would be here, i plan to inform about moving states as > not OK exit code too. > > -- Vladislav Pyatkov Architect-Consultant "GridGain Rus" Llc. +7-929-537-79-60

Various shutdown guaranties

down did not configure all be worked as before according to IMMEDIATE behavior. All other close method will be marked as deprecated. I will be waiting for your opinions. -- Vladislav Pyatkov

Choosing historical rebalance heuristics

]: https://issues.apache.org/jira/browse/IGNITE-13253 [2]: https://issues.apache.org/jira/browse/IGNITE-13254 -- Vladislav Pyatkov

Re: Choosing historical rebalance heuristics

to account. We > don't track skipped updates for atomic caches. As a result, detection of > the absence of updates between two checkpoint markers with the same > partition counter can be false positive. > > -- > Best Regards, > Ivan Rakov > > On Tue, Jul 14, 2020 at 3:03 PM

Re: Choosing historical rebalance heuristics

accepts a side of heuristics above. On Thu, Jul 16, 2020 at 12:09 AM Vladislav Pyatkov wrote: > Ivan, > > I agree with a combined approach: threshold for small partitions and count > of update for partition that outgrew it. > This helps to avoid partitions that update not frequent

Re: Update of the default inline size for variable types

AR, VARCHAR, > VARCHAR, > >VARCHAR, VARCHAR) default index size will be only 64. Same for the columns > >with defined length: by default VARCHAR(100) column will create index only > >with size equal to 64. > > > >Please tell if you have any concerns. Update can be found at > >https://github.com/apache/ignite/pull/8161 > > > >Best regards, > >Evgeniy > > > > > > -- Vladislav Pyatkov

Re: Exception handling in thin client: should we pass stack traces to the client?

gt;get sensitive information about server configuration, such as it's > > version, > > >version of the underlying database, frameworks etc.. This information > may > > >help attacker to apply some version-specific attacks. This is precise > > >reason why def

Re: [DISCUSSION] Maintenance Mode feature

> workflow in case of PDS corruption. > > >> > > > >> > 1. Node has failed in the middle of checkpoint when WAL is > disabled > > >> > for > > >> > a particular cache -> data files of the cache are potentially > > >> corrupted. > > >> > 2. On next startup node detects this situation, creates > Maintenance > > >> > Record on disk and shuts down. > > >> > 3. On next startup node sees Maintenance Record, enters > Maintenance > > >> Mode > > >> > and waits for user to do specific actions: clean potentially > > >> > corrupted > > >> PDS. > > >> > 4. When user has done necessary actions he/she removes Maintenance > > >> > Record using Maintenance Mode API exposed via control.{sh|bat} > > script > > >> or > > >> > JMX. > > >> > 5. On next startup node goes to normal operations as maintenance > > >> > reason > > >> > is fixed. > > >> > > > >> > > > >> > I prepared a PR [3] for ticket [1] with draft implementation. It is > > not > > >> > ready to be merged to master branch but is already fully functional > > and > > >> can > > >> > be reviewed. > > >> > > > >> > Hope you'll share your feedback on the feature and/or any thoughts > on > > >> > implementation. > > >> > > > >> > Thank you! > > >> > > > >> > [1] https://issues.apache.org/jira/browse/IGNITE-13366 > > >> > [2] > > >> > > > >> > > > https://cwiki.apache.org/confluence/display/IGNITE/IEP-47:+Native+persistence+defragmentation > > >> > [3] https://github.com/apache/ignite/pull/8189 > > >> > > >> > > > > > > > > > -- > > > > Best regards, > > Ivan Pavlukhin > > > -- Vladislav Pyatkov

Re: Re[2]: Apache Ignite 2.9.0 RELEASE [Time, Scope, Manager]

;> left, > >> >>>>>>>>>>>> it's close > >> >>>>>>>>>>>>>>>>> to measurement error and I think such a drop is not a > >> >>>>>>>>>>

Re: Re[2]: [DISCUSSION] Request for thread unsafe Compute functionality deprecation.

r {@code null} if not deployed. > > >>>> */ > > >>>> public DeploymentResource findResource(String rsrcName); > > >>>> is thread unsafe by default, no guarantee that concurrent call of > > >>>> localDeployTask and execute will bring expected result. > > >>>> My proposal is to deprecate (or probably annotate [2], as a minimal > > >>>> — additionally document it) this methods and to append additional : > > >>>> public DeploymentResource findResource(String rsrcName, ClassLoader > > >>>> clsLdr); > > >>>> Only one problem i can observe here, if someone creates new class > > loaders > > >>>> and appropriate class instances in loop (i don`t know the purpose) > and > > >>>> doesn`t undeploy them then he will get possibly OOM here. > > >>>> > > >>>> Such approach will give a possibility to use compute in concurrent > > >>>> scenario. If there is no objections here i will mark this methods > and > > >>>> publish my PR, of course with additional tests. > > >>>> > > >>>> What do you think ? > > >>>> > > >>>> > > >>>> [1] > > >>>> > > https://ignite.apache.org/docs/latest/code-deployment/peer-class-loading > > >>>> [2] > > >>>> > > https://jcip.net/annotations/doc/net/jcip/annotations/NotThreadSafe.html > > >>>> > > >>>> > > >> > > >> > > >> > > >> > -- Vladislav Pyatkov

Re: Running single test multiple times on TeamCity

we need such tool? (Or perhaps we already have something and > there is no need to reinvent the wheel.) > 2. What is the best way for us to implement the tool? > > [1] https://github.com/apache/ignite/pull/6076 > [2] https://wiki.jenkins.io/display/JENKINS/Parameterized+Build > > -- > Best regards, > Ivan Pavlukhin > -- Vladislav Pyatkov

Re: in-memory compression

page formats that we need to support. > 2) Once we release version 1.0, we would like TBLignite to be added to the > Ignite "3rd party binary" page. Who decides what gets on this page? > 3) And are there any acceptance criteria or tests that need to be passed? > > We would like to hear from you. > Pascal Schuchhard > TBLcore > > -- Vladislav Pyatkov

Please, review IGNITE-3994

Hi, IGNITE-3994 <https://issues.apache.org/jira/browse/IGNITE-3994> Client buffer CacheContinuousQueryEntry on pendingEvts after reconnect to alive cluster PR: http://195.239.208.174/project.html?projectId=IgniteTests&tab=projectOverview&branch_IgniteTests=pull/1496/head -- Vladislav Pyatkov

Re: IGNITE-4713 : refactoring of GridFinishedFuture and GridFutureAdapter

apter because resFlag can > have 3 values there. > > 2017-02-16 19:58 GMT+03:00 Александр Меньшиков : > > > Hello. > > > > I propose to do refactoring of classes "GridFinishedFuture" and > > "GridFutureAdapter". There is field "resFlag" which can eq

Re: CacheStore and Transaction

Hi Make sure are you using transactional cache. On Mar 19, 2017 10:32 PM, "Alisher Alimov" wrote: > Hello! > > I found bug when using CacheStore with Transaction or it’s expected > behaviour? > > Example: > > CacheConfiguration cacheConfiguration = new CacheConfiguration("test.no-op"); > cacheC

Re: CacheStore and Transaction

I mean *CacheConfiguration.setAtomicityMode*[1] Because transactions makes a sense only for TRANSACTIONAL cache. [1]: https://apacheignite.readme.io/docs/transactions#section-atomicity-mode On Sun, Mar 19, 2017 at 11:14 PM, Vladislav Pyatkov wrote: > Hi > > Make sure are

IGNITE-4022 IgniteServices soesn't throw an exception if there are no server nodes

Please, check my PA: https://issues.apache.org/jira/browse/IGNITE-4022 https://github.com/apache/ignite/pull/1728 I think, test is not need. Because the suggestion will not be affect o logic. But I want have listened someone's mind. -- Vladislav Pyatkov

Re: TouchedExpiryPolicy works incorrect in some cases IGNITE-4401

. So my question is the following: Is the ticket correct ? Should we > close it? > -- > > *Best Regards,* > > *Kuznetsov Aleksey* > -- Vladislav Pyatkov

Re: TouchedExpiryPolicy works incorrect in some cases IGNITE-4401

of this ticket? What is the correct behavior of > the policy? > > пн, 10 апр. 2017 г. в 17:45, Vladislav Pyatkov : > > > Aleksey, > > > > Yes, it's corect. > > Pay attention, in the example was used TouchedExpiryPolicy with 20 > seconds > > as pa

Re: TouchedExpiryPolicy works incorrect in some cases IGNITE-4401

> >>>>>> Do you have sample code? > >>>>>> > >>>>>> — > >>>>>> Denis > >>>>>>> On Apr 11, 2017, at 2:45 AM, ALEKSEY KUZNETSOV < > >>>>> alkuznetsov...@gmail.com <mailto:alkuznetsov...@gmail.com>> wrote: > >>>>>>> > >>>>>>> Hi, igniters! > >>>>>>> While doing https://issues.apache.org/jira/browse/IGNITE-4401 < > >>>>> https://issues.apache.org/jira/browse/IGNITE-4401> ticket i came > >>>>>>> across the fact that cache querying returns null , while cache > still > >>>>> has > >>>>>>> got entry. > >>>>>>> Cache query : SELECT nameProp FROM EDUProp WHERE EDUId = 1 > >>>>>>> Cache get operation : ignite().cache("eduPropCache").get(new > >>>>> AffinityKey("1", > >>>>>>> "1")) non-null > >>>>>>> I cannot even imagine what could be wrong with it. > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> -- > >>>>>>> > >>>>>>> *Best Regards,* > >>>>>>> > >>>>>>> *Kuznetsov Aleksey* > >>>>>> > >>>>>> -- > >>>>>> Best Regards, > >>>>>> > >>>>>> Kuznetsov Aleksey > >>>>>> > >>>>> > >>>>> -- > >>>>> > >>>>> *Best Regards,* > >>>>> > >>>>> *Kuznetsov Aleksey* > >>>>> > >>>> -- > >>>> > >>>> *Best Regards,* > >>>> > >>>> *Kuznetsov Aleksey* > >>> > >>> -- > >> > >> *Best Regards,* > >> > >> *Kuznetsov Aleksey* > >> > > -- > > > > *Best Regards,* > > > > *Kuznetsov Aleksey* > > -- Vladislav Pyatkov

By bytes access to binary format

Buffer.allocate(1024)); or with buffer BinaryObject.writeBytesToBuf("data", new byte[1000], 100); I already created a Jira ticket. https://issues.apache.org/jira/browse/IGNITE-5602 -- Vladislav Pyatkov Architect-Consultant "GridGain Rus" Llc. +7 963 716 68 99

Please review my PR 4968 (IGNITE-9738)

D.Govoruchin, I tried to correct all your comments and TC in correct state. Please, review my changes. -- Vladislav Pyatkov

Re: By bytes access to binary format

Wed, Jun 28, 2017 at 9:36 PM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Vladislav, > > Are you suggesting to stream directly from cache. or from a binary object > that is already copied from cache? > > -Val > > On Wed, Jun 28, 2017 at 2:52

Re: By bytes access to binary format

erstand the problem. Can you show how the API > > you > > > propose would look like? Remember that "field" method can return > anything > > > from primitive, String or byte array, to another BinaryObject. And > > returned > > > BinaryObject can have

Re: PRIMARY_SYNC+readFromBackup semantics

network message from primary node to > local backup, which doesn't make much sense to me and looks like > unnecessary performance overhead. > > Is it possible to update local backup synchronously in this scenario? > > -Val > -- Vladislav Pyatkov

Please review it IGNITE-6737

Hi, I have added PR for this issue: https://issues.apache.org/jira/browse/IGNITE-6737 and this fix passed in TC. This is serious issue witch can loop nodes from cluster. -- Vladislav Pyatkov

Re: Controlling type of object inserted in IgniteCache

Hi Ignite dev comunity, I an start to work on https://issues.apache.org/jira/browse/IGNITE-2909 The problem occurs when we add objects in cache in node where no information abut types (for example server node without end user classes in classpath). After reserch, I try to find way to solve issue.

Cache metrics return incorrect values

I try to understand how statistics work and fixe some problem. I first case: cache.put(46744, "val 46744"); cache.get(46744); In statistic I see: 2016-05-24 14:19:31 INFO ServerNode:78 - Swap put 0 get 0 (0, 0) entries count 0 2016-05-24 14:19:31 INFO ServerNode:81 - OffHeap put 1 get 0 (0, 0) en

Re: Cache metrics return incorrect values

rstanding you can increase this statistics > > exactly in this method - GridCacheSwapManager#readOffheapPointer. > > > > CacheMetrics.getOffHeapPuts - should be incremented every time a put > > operations happens and an entry is moved to off heap. > > > > — >

NonHeap memory usage metrics don't work as expected.

Igniters, I trying to solve https://issues.apache.org/jira/browse/IGNITE-2616 I see that the grid output statistics we use MemoryMXBean (GridDiscoveryManager.java:150) and it does not take what we expect. We have own implementation for manipulationg with offheap memory: GridUnsafeMemory which stor

Re: Maven conflicts within ignite-core from duplicated classes

Why not just rename these classes? On Thu, Jun 16, 2016 at 11:16 AM, Semyon Boikov wrote: > As far as I know the only reason sources of Nullable are in Ignite - we > did not want to have any dependecy for 'core' module. > > On Mon, Jun 13, 2016 at 10:04 AM, Denis Magda wrote: > >> Hi Pete, >> >

Re: Change rest-http Java to JSON null transformation logic

Hello, Why do you want this, if you can save full compatibility using custom serializer for null value (ObjectMapper#setSerializerProvider)? On Thu, Jun 16, 2016 at 12:15 PM, Alexey Kuznetsov wrote: > Hi All! > > I'm working on migrating from outdated json-lib to Jackson issue > IGNITE-3277 [1]

IGNITE-3055

Igniters, I have implemented timeout in DataStreamer by issue IGNITE-3055 (*IgniteDataStreamer can't be timed out*). That lead the change public API: 1) Added set and get methods (IgniteDataStreamer.timeout(long) and IgniteDataStreamer.timeout()

Re: IGNITE-3055

on, Jul 11, 2016 at 1:14 PM, Vladislav Pyatkov > wrote: > > > Igniters, > > > > I have implemented timeout in DataStreamer by issue IGNITE-3055 > > <https://issues.apache.org/jira/browse/IGNITE-3055>(*IgniteDataStreamer > > can't be timed out*). >

Re: IGNITE-3055

s look OK. However, I am not sure about > TimeoutException. Don’t we already have other timeout exceptions in Ignite? > Can we reuse them? > > D. > > On Tue, Jul 12, 2016 at 1:51 PM, Vladislav Pyatkov > wrote: > > > Dmitriy, > > > > I have added the description of

IGNITE-3138 IgniteDataStreamer: failures are not shown on the streaming side

IGNITE-3138 Patch available Please review and let me know if any changes required.

IGNITE-3601 Read-only optimistic transaction shouldn't throw an exception if entry version was not changed.

Hi, I prepared PR[1] for read only transaction. [1]: https://github.com/apache/ignite/pull/1001

Re: Cache consistency

Hi Alisher, At first I assume the discussion need to be moved to user-forum ( u...@ignite.apache.org). If you have 2 backups (in case you have enough nodes) this mean you can loose 2 node, without afraid to loose data. In case you have a fail more than the 2 nodes, it is mean you have incomplete(

Re: Hello

Hi Alex, This is Apache Ignite development community. Are you want to contribute to Ignite or you are have any suggestion? On Wed, Nov 23, 2016 at 12:41 PM, Александр Меньшиков wrote: > Hello >

Re: Hello

Please read https://ignite.apache.org/community/contribute.html#contribute Looking forward for your contributions! On Wed, Nov 23, 2016 at 1:15 PM, Александр Меньшиков wrote: > I want to contribute. > > 2016-11-23 13:04 GMT+03:00 Vladislav Pyatkov : > > > Hi Alex, > > &

Hello all in Ignite dev comunity

My name is Vlad. I am from Moskow, Russia and not be native speaker Englesh. I am newest GridGain developer and going to contribute Apache Ignite project. Want to sart with this bug https://issues.apache.org/jira/browse/IGNITE-2394 and try to get it the nerest.

[jira] [Created] (IGNITE-14185) Synchronous checkpoints on several nodes greatly increase a latency of distributed transaction

Vladislav Pyatkov created IGNITE-14185: -- Summary: Synchronous checkpoints on several nodes greatly increase a latency of distributed transaction Key: IGNITE-14185 URL: https://issues.apache.org/jira/browse

[jira] [Created] (IGNITE-14419) SPI suite hangs sporadically on private TC

Vladislav Pyatkov created IGNITE-14419: -- Summary: SPI suite hangs sporadically on private TC Key: IGNITE-14419 URL: https://issues.apache.org/jira/browse/IGNITE-14419 Project: Ignite

[jira] [Created] (IGNITE-14476) Get rid of using storage implementation explicitly in ConfigurationRoot annotation

Vladislav Pyatkov created IGNITE-14476: -- Summary: Get rid of using storage implementation explicitly in ConfigurationRoot annotation Key: IGNITE-14476 URL: https://issues.apache.org/jira/browse/IGNITE-14476

[jira] [Created] (IGNITE-12290) Re-balance fully restart for case when WAL disabled

Vladislav Pyatkov created IGNITE-12290: -- Summary: Re-balance fully restart for case when WAL disabled Key: IGNITE-12290 URL: https://issues.apache.org/jira/browse/IGNITE-12290 Project: Ignite

[jira] [Created] (IGNITE-12522) Extend test coverage [IGNITE-12104] Check deployment from cache before to load it from local or version storage

Vladislav Pyatkov created IGNITE-12522: -- Summary: Extend test coverage [IGNITE-12104] Check deployment from cache before to load it from local or version storage Key: IGNITE-12522 URL: https

[jira] [Created] (IGNITE-12671) Update of partition's states can stuck when rebalance completed during exchange

Vladislav Pyatkov created IGNITE-12671: -- Summary: Update of partition's states can stuck when rebalance completed during exchange Key: IGNITE-12671 URL: https://issues.apache.org/jira/browse/IGNITE-

[jira] [Created] (IGNITE-12689) Partitions should become owned after a checkpoint, regardless of a topology change. Nevertheless a rebalance is not required.

Vladislav Pyatkov created IGNITE-12689: -- Summary: Partitions should become owned after a checkpoint, regardless of a topology change. Nevertheless a rebalance is not required. Key: IGNITE-12689 URL: https

[jira] [Created] (IGNITE-12780) Deadlock between db-checkpoint-thread and checkpoint-runner

Vladislav Pyatkov created IGNITE-12780: -- Summary: Deadlock between db-checkpoint-thread and checkpoint-runner Key: IGNITE-12780 URL: https://issues.apache.org/jira/browse/IGNITE-12780 Project

[jira] [Created] (IGNITE-12818) SoLinger is not set for reader-sockets in discovery

Vladislav Pyatkov created IGNITE-12818: -- Summary: SoLinger is not set for reader-sockets in discovery Key: IGNITE-12818 URL: https://issues.apache.org/jira/browse/IGNITE-12818 Project: Ignite

[jira] [Created] (IGNITE-12935) Disadvantages in log of historical rebalance

Vladislav Pyatkov created IGNITE-12935: -- Summary: Disadvantages in log of historical rebalance Key: IGNITE-12935 URL: https://issues.apache.org/jira/browse/IGNITE-12935 Project: Ignite

[jira] [Created] (IGNITE-13072) Synchronization problems when different classloaders are used for deployment of same class

Vladislav Pyatkov created IGNITE-13072: -- Summary: Synchronization problems when different classloaders are used for deployment of same class Key: IGNITE-13072 URL: https://issues.apache.org/jira/browse

[jira] [Created] (IGNITE-13168) Retrigger historical rebalance if it was cancelled in case WAL history is still available

Vladislav Pyatkov created IGNITE-13168: -- Summary: Retrigger historical rebalance if it was cancelled in case WAL history is still available Key: IGNITE-13168 URL: https://issues.apache.org/jira/browse/IGNITE

[jira] [Created] (IGNITE-13191) Public-facing API for "waiting for backups on shutdown"

Vladislav Pyatkov created IGNITE-13191: -- Summary: Public-facing API for "waiting for backups on shutdown" Key: IGNITE-13191 URL: https://issues.apache.org/jira/browse/IGNITE-13191 Proje

[jira] [Created] (IGNITE-13245) Rebalance future might hangs in no final state though all partitions are owned

Vladislav Pyatkov created IGNITE-13245: -- Summary: Rebalance future might hangs in no final state though all partitions are owned Key: IGNITE-13245 URL: https://issues.apache.org/jira/browse/IGNITE-13245

[jira] [Created] (IGNITE-13253) Advanced heuristics for historical rebalance

Vladislav Pyatkov created IGNITE-13253: -- Summary: Advanced heuristics for historical rebalance Key: IGNITE-13253 URL: https://issues.apache.org/jira/browse/IGNITE-13253 Project: Ignite

[jira] [Created] (IGNITE-13254) Historical rebalance iterator may skip checkpoint if it not contains updates

Vladislav Pyatkov created IGNITE-13254: -- Summary: Historical rebalance iterator may skip checkpoint if it not contains updates Key: IGNITE-13254 URL: https://issues.apache.org/jira/browse/IGNITE-13254

[jira] [Created] (IGNITE-13265) Historical iterator for atomic group should transfer few more rows than required

Vladislav Pyatkov created IGNITE-13265: -- Summary: Historical iterator for atomic group should transfer few more rows than required Key: IGNITE-13265 URL: https://issues.apache.org/jira/browse/IGNITE-13265

[jira] [Created] (IGNITE-13377) WalModeChangeAdvancedSelfTest.testServerRestartNonCoordinator

Vladislav Pyatkov created IGNITE-13377: -- Summary: WalModeChangeAdvancedSelfTest.testServerRestartNonCoordinator Key: IGNITE-13377 URL: https://issues.apache.org/jira/browse/IGNITE-13377 Project

[jira] [Created] (IGNITE-13379) Exception occur on SQL caches when client reconnect

Vladislav Pyatkov created IGNITE-13379: -- Summary: Exception occur on SQL caches when client reconnect Key: IGNITE-13379 URL: https://issues.apache.org/jira/browse/IGNITE-13379 Project: Ignite

[jira] [Created] (IGNITE-13402) [Suite] PDS 3 flaky failed on TC

Vladislav Pyatkov created IGNITE-13402: -- Summary: [Suite] PDS 3 flaky failed on TC Key: IGNITE-13402 URL: https://issues.apache.org/jira/browse/IGNITE-13402 Project: Ignite Issue Type

[jira] [Created] (IGNITE-13417) Cache Interceptors deserialization on client nodes

Vladislav Pyatkov created IGNITE-13417: -- Summary: Cache Interceptors deserialization on client nodes Key: IGNITE-13417 URL: https://issues.apache.org/jira/browse/IGNITE-13417 Project: Ignite

[jira] [Created] (IGNITE-13501) AssertionError: Invalid value in testMergeServersFail1_8

Vladislav Pyatkov created IGNITE-13501: -- Summary: AssertionError: Invalid value in testMergeServersFail1_8 Key: IGNITE-13501 URL: https://issues.apache.org/jira/browse/IGNITE-13501 Project

[jira] [Created] (IGNITE-13593) IgniteClientCacheStartFailoverTest.testRebalanceStateConcurrentStart (Cache 2) is flaky

Vladislav Pyatkov created IGNITE-13593: -- Summary: IgniteClientCacheStartFailoverTest.testRebalanceStateConcurrentStart (Cache 2) is flaky Key: IGNITE-13593 URL: https://issues.apache.org/jira/browse/IGNITE

[jira] [Created] (IGNITE-13594) Model classes require manual deserialization if used inside Job loaded by p2p

Vladislav Pyatkov created IGNITE-13594: -- Summary: Model classes require manual deserialization if used inside Job loaded by p2p Key: IGNITE-13594 URL: https://issues.apache.org/jira/browse/IGNITE-13594

[jira] [Created] (IGNITE-13864) Assertion error happens on stale latch's acknowledge

Vladislav Pyatkov created IGNITE-13864: -- Summary: Assertion error happens on stale latch's acknowledge Key: IGNITE-13864 URL: https://issues.apache.org/jira/browse/IGNITE-13864 Project: I

[jira] [Created] (IGNITE-13866) Validate index does not stop after process of control.sh was interrupted

Vladislav Pyatkov created IGNITE-13866: -- Summary: Validate index does not stop after process of control.sh was interrupted Key: IGNITE-13866 URL: https://issues.apache.org/jira/browse/IGNITE-13866

[jira] [Created] (IGNITE-13977) Code enhancement after review of encryption persistent storage

Vladislav Pyatkov created IGNITE-13977: -- Summary: Code enhancement after review of encryption persistent storage Key: IGNITE-13977 URL: https://issues.apache.org/jira/browse/IGNITE-13977 Project

[jira] [Created] (IGNITE-14073) False alarm to lose all transaction nodes

Vladislav Pyatkov created IGNITE-14073: -- Summary: False alarm to lose all transaction nodes Key: IGNITE-14073 URL: https://issues.apache.org/jira/browse/IGNITE-14073 Project: Ignite

[jira] [Created] (IGNITE-14138) Historical rebalance kills cluster

Vladislav Pyatkov created IGNITE-14138: -- Summary: Historical rebalance kills cluster Key: IGNITE-14138 URL: https://issues.apache.org/jira/browse/IGNITE-14138 Project: Ignite Issue Type

[jira] [Created] (IGNITE-14139) Incorrect initialize checkpoint-runner-cpu thread pool

Vladislav Pyatkov created IGNITE-14139: -- Summary: Incorrect initialize checkpoint-runner-cpu thread pool Key: IGNITE-14139 URL: https://issues.apache.org/jira/browse/IGNITE-14139 Project: Ignite

[jira] [Created] (IGNITE-14140) Checkpointer thread holds write lock too long

Vladislav Pyatkov created IGNITE-14140: -- Summary: Checkpointer thread holds write lock too long Key: IGNITE-14140 URL: https://issues.apache.org/jira/browse/IGNITE-14140 Project: Ignite

[jira] [Created] (IGNITE-10933) Node may hang on join to topology and not move forward

Vladislav Pyatkov created IGNITE-10933: -- Summary: Node may hang on join to topology and not move forward Key: IGNITE-10933 URL: https://issues.apache.org/jira/browse/IGNITE-10933 Project: Ignite

[jira] [Created] (IGNITE-11023) Processing data bag on GridMarshallerMappingProcessor consume many time

Vladislav Pyatkov created IGNITE-11023: -- Summary: Processing data bag on GridMarshallerMappingProcessor consume many time Key: IGNITE-11023 URL: https://issues.apache.org/jira/browse/IGNITE-11023

[jira] [Created] (IGNITE-11120) Remove static fields from GridDhtLockFuture

Vladislav Pyatkov created IGNITE-11120: -- Summary: Remove static fields from GridDhtLockFuture Key: IGNITE-11120 URL: https://issues.apache.org/jira/browse/IGNITE-11120 Project: Ignite

[jira] [Created] (IGNITE-11262) Compression on Discovery data bag

Vladislav Pyatkov created IGNITE-11262: -- Summary: Compression on Discovery data bag Key: IGNITE-11262 URL: https://issues.apache.org/jira/browse/IGNITE-11262 Project: Ignite Issue Type

[jira] [Created] (IGNITE-11269) Optimize node join to topology

Vladislav Pyatkov created IGNITE-11269: -- Summary: Optimize node join to topology Key: IGNITE-11269 URL: https://issues.apache.org/jira/browse/IGNITE-11269 Project: Ignite Issue Type

[jira] [Created] (IGNITE-11270) Batch join to topology

Vladislav Pyatkov created IGNITE-11270: -- Summary: Batch join to topology Key: IGNITE-11270 URL: https://issues.apache.org/jira/browse/IGNITE-11270 Project: Ignite Issue Type

[jira] [Created] (IGNITE-11291) Assertion error in time of rebalance completion lead to to critical failure node

Vladislav Pyatkov created IGNITE-11291: -- Summary: Assertion error in time of rebalance completion lead to to critical failure node Key: IGNITE-11291 URL: https://issues.apache.org/jira/browse/IGNITE-11291

[jira] [Created] (IGNITE-11425) Log information about inaccessible nodes through Communication

Vladislav Pyatkov created IGNITE-11425: -- Summary: Log information about inaccessible nodes through Communication Key: IGNITE-11425 URL: https://issues.apache.org/jira/browse/IGNITE-11425 Project

[jira] [Created] (IGNITE-11474) Add possibility to run idle_verify in not idle cluster

Vladislav Pyatkov created IGNITE-11474: -- Summary: Add possibility to run idle_verify in not idle cluster Key: IGNITE-11474 URL: https://issues.apache.org/jira/browse/IGNITE-11474 Project: Ignite

[jira] [Created] (IGNITE-11643) Optimize GC pressure on GridDhtPartitionTopologyImpl#updateRebalanceVersion

Vladislav Pyatkov created IGNITE-11643: -- Summary: Optimize GC pressure on GridDhtPartitionTopologyImpl#updateRebalanceVersion Key: IGNITE-11643 URL: https://issues.apache.org/jira/browse/IGNITE-11643

[jira] [Created] (IGNITE-11698) Issue with P2P class loader

Vladislav Pyatkov created IGNITE-11698: -- Summary: Issue with P2P class loader Key: IGNITE-11698 URL: https://issues.apache.org/jira/browse/IGNITE-11698 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-11734) IgniteCache.replace(k, v, nv) requires classes when element is null or old value - null

Vladislav Pyatkov created IGNITE-11734: -- Summary: IgniteCache.replace(k, v, nv) requires classes when element is null or old value - null Key: IGNITE-11734 URL: https://issues.apache.org/jira/browse/IGNITE

[jira] [Created] (IGNITE-11763) GridP2PComputeWithNestedEntryProcessorTest failed on TC

Vladislav Pyatkov created IGNITE-11763: -- Summary: GridP2PComputeWithNestedEntryProcessorTest failed on TC Key: IGNITE-11763 URL: https://issues.apache.org/jira/browse/IGNITE-11763 Project: Ignite

[jira] [Created] (IGNITE-11834) Confusing message on rebalance

Vladislav Pyatkov created IGNITE-11834: -- Summary: Confusing message on rebalance Key: IGNITE-11834 URL: https://issues.apache.org/jira/browse/IGNITE-11834 Project: Ignite Issue Type

[jira] [Created] (IGNITE-11844) Should to filtered indexes by cache name instead of validate all caches in group

Vladislav Pyatkov created IGNITE-11844: -- Summary: Should to filtered indexes by cache name instead of validate all caches in group Key: IGNITE-11844 URL: https://issues.apache.org/jira/browse/IGNITE-11844

[jira] [Created] (IGNITE-12104) Check deployment from cache before to load it from local or version storage

Vladislav Pyatkov created IGNITE-12104: -- Summary: Check deployment from cache before to load it from local or version storage Key: IGNITE-12104 URL: https://issues.apache.org/jira/browse/IGNITE-12104

[jira] [Created] (IGNITE-12203) Rebalance is loading partitions already loading after cancellation without WAL

Vladislav Pyatkov created IGNITE-12203: -- Summary: Rebalance is loading partitions already loading after cancellation without WAL Key: IGNITE-12203 URL: https://issues.apache.org/jira/browse/IGNITE-12203

[jira] [Created] (IGNITE-4579) Cluster ceased to process transaction, after massive operations of cache on compute task

Vladislav Pyatkov created IGNITE-4579: - Summary: Cluster ceased to process transaction, after massive operations of cache on compute task Key: IGNITE-4579 URL: https://issues.apache.org/jira/browse/IGNITE

[jira] [Created] (IGNITE-4747) Memory leak on massive cache operations over atomic cache

Vladislav Pyatkov created IGNITE-4747: - Summary: Memory leak on massive cache operations over atomic cache Key: IGNITE-4747 URL: https://issues.apache.org/jira/browse/IGNITE-4747 Project: Ignite

[jira] [Created] (IGNITE-4882) Sometime network request will be produce when cache entry is locked

Vladislav Pyatkov created IGNITE-4882: - Summary: Sometime network request will be produce when cache entry is locked Key: IGNITE-4882 URL: https://issues.apache.org/jira/browse/IGNITE-4882

[jira] [Created] (IGNITE-5340) AssertionError in index name check

Vladislav Pyatkov created IGNITE-5340: - Summary: AssertionError in index name check Key: IGNITE-5340 URL: https://issues.apache.org/jira/browse/IGNITE-5340 Project: Ignite Issue Type

[jira] [Created] (IGNITE-5417) Implement JSON marshaller through BinaryObject in ignite-rest-http

Vladislav Pyatkov created IGNITE-5417: - Summary: Implement JSON marshaller through BinaryObject in ignite-rest-http Key: IGNITE-5417 URL: https://issues.apache.org/jira/browse/IGNITE-5417

  1   2   >