Issue:
For a Cloudera Manager-managed Streamsets Data Collector instance, when accessing the configuration page for SDC via the CM UI, the configurations available are outdated, which may result in configurations from older SDC versions showing up and up-to-date configurations missing.
Solution:
If you notice the symptoms described above, it is likely that the custom service descriptor (CSD) is out-of-date for the SDC service in CM. This can happen if the SDC parcel is upgraded to a new version, but the manual CSD installation step is not done, resulting in an outdated active CSD.
The CSD jar contains a 'descriptor/service.sdl' file, which contains custom service definitions, including the configurations that are exposed in the CM UI.
You can check the CSD applied by taking a look at the local descriptor repository path on the Cloudera manager node, and looking for the StreamSets CSD file (STREAMSETS-<version>.jar). The local descriptor repository path by default is '/opt/cloudera/csd'. To check what path is used by your CDH cluster, check the following property in CM:
Administration -> Settings -> Category: Custom Service Descriptors -> Local Descriptor Repository Path
If the CSD file that you find is of an older SDC version than that of the instance currently running, please upgrade the CSD to make sure the most up-to-date configs are reflected in the configurations page. This is part of the SDC upgrade step, and installation steps are listed here.
