data structures even with Pages Write Throttling enabled.
Best Regards,
Ivan Rakov
On 22.03.2018 23:20, Dmitry Pavlov wrote:
Hi Igniters,
Why not? Let's release it a bit earlier.
I think it would be good if Ivan will prepare fix for WAL LOG_ONLY:
http://apache-ignite-developers.
Fixes are quite simple.
I expect them to be merged in master in a week in worst case.
Best Regards,
Ivan Rakov
On 22.03.2018 17:49, Denis Magda wrote:
Ivan,
How quick are you going to merge the fix into the master? Many persistence
related optimizations have already stacked up. Probably, we
Thanks all!
We seem to have reached a consensus on this issue. I'll just add
necessary fsyncs under IGNITE-7754.
Best Regards,
Ivan Rakov
On 22.03.2018 15:13, Ilya Lantukh wrote:
+1 for fixing LOG_ONLY. If current implementation doesn't protect from data
corruption, it doesn&#x
Congrats!
Best Regards,
Ivan Rakov
On 22.03.2018 10:08, Vyacheslav Daradur wrote:
Congrats, Dmitry, great work!
On Thu, Mar 22, 2018 at 10:06 AM, Petr Ivanov wrote:
Congratulations, Dmitry!
On 22 Mar 2018, at 01:33, Denis Magda wrote:
The Project Management Committee (PMC) for Apache
r. That implies that we'll be ready to release
AI 2.5 with 7% drop.
2) Introduce LOG_ONLY_SAFE, make it default, add release note to AI 2.5
that we added power loss durability in default mode, but user may
fallback to previous LOG_ONLY in order to retain performance.
Thoughts?
Best Regards,
badly as strong guarantees. I'll
share benchmark results soon.
Best Regards,
Ivan Rakov
On 20.03.2018 5:09, Valentin Kulichenko wrote:
Guys,
What do we understand under "data corruption" here? If a storage is in
corrupted state, does it mean that it needs to be completely r
Ticket to track changes: https://issues.apache.org/jira/browse/IGNITE-7754
Best Regards,
Ivan Rakov
On 16.03.2018 10:58, Dmitriy Setrakyan wrote:
On Fri, Mar 16, 2018 at 12:55 AM, Ivan Rakov wrote:
Vladimir,
Unlike BACKGROUND, LOG_ONLY provides strict write guarantees unless power
loss has
if it will be perceptible,
we'll continue the discussion about introducing LOG_ONLY_SAFE.
Makes sense?
Best Regards,
Ivan Rakov
On 16.03.2018 10:45, Dmitry Pavlov wrote:
Folks, I do not expect any performance degradation here for high load
becase we already do fsync on rollover. So extra fsyn
ch
faster.
Best Regards,
Ivan Rakov
On 16.03.2018 8:17, Dmitriy Setrakyan wrote:
Ivan,
Is there a performance difference between LOG_ONLY and LOG_ONLY_SAFE?
D.
On Thu, Mar 15, 2018 at 4:23 PM, Ivan Rakov wrote:
Igniters and especially Native Persistence experts,
We decided to change defaul
G_ONLY - writes survive process crash, power loss can lead to corruption
LOG_ONLY_SAFE (default) - writes survive process crash, power loss can
lead to last updates loss
FSYNC - writes survive both process crash and power loss
Thoughts?
Best Regards,
Ivan Rakov
don't have such statistics.
It may be bad example, but: in our CI tests we intentionally break grid
in many harsh ways and perform a graceful stop after the test execution,
and it doesn't hang - otherwise we'd see many "Execution timeout" test
suite hangs.
Best Regards,
ng to different clusters". This is possible only in embedded
mode. I think, we shouldn't shock user by sudden JVM halt (possibly,
along with another healthy nodes) if there's a chance of successful node
stop.
Best Regards,
Ivan Rakov
On 14.03.2018 1:47, Dmitriy Setrakyan wrote:
Ivan Rakov created IGNITE-7901:
--
Summary: Refactor Pages Write Throttling: introduce exponential
throttle as separate class
Key: IGNITE-7901
URL: https://issues.apache.org/jira/browse/IGNITE-7901
swap mode over
Ignite Native Persistence.
Igniters, please correct me if there are still any actual cases.
Right now we indeed can configure both Ignite Native Persistence and
swapping, but this makes even less sense. Node will just perform extra
job by persisting data twice.
Best Regards,
Ivan
Ivan Rakov created IGNITE-7751:
--
Summary: Pages Write Throttle mode doesn't protect from checkpoint
buffer overflow
Key: IGNITE-7751
URL: https://issues.apache.org/jira/browse/IGNITE-7751
Pr
oc.
Best Regards,
Ivan Rakov
On 16.02.2018 17:07, Dmitriy Setrakyan wrote:
Igniters, just to clarify, does the term LOG_ONLY mean anything in the
industry or is this just an Ignite term?
D.
On Fri, Feb 16, 2018 at 8:03 AM, Anton Vinogradov
wrote:
Log only mode: flushes application buffers.
So,
it may be scientific - but SYNC sounds scientific as
well).
Best Regards,
Ivan Rakov
On 16.02.2018 15:55, Anton Vinogradov wrote:
>> I had idea to name old default as FSYNC, but it would be too scientific.
So, then it can be FSYNC, SYNC, BACKGROUND and NONE!
On Fri, Feb 16, 2018 at
From my point of view, STRICT is the best option. The name signalizes
to user that this mode provides optional strict guarantees.
FULL_SYNC can be messed with CacheWriteSynchronizationMode#FULL_SYNC. I
don't like the idea of naming different things with same names.
Best Regards,
Ivan Rako
ck of free
space - just delete compressed segments. We should mention it in
documentation for 2.4 release.
Best Regards,
Ivan Rakov
On 13.02.2018 23:53, Dmitry Pavlov wrote:
I see, it seems subgoal 'gain predictable size' can be achieved with
following options:
- https://issues.ap
rent
mode (at least, on filesystems different from XFS). It will be useful
for users who has lots of disk space and want to gain maximum throughput.
Best Regards,
Ivan Rakov
On 13.02.2018 23:14, Dmitry Pavlov wrote:
Hi, I didn't get the point why it may be required to separat
iterators), but feasible.
Best Regards,
Ivan Rakov
On 13.02.2018 22:06, Ivan Rakov wrote:
Yakov,
This will work. However, I expect performance degradation with this
change. Disk storage has a limited number of I/O operations per second
on hardware level. List of already existing disk I/O ac
partition files during checkpoint) will be updated with a new one -
copying from WAL work dir to temp dir.
Best Regards,
Ivan Rakov
On 13.02.2018 21:35, Yakov Zhdanov wrote:
Ivan,
I do not want to create new files. As far as I know, now we copy segments
to archive dir before they get
XFS - fsync time is nearly twice bigger for recently
created files.
Best Regards,
Ivan Rakov
On 13.02.2018 21:22, Yakov Zhdanov wrote:
I meant we still will be copying segment once and then will be moving it to
archive which should not affect file system much.
Thoughts?
--Yakov
2018-02-13 2
ot; term is common in operating systems, and that's why
we'll confuse our "page swapping" (which is essential of Ignite native
persistence) with actual OS page swapping (which usually signals about
ineffective hardware resources usage and is better to be avoided) in
many discus
Ivan Rakov created IGNITE-7475:
--
Summary: Improve VerifyBackupPartitionsTask to calculate partition
hashes in multiple threads
Key: IGNITE-7475
URL: https://issues.apache.org/jira/browse/IGNITE-7475
*Request/Response.
Best Regards,
Ivan Rakov
On 20.12.2017 18:18, Alexey Goncharuk wrote:
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 contri
Ivan Rakov created IGNITE-7182:
--
Summary: Long sorting of pages collection on checkpoint begin can
cause zero dropdown even with throttling enabled
Key: IGNITE-7182
URL: https://issues.apache.org/jira/browse/IGNITE
I agree.
Moreover, peak throughput after long idle period won't be decreased.
Throttling works only during ongoing checkpoint (and probability of
checkpoint running after idle period is very low).
Best Regards,
Ivan Rakov
On 16.11.2017 10:52, Dmitry Pavlov wrote:
Yes, it is correct.
Dmitriy,
Please check description of
https://issues.apache.org/jira/browse/IGNITE-6030, I've updated it with
actual list of properties.
Best Regards,
Ivan Rakov
On 17.10.2017 21:46, Dmitriy Setrakyan wrote:
I am now confused. Can I please ask for the final configuration again? What
wi
(checking both
old-style and new-style paths) is complex and hard to maintain in the
codebase.
Best Regards,
Ivan Rakov
My vote is for *storagePath* and keeping behavior as is.
On 16.10.2017 16:53, Pavel Tupitsyn wrote:
Igniters, another thing to consider:
DataRegionConfiguration.SwapFilePath
Ivan Rakov created IGNITE-6629:
--
Summary: Make service persistence and automatic redeployment
configurable in ServiceConfiguration
Key: IGNITE-6629
URL: https://issues.apache.org/jira/browse/IGNITE-6629
: /storage1/NMVe_drive/storage
walPath: /storage2/Big_SSD_drive/wal
We even recommend this in tuning guide:
https://apacheignite.readme.io/docs/durable-memory-tuning
That's why I think *persistencePath* is misleading.
Best Regards,
Ivan Rakov
On 13.10.2017 5:03, Dmitriy Setrakyan wrote:
O
*
*
Best Regards,
Ivan Rakov
On 12.10.2017 8:05, Dmitriy Setrakyan wrote:
Is the storage path the root folder for the persistence or only the root
path for the main storage?
On Wed, Oct 11, 2017 at 3:54 PM, Denis Magda wrote:
Ivan,
Instead of “setStoragePath” I would suggest “setPersistenceP
Typo in my previous reply: *walArchivePath* -> *setWalArchivePath*
Best Regards,
Ivan Rakov
On 11.10.2017 14:30, Ivan Rakov wrote:
Vladimir,
Thanks for focusing on existing namings. Most of your suggestions
really sound better. I've posted my thoughts under your comment.
By the
st Regards,
Ivan Rakov
On 11.10.2017 14:05, Vladimir Ozerov wrote:
Ivan,
I left some comments in the ticket [1], please take a look.
[1]
https://issues.apache.org/jira/browse/IGNITE-6030?focusedCommentId=16200050&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16
Igniters,
https://issues.apache.org/jira/browse/IGNITE-6030 is ready and enqueued
for TC run.
PR: https://github.com/apache/ignite/pull/2828
Everyone interested in new data storage configuration API, please pay
attention and review.
Best Regards,
Ivan Rakov
On 09.10.2017 12:40, Pavel
Pavel,
Sounds reasonable.
I suggest to include both "data" and "configuration" to make it even
more obvious:
set/getDefaultDataRegionConfiguration
set/getDataRegionConfigurations
Best Regards,
Ivan Rakov
On 09.10.2017 10:51, Pavel Tupitsyn wrote:
Sorry that I'm la
Denis,
Yes, you're right. All cache groups without specific data region
configured will be persistent.
And if you want to add another persistent data region, you should set
*isPeristenceEnabled* flag in its *DataRegionConfiguration* explictly.
Best Regards,
Ivan Rakov
On 02.10.2017
Denis, why do you need to access an instance of the default region bean?
If you want to set any parameter, just instantiate new bean with this
parameter set (like in XML snipped below). Other parameters will be
automatically initialized with their default values.
Best Regards,
Ivan Rakov
On
s persistence will be disabled by default.
I've updated draft in https://issues.apache.org/jira/browse/IGNITE-6030
with these changes.
Best Regards,
Ivan Rakov
On 02.10.2017 18:35, Denis Magda wrote:
To resolve this, I suggest to
introduce just another field defaultRegion
Vladimir,
I like your approach because it's easier to implement.
However, user may be confused by setting *isDefaultPersistenceEnabled*
flag and seeing that persistence is not enabled by default in custom
memory region. I'll add clarifying Javadoc at this place.
Best Regards,
Ivan
abled* property,
which will be used for enabling persistence in corresponding data
region. If value is not set, value of
*DataStorageConfiguration::isDefaultPersistenceEnabled* will be used by
default.
Best Regards,
Ivan Rakov
On 02.10.2017 7:49, Dmitriy Setrakyan wrote:
On Mon, Oct 2, 2017 at 7:
Vladimir,
*DataRegionMetrics* is for former memory metrics.
*DataStorageMetrics* will contain metrics about persistence.
If DataStorageMetrics is ok, let's go this way.
Best Regards,
Ivan Rakov
On 01.10.2017 15:19, Vladimir Ozerov wrote:
We merged memory and persistence on config leve
ics of persistent storage. Probably
*DataStoragePersistenceMetrics*,*PersistentDataStorageMetrics *or even
keeping *PersistenceMetrics* are better.
What do you think?
Best Regards,
Ivan Rakov
On 29.09.2017 21:12, Denis Magda wrote:
Ivan,
Several questions/concerns:
1. Looking at the new
Guys,
I've attached new configuration design draft to the ticket description:
https://issues.apache.org/jira/browse/IGNITE-6030
Please, take a look. Right now is the best time to change name of any
property.
And question about metrics: are we going to rename MemoryMetrics and
PersistenceMetr
Ivan Rakov created IGNITE-6532:
--
Summary: Introduce preallocation in LFS files to avoid high
fragmentation on filesystem level
Key: IGNITE-6532
URL: https://issues.apache.org/jira/browse/IGNITE-6532
Ivan Rakov created IGNITE-6504:
--
Summary: Very quick checkpoint can cause AssertionError on next
start from LFS
Key: IGNITE-6504
URL: https://issues.apache.org/jira/browse/IGNITE-6504
Project: Ignite
Ivan Rakov created IGNITE-6452:
--
Summary: Invocation of getAll() through cache proxy during cache
restart can throw unexpected CacheException
Key: IGNITE-6452
URL: https://issues.apache.org/jira/browse/IGNITE-6452
d fix this in documentation.
Best Regards,
Ivan Rakov
On 14.09.2017 3:46, Denis Magda wrote:
Ivan,
Documented:
https://apacheignite.readme.io/v2.1/docs/durable-memory-tuning
<https://apacheignite.readme.io/v2.1/docs/durable-memory-tuning>
However, I’m a bit confused with you 6. point re
Ivan Rakov created IGNITE-6385:
--
Summary: Offheap page eviction is broken in case loading data
without data streamer
Key: IGNITE-6385
URL: https://issues.apache.org/jira/browse/IGNITE-6385
Project
ult pageSize set
to 4K - since 2.3
Best Regards,
Ivan Rakov
On 13.09.2017 12:29, Ivan Rakov wrote:
Folks,
We had some experience of benchmarking Ignite with persistent store on
SSD. I think we can share some helpful advice. None of them require
changing configuration of Ignite or persistent st
ze of Ignite shouldn't be less
than OS page size. How to check OS cache page size in Unix:
https://unix.stackexchange.com/questions/128213/how-is-page-size-determined-in-virtual-address-space
Best Regards,
Ivan Rakov
On 01.09.2017 21:08, Denis Magda wrote:
Igniters,
I see a lot of compl
Ivan Rakov created IGNITE-6355:
--
Summary: Calculating cache size during cache stop sporadically
fails with ClusterGroupEmptyCheckedException
Key: IGNITE-6355
URL: https://issues.apache.org/jira/browse/IGNITE-6355
Ivan Rakov created IGNITE-6334:
--
Summary: Throttle writing threads during ongoing checkpoint with
token bucket algorithm
Key: IGNITE-6334
URL: https://issues.apache.org/jira/browse/IGNITE-6334
Project
Ivan Rakov created IGNITE-6228:
--
Summary: Avoid closing page store file with
ClosedByInterruptException when user thread is interrupted
Key: IGNITE-6228
URL: https://issues.apache.org/jira/browse/IGNITE-6228
Ivan Rakov created IGNITE-6216:
--
Summary: Add CheckpointWriteOrder enum in .NET persistent store
configuration
Key: IGNITE-6216
URL: https://issues.apache.org/jira/browse/IGNITE-6216
Project: Ignite
Backport issue: https://issues.apache.org/jira/browse/IGNITE-6204
Best Regards,
Ivan Rakov
On 28.08.2017 17:19, Anton Vinogradov wrote:
Igniters,
Seems 2.2 is a urgent bugfix release, so it should be based on 2.1,
In this case all other issues with fixVersion = 2.2 should be moved to 2.3
Ivan Rakov created IGNITE-6204:
--
Summary: Backport optimizations of checkpointing algorithm into 2.2
Key: IGNITE-6204
URL: https://issues.apache.org/jira/browse/IGNITE-6204
Project: Ignite
l-to-false-td20473.html>.
Best Regards,
Ivan Rakov
On 25.08.2017 3:31, Dmitriy Setrakyan wrote:
+1 on the release, let's do it ASAP.
On Thu, Aug 24, 2017 at 12:32 PM, Denis Magda wrote:
Igniters,
Presently every Apache Ignite node requests 80% of RAM from an operating
system. We deba
Ivan Rakov created IGNITE-6183:
--
Summary: Make "Node crashed in the middle of checkpoint" message
softer and more informative
Key: IGNITE-6183
URL: https://issues.apache.org/jira/browse/I
Ivan Rakov created IGNITE-6178:
--
Summary: Make CheckpointWriteOrder.SEQUENTIAL and
checkpointingThreads=4 default in persistent store confguration
Key: IGNITE-6178
URL: https://issues.apache.org/jira/browse/IGNITE
Ivan Rakov created IGNITE-6176:
--
Summary: Request to BinaryMetadataTransport may cause deadlock on
grid stop
Key: IGNITE-6176
URL: https://issues.apache.org/jira/browse/IGNITE-6176
Project: Ignite
Ivan Rakov created IGNITE-6102:
--
Summary: Implement checks that node that joins topology has
consistent database configuration
Key: IGNITE-6102
URL: https://issues.apache.org/jira/browse/IGNITE-6102
most popular
enviroment among users), and recommend user to migrate to 4K-page LFS.
If user still wants to work with 2k pages, he can always set it
explicitly in MemoryConfiguration and start node.
Thoughts?
--
Best Regards,
Ivan Rakov
Ivan Rakov created IGNITE-6033:
--
Summary: Add sorted and multithreaded modes in checkpoint algorithm
Key: IGNITE-6033
URL: https://issues.apache.org/jira/browse/IGNITE-6033
Project: Ignite
Ivan Rakov created IGNITE-6016:
--
Summary: Get rid of checking topology hash in ackTopology
Key: IGNITE-6016
URL: https://issues.apache.org/jira/browse/IGNITE-6016
Project: Ignite
Issue Type
will be automatically
persisted. Efficiency of encoding will be higher than in per-page case.
Thoughts?
The open question for per-partition dictionary is how to
"garbage-collect" it. In per-page case we can do it under page write
lock, but here we have to do it in more tricky way.
Best
Ivan Rakov created IGNITE-5971:
--
Summary: Ignite Continuous Query 2: Flaky failure of
#testMultiThreadedFailover
Key: IGNITE-5971
URL: https://issues.apache.org/jira/browse/IGNITE-5971
Project: Ignite
Ivan Rakov created IGNITE-5970:
--
Summary: Ignite Binary Objects Simple Mapper Basic: Flaky failure
of
org.apache.ignite.p2p.GridP2PLocalDeploymentSelfTest#testConcurrentDeploymentWithDelegatingClassloader
Key: IGNITE-5970
Ivan Rakov created IGNITE-5965:
--
Summary: Ignite Basic: Flaky failure of
GridServiceProcessorMultiNodeConfigSelfTest.testDeployOnEachNodeUpdateTopology
Key: IGNITE-5965
URL: https://issues.apache.org/jira/browse
Ivan Rakov created IGNITE-5961:
--
Summary: Align pages in LFS partition files to pageSize
Key: IGNITE-5961
URL: https://issues.apache.org/jira/browse/IGNITE-5961
Project: Ignite
Issue Type
r - less WAL records to replay.
2) Partition files will be locally consistent after node stop. User will
be able to save partition file for any kind of analysis.
Are they strong enough to force user to wait on stop?
Best Regards,
Ivan Rakov
On 04.08.2017 13:42, Vyacheslav Daradur wrote:
Hi gu
hread hanging
on Ignite.close() may confuse user much more than "crashed in the middle
of checkpoint" message.
Best Regards,
Ivan Rakov
On 03.08.2017 22:34, Dmitry Pavlov wrote:
Hi Igniters,
I’ve created the simplest example using Ignite 2.1 and persistence (see the
code below)
Ivan Rakov created IGNITE-5884:
--
Summary: Change default pageSize of page memory to 4KB
Key: IGNITE-5884
URL: https://issues.apache.org/jira/browse/IGNITE-5884
Project: Ignite
Issue Type
Ivan Rakov created IGNITE-5883:
--
Summary: Ignite Start Nodes test suite is flaky
Key: IGNITE-5883
URL: https://issues.apache.org/jira/browse/IGNITE-5883
Project: Ignite
Issue Type: Bug
Ivan Rakov created IGNITE-5875:
--
Summary: Implement memory metric that will signal about uneven
distribution of pages between segments of durable memory
Key: IGNITE-5875
URL: https://issues.apache.org/jira/browse
Ivan Rakov created IGNITE-5874:
--
Summary: Store TTL expire times in B+ tree on per-partition basis
Key: IGNITE-5874
URL: https://issues.apache.org/jira/browse/IGNITE-5874
Project: Ignite
Issue
Ivan Rakov created IGNITE-5793:
--
Summary: Cache with constant time TTL for entries and enabled
persistence hangs for a long time when TTL expirations start
Key: IGNITE-5793
URL: https://issues.apache.org/jira/browse
Dmitriy,
I agree, hashFunctionScore is more comprehensible.
I'd correct it to "pageHashFunctionScore" to make it clear that it's
about function that distributes pages, not about hashCode() of
user-provided keys.
--
Best Regards,
Ivan Rakov
On 18.07.2017 19:34, Dmitriy Se
difference between maximum
and minimum percentage of segment fill. Greater variance signals about
worse hash function.
Thoughts?
--
Best Regards,
Ivan Rakov
Agree as well.
Best Regards,
Ivan Rakov
On 22.06.2017 1:23, Valentin Kulichenko wrote:
I agree. Ivan, do you have objections?
-Val
On Mon, Jun 19, 2017 at 3:55 PM, Dmitriy Setrakyan
mailto:dsetrak...@apache.org>> wrote:
Ivan,
The semantic now is very confusing, because loca
Semantics in 2.0: if onheap cache enabled, method evicts entry from it.
If onheap cache is disabled (default case), implementation is no-op.
Probably we should keep the method and add some note in javadoc.
Best Regards,
Ivan Rakov
On 19.06.2017 17:01, Igor Sapego wrote:
What if user enables
Semantics in 2.0: if onheap cache is enabled, method evicts entry from
it. If onheap cache is disabled (default case), implementation is no-op.
Probably we should keep the method and add some note in javadoc.
Best Regards,
Ivan Rakov
On 19.06.2017 17:01, Igor Sapego wrote:
What if user
Ivan Rakov created IGNITE-5526:
--
Summary: Dynamic cache stop/start from non-affinity coordinator
node hangs with AssertionError
Key: IGNITE-5526
URL: https://issues.apache.org/jira/browse/IGNITE-5526
Ivan Rakov created IGNITE-5490:
--
Summary: Implement replacement for obsolete
CacheMetrics#getOffHeapAllocatedSize
Key: IGNITE-5490
URL: https://issues.apache.org/jira/browse/IGNITE-5490
Project: Ignite
gards,
Ivan Rakov
On 24.05.2017 19:57, Ivan V. wrote:
Hi, colleagues,
as Ignite caches moved to paged offheap memory , the
IgfsPerBlockLruEvictionPolicy does not seem to work as expected any more,
because
1) interface org.apache.ignite.cache.eviction.EvictionPolicy now only
defines "eviction fr
Ivan Rakov created IGNITE-5215:
--
Summary: Allow user to configure memory policy with maxSize lesser
than default initialSize
Key: IGNITE-5215
URL: https://issues.apache.org/jira/browse/IGNITE-5215
Ivan Rakov created IGNITE-4959:
--
Summary: Possible slight memory leak in free list
Key: IGNITE-4959
URL: https://issues.apache.org/jira/browse/IGNITE-4959
Project: Ignite
Issue Type
Ivan Rakov created IGNITE-4958:
--
Summary: Make data pages recyclable into index/meta/etc pages and
vice versa
Key: IGNITE-4958
URL: https://issues.apache.org/jira/browse/IGNITE-4958
Project: Ignite
Ivan Rakov created IGNITE-4921:
--
Summary: Refactor segments array in PageMemoryNoStoreImpl
Key: IGNITE-4921
URL: https://issues.apache.org/jira/browse/IGNITE-4921
Project: Ignite
Issue Type
mechanism. Do we want to support it for off-heap storage
as well?
Please let me know if my understanding of any algorithm or part of the
system is wrong.
--
Best Regards,
Ivan Rakov
Hello, community!
My name is Ivan. I'm new to the project and want to contribute.
I would like to start with
https://issues.apache.org/jira/browse/IGNITE-4534, will be ready to
provide design sketch soon.
--
Best Regards,
Ivan Rakov
201 - 292 of 292 matches
Mail list logo
