confused handler when rpc client catch serve rerror about go-micro HOT 7 CLOSED

The selector is pluggable. You can write a new selector that suits your requirements. We could potentially provide one that doesn't blacklist. But the fact that the call fails 3 times implies there's an issue, hence blacklisting the node. Only that specific node is blacklisted. So if you're only running one instance of a service, yes it's going to return no service available. Why is it throwing an error? Can you run more instances of the service?

from go-micro.

I guess the key is

what is the best way to throwing error?

for example：invalid request params and so on，they will return error，but not reason to block that specific node. People will benchmark wrong request and make all node not available

from go-micro.

I have use my own selector,problem solved.

from go-micro.

great

from go-micro.

Let us know if you open source it. Would be great to see what it looks like.

from go-micro.

ok,my team use micro on a e-commerce project, we will open source some plugins when code stable.
your great job help us reduce much work,thanks

from go-micro.

Cool. Feel free to add your company to the Users list https://github.com/micro/micro/wiki/Users

from go-micro.