From 1262783cca929efa4d9d6fb13df767d0384c84ce Mon Sep 17 00:00:00 2001
From: Idan Hefetz <idan.hefetz@nokia.com>
Date: Wed, 23 May 2018 08:35:08 +0000
Subject: [PATCH] rpc server executor reverted to blocking

The threading executor consumes allot of memory, as the max thread count
is 5 x cpus, and this cannot be limited.
Blocking or threading doesnt make allot of difference for our needs,
as api parallelism is blocked by the GIL.

Change-Id: I10eab99204c779d93590552c2eb4b3ed207975d7
---
 vitrage/rpc.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/vitrage/rpc.py b/vitrage/rpc.py
index 2b443059c..4e874df15 100644
--- a/vitrage/rpc.py
+++ b/vitrage/rpc.py
@@ -107,6 +107,6 @@ def get_server(target, endpoints, transport, serializer=None):
     return messaging.get_rpc_server(transport,
                                     target,
                                     endpoints,
-                                    executor='threading',
+                                    executor='blocking',
                                     serializer=serializer,
                                     access_policy=access_policy)