Re: Ignite components deserialization

he ticket where we improved the serialization of Ignite > components [1]. > > From what I can see, the fix was made for IgniteKernal, but not for other > classes like ClusterGroupAdapter, GridKernalContextImpl and others. What is > the reason for this? > > Vladimir Ershov, it look

[jira] [Created] (IGNITE-2649) Ignition.localIgnite() unreliable under Gateways and cause wrong components deserialization.

Vladimir Ershov created IGNITE-2649: --- Summary: Ignition.localIgnite() unreliable under Gateways and cause wrong components deserialization. Key: IGNITE-2649 URL: https://issues.apache.org/jira/browse/IGNITE

[jira] [Created] (IGNITE-2636) Server cache metrics for put-get-remove avg time are incorrect for case when request sent from client

Vladimir Ershov created IGNITE-2636: --- Summary: Server cache metrics for put-get-remove avg time are incorrect for case when request sent from client Key: IGNITE-2636 URL: https://issues.apache.org/jira/browse

[jira] [Created] (IGNITE-2616) NonHeap memory usage metrics don't work as expected.

Vladimir Ershov created IGNITE-2616: --- Summary: NonHeap memory usage metrics don't work as expected. Key: IGNITE-2616 URL: https://issues.apache.org/jira/browse/IGNITE-2616 Project: Ignite

[jira] [Created] (IGNITE-2585) Force Unit tests to fail in case of NPE in logs.

Vladimir Ershov created IGNITE-2585: --- Summary: Force Unit tests to fail in case of NPE in logs. Key: IGNITE-2585 URL: https://issues.apache.org/jira/browse/IGNITE-2585 Project: Ignite

Client Cache metrics API design discussion.

Igniters! Here is a handsome moment in our current cache metrics API, that begs for an improvement and due to it significancy assumed to be discussed communitywise. Current CacheMetrics interface is confusing for a case, when it is accessed from a client node. One of the typical question is:

[jira] [Created] (IGNITE-2569) Ignite GridComponent used incorrectly during IgniteStart. Could cause NPE

Vladimir Ershov created IGNITE-2569: --- Summary: Ignite GridComponent used incorrectly during IgniteStart. Could cause NPE Key: IGNITE-2569 URL: https://issues.apache.org/jira/browse/IGNITE-2569

[jira] [Created] (IGNITE-2539) NPE at RendezvousAffinityFunction

Vladimir Ershov created IGNITE-2539: --- Summary: NPE at RendezvousAffinityFunction Key: IGNITE-2539 URL: https://issues.apache.org/jira/browse/IGNITE-2539 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-2453) GridCacheStopSelfTest reveal NPE at GridNearTxFinishFuture for backup node is null

Vladimir Ershov created IGNITE-2453: --- Summary: GridCacheStopSelfTest reveal NPE at GridNearTxFinishFuture for backup node is null Key: IGNITE-2453 URL: https://issues.apache.org/jira/browse/IGNITE-2453

[jira] [Created] (IGNITE-2428) [Test] [Rare] IgniteClientReconnectFailoverTest.testReconnectComputeApi

Vladimir Ershov created IGNITE-2428: --- Summary: [Test] [Rare] IgniteClientReconnectFailoverTest.testReconnectComputeApi Key: IGNITE-2428 URL: https://issues.apache.org/jira/browse/IGNITE-2428

Re: Re: Re: about AOP development

Mail Master > > > On 2016-01-20 22:20 , Vladimir Ershov <vers...@gridgain.com> Wrote: > > As for the last step, let me correct myself: > >3. Start server Ignite node from spring context *AND *put spring jars > inside classpath in *.sh file. Be sure, that both nodes a

[jira] [Created] (IGNITE-2427) [Test] [Rare] CacheSerializableTransactionsTest.testGetRemoveTxNearCache2

Vladimir Ershov created IGNITE-2427: --- Summary: [Test] [Rare] CacheSerializableTransactionsTest.testGetRemoveTxNearCache2 Key: IGNITE-2427 URL: https://issues.apache.org/jira/browse/IGNITE-2427

[jira] [Created] (IGNITE-2420) [Test] Ignite AWS lacks amazon credentials.

Vladimir Ershov created IGNITE-2420: --- Summary: [Test] Ignite AWS lacks amazon credentials. Key: IGNITE-2420 URL: https://issues.apache.org/jira/browse/IGNITE-2420 Project: Ignite Issue

Re: Re: about AOP development

Hi! I've checked your code and spot an issue. The root cause, is using of Autowired annotation, since it cause bean to be serialized on a client side, and that leads ClassNotFoundException on the server side during bean deserialization, since server was started from *.sh, without necessary spring

[jira] [Created] (IGNITE-2400) [Test] [Rare] GridCacheReplicatedDataStructuresFailoverSelfTest.testQueueTopologyChange

Vladimir Ershov created IGNITE-2400: --- Summary: [Test] [Rare] GridCacheReplicatedDataStructuresFailoverSelfTest.testQueueTopologyChange Key: IGNITE-2400 URL: https://issues.apache.org/jira/browse/IGNITE-2400

[jira] [Created] (IGNITE-2401) [Test] [Rare] IgniteCacheCreatePutTest.testStartNodes

Vladimir Ershov created IGNITE-2401: --- Summary: [Test] [Rare] IgniteCacheCreatePutTest.testStartNodes Key: IGNITE-2401 URL: https://issues.apache.org/jira/browse/IGNITE-2401 Project: Ignite

[jira] [Created] (IGNITE-2406) [Test] [Rare] GridEventStorageCheckAllEventsSelfTest.testSuccessTask

Vladimir Ershov created IGNITE-2406: --- Summary: [Test] [Rare] GridEventStorageCheckAllEventsSelfTest.testSuccessTask Key: IGNITE-2406 URL: https://issues.apache.org/jira/browse/IGNITE-2406 Project

[jira] [Created] (IGNITE-2410) Ignite Platform .NET JVM crashed on TC

Vladimir Ershov created IGNITE-2410: --- Summary: Ignite Platform .NET JVM crashed on TC Key: IGNITE-2410 URL: https://issues.apache.org/jira/browse/IGNITE-2410 Project: Ignite Issue Type

[jira] [Created] (IGNITE-2378) Data loss Part 2. Add flexible DataLoss Policy. Improve dataLoss event with batch.

Vladimir Ershov created IGNITE-2378: --- Summary: Data loss Part 2. Add flexible DataLoss Policy. Improve dataLoss event with batch. Key: IGNITE-2378 URL: https://issues.apache.org/jira/browse/IGNITE-2378

New method in IgniteCache API.

Igniters! Since we are going to add stronger data loss check IGNITE-1605 I'm about to add new method for the manual resetting state of the lost partition in IgniteCache IgniteFuture *resetLostPartitions*(); just near #rebalance(). And would

Re: New method in IgniteCache API.

part of the topology validator? > 3. Are we going to block reads and writes or only writes? Ideally, user > should be able to configure either. > > D. > > On Wed, Jan 13, 2016 at 9:05 AM, Vladimir Ershov <vers...@gridgain.com> > wrote: > > > Dmitriy, > > I'v

Re: New method in IgniteCache API.

ition means. > > D. > > On Wed, Jan 13, 2016 at 5:23 AM, Vladimir Ershov <vers...@gridgain.com> > wrote: > > > Igniters! > > > > Since we are going to add stronger data loss check IGNITE-1605 > > <https://issues.apache.org/jira/browse/IGNITE

[jira] [Created] (IGNITE-2367) Preparation for the SQL DML design. Investiation of the current SQL processing.

Vladimir Ershov created IGNITE-2367: --- Summary: Preparation for the SQL DML design. Investiation of the current SQL processing. Key: IGNITE-2367 URL: https://issues.apache.org/jira/browse/IGNITE-2367

[jira] [Created] (IGNITE-2368) Performance optimization for an IgnitCache.query execution.

Vladimir Ershov created IGNITE-2368: --- Summary: Performance optimization for an IgnitCache.query execution. Key: IGNITE-2368 URL: https://issues.apache.org/jira/browse/IGNITE-2368 Project: Ignite

[jira] [Created] (IGNITE-2139) Expose indexing metrics using MBean

Vladimir Ershov created IGNITE-2139: --- Summary: Expose indexing metrics using MBean Key: IGNITE-2139 URL: https://issues.apache.org/jira/browse/IGNITE-2139 Project: Ignite Issue Type: Task

Introduction letter.

Dear Igniters! My name is Vladimir Ershov, I am a software engineer from Saint-Peresburg, Russia. I have joined the community recently and I hope to find here a lot of possibilities to create and design new solutions, to apply and develop my skills, and to be helpful by taking part in the most

[jira] [Created] (IGNITE-2031) Add the possibility to adress local ignite instance inside lambda.

Vladimir Ershov created IGNITE-2031: --- Summary: Add the possibility to adress local ignite instance inside lambda. Key: IGNITE-2031 URL: https://issues.apache.org/jira/browse/IGNITE-2031 Project

Re: Rename IgniteBinary to IgniteBinaries?

Imho, *IgniteBinaryProto *is also an option. Vladimir. On Thu, Nov 26, 2015 at 12:51 PM, Dmitriy Setrakyan wrote: > I prefer IgniteBinary. The plural form sounds like a release archive. > > D. > > On Thu, Nov 26, 2015 at 12:20 PM, Vladimir Ozerov

The ability to execute cache modifications during recovery.

Hi Folks! Assume case, when some cache partitions with data are lost from the grid, and thus EVT_CACHE_REBALANCE_PART_DATA_LOST event happen. Do we need the ability to execute cache modifications somehow, maybe like recover(Map<,> missingKeysAndValues) as part of GridDhtPartitionTopology API?

Re: [jira] [Created] (IGNITE-2009) Cached prepared SQL statement causes IgniteKernal leak.

Hi, Why then thread couldn't clear this threadLocal query at the end of the task execution? On Thu, Nov 26, 2015 at 5:06 PM, Vladimir Ozerov (JIRA) wrote: > Vladimir Ozerov created IGNITE-2009: > --- > > Summary: Cached prepared