[
https://issues.apache.org/jira/browse/SAMZA-598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389191#comment-14389191
]
Yan Fang commented on SAMZA-598:
--------------------------------
{quote}
Gradle provides the scalaConsole target, which brings up the Scala REPL with
all the class files loaded on the classpath. This would be a good entry point
for such an interactive tool.
{quote}
That sounds very promising. Will investigate it after finishing the (1) and
(2). Maybe in another ticket.
{quote}
For (1), I agree, it's problematic if you can't access the DB from a separate
process. I haven't tried this, though. Are you sure it's permanently locked
from outside files? Based on RocksDB's administration page, it sounds like they
support some way to poke at the data from the CLI.
{quote}
Did further investigation. Actually I can not find the [Ldb
Tool|https://github.com/facebook/rocksdb/wiki/Ldb-Tool] mentioned in the
administration page in RocksDB. However, after 3.7 release, there is
openReadOnly method in RocksDB, which supports multiple read-only clients. This
is what we need. Since currently we are using 3.5.1 release, need the Samza to
update to the later versions - SAMZA-442.
> Provide a tool to debug state stores
> ------------------------------------
>
> Key: SAMZA-598
> URL: https://issues.apache.org/jira/browse/SAMZA-598
> Project: Samza
> Issue Type: Bug
> Components: kv
> Affects Versions: 0.9.0
> Reporter: Chris Riccomini
> Fix For: 0.10.0
>
>
> There is currently no easy way to debug a Samza job when there are problems
> with the state store data. It would be nice to provide a tool that will:
> # Connect to a local KV state store, and dump its content.
> # Consume a changelog to and materialize a state store locally.
> Optionally, it would be nice to allow users to fetch values for a give key
> via a REPL. This is a little tricky, though, since the key might be
> serialized in Protobu, Avro, etc.
> Between 1-2, users will be able to inspect local stores of jobs that are
> running (1), and create a local copy of a state store for jobs that have lost
> their local state already (2).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
