w3ll1ngt commented on code in PR #13741:
URL: https://github.com/apache/ignite/pull/13741#discussion_r4443536735


##########
docs/_docs/server-node-file-system-layout.adoc:
##########
@@ -0,0 +1,230 @@
+// 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
+
+Plan disk space separately for persistent data, WAL, retained WAL segments, 
snapshots, logs, and JVM diagnostics.
+If these files share a file system, growth in one directory can exhaust the 
space needed by the others.
+A failed write to Ignite data, WAL, or metadata can cause the node to stop.
+A full file system can also prevent the node from restarting.
+
+These recommendations apply to production server nodes.
+For nodes without native persistence, the recommendations for the work 
directory, logs, and JVM diagnostics still apply.

Review Comment:
   thx, did it more readable imho
   @ On nodes without native persistence, the guidance for the work directory, 
logs, and JVM diagnostics still applies.



-- 
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]

Reply via email to