public interface SegmentNodeStorePersistence
Modifier and Type | Method and Description |
---|---|
SegmentArchiveManager |
createArchiveManager(boolean memoryMapping,
boolean offHeapAccess,
IOMonitor ioMonitor,
FileStoreMonitor fileStoreMonitor,
RemoteStoreMonitor remoteStoreMonitor)
Opens a new archive manager.
|
GCJournalFile |
getGCJournalFile()
Create the
GCJournalFile . |
JournalFile |
getJournalFile()
Create the
JournalFile . |
ManifestFile |
getManifestFile()
Create the
ManifestFile . |
RepositoryLock |
lockRepository()
Acquire the lock on the repository.
|
boolean |
segmentFilesExist()
Check if the segment store already contains any segments
|
SegmentArchiveManager createArchiveManager(boolean memoryMapping, boolean offHeapAccess, IOMonitor ioMonitor, FileStoreMonitor fileStoreMonitor, RemoteStoreMonitor remoteStoreMonitor) throws IOException
memoryMapping
- whether the memory mapping should be used (if the given
persistence supports it)offHeapAccess
- whether off heap access for segments should be usedioMonitor
- object used to monitor segment-related IO access. The
implementation should call the appropriate methods when
accessing segments.fileStoreMonitor
- object used to monitor the general IO usage.IOException
boolean segmentFilesExist()
true
is some segments are available for readingJournalFile getJournalFile()
JournalFile
.GCJournalFile getGCJournalFile() throws IOException
GCJournalFile
.IOException
ManifestFile getManifestFile() throws IOException
ManifestFile
.IOException
RepositoryLock lockRepository() throws IOException
The lock can be released manually by calling RepositoryLock.unlock()
.
If the segment node store is shut down uncleanly (eg. the process crashes),
it should be released automatically, so no extra maintenance tasks are
required to run the process again.
IOException
Copyright © 2012–2020 The Apache Software Foundation. All rights reserved.