[ODLPARENT-112] Nitrogen Mdsal northbound server is slow to accept SSH connections Created: 21/Aug/17  Updated: 05/Sep/18  Resolved: 05/Sep/18

Status: Resolved
Project: odlparent
Component/s: General
Affects Version/s: 3.0.2
Fix Version/s: None

Type: Bug
Reporter: Vratko Polak Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


External issue ID: 9020

 Description   

While Carbon takes less than a second [0], Nitrogen frequently takes more than 10 seconds [1] to accept a connection, causing test failures.

Karaf.log [2] shows the pause happens after "Generating host key" at 19:57:39,100.

[0] https://logs.opendaylight.org/releng/jenkins092/netconf-csit-1node-userfeatures-only-carbon/564/log.html.gz#s1-s3-s1-t1-k3-k1-k2
[1] https://logs.opendaylight.org/releng/jenkins092/netconf-csit-1node-userfeatures-only-nitrogen/115/log.html.gz#s1-s3-s1-t1-k3-k1-k2
[2] https://logs.opendaylight.org/releng/jenkins092/netconf-csit-1node-userfeatures-only-nitrogen/115/odl1_karaf.log.gz



 Comments   
Comment by Jakub Morvay [ 05/Sep/17 ]

Yeah, this seems like performance regression in setting up SSH connection to NETCONF northbound servers in some cases. This was possibly introduced by bumping crypto libraries to newer versions or tweaking some crypto settings.

Updating NETCONF user guide with this regression:
https://git.opendaylight.org/gerrit/#/c/62664/

This causes the large part of NETCONF MDSAL suite to be unusable, since setting up the SSH connection to MDSAL northbound is its first step. Increasing timeout to 60 seconds so the suite can connect to MDSAL northbound and perform its other tests.
https://git.opendaylight.org/gerrit/#/c/62665/

Comment by Andrej Vanko [ 09/Oct/17 ]

moved to ODL parent project

Comment by Robert Varga [ 05/Sep/18 ]

The loop-back connection is no longer used and this only happens on first startup.

Generated at Wed Feb 07 20:27:40 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.