Open vigne opened 8 years ago
Hi Ralph,
I believe this comes down to the default name resolution behavior of Ruby, but there are libraries like Resolv that will return all A records. It's something I will look into in the next couple days to see how much effort will be involved in bringing it in. After that, I'll update the issue with a time estimate, etc.
Thanks for bringing this to my attention, I wasn't even aware that a logstash plugin was using OnStomp.
Hi,
Thanks for looking into this. Your help is very much appreciated.
Looking forward to your conclusion.
Cheers, Ralph
On Mon, Mar 14, 2016, 13:36 Ian Eccles notifications@github.com wrote:
Hi Ralph,
I believe this comes down to the default name resolution behavior of Ruby, but there are libraries like Resolv that will return all A records. It's something I will look into in the next couple days to see how much effort will be involved in bringing it in. After that, I'll update the issue with a time estimate, etc.
Thanks for bringing this to my attention, I wasn't even aware that a logstash plugin was using OnStomp.
— Reply to this email directly or view it on GitHub https://github.com/iande/onstomp/issues/31#issuecomment-196293037.
Hi ! 2 years - 1 day should account for a couple of days :D Did you per chance have any look at this issue ? We are seeing the same :-) Thanks ! Chris
Hi,
I already submitted this report on the Stomp plugin of Logstash, but I think it ultimately goes down to this library.
I have a cluster of four message broker sharing one DN i.e. all four IPs are registered for the same DN.
`nslookup mb Server: 192.168.1.10 Address: 192.168.1.10#53
Name: mb Address: 192.168.1.100 Name: mb Address: 192.168.1.101 Name: mb Address: 192.168.1.102 Name: mb Address: 192.168.1.103`
Now it seems that only one broker from DNS response is used (e.g. 192.168.1.100) instead of all four.
Currently we defined all four separately, but this solution is not great as it requires manual maintenance. Therefore I was hoping you could extend the library to open one connection for each IP in the DNS response to fix this issue.
Thanks for considering!
Cheers, Ralph