[jira] [Created] (IGNITE-9425) NPE on index rebuild

Dmitry Karachentsev created IGNITE-9425: --- Summary: NPE on index rebuild Key: IGNITE-9425 URL: https://issues.apache.org/jira/browse/IGNITE-9425 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-9259) Wrong log message in IgniteKernal#ackMemoryConfiguration

Dmitry Karachentsev created IGNITE-9259: --- Summary: Wrong log message in IgniteKernal#ackMemoryConfiguration Key: IGNITE-9259 URL: https://issues.apache.org/jira/browse/IGNITE-9259 Project

[jira] [Created] (IGNITE-9257) LOCAL cache doesn't evict entries from heap

Dmitry Karachentsev created IGNITE-9257: --- Summary: LOCAL cache doesn't evict entries from heap Key: IGNITE-9257 URL: https://issues.apache.org/jira/browse/IGNITE-9257 Project: Ignite

[jira] [Created] (IGNITE-9038) Node join serialization defaults

Dmitry Karachentsev created IGNITE-9038: --- Summary: Node join serialization defaults Key: IGNITE-9038 URL: https://issues.apache.org/jira/browse/IGNITE-9038 Project: Ignite Issue Type

Re: Neighbors exclusion

at 8:05 AM Dmitry Karachentsev < dkarachent...@gridgain.com> wrote: Hi folks, Why RendezvousAffinityFunction.excludeNeighbors [1] is false by default? It's not obvious that if user wants to run more than one node per machine it has also set this flag to true explicitly. Maybe it would be

Neighbors exclusion

Hi folks, Why RendezvousAffinityFunction.excludeNeighbors [1] is false by default? It's not obvious that if user wants to run more than one node per machine it has also set this flag to true explicitly. Maybe it would be better to set it to true by default? At the same time if

Re: Stable/experimental releases

+ - stabilization. This seems to be more standard and flexible approach. чт, 5 июля 2018 г. в 17:39, Dmitry Karachentsev < dkarachent...@gridgain.com : Hi igniters! Following our discussions about emergency releases I see that here might be applied new way for doing releases. Like it was for Li

[jira] [Created] (IGNITE-8944) TcpDiscoverySpi: set connection check frequency to fixed value

Dmitry Karachentsev created IGNITE-8944: --- Summary: TcpDiscoverySpi: set connection check frequency to fixed value Key: IGNITE-8944 URL: https://issues.apache.org/jira/browse/IGNITE-8944 Project

Stable/experimental releases

Hi igniters! Following our discussions about emergency releases I see that here might be applied new way for doing releases. Like it was for Linux or like it is for Ubuntu. I mean do interleaving releases: first is experimental with newest features and second - with bug fixes ONLY. For

Re: is these correct?

Hi, Please clarify what's wrong in your opinion? If you mean that you do not see hits or misses - metrics are disabled by default [1]. [1] https://apacheignite.readme.io/v2.0/docs/memory-and-cache-metrics Thanks! -Dmitry 30.06.2018 05:12, kcheng.mvp пишет: here is the environment : 1

Re: Review IGNITE-8859

have you tested running built Apache Ignite under JDK10? On 29 Jun 2018, at 17:06, Dmitry Karachentsev wrote: Forgot a link to the ticket https://issues.apache.org/jira/browse/IGNITE-8859 29.06.2018 17:06, Dmitry Karachentsev пишет: Hi guys, I've enhanced our scripts a bit to allow run

Re: Review IGNITE-8859

Forgot a link to the ticket https://issues.apache.org/jira/browse/IGNITE-8859 29.06.2018 17:06, Dmitry Karachentsev пишет: Hi guys, I've enhanced our scripts a bit to allow run Ignite on Java 10+. Please review. I'm not sure if there exist tests, but I tested on Windows/Linux for 1.7, 1.8

Review IGNITE-8859

Hi guys, I've enhanced our scripts a bit to allow run Ignite on Java 10+. Please review. I'm not sure if there exist tests, but I tested on Windows/Linux for 1.7, 1.8, 9 and 10 JDKs manually. Thanks!

[jira] [Created] (IGNITE-8896) Wrong javadoc for TcpCommunicationSpi.setSlowClientQueueLimit()

Dmitry Karachentsev created IGNITE-8896: --- Summary: Wrong javadoc for TcpCommunicationSpi.setSlowClientQueueLimit() Key: IGNITE-8896 URL: https://issues.apache.org/jira/browse/IGNITE-8896

[jira] [Created] (IGNITE-8859) Open upper Java verison bounds

Dmitry Karachentsev created IGNITE-8859: --- Summary: Open upper Java verison bounds Key: IGNITE-8859 URL: https://issues.apache.org/jira/browse/IGNITE-8859 Project: Ignite Issue Type

[jira] [Created] (IGNITE-8858) Client none may not stop

Dmitry Karachentsev created IGNITE-8858: --- Summary: Client none may not stop Key: IGNITE-8858 URL: https://issues.apache.org/jira/browse/IGNITE-8858 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-8852) CacheJoinNodeDiscoveryData.CacheInfo has boolean flags and long field for flags

Dmitry Karachentsev created IGNITE-8852: --- Summary: CacheJoinNodeDiscoveryData.CacheInfo has boolean flags and long field for flags Key: IGNITE-8852 URL: https://issues.apache.org/jira/browse/IGNITE-8852

[jira] [Created] (IGNITE-8851) StoredCacheData and CacheJoinNodeDiscoveryData.CacheInfo duplicate "sql" flag

Dmitry Karachentsev created IGNITE-8851: --- Summary: StoredCacheData and CacheJoinNodeDiscoveryData.CacheInfo duplicate "sql" flag Key: IGNITE-8851 URL: https://issues.apache.org/jira/browse/I

[jira] [Created] (IGNITE-8813) Add ComputeJobResultPolicy to JobEvent

Dmitry Karachentsev created IGNITE-8813: --- Summary: Add ComputeJobResultPolicy to JobEvent Key: IGNITE-8813 URL: https://issues.apache.org/jira/browse/IGNITE-8813 Project: Ignite Issue

Re: IGNITE-4188, savepoints with atomic cache?

I would vote for 1 or 3 (this I like more), but not 2 as such breaking change involves more pain to our users. Let it be in 3.0 and included in migration guide, I don't see much drawbacks here. Thanks! 13.06.2018 19:20, Ivan Rakov пишет: +1 to Eduard. It's a reasonable change, but we can't

[jira] [Created] (IGNITE-8500) [Cassandra] Allow dynamic cache creation with Cassandra Store

Dmitry Karachentsev created IGNITE-8500: --- Summary: [Cassandra] Allow dynamic cache creation with Cassandra Store Key: IGNITE-8500 URL: https://issues.apache.org/jira/browse/IGNITE-8500 Project

[jira] [Created] (IGNITE-7673) Remove using of Collections.UnmodifiableCollection from GridTaskSessionImpl

Dmitry Karachentsev created IGNITE-7673: --- Summary: Remove using of Collections.UnmodifiableCollection from GridTaskSessionImpl Key: IGNITE-7673 URL: https://issues.apache.org/jira/browse/IGNITE-7673

Re: Text query with persistence

Dmitry Karachentsev <dkarachent...@gridgain.com>: Hi guys, We have Apache Lucene based full text search that creates in-memory indexes. It's a nice feature, but it seems absolutely useless with persistence as indexes are dropped on node restart. Probably we need a configuration flag and\or AP

Text query with persistence

Hi guys, We have Apache Lucene based full text search that creates in-memory indexes. It's a nice feature, but it seems absolutely useless with persistence as indexes are dropped on node restart. Probably we need a configuration flag and\or API call to rebuild them, or persist somehow. Do

Re: LOCAL cache on client

8-02-01 7:36 GMT-08:00 Dmitry Karachentsev <dkarachent...@gridgain.com : Hello everyone! We have an erroneous use case when client tries to create LOCAL cache, but by default it does not initiates default data region. So client gets NPE. [1] I think it should be a lazy data region initializati

LOCAL cache on client

Hello everyone! We have an erroneous use case when client tries to create LOCAL cache, but by default it does not initiates default data region. So client gets NPE. [1] I think it should be a lazy data region initialization on client. Do you have any concerns about this approach or other

[jira] [Created] (IGNITE-7340) Fix flaky org.apache.ignite.internal.processors.service.GridServiceProcessorMultiNodeConfigSelfTest#checkDeployOnEachNodeUpdateTopology

Dmitry Karachentsev created IGNITE-7340: --- Summary: Fix flaky org.apache.ignite.internal.processors.service.GridServiceProcessorMultiNodeConfigSelfTest#checkDeployOnEachNodeUpdateTopology Key: IGNITE-7340

Re: List of running Continuous queries or CacheEntryListener per cache or node

to track all user-provided tasks - CacheListener, ContinuousQuery, ComputeTasks, etc. В Чт, 21/12/2017 в 10:13 +0300, Dmitry Karachentsev пишет: Crossposting to devlist. Hi Igniters! It's might be a nice feature to have - get list of registered continuous queries with ability to deregister them

Re: List of running Continuous queries or CacheEntryListener per cache or node

Crossposting to devlist. Hi Igniters! It's might be a nice feature to have - get list of registered continuous queries with ability to deregister them. What do you think? Thanks! -Dmitry 20.12.2017 16:59, fefe пишет: For sanity checks or tests. I want to be sure that I haven't forgot to

[jira] [Created] (IGNITE-7239) In case of not serializable cache update response, future on node requester will never complete

Dmitry Karachentsev created IGNITE-7239: --- Summary: In case of not serializable cache update response, future on node requester will never complete Key: IGNITE-7239 URL: https://issues.apache.org/jira/browse

[jira] [Created] (IGNITE-7206) Nodes may ping each other on stop for a failureDetectionTimeout period

Dmitry Karachentsev created IGNITE-7206: --- Summary: Nodes may ping each other on stop for a failureDetectionTimeout period Key: IGNITE-7206 URL: https://issues.apache.org/jira/browse/IGNITE-7206

[jira] [Created] (IGNITE-7181) Fix IGNITE-7086 doesn't work with PESSIMISTIC REPEATABLE_READ transaction

Dmitry Karachentsev created IGNITE-7181: --- Summary: Fix IGNITE-7086 doesn't work with PESSIMISTIC REPEATABLE_READ transaction Key: IGNITE-7181 URL: https://issues.apache.org/jira/browse/IGNITE-7181

[jira] [Created] (IGNITE-7159) Fix IGNITE-7086 fails IgniteCacheAtomicExpiryPolicyWithStoreTest.testGetReadThrough

Dmitry Karachentsev created IGNITE-7159: --- Summary: Fix IGNITE-7086 fails IgniteCacheAtomicExpiryPolicyWithStoreTest.testGetReadThrough Key: IGNITE-7159 URL: https://issues.apache.org/jira/browse/IGNITE-7159

[jira] [Created] (IGNITE-6818) In case of incoming communication connection ping the old one if it's alive

Dmitry Karachentsev created IGNITE-6818: --- Summary: In case of incoming communication connection ping the old one if it's alive Key: IGNITE-6818 URL: https://issues.apache.org/jira/browse/IGNITE-6818

[jira] [Created] (IGNITE-6671) [Web Console] Wrong java type used in generated config from DB schema

Dmitry Karachentsev created IGNITE-6671: --- Summary: [Web Console] Wrong java type used in generated config from DB schema Key: IGNITE-6671 URL: https://issues.apache.org/jira/browse/IGNITE-6671

[jira] [Created] (IGNITE-6487) Affinity may return more backups that set during exchange

Dmitry Karachentsev created IGNITE-6487: --- Summary: Affinity may return more backups that set during exchange Key: IGNITE-6487 URL: https://issues.apache.org/jira/browse/IGNITE-6487 Project

[jira] [Created] (IGNITE-6431) Web Console: "Partition loss policy" field is duplicated

Dmitry Karachentsev created IGNITE-6431: --- Summary: Web Console: "Partition loss policy" field is duplicated Key: IGNITE-6431 URL: https://issues.apache.org/jira/browse/IGNITE-6431

[jira] [Created] (IGNITE-6166) Exceptions are printed to console, instead of log

Dmitry Karachentsev created IGNITE-6166: --- Summary: Exceptions are printed to console, instead of log Key: IGNITE-6166 URL: https://issues.apache.org/jira/browse/IGNITE-6166 Project: Ignite

[jira] [Created] (IGNITE-6165) Use SSL connection in IpcClientTcpEndpoint when it's configured for grid

Dmitry Karachentsev created IGNITE-6165: --- Summary: Use SSL connection in IpcClientTcpEndpoint when it's configured for grid Key: IGNITE-6165 URL: https://issues.apache.org/jira/browse/IGNITE-6165

[jira] [Created] (IGNITE-5795) @AffinityKeyMapped ignored if QueryEntity used

Dmitry Karachentsev created IGNITE-5795: --- Summary: @AffinityKeyMapped ignored if QueryEntity used Key: IGNITE-5795 URL: https://issues.apache.org/jira/browse/IGNITE-5795 Project: Ignite

[jira] [Created] (IGNITE-5768) Retry resolving class name from marshaller cache and .classname file

Dmitry Karachentsev created IGNITE-5768: --- Summary: Retry resolving class name from marshaller cache and .classname file Key: IGNITE-5768 URL: https://issues.apache.org/jira/browse/IGNITE-5768

[jira] [Created] (IGNITE-5570) IgniteMessaging should have sendAsync() method

Dmitry Karachentsev created IGNITE-5570: --- Summary: IgniteMessaging should have sendAsync() method Key: IGNITE-5570 URL: https://issues.apache.org/jira/browse/IGNITE-5570 Project: Ignite

[jira] [Created] (IGNITE-5424) GridServiceProxy does not unwraps exception message from InvocationTargetException

Dmitry Karachentsev created IGNITE-5424: --- Summary: GridServiceProxy does not unwraps exception message from InvocationTargetException Key: IGNITE-5424 URL: https://issues.apache.org/jira/browse/IGNITE-5424

[jira] [Created] (IGNITE-5342) Skip permission check for TASK_EXECUTE for service jobs

Dmitry Karachentsev created IGNITE-5342: --- Summary: Skip permission check for TASK_EXECUTE for service jobs Key: IGNITE-5342 URL: https://issues.apache.org/jira/browse/IGNITE-5342 Project: Ignite

[jira] [Created] (IGNITE-5332) Add toString() to GridNearAtomicAbstractSingleUpdateRequest and it's inheritors

Dmitry Karachentsev created IGNITE-5332: --- Summary: Add toString() to GridNearAtomicAbstractSingleUpdateRequest and it's inheritors Key: IGNITE-5332 URL: https://issues.apache.org/jira/browse/IGNITE-5332

[jira] [Created] (IGNITE-5259) Support backward compatibility with versions without service permissions

Dmitry Karachentsev created IGNITE-5259: --- Summary: Support backward compatibility with versions without service permissions Key: IGNITE-5259 URL: https://issues.apache.org/jira/browse/IGNITE-5259

[jira] [Created] (IGNITE-5223) Allow use local binary metadata cache if it's possible

Dmitry Karachentsev created IGNITE-5223: --- Summary: Allow use local binary metadata cache if it's possible Key: IGNITE-5223 URL: https://issues.apache.org/jira/browse/IGNITE-5223 Project: Ignite

[jira] [Created] (IGNITE-5145) Support multiple service deployment in API

Dmitry Karachentsev created IGNITE-5145: --- Summary: Support multiple service deployment in API Key: IGNITE-5145 URL: https://issues.apache.org/jira/browse/IGNITE-5145 Project: Ignite

[jira] [Created] (IGNITE-5144) Do not start remappings in DataStreamer on client node leave/arrive

Dmitry Karachentsev created IGNITE-5144: --- Summary: Do not start remappings in DataStreamer on client node leave/arrive Key: IGNITE-5144 URL: https://issues.apache.org/jira/browse/IGNITE-5144

[jira] [Created] (IGNITE-5077) Support service permissions

Dmitry Karachentsev created IGNITE-5077: --- Summary: Support service permissions Key: IGNITE-5077 URL: https://issues.apache.org/jira/browse/IGNITE-5077 Project: Ignite Issue Type: New

[jira] [Created] (IGNITE-5038) Add BinaryObject.deserialize(ClassLoader) method

Dmitry Karachentsev created IGNITE-5038: --- Summary: Add BinaryObject.deserialize(ClassLoader) method Key: IGNITE-5038 URL: https://issues.apache.org/jira/browse/IGNITE-5038 Project: Ignite

[jira] [Created] (IGNITE-5032) IgniteLock broken state resets on node restart

Dmitry Karachentsev created IGNITE-5032: --- Summary: IgniteLock broken state resets on node restart Key: IGNITE-5032 URL: https://issues.apache.org/jira/browse/IGNITE-5032 Project: Ignite

[jira] [Created] (IGNITE-5013) Allow pass custom types to Cassandra store

Dmitry Karachentsev created IGNITE-5013: --- Summary: Allow pass custom types to Cassandra store Key: IGNITE-5013 URL: https://issues.apache.org/jira/browse/IGNITE-5013 Project: Ignite

Re: IgniteSemaphore and failoverSafe flag

is interrupt flag is not always cleared properly in #GridCacheSemaphore.acquire method (but it doesn't have anything to do with latest fix) Can you make it reproducible? On Fri, Apr 14, 2017 at 2:46 PM, Dmitry Karachentsev <dkarachent...@gridgain.com <mailto:dkarachent...@gridgain.com&g

Re: IgniteSemaphore and failoverSafe flag

://issues.apache.org/jira/browse/IGNITE-1977 Thanks! 14.04.2017 15:27, Dmitry Karachentsev пишет: Vladislav, Yep, you're right. I'll fix it. Thanks! 14.04.2017 15:18, Vladisav Jelisavcic пишет: Hi Dmitry, it looks to me that this test is not valid - after the semaphore 2 fails the permits

Re: IgniteSemaphore and failoverSafe flag

guess before latest fix this test was (incorrectly) passing because permits weren't released properly. What do you think? On Fri, Apr 14, 2017 at 11:27 AM, Dmitry Karachentsev <dkarachent...@gridgain.com <mailto:dkarachent...@gridgain.com>> wrote: Hi Vladislav, It look

Re: IgniteSemaphore and failoverSafe flag

Karachentsev пишет: Thanks a lot! 12.04.2017 16:35, Vladisav Jelisavcic пишет: Hi Dmitry, sure, I made a fix, take a look at the PR and the comments in the ticket. Best regards, Vladisav On Tue, Apr 11, 2017 at 3:00 PM, Dmitry Karachentsev <dkarachent...@gridgain.com <mailto:dkarachent...@gridga

Re: IgniteSemaphore and failoverSafe flag

Thanks a lot! 12.04.2017 16:35, Vladisav Jelisavcic пишет: Hi Dmitry, sure, I made a fix, take a look at the PR and the comments in the ticket. Best regards, Vladisav On Tue, Apr 11, 2017 at 3:00 PM, Dmitry Karachentsev <dkarachent...@gridgain.com <mailto:dkarachent...@gridgain.com&g

Re: IgniteSemaphore and failoverSafe flag

to bake a pr later during the day. Best regards, Vladisav On Tue, Apr 4, 2017 at 11:05 AM, Dmitry Karachentsev <dkarachent...@gridgain.com <mailto:dkarachent...@gridgain.com>> wrote: Hi Vladislav, I see you're developing [1] for a while, did you have any chanc

Async listeners for IgniteFuture

Hello everyone! I'm working on this ticket [1] and Vladimir made a review where he has concerns about implementation. I want to know community opinion about second one: where user callbacks should be processed by default? For that purpose I used public pool for now, but this could lead to

[jira] [Created] (IGNITE-4912) Fix testDeployCalledAfterCacheStart and testDeployCalledBeforeCacheStart tests

Dmitry Karachentsev created IGNITE-4912: --- Summary: Fix testDeployCalledAfterCacheStart and testDeployCalledBeforeCacheStart tests Key: IGNITE-4912 URL: https://issues.apache.org/jira/browse/IGNITE-4912

[jira] [Created] (IGNITE-4911) Fix tests #1

Dmitry Karachentsev created IGNITE-4911: --- Summary: Fix tests #1 Key: IGNITE-4911 URL: https://issues.apache.org/jira/browse/IGNITE-4911 Project: Ignite Issue Type: Bug

Re: IgniteSemaphore and failoverSafe flag

Hi Vladislav, I see you're developing [1] for a while, did you have any chance to fix it? If no, is there any estimate? [1] https://issues.apache.org/jira/browse/IGNITE-1977 Thanks! -Dmitry. 20.03.2017 10:28, Alexey Goncharuk пишет: I think re-creation should be handled by a user who

Re: IGNITE-4284 - ready for review

Hi Nikita, I've looked through the issue and, because fix is quite small and important, committed to PR#1681 [1]. Please take a look at it. Here is the code review [2]. I'll assign it to myself and resolve. If you have any questions about fix, please ask. Thanks for your effort! [1]

Re: IgniteMessaging in async mode

it would be very confusing as actual send is always asynchronous. -Val On Fri, Mar 24, 2017 at 9:10 AM, Dmitriy Setrakyan <dsetrak...@apache.org> wrote: I am a bit confused. The "send()" method does not wait for any replies, why would it block? On Fri, Mar 24, 2017 at 2:38 AM, Dmi

[jira] [Created] (IGNITE-4867) CacheMetricsSnapshot ignores 'size' and 'keySize' fields

Dmitry Karachentsev created IGNITE-4867: --- Summary: CacheMetricsSnapshot ignores 'size' and 'keySize' fields Key: IGNITE-4867 URL: https://issues.apache.org/jira/browse/IGNITE-4867 Project

[jira] [Created] (IGNITE-4866) Add lazy value deserialization in GridCacheRawVersionedEntry

Dmitry Karachentsev created IGNITE-4866: --- Summary: Add lazy value deserialization in GridCacheRawVersionedEntry Key: IGNITE-4866 URL: https://issues.apache.org/jira/browse/IGNITE-4866 Project

[jira] [Created] (IGNITE-4862) NPE in reading data from IGFS

Dmitry Karachentsev created IGNITE-4862: --- Summary: NPE in reading data from IGFS Key: IGNITE-4862 URL: https://issues.apache.org/jira/browse/IGNITE-4862 Project: Ignite Issue Type: Bug

IgniteMessaging in async mode

Hi Igniters! We have in IgniteMessaging interface async support, and it's used only for registering/deregistering listeners, not for message sending. But user may fall into the case, when connection to destination node was lost and user's thread is blocked on

Re: Can I let Ignite to do rebalance at a particular time?

Hi, Totally agree wit that. And it should be possible to start re-balancing from client node too. > But I think it is more convenient to start rebalancing manually from management console, is it right? I don't see the difference on how to start re-balancing: from Ignite API or console,

[jira] [Created] (IGNITE-4740) Service could be initialized twice on concurrent cancel and discovery event

Dmitry Karachentsev created IGNITE-4740: --- Summary: Service could be initialized twice on concurrent cancel and discovery event Key: IGNITE-4740 URL: https://issues.apache.org/jira/browse/IGNITE-4740

[jira] [Created] (IGNITE-4718) Add section in documentation on what actions may cause deadlock

Dmitry Karachentsev created IGNITE-4718: --- Summary: Add section in documentation on what actions may cause deadlock Key: IGNITE-4718 URL: https://issues.apache.org/jira/browse/IGNITE-4718

[jira] [Created] (IGNITE-4671) FairAffinityFunction fails on node restart with backupFilter set and no backups

Dmitry Karachentsev created IGNITE-4671: --- Summary: FairAffinityFunction fails on node restart with backupFilter set and no backups Key: IGNITE-4671 URL: https://issues.apache.org/jira/browse/IGNITE-4671

[jira] [Created] (IGNITE-4667) Throw exception on starting client cache when indexed types cannot be loaded

Dmitry Karachentsev created IGNITE-4667: --- Summary: Throw exception on starting client cache when indexed types cannot be loaded Key: IGNITE-4667 URL: https://issues.apache.org/jira/browse/IGNITE-4667

[jira] [Created] (IGNITE-4644) Value from IgniteQueue in atomic mode could be lost

Dmitry Karachentsev created IGNITE-4644: --- Summary: Value from IgniteQueue in atomic mode could be lost Key: IGNITE-4644 URL: https://issues.apache.org/jira/browse/IGNITE-4644 Project: Ignite

Re: Error in JDBC store

Opened a ticket for that [1]. [1] https://issues.apache.org/jira/browse/IGNITE-4515 On 29.12.2016 23:07, Valentin Kulichenko wrote: Hi Dmitry, My opinion is that this is not a valid case and we should throw an exception on cache startup if two Java fields are mapped to the same DB field. Even

[jira] [Created] (IGNITE-4515) Throw exception when key and value fields mapped to the same DB columns

Dmitry Karachentsev created IGNITE-4515: --- Summary: Throw exception when key and value fields mapped to the same DB columns Key: IGNITE-4515 URL: https://issues.apache.org/jira/browse/IGNITE-4515

[jira] [Created] (IGNITE-4487) NPE on query execution

Dmitry Karachentsev created IGNITE-4487: --- Summary: NPE on query execution Key: IGNITE-4487 URL: https://issues.apache.org/jira/browse/IGNITE-4487 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-4455) Node restarts may hang grid on exchange process

Dmitry Karachentsev created IGNITE-4455: --- Summary: Node restarts may hang grid on exchange process Key: IGNITE-4455 URL: https://issues.apache.org/jira/browse/IGNITE-4455 Project: Ignite

Re: Grid hang on compute

easier to implement) to have separate connections. As a workaround you can increase the limit. Setting it to 0 may lead to a potential OOME on sender or receiver sides. --Yakov 2016-12-07 20:35 GMT+07:00 Dmitry Karachentsev <dkarachent...@gridgain.com : Igniters! Recently faced with argua

[jira] [Created] (IGNITE-4395) Implement communication backpressure per policy - SYSTEM or PUBLIC

Dmitry Karachentsev created IGNITE-4395: --- Summary: Implement communication backpressure per policy - SYSTEM or PUBLIC Key: IGNITE-4395 URL: https://issues.apache.org/jira/browse/IGNITE-4395

Grid hang on compute

Igniters! Recently faced with arguable issue, it looks like a bug. Scenario is following: 1) Start two data nodes with some cache. 2) From one node in async mode post some big number of jobs to another. That jobs do some cache operations. 3) Grid hangs almost immediately and all threads

[jira] [Created] (IGNITE-4284) Failed second client node join with continuous query and peer class loading enabled

Dmitry Karachentsev created IGNITE-4284: --- Summary: Failed second client node join with continuous query and peer class loading enabled Key: IGNITE-4284 URL: https://issues.apache.org/jira/browse/IGNITE-4284

[jira] [Created] (IGNITE-4231) Hangs on compute result serialization error

Dmitry Karachentsev created IGNITE-4231: --- Summary: Hangs on compute result serialization error Key: IGNITE-4231 URL: https://issues.apache.org/jira/browse/IGNITE-4231 Project: Ignite

Re: Service proxy API changes

Valentin, as I understand, this situation is abnormal, and if user thread hangs on getting service proxy, it's worth to check logs for failure instead of making workaround. On 15.11.2016 19:47, Valentin Kulichenko wrote: I would still add a timeout there. In my view, it makes sense to have

[jira] [Created] (IGNITE-3813) High contention on GridCacheMapEntry.obsolete() on loading data to data stremer with composite keys

Dmitry Karachentsev created IGNITE-3813: --- Summary: High contention on GridCacheMapEntry.obsolete() on loading data to data stremer with composite keys Key: IGNITE-3813 URL: https://issues.apache.org/jira

[jira] [Created] (IGNITE-3590) Create test and first simple implementation of secondary file system.

Dmitry Karachentsev created IGNITE-3590: --- Summary: Create test and first simple implementation of secondary file system. Key: IGNITE-3590 URL: https://issues.apache.org/jira/browse/IGNITE-3590

[jira] [Created] (IGNITE-3339) get() in explicit READ_COMMITTED transaction on OFFHEAP_TIERED cache copies data from offheap to onheap.

Dmitry Karachentsev created IGNITE-3339: --- Summary: get() in explicit READ_COMMITTED transaction on OFFHEAP_TIERED cache copies data from offheap to onheap. Key: IGNITE-3339 URL: https://issues.apache.org

Code merge in 1.6 branch at 16-th

Anton V., is it still be possible to merge changes to 1.6 branch at Monday 16-th? I have a fix that waiting for review and it would be nice to add it in that release (IGNITE-3087 ). Thanks! Dmitry.

[jira] [Created] (IGNITE-3117) Weblogic manual tests for HttpSession caching.

Dmitry Karachentsev created IGNITE-3117: --- Summary: Weblogic manual tests for HttpSession caching. Key: IGNITE-3117 URL: https://issues.apache.org/jira/browse/IGNITE-3117 Project: Ignite

[jira] [Created] (IGNITE-2995) putAll() and removeAll() operations on transactional cache are very slow on big number of entries

Dmitry Karachentsev created IGNITE-2995: --- Summary: putAll() and removeAll() operations on transactional cache are very slow on big number of entries Key: IGNITE-2995 URL: https://issues.apache.org/jira

Re: Stream API doesn't update cache metrics.

Yes, switching it to 'true' does the magic. Thanks! On 08.04.2016 13:52, Yakov Zhdanov wrote: Is allowOverwrite set to 'false'? Thanks! -- Yakov Zhdanov, Director R *GridGain Systems* www.gridgain.com 2016-04-08 10:30 GMT+03:00 Dmitry Karachentsev <dkarachent...@gridgain.com>:

Stream API doesn't update cache metrics.

Hi all. Adding data to cache via streamer doesn't update cache metrics like AveragePutTime, CachePuts. Was it made intentionally? Thanks! Dmitry.

[jira] [Created] (IGNITE-2763) GridDhtPartitionDemander fails with assertion on partition move

Dmitry Karachentsev created IGNITE-2763: --- Summary: GridDhtPartitionDemander fails with assertion on partition move Key: IGNITE-2763 URL: https://issues.apache.org/jira/browse/IGNITE-2763

[jira] [Created] (IGNITE-2692) Set thread local context in IgnitionEx to affect cache functions

Dmitry Karachentsev created IGNITE-2692: --- Summary: Set thread local context in IgnitionEx to affect cache functions Key: IGNITE-2692 URL: https://issues.apache.org/jira/browse/IGNITE-2692

[jira] [Created] (IGNITE-2691) Wrap all Marshaller interface usage to set thread local context in IgnitionEx

Dmitry Karachentsev created IGNITE-2691: --- Summary: Wrap all Marshaller interface usage to set thread local context in IgnitionEx Key: IGNITE-2691 URL: https://issues.apache.org/jira/browse/IGNITE-2691