Recovery using SharedNothing, eviction and eviction policy 'lru'.
book
Article ID: KB0093914
calendar_today
Updated On:
Products
Versions
TIBCO ActiveSpaces
-
Not Applicable
-
Description
Resolution: Shared nothing has been enabled and capacity for the Space is limited and eviction policy is set to lru. On restart, recovering issued but as-admin "show space" output returns all tuples and the number of evicted tuples is 0.
Example:
as-admin> show space 'dist-limited-bs-readOnly-teste--be_gen_Concepts_test1'
Space Definition: _____________________________________________________________________________________________
Space Name : dist-limited-bs-readOnly-teste--be_gen_Concepts_test1 Space State : ready Distribution Policy : distributed Min Seeders : 1 Replication Count : 1 Replication Policy : sync Capacity : 100 Eviction Policy : lru Cache Policy : read-write through Lock Scope : process Persistence Policy : async Persistence Type : shared nothing Update Transport : unicast Entry TTL : -1 Lock Wait : 0 Lock TTL : -1 Space Wait : 60000 Write Timeout : 60000 Read Timeout : 60000 Virtual Node Count : 1000 Phase Count : -1 Phase Interval : 200 Forget Old Value : false Host Aware Replication : true Routed : false Phase Ratio : 100 Query Limit : 10000 Query Timeout : -1 File Sync Interval : 10000 Version Number : 0
This is expected behavior. During recovery, in order to avoid unnecessary eviction right after completion of recovery, tuples are loaded into memory that are already evicted. TIBCO ActiveSpaces will not load more tuples into local memory as configured.
Note: ActiveSpaces uses memory for each tuple stored in the context of SharedNothing persistence plus eviction. Only the non-indexed portion of a tuple is evicted. The metadata (tuple information) and indexed portion of the tuple is still held in memory, even if the tuple has been evicted.
Issue/Introduction
Recovery using SharedNothing, eviction and eviction policy 'lru'.