You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@solr.apache.org by gi...@apache.org on 2022/10/21 23:10:47 UTC
[solr-site] branch asf-site updated: Automatic Site Publish by Buildbot
This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/solr-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 5ad37fd6b Automatic Site Publish by Buildbot
5ad37fd6b is described below
commit 5ad37fd6b855a6f33f779e0c1ba8612076d65bac
Author: buildbot <us...@infra.apache.org>
AuthorDate: Fri Oct 21 23:10:44 2022 +0000
Automatic Site Publish by Buildbot
---
output/feeds/all.atom.xml | 36 +++++++++++++++++++++++++++++++++-
output/feeds/solr/news.atom.xml | 36 +++++++++++++++++++++++++++++++++-
output/index.html | 6 +++---
output/news.html | 43 +++++++++++++++++++++++++++++++++++++++++
4 files changed, 116 insertions(+), 5 deletions(-)
diff --git a/output/feeds/all.atom.xml b/output/feeds/all.atom.xml
index 78400e6d4..6183582ab 100644
--- a/output/feeds/all.atom.xml
+++ b/output/feeds/all.atom.xml
@@ -1,5 +1,39 @@
<?xml version="1.0" encoding="utf-8"?>
-<feed xmlns="http://www.w3.org/2005/Atom"><title>Apache Solr</title><link href="/" rel="alternate"></link><link href="/feeds/all.atom.xml" rel="self"></link><id>/</id><updated>2022-08-14T00:00:00+00:00</updated><subtitle></subtitle><subtitle></subtitle><entry><title>Apache Solr Operator™ v0.6.0 available</title><link href="/apache-solr-operatortm-v060-available.html" rel="alternate"></link><published>2022-08-14T00:00:00+00:00</published><updated>2022-08-14T00:00:00+00:00</updated><author [...]
+<feed xmlns="http://www.w3.org/2005/Atom"><title>Apache Solr</title><link href="/" rel="alternate"></link><link href="/feeds/all.atom.xml" rel="self"></link><id>/</id><updated>2022-10-21T00:00:00+00:00</updated><subtitle></subtitle><subtitle></subtitle><entry><title>Java 17 bug affecting Solr</title><link href="/java-17-bug-affecting-solr.html" rel="alternate"></link><published>2022-10-21T00:00:00+00:00</published><updated>2022-10-21T00:00:00+00:00</updated><author><name>Solr Developers< [...]
+<p>Known mitigations are to either downgrade to JDK 11 or to start Solr with a Java startup flag that avoids the failure …</p></summary><content type="html"><p>Several users running Solr in production on OpenJDK 17 have experienced JVM crashes due to a known bug in the JDK. Read more about the bug in <a href="https://issues.apache.org/jira/browse/SOLR-16463">SOLR-16463</a>.</p>
+<p>Known mitigations are to either downgrade to JDK 11 or to start Solr with a Java startup flag that avoids the failure condition. Here is how to manually apply the flag:</p>
+<p>Edit your <code>solr.in.sh</code> or <code>solr.in.cmd</code> file to set the <code>SOLR_OPTS</code> environment variable as follows:</p>
+<p><em>Linux:</em> </p>
+<div class="codehilite"><pre><span></span><code><span class="nv">SOLR_OPTS</span><span class="o">=</span>-XX:CompileCommand<span class="o">=</span>exclude,com.github.benmanes.caffeine.cache.BoundedLocalCache::put
+</code></pre></div>
+
+<p><em>Windows:</em></p>
+<div class="codehilite"><pre><span></span><code>SET <span class="nv">SOLR_OPTS</span><span class="o">=</span>-XX:CompileCommand<span class="o">=</span>exclude,com.github.benmanes.caffeine.cache.BoundedLocalCache::put
+</code></pre></div>
+
+<p>Alternatively, you can inject the same flag with the <code>-a</code> argument, e.g:</p>
+<div class="codehilite"><pre><span></span><code>bin/solr -a <span class="s2">&quot;-XX:CompileCommand=exclude,com.github.benmanes.caffeine.cache.BoundedLocalCache::put&quot;</span>
+</code></pre></div>
+
+<p>If you run Solr 9 with the official Docker image, we have already pushed an updated Docker image to Docker Hub that will inject the flag for you.
+Just pull the image again to get it.
+The Docker image uses the <code>-a</code> option to set this java flag when running Solr, so if you are using the
+<code>-a</code> option you will need to provide the JVM flag mentioned above in addition to the other flags you are setting.</p></content><category term="solr/news"></category></entry><entry><title>Solr 8 Docker image changes to Eclipse Temurin JDK</title><link href="/solr-8-docker-image-changes-to-eclipse-temurin-jdk.html" rel="alternate"></link><published>2022-10-20T00:00:00+00:00</published><updated>2022-10-20T00:00:00+00:00</updated><author><name>Solr Developers</na [...]
+<p>Users should be aware that on your next <code>docker pull solr:8.11.2</code> you will be upgraded. For most users there will be no issues, as it is mainly a new distribution of the same upstream OpenJDK version. However, if you use our image as base image and rely on specific tools to be present, you may need to adapt. While <code>openjdk:11-jre</code> uses <code>Debian GNU/Linux 11 (bullseye)</code>, the <code>eclipse-temurin:11-jre-foc [...]
+<p>Furthermore, there is now no difference between the <code>solr:11-jre</code> and <code>solr:11-jre-slim</code> images, because our new vendor only offers one variant which is fairly slim already.</p></content><category term="solr/news"></category></entry><entry><title>Solr Docker images now pin the Linux release</title><link href="/solr-docker-images-now-pin-the-linux-release.html" rel="alternate"></link><published>2022-10-20T00:00:00+00:00</publish [...]
+Docker image will thus always use an updated Java 17 version. If you pull the docker image from time to time that is.</p>
+<p>However, the base image tag …</p></summary><content type="html"><p>Solr 9 was released on May 12th, using the <code>eclipse-temurin:17-jre</code> base image. Thus, we are pinned to Java 17 and Solr's
+Docker image will thus always use an updated Java 17 version. If you pull the docker image from time to time that is.</p>
+<p>However, the base image tag <code>17-jre</code> did not give us pinning to a specific Ubuntu Linux major release.
+At the time of <a href="http://localhost:8000/news.html#apache-solrtm-900-available">Solr 9 release</a> on May 12th
+it would pull Ubuntu 20.04 (Focal Fossa), but at the end of May, it was <a href="https://github.com/docker-library/official-images/commit/6d689db4846a3eb4c2ebd0e5d06139c650ef3bbb">auto upgraded</a> to the brand new Ubuntu
+22.04 (Jammy Jellyfish). This was not our desire, and we have learnt that due to this, our image is no longer compatible
+with Docker client versions before 20.10.16. Having a "floating" linux release like this can also break the image in
+other subtle ways, as well as breaking downstream images using us as a base image.</p>
+<p>We therefore decided to start pinning not only Java release, but also Linux release in our official Docker images.
+This means that Solr 9.0 is once again based on Ubuntu 20.04 Focal, i.e. a downgrade.</p>
+<p>Note that our images will still receive important Linux bug fixes from time to time, but you won't get them unless you
+re-pull the image. When we upgrade to Ubuntu 22.04 in the future, it will be a deliberate decision and not by accident.</p></content><category term="solr/news"></category></entry><entry><title>Apache Solr Operator™ v0.6.0 available</title><link href="/apache-solr-operatortm-v060-available.html" rel="alternate"></link><published>2022-08-14T00:00:00+00:00</published><updated>2022-08-14T00:00:00+00:00</updated><author><name>Solr Developers</name></author><id>tag:None,2022-08-14:/apach [...]
<p>The Apache Solr Operator is a safe and easy way of managing a Solr ecosystem in Kubernetes.</p>
<p>This release contains numerous bug fixes, optimizations, and improvements, some of which are highlighted below …</p></summary><content type="html"><p>The Apache Solr PMC is pleased to announce the release of the Apache Solr Operator v0.6.0.</p>
<p>The Apache Solr Operator is a safe and easy way of managing a Solr ecosystem in Kubernetes.</p>
diff --git a/output/feeds/solr/news.atom.xml b/output/feeds/solr/news.atom.xml
index 67833c60e..9afae14ff 100644
--- a/output/feeds/solr/news.atom.xml
+++ b/output/feeds/solr/news.atom.xml
@@ -1,5 +1,39 @@
<?xml version="1.0" encoding="utf-8"?>
-<feed xmlns="http://www.w3.org/2005/Atom"><title>Apache Solr - solr/news</title><link href="/" rel="alternate"></link><link href="/feeds/solr/news.atom.xml" rel="self"></link><id>/</id><updated>2022-06-17T00:00:00+00:00</updated><subtitle></subtitle><subtitle></subtitle><entry><title>Apache Solr™ 8.11.2 available</title><link href="/apache-solrtm-8112-available.html" rel="alternate"></link><published>2022-06-17T00:00:00+00:00</published><updated>2022-06-17T00:00:00+00:00</updated><author [...]
+<feed xmlns="http://www.w3.org/2005/Atom"><title>Apache Solr - solr/news</title><link href="/" rel="alternate"></link><link href="/feeds/solr/news.atom.xml" rel="self"></link><id>/</id><updated>2022-10-21T00:00:00+00:00</updated><subtitle></subtitle><subtitle></subtitle><entry><title>Java 17 bug affecting Solr</title><link href="/java-17-bug-affecting-solr.html" rel="alternate"></link><published>2022-10-21T00:00:00+00:00</published><updated>2022-10-21T00:00:00+00:00</updated><author><nam [...]
+<p>Known mitigations are to either downgrade to JDK 11 or to start Solr with a Java startup flag that avoids the failure …</p></summary><content type="html"><p>Several users running Solr in production on OpenJDK 17 have experienced JVM crashes due to a known bug in the JDK. Read more about the bug in <a href="https://issues.apache.org/jira/browse/SOLR-16463">SOLR-16463</a>.</p>
+<p>Known mitigations are to either downgrade to JDK 11 or to start Solr with a Java startup flag that avoids the failure condition. Here is how to manually apply the flag:</p>
+<p>Edit your <code>solr.in.sh</code> or <code>solr.in.cmd</code> file to set the <code>SOLR_OPTS</code> environment variable as follows:</p>
+<p><em>Linux:</em> </p>
+<div class="codehilite"><pre><span></span><code><span class="nv">SOLR_OPTS</span><span class="o">=</span>-XX:CompileCommand<span class="o">=</span>exclude,com.github.benmanes.caffeine.cache.BoundedLocalCache::put
+</code></pre></div>
+
+<p><em>Windows:</em></p>
+<div class="codehilite"><pre><span></span><code>SET <span class="nv">SOLR_OPTS</span><span class="o">=</span>-XX:CompileCommand<span class="o">=</span>exclude,com.github.benmanes.caffeine.cache.BoundedLocalCache::put
+</code></pre></div>
+
+<p>Alternatively, you can inject the same flag with the <code>-a</code> argument, e.g:</p>
+<div class="codehilite"><pre><span></span><code>bin/solr -a <span class="s2">&quot;-XX:CompileCommand=exclude,com.github.benmanes.caffeine.cache.BoundedLocalCache::put&quot;</span>
+</code></pre></div>
+
+<p>If you run Solr 9 with the official Docker image, we have already pushed an updated Docker image to Docker Hub that will inject the flag for you.
+Just pull the image again to get it.
+The Docker image uses the <code>-a</code> option to set this java flag when running Solr, so if you are using the
+<code>-a</code> option you will need to provide the JVM flag mentioned above in addition to the other flags you are setting.</p></content><category term="solr/news"></category></entry><entry><title>Solr 8 Docker image changes to Eclipse Temurin JDK</title><link href="/solr-8-docker-image-changes-to-eclipse-temurin-jdk.html" rel="alternate"></link><published>2022-10-20T00:00:00+00:00</published><updated>2022-10-20T00:00:00+00:00</updated><author><name>Solr Developers</na [...]
+<p>Users should be aware that on your next <code>docker pull solr:8.11.2</code> you will be upgraded. For most users there will be no issues, as it is mainly a new distribution of the same upstream OpenJDK version. However, if you use our image as base image and rely on specific tools to be present, you may need to adapt. While <code>openjdk:11-jre</code> uses <code>Debian GNU/Linux 11 (bullseye)</code>, the <code>eclipse-temurin:11-jre-foc [...]
+<p>Furthermore, there is now no difference between the <code>solr:11-jre</code> and <code>solr:11-jre-slim</code> images, because our new vendor only offers one variant which is fairly slim already.</p></content><category term="solr/news"></category></entry><entry><title>Solr Docker images now pin the Linux release</title><link href="/solr-docker-images-now-pin-the-linux-release.html" rel="alternate"></link><published>2022-10-20T00:00:00+00:00</publish [...]
+Docker image will thus always use an updated Java 17 version. If you pull the docker image from time to time that is.</p>
+<p>However, the base image tag …</p></summary><content type="html"><p>Solr 9 was released on May 12th, using the <code>eclipse-temurin:17-jre</code> base image. Thus, we are pinned to Java 17 and Solr's
+Docker image will thus always use an updated Java 17 version. If you pull the docker image from time to time that is.</p>
+<p>However, the base image tag <code>17-jre</code> did not give us pinning to a specific Ubuntu Linux major release.
+At the time of <a href="http://localhost:8000/news.html#apache-solrtm-900-available">Solr 9 release</a> on May 12th
+it would pull Ubuntu 20.04 (Focal Fossa), but at the end of May, it was <a href="https://github.com/docker-library/official-images/commit/6d689db4846a3eb4c2ebd0e5d06139c650ef3bbb">auto upgraded</a> to the brand new Ubuntu
+22.04 (Jammy Jellyfish). This was not our desire, and we have learnt that due to this, our image is no longer compatible
+with Docker client versions before 20.10.16. Having a "floating" linux release like this can also break the image in
+other subtle ways, as well as breaking downstream images using us as a base image.</p>
+<p>We therefore decided to start pinning not only Java release, but also Linux release in our official Docker images.
+This means that Solr 9.0 is once again based on Ubuntu 20.04 Focal, i.e. a downgrade.</p>
+<p>Note that our images will still receive important Linux bug fixes from time to time, but you won't get them unless you
+re-pull the image. When we upgrade to Ubuntu 22.04 in the future, it will be a deliberate decision and not by accident.</p></content><category term="solr/news"></category></entry><entry><title>Apache Solr™ 8.11.2 available</title><link href="/apache-solrtm-8112-available.html" rel="alternate"></link><published>2022-06-17T00:00:00+00:00</published><updated>2022-06-17T00:00:00+00:00</updated><author><name>Solr Developers</name></author><id>tag:None,2022-06-17:/apache-solrtm-8112-avai [...]
<p>Solr is the popular, blazing fast, open source NoSQL search platform from the Apache Lucene project. Its major features include powerful full-text search, hit highlighting, faceted search, dynamic clustering, database integration, rich document …</p></summary><content type="html"><p>The Lucene and Solr PMCs are pleased to announce the release of Apache Solr 8.11.2.</p>
<p>Solr is the popular, blazing fast, open source NoSQL search platform from the Apache Lucene project. Its major features include powerful full-text search, hit highlighting, faceted search, dynamic clustering, database integration, rich document handling, and geospatial search. Solr is highly scalable, providing fault tolerant distributed search and indexing, and powers the search and navigation features of many of the world's largest internet sites.</p>
<p>Solr 8.11.2 is available for immediate download at:</p>
diff --git a/output/index.html b/output/index.html
index 02feb66c1..603a0df78 100644
--- a/output/index.html
+++ b/output/index.html
@@ -119,10 +119,10 @@
</div>
</div>
</section>
-<section class="topnews" latest-date="2022-06-17">
+<section class="topnews" latest-date="2022-10-21">
<div class="row">
- <p id="apache-solrtm-8112-available">
- <a href="/news.html#apache-solrtm-8112-available"><b>NEWS:</b> Apache Solr™ 8.11.2 available</a> <span class="news-date">(17.Jun)</span>
+ <p id="java-17-bug-affecting-solr">
+ <a href="/news.html#java-17-bug-affecting-solr"><b>NEWS:</b> Java 17 bug affecting Solr</a> <span class="news-date">(21.Oct)</span>
</p>
</div>
</section>
diff --git a/output/news.html b/output/news.html
index d7b14f45f..e02200606 100644
--- a/output/news.html
+++ b/output/news.html
@@ -132,6 +132,49 @@
<h1 id="solr-news">Solr<sup>™</sup> News<a class="headerlink" href="#solr-news" title="Permanent link">¶</a></h1>
<p>You may also read these news as an <a href="/feeds/solr/news.atom.xml">ATOM feed</a>.</p>
+ <h2 id="java-17-bug-affecting-solr">21 October 2022, Java 17 bug affecting Solr
+ <a class="headerlink" href="#java-17-bug-affecting-solr" title="Permanent link">¶</a>
+ </h2>
+ <p>Several users running Solr in production on OpenJDK 17 have experienced JVM crashes due to a known bug in the JDK. Read more about the bug in <a href="https://issues.apache.org/jira/browse/SOLR-16463">SOLR-16463</a>.</p>
+<p>Known mitigations are to either downgrade to JDK 11 or to start Solr with a Java startup flag that avoids the failure condition. Here is how to manually apply the flag:</p>
+<p>Edit your <code>solr.in.sh</code> or <code>solr.in.cmd</code> file to set the <code>SOLR_OPTS</code> environment variable as follows:</p>
+<p><em>Linux:</em> </p>
+<div class="codehilite"><pre><span></span><code><span class="nv">SOLR_OPTS</span><span class="o">=</span>-XX:CompileCommand<span class="o">=</span>exclude,com.github.benmanes.caffeine.cache.BoundedLocalCache::put
+</code></pre></div>
+
+<p><em>Windows:</em></p>
+<div class="codehilite"><pre><span></span><code>SET <span class="nv">SOLR_OPTS</span><span class="o">=</span>-XX:CompileCommand<span class="o">=</span>exclude,com.github.benmanes.caffeine.cache.BoundedLocalCache::put
+</code></pre></div>
+
+<p>Alternatively, you can inject the same flag with the <code>-a</code> argument, e.g:</p>
+<div class="codehilite"><pre><span></span><code>bin/solr -a <span class="s2">"-XX:CompileCommand=exclude,com.github.benmanes.caffeine.cache.BoundedLocalCache::put"</span>
+</code></pre></div>
+
+<p>If you run Solr 9 with the official Docker image, we have already pushed an updated Docker image to Docker Hub that will inject the flag for you.
+Just pull the image again to get it.
+The Docker image uses the <code>-a</code> option to set this java flag when running Solr, so if you are using the
+<code>-a</code> option you will need to provide the JVM flag mentioned above in addition to the other flags you are setting.</p>
+ <h2 id="solr-8-docker-image-changes-to-eclipse-temurin-jdk">20 October 2022, Solr 8 Docker image changes to Eclipse Temurin JDK
+ <a class="headerlink" href="#solr-8-docker-image-changes-to-eclipse-temurin-jdk" title="Permanent link">¶</a>
+ </h2>
+ <p>The official docker image for Solr 8.11 has been running on <a href="https://hub.docker.com/_/openjdk">Oracle OpenJDK 11 JRE</a>. However, due to Oracle's new release policies, they now no longer provide support for JDK11. Since Solr 8.11 is still being supported by the Apache Solr project, we needed to switch to another OpenJDK vendor with JDK11 support. We chose <a href="https://hub.docker.com/_/eclipse-temurin">Eclipse Temurin</a> from the Adoptium project. This is the same vendo [...]
+<p>Users should be aware that on your next <code>docker pull solr:8.11.2</code> you will be upgraded. For most users there will be no issues, as it is mainly a new distribution of the same upstream OpenJDK version. However, if you use our image as base image and rely on specific tools to be present, you may need to adapt. While <code>openjdk:11-jre</code> uses <code>Debian GNU/Linux 11 (bullseye)</code>, the <code>eclipse-temurin:11-jre-focal</code> image uses <code>Ubuntu 20.04.5 LTS (F [...]
+<p>Furthermore, there is now no difference between the <code>solr:11-jre</code> and <code>solr:11-jre-slim</code> images, because our new vendor only offers one variant which is fairly slim already.</p>
+ <h2 id="solr-docker-images-now-pin-the-linux-release">20 October 2022, Solr Docker images now pin the Linux release
+ <a class="headerlink" href="#solr-docker-images-now-pin-the-linux-release" title="Permanent link">¶</a>
+ </h2>
+ <p>Solr 9 was released on May 12th, using the <code>eclipse-temurin:17-jre</code> base image. Thus, we are pinned to Java 17 and Solr's
+Docker image will thus always use an updated Java 17 version. If you pull the docker image from time to time that is.</p>
+<p>However, the base image tag <code>17-jre</code> did not give us pinning to a specific Ubuntu Linux major release.
+At the time of <a href="http://localhost:8000/news.html#apache-solrtm-900-available">Solr 9 release</a> on May 12th
+it would pull Ubuntu 20.04 (Focal Fossa), but at the end of May, it was <a href="https://github.com/docker-library/official-images/commit/6d689db4846a3eb4c2ebd0e5d06139c650ef3bbb">auto upgraded</a> to the brand new Ubuntu
+22.04 (Jammy Jellyfish). This was not our desire, and we have learnt that due to this, our image is no longer compatible
+with Docker client versions before 20.10.16. Having a "floating" linux release like this can also break the image in
+other subtle ways, as well as breaking downstream images using us as a base image.</p>
+<p>We therefore decided to start pinning not only Java release, but also Linux release in our official Docker images.
+This means that Solr 9.0 is once again based on Ubuntu 20.04 Focal, i.e. a downgrade.</p>
+<p>Note that our images will still receive important Linux bug fixes from time to time, but you won't get them unless you
+re-pull the image. When we upgrade to Ubuntu 22.04 in the future, it will be a deliberate decision and not by accident.</p>
<h2 id="apache-solrtm-8112-available">17 June 2022, Apache Solr™ 8.11.2 available
<a class="headerlink" href="#apache-solrtm-8112-available" title="Permanent link">¶</a>
</h2>