Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[DOC] Add new property setting fast_double_writer to install documentation #4580

Merged
merged 6 commits into from
Jul 17, 2023
Merged

[DOC] Add new property setting fast_double_writer to install documentation #4580

Changes from 2 commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
dcef569
add new property setting
vagimeli Jul 17, 2023
b9d9feb
Copy edit
vagimeli Jul 17, 2023
2465506
Update index.md
vagimeli Jul 17, 2023
ce0d476
Update _install-and-configure/install-opensearch/index.md
vagimeli Jul 17, 2023
33f280f
Update _install-and-configure/install-opensearch/index.md
vagimeli Jul 17, 2023
ad90338
Update index.md
vagimeli Jul 17, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions _install-and-configure/install-opensearch/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -102,9 +102,9 @@ Do not declare the same JVM options in multiple locations because it can result

## Important system properties

OpenSearch has a number of system properties that you can specify in `config/jvm.options` or `OPENSEARCH_JAVA_OPTS` using `-D` command line argument notation, for example:

- `opensearch.xcontent.string.length.max=<value>`

By default, OpenSearch does not impose any limits on the maximum length of the JSON string fields. To protect your cluster from potential distributed denial-of-service (DDoS) or memory issues, you can set the `opensearch.xcontent.string.length.max` system property to a reasonable limit (the maximum is 2,147,483,647), for example, `-Dopensearch.xcontent.string.length.max=5000000`.
OpenSearch has a number of system properties, listed in the following table, that you can specify in `config/jvm.options` or `OPENSEARCH_JAVA_OPTS` using `-D` command line argument notation.

Property | Description
:---------- | :--------
`opensearch.xcontent.string.length.max=<value>` | By default, OpenSearch does not impose any limits on the maximum length of the JSON string fields. To protect your cluster from potential distributed denial-of-service (DDoS) or memory issues, you can set the `opensearch.xcontent.string.length.max` system property to a reasonable limit (the maximum is 2,147,483,647), for example, `-Dopensearch.xcontent.string.length.max=5000000`. |
vagimeli marked this conversation as resolved.
Show resolved Hide resolved
vagimeli marked this conversation as resolved.
Show resolved Hide resolved
`opensearch.xcontent.fast_double_writer=[true|false]` | By default, OpenSearch uses the floating point parsing capability built in to the Java Runtime Environment. Set this value to true to configure OpenSearch to use the [FastDoubleParser](https://github.com/wrandelshofer/FastDoubleParser) library to parse floating point numbers, which has shown to be faster in many cases. The property can be set to determine whether to use standard Java code to write floats/doubles (default) or use the Schubfach algorithm, which is faster. The latter approach may lead to small differences in the precision of the float/double that is written to the JSON output. Default is `false`. |
vagimeli marked this conversation as resolved.
Show resolved Hide resolved