You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ratis.apache.org by "Josh Elser (Jira)" <ji...@apache.org> on 2019/08/26 23:46:00 UTC
[jira] [Commented] (RATIS-629) Vagrant loadgen does not run
[ https://issues.apache.org/jira/browse/RATIS-629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16916230#comment-16916230 ]
Josh Elser commented on RATIS-629:
----------------------------------
Works for me! Thanks for the fix, Clay.
Committing...
> Vagrant loadgen does not run
> ----------------------------
>
> Key: RATIS-629
> URL: https://issues.apache.org/jira/browse/RATIS-629
> Project: Ratis
> Issue Type: Bug
> Reporter: Clay B.
> Assignee: Clay B.
> Priority: Trivial
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The [vagrant|https://github.com/apache/incubator-ratis/commit/35838f032a4096d78843130fa1435bcddf5ce961] test-harness bits are broken as the load generator does not launch. It fails with the following output:
> {code:java}
> Found /home/vagrant/incubator-ratis/ratis-examples/target/ratis-examples-0.4.0-SNAPSHOT.jar
> 2019-07-20 21:02:13 INFO LogUtils:41 - Set org.apache.ratis.server.impl.RaftServerImpl log level to DEBUG
> 2019-07-20 21:02:13 INFO LogUtils:41 - Set org.apache.ratis.client.RaftClient log level to DEBUG
> Wrong parameters: Can only specify option --peers once.
> Usage: <main class> [command] [command options]
> Commands:
> server Start an filestore server
> Usage: server [options]
> Options:
> * --id, -i
> Raft id of this server
> * --peers, -r
> Raft peers (format: name:host:port,name:host:port)
> --raftGroup, -g
> Raft group identifier
> Default: demoRaftGroup123
> * --storage, -s
> Storage dir
> loadgen Load Generator for FileStore
> Usage: loadgen [options]
> Options:
> * --numFiles
> Number of files
> * --peers, -r
> Raft peers (format: name:host:port,name:host:port)
> --raftGroup, -g
> Raft group identifier
> Default: demoRaftGroup123
> * --size
> Size of each file
> Verification of all Ratis file server logs have the same checksum across all storage directories:
> find: ‘/home/vagrant/test_data/data?’: No such file or directory
> === Command terminated normally (Sat Jul 20 21:02:13 2019) ===
> {code}
> Further, it appears that the servers are no longer logging to the {{screen}} session or the {{server_n*.log}} files.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)