Eamon Ford created SDAP-259:
-------------------------------
Summary: Collection Manager does not pick up Collections Config
file updates with K8s
Key: SDAP-259
URL: https://issues.apache.org/jira/browse/SDAP-259
Project: Apache Science Data Analytics Platform
Issue Type: Bug
Components: collection-ingester
Reporter: Eamon Ford
Assignee: Eamon Ford
When the Collection Manager is deployed in kubernetes, the Collections Config
exists as a k8s configmap which gets mounted in the Collection Manager as a
file in a volume. However, when the configmap gets updated (by the Config
Operator), the file mounted in the Collection Manager does not produce the
expected "modified" Linux filesystem event, which the Collection Manager relies
on. Instead, it produces a sequence of "created", "moved", "deleted" filesystem
events which are a result of the way Kubernetes updates mounted configmaps.
Since the Collection Manager should be agnostic to whether or not it's running
inside Kubernetes, we should not change it to look for this Kubernetes-specific
sequence of filesystem events as that would break the functionality when
running outside of Kubernetes. Instead, the class that watches the Collections
Config file for updates should be changed to just reload the file on a regular
interval.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
