nameservice.c: adjust writing files #114
Conversation
At Freifunk Berlin we experienced fairly random updates on the files. This resulted from the calc_jitter() function in the scheduler.c. By calling the function with a jitter of 0% there shouldn't be any randomness anymore and the nameservice-files should get written on schedule. Signed-off-by: Martin Hübner <[email protected]>
|
@Akira25, I'm just curios ...
|
|
@mathiashro The impact is that we observed delays for nameservice updates of several hours even when setting |
|
@Noki / @Akira25, do we want to wait for further comments and community feedback or just merge it? (We may introduce also a config parameter if we do have different requirements by different OLSR users.) For me we are fine to merge and I can finalize that. As for our mesh (Rostock) we did not had the issue with the backup yet but currently mainly try to remove our dependency on the nameservice plugin for all central services. Proceed with merge or wait? |
|
@mathiashro I'd prefer to test this for me. Maybe forgot to make this a Draft. So I'm open to wait for some further comments. |
|
Hi @Akira25, did had some time to test the changes in your environment? |
|
We have a patch laying around somewhere that sends a signal to a process as soon as there is new information on names. This could remove the regular write operation. |
Sadly not. Help with this is highly appreciated! |
|
Hi @Akira25 , any chance to work further on this issue? |
At Freifunk Berlin we experienced fairly random updates on the files. This
resulted from the calc_jitter() function in the scheduler.c.
By calling the function with a jitter of 0% there shouldn't be any randomness
anymore and the nameservice-files should get written on schedule.
Signed-off-by: Martin Hübner [email protected]
This PR is still under testing for having the desired effect. Thus draft-state for now.