In general, how important is it that plugin versions match the
Elasticsearch version? Or are (can) plugins be versioned with no
correlation to Elasticsearch's version at all? Specific case:
I have ES 1.2.2 and phonetic plugin 2.2.1. In good practice, should I be
using ES 2.2.1? Or vice versa; should I use phonetic 1.2.2? so that the
versions match?
I was able to install the plugin on a 3-machine cluster using "plugin --url
file:///home/username/elasticsearch-analysis-phonetic-2.2.1 --install
phonetic-plugin" on all 3 machines (this may not be EXACTLY correct
command, I'm going by memory). On all 3 machines, this created the 'plugins'
directory in my ES home and appeared to properly place the plugin in the
directory. I stopped ES using "service elasticsearch stop". I tried
restarting using "... start" and ES will no longer start. I see errors in
the logs that seem to pertain to plugins. Given this, plus the fact ES
worked fine before the plugin installation, i uninstall the plugin using "plugin
--remove phonetic-plugin". This removed the plugin from the plugins
directory but ES still won't start. The logs still contain plugin-related
errors. Upon looking, I see the plugins directory is still present. I
manually delete the directory, and now ES starts perfectly fine.
My main question is: Should my first course of troubleshooting be obtaining
a 1.2.2 version of the phonetic plugin? Or is something else likely the
culprit?
*Some notes:
This is a disconnected environment with no internet access, so I will
always have to do 'manual' installs.
I currently do not have the exact errors to include here, but I can
hand-write some error details tomorrow when I'm back on the job if you want
more info.
I looked again at the plugin GitHub site and I now see the matrix (below) I
should have seen before posting this. My sincere apologies for not doing
my homework, but I'm still interested in hearing any relevant details that
may have popped into anyone's head while reading this.
In general, how important is it that plugin versions match the
Elasticsearch version? Or are (can) plugins be versioned with no
correlation to Elasticsearch's version at all? Specific case:
I have ES 1.2.2 and phonetic plugin 2.2.1. In good practice, should I be
using ES 2.2.1? Or vice versa; should I use phonetic 1.2.2? so that the
versions match?
I was able to install the plugin on a 3-machine cluster using "plugin
--url file:///home/username/elasticsearch-analysis-phonetic-2.2.1 --install
phonetic-plugin" on all 3 machines (this may not be EXACTLY correct
command, I'm going by memory). On all 3 machines, this created the '
plugins' directory in my ES home and appeared to properly place the
plugin in the directory. I stopped ES using "service elasticsearch stop".
I tried restarting using "... start" and ES will no longer start. I see
errors in the logs that seem to pertain to plugins. Given this, plus the
fact ES worked fine before the plugin installation, i uninstall the plugin
using "plugin --remove phonetic-plugin". This removed the plugin from
the plugins directory but ES still won't start. The logs still contain
plugin-related errors. Upon looking, I see the plugins directory is still
present. I manually delete the directory, and now ES starts perfectly fine.
My main question is: Should my first course of troubleshooting be
obtaining a 1.2.2 version of the phonetic plugin? Or is something else
likely the culprit?
*Some notes:
This is a disconnected environment with no internet access, so I will
always have to do 'manual' installs.
I currently do not have the exact errors to include here, but I can
hand-write some error details tomorrow when I'm back on the job if you want
more info.
Upon second review of the matrix, I realized that I AM in fact pairing a
supported version pair of ES 1.2.2 and phonetic 2.2.1. So although my
version-matching questions are answered, I'm still stuck with why ES won't
start after plugin install. I'm guessing that will require more details
from the log...
On Wednesday, April 1, 2015 at 5:20:42 PM UTC-4, Mark Bramer wrote:
I looked again at the plugin GitHub site and I now see the matrix (below)
I should have seen before posting this. My sincere apologies for not doing
my homework, but I'm still interested in hearing any relevant details that
may have popped into anyone's head while reading this.
In general, how important is it that plugin versions match the
Elasticsearch version? Or are (can) plugins be versioned with no
correlation to Elasticsearch's version at all? Specific case:
I have ES 1.2.2 and phonetic plugin 2.2.1. In good practice, should I be
using ES 2.2.1? Or vice versa; should I use phonetic 1.2.2? so that the
versions match?
I was able to install the plugin on a 3-machine cluster using "plugin
--url file:///home/username/elasticsearch-analysis-phonetic-2.2.1 --install
phonetic-plugin" on all 3 machines (this may not be EXACTLY correct
command, I'm going by memory). On all 3 machines, this created the '
plugins' directory in my ES home and appeared to properly place the
plugin in the directory. I stopped ES using "service elasticsearch stop".
I tried restarting using "... start" and ES will no longer start. I
see errors in the logs that seem to pertain to plugins. Given this, plus
the fact ES worked fine before the plugin installation, i uninstall the
plugin using "plugin --remove phonetic-plugin". This removed the plugin
from the plugins directory but ES still won't start. The logs still contain
plugin-related errors. Upon looking, I see the plugins directory is still
present. I manually delete the directory, and now ES starts perfectly fine.
My main question is: Should my first course of troubleshooting be
obtaining a 1.2.2 version of the phonetic plugin? Or is something else
likely the culprit?
*Some notes:
This is a disconnected environment with no internet access, so I will
always have to do 'manual' installs.
I currently do not have the exact errors to include here, but I can
hand-write some error details tomorrow when I'm back on the job if you want
more info.
Upon second review of the matrix, I realized that I AM in fact pairing a supported version pair of ES 1.2.2 and phonetic 2.2.1. So although my version-matching questions are answered, I'm still stuck with why ES won't start after plugin install. I'm guessing that will require more details from the log...
On Wednesday, April 1, 2015 at 5:20:42 PM UTC-4, Mark Bramer wrote:
I looked again at the plugin GitHub site and I now see the matrix (below) I should have seen before posting this. My sincere apologies for not doing my homework, but I'm still interested in hearing any relevant details that may have popped into anyone's head while reading this.
On Wednesday, April 1, 2015 at 5:17:42 PM UTC-4, Mark Bramer wrote:
Hello,
In general, how important is it that plugin versions match the Elasticsearch version? Or are (can) plugins be versioned with no correlation to Elasticsearch's version at all? Specific case:
I have ES 1.2.2 and phonetic plugin 2.2.1. In good practice, should I be using ES 2.2.1? Or vice versa; should I use phonetic 1.2.2? so that the versions match?
I was able to install the plugin on a 3-machine cluster using "plugin --url file:///home/username/elasticsearch-analysis-phonetic-2.2.1 --install phonetic-plugin" on all 3 machines (this may not be EXACTLY correct command, I'm going by memory). On all 3 machines, this created the 'plugins' directory in my ES home and appeared to properly place the plugin in the directory. I stopped ES using "service elasticsearch stop". I tried restarting using "... start" and ES will no longer start. I see errors in the logs that seem to pertain to plugins. Given this, plus the fact ES worked fine before the plugin installation, i uninstall the plugin using "plugin --remove phonetic-plugin". This removed the plugin from the plugins directory but ES still won't start. The logs still contain plugin-related errors. Upon looking, I see the plugins directory is still present. I manually delete the directory, and now ES starts perfectly fine.
My main question is: Should my first course of troubleshooting be obtaining a 1.2.2 version of the phonetic plugin? Or is something else likely the culprit?
*Some notes:
This is a disconnected environment with no internet access, so I will always have to do 'manual' installs.
I currently do not have the exact errors to include here, but I can hand-write some error details tomorrow when I'm back on the job if you want more info.
I inherited this from someone else (how many times have we all heard
that??) who named the file I'm using - perhaps he made some changes and
rebuilt...? Either way, I'm using ES 1.2 and phonetic 2.1 which according
to the matrix, should work...
On Wednesday, April 1, 2015 at 5:28:22 PM UTC-4, David Pilato wrote:
Is there a version 2.2.1?
--
David
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
Le 1 avr. 2015 à 23:24, Mark Bramer <mark....@gmail.com <javascript:>> a
écrit :
Upon second review of the matrix, I realized that I AM in fact pairing a
supported version pair of ES 1.2.2 and phonetic 2.2.1. So although my
version-matching questions are answered, I'm still stuck with why ES won't
start after plugin install. I'm guessing that will require more details
from the log...
On Wednesday, April 1, 2015 at 5:20:42 PM UTC-4, Mark Bramer wrote:
I looked again at the plugin GitHub site and I now see the matrix (below)
I should have seen before posting this. My sincere apologies for not doing
my homework, but I'm still interested in hearing any relevant details that
may have popped into anyone's head while reading this.
In general, how important is it that plugin versions match the
Elasticsearch version? Or are (can) plugins be versioned with no
correlation to Elasticsearch's version at all? Specific case:
I have ES 1.2.2 and phonetic plugin 2.2.1. In good practice, should I
be using ES 2.2.1? Or vice versa; should I use phonetic 1.2.2? so that
the versions match?
I was able to install the plugin on a 3-machine cluster using "plugin
--url file:///home/username/elasticsearch-analysis-phonetic-2.2.1 --install
phonetic-plugin" on all 3 machines (this may not be EXACTLY correct
command, I'm going by memory). On all 3 machines, this created the '
plugins' directory in my ES home and appeared to properly place the
plugin in the directory. I stopped ES using "service elasticsearch stop".
I tried restarting using "... start" and ES will no longer start. I
see errors in the logs that seem to pertain to plugins. Given this, plus
the fact ES worked fine before the plugin installation, i uninstall the
plugin using "plugin --remove phonetic-plugin". This removed the
plugin from the plugins directory but ES still won't start. The logs still
contain plugin-related errors. Upon looking, I see the plugins directory
is still present. I manually delete the directory, and now ES starts
perfectly fine.
My main question is: Should my first course of troubleshooting be
obtaining a 1.2.2 version of the phonetic plugin? Or is something else
likely the culprit?
*Some notes:
This is a disconnected environment with no internet access, so I will
always have to do 'manual' installs.
I currently do not have the exact errors to include here, but I can
hand-write some error details tomorrow when I'm back on the job if you want
more info.
There's a 2.2.1 snapshot. I don't believe the one I'm using was modified
from this one.
On Wednesday, April 1, 2015 at 5:32:40 PM UTC-4, Mark Bramer wrote:
I inherited this from someone else (how many times have we all heard
that??) who named the file I'm using - perhaps he made some changes and
rebuilt...? Either way, I'm using ES 1.2 and phonetic 2.1 which according
to the matrix, should work...
On Wednesday, April 1, 2015 at 5:28:22 PM UTC-4, David Pilato wrote:
Is there a version 2.2.1?
--
David
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
Upon second review of the matrix, I realized that I AM in fact pairing a
supported version pair of ES 1.2.2 and phonetic 2.2.1. So although my
version-matching questions are answered, I'm still stuck with why ES won't
start after plugin install. I'm guessing that will require more details
from the log...
On Wednesday, April 1, 2015 at 5:20:42 PM UTC-4, Mark Bramer wrote:
I looked again at the plugin GitHub site and I now see the matrix
(below) I should have seen before posting this. My sincere apologies for
not doing my homework, but I'm still interested in hearing any relevant
details that may have popped into anyone's head while reading this.
In general, how important is it that plugin versions match the
Elasticsearch version? Or are (can) plugins be versioned with no
correlation to Elasticsearch's version at all? Specific case:
I have ES 1.2.2 and phonetic plugin 2.2.1. In good practice, should I
be using ES 2.2.1? Or vice versa; should I use phonetic 1.2.2? so that
the versions match?
I was able to install the plugin on a 3-machine cluster using "plugin
--url file:///home/username/elasticsearch-analysis-phonetic-2.2.1 --install
phonetic-plugin" on all 3 machines (this may not be EXACTLY correct
command, I'm going by memory). On all 3 machines, this created the '
plugins' directory in my ES home and appeared to properly place the
plugin in the directory. I stopped ES using "service elasticsearch stop".
I tried restarting using "... start" and ES will no longer start. I
see errors in the logs that seem to pertain to plugins. Given this, plus
the fact ES worked fine before the plugin installation, i uninstall the
plugin using "plugin --remove phonetic-plugin". This removed the
plugin from the plugins directory but ES still won't start. The logs still
contain plugin-related errors. Upon looking, I see the plugins directory
is still present. I manually delete the directory, and now ES starts
perfectly fine.
My main question is: Should my first course of troubleshooting be
obtaining a 1.2.2 version of the phonetic plugin? Or is something else
likely the culprit?
*Some notes:
This is a disconnected environment with no internet access, so I
will always have to do 'manual' installs.
I currently do not have the exact errors to include here, but I can
hand-write some error details tomorrow when I'm back on the job if you want
more info.
There's a 2.2.1 snapshot. I don't believe the one I'm using was modified from this one.
On Wednesday, April 1, 2015 at 5:32:40 PM UTC-4, Mark Bramer wrote:
I inherited this from someone else (how many times have we all heard that??) who named the file I'm using - perhaps he made some changes and rebuilt...? Either way, I'm using ES 1.2 and phonetic 2.1 which according to the matrix, should work...
On Wednesday, April 1, 2015 at 5:28:22 PM UTC-4, David Pilato wrote:
Is there a version 2.2.1?
--
David
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
Upon second review of the matrix, I realized that I AM in fact pairing a supported version pair of ES 1.2.2 and phonetic 2.2.1. So although my version-matching questions are answered, I'm still stuck with why ES won't start after plugin install. I'm guessing that will require more details from the log...
On Wednesday, April 1, 2015 at 5:20:42 PM UTC-4, Mark Bramer wrote:
I looked again at the plugin GitHub site and I now see the matrix (below) I should have seen before posting this. My sincere apologies for not doing my homework, but I'm still interested in hearing any relevant details that may have popped into anyone's head while reading this.
On Wednesday, April 1, 2015 at 5:17:42 PM UTC-4, Mark Bramer wrote:
Hello,
In general, how important is it that plugin versions match the Elasticsearch version? Or are (can) plugins be versioned with no correlation to Elasticsearch's version at all? Specific case:
I have ES 1.2.2 and phonetic plugin 2.2.1. In good practice, should I be using ES 2.2.1? Or vice versa; should I use phonetic 1.2.2? so that the versions match?
I was able to install the plugin on a 3-machine cluster using "plugin --url file:///home/username/elasticsearch-analysis-phonetic-2.2.1 --install phonetic-plugin" on all 3 machines (this may not be EXACTLY correct command, I'm going by memory). On all 3 machines, this created the 'plugins' directory in my ES home and appeared to properly place the plugin in the directory. I stopped ES using "service elasticsearch stop". I tried restarting using "... start" and ES will no longer start. I see errors in the logs that seem to pertain to plugins. Given this, plus the fact ES worked fine before the plugin installation, i uninstall the plugin using "plugin --remove phonetic-plugin". This removed the plugin from the plugins directory but ES still won't start. The logs still contain plugin-related errors. Upon looking, I see the plugins directory is still present. I manually delete the directory, and now ES starts perfectly fine.
My main question is: Should my first course of troubleshooting be obtaining a 1.2.2 version of the phonetic plugin? Or is something else likely the culprit?
*Some notes:
This is a disconnected environment with no internet access, so I will always have to do 'manual' installs.
I currently do not have the exact errors to include here, but I can hand-write some error details tomorrow when I'm back on the job if you want more info.
On Wednesday, April 1, 2015 at 5:55:48 PM UTC-4, David Pilato wrote:
Sorry. I don't follow. You are not using official plugin version 2.2.0 but
a modified version?
David
Le 1 avr. 2015 à 23:42, Mark Bramer <mark....@gmail.com <javascript:>> a
écrit :
There's a 2.2.1 snapshot. I don't believe the one I'm using was modified
from this one.
On Wednesday, April 1, 2015 at 5:32:40 PM UTC-4, Mark Bramer wrote:
I inherited this from someone else (how many times have we all heard
that??) who named the file I'm using - perhaps he made some changes and
rebuilt...? Either way, I'm using ES 1.2 and phonetic 2.1 which according
to the matrix, should work...
On Wednesday, April 1, 2015 at 5:28:22 PM UTC-4, David Pilato wrote:
Is there a version 2.2.1?
--
David
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
Upon second review of the matrix, I realized that I AM in fact pairing a
supported version pair of ES 1.2.2 and phonetic 2.2.1. So although my
version-matching questions are answered, I'm still stuck with why ES won't
start after plugin install. I'm guessing that will require more details
from the log...
On Wednesday, April 1, 2015 at 5:20:42 PM UTC-4, Mark Bramer wrote:
I looked again at the plugin GitHub site and I now see the matrix
(below) I should have seen before posting this. My sincere apologies for
not doing my homework, but I'm still interested in hearing any relevant
details that may have popped into anyone's head while reading this.
In general, how important is it that plugin versions match the
Elasticsearch version? Or are (can) plugins be versioned with no
correlation to Elasticsearch's version at all? Specific case:
I have ES 1.2.2 and phonetic plugin 2.2.1. In good practice, should I
be using ES 2.2.1? Or vice versa; should I use phonetic 1.2.2? so that
the versions match?
I was able to install the plugin on a 3-machine cluster using "plugin
--url file:///home/username/elasticsearch-analysis-phonetic-2.2.1 --install
phonetic-plugin" on all 3 machines (this may not be EXACTLY correct
command, I'm going by memory). On all 3 machines, this created the '
plugins' directory in my ES home and appeared to properly place the
plugin in the directory. I stopped ES using "service elasticsearch
stop". I tried restarting using "... start" and ES will no longer
start. I see errors in the logs that seem to pertain to plugins. Given
this, plus the fact ES worked fine before the plugin installation, i
uninstall the plugin using "plugin --remove phonetic-plugin". This
removed the plugin from the plugins directory but ES still won't start. The
logs still contain plugin-related errors. Upon looking, I see the plugins
directory is still present. I manually delete the directory, and now ES
starts perfectly fine.
My main question is: Should my first course of troubleshooting be
obtaining a 1.2.2 version of the phonetic plugin? Or is something else
likely the culprit?
*Some notes:
This is a disconnected environment with no internet access, so I
will always have to do 'manual' installs.
I currently do not have the exact errors to include here, but I can
hand-write some error details tomorrow when I'm back on the job if you want
more info.
On Wednesday, April 1, 2015 at 5:55:48 PM UTC-4, David Pilato wrote:
Sorry. I don't follow. You are not using official plugin version 2.2.0 but a modified version?
There's a 2.2.1 snapshot. I don't believe the one I'm using was modified from this one.
On Wednesday, April 1, 2015 at 5:32:40 PM UTC-4, Mark Bramer wrote:
I inherited this from someone else (how many times have we all heard that??) who named the file I'm using - perhaps he made some changes and rebuilt...? Either way, I'm using ES 1.2 and phonetic 2.1 which according to the matrix, should work...
On Wednesday, April 1, 2015 at 5:28:22 PM UTC-4, David Pilato wrote:
Is there a version 2.2.1?
--
David
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
Upon second review of the matrix, I realized that I AM in fact pairing a supported version pair of ES 1.2.2 and phonetic 2.2.1. So although my version-matching questions are answered, I'm still stuck with why ES won't start after plugin install. I'm guessing that will require more details from the log...
On Wednesday, April 1, 2015 at 5:20:42 PM UTC-4, Mark Bramer wrote:
I looked again at the plugin GitHub site and I now see the matrix (below) I should have seen before posting this. My sincere apologies for not doing my homework, but I'm still interested in hearing any relevant details that may have popped into anyone's head while reading this.
On Wednesday, April 1, 2015 at 5:17:42 PM UTC-4, Mark Bramer wrote:
Hello,
In general, how important is it that plugin versions match the Elasticsearch version? Or are (can) plugins be versioned with no correlation to Elasticsearch's version at all? Specific case:
I have ES 1.2.2 and phonetic plugin 2.2.1. In good practice, should I be using ES 2.2.1? Or vice versa; should I use phonetic 1.2.2? so that the versions match?
I was able to install the plugin on a 3-machine cluster using "plugin --url file:///home/username/elasticsearch-analysis-phonetic-2.2.1 --install phonetic-plugin" on all 3 machines (this may not be EXACTLY correct command, I'm going by memory). On all 3 machines, this created the 'plugins' directory in my ES home and appeared to properly place the plugin in the directory. I stopped ES using "service elasticsearch stop". I tried restarting using "... start" and ES will no longer start. I see errors in the logs that seem to pertain to plugins. Given this, plus the fact ES worked fine before the plugin installation, i uninstall the plugin using "plugin --remove phonetic-plugin". This removed the plugin from the plugins directory but ES still won't start. The logs still contain plugin-related errors. Upon looking, I see the plugins directory is still present. I manually delete the directory, and now ES starts perfectly fine.
My main question is: Should my first course of troubleshooting be obtaining a 1.2.2 version of the phonetic plugin? Or is something else likely the culprit?
*Some notes:
This is a disconnected environment with no internet access, so I will always have to do 'manual' installs.
I currently do not have the exact errors to include here, but I can hand-write some error details tomorrow when I'm back on the job if you want more info.
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.
