[
https://issues.apache.org/jira/browse/HTRACE-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15049485#comment-15049485
]
stack commented on HTRACE-325:
------------------------------
That may have been the case here. I was not keeping close account (smile).
Let me close this issue then as dup of that one. Folks searching for this issue
should trip over the above error and will find their way to the HTRACE-298
discussion.
> Error loading datastore: got zero-length value for shard info key.
> -------------------------------------------------------------------
>
> Key: HTRACE-325
> URL: https://issues.apache.org/jira/browse/HTRACE-325
> Project: HTrace
> Issue Type: Bug
> Components: htraced
> Reporter: stack
>
> Starting up htraced, I got this after a crash-down:
> {code}
> kalashnikov:build stack$ ./htraced
> 2015-12-08T21:32:42Z I: *** Starting htraced 4.1.0-incubating-SNAPSHOT
> [220a93e6591404e798f7159ce517cadade170877]***
> 2015-12-08T21:32:42Z I: HTRACED_CONF_DIR defaulting to /etc/htraced/conf
> 2015-12-08T21:32:42Z I: Read configuration:
> 2015-12-08T21:32:42Z I: GOMAXPROCS=8
> 2015-12-08T21:32:42Z I: leveldb version=1.18
> 2015-12-08T21:32:42Z W: Expected to be able to use at least 80 fds per shard,
> but we have 2 shards and -44 total fds to allocate, giving us only -22 FDs
> per shard.2015-12-08T21:32:42Z E: Error loading datastore:
> readShardInfo(/tmp/htrace1/db): got zero-length value for shard info key.
> 2015-12-08T21:32:42Z E: Error creating datastore:
> readShardInfo(/tmp/htrace1/db): got zero-length value for shard info key.
> ...
> {code}
> Can leveldb not recover itself?
> This was using tip of the 4.0 branch yesterday
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
