You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Will Berkeley (JIRA)" <ji...@apache.org> on 2018/10/26 18:39:00 UTC

[jira] [Created] (KUDU-2615) Add more tools for dealing with the WAL

Will Berkeley created KUDU-2615:
-----------------------------------

             Summary: Add more tools for dealing with the WAL
                 Key: KUDU-2615
                 URL: https://issues.apache.org/jira/browse/KUDU-2615
             Project: Kudu
          Issue Type: Improvement
          Components: log
    Affects Versions: 1.8.0
            Reporter: Will Berkeley
            Assignee: Will Berkeley
             Fix For: 1.9.0


There's only one tool for dealing with WALs, the dump tool, which lets you see what's in the WAL by reading it like a Kudu server would and then dumping it as debug strings.

We could probably use a few more, though. This JIRA serves as a tracking JIRA for new WAL tools and as a parent JIRA for some existing WAL tool JIRAs.

Tools we could add or enhancements we could make:
* 'kudu wal dump --debug' with batch offsets. This would have been useful to me a couple times when I've done WAL surgery.
* 'kudu wal dump repair' maybe with truncate capability (KUDU-1503) or the capability to 'punch out' an entry.
* A 'kudu wal compare' tool that can compare two WALs and show their differences, so the WALs of two replicas of the same tablet could be compared.
* A 'kudu wal edit' tool that can edit some kinds of wal entries-- the use case for this is editing the hostports of peers in config change operations (KUDU-2396).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)