Hi Everybody! Has anybody had issues with write.lock files on AWS ECS SOLR instances where data is stored on EFS? i.e. if the SOLR ECS task restarts SOLR thinks another process is using the write.lock file to make updates.
But the truth is that the stopped ECS task has not been terminated before the new one starts up automatically Our SOLR ECS tasks use individual solr-data locations on EFS, so they are not sharing data, which makes this problem even more frustrating! I have looked so far at solrconfig.xml changes like the locktype, unlockOnStartup and writeLockTimeout directives, but I'm not sure any of these would help with our scenario. Unfortunately, we are stuck on SOLR 4.10.2, because going to 5 and above means we would have to make code changes to our product that uses SOLR as the dataimport handlers change in version 5. I'm also wondering if this could be an ECS issue, rather than SOLR itself. Perhaps the version of Docker engine we use to build the SOLR images run in ECS (20.10.13) does not play well in ECS land when a task restarts? I have not found yet if it is possible to modify the ECS lifecycle behaviour for a specific ECS cluster Any suggestions or pointers would be greatly appreciated! Cheers, Daz
