Uploaded image for project: 'OpenFlowPlugin'
  1. OpenFlowPlugin
  2. OPNFLWPLUG-686

Li-Plugin: Transaction failure exception in 3-node cluster while processing port statistics

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved
    • Resolution: Done
    • None
    • None
    • General
    • None
    • Operating System: All
      Platform: All

    • 5873

    Description

      I am testing net-virt with openflowplugin lithium plugin in 3-node cluster environment. Whenever OVSDB connects to net-virt, it creates the bridge and set the controller of the bridge to all the three controllers in the 3-node cluster. Whichever instance of openflowplugin become the owner of the openflow bridge, it starts throwing following exception while processing the port statisitics

      2016-05-11 07:25:47,207 | INFO | ntLoopGroup-11-4 | LifecycleConductorImpl | 289 - org.opendaylight.openflowplugin.impl - 0.3.0.SNAPSHOT | Starting/Stopping services for node Uri [_value=openflow:82098239239489] was successful
      2016-05-11 07:25:48,676 | WARN | ntLoopGroup-11-4 | StatisticsGatheringUtils | 289 - org.opendaylight.openflowplugin.impl - 0.3.0.SNAPSHOT | stats processing of type OFPMPPORTSTATS for node Uri [_value=openflow:82098239239489] failed during write-to-tx step
      java.lang.IllegalStateException: Transaction DOM-CHAIN-2-3 is no longer running
      at com.google.common.base.Preconditions.checkState(Preconditions.java:197)[65:com.google.guava:18.0.0]
      at org.opendaylight.controller.cluster.databroker.AbstractDOMBrokerWriteTransaction.checkRunning(AbstractDOMBrokerWriteTransaction.java:145)[181:org.opendaylight.controller.sal-distributed-datastore:1.4.0.SNAPSHOT]
      at org.opendaylight.controller.cluster.databroker.AbstractDOMBrokerWriteTransaction.put(AbstractDOMBrokerWriteTransaction.java:74)[181:org.opendaylight.controller.sal-distributed-datastore:1.4.0.SNAPSHOT]
      at org.opendaylight.controller.md.sal.dom.spi.ForwardingDOMDataReadWriteTransaction.put(ForwardingDOMDataReadWriteTransaction.java:49)[150:org.opendaylight.controller.sal-core-spi:1.4.0.SNAPSHOT]
      at org.opendaylight.controller.md.sal.binding.impl.AbstractWriteTransaction.put(AbstractWriteTransaction.java:46)[153:org.opendaylight.controller.sal-binding-broker-impl:1.4.0.SNAPSHOT]
      at org.opendaylight.controller.md.sal.binding.impl.BindingDOMWriteTransactionAdapter.put(BindingDOMWriteTransactionAdapter.java:40)[153:org.opendaylight.controller.sal-binding-broker-impl:1.4.0.SNAPSHOT]
      at org.opendaylight.openflowplugin.impl.device.TransactionChainManager.writeToTransaction(TransactionChainManager.java:208)[289:org.opendaylight.openflowplugin.impl:0.3.0.SNAPSHOT]
      at org.opendaylight.openflowplugin.impl.device.DeviceContextImpl.writeToTransaction(DeviceContextImpl.java:328)[289:org.opendaylight.openflowplugin.impl:0.3.0.SNAPSHOT]
      at org.opendaylight.openflowplugin.impl.statistics.StatisticsGatheringUtils.processNodeConnectorStatistics(StatisticsGatheringUtils.java:380)[289:org.opendaylight.openflowplugin.impl:0.3.0.SNAPSHOT

      Full log file for one of the controller from 3-node cluster is attached with the bug.

      Attachments

        Issue Links

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

          Activity

            People

              Avishnoi Anil Vishnoi
              Avishnoi Anil Vishnoi
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: