[ 
https://issues.apache.org/jira/browse/IGNITE-6030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ivan Rakov updated IGNITE-6030:
-------------------------------
    Description: 
Also, when cache native persistence is disabled, we need to make sure that 
different {{CacheStores}} can be configured on per-cache basis.

New storage configuration design draft:
{noformat}
DataStorageConfiguration
        // old memory configuration
        getConcurrencyLevel
        getDefaultDataRegionName
        getDefaultDataRegionSize
        getDataRegions
        getPageSize
        getSystemRegionInitialSize
        getSystemRegionMaxSize
        // old persistence coniguration
        getCheckpointingFrequency
        getCheckpointingPageBufferSize
        getCheckpointingThreads
        getCheckpointWriteOrder
        getFileIOFactory
        getLockWaitTime
        getPersistentStorePath
        getRateTimeInterval
        getSubIntervals
        getTlbSize
        getWalArchivePath
        getWalAutoArchiveAfterInactivity
        getWalFlushFrequency
        getWalFsyncDelayNanos
        getWalHistorySize
        getWalMode
        getWalRecordIteratorBufferSize
        getWalSegments
        getWalSegmentSize
        getWalStorePath
        isAlwaysWriteFullPages
        isMetricsEnabled
        isWriteThrottlingEnabled

DataRegionConfiguration
        // old memory policy configuration
        getEmptyPagesPoolSize
        getEvictionThreshold
        getInitialSize
        getMaxSize
        getName
        getPageEvictionMode
        getRateTimeInterval
        getSubIntervals
        getSwapFilePath
        isMetricsEnabled
{noformat}

Metrics and MBeans renamings:
{noformat}
PersistenceMetrics -> DataStorageMetrics
PersistenceMetricsMXBean -> DataStorageMetricsMXBean
MemoryMetrics -> DataRegionMetrics
MemoryMetricsMXBean -> DataRegionMetricsMXBean
{noformat}


  was:
Also, when cache native persistence is disabled, we need to make sure that 
different {{CacheStores}} can be configured on per-cache basis.

New storage configuration design draft:
{noformat}
DataStorageConfiguration
        // old memory configuration
        getConcurrencyLevel
        getDefaultDataRegionName
        getDefaultDataRegionSize
        getDataRegions
        getPageSize
        getSystemRegionInitialSize
        getSystemRegionMaxSize
        // old persistence coniguration
        getCheckpointingFrequency
        getCheckpointingPageBufferSize
        getCheckpointingThreads
        getCheckpointWriteOrder
        getFileIOFactory
        getLockWaitTime
        getPersistentStorePath
        getRateTimeInterval
        getSubIntervals
        getTlbSize
        getWalArchivePath
        getWalAutoArchiveAfterInactivity
        getWalFlushFrequency
        getWalFsyncDelayNanos
        getWalHistorySize
        getWalMode
        getWalRecordIteratorBufferSize
        getWalSegments
        getWalSegmentSize
        getWalStorePath
        isAlwaysWriteFullPages
        isMetricsEnabled
        isWriteThrottlingEnabled

DataRegionConfiguration
        getEmptyPagesPoolSize
        getEvictionThreshold
        getInitialSize
        getMaxSize
        getName
        getPageEvictionMode
        getRateTimeInterval
        getSubIntervals
        getSwapFilePath
        isMetricsEnabled
{noformat}

Metrics and MBeans renamings:
{noformat}
PersistenceMetrics -> DataStorageMetrics
PersistenceMetricsMXBean -> DataStorageMetricsMXBean
MemoryMetrics -> DataRegionMetrics
MemoryMetricsMXBean -> DataRegionMetricsMXBean
{noformat}



> Allow enabling persistence per-cache
> ------------------------------------
>
>                 Key: IGNITE-6030
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6030
>             Project: Ignite
>          Issue Type: New Feature
>          Components: persistence
>    Affects Versions: 2.1
>            Reporter: Alexey Goncharuk
>            Assignee: Ivan Rakov
>            Priority: Critical
>              Labels: important
>             Fix For: 2.3
>
>
> Also, when cache native persistence is disabled, we need to make sure that 
> different {{CacheStores}} can be configured on per-cache basis.
> New storage configuration design draft:
> {noformat}
> DataStorageConfiguration
>       // old memory configuration
>       getConcurrencyLevel
>       getDefaultDataRegionName
>       getDefaultDataRegionSize
>       getDataRegions
>       getPageSize
>       getSystemRegionInitialSize
>       getSystemRegionMaxSize
>       // old persistence coniguration
>       getCheckpointingFrequency
>       getCheckpointingPageBufferSize
>       getCheckpointingThreads
>       getCheckpointWriteOrder
>       getFileIOFactory
>       getLockWaitTime
>       getPersistentStorePath
>       getRateTimeInterval
>       getSubIntervals
>       getTlbSize
>       getWalArchivePath
>       getWalAutoArchiveAfterInactivity
>       getWalFlushFrequency
>       getWalFsyncDelayNanos
>       getWalHistorySize
>       getWalMode
>       getWalRecordIteratorBufferSize
>       getWalSegments
>       getWalSegmentSize
>       getWalStorePath
>       isAlwaysWriteFullPages
>       isMetricsEnabled
>       isWriteThrottlingEnabled
> DataRegionConfiguration
>       // old memory policy configuration
>       getEmptyPagesPoolSize
>       getEvictionThreshold
>       getInitialSize
>       getMaxSize
>       getName
>       getPageEvictionMode
>       getRateTimeInterval
>       getSubIntervals
>       getSwapFilePath
>       isMetricsEnabled
> {noformat}
> Metrics and MBeans renamings:
> {noformat}
> PersistenceMetrics -> DataStorageMetrics
> PersistenceMetricsMXBean -> DataStorageMetricsMXBean
> MemoryMetrics -> DataRegionMetrics
> MemoryMetricsMXBean -> DataRegionMetricsMXBean
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to