On 01/19/2016 01:18 PM, Luis Gomez wrote:
> 5002 is only impacting kara.log for what I can tell. Problem is we cannot see
> further unless we remove the check on NPEs in the test or we fix this issue.
my vote is to fix this, because to me, any time a NPE shows up I think something
is about to blow up. If it's harmless, then maybe we can harmlessly find a way
to avoid logging it? If we skip the check in the test, we're going to miss
other serious issues.
Also, looking more closely at the karaf.log for that longevity run, there are
some other ugly things:
Tons of these:
No local or remote implementation available for rpc
AbsoluteSchemaPath{path=[(urn:opendaylight:flow:statistics?revision=2013-08-19)get-aggregate-flow-statistics-from-flow-table-for-all-flows]}
this:
OptimisticLockFailedException{message=Optimistic lock failed.,
errorList=[RpcError [message=Optimistic lock failed., severity=ERROR,
errorType=APPLICATION, tag=resource-denied, applicationTag=null, info=null,
cause=org.opendaylight.yangtools.yang.data.api.schema.tree.ConflictingModificationAppliedException:
Node was deleted by other transaction.]]}
Thanks,
JamO
>> On Jan 19, 2016, at 12:31 AM, Anil Vishnoi <[email protected]
>> <mailto:[email protected]>> wrote:
>>
>>
>>
>> On Mon, Jan 18, 2016 at 10:50 PM, Luis Gomez <[email protected]
>> <mailto:[email protected]>> wrote:
>>
>> Hi all,
>>
>> I spent most of the day fixing the cluster test so we can measure both
>> plugins with the same test. I have also taken a look at the longevity
>> (stability) test we have this release. Here are the observations:
>>
>> 1) I started with the Lithium plugin:
>>
>> Cluster test works better since
>> https://git.opendaylight.org/gerrit/#/c/32459/ was merged:
>>
>>
>> https://jenkins.opendaylight.org/sandbox/job/openflowplugin-csit-3node-clustering-only-beryllium/2/robot/report/log.html
>>
>> Still I see couple of consistent issues:
>>
>> - Controller does not show correct OF topology after owner recovers from
>> failure - https://bugs.opendaylight.org/show_bug.cgi?id=4999
>> - Controller does not clean operational inventory after a fail and
>> recover cycle - https://bugs.opendaylight.org/show_bug.cgi?id=5000
>>
>> Longevity test shows Out of Memory error after exactly 20 runs of
>> bringing 200 switches:
>>
>>
>> https://jenkins.opendaylight.org/releng/view/openflowplugin/job/openflowplugin-csit-1node-periodic-longevity-lithium-redesign-only-beryllium/
>>
>> Following bug has been opened:
>> https://bugs.opendaylight.org/show_bug.cgi?id=5001
>>
>> 2) I continued with He plugin:
>>
>> Cluster test does not look bad either and only consistent issue seems to
>> be delayed stats reports (>8 secs in some occasions):
>>
>>
>> https://jenkins.opendaylight.org/sandbox/job/openflowplugin-csit-3node-clustering-only-beryllium/7/robot/report/log.html
>>
>> Longevity test shows Null Pointer Errors from the very beginning:
>>
>>
>> https://jenkins.opendaylight.org/releng/view/openflowplugin/job/openflowplugin-csit-1node-periodic-longevity-only-beryllium/
>>
>> So I opened this bug:
>> ​​
>> https://bugs.opendaylight.org/show_bug.cgi?id=5002
>>
>> ​So statistics are not getting collected at all ? or it's initial exception
>> and after that it settles down ?​
>>
>>
>>
>>
>> 3) Finally I saw some inconsistencies in the controller cluster
>> implementation:
>>
>> - Cluster Entity Owner candidate list does not get updated every time
>> owner instance is killed - https://bugs.opendaylight.org/show_bug.cgi?id=5004
>> - Controller sporadically spends lot of time (>10 secs) to resolve
>> shards leaders - I am waiting to have more examples to file a bug
>>
>>
>>
>>
>> _______________________________________________
>> openflowplugin-dev mailing list
>> [email protected]
>> <mailto:[email protected]>
>> https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
>>
>>
>>
>>
>> --
>> Thanks
>> Anil
>
>
>
> _______________________________________________
> openflowplugin-dev mailing list
> [email protected]
> https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
>
_______________________________________________
openflowplugin-dev mailing list
[email protected]
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
