Influxdata
/
docs-v2
mirror of https://github.com/influxdata/docs-v2.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Update content/shared/v3-core-get-started/_index.md 

Co-authored-by: Jason Stirnaman <jstirnaman@influxdata.com>
pull/5861/head
Jameelah Mercer 2025-02-27 17:01:01 -08:00 committed by GitHub
parent fa9a1bf103
commit d0af3b3742
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
content/shared/v3-core-get-started/_index.md
View File

@ -335,7 +335,10 @@ Using `no_sync=true` is best when prioritizing high-throughput writes over absol
- Default behavior(`no_sync=false`): Waits for data to be written to disk before acknowledging writes. This reduces the risk of data loss but increases latency for writes.
- With `no_sync=true`: Reduces write latency but increases the risk of data loss in case of crashes before WAL persistence.
If you are using the HTTP API, here is an example of how to enable the `no_sync` option:
###### Immediate write using the HTTP API
The `no_sync` parameter controls when writes are acknowledged--for example:
```sh
curl -v "http://localhost:8181/api/v3/write_lp?db=sensors&precision=auto&no_sync=true" \