On subscriptions made for pull consumers when the user has asked to "bind", there are conditions when the consumer info lookup will fail, namely when the consumer is cross account and the consumer info lookup has not been exported.
Implementations
Some clients currently ignore this error. This is what is to be discussed.
Consumer Info Lookup Considerations
Some implementations are looking up the consumer in all cases. If the consumer cannot be found, either b/c it's not actually does not exist or the export is not there, the server will respond with a 503 No Responders to the consumer info request. This should be ignored.
Consumer Really Doesn't Exist, Same Account
If the consumer really does not exist within the same account, the pull sends nothing and next message requests fail as if there are simply no messages.
Consumer Really Doesn't Exist, Cross Account
If the consumer really does not exist cross account, you will receive a no responders as the first message after making the pull request. This should be surfaced to the user as an error.
Overview
On subscriptions made for pull consumers when the user has asked to "bind", there are conditions when the consumer info lookup will fail, namely when the consumer is cross account and the consumer info lookup has not been exported.
Implementations
Some clients currently ignore this error. This is what is to be discussed.
Consumer Info Lookup Considerations
Some implementations are looking up the consumer in all cases. If the consumer cannot be found, either b/c it's not actually does not exist or the export is not there, the server will respond with a 503 No Responders to the consumer info request. This should be ignored.
Consumer Really Doesn't Exist, Same Account
If the consumer really does not exist within the same account, the pull sends nothing and next message requests fail as if there are simply no messages.
Consumer Really Doesn't Exist, Cross Account
If the consumer really does not exist cross account, you will receive a no responders as the first message after making the pull request. This should be surfaced to the user as an error.