de975c7e2b
* Performance: remove the synchronous persistence mechanism from batch ElasticSearch DAO. Because the current enhanced persistent session mechanism, don't require the data queryable immediately after the insert and update anymore. * Performance: share `flushInterval` setting for both metrics and record data, due to `synchronous persistence mechanism` removed. Record flush interval used to be hardcoded as 10s. * Remove `syncBulkActions` in ElasticSearch storage option. * Increase the default bulkActions(env, SW_STORAGE_ES_BULK_ACTIONS) to 5000(from 1000). * Increase the flush interval of ElasticSearch indices to 15s(from 10s) Add these 2 references. According to these, **(same _index, _type and _id) in same bulk will be in order** 1. https://github.com/elastic/elasticsearch/issues/50199 2. https://discuss.elastic.co/t/order-of--bulk-request-operations/98124 Notice, the order of different bulks is not guaranteed by the ElasticSearch cluster. We are going to have the risk of dirty write. But consider we set over 20s period between flush, and index flush period is 10, we should be safe. Recommend 5000 bulk size and 15s flush interval only. The persistent period has been set to 25s. |
||
|---|---|---|
| .. | ||
| Compatible-with-other-javaagent-bytecode-processing.md | ||
| ES-Server-FAQ.md | ||
| EnhanceRequireObjectCache-Cast-Exception.md | ||
| Hour-Day-Metrics-Stopping.md | ||
| How-to-build-with-mac-m1.md | ||
| Import-Project-Eclipse-RequireItems-Exception.md | ||
| MQ-involved-architecture.png | ||
| Memory-leak-enhance-Worker-thread.md | ||
| Protoc-Plugin-Fails-When-Build.md | ||
| README.md | ||
| Unexpected-endpoint-register.md | ||
| Why-have-traces-no-others.md | ||
| es-version-conflict.md | ||
| install_agent_on_websphere.md | ||
| kafka-plugin.md | ||
| maven-compile-npm-failure.md | ||
| thrift-plugin.md | ||
| time-and-timezone.md | ||
| v3-version-upgrade.md | ||
| v6-version-upgrade.md | ||
| v8-version-upgrade.md | ||
| vnode.md | ||
| why_mq_not_involved.md | ||
README.md
FAQs
These are known and frequently asked questions about SkyWalking. We welcome you to contribute here.
Design
Compiling
- Protoc plugin fails in maven build
- Required items could not be found when importing project into Eclipse
- Maven compilation failure with error such as
python2 not found - Compiling issues on Mac's M1 chip
Runtime
- Elasticsearch exception
type=version_conflict_engine_exceptionsince 8.7.0 - Version 8.x+ upgrade
- Why do metrics indexes with Hour and Day precisions stop updating after upgrade to 7.x?
- Version 6.x upgrade
- Why are there only traces in UI?
- Tracing doesn't work on the Kafka consumer end
- Agent or collector version upgrade, 3.x -> 5.0.0-alpha
- EnhanceRequireObjectCache class cast exception
- ElasticSearch server performance issues, including ERROR CODE:429
- IllegalStateException when installing Java agent on WebSphere 7
- "FORBIDDEN/12/index read-only / allow delete (api)" appears in the log
- No data shown and backend replies with "Variable 'serviceId' has coerced Null value for NonNull type 'ID!'"
- Unexpected endpoint register warning after 6.6.0
- Use the profile exporter tool if the profile analysis is not right
- Compatibility with other javaagent bytecode processes
- Java agent memory leak when enhancing
Worker threadat Thread Pool - Thrift plugin