[jira] [Resolved] (KUDU-1193) glog logdir not automatically created if it doesn't exist

["Mike Percy (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KUDU-1193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mike Percy resolved KUDU-1193.
------------------------------
       Resolution: Won't Fix
    Fix Version/s: n/a

[~tlipcon] Hmm, yeah I suppose I agree with you... production deployments would have permissions making auto-creation of the log directory impossible, particularly if the logs live in /var/log/kudu-tserver or something like that.

Marking this as Won't Fix.

> glog logdir not automatically created if it doesn't exist
> ---------------------------------------------------------
>
>                 Key: KUDU-1193
>                 URL: https://issues.apache.org/jira/browse/KUDU-1193
>             Project: Kudu
>          Issue Type: Bug
>            Reporter: Mike Percy
>             Fix For: n/a
>
>
> We should create the logdir if it doesn't exist, but right now we crash. Example:
> {noformat}
> mpercy@mpercy-ThinkPad-T530:/tmp/kudu-foo/master$ $KUDU_HOME/build/latest/kudu-master --fs_data_dirs=$(pwd)/data --fs_wal_dir=$(pwd)/wals --log_dir=$(pwd)/logs
> Could not open file in log_dir /tmp/kudu-foo/master/logs: No such file or directory
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)