async operation is not fair async

Hi Igniters, I have a question. Why our async operation in not really async? GridCacheAdapter.syncOp has awaitLastFut(); this call wait last async operation completed. This means all async operation in one thread will be executed one by one but not in parallel. Async operation is not async.

[jira] [Created] (IGNITE-8464) WALItreater broken (race on the switch to the next segment during iteration and concurrent archiving same segment)

Dmitriy Govorukhin created IGNITE-8464: -- Summary: WALItreater broken (race on the switch to the next segment during iteration and concurrent archiving same segment) Key: IGNITE-8464 URL: https

Re: method arguments code style

looks very bad. My proposal was to allow two styles - first when all > arguments are on the same line splitted by 120 char limit, second when all > every arguments is on a separate line. > Mixed style should be disallowed. > > On Mon, May 7, 2018 at 12:35 AM, Dmitriy Govorukhin < &

Re: method arguments code style

uidelines, however, I think we should > allow > > > the old style when the method signature (without throws clause) fits > the > > > line. > > > > > > Thoughts? > > > > > > 2018-05-03 12:09 GMT+03:00 Dmitry Pavlov <dpavlov@gmai

method arguments code style

Hi folks, I read https://cwiki.apache.org/confluence/display/IGNITE/Coding+Guidelines, but did not find anything about code style for method arguments. In many places in the code, I see different code style, this creates difficulties for reading. It seems to me an example below is rather

Re: Orphaned, duplicate, and main-class tests!

Ilya, I guess we can remove all these suites GridActivationAtomicCacheSuit GridActivationCacheAbstractTestSuit GridActivationLocalAndNearCacheSuit GridActivationPartitionedCacheSuit GridActivationReplicatedCacheSuit They became not relevant after standby mode became part of the basic

[jira] [Created] (IGNITE-8346) FileDownloaderTest is not included in the test suite

Dmitriy Govorukhin created IGNITE-8346: -- Summary: FileDownloaderTest is not included in the test suite Key: IGNITE-8346 URL: https://issues.apache.org/jira/browse/IGNITE-8346 Project: Ignite

[jira] [Created] (IGNITE-8341) .NET: Add new metrics for data storage

Dmitriy Govorukhin created IGNITE-8341: -- Summary: .NET: Add new metrics for data storage Key: IGNITE-8341 URL: https://issues.apache.org/jira/browse/IGNITE-8341 Project: Ignite Issue

[jira] [Created] (IGNITE-8340) .NET Implement new JMX metrics for transactions

Dmitriy Govorukhin created IGNITE-8340: -- Summary: .NET Implement new JMX metrics for transactions Key: IGNITE-8340 URL: https://issues.apache.org/jira/browse/IGNITE-8340 Project: Ignite

Re: Memory usage per cache

Folks, I created 2 Jira issue for new metrics. Also, I think they will be useful. Let's discuss in comments. - Add new metrics for data storage IGNITE-8078 - Implement new JMX metrics for transactions IGNITE-8077

[jira] [Created] (IGNITE-8078) Add new metrics for data storage

Dmitriy Govorukhin created IGNITE-8078: -- Summary: Add new metrics for data storage Key: IGNITE-8078 URL: https://issues.apache.org/jira/browse/IGNITE-8078 Project: Ignite Issue Type

[jira] [Created] (IGNITE-8077) Implement new JMX metrics for transactions

Dmitriy Govorukhin created IGNITE-8077: -- Summary: Implement new JMX metrics for transactions Key: IGNITE-8077 URL: https://issues.apache.org/jira/browse/IGNITE-8077 Project: Ignite

Re: Stop nodes after test by default - IGNITE-6842

Looks good for me, please merge. 19 мар. 2018 г. 3:22 ПП пользователь "Dmitry Pavlov" написал: > I agree it is important, I'm going to do a review, but do not have time > slot to do. > > Who could pick up this review? > > Dmitriy G., could I ask you? > > пн, 19 мар. 2018

[jira] [Created] (IGNITE-7933) The error writing wal point to cp/node-start file can lead to the inability to start node

Dmitriy Govorukhin created IGNITE-7933: -- Summary: The error writing wal point to cp/node-start file can lead to the inability to start node Key: IGNITE-7933 URL: https://issues.apache.org/jira/browse/IGNITE

Thin client: transactions support

Hi, Igniters. I've seen a lot of discussions about thin client and binary protocol, but I did not hear anything about transactions support. Do we have some draft for this purpose? As I understand we have several problems: - thread and transaction have hard related (we use thread-local

Re: Code inspection

8:15 +, Dmitry Pavlov пишет: > > Hi Dmitriy, > > > > I think we should resurrect thread about addition of code inspections, > and > > later we can enable automatic control step to TeamCity. > > > > Could you help me to find it? > > > > вт, 6 мар. 2

Code inspection

Hi folks, Do we have 'inspection' [1] scheme for ignite? I see a lot of warnings in my code, and I guess it is because everyone uses different schemes. Let's start the discussion. [1] IDEA inspection

[jira] [Created] (IGNITE-7865) Need to provide method WAL manager for return serialize version

Dmitriy Govorukhin created IGNITE-7865: -- Summary: Need to provide method WAL manager for return serialize version Key: IGNITE-7865 URL: https://issues.apache.org/jira/browse/IGNITE-7865 Project

[jira] [Created] (IGNITE-7755) Potentially crash during write cp-***-start.bin can lead to the impossibility of recovering

Dmitriy Govorukhin created IGNITE-7755: -- Summary: Potentially crash during write cp-***-start.bin can lead to the impossibility of recovering Key: IGNITE-7755 URL: https://issues.apache.org/jira/browse

[jira] [Created] (IGNITE-7747) WAL manage getAndReserveWalFiles should not throw exception if segments not found

Dmitriy Govorukhin created IGNITE-7747: -- Summary: WAL manage getAndReserveWalFiles should not throw exception if segments not found Key: IGNITE-7747 URL: https://issues.apache.org/jira/browse/IGNITE-7747

Re: Plugins in tests

Yakov, Agree, I created the issue for this. I will try to do it in the near future. IGNITE-7679 On Tue, Jan 30, 2018 at 8:40 AM, Yakov Zhdanov wrote: > Guys, > > When running tests from core module I see that Ignite

[jira] [Created] (IGNITE-7679) Move all test plugins to a separate module

Dmitriy Govorukhin created IGNITE-7679: -- Summary: Move all test plugins to a separate module Key: IGNITE-7679 URL: https://issues.apache.org/jira/browse/IGNITE-7679 Project: Ignite

[jira] [Created] (IGNITE-6857) Multi stage start cache

Dmitriy Govorukhin created IGNITE-6857: -- Summary: Multi stage start cache Key: IGNITE-6857 URL: https://issues.apache.org/jira/browse/IGNITE-6857 Project: Ignite Issue Type: Improvement

[jira] [Created] (IGNITE-6547) Need to support ability log timestamp for wal tx and data records

Dmitriy Govorukhin created IGNITE-6547: -- Summary: Need to support ability log timestamp for wal tx and data records Key: IGNITE-6547 URL: https://issues.apache.org/jira/browse/IGNITE-6547

[jira] [Created] (IGNITE-6513) Add ability manage version for WAL serializer via system properties

Dmitriy Govorukhin created IGNITE-6513: -- Summary: Add ability manage version for WAL serializer via system properties Key: IGNITE-6513 URL: https://issues.apache.org/jira/browse/IGNITE-6513

[jira] [Created] (IGNITE-6493) IgnitePdsWalTlbTest.testWalDirectOutOfMemory() hangs

Dmitriy Govorukhin created IGNITE-6493: -- Summary: IgnitePdsWalTlbTest.testWalDirectOutOfMemory() hangs Key: IGNITE-6493 URL: https://issues.apache.org/jira/browse/IGNITE-6493 Project: Ignite

[jira] [Created] (IGNITE-6480) Incorrect server node filter in GridDiscoveryManager

Dmitriy Govorukhin created IGNITE-6480: -- Summary: Incorrect server node filter in GridDiscoveryManager Key: IGNITE-6480 URL: https://issues.apache.org/jira/browse/IGNITE-6480 Project: Ignite

[jira] [Created] (IGNITE-6439) IgnitePersistentStoreSchemaLoadTest is broken

Dmitriy Govorukhin created IGNITE-6439: -- Summary: IgnitePersistentStoreSchemaLoadTest is broken Key: IGNITE-6439 URL: https://issues.apache.org/jira/browse/IGNITE-6439 Project: Ignite

[jira] [Created] (IGNITE-6307) If getAll() fails with NPE, onHeap entry is not removed, for local cache

Dmitriy Govorukhin created IGNITE-6307: -- Summary: If getAll() fails with NPE, onHeap entry is not removed, for local cache Key: IGNITE-6307 URL: https://issues.apache.org/jira/browse/IGNITE-6307

[jira] [Created] (IGNITE-6210) inefficient memory consumption for checkpoint buffer

Dmitriy Govorukhin created IGNITE-6210: -- Summary: inefficient memory consumption for checkpoint buffer Key: IGNITE-6210 URL: https://issues.apache.org/jira/browse/IGNITE-6210 Project: Ignite

[jira] [Created] (IGNITE-6179) Test fail DynamicIndexReplicatedAtomicConcurrentSelfTest.testClientReconnectWithCacheRestart

Dmitriy Govorukhin created IGNITE-6179: -- Summary: Test fail DynamicIndexReplicatedAtomicConcurrentSelfTest.testClientReconnectWithCacheRestart Key: IGNITE-6179 URL: https://issues.apache.org/jira/browse

[jira] [Created] (IGNITE-6154) Incorrect check checkpoint pages collection

Dmitriy Govorukhin created IGNITE-6154: -- Summary: Incorrect check checkpoint pages collection Key: IGNITE-6154 URL: https://issues.apache.org/jira/browse/IGNITE-6154 Project: Ignite

[jira] [Created] (IGNITE-6100) Test fail IgnitePdsRecoveryAfterFileCorruptionTest.testPageRecoveryAfterFileCorruption

Dmitriy Govorukhin created IGNITE-6100: -- Summary: Test fail IgnitePdsRecoveryAfterFileCorruptionTest.testPageRecoveryAfterFileCorruption Key: IGNITE-6100 URL: https://issues.apache.org/jira/browse/IGNITE

[jira] [Created] (IGNITE-6098) Test fail IgniteDataIntegrityTests.testExpandBuffer

Dmitriy Govorukhin created IGNITE-6098: -- Summary: Test fail IgniteDataIntegrityTests.testExpandBuffer Key: IGNITE-6098 URL: https://issues.apache.org/jira/browse/IGNITE-6098 Project: Ignite

[jira] [Created] (IGNITE-6091) Test fail CacheLateAffinityAssignmentTest.testRandomOperations

Dmitriy Govorukhin created IGNITE-6091: -- Summary: Test fail CacheLateAffinityAssignmentTest.testRandomOperations Key: IGNITE-6091 URL: https://issues.apache.org/jira/browse/IGNITE-6091 Project

[jira] [Created] (IGNITE-6082) Test fail DynamicIndexPartitionedTransactionalConcurrentSelfTest.testConcurrentPutRemove

Dmitriy Govorukhin created IGNITE-6082: -- Summary: Test fail DynamicIndexPartitionedTransactionalConcurrentSelfTest.testConcurrentPutRemove Key: IGNITE-6082 URL: https://issues.apache.org/jira/browse/IGNITE

[jira] [Created] (IGNITE-6074) Test fail IgniteWalRecoveryTest#testWalBigObjectNodeCancel

Dmitriy Govorukhin created IGNITE-6074: -- Summary: Test fail IgniteWalRecoveryTest#testWalBigObjectNodeCancel Key: IGNITE-6074 URL: https://issues.apache.org/jira/browse/IGNITE-6074 Project

Re: Control.sh script and cluster activation

er results in a long stack trace... > >instead, it should provide a standard error message, suggesting > possible > >reasons for it. > > > > 4. Whenever trying to connect to a cluster, the script should print out a > message "Connecting to ip-address:port

[jira] [Created] (IGNITE-6064) Rework control.sh script.

Dmitriy Govorukhin created IGNITE-6064: -- Summary: Rework control.sh script. Key: IGNITE-6064 URL: https://issues.apache.org/jira/browse/IGNITE-6064 Project: Ignite Issue Type

Re: Control.sh script and cluster activation

Valentin, We have jira issue for this IGNITE-5586 <https://issues.apache.org/jira/browse/IGNITE-5586> On Tue, Aug 15, 2017 at 10:56 AM, Dmitriy Govorukhin < dmitriy.govoruk...@gmail.com> wrote: > > Denis, > > 1. control.sh have help parameter. If you try enter ./con

Re: Control.sh script and cluster activation

Denis, 1. control.sh have help parameter. If you try enter ./control.sh --help, result is an example of how to use it, "Example: --host {ip} --port {port} --{activate/deactivate} or without command --host {ip} --port {port} then will print status" 2. Visorcmd will start daemon node and join in

[jira] [Created] (IGNITE-6058) Test fail testTransformResourceInjection broken

Dmitriy Govorukhin created IGNITE-6058: -- Summary: Test fail testTransformResourceInjection broken Key: IGNITE-6058 URL: https://issues.apache.org/jira/browse/IGNITE-6058 Project: Ignite

[jira] [Created] (IGNITE-6052) Check cluster state from daemon node return incorrect cluster state

Dmitriy Govorukhin created IGNITE-6052: -- Summary: Check cluster state from daemon node return incorrect cluster state Key: IGNITE-6052 URL: https://issues.apache.org/jira/browse/IGNITE-6052

[jira] [Created] (IGNITE-6015) Test fail in Ignite Cache 2: GridCachePartitionedGetAndTransformStoreSelfTest.testGetAndTransform

Dmitriy Govorukhin created IGNITE-6015: -- Summary: Test fail in Ignite Cache 2: GridCachePartitionedGetAndTransformStoreSelfTest.testGetAndTransform Key: IGNITE-6015 URL: https://issues.apache.org/jira

[jira] [Created] (IGNITE-5968) Test fail in Ignite Cache 2: GridCachePartitionNotLoadedEventSelfTest.testPrimaryAndBackupDead

Dmitriy Govorukhin created IGNITE-5968: -- Summary: Test fail in Ignite Cache 2: GridCachePartitionNotLoadedEventSelfTest.testPrimaryAndBackupDead Key: IGNITE-5968 URL: https://issues.apache.org/jira/browse

[jira] [Created] (IGNITE-5967) Flaky fail in Ignite Java Client: RedisProtocolStringSelfTest.testGetSet

Dmitriy Govorukhin created IGNITE-5967: -- Summary: Flaky fail in Ignite Java Client: RedisProtocolStringSelfTest.testGetSet Key: IGNITE-5967 URL: https://issues.apache.org/jira/browse/IGNITE-5967

[jira] [Created] (IGNITE-5741) Replace HeapByteBuffer to DirectByteBuffer in WAL RecordsIterator

Dmitriy Govorukhin created IGNITE-5741: -- Summary: Replace HeapByteBuffer to DirectByteBuffer in WAL RecordsIterator Key: IGNITE-5741 URL: https://issues.apache.org/jira/browse/IGNITE-5741

[jira] [Created] (IGNITE-5704) Do not allow cluster to be deactivated if the joining node does not complete start all components

Dmitriy Govorukhin created IGNITE-5704: -- Summary: Do not allow cluster to be deactivated if the joining node does not complete start all components Key: IGNITE-5704 URL: https://issues.apache.org/jira/browse

Re: daemon nodes

Yakov, I created jira issue IGNITE-5603 . Whoever has an objection related this task? On Wed, Jun 28, 2017 at 2:28 PM, Yakov Zhdanov wrote: > >For me, daemon server, very strange. > > Agree, daemons can always be a

[jira] [Created] (IGNITE-5603) All daemon node, can be only client daemon, server daemon is not allow.

Dmitriy Govorukhin created IGNITE-5603: -- Summary: All daemon node, can be only client daemon, server daemon is not allow. Key: IGNITE-5603 URL: https://issues.apache.org/jira/browse/IGNITE-5603

Re: daemon nodes

What kind of messages are you talking about? Please, provide example. On Wed, Jun 28, 2017 at 11:54 AM, Дмитрий Рябов <somefire...@gmail.com> wrote: > Some messages don't go through clients. May be some daemon realization will > need them? > > 2017-06-28 11:22 GMT+03:00

Re: daemon nodes

r nodes, but does > not need to participate in computation or data related functionality. > > D. > > On Tue, Jun 27, 2017 at 2:49 AM, Dmitriy Govorukhin < > dmitriy.govoruk...@gmail.com> wrote: > >> Hi Igniters, >> >> Can somebody explain what does mean d

[jira] [Created] (IGNITE-5600) Compute hang if send broadcast runnable on daemon cluster group

Dmitriy Govorukhin created IGNITE-5600: -- Summary: Compute hang if send broadcast runnable on daemon cluster group Key: IGNITE-5600 URL: https://issues.apache.org/jira/browse/IGNITE-5600 Project

daemon nodes

Hi Igniters, Can somebody explain what does mean daemon node? I thought that exist only client and server node, but node may can be daemon (server daemon or client daemon). As is can see, command line visor join in topology as server daemon. Can this be an outdated functionality?

[jira] [Created] (IGNITE-5520) IgniteChangeGlobalStateFailOverTest hangs activate on join node

Dmitriy Govorukhin created IGNITE-5520: -- Summary: IgniteChangeGlobalStateFailOverTest hangs activate on join node Key: IGNITE-5520 URL: https://issues.apache.org/jira/browse/IGNITE-5520 Project

[jira] [Created] (IGNITE-5518) Rework test on join active/inactive node

Dmitriy Govorukhin created IGNITE-5518: -- Summary: Rework test on join active/inactive node Key: IGNITE-5518 URL: https://issues.apache.org/jira/browse/IGNITE-5518 Project: Ignite Issue

[jira] [Created] (IGNITE-5480) Need to correctly handle deactivation process if an exception occured during deactivation

Dmitriy Govorukhin created IGNITE-5480: -- Summary: Need to correctly handle deactivation process if an exception occured during deactivation Key: IGNITE-5480 URL: https://issues.apache.org/jira/browse/IGNITE

Persistent Distributed Store Metrics

Folk, As you know, ignite 2.1 will contain new module (pds), it will be provide ability to store data on disk. Let's discuss what type of metrics we need for this? I think it must be metrics per memory policy, per cache, checkpoint, and global metrics which will be aggregate all metrics. I did

[jira] [Created] (IGNITE-5076) Optimization of multi-threaded start nodes in tests

Dmitriy Govorukhin created IGNITE-5076: -- Summary: Optimization of multi-threaded start nodes in tests Key: IGNITE-5076 URL: https://issues.apache.org/jira/browse/IGNITE-5076 Project: Ignite

[jira] [Created] (IGNITE-5019) Deadlock in GridCacheVariableTopologySelfTest.testNodeStop

Dmitriy Govorukhin created IGNITE-5019: -- Summary: Deadlock in GridCacheVariableTopologySelfTest.testNodeStop Key: IGNITE-5019 URL: https://issues.apache.org/jira/browse/IGNITE-5019 Project

Re: CachePojoStore data loading with binary marshaller

. > > Makes sense? > > -Val > > On Tue, Apr 11, 2017 at 12:06 PM, Dmitriy Govorukhin < > dmitriy.govoruk...@gmail.com> wrote: > > > Hi all, > > > > I found problem related to CacheJdbcPojoStore. If try to load data, with > > enabled binary

CachePojoStore data loading with binary marshaller

Hi all, I found problem related to CacheJdbcPojoStore. If try to load data, with enabled binary marshaller, error may occur. Problem in entryMappings (this map helps resolve stored type when data loading). If binary marshaller disable we just put entry with java type in this map, if enable we

[jira] [Created] (IGNITE-4931) Safe way for deactivate cluster.

Dmitriy Govorukhin created IGNITE-4931: -- Summary: Safe way for deactivate cluster. Key: IGNITE-4931 URL: https://issues.apache.org/jira/browse/IGNITE-4931 Project: Ignite Issue Type

Re: TeamCity agent suspended

ri, Apr 7, 2017 at 10:55 AM, Dmitriy Govorukhin < > dmitriy.govoruk...@gmail.com> wrote: > > > Hi guys, > > > > I have concerns about TC status, i see that 3 agent has overtime 80 h and > > 14 h. Who can restart them? > > >

TeamCity agent suspended

Hi guys, I have concerns about TC status, i see that 3 agent has overtime 80 h and 14 h. Who can restart them?

[jira] [Created] (IGNITE-4919) Remove support BinaryIdentityResolver

Dmitriy Govorukhin created IGNITE-4919: -- Summary: Remove support BinaryIdentityResolver Key: IGNITE-4919 URL: https://issues.apache.org/jira/browse/IGNITE-4919 Project: Ignite Issue

Re: Stable binary key representation

Hi guys, i implemented proxy for IgniteCache in hibernate integration, this proxy transformate cacheKey to our key wrapper, leaves only required field. I think we can remove identity resolve, it should not broke integration with hibernate. Any objections? On Wed, Mar 29, 2017 at 11:07 PM,

[jira] [Created] (IGNITE-4235) Can't get user exception if was on remote service

Dmitriy Govorukhin created IGNITE-4235: -- Summary: Can't get user exception if was on remote service Key: IGNITE-4235 URL: https://issues.apache.org/jira/browse/IGNITE-4235 Project: Ignite

[jira] [Created] (IGNITE-4178) Support permission builder

Dmitriy Govorukhin created IGNITE-4178: -- Summary: Support permission builder Key: IGNITE-4178 URL: https://issues.apache.org/jira/browse/IGNITE-4178 Project: Ignite Issue Type

Re: Ignite TeamCity URL

Yes, from this page wiki <https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+Home>. On Thu, Nov 3, 2016 at 11:59 PM, Dmitriy Setrakyan <dsetrak...@apache.org> wrote: > Is this URL documented on Wiki? > > On Thu, Nov 3, 2016 at 1:52 PM, Dmitriy Govorukhi

Re: Ignite TeamCity URL

Hi Igor, ci.ignite.apache.org 3 нояб. 2016 г. 11:26 PM пользователь "Igor Rudyak" написал: > Hi guys, > > Just curious what's the new URL for Ignite TeamCity? > > Igor >

Add new event in putblic API

HI all, I think what we need add new event for handling unhandled exception. We have some exception which not handled, new event (UnhandledExceptionEvent) can help know if was unhandled exception. Let's discuss. More details about reason IGNITE-2079

[jira] [Created] (IGNITE-4044) Add an option to always authenticate local node

Dmitriy Govorukhin created IGNITE-4044: -- Summary: Add an option to always authenticate local node Key: IGNITE-4044 URL: https://issues.apache.org/jira/browse/IGNITE-4044 Project: Ignite

<    1   2