I would like to add a Java agent to ES, but I'm having difficulties
with that.
Where should I add my Java agent params so that they apply to the JVM
in which ES/org.elasticsearch.bootstrap.Bootstrap runs?
This is what I did:
I added the following to bin/service/elasticsearch.conf:
wrapper.java.additional.13=-Dcom.sun.management.jmxremote -
javaagent:/path/to/my-agent.jar
I restarted ES and indeed I saw my JVM params there
I would like to add a Java agent to ES, but I'm having difficulties
with that.
Where should I add my Java agent params so that they apply to the JVM
in which ES/org.elasticsearch.bootstrap.Bootstrap runs?
This is what I did:
I added the following to bin/service/elasticsearch.conf:
wrapper.java.additional.13=-Dcom.sun.management.jmxremote -
javaagent:/path/to/my-agent.jar
I restarted ES and indeed I saw my JVM params there
But my agent doesn't seem to be used.
My suspicion is this is due to that wrapper app that seems to spawn a
separate JVM to run ES in, and when it does that my params are somehow
not passed through.
(I think this is what the poster in
Yea, it might be related to the service wrapper, just use the regular
script to start it (and ES_JAVA_OPTS is preferable, since then it keeps the
regular JAVA_OPTS as well).
I would like to add a Java agent to ES, but I'm having difficulties
with that.
Where should I add my Java agent params so that they apply to the JVM
in which ES/org.elasticsearch.bootstrap.Bootstrap runs?
This is what I did:
I added the following to bin/service/elasticsearch.conf:
wrapper.java.additional.13=-Dcom.sun.management.jmxremote -
javaagent:/path/to/my-agent.jar
I restarted ES and indeed I saw my JVM params there
But my agent doesn't seem to be used.
My suspicion is this is due to that wrapper app that seems to spawn a
separate JVM to run ES in, and when it does that my params are somehow
not passed through.
(I think this is what the poster in
Bringing up this old post since that I can clarify: does the wrapper
ignore JAVA_OPTS and ES_JAVA_OPTS?
Even tried setting set.default.ES_JAVA_OPTS="..." but none of my
changes seem to take effect.
Ivan
On Tue, Jan 10, 2012 at 2:04 PM, Shay Banon kimchy@gmail.com wrote:
Yea, it might be related to the service wrapper, just use the regular script
to start it (and ES_JAVA_OPTS is preferable, since then it keeps the regular
JAVA_OPTS as well).
I would like to add a Java agent to ES, but I'm having difficulties
with that.
Where should I add my Java agent params so that they apply to the JVM
in which ES/org.elasticsearch.bootstrap.Bootstrap runs?
This is what I did:
I added the following to bin/service/elasticsearch.conf:
wrapper.java.additional.13=-Dcom.sun.management.jmxremote -
javaagent:/path/to/my-agent.jar
I restarted ES and indeed I saw my JVM params there
But my agent doesn't seem to be used.
My suspicion is this is due to that wrapper app that seems to spawn a
separate JVM to run ES in, and when it does that my params are somehow
not passed through.
(I think this is what the poster in
The wrapper has its own configuration to provide options to the JVM in its
conf file. It does not respect the env vars.
On Wed, Mar 21, 2012 at 9:03 PM, Ivan Brusic ivan@brusic.com wrote:
Bringing up this old post since that I can clarify: does the wrapper
ignore JAVA_OPTS and ES_JAVA_OPTS?
Even tried setting set.default.ES_JAVA_OPTS="..." but none of my
changes seem to take effect.
Ivan
On Tue, Jan 10, 2012 at 2:04 PM, Shay Banon kimchy@gmail.com wrote:
Yea, it might be related to the service wrapper, just use the regular
script
to start it (and ES_JAVA_OPTS is preferable, since then it keeps the
regular
JAVA_OPTS as well).
I would like to add a Java agent to ES, but I'm having difficulties
with that.
Where should I add my Java agent params so that they apply to the JVM
in which ES/org.elasticsearch.bootstrap.Bootstrap runs?
This is what I did:
I added the following to bin/service/elasticsearch.conf:
wrapper.java.additional.13=-Dcom.sun.management.jmxremote -
javaagent:/path/to/my-agent.jar
I restarted ES and indeed I saw my JVM params there
But my agent doesn't seem to be used.
My suspicion is this is due to that wrapper app that seems to spawn a
separate JVM to run ES in, and when it does that my params are somehow
not passed through.
(I think this is what the poster in
That is what I assumed. Are the vars defined in
bin/service/elasticsearch.conf whitelisted, or will any line prefixed
with set.default.* be "converted" to a variable?
eg.:
If set.default.ES_MIN_MEM sets the ES_MIN_MEM variable, does
set.default.ES_JAVA_OPTS accomplish the same?
It appears that the vars defined on top of the file are only used in
context of that file. Does the wrapper even call bin/elasticsearch? If
env vars are not respected, then probably not.
What is the best way to add an agent using a wrapper?
Cheers,
Ivan
On Thu, Mar 22, 2012 at 11:22 AM, Shay Banon kimchy@gmail.com wrote:
The wrapper has its own configuration to provide options to the JVM in its
conf file. It does not respect the env vars.
On Wed, Mar 21, 2012 at 9:03 PM, Ivan Brusic ivan@brusic.com wrote:
Bringing up this old post since that I can clarify: does the wrapper
ignore JAVA_OPTS and ES_JAVA_OPTS?
Even tried setting set.default.ES_JAVA_OPTS="..." but none of my
changes seem to take effect.
Ivan
On Tue, Jan 10, 2012 at 2:04 PM, Shay Banon kimchy@gmail.com wrote:
Yea, it might be related to the service wrapper, just use the regular
script
to start it (and ES_JAVA_OPTS is preferable, since then it keeps the
regular
JAVA_OPTS as well).
I would like to add a Java agent to ES, but I'm having difficulties
with that.
Where should I add my Java agent params so that they apply to the JVM
in which ES/org.elasticsearch.bootstrap.Bootstrap runs?
This is what I did:
I added the following to bin/service/elasticsearch.conf:
wrapper.java.additional.13=-Dcom.sun.management.jmxremote -
javaagent:/path/to/my-agent.jar
I restarted ES and indeed I saw my JVM params there
But my agent doesn't seem to be used.
My suspicion is this is due to that wrapper app that seems to spawn a
separate JVM to run ES in, and when it does that my params are somehow
not passed through.
(I think this is what the poster in
On Fri, Mar 23, 2012 at 1:03 AM, Ivan Brusic ivan@brusic.com wrote:
That is what I assumed. Are the vars defined in
bin/service/elasticsearch.conf whitelisted, or will any line prefixed
with set.default.* be "converted" to a variable?
eg.:
If set.default.ES_MIN_MEM sets the ES_MIN_MEM variable, does
set.default.ES_JAVA_OPTS accomplish the same?
It appears that the vars defined on top of the file are only used in
context of that file. Does the wrapper even call bin/elasticsearch? If
env vars are not respected, then probably not.
What is the best way to add an agent using a wrapper?
Cheers,
Ivan
On Thu, Mar 22, 2012 at 11:22 AM, Shay Banon kimchy@gmail.com wrote:
The wrapper has its own configuration to provide options to the JVM in
its
conf file. It does not respect the env vars.
On Wed, Mar 21, 2012 at 9:03 PM, Ivan Brusic ivan@brusic.com wrote:
Bringing up this old post since that I can clarify: does the wrapper
ignore JAVA_OPTS and ES_JAVA_OPTS?
Even tried setting set.default.ES_JAVA_OPTS="..." but none of my
changes seem to take effect.
Ivan
On Tue, Jan 10, 2012 at 2:04 PM, Shay Banon kimchy@gmail.com wrote:
Yea, it might be related to the service wrapper, just use the regular
script
to start it (and ES_JAVA_OPTS is preferable, since then it keeps the
regular
JAVA_OPTS as well).
I would like to add a Java agent to ES, but I'm having difficulties
with that.
Where should I add my Java agent params so that they apply to the
JVM
in which ES/org.elasticsearch.bootstrap.Bootstrap runs?
This is what I did:
I added the following to bin/service/elasticsearch.conf:
wrapper.java.additional.13=-Dcom.sun.management.jmxremote -
javaagent:/path/to/my-agent.jar
I restarted ES and indeed I saw my JVM params there
But my agent doesn't seem to be used.
My suspicion is this is due to that wrapper app that seems to spawn
a
separate JVM to run ES in, and when it does that my params are
somehow
not passed through.
(I think this is what the poster in
On Fri, Mar 23, 2012 at 1:03 AM, Ivan Brusic ivan@brusic.com wrote:
That is what I assumed. Are the vars defined in
bin/service/elasticsearch.conf whitelisted, or will any line prefixed
with set.default.* be "converted" to a variable?
eg.:
If set.default.ES_MIN_MEM sets the ES_MIN_MEM variable, does
set.default.ES_JAVA_OPTS accomplish the same?
It appears that the vars defined on top of the file are only used in
context of that file. Does the wrapper even call bin/elasticsearch? If
env vars are not respected, then probably not.
What is the best way to add an agent using a wrapper?
Cheers,
Ivan
On Thu, Mar 22, 2012 at 11:22 AM, Shay Banon kimchy@gmail.com wrote:
The wrapper has its own configuration to provide options to the JVM in
its
conf file. It does not respect the env vars.
On Wed, Mar 21, 2012 at 9:03 PM, Ivan Brusic ivan@brusic.com wrote:
Bringing up this old post since that I can clarify: does the wrapper
ignore JAVA_OPTS and ES_JAVA_OPTS?
Even tried setting set.default.ES_JAVA_OPTS="..." but none of my
changes seem to take effect.
Ivan
On Tue, Jan 10, 2012 at 2:04 PM, Shay Banon kimchy@gmail.com wrote:
Yea, it might be related to the service wrapper, just use the regular
script
to start it (and ES_JAVA_OPTS is preferable, since then it keeps the
regular
JAVA_OPTS as well).
I would like to add a Java agent to ES, but I'm having difficulties
with that.
Where should I add my Java agent params so that they apply to the
JVM
in which ES/org.elasticsearch.bootstrap.Bootstrap runs?
This is what I did:
I added the following to bin/service/elasticsearch.conf:
wrapper.java.additional.13=-Dcom.sun.management.jmxremote -
javaagent:/path/to/my-agent.jar
I restarted ES and indeed I saw my JVM params there
But my agent doesn't seem to be used.
My suspicion is this is due to that wrapper app that seems to spawn
a
separate JVM to run ES in, and when it does that my params are
somehow
not passed through.
(I think this is what the poster in
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.