https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/TSDR-8 tsdr <p>Environment:<br/> Build#2135 (Integration Build)<br/> Topology#Tree<br/> sudo mn --topo tree,5 --switch ovsk,protocols=OpenFlow13 --controller remote,ip=10.16.148.232</p> <p>Problem:<br/> On HBase datastore,"tsdr:list FlowTableStats" doesn't returns the output on karaf console.Its hungs karaf console.</p> <p>Step to Reproduce:<br/> 1.Install odl-tsdr-hbase on ODL controller<br/> 2.Once HBase collector started,start the tree topology (as given in environment) on mininet VM <span class="error">&#91;Note: Mininet VM running on remotely&#93;</span><br/> 3.Wait for 1~1.30 hours collection.<br/> 4.Issue "tsdr:list FlowTableStats" on karaf console doesn't return output/thrown any error.Waited for almost 16 minutes.</p> <p>However "tsdr:list Portstats" returns output on 75 seconds.<br/> "tsdr:list FlowStats" returns output on 30 seconds </p> <p>TSDR collection doesn't broken and also updated in HBase DB.</p> <p>Note:<br/> ===<br/> During problematic time HBase row counts are,<br/> FlowTableMetrics : 2255901 rows<br/> InterfaceMetrics: 127320 rows<br/> FlowMetrics: 27716 rows</p> <p>Operating System: All<br/> Platform: All</p> TSDR-8

tsdr:list FlowTablStats command hungs the karaf console on HBase DataStore

Bug Verified Done YuLing Chen Vasanthan Balasubramaniyan Tue, 2 Jun 2015 09:40:57 +0000 Fri, 19 Jun 2015 05:34:44 +0000 Fri, 19 Jun 2015 05:34:44 +0000 unspecified General 0 4 <p>Reduced the maximum result size from default (java.lang.Long.MAX_VALUE) to 1000 (Bytes). Unit tested against 4.5 lakhs entries which took 7-8 seconds to respond. This response time is consistent irrespective of entries count.</p> <p>Attachment hs_err_pid21378.log has been added with description: crash hs_err_pid log</p> <p>On RC1 build: distribution-karaf-0.3.0-Lithium-RC1-v201506160017</p> <p>Still this issue reproduciable<br/> 1.Sometimes generated outofMemory<br/> 2.Sometime crashed the ODL Controller.</p> <p>The root cause was that 1) when inserting into hbase, for each row we requested a connection to hbase and 2) we didn't return the connection to the connection pool after the thread is done. This caused a huge number of insertion threads in memory that led to OOM issue.</p> <p>Fixes: 1) get one connection and insert the list of rows into hbase, 2) return the connection to the pool so that there would not be so many insertion threads in memory that caused the OOM issue.</p> <p>Environment:<br/> Build#RC1 (distribution-karaf-0.3.0-Lithium-RC1-v201506180115.zip)<br/> Topology: Tree<br/> sudo mn --controller=remote,ip=10.16.148.232 --topo=tree,6 --switch ovsk,protocols=OpenFlow13<br/> DataStore: odl-tsdr-hbase</p> <p>Verification details<br/> ====================<br/> Tested with 64 ovsk switches with collection of ~18 hours.<br/> Karaf console command respond within 5 seconds (after 18 hrs)</p> <p>After ~18 hours datastore records (in hbase),</p> <p>PortStats : 4015288 row(s)<br/> FlowTableStats: 64304667 row(s)<br/> FlowStats: 841882 row(s)</p> Development External issue ID 3542 External issue URL Issue Type ODL SR Target Milestone Priority Rank 0|i02vdz: