[
https://issues.apache.org/jira/browse/ACCUMULO-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Tubbs resolved ACCUMULO-549.
----------------------------------------
Resolution: Abandoned
Closing this old issue. If this is still a problem, please open a new issue or
PR at https://github.com/apache/accumulo
> Create infrastructure that supports debugging.
> ----------------------------------------------
>
> Key: ACCUMULO-549
> URL: https://issues.apache.org/jira/browse/ACCUMULO-549
> Project: Accumulo
> Issue Type: New Feature
> Reporter: Keith Turner
> Priority: Major
>
> Before a release an extensive amount of testing is done that usually involves
> running test like continuous ingest and random walk on a cluster for extended
> periods of time. When bugs are found by these test it can take a lot of time
> to track the issue down sometimes. Inorder to make tracking these issues
> down easier the write ahead logs are archived. These walogs archives make it
> possible to answer questions about a tablets history because everything ever
> written to the metadata table is there. It would be nice to always have this
> capability on an accumulo system, and have it be easy to use. Spelunking
> around in the write ahead logs is not an easy task.
> It would be nice if accumulo could answer questions like the following.
>
> * Where has a tablet been assigned
> * What compactions has a tablet done
> * What split or merge created a tablet
> These questions can currently be answered with walogs and log4j logs, but its
> painful.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
