New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
modify a namemapping implies a cygnus restart? #2121
Comments
maybe related with permissions file: https://forums.docker.com/t/modify-a-file-which-mount-as-a-data-volume-but-it-didnt-change-in-container/2813 |
NM doc: NM are read each 30 seconds: Lines 72 to 73 in 624329a
Lines 180 to 234 in 624329a
|
Cygnus is able to read a namemmapping file modified without restart in a docker: time=2022-02-07T14:34:28.988Z | lvl=DEBUG | corr=N/A | trans=N/A | srv=N/A | subsrv=N/A | comp=cygnus-ngsi | op=loadNameMappings | msg=com.telefonica.iot.cygnus.interceptors.NGSINameMappingsInterceptor[242] : [nmi] Reading name mappings, Json read: { "serviceMappings": [ { "originalService": "smartcity", "newService": "smartcityXXXXX", "servicePathMappings": [ { "originalServicePath": "", "newServicePath": "", "entityMappings": [ { "originalEntityId": "", "originalEntityType": "", "newEntityId": "", "newEntityType": "", "attributeMappings": [ { "originalAttributeName": "", "originalAttributeType": "", "newAttributeName": "", "newAttributeType": "" } ] } ] } ] } ]} ls -la name_mappings_mysql.conf |
Given a cygnus configured with a NM in a volume like: After change NM file ${PATH_CYGNUS_CONF}/name_mappings_mysql.conf from
to
No restart iot-cygnus container is needed, cygnus reads NM each 30 seconds and after then applies the new NM. |
But the importat detail is modify NM file (or any cygnus config file) without changing i-node (i.e. vim editor does it: moby/moby#15793 (comment)) |
Some questions to clarify:
The text was updated successfully, but these errors were encountered: