[
https://issues.apache.org/jira/browse/AMBARI-8173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yusaku Sako updated AMBARI-8173:
--------------------------------
Attachment: AMBARI-8173_branch-1.7.0.patch
> Kafka does not provide any default value for kafka.log.dirs and creates
> confusion / poor UX
> -------------------------------------------------------------------------------------------
>
> Key: AMBARI-8173
> URL: https://issues.apache.org/jira/browse/AMBARI-8173
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, ambari-web, stacks
> Affects Versions: 1.7.0
> Reporter: Yusaku Sako
> Assignee: Sriharsha Chintalapani
> Priority: Critical
> Fix For: 1.7.0
>
> Attachments: AMBARI-8173.patch, AMBARI-8173_branch-1.7.0.patch
>
>
> Kafka does not provide any default value for log.dirs property.
> The user is prompted to enter a path (or paths) there.
> If the user enters paths that kafka user cannot create, then Kafka Broker
> fails to come up and Kafka Service Check fails Once the user goes to the
> dashboard, most of the services show up red as the start operation for other
> components were canceled .
> There are several problems with this.
> 1. Most users will install the full stack including Kafka. The user does not
> know what directory/directories to put there (and does not want to be
> concerned about that at install time). We specify default directories for all
> other components so we should do the same.
> 2. If we leave this blank, then the user is force to enter something. I put
> /kafka. However, Ambari agent does not try to create/chown/chmod, so Kafka
> tries to create the directory as "kafka" user and this fails and you end up
> getting a dashboard with a bunch of services down. Even if we provide some
> default and the user changes it, the same failure occurs. So Ambari agent
> should automatically take care of directory creation/chown/chmod.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
