You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@lucene.apache.org by da...@apache.org on 2018/10/08 03:39:04 UTC
[1/2] lucene-solr:jira/http2: Update CHANGES.txt and ref-guide since
ssl + http/2 is supported
Repository: lucene-solr
Updated Branches:
refs/heads/jira/http2 2d51180bb -> ba69f2ac2
Update CHANGES.txt and ref-guide since ssl + http/2 is supported
Project: http://git-wip-us.apache.org/repos/asf/lucene-solr/repo
Commit: http://git-wip-us.apache.org/repos/asf/lucene-solr/commit/e903dfa4
Tree: http://git-wip-us.apache.org/repos/asf/lucene-solr/tree/e903dfa4
Diff: http://git-wip-us.apache.org/repos/asf/lucene-solr/diff/e903dfa4
Branch: refs/heads/jira/http2
Commit: e903dfa4faf65f0c42b310565f4e8db0c5de7d98
Parents: 2d51180
Author: Cao Manh Dat <da...@apache.org>
Authored: Mon Oct 8 10:28:55 2018 +0700
Committer: Cao Manh Dat <da...@apache.org>
Committed: Mon Oct 8 10:28:55 2018 +0700
----------------------------------------------------------------------
solr/CHANGES.txt | 7 +++----
solr/solr-ref-guide/src/major-changes-in-solr-8.adoc | 3 +--
2 files changed, 4 insertions(+), 6 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/lucene-solr/blob/e903dfa4/solr/CHANGES.txt
----------------------------------------------------------------------
diff --git a/solr/CHANGES.txt b/solr/CHANGES.txt
index 7f74f8f..b5bfd2a 100644
--- a/solr/CHANGES.txt
+++ b/solr/CHANGES.txt
@@ -31,10 +31,9 @@ Jetty 9.4.11.v20180605
Upgrade Notes
----------------------
-* Solr nodes can now listen and serve HTTP/2 requests. However nodes with HTTPS setup still only serve HTTP/1.1 requests.
- Most of internal requests (sent by UpdateShardHandler, HttpShardHandler) Http2SolrClient is used.
- Since by default, internal requests are sent by using HTTP/2 (except for HTTPS case as mentioned above),
- therefore Solr 8.0 nodes can't talk to old nodes (7.x). However we can follow these steps to do rolling updates:
+* Solr nodes can now listen and serve HTTP/2 requests. Most of internal requests (sent by UpdateShardHandler, HttpShardHandler)
+ Http2SolrClient is used. Since by default, internal requests are sent by using HTTP/2,
+ Solr 8.0 nodes can't talk to old nodes (7.x). However we can follow these steps to do rolling updates:
- Do rolling updates as normally, but the Solr 8.0 nodes must start with -Dsolr.http1=true as startup parameter.
By using this parameter internal requests are sent by using HTTP/1.1
- When all nodes are upgraded to 8.0, restart them, this time -Dsolr.http1 parameter should be removed.
http://git-wip-us.apache.org/repos/asf/lucene-solr/blob/e903dfa4/solr/solr-ref-guide/src/major-changes-in-solr-8.adoc
----------------------------------------------------------------------
diff --git a/solr/solr-ref-guide/src/major-changes-in-solr-8.adoc b/solr/solr-ref-guide/src/major-changes-in-solr-8.adoc
index 8b7566d..459d1cb 100644
--- a/solr/solr-ref-guide/src/major-changes-in-solr-8.adoc
+++ b/solr/solr-ref-guide/src/major-changes-in-solr-8.adoc
@@ -29,8 +29,7 @@ Solr 8 is a major new release of Solr which introduces new features and a number
Due to the introduction of LIR redesign since Solr 7.3 (SOLR-11702) and the removing of old LIR implementation in Solr 8.
Rolling updates are not possible unless all nodes must be on Solr 7.3 or higher. If not updates can be lost.
-Solr nodes can now listen and serve HTTP/2 and HTTP/1 requests. However nodes with HTTPS setup still can only serve
-HTTP/1.1 requests. By default, most of internal requests are sent by using HTTP/2 (except for HTTPS case as mentioned above),
+Solr nodes can now listen and serve HTTP/2 and HTTP/1 requests. By default, most of internal requests are sent by using HTTP/2
therefore Solr 8.0 nodes can't talk to old nodes (7.x).
However we can follow these steps to do rolling updates:
[2/2] lucene-solr:jira/http2: Update javadocs links for ref-guide
Posted by da...@apache.org.
Update javadocs links for ref-guide
Project: http://git-wip-us.apache.org/repos/asf/lucene-solr/repo
Commit: http://git-wip-us.apache.org/repos/asf/lucene-solr/commit/ba69f2ac
Tree: http://git-wip-us.apache.org/repos/asf/lucene-solr/tree/ba69f2ac
Diff: http://git-wip-us.apache.org/repos/asf/lucene-solr/diff/ba69f2ac
Branch: refs/heads/jira/http2
Commit: ba69f2ac2699c885fe0cd24b37cf0169cee84b43
Parents: e903dfa
Author: Cao Manh Dat <da...@apache.org>
Authored: Mon Oct 8 10:39:06 2018 +0700
Committer: Cao Manh Dat <da...@apache.org>
Committed: Mon Oct 8 10:39:06 2018 +0700
----------------------------------------------------------------------
.../src/major-changes-in-solr-8.adoc | 26 +++++++++++++-------
1 file changed, 17 insertions(+), 9 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/lucene-solr/blob/ba69f2ac/solr/solr-ref-guide/src/major-changes-in-solr-8.adoc
----------------------------------------------------------------------
diff --git a/solr/solr-ref-guide/src/major-changes-in-solr-8.adoc b/solr/solr-ref-guide/src/major-changes-in-solr-8.adoc
index 459d1cb..09e5db4 100644
--- a/solr/solr-ref-guide/src/major-changes-in-solr-8.adoc
+++ b/solr/solr-ref-guide/src/major-changes-in-solr-8.adoc
@@ -45,13 +45,21 @@ per TCP connection this means that for sending multiple requests at the same tim
established. This leads to waste of resources on both-sides and long GC-pause. Solr 8 with HTTP/2 support overcomes that problem by allowing
multiple requests can be sent in parallel using a same TCP connection.
-`Http2SolrClient` with HTTP/2 and async capabilities based on Jetty Client is introduced. This client replaced
-`HttpSolrClient` and `ConcurrentUpdateSolrClient` for sending most of internal requests (sent by `UpdateShardHandler`,
-`HttpShardHandler`). An interesting benchmark result showing gain of using `Http2SolrClient` had been posted
-https://issues.apache.org/jira/browse/SOLR-12642?focusedCommentId=16606648&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16606648[here]. However this leads to several changes in configuration and authentication setup
-
-* `UpdateShardHandler.maxConnections` parameter is no longer being used
-* `HttpShardHandlerFactory.maxConnections` parameter is no longer being used
-* Custom `AuthenticationPlugin` must provide its own setup for `Http2SolrClient` through
- `SolrHttpClientBuilder.setHttp2Configurator`, if not internal requests can't be authenticated
+{solr-javadocs}/solr-solrj/org/apache/solr/client/solrj/impl/Http2SolrClient.html[`Http2SolrClient`]
+with HTTP/2 and async capabilities based on Jetty Client is introduced. This client replaced
+{solr-javadocs}/solr-solrj/org/apache/solr/client/solrj/impl/HttpSolrClient.html[`HttpSolrClient`] and
+{solr-javadocs}/solr-solrj/org/apache/solr/client/solrj/impl/ConcurrentUpdateSolrClient.html[`ConcurrentUpdateSolrClient`]
+for sending most of internal requests (sent by
+{solr-javadocs}/solr-core/org/apache/solr/update/UpdateShardHandler.html[`UpdateShardHandler`],
+{solr-javadocs}/solr-core/org/apache/solr/handler/component/HttpShardHandler.html[`HttpShardHandler`]).
+An interesting benchmark result showing gain of using {solr-javadocs}/solr-solrj/org/apache/solr/client/solrj/impl/Http2SolrClient.html[`Http2SolrClient`] had been posted
+https://issues.apache.org/jira/browse/SOLR-12642?focusedCommentId=16606648&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16606648[here].
+However this leads to several changes in configuration and authentication setup
+
+* {solr-javadocs}/solr-core/org/apache/solr/update/UpdateShardHandler.html[`UpdateShardHandler.maxConnections`] parameter is no longer being used
+* {solr-javadocs}/solr-core/org/apache/solr/handler/component/HttpShardHandler.html[`HttpShardHandlerFactory.maxConnections`] parameter is no longer being used
+* Custom {solr-javadocs}/solr-core/org/apache/solr/security/AuthenticationPlugin.html[`AuthenticationPlugin`] must provide its own setup for
+ {solr-javadocs}/solr-solrj/org/apache/solr/client/solrj/impl/Http2SolrClient.html[`Http2SolrClient`] through
+ {solr-javadocs}/solr-solrj/org/apache/solr/client/solrj/impl/SolrHttpClientBuilder.html[`SolrHttpClientBuilder.setHttp2Configurator`],
+ if not internal requests can't be authenticated