Deassociate environment with message processor

[oyamatakuro]

Hello,

As the great feature of apigee, it can easily scale message processor with management api to associate/deassociate environment with it.

I would like to confirm on how edge process when deassociate message processor from an environment as below.

When I call the API to deassociate a message processor which is still processing API traffic at the timing, Edge can wait for the process completion to prevent any api errors?
And also does Router have some control not to foward new api request anymore to the message processor?

Thanks in advance.

Best regards,
Takuro

[DChiesa · Accepted solution]

Yes, you are correct:

When you dis-associate a Message Processor from an environment, if there are in-flight transactions, these transactions continue to run until completion. Dis-associating the MP means that no new messages arrive at that MP, for that environment. This happens at the router. The router stops sending inbound requests to the dis-associated MP.

Does this answer your questions?

[oyamatakuro]

Thanks for your answer.

Yes, so API traffic processing is not affected by deassociating message processor from an environment and does not return api error response to applications, right?

[#4]

That's correct @Takuro Oyama