zstan commented on code in PR #13741: URL: https://github.com/apache/ignite/pull/13741#discussion_r4451524943
########## docs/_docs/server-node-file-system-layout.adoc: ########## @@ -0,0 +1,251 @@ +// Licensed to the Apache Software Foundation (ASF) under one or more +// contributor license agreements. See the NOTICE file distributed with +// this work for additional information regarding copyright ownership. +// The ASF licenses this file to You under the Apache License, Version 2.0 +// (the "License"); you may not use this file except in compliance with +// the License. You may obtain a copy of the License at +// +// https://www.apache.org/licenses/LICENSE-2.0 +// +// Unless required by applicable law or agreed to in writing, software +// distributed under the License is distributed on an "AS IS" BASIS, +// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +// See the License for the specific language governing permissions and +// limitations under the License. + += Server Node File System Layout +:javaFile: {javaCodeDir}/PersistenceTuning.java + +This page brings together recommendations for placing server node files. +Use it to plan disk space, manage retained files, and protect node storage from log and diagnostic growth. + +These recommendations are intended for production server nodes. +On nodes without native persistence, the guidance for the work directory, logs, and JVM diagnostics still applies. + +== Separate File Systems + +Use separate file systems to keep log and diagnostic growth from taking space needed by the node. +For workloads with heavy writes, placing data files and the active WAL on separate devices can also improve write performance. +Choose a layout that fits your workload and available storage. +If several file types share a file system, plan for their combined use, limit retained logs and diagnostic files, and leave free space for checkpoints and WAL rotation. + +Running out of disk space can stop a node and prevent it from restarting. + +A separate file system bounds capacity: directories placed on the same file system share its free space. +It does not by itself reduce I/O contention, which requires a separate device or independently provisioned throughput. +Partitions of one physical disk isolate capacity but still share the failure risk of that disk. + +== Recommended Placement Review Comment: questionable paragraph, as it described - I count 4 'separate FS' near ))) it\`s too huge ) Probably we can suggest to separate pageStore from wal and other are optional ? wdyt ? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
