You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@skywalking.apache.org by wu...@apache.org on 2018/04/10 14:14:00 UTC
[incubator-skywalking] branch master updated: Collector 5.0.0-alpha
version upgrade FAQ. (#1052)
This is an automated email from the ASF dual-hosted git repository.
wusheng pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-skywalking.git
The following commit(s) were added to refs/heads/master by this push:
new 931f3cf Collector 5.0.0-alpha version upgrade FAQ. (#1052)
931f3cf is described below
commit 931f3cfb50f4365dc44583df32ff7417e2486e9c
Author: 彭勇升 pengys <80...@qq.com>
AuthorDate: Tue Apr 10 22:13:56 2018 +0800
Collector 5.0.0-alpha version upgrade FAQ. (#1052)
* Collector 5.0.0-alpha version upgrade FAQ.
* Update Upgrade.md
Reformat document and adjust some English.
* Add link.
---
docs/README.md | 3 ++-
docs/en/FAQ/Upgrade.md | 12 ++++++++++++
2 files changed, 14 insertions(+), 1 deletion(-)
diff --git a/docs/README.md b/docs/README.md
index a3bb22f..fefc0a6 100644
--- a/docs/README.md
+++ b/docs/README.md
@@ -38,4 +38,5 @@
* [Why only traces in UI?](cn/FAQ/Why-have-traces-no-others.md)
* [Too many GRPC logs in the console](cn/FAQ/Too-many-gRPC-logs.md)
* [The trace doesn't continue in kafka consumer side](en/FAQ/kafka-plugin.md)
-
+ * [Agent or collector version upgrade](en/FAQ/Upgrade.md)
+
\ No newline at end of file
diff --git a/docs/en/FAQ/Upgrade.md b/docs/en/FAQ/Upgrade.md
new file mode 100644
index 0000000..2f18bb8
--- /dev/null
+++ b/docs/en/FAQ/Upgrade.md
@@ -0,0 +1,12 @@
+# Upgrade FAQs
+## Version 3.x -> 5.0.0-alpha
+### Collector
+- **Problem**
+There is no information showing in the UI.
+
+- **Cause**
+In upgrate from 3.2.6 to 5.0.0, Elasticsearch indexes aren't recreated, because not indexes exist, but aren't compatible with 5.0.0-alpha.
+When service name registered, the es will create this column by default type string, which is wrong.
+
+- **Solution**
+Clean the data folder in ElasticSearch and restart ElasticSearch, collector and your under monitoring application.
--
To stop receiving notification emails like this one, please contact
wusheng@apache.org.