Class SegmentCacheManager
-
Nested Class Summary
Nested ClassesModifier and TypeClassDescriptionstatic final classException which someone can throw to indicate to the Actor that whatever it was doing is not needed anymore.static classstatic final classCommand to flush a particular region from cache.static classResult of aSegmentCacheManager.FlushCommand.classRegistry of all the indexes that were created for this cache manager, perRolapStar.static interfaceVisitor for messages (commands and events). -
Field Summary
FieldsModifier and TypeFieldDescriptionfinal ExecutorServiceExecutor with which to send requests to external caches.final SegmentCachefinal List<SegmentCacheWorker>final ExecutorServiceExecutor with which to execute SQL requests.final Thread -
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescription<T> Texecute(SegmentCacheManager.Command<T> command) voidexternalSegmentCreated(SegmentHeader header, MondrianServer server) Tells the cache that a segment is newly available in an external cache.voidexternalSegmentDeleted(SegmentHeader header, MondrianServer server) Tells the cache that a segment is no longer available in an external cache.getConverter(RolapStar star, SegmentHeader header) booleanloadCacheForStar(RolapStar star) Load external cached elements for received star.voidloadFailed(RolapStar star, SegmentHeader header, Throwable throwable) Informs cache manager that a segment load failed.voidloadSucceeded(RolapStar star, SegmentHeader header, SegmentBody body) Adds a segment to segment index.peek(CellRequest request) Makes a quick request to the aggregation manager to see whether the cell value required by a particular cell request is in external cache.voidprintCacheState(CacheControl.CellRegion region, PrintWriter pw, Locus locus) voidremove(RolapStar star, SegmentHeader header) Removes a segment from segment index.voidshutdown()Shuts down this cache manager and all active threads and indexes.
-
Field Details
-
thread
-
cacheExecutor
Executor with which to send requests to external caches. -
sqlExecutor
Executor with which to execute SQL requests.TODO: create using factory and/or configuration parameters. Executor should be shared within MondrianServer or target JDBC database.
-
segmentCacheWorkers
-
compositeCache
-
-
Constructor Details
-
SegmentCacheManager
-
-
Method Details
-
loadCacheForStar
Load external cached elements for received star. Similar toexternalSegmentCreatedbut the index is created if not there.- Parameters:
star- the star for which the cache is loaded- Returns:
- true if elements existed for this star.
-
execute
-
getIndexRegistry
-
loadSucceeded
Adds a segment to segment index.Called when a SQL statement has finished loading a segment.
Does not add the segment to the external cache. That is a potentially long-duration operation, better carried out by a worker.
- Parameters:
header- segment headerbody- segment body
-
loadFailed
Informs cache manager that a segment load failed.Called when a SQL statement receives an error while loading a segment.
- Parameters:
header- segment headerthrowable- Error
-
remove
Removes a segment from segment index.Call is asynchronous. It comes back immediately.
Does not remove it from the external cache.
- Parameters:
header- segment header
-
externalSegmentCreated
Tells the cache that a segment is newly available in an external cache. -
externalSegmentDeleted
Tells the cache that a segment is no longer available in an external cache. -
printCacheState
-
shutdown
public void shutdown()Shuts down this cache manager and all active threads and indexes. -
getConverter
-
peek
Makes a quick request to the aggregation manager to see whether the cell value required by a particular cell request is in external cache.'Quick' is relative. It is an asynchronous request (due to the aggregation manager being an actor) and therefore somewhat slow. If the segment is in cache, will save batching up future requests and re-executing the query. Win should be particularly noticeable for queries running on a populated cache. Without this feature, every query would require at least two iterations.
Request does not issue SQL to populate the segment. Nor does it try to find existing segments for rollup. Those operations can wait until next phase.
Client is responsible for adding the segment to its private cache.
- Parameters:
request- Cell request- Returns:
- Segment with data, or null if not in cache
-