Bug 35021 – Heavy load on server: Opening new module in UMC causes errors

Bug 35021 - Heavy load on server: Opening new module in UMC causes errors


Summary:	Heavy load on server: Opening new module in UMC causes errors

Status:	NEW

Product:	UCS
Classification:	Unclassified
Component:	UMC (Generic)
Version:	UCS 5.0
Hardware:	Other Linux

Importance:	P5 normal with 2 votes (vote)
Target Milestone:	---
Assigned To:	UMC maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2014-05-30 10:49 CEST by Dirk Wiesenthal
Modified:	2020-06-22 14:30 CEST (History)
CC List:	3 users (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	4: Minor Usability: Impairs usability in secondary scenarios
Who will be affected by this bug?:	2: Will only affect a few installed domains
How will those affected feel about the bug?:	2: A Pain – users won’t like this once they notice it
User Pain:	0.091
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):	Error handling
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Dirk Wiesenthal

2014-05-30 10:49:32 CEST

From the logs:

30.05.14 10:47:11.021  DEBUG_INIT
...
30.05.14 10:47:23.657  SSL         ( INFO    ) : Server listening to connections

This is 12 seconds from "init" to "ready". Too much for the UMC-server which tells the user that communication with the module process failed.

Opening the module a second time worked fine (new module process, this time only 1 second from "init" to "ready").

Comment 1 Florian Best

2014-12-18 14:02:26 CET

hm, what's the problem more concrete? which module? how to reproduce?

Comment 2 Dirk Wiesenthal

2014-12-19 14:27:48 CET

I do not know which module (appcenter?). Should not really matter. The problem is the too-fast error message "connection to module process failed" although the module is fine, just slow. Not sure whether this is a server or module issue. But the result is a useless opened module and a disappointed user.

Hard to reproduce. I guess a huge IO load is necessary.

Comment 3 Florian Best

2014-12-19 14:47:17 CET

I think if a python module import takes 12 seconds something is wrong in the design of the module.
The appcenter e.g. opens itself and directly checks for a license:
Failed to load license information: {'desc': "Can't contact LDAP server"}

If this would be done in the Instance.init() method everything would be more fine.

Comment 4 Florian Best

2016-09-23 11:34:34 CEST

I see this very often for the appcenter and udm module.