HDDS-8280. [Auto] Update configuration documentation

docs/05-administrator-guide/02-configuration/99-appendix.md

@@ -395,7 +395,7 @@ This page provides a comprehensive overview of the configuration keys available
 | `ozone.client.stream.buffer.max.size` | 32MB | `CLIENT` | Size which determines at what buffer position write call be blocked till acknowledgement of the first partial flush happens by all servers. |
 | `ozone.client.stream.buffer.size` | 4MB | `CLIENT` | The size of chunks the client will send to the server |
 | `ozone.client.stream.putblock.piggybacking` | false | `CLIENT` | Allow PutBlock to be piggybacked in WriteChunk requests if the chunk is small. Can be enabled only when `ozone.client.hbase.enhancements.allowed` = true |
-| `ozone.client.stream.read.pre-read-size` | 33554432 | `CLIENT` | Extra bytes to prefetch during streaming reads. |
+| `ozone.client.stream.read.pre-read-size` | 33554432 | `CLIENT` | Size of the pre-read window for streaming reads: the number of bytes requested from the datanode ahead of the current read position. The window is refilled in bulk once the bytes requested ahead drop below half of this value. Set to 0 to disable pre-read. |
 | `ozone.client.stream.read.response-data-size` | 1048576 | `CLIENT` | Chunk size of streaming read responses from datanodes. |
 | `ozone.client.stream.read.timeout` | 10s | `CLIENT` | Timeout for receiving streaming read responses. |
 | `ozone.client.stream.readblock.enable` | false | `CLIENT` | Allow ReadBlock to stream all the readChunk in one request. |
@@ -422,7 +422,7 @@ This page provides a comprehensive overview of the configuration keys available
 | `ozone.fs.listing.page.size` | 1024 | `OZONE`, `CLIENT` | Listing page size value used by client for listing number of items on fs related sub-commands output. Kindly set this config value responsibly to avoid high resource usage. Maximum value restricted is 5000 for optimum performance. |
 | `ozone.fs.listing.page.size.max` | 5000 | `OZONE`, `OM` | Maximum listing page size value enforced by server for listing items on fs related sub-commands output. Kindly set this config value responsibly to avoid high resource usage. Maximum value restricted is 5000 for optimum performance. |
 | `ozone.hbase.enhancements.allowed` | false | `OZONE`, `OM` | When set to false, server-side HBase enhancement-related Ozone (experimental) features are disabled (not allowed to be enabled) regardless of whether those configs are set. Here is the list of configs and values overridden when this config is set to false: 1. `ozone.fs.hsync.enabled` = false A warning message will be printed if any of the above configs are overridden by this. |
-| `ozone.http.basedir` |  | `OZONE`, `OM`, `SCM`, `MANAGEMENT` | The base dir for HTTP Jetty server to extract contents. If this property is not configured, by default, Jetty will create a directory inside the directory named by the `${ozone.metadata.dirs}`/webserver. While in production environment, it's strongly suggested instructing Jetty to use a different parent directory by setting this property to the name of the desired parent directory. The value of the property will be used to set Jetty context attribute 'org.eclipse.jetty.webapp.basetempdir'. The directory named by this property must exist and be writeable. |
+| `ozone.http.basedir` |  | `OZONE`, `OM`, `SCM`, `MANAGEMENT` | The base dir for the HTTP Jetty server. If this property is not configured, by default the directory named by `${ozone.metadata.dirs}`/webserver is used. While in a production environment, it's strongly suggested to point this at a different parent directory by setting this property. Under this directory Ozone creates and reuses a per-server subdirectory (named after the server) as Jetty's persistent temp directory; it is kept across restarts rather than deleted on stop. The directory named by this property must exist and be writeable. |
 | `ozone.http.filter.initializers` |  | `OZONE`, `SECURITY`, `KERBEROS` | Set to org.apache.hadoop.security.AuthenticationFilterInitializer to enable Kerberos authentication for Ozone HTTP web consoles is enabled using the SPNEGO protocol. When this property is set, `ozone.security.http.kerberos.enabled` should be set to true. |
 | `ozone.http.policy` | HTTP_ONLY | `OZONE`, `SECURITY`, `MANAGEMENT` | Decide if HTTPS(SSL) is supported on Ozone This configures the HTTP endpoint for Ozone daemons: The following values are supported: - HTTP_ONLY : Service is provided only on http - HTTPS_ONLY : Service is provided only on https - HTTP_AND_HTTPS : Service is provided both on http and https |
 | `ozone.https.client.keystore.resource` | ssl-client.xml | `OZONE`, `SECURITY`, `MANAGEMENT` | Resource file from which ssl client keystore information will be extracted |