I know the lmax is used to process the notifications in md-sal, but in my environment, once the lmax thread take up the cpu near 100% for a long time, my controller will not work normally, and the controller will disconnect the openflow switch, all hosts and switches is disappeared in the topology, and I do not know to solve this problem, can you help to find what is wrong with it ?
At 2017-03-28 23:47:56, "Robert Varga" <[email protected]> wrote: >On 27/03/17 03:30, xiaohongaifeng wrote: >> hello all: >> I use odl controller to do some test, after I install all feature, >> I use mininet simulate some hosts(230 hosts) and 3 switches, I found my >> odl controller does not work, and I see the odl java process take >> up nearly 100% cpu, and I use top -p pid -H and jstack found the lmax >> thread is always runable, I do no know what wrong with it ? can you help >> me ? > >+openflowplugin-dev for openflow questions. > >LMAX thread being busy is normal, depending on what is going on. Notably >it is used to shuffle notifications around (such as PacketIns). > >Bye, >Robert >
_______________________________________________ openflowplugin-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
