Posted: Fri Jun 01, 2018 9:14 am Post subject: Managing High load failure scenarios for the Aggregation nod
Newbie
Joined: 21 May 2018 Posts: 6
A common scenario in WMB message flows is when the aggregation message flows call multiple validation services which are supposed to return a reply within 2 minutes.
In normal scenarios, 10 to 50 requests are handled per minute.
In high volume load scenarios, more than 100 requests are received per minute which leads to the failure of aggregation message flows. The aggregate replies from validation services will pile up on the internal broker aggregation reply queues making any new requests impossible.
The piled up requests have to be cleared and only then the failed requests can be retried using a retry message flow which reads the aggregation requests from the input backout queue and processes them once again.
This issue requires attention from IBM and can be fixed by having queue depth monitors or triggers on the internal aggregate request and reply queues. These piled up messages should be cleared automatically and after the timeout of 2 minutes which was mentioned in the aggregation message flows.
I would like to bring this issue to the notice of IBM and a PMR has to be raised for this. We faced this issue in production and would like to request a fix for the issue.
Posted: Mon Jun 04, 2018 6:19 am Post subject: Re: Managing High load failure scenarios for the Aggregation
Partisan
Joined: 24 Aug 2007 Posts: 365 Location: Columbus, OH
eai_developer123 wrote:
I would like to bring this issue to the notice of IBM and a PMR has to be raised for this. We faced this issue in production and would like to request a fix for the issue.
Well the PMR will bring this issue to IBM's notice.
Let us know their answer and if they release a fix for this issue.
I will say that the numbers you are talking about seem low for an issue to occur though. We have aggregations with higher volumes that work just fine.
We did have an aggregation issue last year where messages were arriving on the fan in queues before the aggregation request node had finished recording the message and therefore the quickly arriving messages were marked as unknown. We had to make the fan out requests a transaction to ensure the aggregation was recorded before the messages could arrive on the fan in queues.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum