Search Engine: Elastic

Article ID: 130553, created on Mar 31, 2017, last review on Mar 31, 2017

  • Applies to:
  • Operations Automation

Symptoms

Load Balancer creation takes hours to complete. The Load Balancer hangs in Creation in progress* state for all this time and then turns to **Ready.

Per OACI IM log at /var/log/pa/vps.log, there are no issues faced:

2017-03-30 21:41:44,129 (84f317ce-577b-41e1-a6bf-ed0ec842a053) INFO  CustomLoggingFilter [Grizzly-worker(1)] - 26410 * Server in-bound request
26410 > POST http://192.168.10.12:4465/paci/v1.0/of/1000102/load-balancer/1000123/create/LoadBalancer
...
2017-03-31 02:09:44,304 (84f317ce-577b-41e1-a6bf-ed0ec842a053) INFO  AsyncClientImpl [AsyncClientResponseThread-4] - response: Response{status=200, message=}

Checking /var/log/parallels.log on the Virtuozzo node side:

03-30 23:23:36.134 F /disp:824958:27837/ Task '20Task_MigrateCtTarget' with uuid = {db598551-81f9-48c7-95a5-cb370b99388b} was started. Flags = 0x18000
...
03-31 02:06:24.551 F /disp:824958:27837/ Task '20Task_MigrateCtTarget' with uuid = {db598551-81f9-48c7-95a5-cb370b99388b} was finished with result PRL_ERR_SUCCESS (0) 

Cause

Poor Virtuozzo migration speed between OACI storage node and OACI hardware node, destined for the Load Balancer creation.

Resolution

Contact Virtuozzo Team to analyze the reason of the slow migration speed between the nodes.

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF