[ 
https://issues.apache.org/jira/browse/RATIS-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18041922#comment-18041922
 ] 

Ethan Rose commented on RATIS-2281:
-----------------------------------

The request for this change came from [this 
comment|https://github.com/apache/ozone/pull/8154/files#r2043237901], where we 
added a low level troubleshooting tool to allow manually skipping corrupted 
unapplied raft log entries on all nodes. We are currently deducing which 
segment file has a transaction using a regex on the file name.

> Make getters for start and end index public in LogSegmentStartEnd
> -----------------------------------------------------------------
>
>                 Key: RATIS-2281
>                 URL: https://issues.apache.org/jira/browse/RATIS-2281
>             Project: Ratis
>          Issue Type: Improvement
>          Components: RaftLog
>            Reporter: Tejaskriya
>            Assignee: Abhishek Pal
>            Priority: Minor
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> A helper method to get the start and end index of a segment file will be 
> helpful for any repair tools that want to make changes to the ratis log 
> directly. 
> We could makeĀ {{LogSegmentPath#getStartEnd --> getStartIndex() and 
> getEndIndex()}} publicly accessible to get the range of logs in the file, 
> instead of having to use regex and parse the log file name.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to