Closed dinuta closed 3 years ago
Thanks for submitting, I'll check it out later for the network connection now in my city is poor during this period.
It seems like the InstanceId was '' for all the services. I saw you use this info in your code to uniquely identify the application. In this case your lib override the previous entry because of that.
If it does make sense to have InstanceId same (but think not) it is a bug, otherwise not.
This is the fix in the agent: https://github.com/estuaryoss/estuary-agent-go/pull/5/files
I let the environment replicate the bug if you still need to debug it.
Thanks, Catalin
I closed the issue, thanks.
I think you should give each your instance an unique ID. However, it seems that sometimes the eureka server accepts the empty instance ids. I change some code, if the instance have no id get from eureka server, one will be generated via host name, ip address, app name and instance port. You can find the change in 0.9.7.
Hi @keijack ,
I discovered a bug in the client discovery. Version 0.9.6. Probably this is not new.
Steps to reproduce:
Expected behavior: The client sees 3 Agents and 1 discovery Actual result: The client sees 1 Agent and 1 discovery
Please have a look.
Thanks, Catalin