This leads to issues performing normal operations. A restart puts the memory back to normal levels but I can't figure out what causes it. I have seen before that a memory leak in a previous version caused similar issues but I would have thought that the GC would keep the JVM usage within comfortable limits.
I doubt it since I don't think anything has changed recently in this area. I asked for heap dumps above -- without them, we can't really say what the problem is, and without knowing that we can't really say anything about a fix.
Looks to me like you're using the third-party ReadonlyREST plugin and it's gone haywire, but I can't say much more than that as it's not something we support. I recommend using the official security features instead, they're included by default, they don't cost anything and AFAIK don't suffer from this kind of problem.
Thanks for looking into it. I am keeping an eye on the native security. At the moment, we are making use of IP filtering and LDAP integration, which we would lose if we went to stack native security. Although, if this lasts too long, a loss of convenience outweighs a stable cluster.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.