[GitHub] [skywalking] TinyAllen commented on issue #3276: Skywalking UI blank

2019-08-16 Thread GitBox
TinyAllen commented on issue #3276: Skywalking UI blank
URL: https://github.com/apache/skywalking/issues/3276#issuecomment-522196804
 
 
   @SevenBlue2018 Can you give me your response body data, l think it may has a 
broken link in it.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[skywalking] branch master updated: Module config set override is not working (#3283)

2019-08-16 Thread wusheng
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/skywalking.git


The following commit(s) were added to refs/heads/master by this push:
 new 029  Module config set override is not working (#3283)
029 is described below

commit 029e9a89c85e2dc0493286c4d5a562e748c8
Author: 吴晟 Wu Sheng 
AuthorDate: Sat Aug 17 10:10:30 2019 +0800

Module config set override is not working (#3283)

* set Override is not working.

* Submodule update

* Add header.
---
 .../StorageModuleElasticsearchConfig.java   | 21 +
 skywalking-ui   |  2 +-
 2 files changed, 18 insertions(+), 5 deletions(-)

diff --git 
a/oap-server/server-storage-plugin/storage-elasticsearch-plugin/src/main/java/org/apache/skywalking/oap/server/storage/plugin/elasticsearch/StorageModuleElasticsearchConfig.java
 
b/oap-server/server-storage-plugin/storage-elasticsearch-plugin/src/main/java/org/apache/skywalking/oap/server/storage/plugin/elasticsearch/StorageModuleElasticsearchConfig.java
index 5ba6692..e8a0fc6 100644
--- 
a/oap-server/server-storage-plugin/storage-elasticsearch-plugin/src/main/java/org/apache/skywalking/oap/server/storage/plugin/elasticsearch/StorageModuleElasticsearchConfig.java
+++ 
b/oap-server/server-storage-plugin/storage-elasticsearch-plugin/src/main/java/org/apache/skywalking/oap/server/storage/plugin/elasticsearch/StorageModuleElasticsearchConfig.java
@@ -47,11 +47,24 @@ public class StorageModuleElasticsearchConfig extends 
ModuleConfig {
 private int otherMetricsDataTTL = 0;
 @Setter private int monthMetricsDataTTL = 18;
 
-public void setOtherMetricsDataTTL(int otherMetricsDataTTL) {
+public int getMinuteMetricsDataTTL() {
 if (otherMetricsDataTTL > 0) {
-minuteMetricsDataTTL = otherMetricsDataTTL;
-hourMetricsDataTTL = otherMetricsDataTTL;
-dayMetricsDataTTL = otherMetricsDataTTL;
+return otherMetricsDataTTL;
 }
+return minuteMetricsDataTTL;
+}
+
+public int getHourMetricsDataTTL() {
+if (otherMetricsDataTTL > 0) {
+return otherMetricsDataTTL;
+}
+return hourMetricsDataTTL;
+}
+
+public int getDayMetricsDataTTL() {
+if (otherMetricsDataTTL > 0) {
+return otherMetricsDataTTL;
+}
+return dayMetricsDataTTL;
 }
 }
diff --git a/skywalking-ui b/skywalking-ui
index 3e78e9c..17040ef 16
--- a/skywalking-ui
+++ b/skywalking-ui
@@ -1 +1 @@
-Subproject commit 3e78e9cc16f1749ef3a4deb9598394357d8b161d
+Subproject commit 17040efd79a973b6a3c84a70b1a401cd92ff9ba4



[skywalking] branch other-ttl-bug deleted (was 6688e3f)

2019-08-16 Thread wusheng
This is an automated email from the ASF dual-hosted git repository.

wusheng pushed a change to branch other-ttl-bug
in repository https://gitbox.apache.org/repos/asf/skywalking.git.


 was 6688e3f  Add header.

The revisions that were on this branch are still contained in
other references; therefore, this change does not discard any commits
from the repository.



[GitHub] [skywalking] wu-sheng merged pull request #3283: Module config set override is not working

2019-08-16 Thread GitBox
wu-sheng merged pull request #3283: Module config set override is not working
URL: https://github.com/apache/skywalking/pull/3283
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [skywalking] wu-sheng commented on issue #3283: Module config set override is not working

2019-08-16 Thread GitBox
wu-sheng commented on issue #3283: Module config set override is not working
URL: https://github.com/apache/skywalking/pull/3283#issuecomment-522192625
 
 
   /run ci


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[skywalking] branch other-ttl-bug updated (c5b9a13 -> 6688e3f)

2019-08-16 Thread wusheng
This is an automated email from the ASF dual-hosted git repository.

wusheng pushed a change to branch other-ttl-bug
in repository https://gitbox.apache.org/repos/asf/skywalking.git.


from c5b9a13  Submodule update
 add 6688e3f  Add header.

No new revisions were added by this update.

Summary of changes:
 skywalking-ui | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)



[GitHub] [skywalking] wu-sheng commented on issue #3283: Module config set override is not working

2019-08-16 Thread GitBox
wu-sheng commented on issue #3283: Module config set override is not working
URL: https://github.com/apache/skywalking/pull/3283#issuecomment-522182175
 
 
   /run e2e


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [skywalking] wu-sheng commented on issue #3283: Module config set override is not working

2019-08-16 Thread GitBox
wu-sheng commented on issue #3283: Module config set override is not working
URL: https://github.com/apache/skywalking/pull/3283#issuecomment-522182149
 
 
   /run ci


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [skywalking] wu-sheng removed a comment on issue #3283: Module config set override is not working

2019-08-16 Thread GitBox
wu-sheng removed a comment on issue #3283: Module config set override is not 
working
URL: https://github.com/apache/skywalking/pull/3283#issuecomment-522062525
 
 
   /run e2e


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [skywalking] wu-sheng removed a comment on issue #3283: Module config set override is not working

2019-08-16 Thread GitBox
wu-sheng removed a comment on issue #3283: Module config set override is not 
working
URL: https://github.com/apache/skywalking/pull/3283#issuecomment-522061688
 
 
   /run ci


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [skywalking] wu-sheng commented on issue #3283: Module config set override is not working

2019-08-16 Thread GitBox
wu-sheng commented on issue #3283: Module config set override is not working
URL: https://github.com/apache/skywalking/pull/3283#issuecomment-522062525
 
 
   /run e2e


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [skywalking] wu-sheng commented on issue #3283: Module config set override is not working

2019-08-16 Thread GitBox
wu-sheng commented on issue #3283: Module config set override is not working
URL: https://github.com/apache/skywalking/pull/3283#issuecomment-522061688
 
 
   /run ci


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [skywalking] wu-sheng commented on issue #3273: Support Zookeeper ACL

2019-08-16 Thread GitBox
wu-sheng commented on issue #3273: Support Zookeeper ACL
URL: https://github.com/apache/skywalking/pull/3273#issuecomment-522050637
 
 
   /run ci


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [skywalking] wu-sheng removed a comment on issue #3273: Support Zookeeper ACL

2019-08-16 Thread GitBox
wu-sheng removed a comment on issue #3273: Support Zookeeper ACL
URL: https://github.com/apache/skywalking/pull/3273#issuecomment-521935632
 
 
   /run ci


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[skywalking] branch other-ttl-bug updated (5e6b7dc -> c5b9a13)

2019-08-16 Thread wusheng
This is an automated email from the ASF dual-hosted git repository.

wusheng pushed a change to branch other-ttl-bug
in repository https://gitbox.apache.org/repos/asf/skywalking.git.


from 5e6b7dc  set Override is not working.
 add c5b9a13  Submodule update

No new revisions were added by this update.

Summary of changes:
 skywalking-ui | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)



[GitHub] [skywalking] wu-sheng commented on issue #3283: Module config set override is not working

2019-08-16 Thread GitBox
wu-sheng commented on issue #3283: Module config set override is not working
URL: https://github.com/apache/skywalking/pull/3283#issuecomment-522038000
 
 
   Update UI submodule too.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [skywalking] wu-sheng opened a new pull request #3283: Module config set override is not working

2019-08-16 Thread GitBox
wu-sheng opened a new pull request #3283: Module config set override is not 
working
URL: https://github.com/apache/skywalking/pull/3283
 
 
   Due to our module core is using refactor to set value, the `setter` is not 
working. I just change it to getter.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[skywalking] branch other-ttl-bug created (now 5e6b7dc)

2019-08-16 Thread wusheng
This is an automated email from the ASF dual-hosted git repository.

wusheng pushed a change to branch other-ttl-bug
in repository https://gitbox.apache.org/repos/asf/skywalking.git.


  at 5e6b7dc  set Override is not working.

This branch includes the following new commits:

 new 5e6b7dc  set Override is not working.

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.




[skywalking] 01/01: set Override is not working.

2019-08-16 Thread wusheng
This is an automated email from the ASF dual-hosted git repository.

wusheng pushed a commit to branch other-ttl-bug
in repository https://gitbox.apache.org/repos/asf/skywalking.git

commit 5e6b7dc7ca2f43c443d289184d9822663f8eafe7
Author: Wu Sheng 
AuthorDate: Fri Aug 16 22:46:04 2019 +0800

set Override is not working.
---
 .../StorageModuleElasticsearchConfig.java   | 21 +
 1 file changed, 17 insertions(+), 4 deletions(-)

diff --git 
a/oap-server/server-storage-plugin/storage-elasticsearch-plugin/src/main/java/org/apache/skywalking/oap/server/storage/plugin/elasticsearch/StorageModuleElasticsearchConfig.java
 
b/oap-server/server-storage-plugin/storage-elasticsearch-plugin/src/main/java/org/apache/skywalking/oap/server/storage/plugin/elasticsearch/StorageModuleElasticsearchConfig.java
index 5ba6692..e8a0fc6 100644
--- 
a/oap-server/server-storage-plugin/storage-elasticsearch-plugin/src/main/java/org/apache/skywalking/oap/server/storage/plugin/elasticsearch/StorageModuleElasticsearchConfig.java
+++ 
b/oap-server/server-storage-plugin/storage-elasticsearch-plugin/src/main/java/org/apache/skywalking/oap/server/storage/plugin/elasticsearch/StorageModuleElasticsearchConfig.java
@@ -47,11 +47,24 @@ public class StorageModuleElasticsearchConfig extends 
ModuleConfig {
 private int otherMetricsDataTTL = 0;
 @Setter private int monthMetricsDataTTL = 18;
 
-public void setOtherMetricsDataTTL(int otherMetricsDataTTL) {
+public int getMinuteMetricsDataTTL() {
 if (otherMetricsDataTTL > 0) {
-minuteMetricsDataTTL = otherMetricsDataTTL;
-hourMetricsDataTTL = otherMetricsDataTTL;
-dayMetricsDataTTL = otherMetricsDataTTL;
+return otherMetricsDataTTL;
 }
+return minuteMetricsDataTTL;
+}
+
+public int getHourMetricsDataTTL() {
+if (otherMetricsDataTTL > 0) {
+return otherMetricsDataTTL;
+}
+return hourMetricsDataTTL;
+}
+
+public int getDayMetricsDataTTL() {
+if (otherMetricsDataTTL > 0) {
+return otherMetricsDataTTL;
+}
+return dayMetricsDataTTL;
 }
 }



[GitHub] [skywalking] wu-sheng commented on issue #3281: The skywalking oap server cpu is too high to reach 100%

2019-08-16 Thread GitBox
wu-sheng commented on issue #3281: The skywalking oap server  cpu is too high 
to reach 100%
URL: https://github.com/apache/skywalking/issues/3281#issuecomment-521968971
 
 
   Try 6.3.0, it will reduce some payload to OAP. But to be honest, 4c simple 
node OAP for 40 node agents, looks like not powerful enough. SkyWalking does 
aggregations inside OAP by using internal stream computing core, it is not a 
simple collector to receive and save.
   
   Also, check your ES status, and our recommendations about ES bulk settings.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [skywalking] wu-sheng closed issue #3281: The skywalking oap server cpu is too high to reach 100%

2019-08-16 Thread GitBox
wu-sheng closed issue #3281: The skywalking oap server  cpu is too high to 
reach 100%
URL: https://github.com/apache/skywalking/issues/3281
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [skywalking] kezhenxu94 edited a comment on issue #3282: Modify agent log path

2019-08-16 Thread GitBox
kezhenxu94 edited a comment on issue #3282: Modify agent log path
URL: https://github.com/apache/skywalking/issues/3282#issuecomment-521965212
 
 
   
[Here](https://github.com/apache/skywalking/tree/master/docs/en/setup/service-agent/java-agent#table-of-agent-configuration-properties)
 are the supported properties, you can find the property to change the log path 
and log file name


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [skywalking] kezhenxu94 commented on issue #3282: Modify agent log path

2019-08-16 Thread GitBox
kezhenxu94 commented on issue #3282: Modify agent log path
URL: https://github.com/apache/skywalking/issues/3282#issuecomment-521965212
 
 
   
[Here](https://github.com/apache/skywalking/tree/master/docs/en/setup/service-agent/java-agent#table-of-agent-configuration-properties)
 are the options, you can find the option to change the log path and log file 
name


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [skywalking] kezhenxu94 closed issue #3282: Modify agent log path

2019-08-16 Thread GitBox
kezhenxu94 closed issue #3282: Modify agent log path
URL: https://github.com/apache/skywalking/issues/3282
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [skywalking] liyongfa0311 commented on issue #3281: The skywalking oap server cpu is too high to reach 100%

2019-08-16 Thread GitBox
liyongfa0311 commented on issue #3281: The skywalking oap server  cpu is too 
high to reach 100%
URL: https://github.com/apache/skywalking/issues/3281#issuecomment-521963571
 
 
   the skywalking that I used is 6.2.0 and I use Es cluster,, the machine of es 
is 16c32g


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [skywalking] wu-sheng commented on issue #3281: The skywalking oap server cpu is too high to reach 100%

2019-08-16 Thread GitBox
wu-sheng commented on issue #3281: The skywalking oap server  cpu is too high 
to reach 100%
URL: https://github.com/apache/skywalking/issues/3281#issuecomment-521960790
 
 
   SkyWalking version? I am wondering the storage, do you use Elasticsearch 
cluster?


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [skywalking] lvchhenyang opened a new issue #3282: Modify log path

2019-08-16 Thread GitBox
lvchhenyang opened a new issue #3282: Modify log path
URL: https://github.com/apache/skywalking/issues/3282
 
 
   Please  answer these questions before submitting your issue.
   
   - Why do you submit this issue?
   - [ ] Question or discussion
   - [ ] Bug
   - [ ] Requirement
   - [ ] Feature or performance improvement
   
   ___
   ### Question
   - What do you want to know?
   
   ___
   ### Bug
   - Which version of SkyWalking, OS and JRE?
   
   - Which company or project?
   
   - What happen?
   If possible, provide a way for reproducing the error. e.g. demo application, 
component version.
   
   ___
   ### Requirement or improvement
   - Please describe about your requirements or improvement suggestions.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [skywalking] liyongfa0311 commented on issue #3281: The skywalking oap server cpu is too high to reach 100%

2019-08-16 Thread GitBox
liyongfa0311 commented on issue #3281: The skywalking oap server  cpu is too 
high to reach 100%
URL: https://github.com/apache/skywalking/issues/3281#issuecomment-521952652
 
 
   4 core cpu,all reach 100%,8g ,abount 40 agent instances,I used jstack to 
find that there are a lot of threads waiting in the state.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [skywalking] wu-sheng commented on issue #3281: The skywalking oap server cpu is too high to reach 100%

2019-08-16 Thread GitBox
wu-sheng commented on issue #3281: The skywalking oap server  cpu is too high 
to reach 100%
URL: https://github.com/apache/skywalking/issues/3281#issuecomment-521950827
 
 
   How many CPUs? Which storage? How many agent instances? 


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [skywalking] liyongfa0311 opened a new issue #3281: The skywalking oap server cpu is too high to reach 100%

2019-08-16 Thread GitBox
liyongfa0311 opened a new issue #3281: The skywalking oap server  cpu is too 
high to reach 100%
URL: https://github.com/apache/skywalking/issues/3281
 
 
   Please answer these questions before submitting your issue.
   
   - Why do you submit this issue?
   - [x ] Question or discussion
   - [ ] Bug
   - [ ] Requirement
   - [ ] Feature or performance improvement
   
   ___
   ### Question
   - What do you want to know?
   skywalking oapServer CPU is in 100% by standalone mode.I am adding 20 
service monitors,
   What do I need to do to get the CPU usage down?
   ___
   ### Bug
   - Which version of SkyWalking, OS and JRE?
CentOS7.3
   - Which company or project?
   
   - What happen?
   If possible, provide a way for reproducing the error. e.g. demo application, 
component version.
   
   ___
   ### Requirement or improvement
   - Please describe about your requirements or improvement suggestions.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [skywalking] wu-sheng closed issue #3280: ui could not see data

2019-08-16 Thread GitBox
wu-sheng closed issue #3280: ui could not see data
URL: https://github.com/apache/skywalking/issues/3280
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [skywalking] wu-sheng commented on issue #3280: ui could not see data

2019-08-16 Thread GitBox
wu-sheng commented on issue #3280: ui could not see data
URL: https://github.com/apache/skywalking/issues/3280#issuecomment-521946752
 
 
   This is not the issue too. Please search issue before submit duplicated one.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [skywalking] timqq opened a new issue #3280: ui could not see data

2019-08-16 Thread GitBox
timqq opened a new issue #3280: ui could not see data
URL: https://github.com/apache/skywalking/issues/3280
 
 
   2019-08-16 17:14:05,542 - 
graphql.execution.SimpleDataFetcherExceptionHandler - 23 [qtp908722588-190] 
WARN  [] - Exception while fetching data (/latencyC) : IDs can't be null
   java.lang.RuntimeException: IDs can't be null
at 
org.apache.skywalking.oap.server.core.query.MetricQueryService.getValues(MetricQueryService.java:61)
 ~[server-core-6.1.0.jar:6.1.0]
at 
org.apache.skywalking.oap.query.graphql.resolver.MetricQuery.getValues(MetricQuery.java:53)
 ~[query-graphql-plugin-6.1.0.jar:6.1.0]
at 
org.apache.skywalking.oap.query.graphql.resolver.MetricQueryMethodAccess.invoke(Unknown
 Source) ~[reflectasm-1.11.7.jar:6.1.0]
at 
com.coxautodev.graphql.tools.MethodFieldResolverDataFetcher.get(MethodFieldResolver.kt:147)
 ~[graphql-java-tools-5.2.3.jar:?]
at 
graphql.execution.ExecutionStrategy.fetchField(ExecutionStrategy.java:227) 
[graphql-java-8.0.jar:?]
at 
graphql.execution.ExecutionStrategy.resolveField(ExecutionStrategy.java:170) 
[graphql-java-8.0.jar:?]
at 
graphql.execution.AsyncExecutionStrategy.execute(AsyncExecutionStrategy.java:59)
 [graphql-java-8.0.jar:?]
at graphql.execution.Execution.executeOperation(Execution.java:158) 
[graphql-java-8.0.jar:?]
at graphql.execution.Execution.execute(Execution.java:100) 
[graphql-java-8.0.jar:?]
at graphql.GraphQL.execute(GraphQL.java:558) [graphql-java-8.0.jar:?]
at graphql.GraphQL.parseValidateAndExecute(GraphQL.java:500) 
[graphql-java-8.0.jar:?]
at graphql.GraphQL.executeAsync(GraphQL.java:470) 
[graphql-java-8.0.jar:?]
at graphql.GraphQL.execute(GraphQL.java:401) [graphql-java-8.0.jar:?]
at 
org.apache.skywalking.oap.query.graphql.GraphQLQueryHandler.execute(GraphQLQueryHandler.java:87)
 [query-graphql-plugin-6.1.0.jar:6.1.0]
at 
org.apache.skywalking.oap.query.graphql.GraphQLQueryHandler.doPost(GraphQLQueryHandler.java:81)
 [query-graphql-plugin-6.1.0.jar:6.1.0]
at 
org.apache.skywalking.oap.server.library.server.jetty.JettyJsonHandler.doPost(JettyJsonHandler.java:54)
 [library-server-6.1.0.jar:6.1.0]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) 
[javax.servlet-api-3.1.0.jar:3.1.0]
at 
org.apache.skywalking.oap.server.library.server.jetty.JettyJsonHandler.service(JettyJsonHandler.java:101)
 [library-server-6.1.0.jar:6.1.0]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) 
[javax.servlet-api-3.1.0.jar:3.1.0]
at 
org.apache.skywalking.oap.server.library.server.jetty.JettyJsonHandler.service(JettyJsonHandler.java:105)
 [library-server-6.1.0.jar:6.1.0]
at 
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:841) 
[jetty-servlet-9.4.2.v20170220.jar:9.4.2.v20170220]
at 
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:543) 
[jetty-servlet-9.4.2.v20170220.jar:9.4.2.v20170220]
at 
org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:188)
 [jetty-server-9.4.2.v20170220.jar:9.4.2.v20170220]
at 
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1239)
 [jetty-server-9.4.2.v20170220.jar:9.4.2.v20170220]
at 
org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:168)
 [jetty-server-9.4.2.v20170220.jar:9.4.2.v20170220]
at 
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:481) 
[jetty-servlet-9.4.2.v20170220.jar:9.4.2.v20170220]
at 
org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:166)
 [jetty-server-9.4.2.v20170220.jar:9.4.2.v20170220]
at 
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1141)
 [jetty-server-9.4.2.v20170220.jar:9.4.2.v20170220]
at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) 
[jetty-server-9.4.2.v20170220.jar:9.4.2.v20170220]
at 
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) 
[jetty-server-9.4.2.v20170220.jar:9.4.2.v20170220]
at org.eclipse.jetty.server.Server.handle(Server.java:564) 
[jetty-server-9.4.2.v20170220.jar:9.4.2.v20170220]
at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:320) 
[jetty-server-9.4.2.v20170220.jar:9.4.2.v20170220]
at 
org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251) 
[jetty-server-9.4.2.v20170220.jar:9.4.2.v20170220]
at 
org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:279)
 [jetty-io-9.4.2.v20170220.jar:9.4.2.v20170220]
at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:110) 
[jetty-io-9.4.2.v20170220.jar:9.4.2.v20170220]
at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:124) 
[jetty-io-9.4.2.v20170220.jar:9.4.2.v20170220]
at 

[GitHub] [skywalking] dmsolr commented on a change in pull request #3273: Support Zookeeper ACL

2019-08-16 Thread GitBox
dmsolr commented on a change in pull request #3273: Support Zookeeper ACL
URL: https://github.com/apache/skywalking/pull/3273#discussion_r314637981
 
 

 ##
 File path: 
oap-server/server-cluster-plugin/cluster-zookeeper-plugin/src/main/java/org/apache/skywalking/oap/server/cluster/plugin/zookeeper/ClusterModuleZookeeperProvider.java
 ##
 @@ -61,7 +79,39 @@ public ClusterModuleZookeeperProvider() {
 
 @Override public void prepare() throws ServiceNotProvidedException, 
ModuleStartException {
 RetryPolicy retryPolicy = new 
ExponentialBackoffRetry(config.getBaseSleepTimeMs(), config.getMaxRetries());
-client = CuratorFrameworkFactory.newClient(config.getHostPort(), 
retryPolicy);
+
+CuratorFrameworkFactory.Builder builder = 
CuratorFrameworkFactory.builder()
+.retryPolicy(retryPolicy)
+.connectString(config.getHostPort());
+if (config.isEnableACL()) {
+final List acls = Lists.newArrayList();
+
+String authInfo = config.getAuth();
+if ("digest".equals(config.getSchema())) {
 
 Review comment:
   The Zookeeper Document said:
   > digest uses a username:password string to generate MD5 hash which is then 
used as an ACL ID identity. Authentication is done by sending the 
username:password in clear text. When used in the ACL the expression will be 
the username:base64 encoded SHA1 password digest.
   
   Most projects only provided `digest` schema, such as Solr. 


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [skywalking] wu-sheng commented on issue #3273: Support Zookeeper ACL

2019-08-16 Thread GitBox
wu-sheng commented on issue #3273: Support Zookeeper ACL
URL: https://github.com/apache/skywalking/pull/3273#issuecomment-521935632
 
 
   /run ci


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [skywalking] wu-sheng commented on issue #3279: collector console error occurred when agent restart , after agent started and send new data to collector but ui could not see any new data

2019-08-16 Thread GitBox
wu-sheng commented on issue #3279: collector console error occurred when agent 
restart , after agent started and send new data to collector but ui could not 
see any new data
URL: https://github.com/apache/skywalking/issues/3279#issuecomment-521922783
 
 
   I have said, this is not the case.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [skywalking] wu-sheng closed issue #3279: collector console error occurred when agent restart , after agent started and send new data to collector but ui could not see any new data

2019-08-16 Thread GitBox
wu-sheng closed issue #3279: collector console error occurred when agent 
restart , after agent started and send new data to collector but ui could not 
see any new data
URL: https://github.com/apache/skywalking/issues/3279
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [skywalking] timqq opened a new issue #3279: collector console error occurred when agent restart , after agent started and send new data to collector but ui could not see any new data

2019-08-16 Thread GitBox
timqq opened a new issue #3279: collector console error occurred when agent 
restart , after agent started and send new data to collector but ui could not 
see any new data
URL: https://github.com/apache/skywalking/issues/3279
 
 
   collector console error occurred when agent restart , after agent started 
and send new data to collector but ui could not see any new data
   
   信息: Transport failed
   java.io.IOException: 远程主机强迫关闭了一个现有的连接。
   at sun.nio.ch.SocketDispatcher.read0(Native Method)
   at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:43)
   at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)
   at sun.nio.ch.IOUtil.read(IOUtil.java:192)
   at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380)
   at 
io.netty.buffer.PooledUnsafeDirectByteBuf.setBytes(PooledUnsafeDirectByteBuf.java:288)
   at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:1108)
   at 
io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:345)
   at 
io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:148)
   at 
io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:646)
   at 
io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:581)
   at 
io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:498)
   at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:460)
   at 
io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:884)
   at 
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
   at java.lang.Thread.run(Thread.java:745)


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [skywalking] wu-sheng commented on issue #3275: Can't find service by service instance id from cache, service instance id is: 152

2019-08-16 Thread GitBox
wu-sheng commented on issue #3275: Can't find service by service instance id 
from cache, service instance id is: 152
URL: https://github.com/apache/skywalking/issues/3275#issuecomment-521917710
 
 
   This is not a bug fix. This is a new feature provided in 6.3.0


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [skywalking] wu-sheng commented on issue #3278: collector console error occurred when agent restart

2019-08-16 Thread GitBox
wu-sheng commented on issue #3278: collector console error occurred when agent 
restart
URL: https://github.com/apache/skywalking/issues/3278#issuecomment-521917585
 
 
   This log is not related to that. Check others and your storage.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [skywalking] timqq commented on issue #3278: collector console error occurred when agent restart

2019-08-16 Thread GitBox
timqq commented on issue #3278: collector console error occurred when agent 
restart
URL: https://github.com/apache/skywalking/issues/3278#issuecomment-521916867
 
 
   agent send new data to collector bu ui could not see any new data 


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [skywalking] timqq commented on issue #3278: collector console error occurred when agent restart

2019-08-16 Thread GitBox
timqq commented on issue #3278: collector console error occurred when agent 
restart
URL: https://github.com/apache/skywalking/issues/3278#issuecomment-521915899
 
 
   when agent start ui could not see any new data


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [skywalking] wu-sheng commented on issue #3278: collector console error occurred when agent restart

2019-08-16 Thread GitBox
wu-sheng commented on issue #3278: collector console error occurred when agent 
restart
URL: https://github.com/apache/skywalking/issues/3278#issuecomment-521915053
 
 
   It means client shutdown. Nothing special.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [skywalking] wu-sheng closed issue #3278: collector console error occurred when agent restart

2019-08-16 Thread GitBox
wu-sheng closed issue #3278: collector console error occurred when agent restart
URL: https://github.com/apache/skywalking/issues/3278
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [skywalking] timqq opened a new issue #3278: collector console error occurred when agent restart

2019-08-16 Thread GitBox
timqq opened a new issue #3278: collector console error occurred when agent 
restart
URL: https://github.com/apache/skywalking/issues/3278
 
 
   
   collector console error occurred when agent restart then ui could not see 
any new data
   
   信息: Transport failed
   java.io.IOException: 远程主机强迫关闭了一个现有的连接。
   at sun.nio.ch.SocketDispatcher.read0(Native Method)
   at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:43)
   at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)
   at sun.nio.ch.IOUtil.read(IOUtil.java:192)
   at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380)
   at 
io.netty.buffer.PooledUnsafeDirectByteBuf.setBytes(PooledUnsafeDirectByteBuf.java:288)
   at 
io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:1108)
   at 
io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:345)
   at 
io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:148)
   at 
io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:646)
   at 
io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:581)
   at 
io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:498)
   at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:460)
   at 
io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:884)
   at 
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
   at java.lang.Thread.run(Thread.java:745)
   
   
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [skywalking] qianglu1989 edited a comment on issue #3275: Can't find service by service instance id from cache, service instance id is: 152

2019-08-16 Thread GitBox
qianglu1989 edited a comment on issue #3275: Can't find service by service 
instance id from cache, service instance id is: 152
URL: https://github.com/apache/skywalking/issues/3275#issuecomment-521910993
 
 
   Does upgrade 6.3 fix this?@wu-sheng


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [skywalking] qianglu1989 commented on issue #3275: Can't find service by service instance id from cache, service instance id is: 152

2019-08-16 Thread GitBox
qianglu1989 commented on issue #3275: Can't find service by service instance id 
from cache, service instance id is: 152
URL: https://github.com/apache/skywalking/issues/3275#issuecomment-521910993
 
 
   Does upgrade 6.3 fix this?


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [skywalking] wu-sheng commented on issue #3277: The topology map cannot be displayed after starting for a while

2019-08-16 Thread GitBox
wu-sheng commented on issue #3277: The topology map cannot be displayed after 
starting for a while
URL: https://github.com/apache/skywalking/issues/3277#issuecomment-521904629
 
 
   Check Elasticsearch storage document, there are some ElasticSearch settings 
suggestions. And please make sure your ES cluster is powerful enough.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [skywalking] wu-sheng closed issue #3277: The topology map cannot be displayed after starting for a while

2019-08-16 Thread GitBox
wu-sheng closed issue #3277: The topology map cannot be displayed after 
starting for a while
URL: https://github.com/apache/skywalking/issues/3277
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [skywalking] shook2012 commented on issue #3275: Can't find service by service instance id from cache, service instance id is: 152

2019-08-16 Thread GitBox
shook2012 commented on issue #3275: Can't find service by service instance id 
from cache, service instance id is: 152
URL: https://github.com/apache/skywalking/issues/3275#issuecomment-521904587
 
 
   my skywalking oap-server log also has this error.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [skywalking] wu-sheng commented on issue #3276: Skywalking UI blank

2019-08-16 Thread GitBox
wu-sheng commented on issue #3276: Skywalking UI blank
URL: https://github.com/apache/skywalking/issues/3276#issuecomment-521904204
 
 
   You have to do some UI debug, my guess, traces break somehow, and UI can't 
show up.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [skywalking] wu-sheng closed issue #3275: Can't find service by service instance id from cache, service instance id is: 152

2019-08-16 Thread GitBox
wu-sheng closed issue #3275: Can't find service by service instance id from 
cache, service instance id is: 152
URL: https://github.com/apache/skywalking/issues/3275
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [skywalking] wu-sheng commented on issue #3275: Can't find service by service instance id from cache, service instance id is: 152

2019-08-16 Thread GitBox
wu-sheng commented on issue #3275: Can't find service by service instance id 
from cache, service instance id is: 152
URL: https://github.com/apache/skywalking/issues/3275#issuecomment-521904022
 
 
   Only one way, reboot all your agents. You have erased the metadata, only 
6.3.0+ agents support hot-auto-reboot.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [skywalking] shook2012 opened a new issue #3277: The topology map cannot be displayed after starting for a while

2019-08-16 Thread GitBox
shook2012 opened a new issue #3277: The topology map cannot be displayed after 
starting for a while
URL: https://github.com/apache/skywalking/issues/3277
 
 
   - Why do you submit this issue?
   - [ ] Bug
   
   
   ### Bug
   version:6.3.0
   Jdk: 1.8.131
   os:centos 6.8
   
   
   - What happen?
   The topology map cannot be displayed after starting for a while
   
   2019-08-16 14:32:42,787 - 
org.apache.skywalking.oap.server.library.client.elasticsearch.ElasticSearchClient
 - 292 [pool-16-thread-1] INFO  [] - Synchronous bulk took time: 3429 millis, 
size: 648
   2019-08-16 14:32:44,115 - 
org.apache.skywalking.oap.server.library.client.elasticsearch.ElasticSearchClient
 - 311 [I/O dispatcher 3] INFO  [] - Bulk execution id [7782] completed in 52 
milliseconds, size: 40
   2019-08-16 14:32:45,552 - 
org.apache.skywalking.oap.server.core.register.worker.RegisterPersistentWorker 
- 112 [DataCarrier.REGISTER_L2.BulkConsumePool.0.Thread] ERROR [] - 
Elasticsearch exception [type=es_rejected_execution_exception, reason=rejected 
execution of processing of [19302869][indices:data/write/bulk[s][p]]: request: 
BulkShardRequest [[skywalkingapm_service_inventory][1]] containing [index 
{[skywalkingapm_service_inventory][type][appcloud-app_0_0], 
source[{"sequence":12,"last_update_time":1565585596332,"heartbeat_time":1565937176591,"node_type":0,"name":"appcloud-app","address_id":0,"is_address":0,"mapping_service_id":0,"register_time":1565585596332,"properties":"{}"}]}]
 and a refresh, target allocation id: PbT1YNTuQFOiva22tUafjw, primary term: 3 
on EsThreadPoolExecutor[name = es_3/write, queue capacity = 200, 
org.elasticsearch.common.util.concurrent.EsThreadPoolExecutor@3076e97[Running, 
pool size = 4, active threads = 4, queued tasks = 200, completed tasks = 
5720877]]]
   org.elasticsearch.ElasticsearchStatusException: Elasticsearch exception 
[type=es_rejected_execution_exception, reason=rejected execution of processing 
of [19302869][indices:data/write/bulk[s][p]]: request: BulkShardRequest 
[[skywalkingapm_service_inventory][1]] containing [index 
{[skywalkingapm_service_inventory][type][appcloud-app_0_0], 
source[{"sequence":12,"last_update_time":1565585596332,"heartbeat_time":1565937176591,"node_type":0,"name":"appcloud-app","address_id":0,"is_address":0,"mapping_service_id":0,"register_time":1565585596332,"properties":"{}"}]}]
 and a refresh, target allocation id: PbT1YNTuQFOiva22tUafjw, primary term: 3 
on EsThreadPoolExecutor[name = es_3/write, queue capacity = 200, 
org.elasticsearch.common.util.concurrent.EsThreadPoolExecutor@3076e97[Running, 
pool size = 4, active threads = 4, queued tasks = 200, completed tasks = 
5720877]]]
at 
org.elasticsearch.rest.BytesRestResponse.errorFromXContent(BytesRestResponse.java:177)
 ~[elasticsearch-6.3.2.jar:6.3.2]
at 
org.elasticsearch.client.RestHighLevelClient.parseEntity(RestHighLevelClient.java:653)
 ~[elasticsearch-rest-high-level-client-6.3.2.jar:6.3.2]
at 
org.elasticsearch.client.RestHighLevelClient.parseResponseException(RestHighLevelClient.java:628)
 ~[elasticsearch-rest-high-level-client-6.3.2.jar:6.3.2]
at 
org.elasticsearch.client.RestHighLevelClient.performRequest(RestHighLevelClient.java:535)
 ~[elasticsearch-rest-high-level-client-6.3.2.jar:6.3.2]
at 
org.elasticsearch.client.RestHighLevelClient.performRequestAndParseEntity(RestHighLevelClient.java:508)
 ~[elasticsearch-rest-high-level-client-6.3.2.jar:6.3.2]
at 
org.elasticsearch.client.RestHighLevelClient.update(RestHighLevelClient.java:366)
 ~[elasticsearch-rest-high-level-client-6.3.2.jar:6.3.2]
at 
org.apache.skywalking.oap.server.library.client.elasticsearch.ElasticSearchClient.forceUpdate(ElasticSearchClient.java:254)
 ~[library-client-6.3.0.jar:6.3.0]
at 
org.apache.skywalking.oap.server.storage.plugin.elasticsearch.base.RegisterEsDAO.forceUpdate(RegisterEsDAO.java:56)
 ~[storage-elasticsearch-plugin-6.3.0.jar:6.3.0]
at 
org.apache.skywalking.oap.server.core.register.worker.RegisterPersistentWorker.lambda$onWork$0(RegisterPersistentWorker.java:89)
 ~[server-core-6.3.0.jar:6.3.0]
at java.util.HashMap$Values.forEach(HashMap.java:980) [?:1.8.0_131]
at 
org.apache.skywalking.oap.server.core.register.worker.RegisterPersistentWorker.onWork(RegisterPersistentWorker.java:84)
 [server-core-6.3.0.jar:6.3.0]
at 
org.apache.skywalking.oap.server.core.register.worker.RegisterPersistentWorker.access$100(RegisterPersistentWorker.java:35)
 [server-core-6.3.0.jar:6.3.0]
at 
org.apache.skywalking.oap.server.core.register.worker.RegisterPersistentWorker$PersistentConsumer.consume(RegisterPersistentWorker.java:141)
 [server-core-6.3.0.jar:6.3.0]
at 
org.apache.skywalking.apm.commons.datacarrier.consumer.MultipleChannelsConsumer.consume(MultipleChannelsConsumer.java:82)
 [apm-datacarrier-6.3.0.jar:6.3.0]
at 

[skywalking] branch master updated: Check license header strictly (#3274)

2019-08-16 Thread wusheng
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/skywalking.git


The following commit(s) were added to refs/heads/master by this push:
 new db9759f  Check license header strictly (#3274)
db9759f is described below

commit db9759fcc2d76977426f1328f36b7590f314db69
Author: kezhenxu94 
AuthorDate: Fri Aug 16 14:37:44 2019 +0800

Check license header strictly (#3274)

* Check license header strictly

* Ignore header template

* Include more files to check list
---
 apm-checkstyle/CHECKSTYLE_HEAD | 35 +++---
 apm-checkstyle/checkStyle.xml  |  6 
 .../skywalking/apm/agent/core/base64/Base64.java   |  4 +--
 apm-webapp/src/main/resources/application.yml  | 14 -
 .../src/test/resources/alarm-settings.yml  | 13 
 .../src/test/resources/application.yml | 14 -
 .../src/test/resources/application.yml | 14 -
 .../src/test/resources/application.yml | 14 -
 .../src/test/resources/application.yml | 13 
 ...alking.oap.server.library.module.ModuleProvider |  0
 .../src/test/resources/component-libraries.yml | 13 
 .../src/test/resources/application.yml | 13 
 .../src/main/resources/alarm-settings.yml  | 13 
 .../src/main/resources/application.yml | 13 
 .../src/main/resources/component-libraries.yml | 13 
 .../main/resources/datasource-settings.properties  |  0
 ...alking.oap.server.library.module.ModuleProvider | 18 ---
 pom.xml|  9 ++
 18 files changed, 105 insertions(+), 114 deletions(-)

diff --git a/apm-checkstyle/CHECKSTYLE_HEAD b/apm-checkstyle/CHECKSTYLE_HEAD
old mode 100644
new mode 100755
index 70774e0..00e3b09
--- a/apm-checkstyle/CHECKSTYLE_HEAD
+++ b/apm-checkstyle/CHECKSTYLE_HEAD
@@ -1,17 +1,18 @@
-/*
- * Licensed to the Apache Software Foundation (ASF) under one or more
- * contributor license agreements.  See the NOTICE file distributed with
- * this work for additional information regarding copyright ownership.
- * The ASF licenses this file to You under the Apache License, Version 2.0
- * (the "License"); you may not use this file except in compliance with
- * the License.  You may obtain a copy of the License at
- *
- * http://www.apache.org/licenses/LICENSE-2.0
- *
- * Unless required by applicable law or agreed to in writing, software
- * distributed under the License is distributed on an "AS IS" BASIS,
- * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- * See the License for the specific language governing permissions and
- * limitations under the License.
- *
- */
+^<\?xml version="1\.0" encoding="UTF-8"\?>$
+^
 
.mvn/wrapper/maven-wrapper.properties
 
tools/dependencies/known-oap-backend-dependencies.txt
+apm-checkstyle/CHECKSTYLE_HEAD
 
 
 
@@ -506,6 +507,14 @@
 
true
 true
 org/apache/skywalking/**/*.java
+
+**/*.properties,
+**/*.sh,
+**/*.bat,
+**/*.yml,
+**/*.yaml,
+**/*.xml
+
 
 
org/apache/skywalking/apm/network/register/v2/**/*.java,
 org/apache/skywalking/apm/network/common/**/*.java,



[GitHub] [skywalking] wu-sheng merged pull request #3274: Check license header strictly

2019-08-16 Thread GitBox
wu-sheng merged pull request #3274: Check license header strictly
URL: https://github.com/apache/skywalking/pull/3274
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [skywalking] SevenBlue2018 commented on issue #3276: Skywalking UI blank

2019-08-16 Thread GitBox
SevenBlue2018 commented on issue #3276: Skywalking UI blank
URL: https://github.com/apache/skywalking/issues/3276#issuecomment-521902724
 
 
   I see that the response data is normal.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [skywalking] SevenBlue2018 opened a new issue #3276: Skywalking UI blank

2019-08-16 Thread GitBox
SevenBlue2018 opened a new issue #3276: Skywalking UI blank
URL: https://github.com/apache/skywalking/issues/3276
 
 
   
![image](https://user-images.githubusercontent.com/11767168/63148178-f69ea280-c032-11e9-843a-2ccdc3f91007.png)
   Why is the area in the box blank?


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [skywalking] qianglu1989 opened a new issue #3275: Can't find service by service instance id from cache, service instance id is: 152

2019-08-16 Thread GitBox
qianglu1989 opened a new issue #3275: Can't find service by service instance id 
from cache, service instance id is: 152
URL: https://github.com/apache/skywalking/issues/3275
 
 
   英文不好,中文说下,异常如下,切换es集群了,为了方便数据没有迁移,会一直报下面的问题,怎么解决?
   
   
   
   
rg.apache.skywalking.oap.server.core.register.service.ServiceInstanceInventoryRegister
 - 108 [grpc-default-executor-24] WARN  [] - Service instance 956 heartbeat, 
but not found in storage.
   2019-08-16 14:32:41,008 - 
org.apache.skywalking.oap.server.receiver.jvm.provider.handler.JVMSourceDispatcher
 - 51 [grpc-default-executor-83] WARN  [] - Can't find service by service 
instance id from cache, service instance id is: 152
   2019-08-16 14:32:41,008 - 
org.apache.skywalking.oap.server.receiver.jvm.provider.handler.JVMSourceDispatcher
 - 51 [grpc-default-executor-75] WARN  [] - Can't find service by service 
instance id from cache, service instance id is: 956
   2019-08-16 14:32:41,009 - 
org.apache.skywalking.oap.server.receiver.jvm.provider.handler.JVMSourceDispatcher
 - 51 [grpc-default-executor-44] WARN  [] - Can't find service by service 
instance id from cache, service instance id is: 902
   2019-08-16 14:32:41,009 - 
org.apache.skywalking.oap.server.receiver.register.provider.handler.v6.grpc.ServiceInstancePingServiceHandler
 - 68 [grpc-default-executor-24] WARN  [] - Can't find service by service 
instance id from cache, service instance id is: 956, will send a reset command 
to agent side
   2019-08-16 14:32:41,011 - 
org.apache.skywalking.oap.server.core.register.service.ServiceInstanceInventoryRegister
 - 108 [grpc-default-executor-85] WARN  [] - Service instance 902 heartbeat, 
but not found in storage.
   2019-08-16 14:32:41,012 - 
org.apache.skywalking.oap.server.receiver.register.provider.handler.v6.grpc.ServiceInstancePingServiceHandler
 - 68 [grpc-default-executor-85] WARN  [] - Can't find service by service 
instance id from cache, service instance id is: 902, will send a reset command 
to agent side
   2019-08-16 14:32:41,017 - 
org.apache.skywalking.oap.server.receiver.jvm.provider.handler.JVMSourceDispatcher
 - 51 [grpc-default-executor-115] WARN  [] - Can't find service by service 
instance id from cache, service instance id is: 1029
   2019-08-16 14:32:41,017 - 
org.apache.skywalking.oap.server.receiver.jvm.provider.handler.JVMSourceDispatcher
 - 51 [grpc-default-executor-75] WARN  [] - Can't find service by service 
instance id from cache, service instance id is: 33
   2019-08-16 14:32:41,032 - 
org.apache.skywalking.oap.server.receiver.jvm.provider.handler.JVMSourceDispatcher
 - 51 [grpc-default-executor-66] WARN  [] - Can't find service by service 
instance id from cache, service instance id is: 501
   2019-08-16 14:32:41,034 - 
org.apache.skywalking.oap.server.receiver.jvm.provider.handler.JVMSourceDispatcher
 - 51 [grpc-default-executor-114] WARN  [] - Can't find service by service 
instance id from cache, service instance id is: 295
   2019-08-16 14:32:41,034 - 
org.apache.skywalking.oap.server.receiver.jvm.provider.handler.JVMSourceDispatcher
 - 51 [grpc-default-executor-85] WARN  [] - Can't find service by service 
instance id from cache, service instance id is: 1149
   2019-08-16 14:32:41,035 - 
org.apache.skywalking.oap.server.core.register.service.ServiceInstanceInventoryRegister
 - 108 [grpc-default-executor-114] WARN  [] - Service instance 295 heartbeat, 
but not found in storage.
   2019-08-16 14:32:41,036 - 
org.apache.skywalking.oap.server.receiver.register.provider.handler.v6.grpc.ServiceInstancePingServiceHandler
 - 68 [grpc-default-executor-114] WARN  [] - Can't find service by service 
instance id from cache, service instance id is: 295, will send a reset command 
to agent side


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services