Reducing disk activity of the Omada Controller

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Reducing disk activity of the Omada Controller

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Reducing disk activity of the Omada Controller
Reducing disk activity of the Omada Controller
2020-02-01 18:16:15

The omada controller is run on a variety of devices, some of which may not have storage systems which can handle large amounts of writes.

 

I was curious about reducing the write operations of the Omada Controller and I figured starting a thread would be handy.

 

On my 3.2.4 installation, I rebooted the controller and monitored the disk usage for about 8 hours, and there is definitely disk activity (overnight was about 100MB across omada and mongodb).

 

I will noted that I have already tried to disable the mongodb journaling in an effort to reduce the writes.

Warning - disabling Journaling comes at a risk of database corruption if there is a system failure - so consider your use case.

 

It think changing it was pretty:

in /opt/tplink/EAPController/properties/mongodb.properties change the linux.mongod.nojournal entry to true

 

##disable mongodb journaling in linux
linux.mongod.nojournal=true

 

Note, my copy of the file looks like it was written with MSDOS carriage returns...someone using a Windows text editor?

 

Other sources of writes are most likely the log files and the mongodb.

@R1D2 has already identifed a the omada logs are in /opt/OmadaController/logs and suggested using an tmpfs which is probably the way to go.

 

That said, I suspect the majority of writes go to /opt/tplink/EAPController/data/db

If journaling is enabled, this area was about 3GB+ on my installation. So putting that in tmpfs may require considerable amounts of memory.

 

By disabling journaling, the disk space of my database is down to 200MB, which is more feasible on my system.

 

To help manage keeping the database alive over system reboots, I have had some luck with using persist, which is a syncable ramdisk service on debian.

I'll play around with it and post here if I manage to make any progress!

  0      
  0      
#1
Options
1 Reply
Re:Reducing disk activity of the Omada Controller
2020-02-02 09:45:08

 

elmado wrote

Note, my copy of the file looks like it was written with MSDOS carriage returns...someone using a Windows text editor?

 

You can change this to UNIX file format using the vi editor (command set fileformat=unix, then write) or using tr.

The community version of Omada controller comes with this file format by default.

 

@R1D2 has already identifed a the omada logs are in /opt/OmadaController/logs and suggested using an tmpfs which is probably the way to go.

 

The community of Omada controller version uses /opt/tplink/OmadaController-x.y.z as the top-level directory where x.y.z is the version number. OmadaController is just a symlink to (historical file structure, allows to switch between old and newer versions using omadactl switch if more than one version is installed).

 

The official version still uses /opt/tplink/EAPController as the top-level directory (old name before versions 3.x).

 

Log files should go to /var/log/somedir, which on embedded systems is most often a non-persistant storage in a tmpfs. Community version did so, but after people's complaints about changes one needs to manually provide a symlink if you prefer logging under /var/log.

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#2
Options