[jira] [Commented] (KUDU-3158) Document recommendation to use a dedicated SSD for the WAL
[ https://issues.apache.org/jira/browse/KUDU-3158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17145942#comment-17145942 ] Grant Henke commented on KUDU-3158: --- I agree this needs to be documented so that it isn't viewed as a requirement but as a consideration when picking hardware/resources. I also agree that more concrete data to support it would be useful as well. > 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)
[jira] [Commented] (KUDU-3158) Document recommendation to use a dedicated SSD for the WAL
[ https://issues.apache.org/jira/browse/KUDU-3158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
[jira] [Commented] (KUDU-2612) Implement multi-row transactions
[ https://issues.apache.org/jira/browse/KUDU-2612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17145802#comment-17145802 ] ASF subversion and git services commented on KUDU-2612: --- Commit 396b70b24b80b1b0b362910e56e4da3f09c441e0 in kudu's branch refs/heads/master from Andrew Wong [ https://gitbox.apache.org/repos/asf?p=kudu.git;h=396b70b ] KUDU-2612 p1: add initial transaction status storage This adds a system tablet storage API for storing the status of transactions, in the form of the newly added TxnStatusTablet which is a wrapper around a TabletReplica with a schema tailored for storing transaction metadata. The abstraction is comparable to the SysCatalogTable abstraction used by the master to store metadata about the Kudu catalog, but rather than storing metadata about tables and tablets, the TxnStatusTablet stores metadata about transactions and transaction participants. Partitioning isn't addressed in this patch, but I'm expecting later patches to allow for the creation of partitioned transaction status tables, and having the individual tablet replicas of that table be accessed via this TxnStatusTablet API. This patch only introduces the schema, basic write calls, and scan calls to be used by a transaction management entity to be added in a later patch. There is currently no way to create or define partitions for TxnStatusTablets on tablet servers. Change-Id: I94ddbd37c65932120835d6e138307f819935173c Reviewed-on: http://gerrit.cloudera.org:8080/16043 Reviewed-by: Attila Bukor Reviewed-by: Alexey Serbin Tested-by: Andrew Wong > Implement multi-row transactions > > > Key: KUDU-2612 > URL: https://issues.apache.org/jira/browse/KUDU-2612 > Project: Kudu > Issue Type: Task >Reporter: Mike Percy >Priority: Major > Labels: roadmap-candidate > > Tracking Jira to implement multi-row / multi-table transactions in Kudu. -- This message was sent by Atlassian Jira (v8.3.4#803005)
