You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Bakai Ádám (Jira)" <ji...@apache.org> on 2022/11/10 11:59:00 UTC
[jira] [Updated] (KUDU-3421) Make commane line error message more useful
[ https://issues.apache.org/jira/browse/KUDU-3421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bakai Ádám updated KUDU-3421:
-----------------------------
Description:
If the user runs this command for example:
{code:java}
/data/9/abakai/kudu/build/debug% /data/9/abakai/kudu/build/debug/bin/kudu-tserver --fs_data_dirs=/data/9/abakai/kudu/build/debug/tserver-2/data --fs_wal_dir=/data/9/abakai/kudu/build/debug/tserver-2/wal --log_dir=/data/9/abakai/kudu/build/debug/tserver-2/log --rpc_bind_addresses=127.0.0.1:19874 --time_source=system_unsync --unlock_unsafe_flags --webserver_interface=127.0.0.1 --webserver_port=19875 --tserver_master_addrs=127.0.0.1:18764 --webserver_doc_root=/data/9/abakai/kudu/build/debug/../../www --memory_limit_hard_bytes=72050161527 -block_manager log {code}
it works fine. But if the user adds "-logtostderr true", it will throw an error:
{code:java}
[abakai@va1022]/data/9/abakai/kudu/build/debug% /data/9/abakai/kudu/build/debug/bin/kudu-tserver --fs_data_dirs=/data/9/abakai/kudu/build/debug/tserver-2/data --fs_wal_dir=/data/9/abakai/kudu/build/debug/tserver-2/wal --log_dir=/data/9/abakai/kudu/build/debug/tserver-2/log --rpc_bind_addresses=127.0.0.1:19874 --time_source=system_unsync --unlock_unsafe_flags --webserver_interface=127.0.0.1 --webserver_port=19875 --tserver_master_addrs=127.0.0.1:18764 --webserver_doc_root=/data/9/abakai/kudu/build/debug/../../www --memory_limit_hard_bytes=72050161527 -block_manager log -logtostderr true
usage: /data/9/abakai/kudu/build/debug/bin/kudu-tserver {code}
Which doesn't really help to identify which command line option is incorrect (and maybe how is it incorrect)
(By the way the problem with the second command is that logtostderr doesn't need true or false option, it's existence indicates that logtostderr should be switched to true)
was:
If the user runs this command for example:
{code:java}
/data/9/abakai/kudu/build/debug% /data/9/abakai/kudu/build/debug/bin/kudu-tserver --fs_data_dirs=/data/9/abakai/kudu/build/debug/tserver-2/data --fs_wal_dir=/data/9/abakai/kudu/build/debug/tserver-2/wal --log_dir=/data/9/abakai/kudu/build/debug/tserver-2/log --rpc_bind_addresses=127.0.0.1:19874 --time_source=system_unsync --unlock_unsafe_flags --webserver_interface=127.0.0.1 --webserver_port=19875 --tserver_master_addrs=127.0.0.1:18764 --webserver_doc_root=/data/9/abakai/kudu/build/debug/../../www --memory_limit_hard_bytes=72050161527 -block_manager log {code}
it works fine. But if the user adds "-logtostderr true", it will throw an error:
{code:java}
[abakai@va1022]/data/9/abakai/kudu/build/debug% /data/9/abakai/kudu/build/debug/bin/kudu-tserver --fs_data_dirs=/data/9/abakai/kudu/build/debug/tserver-2/data --fs_wal_dir=/data/9/abakai/kudu/build/debug/tserver-2/wal --log_dir=/data/9/abakai/kudu/build/debug/tserver-2/log --rpc_bind_addresses=127.0.0.1:19874 --time_source=system_unsync --unlock_unsafe_flags --webserver_interface=127.0.0.1 --webserver_port=19875 --tserver_master_addrs=127.0.0.1:18764 --webserver_doc_root=/data/9/abakai/kudu/build/debug/../../www --memory_limit_hard_bytes=72050161527 -block_manager log -logtostderr true
usage: /data/9/abakai/kudu/build/debug/bin/kudu-tserver {code}
Which doesn't really help to identify which command line option is incorrect (and maybe how is it incorrect)
> Make commane line error message more useful
> -------------------------------------------
>
> Key: KUDU-3421
> URL: https://issues.apache.org/jira/browse/KUDU-3421
> Project: Kudu
> Issue Type: Improvement
> Components: CLI
> Reporter: Bakai Ádám
> Priority: Major
>
> If the user runs this command for example:
> {code:java}
> /data/9/abakai/kudu/build/debug% /data/9/abakai/kudu/build/debug/bin/kudu-tserver --fs_data_dirs=/data/9/abakai/kudu/build/debug/tserver-2/data --fs_wal_dir=/data/9/abakai/kudu/build/debug/tserver-2/wal --log_dir=/data/9/abakai/kudu/build/debug/tserver-2/log --rpc_bind_addresses=127.0.0.1:19874 --time_source=system_unsync --unlock_unsafe_flags --webserver_interface=127.0.0.1 --webserver_port=19875 --tserver_master_addrs=127.0.0.1:18764 --webserver_doc_root=/data/9/abakai/kudu/build/debug/../../www --memory_limit_hard_bytes=72050161527 -block_manager log {code}
> it works fine. But if the user adds "-logtostderr true", it will throw an error:
> {code:java}
> [abakai@va1022]/data/9/abakai/kudu/build/debug% /data/9/abakai/kudu/build/debug/bin/kudu-tserver --fs_data_dirs=/data/9/abakai/kudu/build/debug/tserver-2/data --fs_wal_dir=/data/9/abakai/kudu/build/debug/tserver-2/wal --log_dir=/data/9/abakai/kudu/build/debug/tserver-2/log --rpc_bind_addresses=127.0.0.1:19874 --time_source=system_unsync --unlock_unsafe_flags --webserver_interface=127.0.0.1 --webserver_port=19875 --tserver_master_addrs=127.0.0.1:18764 --webserver_doc_root=/data/9/abakai/kudu/build/debug/../../www --memory_limit_hard_bytes=72050161527 -block_manager log -logtostderr true
> usage: /data/9/abakai/kudu/build/debug/bin/kudu-tserver {code}
> Which doesn't really help to identify which command line option is incorrect (and maybe how is it incorrect)
> (By the way the problem with the second command is that logtostderr doesn't need true or false option, it's existence indicates that logtostderr should be switched to true)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)