You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@htrace.apache.org by "stack (JIRA)" <ji...@apache.org> on 2015/12/09 20:36:10 UTC
[jira] [Created] (HTRACE-325) Error loading datastore: got
zero-length value for shard info key.
stack created HTRACE-325:
----------------------------
Summary: 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)