Community for yuuvis® RAD

0 votes
by (790 points)

Hello dear enaio/yuuvis developers,

after update to 5.10 both services index and search are reported as offline at http://service-manager-host:7273

However, when I access the /manage/health endpoint
(http://service-manager-host:7281/manage/health)

I get the following:

{
  "description": "Composite Discovery Client",
  "status": "UP",
  "discoveryComposite": {
    "description": "Composite Discovery Client",
    "status": "UP",
    "discoveryClient": {
      "description": "Composite Discovery Client",
      "status": "UP",
      "services": [
        "search",
        "index",
         ...
      ]
    },
    "eureka": {
      "description": "Remote status from Eureka server",
      "status": "UP",
      "applications": {
        "INDEX": 1,
        "SEARCH": 1,
        ...
      }
    }
  },

Both services report status 503, when i try to access their respective health endpoints.
e.g. http://service-manager-host:7291/manage/health

in service logs i see the following exception (for both services):

indexservice.7291 : java.util.concurrent.TimeoutException: null
indexservice.7291 : at java.util.concurrent.FutureTask.get(FutureTask.java:205)
indexservice.7291 : at com.netflix.discovery.TimedSupervisorTask.run(TimedSupervisorTask.java:64)
indexservice.7291 : at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
indexservice.7291 : at java.util.concurrent.FutureTask.run(FutureTask.java:266)
indexservice.7291 : at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
indexservice.7291 : at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
indexservice.7291 : at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
indexservice.7291 : at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
indexservice.7291 : at java.lang.Thread.run(Thread.java:748)

Any help appreciated!

Best regards,
Umar

1 Answer

+1 vote
by (1.5k points)
selected by
 
Best answer

Setting "spring.elasticsearch.rest.uris: 'es-server-ip:9200'" should fix this.

https://developer.enaio.org/redline/pages/viewpage.action?pageId=26837032

Regards,
Robert

by (790 points)
Yep! That has done the trick!
Thank you Robert!

Best wishes,
Umar

Related questions

+1 vote
1 answer
0 votes
6 answers
0 votes
1 answer
asked Apr 30, 2019 by katsikiotisP (200 points)
...