You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@skywalking.apache.org by GitBox <gi...@apache.org> on 2021/03/22 10:01:05 UTC

[GitHub] [skywalking] ktpktr0 opened a new issue #6596: Health check fails. reason: can't get the instance list

ktpktr0 opened a new issue #6596:
URL: https://github.com/apache/skywalking/issues/6596


   Please answer these questions before submitting your issue.
   
   - Why do you submit this issue?
   - [ ] Question or discussion
   - [ ] Bug
   - [ ] Requirement
   - [ ] Feature or performance improvement
   
   ___
   ### Question
   How to use Nacos to realize dynamic configuration in skywalking8
   
   ___
   ### Bug
   - Which version of SkyWalking, OS, and JRE?
   
   - Which company or project?
   
   - What happened?
   I use skywalking 8.2 to use Nacos 1.4.1, which are based on k8s deployment. When I configure Nacos and skywalking, I can find skywalking oapserver in Nacos server list. But the log has the following errors, which are thrown irregularly.
   
   ```
   2021-03-22 09:42:48,417 - org.apache.skywalking.oap.server.library.client.elasticsearch.ElasticSearchClient -160997 [pool-6-thread-1] INFO  [] - Synchronous bulk took time: 6864 millis, size: 108
   2021-03-22 09:42:51,661 - org.apache.skywalking.oap.server.telemetry.api.HealthCheckMetrics -164241 [pool-4-thread-1] WARN  [] - Health check fails. reason: can't get the instance list
   2021-03-22 09:42:51,773 - org.apache.skywalking.oap.server.core.remote.RemoteSenderService -164353 [DataCarrier.METRICS_L1_AGGREGATION.BulkConsumePool.2.Thread] WARN  [] - There is no available remote server for now, ignore the streaming data until the cluster metadata initialized.
   2021-03-22 09:42:51,773 - org.apache.skywalking.oap.server.core.remote.RemoteSenderService -164353 [DataCarrier.METRICS_L1_AGGREGATION.BulkConsumePool.2.Thread] WARN  [] - There is no available remote server for now, ignore the streaming data until the cluster metadata initialized.
   2021-03-22 09:42:51,773 - org.apache.skywalking.oap.server.core.remote.RemoteSenderService -164353 [DataCarrier.METRICS_L1_AGGREGATION.BulkConsumePool.2.Thread] WARN  [] - There is no available remote server for now, ignore the streaming data until the cluster metadata initialized.
   2021-03-22 09:42:51,777 - org.apache.skywalking.oap.server.core.remote.RemoteSenderService -164357 [DataCarrier.METRICS_L1_AGGREGATION.BulkConsumePool.1.Thread] WARN  [] - There is no available remote server for now, ignore the streaming data until the cluster metadata initialized.
   2021-03-22 09:42:51,777 - org.apache.skywalking.oap.server.core.remote.RemoteSenderService -164357 [DataCarrier.METRICS_L1_AGGREGATION.BulkConsumePool.1.Thread] WARN  [] - There is no available remote server for now, ignore the streaming data until the cluster metadata initialized.
   ```
   
   Skywalking is configured to connect Nacos as follows
   
   ```
   nacos:
           # Nacos Server Host
           serverAddr: ${SW_CONFIG_NACOS_SERVER_ADDR:127.0.0.1}
           # Nacos Server Port
           port: ${SW_CONFIG_NACOS_SERVER_PORT:8848}
           # Nacos Configuration Group
           group: ${SW_CONFIG_NACOS_SERVER_GROUP:skywalking}
           # Nacos Configuration namespace
           namespace: ${SW_CONFIG_NACOS_SERVER_NAMESPACE:}
           # Unit seconds, sync period. Default fetch every 60 seconds.
           period: ${SW_CONFIG_NACOS_PERIOD:60}
           # Nacos auth username
           username: ${SW_CONFIG_NACOS_USERNAME:""}
           password: ${SW_CONFIG_NACOS_PASSWORD:""}
           # Nacos auth accessKey
           accessKey: ${SW_CONFIG_NACOS_ACCESSKEY:""}
           secretKey: ${SW_CONFIG_NACOS_SECRETKEY:""}
   ```
   ```
         nacos:
           serviceName: ${SW_SERVICE_NAME:"SkyWalking_OAP_Cluster"}
           hostPort: ${SW_CLUSTER_NACOS_HOST_PORT:localhost:8848}
           # Nacos Configuration namespace
           namespace: ${SW_CLUSTER_NACOS_NAMESPACE:"public"}
           # Nacos auth username
           username: ${SW_CLUSTER_NACOS_USERNAME:""}
           password: ${SW_CLUSTER_NACOS_PASSWORD:""}
           # Nacos auth accessKey
           accessKey: ${SW_CLUSTER_NACOS_ACCESSKEY:""}
           secretKey: ${SW_CLUSTER_NACOS_SECRETKEY:""}
   ```
   
   ___
   ### Requirement or improvement
   - Please describe 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:
users@infra.apache.org



[GitHub] [skywalking] ktpktr0 commented on issue #6596: Health check fails. reason: can't get the instance list

Posted by GitBox <gi...@apache.org>.
ktpktr0 commented on issue #6596:
URL: https://github.com/apache/skywalking/issues/6596#issuecomment-804740345


   I upgraded es cluster to 6.8, and this error no longer appears. But dynamic configuration failed


-- 
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:
users@infra.apache.org



[GitHub] [skywalking] ktpktr0 commented on issue #6596: Health check fails. reason: can't get the instance list

Posted by GitBox <gi...@apache.org>.
ktpktr0 commented on issue #6596:
URL: https://github.com/apache/skywalking/issues/6596#issuecomment-804526621


   > 阅读`NacosCoordinator#queryRemoteNodes`工作原理。
   
   I checked the code and read the host and port of Nacos. My settings are correct, but I still get the 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:
users@infra.apache.org



[GitHub] [skywalking] wu-sheng commented on issue #6596: Health check fails. reason: can't get the instance list

Posted by GitBox <gi...@apache.org>.
wu-sheng commented on issue #6596:
URL: https://github.com/apache/skywalking/issues/6596#issuecomment-804601544


   This seems more like the usage of Nacos, than SkyWalking.


-- 
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:
users@infra.apache.org



[GitHub] [skywalking] wu-sheng commented on issue #6596: Health check fails. reason: can't get the instance list

Posted by GitBox <gi...@apache.org>.
wu-sheng commented on issue #6596:
URL: https://github.com/apache/skywalking/issues/6596#issuecomment-803937104


   Read how `NacosCoordinator#queryRemoteNodes` works.


-- 
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:
users@infra.apache.org



[GitHub] [skywalking] ktpktr0 removed a comment on issue #6596: Health check fails. reason: can't get the instance list

Posted by GitBox <gi...@apache.org>.
ktpktr0 removed a comment on issue #6596:
URL: https://github.com/apache/skywalking/issues/6596#issuecomment-804740345


   I upgraded es cluster to 6.8, and this error no longer appears. But dynamic configuration failed


-- 
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:
users@infra.apache.org



[GitHub] [skywalking] ktpktr0 commented on issue #6596: Health check fails. reason: can't get the instance list

Posted by GitBox <gi...@apache.org>.
ktpktr0 commented on issue #6596:
URL: https://github.com/apache/skywalking/issues/6596#issuecomment-805538241


   I upgraded the ES version and the error no longer appears. An attempt was made to update the alarm configuration, but the log display is null
   ```
   2021-03-24 06:25:44,289 - org.apache.skywalking.oap.server.library.client.elasticsearch.ElasticSearchClient -9131782 [pool-7-thread-1] INFO  [] - Synchronous bulk took time: 7079 millis, size: 36
   2021-03-24 06:25:51,242 - org.apache.skywalking.oap.server.analyzer.provider.trace.UninstrumentedGatewaysConfig -9138735 [pool-6-thread-1] INFO  [] - Updating uninstrumented gateways with: null
   2021-03-24 06:25:51,242 - org.apache.skywalking.oap.server.core.alarm.provider.AlarmRulesWatcher -9138735 [pool-6-thread-1] INFO  [] - Update alarm rules to Rules(rules=[], webhooks=[], grpchookSetting=null, slacks=null, wecchats=null, compositeRules=[], dingtalks=null, feishus=null)
   2021-03-24 06:25:54,346 - org.apache.skywalking.oap.server.library.client.elasticsearch.ElasticSearchClient -9141839 [pool-7-thread-1] INFO  [] - Synchronous bulk took time: 7054 millis, size: 37
   ```


-- 
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:
users@infra.apache.org



[GitHub] [skywalking] wu-sheng closed issue #6596: Health check fails. reason: can't get the instance list

Posted by GitBox <gi...@apache.org>.
wu-sheng closed issue #6596:
URL: https://github.com/apache/skywalking/issues/6596


   


-- 
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:
users@infra.apache.org