https://jira.akraino.org This file is an XML representation of an issue en-us 9.4.5 940005 11-04-2023 https://jira.akraino.org/browse/IEC-12 Integrated Edge Cloud <p>Deploy SEBA on MACCHIATObin, encount one issue, platform kafka pod alway at the stage of Crash, not running; Trough logs info, I found The link between kafka pod and zookeeper pod cannot be established.<br/> Deploy seba on the ThunderX2 and Amper servers, respectively;<br/> SEBA runs normally on Amper server; But on the ThunderX2 server, SEBA is abnormal;</p> <p>This task will fixed the issues about deploy SEBA .</p> IEC-12

Deploy SEBA on MACCHIATObin and ThunderX2

Task High Done Done Jianlin Lv Jianlin Lv Release_1 Fri, 26 Apr 2019 07:29:41 +0000 Thu, 9 May 2019 04:51:00 +0000 Thu, 9 May 2019 04:51:00 +0000 0 1 <p>5/9/2019<br/> 1.Deploy SEBA on  MACCHIATObin successfully.  All pods in correct condition.</p> <p><span class="image-wrap" style=""><img src="https://jira.akraino.org/secure/attachment/10016/10016_image-2019-05-09-12-50-37-994.png" style="border: 0px solid black" /></span></p> <p>5/7/2019<br/> 1.reconfig kernel module, enable NETFILTER_XT_MATCH_STATISTIC and other kernel module,  iptables rule running correctlly ;</p> <p>5/5/2019<br/> Testing k8s basci service using Nginx, when try to connect to port 80, the connection refused</p> <p>the log of kube-proxy show some error about iptable_restore;</p> <p>Now I make sure iptable rules is abnormal;</p> <p>manually config iptables relevant to NGINX, the service work correctly .</p> <p>4/26/2019</p> <p>By observing the actual memory utilization of ThunderX2, it is found that if SEBA is deployed on a single node, at least 15G of memory is required;</p> <p>4/26/2019</p> <p>Fixed issue of failling to deploy SEBA on ThunderX2;<br/> The problem is that once SEBA is deployed, ThunderX2 gets stuck and offline;<br/> After investigation, I found that oom caused kernel crash. Under normal startup, the memory occupation rate was 90%, and there were other applications in the system that occupied too much memory. It was strange that it could not locate which application occupied these memory through ps command.<br/> After uninstalling the useless service, the memory occupation rate returns to normal and the SEBA deployment is successful.</p> Development Rank 0|i000f3: