You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're working on deploying Elasticsearch in an arm environment and have noticed that the armhf version of openjdk-7 is not included in the JDK-DIRS for the Elasticsearch service.
Now while Java should theoretically set its Java_Home, doing the default apt-get install openjdk-7-jre does not do this (on X86 or ARM) which is why I'm assuming the JDK_DIRs list was created.
The path would be /usr/lib/jvm/java-7-openjdk-armhf/ and /usr/lib/jvm/java-6-openjdk-armhf/
The text was updated successfully, but these errors were encountered:
Yep the debian init script. I can get a pull request in in the morning with the two added dirs.
Besides the init script, we've had no problems using elasticsearch on arm, everything seems to work, we just install the debian, update the service with the right java path and presto. We've also been using head and the phonetic analysis plugin and those also work.
matthewarkin
added a commit
to matthewarkin/elasticsearch
that referenced
this issue
Sep 13, 2013
We're working on deploying Elasticsearch in an arm environment and have noticed that the armhf version of openjdk-7 is not included in the JDK-DIRS for the Elasticsearch service.
Now while Java should theoretically set its Java_Home, doing the default apt-get install openjdk-7-jre does not do this (on X86 or ARM) which is why I'm assuming the JDK_DIRs list was created.
The path would be /usr/lib/jvm/java-7-openjdk-armhf/ and /usr/lib/jvm/java-6-openjdk-armhf/
The text was updated successfully, but these errors were encountered: