[IGNITE-4927] Write behind - add an option to skip write coalescing

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 1.9
• Fix Version/s: 2.0
• Assignee: Nikolay Tikhonov
• Reporter: Yakov Zhdanov
• Created: 06/Apr/17 16:46
• Updated: 02/Jun/17 09:06
• Resolved: 18/Apr/17 14:32

Description

Currently, the write-behind store is backed by a map, therefore when several updates come to the same key, they are coalesced.

We need to introduce optional mode and back write-behind with a queue and pass each <k, v> to a database.

Issue Links

• is duplicated by: IGNITE-4933 Need to add an option to write all updates in write-behind store
• is related to: IGNITE-5390 Bug in IgniteCacheTxStoreSessionWriteBehindCoalescingTest
• is related to: IGNITE-4999 Use one thread pool to flush all CacheWriteBehindStore
• relates to: IGNITE-5004 GridCacheWriteBegindStore - remove StatefulValue
• relates to: IGNITE-5005 WriteBehindStore - split flusher's to different classes by writeCoalescing
• relates to: IGNITE-5184 Collect write behind batch with out of order
• relates to: IGNITE-5003 Parallel write&evict same key in CacheWriteBehindStore
• relates to: IGNITE-5043 .NET: CacheConfiguration.WriteBehindCoalescing