I'm very interested in Solr Docker images...
Is this the "official" thing? I see it's supported by Lucidworks...
On Thu, Sep 15, 2016 at 1:27 AM, Georg Sorst <georg.so...@gmail.com> wrote:
> If you are using the Solr's Docker images this is even easier:
>
> FROM solr:6.0.0
>
> USER $SOLR_USER
>
> # Expose JMX port
> EXPOSE 1${SOLR_UID}
>
> # Enable JMX
> RUN sed -i -e
> 's/^ENABLE_REMOTE_JMX_OPTS=.*$/ENABLE_REMOTE_JMX_OPTS="true"/' bin/
> solr.in.sh
> RUN sed -i -e 's/^SOLR_JETTY_CONFIG=()$/SOLR_JETTY_CONFIG=("etc\/
> jetty.xml"
> "etc\/jetty-jmx.xml")/' bin/solr
>
> Rallavagu <rallav...@gmail.com> schrieb am Mo., 12. Sep. 2016 um 23:56
> Uhr:
>
> > I have modified modules/http.mod as following (for solr 5.4.1, Jetty 9).
> > As you can see I have referred jetty-jmx.xml.
> >
> > #
> > # Jetty HTTP Connector
> > #
> >
> > [depend]
> > server
> >
> > [xml]
> > etc/jetty-http.xml
> > etc/jetty-jmx.xml
> >
> >
> >
> > On 5/21/16 3:59 AM, Georg Sorst wrote:
> > > Hi list,
> > >
> > > how do I correctly enable JMX in Solr 6 so that I can monitor Jetty's
> > > thread pool?
> > >
> > > The first step is to set ENABLE_REMOTE_JMX_OPTS="true" in bin/
> solr.in.sh
> > .
> > > This will give me JMX access to JVM properties (garbage collection,
> class
> > > loading etc.) and works fine. However, this will not give me any Jetty
> > > specific properties.
> > >
> > > I've tried manually adding jetty-jmx.xml from the jetty 9 distribution
> to
> > > server/etc/ and then starting Solr with 'java ... start.jar
> > > etc/jetty-jmx.xml'. This works fine and gives me access to the right
> > > properties, but seems wrong. I could similarly copy the contents of
> > > jetty-jmx.xml into jetty.xml but this is not much better either.
> > >
> > > Is there a correct way for this?
> > >
> > > Thanks!
> > > Georg
> > >
> >
>
