accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Newton (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-549) Create infrastructure that supports debugging.
Date Wed, 16 May 2012 02:22:06 GMT


Eric Newton commented on ACCUMULO-549:

I would add: 

 # ability to consume the logs into an accumulo instance so we can query and search 10G of
logs with greater parallelism and speed
 # statistical analysis of traces, which will probably require the accumulo instance to be
be up and running

> Create infrastructure that supports debugging.
> ----------------------------------------------
>                 Key: ACCUMULO-549
>                 URL:
>             Project: Accumulo
>          Issue Type: New Feature
>            Reporter: Keith Turner
>             Fix For: 1.5.0
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message