Hi Hermant, configoverlay.json is not a file with content provided by Solr out of the box. Instead, it's used to hold any changes you make to Solr's default configuration using the config API (/config). More details at the top of the article here: https://lucene.apache.org/solr/guide/6_6/config-api.html
So the fact that you see this in your configoverlay.json means that someone with access to your Solr cluster specifically used the API to request that RunExecutableListener configuration. (This is true of everything in configoverlay.json). Another possibility is that these settings were requested via the API on a different cluster you had, and then copied over to your new cluster by whoever set it up. This latter possibility could explain why your RunExecutableListener config seems to be setup to run Linux commands, even though it runs on Windows. If you want you can delete configoverlay.json, or create a new collection without it. But since these configuration options were chosen by a cluster admin on your end at some point (and aren't Solr "defaults"), then your real first concern should be auditing what's in configoverlay.json and seeing what still makes sense for use in your cluster. Hope that helps, Jason On Fri, Feb 15, 2019 at 2:05 PM Hemant Verma <hemantverm...@gmail.com> wrote: > > Thanks Jan > We are using Solr 6.6.3 version. > We didn't configure RunExecutableListener in solrconfig.xml, it seems > configured in configoverlay.json as default. Even we don't want to configure > RunExecutableListener. > > Is it mandatory to use configoverlay.json or can we get rid of it? If yes > can you share details. > > Attached the solrconfig.xml > > solrconfig.xml > <http://lucene.472066.n3.nabble.com/file/t86258/solrconfig.xml> > > > > -- > Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
