[
https://issues.apache.org/jira/browse/HDDS-10295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17814515#comment-17814515
]
Tsz-wo Sze commented on HDDS-10295:
-----------------------------------
We may use the rocksdb_ldb tool (provided by Rocksdb) for the moment:
{code}
$ rocksdb_ldb --db=/var/lib/hadoop-ozone/om/data/om.db/ scan
--column_family=transactionInfoTable
#TRANSACTIONINFO ==> 11#282615
$rocksdb_ldb --db=/var/lib/hadoop-ozone/om/data/om.db/ put "#TRANSACTIONINFO"
"11#573145" --column_family=transactionInfoTable
OK
$rocksdb_ldb --db=/var/lib/hadoop-ozone/om/data/om.db/ scan
--column_family=transactionInfoTable
#TRANSACTIONINFO ==> 11#573145
{code}
See also https://github.com/facebook/rocksdb/wiki/RocksDB-Troubleshooting-Guide
> Provide a "ozone debug" subcommand to update the snapshot info in
> transactionInfoTable
> --------------------------------------------------------------------------------------
>
> Key: HDDS-10295
> URL: https://issues.apache.org/jira/browse/HDDS-10295
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Sammi Chen
> Priority: Major
>
> The issue found in HDDS-9342 caused the snapshot info in OM
> transactionInfoTable not get updated timely, so that OM restart failed at
> update ID check during raft log reapply.
> The recover solution is to find the largest update ID, and update the
> snapshot info in transactionInfoTable with this it.
> The task aims to provide such an CLI to update the table. Be noted, the
> largest update ID and its term currently should still need manual find.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
