[
https://issues.apache.org/jira/browse/HBASE-4132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13109793#comment-13109793
]
dhruba borthakur commented on HBASE-4132:
-----------------------------------------
I am getting back to this one. Here is the modified proposal as suggested by
Andrew. I will remove WALActionsListener.logRolled and introduce the following
methods to WALActionsListener:
{code}
/**
* The WAL is going to be rolled.
* @param oldPath the path to the old hlog
* @param newPath the path to the new hlog
*/
public void preLogRoll(Path oldPath, Path newPath) throws IOException;
/**
* The WAL has been rolled.
* @param oldPath the path to the old hlog
* @param newPath the path to the new hlog
*/
public void postLogRoll(Path oldPath, Path newPath) throws IOException;
/**
* The WAL is going to be archived.
* @param oldPath the path to the old hlog
* @param newPath the path to the new hlog
*/
public void preLogArchive(Path oldPath, Path newPath) throws IOException;
/**
* The WAL has been archived.
* @param oldPath the path to the old hlog
* @param newPath the path to the new hlog
*/
public void postLogArchive(Path oldPath, Path newPath) throws IOException;
{code}
> Extend the WALActionsListener API to accomodate log archival
> ------------------------------------------------------------
>
> Key: HBASE-4132
> URL: https://issues.apache.org/jira/browse/HBASE-4132
> Project: HBase
> Issue Type: Improvement
> Components: regionserver
> Reporter: dhruba borthakur
> Fix For: 0.94.0
>
> Attachments: walArchive.txt
>
>
> The WALObserver interface exposes the log roll events. It would be nice to
> extend it to accomodate log archival events as well.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
