We are running 90.11 version on a cluster with master, data and client
nodes.
Our master and data nodes are on Linux. But client boxes are running on
Windows 64 but boxes as we have .Net applications.
In past we had allocated ES_HEAP_SIZE as 2g to client boxes and we had
issues of service was getting hanged.
Then we tried 4g and now to 10g. We are still facing issues, even when
service is running fine it shows more than 10g being occupied by service
wrapper.
Bigdesk show 9.9 gb committed and 2 gb used but windows process shows it as
11g.
What is the issue? Does this has to do with ES service wrapper ?
We are running 90.11 version on a cluster with master, data and client
nodes.
Our master and data nodes are on Linux. But client boxes are running on
Windows 64 but boxes as we have .Net applications.
In past we had allocated ES_HEAP_SIZE as 2g to client boxes and we had
issues of service was getting hanged.
Then we tried 4g and now to 10g. We are still facing issues, even when
service is running fine it shows more than 10g being occupied by service
wrapper.
Bigdesk show 9.9 gb committed and 2 gb used but windows process shows it
as 11g.
What is the issue? Does this has to do with ES service wrapper ?
We are running 90.11 version on a cluster with master, data and client
nodes.
Our master and data nodes are on Linux. But client boxes are running on
Windows 64 but boxes as we have .Net applications.
In past we had allocated ES_HEAP_SIZE as 2g to client boxes and we had
issues of service was getting hanged.
Then we tried 4g and now to 10g. We are still facing issues, even when
service is running fine it shows more than 10g being occupied by service
wrapper.
Bigdesk show 9.9 gb committed and 2 gb used but windows process shows it
as 11g.
What is the issue? Does this has to do with ES service wrapper ?
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.