public class OverflowMetadata extends Object
Modifier and Type | Field and Description |
---|---|
long |
lastCommitTime
The last commit time on the old journal.
|
protected static org.apache.log4j.Logger |
log |
boolean |
postProcess
Set
true iff asynchronous post-processing should be
performed. |
ResourceManager |
resourceManager
The resource manager.
|
Constructor and Description |
---|
OverflowMetadata(ResourceManager resourceManager)
Captures various metadata about the live journal in preparation for a
synchronous overflow operation.
|
Modifier and Type | Method and Description |
---|---|
int |
getActionCount(OverflowActionEnum action)
Return the #of index partitions for which the specified action was
chosen.
|
int |
getActiveCount()
The #of active index partitions on this data service.
|
int |
getIndexCount()
The #of indices on the old journal.
|
com.bigdata.resources.Score |
getScore(String name)
Return
true if the named index partition is "warm" for
ITx.UNISOLATED and/or ITx.READ_COMMITTED operations. |
List<com.bigdata.resources.Score> |
getScores()
The scores in order from least active to most active.
|
com.bigdata.resources.ViewMetadata |
getViewMetadata(String name)
Random lookup of the
ViewMetadata . |
boolean |
isCopied(String name)
True if the tuples for the index were copied to the new live journal
during synchronous overflow.
|
void |
setAction(String name,
OverflowActionEnum action)
Specify the action to be taken.
|
Iterator<com.bigdata.resources.ViewMetadata> |
views()
The views that are being processed in index name order.
|
protected static final org.apache.log4j.Logger log
public final ResourceManager resourceManager
public final long lastCommitTime
public boolean postProcess
true
iff asynchronous post-processing should be
performed. Flag is set iff some indices are NOT copied onto the new
journal such that asynchronous post-processing should be performed.public OverflowMetadata(ResourceManager resourceManager)
Note: This captures metadata which has low latency and does not force the
materialization of the fused view of an index partition but may force the
loading of the BTree
from the old journal, which it itself a very
light weight operation.
resourceManager
- public final com.bigdata.resources.ViewMetadata getViewMetadata(String name)
ViewMetadata
.name
- The index name.ViewMetadata
and null
if none is
found.IllegalStateException
- if #collectMoreData(ResourceManager)
has not been
called.public Iterator<com.bigdata.resources.ViewMetadata> views()
public int getIndexCount()
public boolean isCopied(String name)
name
- The name of the index partition.public void setAction(String name, OverflowActionEnum action)
name
- The index partition name.action
- The action.IllegalStateException
- if an action has already been specified.public int getActionCount(OverflowActionEnum action)
action
- The action.public int getActiveCount()
public List<com.bigdata.resources.Score> getScores()
public com.bigdata.resources.Score getScore(String name)
true
if the named index partition is "warm" for
ITx.UNISOLATED
and/or ITx.READ_COMMITTED
operations.
Note: This method informs the selection of index partitions that will be
moved to another IDataService
. The preference is always to move
an index partition that is "warm" rather than "hot" or "cold". Moving a
"hot" index partition causes more latency since more writes will have
been buffered and unisolated access to the index partition will be
suspended during the atomic part of the move operation. Likewise, "cold"
index partitions are not consuming any resources other than disk space
for their history, and the history of an index is not moved when the
index partition is moved.
Since the history of an index partition is not moved when the index
partition is moved, the determination of cold, warm or hot is made in
terms of the resources consumed by ITx.READ_COMMITTED
and
ITx.UNISOLATED
access to named index partitions. If an index
partition is hot for historical read, then your only choices are to shed
other index partitions from the data service, to read from a failover
data service having the same index partition, or possibly to increase the
replication count for the index partition.
name
- The name of an index partition.Score
-or- null
iff the index
was not touched for read-committed or unisolated operations.Copyright © 2006–2019 SYSTAP, LLC DBA Blazegraph. All rights reserved.