Uploaded image for project: 'netconf'
  1. netconf
  2. NETCONF-584

Netconf connection is very slow in Neon

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved
    • High
    • Resolution: Done
    • Neon
    • Neon
    • Netconf
    • None

    Description

      Cluster test is currently failing in Neon:

      https://jenkins.opendaylight.org/releng/view/netconf/job/netconf-csit-3node-clustering-scale-only-neon/

      The reason is the netconf connection to the test tool takes very long time to get established:

      From a karaf log in Neon, it takes 35 sec to establish a connection:

      2018-11-23T09:56:25,668 | INFO  | opendaylight-cluster-data-notification-dispatcher-58 | NetconfTopologyUtils             | 300 - org.opendaylight.netconf.topology-singleton - 1.6.0 | RemoteDevice{netconf-test-device} : using the default directory cache/schema
      2018-11-23T09:56:25,720 | INFO  | opendaylight-cluster-data-akka.actor.default-dispatcher-3 | NetconfTopologyContext           | 300 - org.opendaylight.netconf.topology-singleton - 1.6.0 | Master was selected: IpAddress{_ipv4Address=Ipv4Address{_value=10.30.170.185}}
      2018-11-23T09:56:25,893 | INFO  | opendaylight-cluster-data-akka.actor.default-dispatcher-3 | RemoteDeviceConnectorImpl        | 300 - org.opendaylight.netconf.topology-singleton - 1.6.0 | RemoteDevice{netconf-test-device}: Concurrent rpc limit is smaller than 1, no limit will be enforced.
      2018-11-23T09:56:43,476 | WARN  | sshd-SshClient[37a6a20]-nio2-thread-3 | AcceptAllServerKeyVerifier       | 140 - org.apache.sshd.core - 2.0.0 | Server at /10.30.170.185:17830 presented unverified RSA key: SHA256:XjJQHnRvql9JMskfq1z3r4PkLnsid3BfkIudC80RE0k
      2018-11-23T09:57:00,299 | INFO  | remote-connector-processing-executor-11 | MasterSalFacade                  | 300 - org.opendaylight.netconf.topology-singleton - 1.6.0 | Device RemoteDevice{netconf-test-device} connected - registering master mount point
      2018-11-23T09:57:00,316 | INFO  | remote-connector-processing-executor-11 | NetconfDevice                    | 296 - org.opendaylight.netconf.sal-netconf-connector - 1.9.0 | RemoteDevice{netconf-test-device}: Netconf connector initialized successfully
      

      Same test is Fluorine takes 5 secs:

      2018-11-23T21:08:11,758 | INFO  | opendaylight-cluster-data-notification-dispatcher-57 | NetconfTopologyUtils             | 287 - org.opendaylight.netconf.topology-singleton - 1.5.2 | RemoteDevice{netconf-test-device} : using the default directory cache/schema
      2018-11-23T21:08:11,878 | INFO  | opendaylight-cluster-data-akka.actor.default-dispatcher-38 | NetconfTopologyContext           | 287 - org.opendaylight.netconf.topology-singleton - 1.5.2 | Master was selected: IpAddress{_ipv4Address=Ipv4Address{_value=10.30.171.2}}
      2018-11-23T21:08:12,170 | INFO  | opendaylight-cluster-data-akka.actor.default-dispatcher-38 | RemoteDeviceConnectorImpl        | 287 - org.opendaylight.netconf.topology-singleton - 1.5.2 | RemoteDevice{netconf-test-device}: Concurrent rpc limit is smaller than 1, no limit will be enforced.
      2018-11-23T21:08:14,221 | WARN  | sshd-SshClient[7bacd182]-nio2-thread-4 | AcceptAllServerKeyVerifier       | 134 - org.apache.sshd.core - 2.0.0 | Server at /10.30.171.2:17830 presented unverified RSA key: SHA256:jweQ/hbCJY/oBn8B7y8NPGPLTcH1EYgy+dabW5X46gs
      2018-11-23T21:08:16,362 | INFO  | remote-connector-processing-executor-11 | MasterSalFacade                  | 287 - org.opendaylight.netconf.topology-singleton - 1.5.2 | Device RemoteDevice{netconf-test-device} connected - registering master mount point
      2018-11-23T21:08:16,391 | INFO  | remote-connector-processing-executor-11 | NetconfDevice                    | 282 - org.opendaylight.netconf.sal-netconf-connector - 1.8.2 | RemoteDevice{netconf-test-device}: Netconf connector initialized successfully
      

      Single instance netconf connection in Neon also takes more time than usual (18 secs):

      2018-11-20T03:28:50,648 | INFO  | opendaylight-cluster-data-notification-dispatcher-43 | AbstractNetconfTopology          | 83 - netconf-topology-config - 1.6.0 | Connecting RemoteDevice{Uri{_value=netconf-test-device}} , with config Node{getNodeId=Uri{_value=netconf-test-device}, augmentations={interface org.opendaylight.yang.gen.v1.urn.opendaylight.netconf.node.topology.rev150114.NetconfNode=NetconfNode{getActorResponseWaitTime=5, getBetweenAttemptsTimeoutMillis=2000, getConcurrentRpcLimit=0, getConnectionTimeoutMillis=20000, getCredentials=LoginPassword{getPassword=topsecret, getUsername=admin, augmentations={}}, getDefaultRequestTimeoutMillis=60000, getHost=Host{_ipAddress=IpAddress{_ipv4Address=Ipv4Address{_value=10.30.170.145}}}, getKeepaliveDelay=0, getMaxConnectionAttempts=0, getPort=PortNumber{_value=17830}, getSchemaCacheDirectory=schema, getSleepFactor=1.5, isReconnectOnChangedSchema=false, isSchemaless=false, isTcpOnly=false}}}
      2018-11-20T03:28:50,651 | INFO  | opendaylight-cluster-data-notification-dispatcher-43 | AbstractNetconfTopology          | 83 - netconf-topology-config - 1.6.0 | Concurrent rpc limit is smaller than 1, no limit will be enforced for device RemoteDevice{netconf-test-device}
      2018-11-20T03:28:52,379 | WARN  | sshd-SshClient[78608917]-nio2-thread-7 | AcceptAllServerKeyVerifier       | 149 - org.apache.sshd.core - 2.0.0 | Server at /10.30.170.145:17830 presented unverified RSA key: SHA256:TfybKihnH82uOinnT8MzbdILu8oZU2ku//sClM2e67c
      2018-11-20T03:29:08,612 | INFO  | remote-connector-processing-executor-1 | NetconfDevice                    | 407 - org.opendaylight.netconf.sal-netconf-connector - 1.9.0 | RemoteDevice{netconf-test-device}: Netconf connector initialized successfully
      

      Finally, I changed testool version in Neon test to Fluorine but this did not help so the issue has to be in the controller itself.

      Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          People

            JMorvay Jakub Morvay
            ecelgp Luis Gomez
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: