Re: [ANNOUNCE] New committer: Vyacheslav Koptilin

My congratulations, Slava! On Tue, Feb 18, 2020 at 11:33 PM Andrey Kuznetsov wrote: > Congratulations, Slava! > > вт, 18 февр. 2020 г. в 22:20, Dmitriy Pavlov : > > > Hello Ignite Community, > > > > The Project Management Committee (PMC) for Apache Ignite has invited > > Vyacheslav Koptilin to

Re: [VOTE] Allow or prohibit a joint use of @deprecated and @IgniteExperimental

-1 Prohibit On Mon, Feb 10, 2020 at 12:58 PM Pavel Tupitsyn wrote: > -1 Prohibit > > On Mon, Feb 10, 2020 at 12:41 PM Zhenya Stanilovsky > wrote: > > > > > -1, sounds confusing, i wan`t use deprecated API > > and @IgniteExperimental it`s something unknown with undefined «time for > > support».

Re: [VOTE] Apache Ignite PMC Chair

+1 for Dmitry Pavlov сб, 2 нояб. 2019 г., 0:26 Alexey Goncharuk : > +1 for Alexey Goncharuk (binding) > > пн, 28 окт. 2019 г. в 21:06, Denis Magda : > > > Ignite community, > > > > Please cast a vote for one of the following candidates: > > > >- Alexey Goncharuk > >- Dmitry Pavlov > >

Re: Re[2]: Apache Ignite 2.7.6 (Time, Scope, and Release manager)

Hi Igniters, I finished work on https://issues.apache.org/jira/browse/IGNITE-12127, fix already in master and ignite-2.7.6 On Wed, Sep 4, 2019 at 2:22 PM Dmitriy Govorukhin < dmitriy.govoruk...@gmail.com> wrote: > Hi Alexey, > > I think that I will finish work on the fix tomorr

Re: Re[2]: Apache Ignite 2.7.6 (Time, Scope, and Release manager)

Hi Alexey, I think that I will finish work on the fix tomorrow. Fix already completed but I need to get VISA from TC bot. On Mon, Sep 2, 2019 at 8:27 PM Alexey Goncharuk wrote: > Folks, it looks like I was overly optimistic with the estimates for the > mentioned two tickets. > > Dmitriy,

[jira] [Created] (IGNITE-12128) Potentially pds corruption on a failed node during checkpoint

Dmitriy Govorukhin created IGNITE-12128: --- Summary: Potentially pds corruption on a failed node during checkpoint Key: IGNITE-12128 URL: https://issues.apache.org/jira/browse/IGNITE-12128

[jira] [Created] (IGNITE-12127) WAL writer may close file IO with unflushed changes when MMAP is disabled

Dmitriy Govorukhin created IGNITE-12127: --- Summary: WAL writer may close file IO with unflushed changes when MMAP is disabled Key: IGNITE-12127 URL: https://issues.apache.org/jira/browse/IGNITE-12127

[jira] [Created] (IGNITE-12110) Bugs & tests fixes

Dmitriy Govorukhin created IGNITE-12110: --- Summary: Bugs & tests fixes Key: IGNITE-12110 URL: https://issues.apache.org/jira/browse/IGNITE-12110 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-12102) idle_verify should show info about lost partitions

Dmitriy Govorukhin created IGNITE-12102: --- Summary: idle_verify should show info about lost partitions Key: IGNITE-12102 URL: https://issues.apache.org/jira/browse/IGNITE-12102 Project: Ignite

[jira] [Created] (IGNITE-12081) Page replacement can reload invalid page during checkpoint

Dmitriy Govorukhin created IGNITE-12081: --- Summary: Page replacement can reload invalid page during checkpoint Key: IGNITE-12081 URL: https://issues.apache.org/jira/browse/IGNITE-12081 Project

Re: Apache Ignite 2.7.6 (Time, Scope, and Release manager)

Hi all, Can we include https://issues.apache.org/jira/browse/IGNITE-12060? This is a https://issues.apache.org/jira/browse/IGNITE-11953 On Fri, Aug 9, 2019 at 10:04 AM Nikolay Izhikov wrote: > Hello, Deni. > > > Nickolay, could you check if that's a quick upgrade? > > Yes, I will take a look. >

[jira] [Created] (IGNITE-12060) Incorrect row size calculation, lead to tree corruption.

Dmitriy Govorukhin created IGNITE-12060: --- Summary: Incorrect row size calculation, lead to tree corruption. Key: IGNITE-12060 URL: https://issues.apache.org/jira/browse/IGNITE-12060 Project

[jira] [Created] (IGNITE-12057) Persistence files are stored to temp dir

Dmitriy Govorukhin created IGNITE-12057: --- Summary: Persistence files are stored to temp dir Key: IGNITE-12057 URL: https://issues.apache.org/jira/browse/IGNITE-12057 Project: Ignite

[jira] [Created] (IGNITE-12048) Bugs & tests fixes

Dmitriy Govorukhin created IGNITE-12048: --- Summary: Bugs & tests fixes Key: IGNITE-12048 URL: https://issues.apache.org/jira/browse/IGNITE-12048 Project: Ignite Issue Type:

Re: Link to Grid Gain internal ticket in Ignite

Nikolay, my fault, already fixed. https://issues.apache.org/jira/browse/IGNITE-11998 On Thu, Jul 18, 2019 at 4:06 PM Nikolay Izhikov wrote: > Hello, Igniters. > > Dmitriy, can you, please, create an Ignite Jira ticket from your internal? > [1] > Or change link to existing Ignite ticket. > >

[jira] [Created] (IGNITE-11953) BTree corruption caused by byte array values

Dmitriy Govorukhin created IGNITE-11953: --- Summary: BTree corruption caused by byte array values Key: IGNITE-11953 URL: https://issues.apache.org/jira/browse/IGNITE-11953 Project: Ignite

[jira] [Created] (IGNITE-11934) Bugs & tests fixes

Dmitriy Govorukhin created IGNITE-11934: --- Summary: Bugs & tests fixes Key: IGNITE-11934 URL: https://issues.apache.org/jira/browse/IGNITE-11934 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-11835) Support JMX/control.sh API for page lock dump

Dmitriy Govorukhin created IGNITE-11835: --- Summary: Support JMX/control.sh API for page lock dump Key: IGNITE-11835 URL: https://issues.apache.org/jira/browse/IGNITE-11835 Project: Ignite

[jira] [Created] (IGNITE-11824) Integrate PageLockTracker to DataStructure (per-thread tracker)

Dmitriy Govorukhin created IGNITE-11824: --- Summary: Integrate PageLockTracker to DataStructure (per-thread tracker) Key: IGNITE-11824 URL: https://issues.apache.org/jira/browse/IGNITE-11824

[jira] [Created] (IGNITE-11786) Implement thread-local stack for trucking page locks

Dmitriy Govorukhin created IGNITE-11786: --- Summary: Implement thread-local stack for trucking page locks Key: IGNITE-11786 URL: https://issues.apache.org/jira/browse/IGNITE-11786 Project: Ignite

[jira] [Created] (IGNITE-11738) Incorrect check ObjectInput.available() in CacheMetricsSnapshot

Dmitriy Govorukhin created IGNITE-11738: --- Summary: Incorrect check ObjectInput.available() in CacheMetricsSnapshot Key: IGNITE-11738 URL: https://issues.apache.org/jira/browse/IGNITE-11738

[jira] [Created] (IGNITE-11641) Server node copies a lot of WAL files in WAL archive after restart

Dmitriy Govorukhin created IGNITE-11641: --- Summary: Server node copies a lot of WAL files in WAL archive after restart Key: IGNITE-11641 URL: https://issues.apache.org/jira/browse/IGNITE-11641

[jira] [Created] (IGNITE-11509) Remove DistributedBaselineConfiguration and replace to methods on IgniteCluster

Dmitriy Govorukhin created IGNITE-11509: --- Summary: Remove DistributedBaselineConfiguration and replace to methods on IgniteCluster Key: IGNITE-11509 URL: https://issues.apache.org/jira/browse/IGNITE-11509

Re: [DISCUSSION] Usage of system properties in tests

++1 from my side. I guess it will be a more reliable way for works with properties in the tests. From time to time somebody forgot clear property after test and next tests may be failed or flaky failed completion. On Thu, Feb 14, 2019 at 6:56 PM Dmitriy Pavlov wrote: > I find it absolutely

[jira] [Created] (IGNITE-11095) Failed WalCompactionTest flaky test

Dmitriy Govorukhin created IGNITE-11095: --- Summary: Failed WalCompactionTest flaky test Key: IGNITE-11095 URL: https://issues.apache.org/jira/browse/IGNITE-11095 Project: Ignite Issue

[jira] [Created] (IGNITE-10974) Grid may hangs if an exception is thrown from PageMemoryImpl.beforeReleaseWrite()

Dmitriy Govorukhin created IGNITE-10974: --- Summary: Grid may hangs if an exception is thrown from PageMemoryImpl.beforeReleaseWrite() Key: IGNITE-10974 URL: https://issues.apache.org/jira/browse/IGNITE-10974

[jira] [Created] (IGNITE-10909) GridCacheBalancingStoreSelfTest.testConcurrentLoad flaky test fail in Cache 1

Dmitriy Govorukhin created IGNITE-10909: --- Summary: GridCacheBalancingStoreSelfTest.testConcurrentLoad flaky test fail in Cache 1 Key: IGNITE-10909 URL: https://issues.apache.org/jira/browse/IGNITE-10909

[jira] [Created] (IGNITE-10908) GridServiceProcessorBatchDeploySelfTest.testDeployAllTopologyChange flaky fail with NPE in Service Grid (legacy mode)

Dmitriy Govorukhin created IGNITE-10908: --- Summary: GridServiceProcessorBatchDeploySelfTest.testDeployAllTopologyChange flaky fail with NPE in Service Grid (legacy mode) Key: IGNITE-10908 URL: https

[jira] [Created] (IGNITE-10907) IgniteUtilsSelfTest.testDoInParallelWithStealingJobRunTaskInExecutor flaky failed in Basic 1

Dmitriy Govorukhin created IGNITE-10907: --- Summary: IgniteUtilsSelfTest.testDoInParallelWithStealingJobRunTaskInExecutor flaky failed in Basic 1 Key: IGNITE-10907 URL: https://issues.apache.org/jira/browse

[jira] [Created] (IGNITE-10891) IgnitePdsThreadInterruptionTest.testInterruptsOnLFSRead flaky in PDS indexing

Dmitriy Govorukhin created IGNITE-10891: --- Summary: IgnitePdsThreadInterruptionTest.testInterruptsOnLFSRead flaky in PDS indexing Key: IGNITE-10891 URL: https://issues.apache.org/jira/browse/IGNITE-10891

[jira] [Created] (IGNITE-10883) IgniteRebalanceOnCachesStoppingOrDestroyingTest flaky failed in PDS4

Dmitriy Govorukhin created IGNITE-10883: --- Summary: IgniteRebalanceOnCachesStoppingOrDestroyingTest flaky failed in PDS4 Key: IGNITE-10883 URL: https://issues.apache.org/jira/browse/IGNITE-10883

[jira] [Created] (IGNITE-10508) Need to support the new checkpoint feature not wait for the previous operation to complete

Dmitriy Govorukhin created IGNITE-10508: --- Summary: Need to support the new checkpoint feature not wait for the previous operation to complete Key: IGNITE-10508 URL: https://issues.apache.org/jira/browse

Re: [VOTE] Creation dedicated list for github notifiacations

+1 вт, 27 нояб. 2018 г., 19:41 Denis Mekhanikov dmekhani...@gmail.com: > +1 > I'm for making the dev list readable without filters of any kind. > > On Tue, Nov 27, 2018, 15:14 Maxim Muzafarov > > +1 > > > > Let's have a look at how it will be. > > > > On Tue, 27 Nov 2018 at 14:48 Seliverstov

[jira] [Created] (IGNITE-10341) Missed loss policy tests with persistence

Dmitriy Govorukhin created IGNITE-10341: --- Summary: Missed loss policy tests with persistence Key: IGNITE-10341 URL: https://issues.apache.org/jira/browse/IGNITE-10341 Project: Ignite

[jira] [Created] (IGNITE-10290) Map.Entry interface for key cache may lead to incorrect calculation hash code

Dmitriy Govorukhin created IGNITE-10290: --- Summary: Map.Entry interface for key cache may lead to incorrect calculation hash code Key: IGNITE-10290 URL: https://issues.apache.org/jira/browse/IGNITE-10290

[jira] [Created] (IGNITE-10285) U.doInParallel may lead to deadlock

Dmitriy Govorukhin created IGNITE-10285: --- Summary: U.doInParallel may lead to deadlock Key: IGNITE-10285 URL: https://issues.apache.org/jira/browse/IGNITE-10285 Project: Ignite Issue

[jira] [Created] (IGNITE-10252) Cache.get() may be mapped to the node with partition state is "MOVING"

Dmitriy Govorukhin created IGNITE-10252: --- Summary: Cache.get() may be mapped to the node with partition state is "MOVING" Key: IGNITE-10252 URL: https://issues.apache.org/jira/browse/IG

[jira] [Created] (IGNITE-10207) Missed loss policy checks

Dmitriy Govorukhin created IGNITE-10207: --- Summary: Missed loss policy checks Key: IGNITE-10207 URL: https://issues.apache.org/jira/browse/IGNITE-10207 Project: Ignite Issue Type: Bug

Re: Apache Ignite 2.7. Last Mile

gt; > > > > > > > > > > Nikolay, > > > > > > > > > > > > > > > > > > > > > > > > > > It completely breaks a major feature under certain > > > > > > > > > > conditions. >

[jira] [Created] (IGNITE-9898) Checkpointer thread hangs on await async task complete

Dmitriy Govorukhin created IGNITE-9898: -- Summary: Checkpointer thread hangs on await async task complete Key: IGNITE-9898 URL: https://issues.apache.org/jira/browse/IGNITE-9898 Project: Ignite

Re: jira issue filling rules

Vyacheslav, Thanks for links, I just wanted to remind these rules for all. Not all Igniters use these rules in work. On Mon, Oct 8, 2018 at 12:17 PM Vyacheslav Daradur wrote: > Hi Igniters, > > Dmitriy Govorukhin, the naming of GitHub PR [1] and Upsource review > [2] alrea

jira issue filling rules

Hi folks, Recently time ago, I noticed that many Jira issues created and filled in different ways, so someone does not fill issue description, someone does not attach links in the links section instead, add links to comments and etc. I want to star discussion regards to Jira issue filling rules.

Re: New PMC member: Dmitriy Pavlov

Dmitriy, My congratulations! Thank you for your work! On Thu, Aug 30, 2018 at 1:58 PM Maxim Muzafarov wrote: > Dmitry, > > My congratulations! > Thank you for guiding and helping the community members and me, in > particular, > to follow the Apache Way principles and also for your

[jira] [Created] (IGNITE-9426) IgniteAtomicSequence benchmarks

Dmitriy Govorukhin created IGNITE-9426: -- Summary: IgniteAtomicSequence benchmarks Key: IGNITE-9426 URL: https://issues.apache.org/jira/browse/IGNITE-9426 Project: Ignite Issue Type: Bug

Re: StandaloneWalRecordsIterator: support iteration from custom pointer

Ivan, I implemented this issue, please review my changes. https://reviews.ignite.apache.org/ignite/review/IGNT-CR-729 On Thu, Aug 16, 2018 at 3:09 PM Ivan Rakov wrote: > Thanks for your comments! > I've created a ticket: https://issues.apache.org/jira/browse/IGNITE-9294 > > Best Regards, >

[jira] [Created] (IGNITE-9260) StandaloneWalRecordsIterator broken on WalSegmentTailReachedException not in work dir

Dmitriy Govorukhin created IGNITE-9260: -- Summary: StandaloneWalRecordsIterator broken on WalSegmentTailReachedException not in work dir Key: IGNITE-9260 URL: https://issues.apache.org/jira/browse/IGNITE-9260

[jira] [Created] (IGNITE-9244) Partition eviction may use all threads in sys pool, it leads to hangs send a message via sys pool

Dmitriy Govorukhin created IGNITE-9244: -- Summary: Partition eviction may use all threads in sys pool, it leads to hangs send a message via sys pool Key: IGNITE-9244 URL: https://issues.apache.org/jira

Re: async operation is not fair async

Folks, Any comments? I will start to implement withFairAsync(); decorator soon. On Wed, Aug 1, 2018 at 12:22 PM Dmitriy Pavlov wrote: > Igniters, > > I've re-read this thread in brief. As far as I know this change is not > coming from some company, so this change will be at least good for

Re: Quick questions on B+ Trees and Partitions

Hi John, 1. B + tree in a partition is a primary key index, this means that we use a B+ tree index for searching data in the partition. 2. Not fully understood a question, please explain more details. 3. It depends how many partitions do you have for these caches, by default it 1024 per cache, in

Need review IGNITE-9050

Igniters, I completed work on IGNITE-9050 (WALIterator should throw an exception if iterator stopped in the WAL archive but not in WAL work). review link - CR-697

[jira] [Created] (IGNITE-9050) WALIterator should throws exception if iterator stopped in the WALArchive but not in WALWork

Dmitriy Govorukhin created IGNITE-9050: -- Summary: WALIterator should throws exception if iterator stopped in the WALArchive but not in WALWork Key: IGNITE-9050 URL: https://issues.apache.org/jira/browse

[jira] [Created] (IGNITE-9049) Missed SWITCH_SEGMENT_RECORD at the end of WAL file but space enough

Dmitriy Govorukhin created IGNITE-9049: -- Summary: Missed SWITCH_SEGMENT_RECORD at the end of WAL file but space enough Key: IGNITE-9049 URL: https://issues.apache.org/jira/browse/IGNITE-9049

[jira] [Created] (IGNITE-9047) Add idleVerify check for GridCommonAbstractTest

Dmitriy Govorukhin created IGNITE-9047: -- Summary: Add idleVerify check for GridCommonAbstractTest Key: IGNITE-9047 URL: https://issues.apache.org/jira/browse/IGNITE-9047 Project: Ignite

[jira] [Created] (IGNITE-9042) Transaction with small timeout may lead to inconsistent partition state

Dmitriy Govorukhin created IGNITE-9042: -- Summary: Transaction with small timeout may lead to inconsistent partition state Key: IGNITE-9042 URL: https://issues.apache.org/jira/browse/IGNITE-9042

Re: data extractor

hes to upload to, etc. > > сб, 30 июн. 2018 г. в 22:38, Dmitriy Govorukhin < > dmitriy.govoruk...@gmail.com>: > > > Igniters, > > > > I am working on IGNITE-7644 > > <https://issues.apache.org/jira/browse/IGNITE-7644> (export all > key-value >

[jira] [Created] (IGNITE-8973) Need to support dump for idle_verify

Dmitriy Govorukhin created IGNITE-8973: -- Summary: Need to support dump for idle_verify Key: IGNITE-8973 URL: https://issues.apache.org/jira/browse/IGNITE-8973 Project: Ignite Issue

[jira] [Created] (IGNITE-8929) WAL should not disable for the group if none a partition is not assigned to a local node.

Dmitriy Govorukhin created IGNITE-8929: -- Summary: WAL should not disable for the group if none a partition is not assigned to a local node. Key: IGNITE-8929 URL: https://issues.apache.org/jira/browse/IGNITE

Re: data extractor

ake a look. > > ticket - https://issues.apache.org/jira/browse/IGNITE-8485 > prototype - https://github.com/apache/ignite/pull/4167 > spi - > https://github.com/apache/ignite/pull/4167/files#diff-9a792ab0e6971f202d22d530af0ac933 > > В Сб, 30/06/2018 в 22:37 +0300, Dmitriy Govorukhin пишет: > &

data extractor

Igniters, I am working on IGNITE-7644 (export all key-value data from a persisted partition), it will be command line tool for extracting data from Ignite partition file without the need to start node. The main motivation is to have a lifebuoy

Re: Introduce a sample of activation policy when cluster is activated first time

Vladimir, Auto-activation on the first start? Please, shared an issue link if you have. On Tue, Jun 26, 2018 at 11:29 AM Vladimir Ozerov wrote: > Pavel, > > As far as I know we agreed to implement auto activation in one of the > nearest releases. Am I missing something? > > вт, 26 июня 2018 г.

Re: unused or only used in tests methonds

Igniters, If no one objects, then I delete these methods in next refactoring task. On Fri, Jun 15, 2018 at 6:38 PM Alexey Goncharuk wrote: > I have no objections to remove these methods. > > --AG > > чт, 14 июн. 2018 г. в 17:39, Dmitriy Govorukhin < > dmitriy

Re: Review request for IGNITE-8740: Support reuse of already initialized Ignite in IgniteSpringBean

Valentin, Seems that these changes have classes without license head. TC link

[jira] [Created] (IGNITE-8827) Disable WAL during apply updates on recovery

Dmitriy Govorukhin created IGNITE-8827: -- Summary: Disable WAL during apply updates on recovery Key: IGNITE-8827 URL: https://issues.apache.org/jira/browse/IGNITE-8827 Project: Ignite

Re: Need review IGNITE-8661

! Very important fix to a very bad problem in the > product > > that could cause data consistency issue. > > > > Will it be included into 2.6, or will we have to wait for 2.7? > > > > D. > > > > On Thu, Jun 14, 2018 at 6:53 AM, Dmitriy Govorukhin &

unused or only used in tests methonds

Igniters, I found 2 methods, 1. PageStore.pageOffset(long pageId) - it unused, seem that old artifact. 2. IgnitePageStoreManager.pagesAllocated(int grpId) - used only in test, seem that same problem can be solved with IgnitePageStoreManager.pages(grpId, partId). I suggest, remove these methods

Re: Atomic cache inconsistent state

Denis, Seem that you right, it is a problem. I guess in this case primary node should send CachePartialUpdateException to near node. On Tue, Jun 5, 2018 at 6:13 PM, Denis Garus wrote: > Fix formatting > > Hello Igniters! > > I have found some confusing behavior of atomic partitioned cache with

[jira] [Created] (IGNITE-8707) DataStorageMetrics.getTotalAllocatedSize metric does not account reserved partition page header.

Dmitriy Govorukhin created IGNITE-8707: -- Summary: DataStorageMetrics.getTotalAllocatedSize metric does not account reserved partition page header. Key: IGNITE-8707 URL: https://issues.apache.org/jira/browse

IGNITE-8685 review request

Igniters, I prepared a rather important patch [1] related to WAL. In the current implementation, we calculation incorrect size for SEGMENT_SWITCH record, it leads to stopping the iteration at the end of a segment and iterator do not advance to the next segment. [1]

[jira] [Created] (IGNITE-8685) Incorrect size for switch segment record

Dmitriy Govorukhin created IGNITE-8685: -- Summary: Incorrect size for switch segment record Key: IGNITE-8685 URL: https://issues.apache.org/jira/browse/IGNITE-8685 Project: Ignite Issue

Re: WAL iterator unexpected behavior

. > > On Sun, Jun 3, 2018, 12:11 Dmitriy Govorukhin < > dmitriy.govoruk...@gmail.com> > wrote: > > > Dmitriy, > > > > The iterator will be stopped. and method "it.next()" will throw the > > exception. > > > > On Sat, Jun 2, 2018 at 4

Re: WAL iterator unexpected behavior

Dmitriy, The iterator will be stopped. and method "it.next()" will throw the exception. On Sat, Jun 2, 2018 at 4:27 PM, Dmitriy Setrakyan wrote: > Dmitriy, what happens in case of unknown exceptions? > > > On Thu, May 31, 2018 at 6:35 AM, Dmitriy Govorukhin < >

Re: Issues with forceServerMode on clients and unclear contract of isClient/isClientMode methods

Eduard, Sounds reasonable, agree with you. On Thu, May 31, 2018 at 5:10 PM, Eduard Shangareev < eduard.shangar...@gmail.com> wrote: > Hi, guys! > > I just have found that we widely > misuse org.apache.ignite.cluster.ClusterNode#isClient method. > > Now it returns how a node is connected to

Re: WAL iterator unexpected behavior

bility skip records by type or some pointer for the StandaloneWalRecordsIterator Comments are welcome. On Thu, May 31, 2018 at 12:53 AM, Dmitriy Setrakyan wrote: > On Wed, May 30, 2018 at 8:04 AM, Dmitriy Govorukhin < > dmitriy.govoruk...@gmail.com> wrote: > > > Dmitriy, >

[jira] [Created] (IGNITE-8661) WALItreater is not stopped if can not deserialize record

Dmitriy Govorukhin created IGNITE-8661: -- Summary: WALItreater is not stopped if can not deserialize record Key: IGNITE-8661 URL: https://issues.apache.org/jira/browse/IGNITE-8661 Project: Ignite

Re: WAL iterator unexpected behavior

t; different. I do not think it is OK to skip records during normal operation. > In my view, we should report an error and stop. However, when offline, it > is OK to report an error and continue in my view. > > D. > > On Wed, May 30, 2018 at 5:39 AM, Dmitriy Govorukhin < >

Re: WAL iterator unexpected behavior

Yakov, This problem is not for offline only, it applicable for all types of the iterators. In general, iterator does not know which class will be needed for deserialization. I guess we can expand WAL Iterator factory and provide a method for creating the iterator with some filter, which will

[jira] [Created] (IGNITE-8607) [.NET] Support metrics changes in DataStorageMetricsMXBean

Dmitriy Govorukhin created IGNITE-8607: -- Summary: [.NET] Support metrics changes in DataStorageMetricsMXBean Key: IGNITE-8607 URL: https://issues.apache.org/jira/browse/IGNITE-8607 Project

Re: Baseline topology documentation clarified: usage scenarios and definition

+1 for a webinar, I would like to see it. On Wed, May 23, 2018 at 5:34 PM, Dmitry Pavlov wrote: > Hi Ivan, > > Would you like to run presentation based on this slides for Igniters? > > We can set up webinar using gotomeeting if you like this idea. > > Sincerely, > Dmitriy

IGNITE-8583 - review needed

Igniters, I fixed DataStorageMetricsMXBean.getOffHeapSize, please review my changes. https://issues.apache.org/jira/browse/IGNITE-8583

Re: async operation is not fair async

(or whether we should delay this change to 3.0 at all). > > 2018-05-15 22:13 GMT+03:00 Dmitriy Govorukhin < > dmitriy.govoruk...@gmail.com> > : > > > Alexey, > > > > Any updates? > > > > On Mon, May 14, 2018 at 6:19 PM, Dmitriy Govorukhin < > >

[jira] [Created] (IGNITE-8583) DataStorageMetricsMXBean.getOffHeapSize include checkpoint buffer size, this is not clear

Dmitriy Govorukhin created IGNITE-8583: -- Summary: DataStorageMetricsMXBean.getOffHeapSize include checkpoint buffer size, this is not clear Key: IGNITE-8583 URL: https://issues.apache.org/jira/browse/IGNITE

Re: work with files and directories

d other components using > files. > > ср, 16 мая 2018 г. в 11:27, Dmitriy Govorukhin < > dmitriy.govoruk...@gmail.com > >: > > > Andrey, > > > > My point is, it will be very cool if there is some component who will > know > > about persistence

Re: Avoid JIRA comments deletion

+1 Dmitriy, I do not see any reason for deletion comments. Maybe only edit operation must be allowed. On Wed, May 16, 2018 at 12:32 PM, Igor Sapego wrote: > I totally agree. There is no sense in most cases in deletion > of commentaries. > > There is even less sense, when

Re: work with files and directories

> > https://sonarcloud.io/component_measures?id=org. > > apache.ignite%3Aapache-ignite=duplicated_blocks& > > selected=org.apache.ignite%3Aignite-core%3Asrc%2Fmain% > > 2Fjava%2Forg%2Fapache%2Fignite%2Finternal%2Fprocessors%2Fcache% > > 2Fpersistence%2Fwal%2FFsyncModeFileW

Re: supporting different configuration format json,yaml...

configuration > > > > > > > > > > > >> and Spring approach in general. > > > > > > > > > > > >> > > > > > > > > > > > >> What will change is a XML formatting is goi

Re: async operation is not fair async

Alexey, Any updates? On Mon, May 14, 2018 at 6:19 PM, Dmitriy Govorukhin < dmitriy.govoruk...@gmail.com> wrote: > Alexey, > > Could you please add more description information for this task? [1] > Perhaps, base steps for implementation. > > [1] https://issues.apache.org

work with files and directories

Hi Ignite, Do we have a general approach to work with a file and directories? I see many duplication logic for write through .tmp file. For example, GridCacheDatabaseSharedManager.writeCheckpointEntry(); GridCacheDatabaseSharedManage.nodeStart();

Re: IGNITE-6430 (Done) CacheGroupsMetricsRebalanceTest.testRebalanceEstimateFinishTime test fails periodically

Dmitriy, Looks good for me please merge. On Tue, May 15, 2018 at 11:20 AM, Dmitriy Govorukhin < dmitriy.govoruk...@gmail.com> wrote: > Dmitriy, > > Ok, I will do it soon. > > On Mon, May 14, 2018 at 8:41 PM, Dmitry Pavlov <dpavlov@gmail.com> > wrote: >

Re: supporting different configuration format json,yaml...

n via XML Schema. We can surely hack this > around > > (I > > > bet there are existing libraries for configuring Spring with JSON), > but I > > > don't think that anyone suffered from inability to statically configure > > > Ignite with json/yaml. > > > >

Re: IGNITE-6430 (Done) CacheGroupsMetricsRebalanceTest.testRebalanceEstimateFinishTime test fails periodically

Dmitriy, Ok, I will do it soon. On Mon, May 14, 2018 at 8:41 PM, Dmitry Pavlov wrote: > Hi Dmitriy G, > > could you please pick up this review? > > Sincerely, > Dmitriy Pavlov > > чт, 10 мая 2018 г. в 15:50, Александр Меньшиков : > >> Hi, >> >> I

Re: async operation is not fair async

the operation chain > inside a transaction. I see absolutely no point in maintaining this chain > outside of transactions. > > --AG > > 2018-05-14 16:01 GMT+03:00 Dmitriy Govorukhin < > dmitriy.govoruk...@gmail.com> > : > > > Andrey, > > > >

Re: async operation is not fair async

And as a next step I would think on > >> adopting async cache and SQL APIs. > >> > >> Vladimir. > >> > >> [1] > >> http://www.oracle.com/technetwork/database/ > application-development/jdbc/ > >> con1491-3961036.pdf > >> [2] http

Re: async operation is not fair async

Dmitriy S, If it will be in the internal package, and only for internal usage, are you agree with changes? пт, 11 мая 2018 г., 21:12 Dmitriy Setrakyan <dsetrak...@apache.org>: > On Fri, May 11, 2018 at 6:49 PM, Dmitriy Govorukhin < > dmitriy.govoruk...@gmail.com> wrot

Re: async operation is not fair async

Dmitriy S, It is not broke existing code, because for use this ability you must use decorator "withFairSycn()". What about the argument of Vladimir? On Fri, May 11, 2018 at 8:41 PM, Dmitriy Setrakyan <dsetrak...@apache.org> wrote: > On Fri, May 11, 2018 at 6:38 PM,

Re: async operation is not fair async

Dmitriy S, Why method named as "async" but does not work as async? This is misleading. getAllAsync() is a special case. Not always you can use getAllAsync() instead of multiple getAsync(). In this topic, I wanna discuss problem not only for the GET operation but also all async operation behavior

Re: async operation is not fair async

an Rakov > > > On 11.05.2018 18:30, Dmitriy Govorukhin wrote: > >> Ivan, >> >> My suggestion "withFairAsync()". What do you think? >> >> On Fri, May 11, 2018 at 6:23 PM, Ivan Rakov <ivan.glu...@gmail.com> >> wrote: >> >> I

[jira] [Created] (IGNITE-8475) Create new IgniteCache decorator with fair async methonds

Dmitriy Govorukhin created IGNITE-8475: -- Summary: Create new IgniteCache decorator with fair async methonds Key: IGNITE-8475 URL: https://issues.apache.org/jira/browse/IGNITE-8475 Project: Ignite

Re: async operation is not fair async

olicy and so on. > > Best Regards, > Ivan Rakov > > > On 11.05.2018 18:18, Dmitriy Govorukhin wrote: > >> Vladimir, >> >> Should we create the new cache adapter or rework GridCacheAdapter? >> >> On Fri, May 11, 2018 at 5:52 PM, Vladimir Ozerov

Re: async operation is not fair async

roblem - deadlocks. We need to inform user > that this mode should be used with great care. > > On Fri, May 11, 2018 at 5:21 PM, Dmitriy Govorukhin < > dmitriy.govoruk...@gmail.com> wrote: > > > Hi Igniters, > > > > I have a question. Why our async operation

Re: Disable WAL for several cache groups within one exchange

Ivan, Agree, if we have the batch method for cache create, we should have the ability to enable/disable WAL in the batch too. On Fri, May 11, 2018 at 5:17 PM, Ivan Rakov wrote: > Igniters, > > API method for disabling WAL in IgniteCluster accepts only one cache name. >

  1   2   >