Smirnov Viacheslav
Smirnov Viacheslav
__Workaround with org.influxdb:influxdb-java:2.23__ ```java //Point from https://github.com/influxdata/influxdb-client-java import com.influxdb.client.write.Point; // Client from https://github.com/influxdata/influxdb-java import org.influxdb.InfluxDB; import org.influxdb.InfluxDBFactory; ... final InfluxDB influxDB = InfluxDBFactory.connect(InfluxDBAddress, Username, Password); influxDB.setDatabase(DataBase); influxDB.setRetentionPolicy(RetentionPolicy); InfluxLineGenerator influxLineGenerator =...
Hey, I'm using similar Dockerfile: ``` FROM mcr.microsoft.com/playwright:v1.44.1 RUN npm install -g artillery RUN npm cache clean --force && rm -rf /root/.cache ENTRYPOINT ["/usr/bin/artillery"] ``` The microsoft team supports playwright...
Hello! I can confirm that the same issue happens with the `influxdb:2.7.6` docker image. I have a big database with many shards. A result of the simple command: `docker run...
offtop_mode_on > I just moved out to victoriaMetrics My teammates would like to have a storage without strict cardinality limits. And they would like to use some complex scripts for...
My current workaround is `docker run --user=influxdb --restart=on-failure --restart unless-stopped --entrypoint '/bin/bash' -d -p 8086:8086 --log-driver=syslog --name influx --env-file env.list -v /home/influxdb:/var/lib/influxdb2 influxdb:2.7.6-alpine --verbose -c "find /var/lib/influxdb2/engine/data/ -type d -name...
I still have the OOM problem. But I have logs. The root cause of the OOM problem is an operation: "TSI log compaction". The first message was about "TSI log...
I used some limits (2) for compactions settings: My settings > Duration at which the storage engine will compact all TSM files in a shard if it hasn’t received writes...
@philjb I will use settings with MEM Limit and GC settings, and I have disabled `INFLUXD_STORAGE_COMPACT_FULL_WRITE_COLD_DURATION`: env.list ``` GOMEMLIMIT=20GiB GOGC=10 INFLUXD_REPORTING_DISABLED=true INFLUXD_STORAGE_CACHE_SNAPSHOT_WRITE_COLD_DURATION=1000d INFLUXD_STORAGE_COMPACT_FULL_WRITE_COLD_DURATION=1000d INFLUXD_STORAGE_COMPACT_THROUGHPUT_BURST=80388608 INFLUXD_STORAGE_MAX_CONCURRENT_COMPACTIONS=1 INFLUXD_STORAGE_SERIES_FILE_MAX_CONCURRENT_SNAPSHOT_COMPACTIONS=1 INFLUXDB_DATA_INDEX_VERSION="tsi1" INFLUXDB_DATA_CACHE_SNAPSHOT_MEMORY_SIZE="200m" INFLUXDB_DATA_MAX_INDEX_LOG_FILE_SIZE=10485760 INFLUXDB_DATA_SERIES_ID_SET_CACHE_SIZE=100...
My current recipe 1. Remove indexes 2. Disable index compactions The custom command `docker run --shm-size 2g --user=influxdb --restart=on-failure --restart unless-stopped --entrypoint '/bin/bash' -d -p 8086:8086 --log-driver=syslog --name influx --env-file...
The second suggestion is about adding new steps/intervals about the Navigation timing. I'm talking about **blocks** and **connections** between the blocks of the diagram: - https://mdn.github.io/shared-assets/images/diagrams/api/performance/timestamp-diagram.svg I used a custom...