[
https://issues.apache.org/jira/browse/SAMZA-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14959294#comment-14959294
]
Navina Ramesh commented on SAMZA-626:
-------------------------------------
I used Yan's patch and updated it based on the feedback here ->
https://reviews.apache.org/r/39252/
Although it builds fine and unit tests run properly, it doesn't seem to work
with hello-samza. Seems like when an application holds a lock on the DB, the
tool silently fails to retrieve the key and always ends up getting a null
result. If I stop the application (in this case, Samza job) and run the tool
against the same DB, it seems to work :(
I suspect it could be a silent bug in the rocksdb where the exception is not
being bubbled up or we are not handling it correctly in Java. Anybody seen this
behavior before? [~closeuris] ? [~nickpan47] ?
> Read KV state store for a running job
> -------------------------------------
>
> Key: SAMZA-626
> URL: https://issues.apache.org/jira/browse/SAMZA-626
> Project: Samza
> Issue Type: Sub-task
> Components: kv
> Affects Versions: 0.10.0
> Reporter: Yan Fang
> Assignee: Yan Fang
> Fix For: 0.10.0
>
> Attachments: SAMZA-626.2.patch
>
>
> Provide the tool to connect to kv state store and read the content of the
> store.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
