[jira] [Commented] (KUDU-3158) Document recommendation to use a dedicated SSD for the WAL

["Todd Lipcon (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KUDU-3158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17145902#comment-17145902 ] 

Todd Lipcon commented on KUDU-3158:
-----------------------------------

Do we have any substantial data showing that this is really a strong recommendation? I've always been hesitant to recommend it, lest people think it's a "requirement" and then avoid using Kudu because SSDs aren't available on their nodes. I think the vast majority of production clusters do _not_ use SSDs and are still successful, so we should make sure to outline what specific scenarios really need/benefit from SSDs.

> Document recommendation to use a dedicated SSD for the WAL
> ----------------------------------------------------------
>
>                 Key: KUDU-3158
>                 URL: https://issues.apache.org/jira/browse/KUDU-3158
>             Project: Kudu
>          Issue Type: Improvement
>          Components: documentation
>            Reporter: Grant Henke
>            Priority: Major
>
> It is a common deployment best practice to place the WAL on its own SSD to maximize ingest throughput in a Kudu cluster. However, we don't clearly document that recommendation in the places users would commonly look for it. 
> It is mentioned somewhat in the FAQ:
> https://kudu.apache.org/faq.html#how-does-kudu-store-its-data-is-the-underlying-data-storage-readable-without-going-through-kudu
> But it should probably be mentioned in these places:
> https://kudu.apache.org/docs/installation.html#prerequisites_and_requirements
> https://kudu.apache.org/docs/configuration.html#directory_configuration
> https://kudu.apache.org/docs/scaling_guide.html
> Alternatively a hardware/deployment guide might be useful, but that is a larger undertaking.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)