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 2018/11/16 09:28:10 UTC

[GitHub] Sunlitkid opened a new issue #1918: There is some problem in SkyWalking 6.0 with elasticsearch-5.6.8

Sunlitkid opened a new issue #1918: There is some problem in SkyWalking 6.0  with elasticsearch-5.6.8
URL: https://github.com/apache/incubator-skywalking/issues/1918
 
 
   Please answer these questions before submitting your issue.
   
   - Why do you submit this issue?
   - [x] Question or discussion
   - [x] Bug
   - [ ] Requirement
   - [ ] Feature or performance improvement
   
   ___
   ### Question
   - I know sw6.0 's default DataBase is H2 .
   sw6.0  works well with H2 ,but when I change H2 to ES  .
   There is some problem come out.
   
   Deploy step:
   1.clean es db 5.6.8 's data and start it      (skywalking 5.0 run with it  OK)
   2.open sky-walking‘s configration about es-db and close H2‘s configration
   3.click startup.bat 
   4. start my service and inject to sw ,then I called my service's HTTP-interface
   5.open sw-web and I saw some [Red ERROR]  at top right corner
   
   
   ERROR:
   【Dashboard  page】:  and this page can't show any data
   Exception while fetching data (/getTopNSlowEndpoint) : Elasticsearch exception [type=search_phase_execution_exception, reason=all shards failed]
   
   Exception while fetching data (/getTopNServiceThroughput) : Elasticsearch exception [type=search_phase_execution_exception, reason=all shards failed]
   
   【Service page】: and this page can't show any data
   Exception while fetching data (/getSlowEndpoint) : Elasticsearch exception [type=search_phase_execution_exception, reason=all shards failed]
   
   Exception while fetching data (/getServiceInstanceThroughput) : Elasticsearch exception [type=search_phase_execution_exception, reason=all shards failed]
   
   Exception while fetching data (/getServiceTopology) : Elasticsearch exception [type=search_phase_execution_exception, reason=all shards failed]
   
   
   And I saw some info in 【skywalking-oap-server.log】
   one of debug :
   -----start------
   Caused by: org.elasticsearch.client.ResponseException: method [POST], host [http://localhost:9200], URI [/service_relation_client_side/type/_search?typed_keys=true&ignore_unavailable=false&expand_wildcards=open&allow_no_indices=true&search_type=query_then_fetch&batched_reduce_size=512], status line [HTTP/1.1 500 Internal Server Error]
   {"error":{"root_cause":[{"type":"aggregation_execution_exception","reason":"Invalid term-aggregator order path [_key]. Unknown aggregation [_key]"}],"type":"search_phase_execution_exception","reason":"all shards failed","phase":"query","grouped":true,"failed_shards":[{"shard":0,"index":"service_relation_client_side","node":"YCskJjy9SCGioeF_KGqQcg","reason":{"type":"aggregation_execution_exception","reason":"Invalid term-aggregator order path [_key]. Unknown aggregation [_key]"}}]},"status":500}
   -----end------	
   
   and I called The url 
   
   localhost:9200/service_relation_client_side/type/_search?typed_keys=true&ignore_unavailable=false&expand_wildcards=open&allow_no_indices=true&search_type=query_then_fetch&batched_reduce_size=512
   
   And response is  empty data
   
   {
       "took": 1,
       "timed_out": false,
       "_shards": {
           "total": 2,
           "successful": 2,
           "skipped": 0,
           "failed": 0
       },
       "hits": {
           "total": 0,
           "max_score": null,
           "hits": []
       }
   }
   
   
   
   ___
   ### Bug
   
   I thought there are some bugs
   
   because : 
   Page 【Trace】 can saw all my traces .
   Page 【End Point】 can saw all my data such as cpm / sla / avg Response Time    and     They are all right.
   
   But Page 【dashboard \Topology \Service】 throws some error  
   
   I thought it is  a  query bug about ES db
   ___
   
   Thanks for your reading

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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


With regards,
Apache Git Services