Re: IGNITE-6827 - Review needed.

ld be > > PartitionMapExchangePreparationTimeout or PartitionMapExchangeTxTimeout. > > > > Am I missing something? > > > > D. > > > > On Mon, Apr 2, 2018 at 2:48 AM, Alexey Goncharuk < > alexey.goncha...@gmail.com > >> wrote: > > > >>

[jira] [Created] (IGNITE-8160) GridCacheAbstractDataStructuresFailoverSelfTest#testAtomicInitialization flaky-fails on TC

Alexey Goncharuk created IGNITE-8160: Summary: GridCacheAbstractDataStructuresFailoverSelfTest#testAtomicInitialization flaky-fails on TC Key: IGNITE-8160 URL: https://issues.apache.org/jira/browse/IGNITE

Re: Trimming exceptions in IgniteUtils::cast

Stanislav, Thanks for the patch. It is a bit complex change, I will try to review it over the next weekend. --AG 2018-03-12 21:34 GMT+03:00 Valentin Kulichenko < valentin.kuliche...@gmail.com>: > Generally, I think we should not trim any exceptions, because this way we > can unexpectedly

Re: Make TC issues seems to be hung up

or tests fixing seems have no progress . Mainteiners, > > please address. > > > > https://issues.apache.org/jira/browse/IGNITE-7766 > > - Alexei Scherbakov - not responding, if contributor is not interested in > > this test anymore, probably we should remove it from cod

Re: Memory usage per cache

tioned in the tickets. > >- Will it return a value of a respective cache group if the cache is the >only one in the group. >- What will it return if there are several caches in a group? > > -- > Denis > > On Fri, Mar 30, 2018 at 8:16 AM, Alexey Goncharuk < > alexey

[jira] [Created] (IGNITE-8130) WalModeChangeCoordinatorNotAffinityNodeSelfTest#testLocalCache fails sporadically in master

Alexey Goncharuk created IGNITE-8130: Summary: WalModeChangeCoordinatorNotAffinityNodeSelfTest#testLocalCache fails sporadically in master Key: IGNITE-8130 URL: https://issues.apache.org/jira/browse/IGNITE

Re: Contribute to Apache Ignite

Hello Anton, Welcome to the Ignite community! I've added you to the list, please go ahead with the ticket! Thanks, AG 2018-04-03 17:59 GMT+03:00 Anton Kurbanov : > Hello Ignite Community! > > My name is Anton Kurbanov and I want to contribute to Apache Ignite. > > I would

Re: Welcome

Hello Denis, Welcome to the Ignite community! I have added you to the contributors list, you should be able to assign the issue now. Thanks, AG 2018-04-03 16:08 GMT+03:00 Yandex Mail : > Hello Ignite Community! > > > > My name is Denis Garus. I want to contribute to Apache

[jira] [Created] (IGNITE-8115) Add a warning on local node startup if the node is not in Baseline

Alexey Goncharuk created IGNITE-8115: Summary: Add a warning on local node startup if the node is not in Baseline Key: IGNITE-8115 URL: https://issues.apache.org/jira/browse/IGNITE-8115 Project

Re: IGNITE-6827 - Review needed.

Guys, especially Vladimir Ozerov, Yakov Zhanov, Dmitriy Setrakyan, While the technical side of the change is being reviewed, I would also ask you to pay attention to the public API changes here. --AG 2018-03-21 23:43 GMT+03:00 Pavel Tupitsyn : > Hi Alexei, > > > Pavel

Re: Memory usage per cache

gt; > > On Fri, Mar 30, 2018 at 7:32 AM, Alexey Goncharuk < > alexey.goncha...@gmail.com> wrote: > > > Dmitriy, > > > > getLockedKeys returns only the number of locked keys, not the keys > > themselves. Looks like the method name is confusing, should we rena

Re: Memory usage per cache

dex pages. Please confirm that my > > > statement is correct. Also, does that counter accumulates size of > > > BinaryObjects or the whole data/index pages? > > > > > > Finally, do you plan to rework CacheMetrics.getOffHeapAllocatedSize > > method &g

Re: Code inspection

t; > viewType.html?buildTypeId=IgniteTests24Java8_InspectionsCore_ > > > > IgniteTests24Java8=%3Cdefault%3E=buildTypeStatusDiv> > > > > >> ? > > > > >> > > > > >> Sincerely, > > > > >> Dmitriy Pavlov > > >

Re: Memory usage per cache

Denis, Currently there is an easy way to add per-cache-group metrics for data and index pages. There is an internal counter, but it is not published as an MBean metric, we will do this as a part of IEP-6. As for the per-cache metrics, this can be implemented, but it will take a significantly

Re: Welcome

Hello Alexey, Welcome to the Ignite community! I've added you to the contributors list, you should be now able to assign the JIRA ticket. --AG 2018-03-27 18:42 GMT+03:00 Spider (Alexey) : > Hello Ignite Community! > > My name is Aleksey. I want to contribute to Apache

Re: Code inspection

ty > improvement goals. > > > > Did not quite get you about push-to-master prohibition. Can you explain > scenario in more details? > > > > > > > On 6 Mar 2018, at 13:27, Dmitry Pavlov <dpavlov@gmail.com dpavlov@gmail.com>> wrote: > > &

Re: Data compression design proposal

Guys, How does this fit the PageMemory concept? Currently it assumes that the size of the page in memory and the size of the page on disk is the same, so only per-entry level compression within a page makes sense. If you compress a whole page, how do you calculate the page offset in the target

[jira] [Created] (IGNITE-8049) Limit the number of operation cycles in B+Tree

Alexey Goncharuk created IGNITE-8049: Summary: Limit the number of operation cycles in B+Tree Key: IGNITE-8049 URL: https://issues.apache.org/jira/browse/IGNITE-8049 Project: Ignite

[jira] [Created] (IGNITE-8048) Dynamic indexes are not stored to cache data on node join

Alexey Goncharuk created IGNITE-8048: Summary: Dynamic indexes are not stored to cache data on node join Key: IGNITE-8048 URL: https://issues.apache.org/jira/browse/IGNITE-8048 Project: Ignite

Re: IEP-14: Ignite failures handling (Discussion)

Yakov, I agree with Andrey that a separate abstraction for failure handling makes sense. First, using event listeners for this kind of response allows users to install multiple listeners, which may be invoked in an unpredictable order, this looks error-prone to me. Second, we may add an

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

+1 for fixing LOG_ONLY to enforce corruption safety given the provided performance results. 2018-03-21 18:20 GMT+03:00 Vladimir Ozerov : > +1 for accepting drop in LOG_ONLY. 7% is not that much and not a drop at > all, provided that we fixing a bug. I.e. should we implement

Re: welcome

Andrei, Welcome to the community! Added you to the contributors list. 2018-03-21 15:04 GMT+03:00 Andrei Aleksandrov : > Hi Dmitry, > > This one is that I see in my profile: > > Username: >aealeksandrov > > Full name: >Andrey Aleksandrov > > Email: >

Re: 2 phase waiting for partitions release

For now, I think the two-phase await is the only option. After the fix is prototyped we need to benchmark and check what is the impact of this change on PME timing. 2018-03-20 18:09 GMT+03:00 Dmitry Pavlov : > Hi Igniters, > > I prefer option 1 because throwing any

Re: MTCGA: IGNITE-7791 and GridDhtPartitionsSingleMessage

Hello Maxim, SingleMessage with exchId=null is sent when a node updates local partitions' state and schedules a background cluster notification. In contrast, when a partition map exchange happends, it is completed with exchId != null. I need more context regarding how this message interferes

[jira] [Created] (IGNITE-7967) DataRegionMetrics#totalAllocatedPages is invalid if metrics were enabled during runtime

Alexey Goncharuk created IGNITE-7967: Summary: DataRegionMetrics#totalAllocatedPages is invalid if metrics were enabled during runtime Key: IGNITE-7967 URL: https://issues.apache.org/jira/browse/IGNITE-7967

Re: Atomic sequence and topology exception

Pavel, The exception from an AtomicSequence looks like a bug to me. Ignite should retry all operations that do not involve user's logic, this stands for AtomicSequence. I believe such handling already present in AtomicLong, so it should not be difficult to fix. The only case when a user must

Re: Data eviction/expiration from Ignite persistence

ook consistent product wide. > > -- > Denis > > On Tue, Mar 13, 2018 at 12:50 AM, Alexey Goncharuk < > alexey.goncha...@gmail.com> wrote: > > > Denis, > > > > What do you mean by 'current behavior when data is evicted from the > memory > > o

Re: Data eviction/expiration from Ignite persistence

for this tree. --AG 2018-03-13 15:30 GMT+03:00 Dmitriy Setrakyan <dsetrak...@apache.org>: > > > On Tue, Mar 13, 2018 at 3:50 AM, Alexey Goncharuk < > alexey.goncha...@gmail.com> wrote: > >> Denis, >> >> What do you mean by 'current behavior when

Re: IEP-14: Ignite failures handling (Discussion)

I also like "kill if standalone, stop if embedded" by default. A use can change it to kill for embedded mode, but it will be a controlled safe choice. 2018-03-13 11:26 GMT+03:00 Vladimir Ozerov : > +1 for "kill if standalone, stop if embedded". We should never kill a >

Re: Data eviction/expiration from Ignite persistence

y Pavlov > > > > пн, 12 мар. 2018 г. в 23:32, Denis Magda <dma...@gridgain.com>: > > > > > Alexey, Dmitriy, > > > > > > What would be the configuration parameter that defines if the eviction > > > should happen in the in-memory layer only or in both

Re: Data eviction/expiration from Ignite persistence

ry and persistence? > > -Val > > On Sat, Mar 10, 2018 at 12:06 AM, Alexey Goncharuk < > alexey.goncha...@gmail.com> wrote: > > > The ticket [1] is in patch available state looks good, the only thing > left > > there is to transfer old entries to new storage. I hope

Re: [VOTE] Apache Ignite 2.4.0 RC1

+1 (binding) Build from source: OK Start nodes with persistence, couple of BLT changes: OK Ssserj, as for the persistence issue you are talking about - you are hitting the issue [1] which is almost finished, but did not make it to the 2.4 release. As the affects version is 2.1, this is not a

Re: Data eviction/expiration from Ignite persistence

The ticket [1] is in patch available state looks good, the only thing left there is to transfer old entries to new storage. I hope Andrey will have time to finish this soon, so we can target the fix for 2.5. [1] https://issues.apache.org/jira/browse/IGNITE-5874 2018-03-09 22:51 GMT+03:00 Denis

Re: Request for contributor permissions

Ivan, Welcome to the community! I've added you to the contributors list. --AG 2018-03-06 16:52 GMT+03:00 Ivan Daschinsky : > Hello Ignite Community! > > My name is Ivan Daschinskiy. I want to contribute to Apache Ignite and want > to start with this issue - IGNITE-6860 >

Re: Transparent Data Encryption (TDE) in Apache Ignite

ecords for encrypted pages? > > I don't have an answer to this questions for now. > So, prior to starting an implementation we returns with answers. > > [1] https://docs.oracle.com/javase/7/docs/api/java/security/KeyStore.html > [2] https://1drv.ms/w/s!AqZdfua4UpmuhneoVhOCiXSUBGIf > > &g

Re: Code inspection

Dmitriy, I like this idea a lot. For example, the inspection profile should have inspection 'Anonymous class can be converted to lambda' disabled because quite a lot of such classes can be sent over the network (although even anonymous classes are discourage for such purposes). I believe we can

Re: Transparent Data Encryption (TDE) in Apache Ignite

My bad, the correct link is https://issues.apache.org/jira/browse/IGNITE-5829 2018-03-06 13:04 GMT+03:00 Alexey Goncharuk <alexey.goncha...@gmail.com>: > Guys, > > I think this TDE proposal is not thought through enough yet. Please > consider the following points when writing t

Re: Transparent Data Encryption (TDE) in Apache Ignite

Guys, I think this TDE proposal is not thought through enough yet. Please consider the following points when writing the IEP: * How encryption keys will be stored and accessed? If the encryption key is stored with the same permissions as the main data storage, the whole exercise with encryption

Re: Let's keep Apache Ignite docs up-to-date

Igniters, Bumping up this discussion. I have recently found out that we have this process for documenting new releases [1] which looks quite ridiculous to me. First, creating a copy of page with next-version suffix is inconvenient and error-prone: the next-version page is not visible to anyone,

[jira] [Created] (IGNITE-7842) testPutReaderUpdatePrimaryFails1 fails on TC

Alexey Goncharuk created IGNITE-7842: Summary: testPutReaderUpdatePrimaryFails1 fails on TC Key: IGNITE-7842 URL: https://issues.apache.org/jira/browse/IGNITE-7842 Project: Ignite Issue

[jira] [Created] (IGNITE-7836) ExchangeFuture misses onBaselineTopologyChanged callback when forceReassignment is false

Alexey Goncharuk created IGNITE-7836: Summary: ExchangeFuture misses onBaselineTopologyChanged callback when forceReassignment is false Key: IGNITE-7836 URL: https://issues.apache.org/jira/browse/IGNITE-7836

[jira] [Created] (IGNITE-7819) IgniteServiceConfigVariationsFullApiTest must stop services in finally block

Alexey Goncharuk created IGNITE-7819: Summary: IgniteServiceConfigVariationsFullApiTest must stop services in finally block Key: IGNITE-7819 URL: https://issues.apache.org/jira/browse/IGNITE-7819

[jira] [Created] (IGNITE-7812) Slow rebalancing in case of enabled persistence

Alexey Goncharuk created IGNITE-7812: Summary: Slow rebalancing in case of enabled persistence Key: IGNITE-7812 URL: https://issues.apache.org/jira/browse/IGNITE-7812 Project: Ignite

Re: Apache Ignite 2.4 release

In terms of 'safety', Ignite default settings are far beyond optimal. For in-memory mode, we have 0 backups by default, which means partition loss in a case of node failure, we have readFromBackup=true and PRIMARY_SYNC by default which effectively cancels linearizability property for cache

Re: Semaphore Stuck when no acquirers to assign permit

Hi Vladislav, Can you please finalize the review? I would like to include the fix in one of the nightly Ignite builds for my own project. Thanks. --AG 2018-02-01 4:47 GMT+03:00 Dmitriy Setrakyan : > Hi Tim, Vlad, > > Any update on this ticket? I looked inside, but cannot

[jira] [Created] (IGNITE-7722) IgnitePdsCheckpointSimulationWithRealCpDisabledTest generates too many strings

Alexey Goncharuk created IGNITE-7722: Summary: IgnitePdsCheckpointSimulationWithRealCpDisabledTest generates too many strings Key: IGNITE-7722 URL: https://issues.apache.org/jira/browse/IGNITE-7722

[jira] [Created] (IGNITE-7713) Include cache name to rebalancing finish message

Alexey Goncharuk created IGNITE-7713: Summary: Include cache name to rebalancing finish message Key: IGNITE-7713 URL: https://issues.apache.org/jira/browse/IGNITE-7713 Project: Ignite

Re: EvictableEntry.isCached() state meaning

Andrey, isCached() may return false if the entry was concurrently removed from the heap (note that EvictableEntry covers only on-heap evictions since it is passed to the instance of an EvictionPolicy). Any cache access of the entry key (get or update) will bring the entry back on-heap. --AG

[jira] [Created] (IGNITE-7698) Page read during replacement should be outside of segment write lock

Alexey Goncharuk created IGNITE-7698: Summary: Page read during replacement should be outside of segment write lock Key: IGNITE-7698 URL: https://issues.apache.org/jira/browse/IGNITE-7698 Project

[jira] [Created] (IGNITE-7694) testActiveClientReconnectToInactiveCluster hangs because of an assertion

Alexey Goncharuk created IGNITE-7694: Summary: testActiveClientReconnectToInactiveCluster hangs because of an assertion Key: IGNITE-7694 URL: https://issues.apache.org/jira/browse/IGNITE-7694

[jira] [Created] (IGNITE-7692) affinityCall and affinityRun may execute code on backup partitions

Alexey Goncharuk created IGNITE-7692: Summary: affinityCall and affinityRun may execute code on backup partitions Key: IGNITE-7692 URL: https://issues.apache.org/jira/browse/IGNITE-7692 Project

[jira] [Created] (IGNITE-7689) IgnitePdsBinaryMetadataOnClusterRestartTest flaky fails on TC

Alexey Goncharuk created IGNITE-7689: Summary: IgnitePdsBinaryMetadataOnClusterRestartTest flaky fails on TC Key: IGNITE-7689 URL: https://issues.apache.org/jira/browse/IGNITE-7689 Project

[jira] [Created] (IGNITE-7678) Persistence: newly created cache creates partitions in MOVING state

Alexey Goncharuk created IGNITE-7678: Summary: Persistence: newly created cache creates partitions in MOVING state Key: IGNITE-7678 URL: https://issues.apache.org/jira/browse/IGNITE-7678 Project

[jira] [Created] (IGNITE-7677) CacheBaselineTopologyTest flaky-fails on TC

Alexey Goncharuk created IGNITE-7677: Summary: CacheBaselineTopologyTest flaky-fails on TC Key: IGNITE-7677 URL: https://issues.apache.org/jira/browse/IGNITE-7677 Project: Ignite Issue

[jira] [Created] (IGNITE-7644) Add an utility to export all key-value data from a persisted partition

Alexey Goncharuk created IGNITE-7644: Summary: Add an utility to export all key-value data from a persisted partition Key: IGNITE-7644 URL: https://issues.apache.org/jira/browse/IGNITE-7644

Re: Text query with persistence

Hi Dmitriy, We do have a ticket for this [1], however, I am not sure it will be completed any time soon. As for the rebuilding indexes at the node startup, we already have an internal routine for this (see GridQueryIndexing#rebuildIndexesFromHash). The only thing we need to implement is skipping

Re: Apache Ignite 2.4 release

Guys, Thanks to Dmitriy Pavlov we found the ticket [1] which causes a major slowdown when page replacement starts. Even though it's not a regression, I suggest we consider it a blocker for 2.4 because this is a huge performance issue which can make it virtually impossible to use native

Re: Eviction policies with persistence

n phase? If it’s true then it’s still a page based > eviction - we select 5 random oldest pages and purge all the key-values > from them. > > — > Denis > > > On Feb 4, 2018, at 12:05 PM, Alexey Goncharuk < > alexey.goncha...@gmail.com> wrote: > > > >

[jira] [Created] (IGNITE-7640) Refactor DiscoveryDataClusterState to be immutable

Alexey Goncharuk created IGNITE-7640: Summary: Refactor DiscoveryDataClusterState to be immutable Key: IGNITE-7640 URL: https://issues.apache.org/jira/browse/IGNITE-7640 Project: Ignite

[jira] [Created] (IGNITE-7639) NullPointerException in publicApiActiveState

Alexey Goncharuk created IGNITE-7639: Summary: NullPointerException in publicApiActiveState Key: IGNITE-7639 URL: https://issues.apache.org/jira/browse/IGNITE-7639 Project: Ignite Issue

[jira] [Created] (IGNITE-7619) Documentation: using native persistence with CacheStore

Alexey Goncharuk created IGNITE-7619: Summary: Documentation: using native persistence with CacheStore Key: IGNITE-7619 URL: https://issues.apache.org/jira/browse/IGNITE-7619 Project: Ignite

Re: Eviction policies with persistence

Guys, To clarify the questions, I would like to reiterate over the mechanics of evictions and then suggest a renaming that should resolve such things in the future. First of all, Lucas is right - eviction policy only makes sense when native persistence is disabled because what it does is

[jira] [Created] (IGNITE-7618) validateCache synchronously waits for state change

Alexey Goncharuk created IGNITE-7618: Summary: validateCache synchronously waits for state change Key: IGNITE-7618 URL: https://issues.apache.org/jira/browse/IGNITE-7618 Project: Ignite

[jira] [Created] (IGNITE-7581) TxPessimisticDeadlockDetectionTest.testDeadlocksLocal hangs on TC

Alexey Goncharuk created IGNITE-7581: Summary: TxPessimisticDeadlockDetectionTest.testDeadlocksLocal hangs on TC Key: IGNITE-7581 URL: https://issues.apache.org/jira/browse/IGNITE-7581 Project

Re: cache operation failed after transaction rolled back due to deadlock

Aleksey, thanks, we will take a look at this ticket and fix it in 2.5. 2018-01-23 19:57 GMT+03:00 Yakov Zhdanov : > Alex Goncharuk, can you please take a look and comment? Test seems to be > valid from my standpoint. > > Yakov Zhdanov, > www.gridgain.com > > 2018-01-22

[jira] [Created] (IGNITE-7577) GridClusterStateProcessor#publicApiActiveState returns false when baseline change is in progress

Alexey Goncharuk created IGNITE-7577: Summary: GridClusterStateProcessor#publicApiActiveState returns false when baseline change is in progress Key: IGNITE-7577 URL: https://issues.apache.org/jira/browse

Re: IGNITE_HOME for persistence

Denis, Dmitriy, I do not think the behavior should be in any way specific to the case when persistence is enabled. We have quite a bit of other information (such as binary marshaller metadata and marshaller class mappings) that are also stored in the work folder and may be required after the

[jira] [Created] (IGNITE-7573) IgniteOfflineBaselineNodeFullApiSelfTest.testSize fails

Alexey Goncharuk created IGNITE-7573: Summary: IgniteOfflineBaselineNodeFullApiSelfTest.testSize fails Key: IGNITE-7573 URL: https://issues.apache.org/jira/browse/IGNITE-7573 Project: Ignite

[jira] [Created] (IGNITE-7569) Index rebuild future is created too late

Alexey Goncharuk created IGNITE-7569: Summary: Index rebuild future is created too late Key: IGNITE-7569 URL: https://issues.apache.org/jira/browse/IGNITE-7569 Project: Ignite Issue Type

[jira] [Created] (IGNITE-7510) IgnitePdsClientNearCachePutGetTest fails flaky on TC

Alexey Goncharuk created IGNITE-7510: Summary: IgnitePdsClientNearCachePutGetTest fails flaky on TC Key: IGNITE-7510 URL: https://issues.apache.org/jira/browse/IGNITE-7510 Project: Ignite

Re: Partition loss policy to disable cache completely

Valentin, I am ok with having a policy which prohibits all cache operations, and this is not very hard to implement. Although, I agree with Yakov - I do not see any point in reducing cluster availability when operations can be safely completed. 2018-01-23 2:22 GMT+03:00 Yakov Zhdanov

[jira] [Created] (IGNITE-7505) Node not in baseline topology may initialize local partition

Alexey Goncharuk created IGNITE-7505: Summary: Node not in baseline topology may initialize local partition Key: IGNITE-7505 URL: https://issues.apache.org/jira/browse/IGNITE-7505 Project: Ignite

[jira] [Created] (IGNITE-7471) Use soft reference for checkpoint entry contents to avoid excessive memory usage

Alexey Goncharuk created IGNITE-7471: Summary: Use soft reference for checkpoint entry contents to avoid excessive memory usage Key: IGNITE-7471 URL: https://issues.apache.org/jira/browse/IGNITE-7471

[jira] [Created] (IGNITE-7453) PageSnapshot uses direct invocation of DirectBuffer.clean()

Alexey Goncharuk created IGNITE-7453: Summary: PageSnapshot uses direct invocation of DirectBuffer.clean() Key: IGNITE-7453 URL: https://issues.apache.org/jira/browse/IGNITE-7453 Project: Ignite

[jira] [Created] (IGNITE-7324) AssertionError Entry cannot become obsolete when DHT local candidate is added in deadlock detection suite

Alexey Goncharuk created IGNITE-7324: Summary: AssertionError Entry cannot become obsolete when DHT local candidate is added in deadlock detection suite Key: IGNITE-7324 URL: https://issues.apache.org/jira

[jira] [Created] (IGNITE-7308) Caches info is updated on cluster change finish message in discovery thread

Alexey Goncharuk created IGNITE-7308: Summary: Caches info is updated on cluster change finish message in discovery thread Key: IGNITE-7308 URL: https://issues.apache.org/jira/browse/IGNITE-7308

[jira] [Created] (IGNITE-7290) Log when partition is moved to a LOST state

Alexey Goncharuk created IGNITE-7290: Summary: Log when partition is moved to a LOST state Key: IGNITE-7290 URL: https://issues.apache.org/jira/browse/IGNITE-7290 Project: Ignite Issue

Re: Transaction classes naming

> looks really obfuscating for new contributor, since in fact they are not > adapters for something but abstract superclasses. > > 2017-12-20 18:18 GMT+03:00 Alexey Goncharuk <alexey.goncha...@gmail.com>: > > > Igniters, > > > > As I review transaction-related

Transaction classes naming

Igniters, As I review transaction-related PRs and communicate with other fellow Igniters, I realized that our transaction classes naming became inconsistent and almost impossible to explain to a new contributor. A few examples: 1) We have a GridNearTxLocal class, but Near in the name does not

[jira] [Created] (IGNITE-7254) Add more ways to activate a cluster to the error message for an inactive cluster

Alexey Goncharuk created IGNITE-7254: Summary: Add more ways to activate a cluster to the error message for an inactive cluster Key: IGNITE-7254 URL: https://issues.apache.org/jira/browse/IGNITE-7254

[jira] [Created] (IGNITE-7235) Add warning with with a list of restrictions when Ignite native persistence is used with write-though cache store

Alexey Goncharuk created IGNITE-7235: Summary: Add warning with with a list of restrictions when Ignite native persistence is used with write-though cache store Key: IGNITE-7235 URL: https://issues.apache.org

Re: IgniteProjectionStartStopRestartSelfTest is failing for about a week on TC

This may be related to the recent changes in TC infrastructure. I see the following in remote nodes output: nohup: ignoring input /data/teamcity/work/820be461cd64b574/bin/ignite.sh, ERROR: The version of JAVA installed in JAVA_HOME= is incorrect. Please point JAVA_HOME variable to installation of

Re: Rework locking architecture for MVCC and transactional SQL

ifferent temporal stuff: > > 1) Locks > > 2) UNDO data > > 3) Sort/join data (for SELECT and CREATE INDEX, statistics, whatsoever) > > 4) If needed - visibility info (e.g. for covering indexes and > purge/vacuum) > > > > WDYT? > > > > Vladimir

Re: Rework locking architecture for MVCC and transactional SQL

Vladimir, What about moving the entire locking mechanism to a separate off-heap memory region which will be volatile wrt restarts, but will still support off-load to disk. In the current architecture, it means that we will need to allocate a separate DataRegion with no WAL and no crash recovery -

Re: MVCC version format

Vladimir, Although at the first glance this seems to be ok for a local solution, I have a few concerns wrt distributed version behavior: 1) I cannot say that epoch switch in this approach will be an extremely rare event. Let's say a user regularly deploys a new version of application code to a

Re: How properly handle IgniteOOM

Mikhail, Here is the first idea that came to my mind. Before a transaction is committed (or an atomic update is applied), we have all entries being written on hands. We can estimate the maximum amount of memory required for this to happen and make a reservation (one AtomicLong CAS) for this

[jira] [Created] (IGNITE-7194) Limit the number of collection elements printed in S.toString()

Alexey Goncharuk created IGNITE-7194: Summary: Limit the number of collection elements printed in S.toString() Key: IGNITE-7194 URL: https://issues.apache.org/jira/browse/IGNITE-7194 Project

[jira] [Created] (IGNITE-7177) Custom discovery messages from plugins are handled incorrectly

Alexey Goncharuk created IGNITE-7177: Summary: Custom discovery messages from plugins are handled incorrectly Key: IGNITE-7177 URL: https://issues.apache.org/jira/browse/IGNITE-7177 Project

[jira] [Created] (IGNITE-7017) Reconsider WAL archive strategy

Alexey Goncharuk created IGNITE-7017: Summary: Reconsider WAL archive strategy Key: IGNITE-7017 URL: https://issues.apache.org/jira/browse/IGNITE-7017 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-7016) Avoid fsync on WAL rollover in non-default mode

Alexey Goncharuk created IGNITE-7016: Summary: Avoid fsync on WAL rollover in non-default mode Key: IGNITE-7016 URL: https://issues.apache.org/jira/browse/IGNITE-7016 Project: Ignite

[jira] [Created] (IGNITE-6957) Reduce excessive int boxing when accessing cache by ID

Alexey Goncharuk created IGNITE-6957: Summary: Reduce excessive int boxing when accessing cache by ID Key: IGNITE-6957 URL: https://issues.apache.org/jira/browse/IGNITE-6957 Project: Ignite

[jira] [Created] (IGNITE-6956) Reduce excessive iterator allocations during GridDhtPartitionMap instantiation

Alexey Goncharuk created IGNITE-6956: Summary: Reduce excessive iterator allocations during GridDhtPartitionMap instantiation Key: IGNITE-6956 URL: https://issues.apache.org/jira/browse/IGNITE-6956

Re: IGNITE-6802 is ready for review (NullPointerException when WAL store and WAL archive paths are same )

Dmitriy, I added comments to the upsource review, please take a look. 2017-11-17 15:57 GMT+03:00 Дмитрий Рябов : > Hello, Igniters! Please review. > > JIRA: https://issues.apache.org/jira/browse/IGNITE-6802 > PR: https://github.com/apache/ignite/pull/3021/files >

Re: Stop Ignite opening 47500 and 47100

Hi, You can implement your own no-op discovery and communication SPIs and plug them in IgniteConfiguration, then no network ports will be opened. --AG 2017-11-17 16:05 GMT+03:00 karthik : > In our Project we are not allowed to open any port. Is it possible to >

[jira] [Created] (IGNITE-6947) Near optimistic prepare future should abandon remap after failed map attempt

Alexey Goncharuk created IGNITE-6947: Summary: Near optimistic prepare future should abandon remap after failed map attempt Key: IGNITE-6947 URL: https://issues.apache.org/jira/browse/IGNITE-6947

[jira] [Created] (IGNITE-6939) Exclude false owners from the execution plan based on query response

Alexey Goncharuk created IGNITE-6939: Summary: Exclude false owners from the execution plan based on query response Key: IGNITE-6939 URL: https://issues.apache.org/jira/browse/IGNITE-6939 Project

[jira] [Created] (IGNITE-6933) Consider executing updates in-place when SQL indexes are present or object size is smaller than the old object size

Alexey Goncharuk created IGNITE-6933: Summary: Consider executing updates in-place when SQL indexes are present or object size is smaller than the old object size Key: IGNITE-6933 URL: https

Re: collocated compute and off-heap cache

Dmitriy, There will be no performance overhead for reads, but there will be a significant performance overhead for writes because each update must be changed in offheap, and since the offheap will be very small, there will be a lot of pages reads and spills. 2017-11-15 6:53 GMT+03:00 Dmitriy

Fair affinity resurrection with baseline topology

Igniters, After spending some time on baseline topology review, it came to my mind that we can return stateful affinity functions for persistent caches. Since now we will have a topology which is persisted to the cluster metastore, why not save the partition affinity distribution together with

Re: Cluster auto activation design proposal

Sounds good to me. 2017-11-08 10:48 GMT+03:00 Dmitriy Setrakyan <dsetrak...@apache.org>: > How about BaseNode? > > On Wed, Nov 8, 2017 at 2:40 PM, Alexey Goncharuk < > alexey.goncha...@gmail.com > > wrote: > > > Dmitriy, > > > > An offline node is

<    1   2   3   4   5   6   7   8   9   10   >