Carlos Justiniano

@jkyberneees on startup, your hapi-service-test should have sent a message to hydra-router with its updated routes.

@jkyberneees I looked into this. I don't see a way to address it. I think it's up to the service builder to ensure that routes are not reused by other...

@arn-the-long-beard which version of hydra-cli are you using? How comfortable are you with Redis? Is this happening locally or on a production server?

@PraveenShrivastava11jan when you say that you're `running three local redis instance on port 5353, 5352, 5351` are you saying that you have three instances of Redis running? Or do you...

@PraveenShrivastava11jan Hydra routing (without knowledge of IP/PORT) is accomplished with the use of a shared Redis server. All Hydra-enabled services (that is services which import the hydra or hydra-express NPM...

@PraveenShrivastava11jan Hydra services are bound to a Redis server (or redis cluster). Services using one redis instance can't communicate with services running using other redis servers. You can have services...

@PraveenShrivastava11jan is there still an outstanding issue/concern here? Or can I close this one?

@PraveenShrivastava11jan thanks for your efforts.

@intermund the most common reason for the issue above is that your hydra-router config/config.json isn't properly setup to point to your instance of Redis. Looking at your docker run command...

@intermund let us know if the above fixed your issue?