Re: Re[2]: [VOTE] Apache Ignite PMC Chair

+1 Alexey Goncharuk On Thu, Oct 31, 2019 at 12:53 PM Sergey Antonov wrote: > +1 Dmitry Pavlov > > чт, 31 окт. 2019 г. в 13:59, Вячеслав Коптилин : > > > +1 Dmitry Pavlov > > > > Thanks, > > S. > > > > чт, 31 окт. 2019 г. в 12:31, Алексей Платонов : > > > > > +1 for Dmitry Pavlov > > > > > > чт,

Re: DataRegionConfiguration is a FINAL class but could we make it not final?

Hi, I couldn't find any strong reason why this class needs to be final. So, if that is a restriction for you, feel free to create a ticket and submit a pull request. On Fri, Mar 15, 2019 at 11:47 PM hlopez wrote: > Is there a very good reason why the DataRegionConfiguration is a *FINAL* >

Re: New committer: Ilya Lantukh

that it eventually happened. > > > > > > > > пт, 15 февр. 2019 г. в 11:04, Alexey Goncharuk < > agoncha...@apache.org > > >: > > > > > > > > > Dear Ignite Developers, > > > > > > > > > >

Re: Default failure handler was changed for tests

AssertionFailedError(message); > >> > > > >> > > So, yes, for now it is absolutely valid reason to revert and rework > >> fix > >> > > > >> > > - as Nikolay suggested to reduce method override ocurrences. > >> > > - an

Re: Default failure handler was changed for tests

Unfortunately, this FailureHandler doesn't seem to work. I wrote a test that reproduces a bug and should fail. It prints the following text into log, but the test still passes "successfully": [2018-12-07

[jira] [Created] (IGNITE-10392) Client broken cluster where try to connect. Server nodes drop by handler

Ilya Lantukh created IGNITE-10392: - Summary: Client broken cluster where try to connect. Server nodes drop by handler Key: IGNITE-10392 URL: https://issues.apache.org/jira/browse/IGNITE-10392 Project

Re: [ANNOUNCE] Welcome Pavel Kovalenko as a new committer

Congratulations! On Wed, Nov 21, 2018 at 12:30 PM Dmitriy Pavlov wrote: > Congrats, Pavel. Well deserved achievement. > > ср, 21 нояб. 2018 г., 12:09 Nikita Amelchev : > > > Congratulations, Pavel! > > ср, 21 нояб. 2018 г. в 11:47, Vyacheslav Daradur : > > > > > > Congrats Pavel, I'm looking

[jira] [Created] (IGNITE-10186) Revise ability to merge client-only exchanges

Ilya Lantukh created IGNITE-10186: - Summary: Revise ability to merge client-only exchanges Key: IGNITE-10186 URL: https://issues.apache.org/jira/browse/IGNITE-10186 Project: Ignite Issue

[jira] [Created] (IGNITE-10046) MVCC: IgniteCachePrimaryNodeFailureRecoveryAbstractTest.testPessimisticPrimaryNodeFailureRollback hangs sometimes.

Ilya Lantukh created IGNITE-10046: - Summary: MVCC: IgniteCachePrimaryNodeFailureRecoveryAbstractTest.testPessimisticPrimaryNodeFailureRollback hangs sometimes. Key: IGNITE-10046 URL: https://issues.apache.org

Re: Applicability of term 'cache' to Apache Ignite

I thought that current "caches" and "tables" have 1-to-N relation. If that's not a problem, than I also think that "table" is the best term. On Thu, Oct 18, 2018 at 9:29 AM Vladimir Ozerov wrote: > Well, I never thought about term “table” as a replacement for “cache”, but > it appears to be

Re: Applicability of term 'cache' to Apache Ignite

or current users, but in long term it will help new users to understand what Ignite is and what it isn't. And most short-term problems can easily be avoided by keeping @Deprecated IgniteCache. On Wed, Oct 17, 2018 at 2:59 PM Ilya Lantukh wrote: > Unfortunately, we already use the word *"stor

Re: Applicability of term 'cache' to Apache Ignite

Unfortunately, we already use the word *"store"* for many other concepts, like CacheStore and PageStore. I'd prefer to avoid giving it one more meaning. As already mentioned, *"dataset"* has special meaning for ML folks. *"Bucket" *might give wrong association with bucket in a hash table. On

Re: Abbreviation code-style requirement.

+ 1 from me to make abbreviations optional. On Wed, Oct 17, 2018 at 1:00 PM Sergey Antonov wrote: > + 1 > > But, I think that we must leave abbreviations for common words with single > meaning. For example, group -> grp, transaction -> tx, context -> ctx. > > ср, 17 окт. 2018 г. в 12:46, Alexey

Re: Applicability of term 'cache' to Apache Ignite

tore > > key-value pairs and implements JCache API > > - IgniteSql (we’re doing it eventually, right?) is a wrapper around > > IgniteSpace that allows to store SQL tables and implements ANSI SQL > > - IgniteQueue is a wrapper that implements Queue > > and so on. > >

Applicability of term 'cache' to Apache Ignite

Hi Igniters, I would like to rise a question how we use the term *'cache'* in Ignite and how it corresponds to terminology in IT industry in general. >From wikipedia: In computing , a *cache* /kæʃ/ *kash*

Re: The future of Affinity / Topology concepts and possible PME optimizations.

does not affect affinity distribution. > > > > Agree with Dmitriy that we should start with simpler optimizations first. > > > > чт, 13 сент. 2018 г. в 15:58, Ilya Lantukh : > > > > > Igniters, > > > > > > As most of you know, Ignite h

The future of Affinity / Topology concepts and possible PME optimizations.

Igniters, As most of you know, Ignite has a concept of AffinityTopologyVersion, which is associated with nodes that are currently present in topology and a global cluster state (active/inactive, baseline topology, started caches). Modification of either of them involves process called Partition

[jira] [Created] (IGNITE-9400) TC bot: add progress bar to history page

Ilya Lantukh created IGNITE-9400: Summary: TC bot: add progress bar to history page Key: IGNITE-9400 URL: https://issues.apache.org/jira/browse/IGNITE-9400 Project: Ignite Issue Type

[jira] [Created] (IGNITE-9392) CacheAsyncOperationsFailoverTxTest hangs on TC

Ilya Lantukh created IGNITE-9392: Summary: CacheAsyncOperationsFailoverTxTest hangs on TC Key: IGNITE-9392 URL: https://issues.apache.org/jira/browse/IGNITE-9392 Project: Ignite Issue Type

Re: Pessimistic Mode and Transactions and 2PC

Hi John, 1. There is no "begin prepare" record, nodes acquire locks on TX keys and then transfer local TX to PREPARED state. 2. TxRecord is logged when local TX state changes to PREPARED, COMMITED or ROLLED_BACK before sending a response to what you call "coordinator" (in Ignite we use the term

[jira] [Created] (IGNITE-9249) Tests hang when different threads try to start and stop nodes at the same time.

Ilya Lantukh created IGNITE-9249: Summary: Tests hang when different threads try to start and stop nodes at the same time. Key: IGNITE-9249 URL: https://issues.apache.org/jira/browse/IGNITE-9249

[jira] [Created] (IGNITE-9236) Handshake timeout never completes in some tests (GridCacheReplicatedFailoverSelfTest in particular)

Ilya Lantukh created IGNITE-9236: Summary: Handshake timeout never completes in some tests (GridCacheReplicatedFailoverSelfTest in particular) Key: IGNITE-9236 URL: https://issues.apache.org/jira/browse/IGNITE

[jira] [Created] (IGNITE-9213) CacheLockReleaseNodeLeaveTest.testLockTopologyChange hangs sometimes, leading to TC timeout

Ilya Lantukh created IGNITE-9213: Summary: CacheLockReleaseNodeLeaveTest.testLockTopologyChange hangs sometimes, leading to TC timeout Key: IGNITE-9213 URL: https://issues.apache.org/jira/browse/IGNITE-9213

[jira] [Created] (IGNITE-9155) Exception during cluster state change terminates ExchangeWorker

Ilya Lantukh created IGNITE-9155: Summary: Exception during cluster state change terminates ExchangeWorker Key: IGNITE-9155 URL: https://issues.apache.org/jira/browse/IGNITE-9155 Project: Ignite

Re: Quick question on data and index pages

Hi, 1. As the name implies, indirectCount is the count of indirect items, which are references to direct items. According to our DataPage format, we keep all items in the beginning of the page. Take a look at this diagram:

Re: ConcurrentLinkedHashMap works incorrectly after clear()

Thanks for revealing this issue! I don't understand why should we disallow calling clear(). One way how it can be re-implemented is: 1. acquire write locks on all segments; 2. clear them; 3. reset size to 0; 4. release locks. Another approach is to calculate inside

[jira] [Created] (IGNITE-8877) PartitionsExchangeOnDiscoveryHistoryOverflowTest.testDynamicCacheCreation leads to OutOfMemoryError

Ilya Lantukh created IGNITE-8877: Summary: PartitionsExchangeOnDiscoveryHistoryOverflowTest.testDynamicCacheCreation leads to OutOfMemoryError Key: IGNITE-8877 URL: https://issues.apache.org/jira/browse/IGNITE

Re: Enabling Persistent Memory for Ignite

Hi, Thank you for your willingness to contribute. Please assign the Jira ticket to yourself and set it's status to "In Progress", so Apache community can see that this feature is currently being worked on. Also, please open a Github pull request so we can review and give you feedback in a more

[jira] [Created] (IGNITE-8839) Throw meaningful and user-friendly exception when Ignite Persistence files are unaccessible

Ilya Lantukh created IGNITE-8839: Summary: Throw meaningful and user-friendly exception when Ignite Persistence files are unaccessible Key: IGNITE-8839 URL: https://issues.apache.org/jira/browse/IGNITE-8839

[jira] [Created] (IGNITE-8725) Make IGNITE_DISABLE_WAL_DURING_REBALANCING enabled by default

Ilya Lantukh created IGNITE-8725: Summary: Make IGNITE_DISABLE_WAL_DURING_REBALANCING enabled by default Key: IGNITE-8725 URL: https://issues.apache.org/jira/browse/IGNITE-8725 Project: Ignite

[jira] [Created] (IGNITE-8693) SQL JOIN between PARTITIONED and REPLICATED cache fails

Ilya Lantukh created IGNITE-8693: Summary: SQL JOIN between PARTITIONED and REPLICATED cache fails Key: IGNITE-8693 URL: https://issues.apache.org/jira/browse/IGNITE-8693 Project: Ignite

Re: I am sorry for causing confusion. IGNITE-6531

Welcome to Apache Ignite community! The problem with your ticket is that it's not clear what value it adds to the project and how it will improve user experience in general. The problem you described is rather narrow and I am sure it's possible to find a workaround without modifying Ignite code.

Re: IEP-4, Phase 2. Using BL(A)T for in-memory caches.

Eduard, I'm not sure I understand what you mean by "policy". Is it an interface that will have a few default implementations and user will be able to create his own one? If so, could you please write an example of such interface (how you see it) and how and when it's methods will be invoked. On

Re: Atomic caches

Val, The logic you describe changed a while ago, with introduction of persistent storage and cache group mechanics. Currently there might exist multiple special caches where data structures are stored. The main reason for it was to give users ability to put different structures into different

Deprecate CacheRebalanceMode.NONE

Igniters, While working on rebalancing optimizations, I've discovered that we have very weird logic for CacheRebalanceMode.NONE. In this mode we always keep partitions in OWNING state even if their data is outdated, breaking our internal invariants. In this mode every cache.get(...) will lead to

Re: Rebalancing - how to make it faster

ringRebalancing" in IgniteConfiguration. Do you thing such name is meaningful and self-explanatory? Do we need to ensure that it has the same value on every node? Should I make it configurable per cache rather than globally? Please share your thoughts. On Mon, Apr 9, 2018 at 4:32 PM,

Re: Rebalancing - how to make it faster

auling design of Ignite storage mechanism. Right > now > >> we > >> > can > >> > >> afford only to change WAL mode per cache group. > >> > > >> > Cache group rebalancing is a one cache rebalancing, and then this > cache > >&g

Re: Atomic caches

Anton, Please do not use term "atomic cache" for system caches that hold internal data for atomic data structures. This is very confusing. You are right, currently there is no logic that will validate cache configuration. It definitely should be fixed. And having configuration parameters encoded

Re: Rebalancing - how to make it faster

aches. > So, there is no issues for initial rebalancing. > Lets disable WAL on initial rebalancing. > > 2018-03-26 16:46 GMT+03:00 Ilya Lantukh <ilant...@gridgain.com>: > > > Dmitry, > > It is impossible to disable WAL only for certain partitions without > >

Re: Rebalancing - how to make it faster

t disable WAL for the sake of rebalancing; it's too risky. > > > > If you agree, then let's create the IEP. This way it will be easier to > > track this endeavor. BTW, are you already ready to release any > > optimizations in 2.5 that is being discussed in a separate thread? &g

Re: Rebalancing - how to make it faster

- Any chance you had a prototype that shows performance optimizations of >the approach you are suggesting to take? > > -- > Denis > > On Thu, Mar 22, 2018 at 8:38 AM, Ilya Lantukh <ilant...@gridgain.com> > wrote: > > > Igniters, > > > > I've spent some time

Rebalancing - how to make it faster

Igniters, I've spent some time analyzing performance of rebalancing process. The initial goal was to understand, what limits it's throughput, because it is significantly slower than network and storage device can theoretically handle. Turns out, our current implementation has a number of issues

[jira] [Created] (IGNITE-8020) Rebalancing for persistent cache should transfer file store over network instead of using existing supply/demand protocol

Ilya Lantukh created IGNITE-8020: Summary: Rebalancing for persistent cache should transfer file store over network instead of using existing supply/demand protocol Key: IGNITE-8020 URL: https://issues.apache.org

[jira] [Created] (IGNITE-8019) During rebalancing checkpoint read lock is acquired for each entry (twice).

Ilya Lantukh created IGNITE-8019: Summary: During rebalancing checkpoint read lock is acquired for each entry (twice). Key: IGNITE-8019 URL: https://issues.apache.org/jira/browse/IGNITE-8019 Project

[jira] [Created] (IGNITE-8018) Avoid unnecessary unswap(...) call in GridCacheMapEntry.initialValue(...)

Ilya Lantukh created IGNITE-8018: Summary: Avoid unnecessary unswap(...) call in GridCacheMapEntry.initialValue(...) Key: IGNITE-8018 URL: https://issues.apache.org/jira/browse/IGNITE-8018 Project

[jira] [Created] (IGNITE-8017) Disable WAL during initial preloading

Ilya Lantukh created IGNITE-8017: Summary: Disable WAL during initial preloading Key: IGNITE-8017 URL: https://issues.apache.org/jira/browse/IGNITE-8017 Project: Ignite Issue Type

Re: Reconsider default WAL mode: we need something between LOG_ONLY and FSYNC

+1 for fixing LOG_ONLY. If current implementation doesn't protect from data corruption, it doesn't make sence. On Wed, Mar 21, 2018 at 10:38 PM, Denis Magda wrote: > +1 for the fix of LOG_ONLY > > On Wed, Mar 21, 2018 at 11:23 AM, Alexey Goncharuk < >

[jira] [Created] (IGNITE-7961) Rebalance throughput requires optimization

Ilya Lantukh created IGNITE-7961: Summary: Rebalance throughput requires optimization Key: IGNITE-7961 URL: https://issues.apache.org/jira/browse/IGNITE-7961 Project: Ignite Issue Type

[jira] [Created] (IGNITE-7936) Make partition state transfer from OWNING state possible only within exchange.

Ilya Lantukh created IGNITE-7936: Summary: Make partition state transfer from OWNING state possible only within exchange. Key: IGNITE-7936 URL: https://issues.apache.org/jira/browse/IGNITE-7936

[jira] [Created] (IGNITE-7934) Do not checkpoint pages from MOVING partitions

Ilya Lantukh created IGNITE-7934: Summary: Do not checkpoint pages from MOVING partitions Key: IGNITE-7934 URL: https://issues.apache.org/jira/browse/IGNITE-7934 Project: Ignite Issue Type

[jira] [Created] (IGNITE-7935) Add batch put operation to B+ tree implementation.

Ilya Lantukh created IGNITE-7935: Summary: Add batch put operation to B+ tree implementation. Key: IGNITE-7935 URL: https://issues.apache.org/jira/browse/IGNITE-7935 Project: Ignite Issue

[jira] [Created] (IGNITE-7890) Node start with corrupted pds hangs indefinitely.

Ilya Lantukh created IGNITE-7890: Summary: Node start with corrupted pds hangs indefinitely. Key: IGNITE-7890 URL: https://issues.apache.org/jira/browse/IGNITE-7890 Project: Ignite Issue

[jira] [Created] (IGNITE-7857) Extend IgniteWalFlushMultiNodeFailoverAbstractSelfTest to cover MMAP mode

Ilya Lantukh created IGNITE-7857: Summary: Extend IgniteWalFlushMultiNodeFailoverAbstractSelfTest to cover MMAP mode Key: IGNITE-7857 URL: https://issues.apache.org/jira/browse/IGNITE-7857 Project

[jira] [Created] (IGNITE-7831) Throw Exceptions instead of AssertionErrors when reading from corrupted persistence

Ilya Lantukh created IGNITE-7831: Summary: Throw Exceptions instead of AssertionErrors when reading from corrupted persistence Key: IGNITE-7831 URL: https://issues.apache.org/jira/browse/IGNITE-7831

[jira] [Created] (IGNITE-7767) Update WALMode configuration in .NET

Ilya Lantukh created IGNITE-7767: Summary: Update WALMode configuration in .NET Key: IGNITE-7767 URL: https://issues.apache.org/jira/browse/IGNITE-7767 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-7754) WAL in LOG_ONLY mode doesn't execute fsync on checkpoint begin

Ilya Lantukh created IGNITE-7754: Summary: WAL in LOG_ONLY mode doesn't execute fsync on checkpoint begin Key: IGNITE-7754 URL: https://issues.apache.org/jira/browse/IGNITE-7754 Project: Ignite

Re: Apache Ignite 2.4 release

I am OK with either FSYNC or STRICT variant. LOG_ONLY name means "log without fsync". On Fri, Feb 16, 2018 at 4:05 PM, Dmitriy Setrakyan wrote: > On Fri, Feb 16, 2018 at 7:02 AM, Ivan Rakov wrote: > > > Why create a new term to define something

Re: Apache Ignite 2.4 release

Hi all, I'd like to suggest to change default WALMode. Currently we have: DEFAULT (write and fsync), LOG_ONLY (write without fsync), BACKGROUND, NONE. It turns out that fsyncs in current DEFAULT mode significantly restricts Ignite performance. Compared to LOG_ONLY, it offers additional

Re: Author in header of class

I agree with Vyacheslav and Anton Vinogradov. Using @author tag can be misleading, Upsource will provide more up-to-date information. On Wed, Feb 14, 2018 at 3:06 PM, Anton Vinogradov wrote: > +1 to Upsource usage. > > Checked that code ownership provided by Upsource

Re: IGNITE-6005 is ready for review

R [2] > The fix in DataStructuresProcessor.java > > As far as I can see from git log Ilya Lantukh maintains this piece of code. > > Ilya, can you please take a look at the fix? > > [1] https://issues.apache.org/jira/browse/IGNITE-6005 > > [2] https://github.com/apache/ignite/pull/2773 -- Best regards, Ilya

[jira] [Created] (IGNITE-7592) Cache with rebalanceDelay == -1 doesn't trigger late affinity assignment even after explicit rebalance is called on every node

Ilya Lantukh created IGNITE-7592: Summary: Cache with rebalanceDelay == -1 doesn't trigger late affinity assignment even after explicit rebalance is called on every node Key: IGNITE-7592 URL: https

[jira] [Created] (IGNITE-7514) Affinity assignment isn't recalculated if PRIMARY node isn't OWNER

Ilya Lantukh created IGNITE-7514: Summary: Affinity assignment isn't recalculated if PRIMARY node isn't OWNER Key: IGNITE-7514 URL: https://issues.apache.org/jira/browse/IGNITE-7514 Project: Ignite

[jira] [Created] (IGNITE-7502) Baseline topology should affect only persistent caches

Ilya Lantukh created IGNITE-7502: Summary: Baseline topology should affect only persistent caches Key: IGNITE-7502 URL: https://issues.apache.org/jira/browse/IGNITE-7502 Project: Ignite

Re: Ignite Committership Bar Guidance

itters don’t keep an eye on > his/her progress the contributor can remind about personal existence by > sending a message to @dev. ;) > > — > Denis > > > On Dec 23, 2017, at 3:58 AM, Ilya Lantukh <ilant...@gridgain.com> wrote: > > > > Hi Denis, > >

Re: Runtime.availableProcessors() returns hardware's CPU count which is the issue with Ignite in Kubernetes

Hi Yakov, I think that property IGNITE_NODES_PER_HOST, as you suggested, would be confusing, because users might want to reduce amount of available resources for ignite node not only because they run multiple nodes per host, but also because they run other software. Also, in my opinion all types

Re: Ignite Committership Bar Guidance

Hi Denis, Who should take the initiative in promotion? As a contributor who meets those criteria, should I send my application to the PMC or just wait? On Fri, Dec 22, 2017 at 8:24 PM, Denis Magda wrote: > Hi Vyacheslav, > > Some common sense, I presume. A committer who will

Re: Cluster auto activation design proposal

I assume that BaselineNode is intended to be used instead of ClusterNode during affinity assignment calculation. However, it will require that we change signature of AffinityFunction and AffinityFunctionContext methods, which are part of public API. Can we actually do it? On Sat, Nov 4, 2017 at

Re: Monitoring of active transactions

gt; > feature in Ignite. > > > > > > > > Ilya, can you create a ticket and submit it for review? > > > > > > > > D. > > > > > > > > On Fri, Sep 8, 2017 at 7:15 AM, Anton Vinogradov <a...@apache.org> > > wrote: > > >

[jira] [Created] (IGNITE-6384) Introduce API to monitor pending locks and transactions

Ilya Lantukh created IGNITE-6384: Summary: Introduce API to monitor pending locks and transactions Key: IGNITE-6384 URL: https://issues.apache.org/jira/browse/IGNITE-6384 Project: Ignite

[jira] [Created] (IGNITE-6340) Attempting to create the same cache from multiple threads leads to creation of client cache on server node

Ilya Lantukh created IGNITE-6340: Summary: Attempting to create the same cache from multiple threads leads to creation of client cache on server node Key: IGNITE-6340 URL: https://issues.apache.org/jira/browse

Monitoring of active transactions

Igniters, According to our current design and implementation, unclosed transaction or unreleased lock can hang ignite cluster forever. This is logical, and with correct usage of those mechanics such issue should never happen, in real world developers can make mistakes and leave transaction open.

[jira] [Created] (IGNITE-6254) Assertion error in IgniteTxHandler.processDhtTxFinishRequest(...)

Ilya Lantukh created IGNITE-6254: Summary: Assertion error in IgniteTxHandler.processDhtTxFinishRequest(...) Key: IGNITE-6254 URL: https://issues.apache.org/jira/browse/IGNITE-6254 Project: Ignite

[jira] [Created] (IGNITE-6232) Introduce WAL records for partition map exchange start/finish

Ilya Lantukh created IGNITE-6232: Summary: Introduce WAL records for partition map exchange start/finish Key: IGNITE-6232 URL: https://issues.apache.org/jira/browse/IGNITE-6232 Project: Ignite

[jira] [Created] (IGNITE-6212) Assertion error: Invalid node2part

Ilya Lantukh created IGNITE-6212: Summary: Assertion error: Invalid node2part Key: IGNITE-6212 URL: https://issues.apache.org/jira/browse/IGNITE-6212 Project: Ignite Issue Type: Bug

Re: Service versioning

Every Service Grid user will welcome this feature. Fully for it. > > > > Mentioned in the ticket that it has to be documented before the ticket is > > closed. > > > > — > > Denis > > > > > On Aug 15, 2017, at 8:18 AM, Ilya Lantukh <ilant.

[jira] [Created] (IGNITE-6097) GridCacheDatabaseSharedManager.restorePartitionState(...) should not access PageMemory directly

Ilya Lantukh created IGNITE-6097: Summary: GridCacheDatabaseSharedManager.restorePartitionState(...) should not access PageMemory directly Key: IGNITE-6097 URL: https://issues.apache.org/jira/browse/IGNITE-6097

[jira] [Created] (IGNITE-6096) Race between partition eviction and re-creation

Ilya Lantukh created IGNITE-6096: Summary: Race between partition eviction and re-creation Key: IGNITE-6096 URL: https://issues.apache.org/jira/browse/IGNITE-6096 Project: Ignite Issue Type

Service versioning

Igniters, Our current ServiceGrid implementation lacks several important features, one of which is ability to upgrade Service without downtime. I've created ticket to add this feature: https://issues.apache.org/jira/browse/IGNITE-6069. To implement it, the following problems must be solved: -

[jira] [Created] (IGNITE-6069) Service versioning

Ilya Lantukh created IGNITE-6069: Summary: Service versioning Key: IGNITE-6069 URL: https://issues.apache.org/jira/browse/IGNITE-6069 Project: Ignite Issue Type: New Feature

[jira] [Created] (IGNITE-6010) ZookeeperIpFinderTest.testFourNodesKillRestartZookeeper fails sometimes

Ilya Lantukh created IGNITE-6010: Summary: ZookeeperIpFinderTest.testFourNodesKillRestartZookeeper fails sometimes Key: IGNITE-6010 URL: https://issues.apache.org/jira/browse/IGNITE-6010 Project

[jira] [Created] (IGNITE-6009) CacheExamplesSelfTest.testCacheSemaphoreExample fails sometimes due to timeout

Ilya Lantukh created IGNITE-6009: Summary: CacheExamplesSelfTest.testCacheSemaphoreExample fails sometimes due to timeout Key: IGNITE-6009 URL: https://issues.apache.org/jira/browse/IGNITE-6009

[jira] [Created] (IGNITE-6008) CacheRemoveAllSelfTest.testRemoveAll fails sometimes

Ilya Lantukh created IGNITE-6008: Summary: CacheRemoveAllSelfTest.testRemoveAll fails sometimes Key: IGNITE-6008 URL: https://issues.apache.org/jira/browse/IGNITE-6008 Project: Ignite Issue

[jira] [Created] (IGNITE-6007) GridCacheBinaryObjectMetadataExchangeMultinodeTest.testSequentialUpdatesNoConflicts fails sometimes

Ilya Lantukh created IGNITE-6007: Summary: GridCacheBinaryObjectMetadataExchangeMultinodeTest.testSequentialUpdatesNoConflicts fails sometimes Key: IGNITE-6007 URL: https://issues.apache.org/jira/browse/IGNITE

[jira] [Created] (IGNITE-5990) IgniteCachePutAllRestartTest.testStopOriginatingNode fails on TC sometimes

Ilya Lantukh created IGNITE-5990: Summary: IgniteCachePutAllRestartTest.testStopOriginatingNode fails on TC sometimes Key: IGNITE-5990 URL: https://issues.apache.org/jira/browse/IGNITE-5990 Project

[jira] [Created] (IGNITE-5962) Increase max length of index name

Ilya Lantukh created IGNITE-5962: Summary: Increase max length of index name Key: IGNITE-5962 URL: https://issues.apache.org/jira/browse/IGNITE-5962 Project: Ignite Issue Type: Improvement

[jira] [Created] (IGNITE-5794) BinaryMetadata is lost if all server nodes have been restarted

Ilya Lantukh created IGNITE-5794: Summary: BinaryMetadata is lost if all server nodes have been restarted Key: IGNITE-5794 URL: https://issues.apache.org/jira/browse/IGNITE-5794 Project: Ignite

[jira] [Created] (IGNITE-5694) IgniteAtomicLongChangingTopologySelfTest.testClientQueueCreateCloseFailover() fails sometimes

Ilya Lantukh created IGNITE-5694: Summary: IgniteAtomicLongChangingTopologySelfTest.testClientQueueCreateCloseFailover() fails sometimes Key: IGNITE-5694 URL: https://issues.apache.org/jira/browse/IGNITE-5694

[jira] [Created] (IGNITE-5690) JavaEmbeddedIgniteRDDSelfTest sometimes hangs on TC

Ilya Lantukh created IGNITE-5690: Summary: JavaEmbeddedIgniteRDDSelfTest sometimes hangs on TC Key: IGNITE-5690 URL: https://issues.apache.org/jira/browse/IGNITE-5690 Project: Ignite Issue

[jira] [Created] (IGNITE-5689) IgniteCommunicationBalanceTest hangs on Windows

Ilya Lantukh created IGNITE-5689: Summary: IgniteCommunicationBalanceTest hangs on Windows Key: IGNITE-5689 URL: https://issues.apache.org/jira/browse/IGNITE-5689 Project: Ignite Issue Type

[jira] [Created] (IGNITE-5529) Assertion Error in GridDhtPartitionsExchangeFuture : msg == null

Ilya Lantukh created IGNITE-5529: Summary: Assertion Error in GridDhtPartitionsExchangeFuture : msg == null Key: IGNITE-5529 URL: https://issues.apache.org/jira/browse/IGNITE-5529 Project: Ignite

Re: contention on DataStructure creation/removing

uration again. In my understanding, we only need to >> add groupName to Atomics and Collection configuration. >> >> Thoughts? >> >> 2017-06-01 16:32 GMT+03:00 Ilya Lantukh <ilant...@gridgain.com>: >> >>> This is how I see API to create data structures in u

Re: contention on DataStructure creation/removing

This is how I see API to create data structures in user-defined caches: https://github.com/apache/ignite/pull/2058 On Thu, Jun 1, 2017 at 2:56 PM, Ilya Lantukh <ilant...@gridgain.com> wrote: > Hi all, > > There are other problems with current data structures implementation, >

Re: contention on DataStructure creation/removing

Hi all, There are other problems with current data structures implementation, which are related to new persistence mechanics. For example, take a look at this ticket: https://issues.apache.org/jira/browse/IGNITE-5324 I think the best approach is to store data structures not in special system

Re: Message.directType

Yury, All message type IDs are listed in GridIoMessageFactory#create(...) method in switch block. You can check there which IDs are still free. On Fri, May 19, 2017 at 6:44 PM, Yury Babak wrote: > Hi all! > > I want to create new custom implementation of >

[jira] [Created] (IGNITE-5068) Redesign usage of GridDhtPartitionTopologyImpl.part2node map to store only diff from affinity assignment

Ilya Lantukh created IGNITE-5068: Summary: Redesign usage of GridDhtPartitionTopologyImpl.part2node map to store only diff from affinity assignment Key: IGNITE-5068 URL: https://issues.apache.org/jira/browse

Re: IGNITE-4535 : Add option to store deserialized values on-heap

p tests > to test the scenario with on-heap caches. > > D. > > On Tue, Apr 4, 2017 at 8:12 AM, Ilya Lantukh <ilant...@gridgain.com> > wrote: > > > Hi Igniters, > > > > Since review of IGNITE-4535 > > <https://issues.apache.org/jira/bro

IGNITE-4535 : Add option to store deserialized values on-heap

Hi Igniters, Since review of IGNITE-4535 implementation caused some misunderstandings, I'd like to open a discussion here and see if everyone agrees with the chosen approach or can suggest a better one. We are going to re-use existing

Re: IGNITE-4536 metrics of new offheap storage

Denis, Sergey, Changes in https://issues.apache.org/jira/browse/IGNITE-4535 won't be so global. I am not going to replace older mechanics, but rather re-enable and adjust them to work with PageMemory. We will still use the same distributed hash table and evict entries based on existing

[jira] [Created] (IGNITE-3950) Deadlock when exchange happens with pending explicit lock

Ilya Lantukh created IGNITE-3950: Summary: Deadlock when exchange happens with pending explicit lock Key: IGNITE-3950 URL: https://issues.apache.org/jira/browse/IGNITE-3950 Project: Ignite

[jira] [Created] (IGNITE-3014) Optimize GridDhtPartitionTopologyImpl#localPartition()

Ilya Lantukh created IGNITE-3014: Summary: Optimize GridDhtPartitionTopologyImpl#localPartition() Key: IGNITE-3014 URL: https://issues.apache.org/jira/browse/IGNITE-3014 Project: Ignite

  1   2   >