You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@lucene.apache.org by kr...@apache.org on 2016/10/27 20:09:49 UTC

[45/50] [abbrv] lucene-solr:jira/solr-8593: SOLR-9692: blockUnknown property makes inter-node communication impossible

SOLR-9692: blockUnknown property makes inter-node communication impossible


Project: http://git-wip-us.apache.org/repos/asf/lucene-solr/repo
Commit: http://git-wip-us.apache.org/repos/asf/lucene-solr/commit/d9c4846e
Tree: http://git-wip-us.apache.org/repos/asf/lucene-solr/tree/d9c4846e
Diff: http://git-wip-us.apache.org/repos/asf/lucene-solr/diff/d9c4846e

Branch: refs/heads/jira/solr-8593
Commit: d9c4846ee17c18114843e01a6319b31033a4d3a9
Parents: 7b3d29d
Author: Noble Paul <no...@apache.org>
Authored: Thu Oct 27 14:35:18 2016 +0530
Committer: Noble Paul <no...@apache.org>
Committed: Thu Oct 27 14:35:18 2016 +0530

----------------------------------------------------------------------
 solr/CHANGES.txt | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/lucene-solr/blob/d9c4846e/solr/CHANGES.txt
----------------------------------------------------------------------
diff --git a/solr/CHANGES.txt b/solr/CHANGES.txt
index 0c3ec3a..7d9a4fa 100644
--- a/solr/CHANGES.txt
+++ b/solr/CHANGES.txt
@@ -232,6 +232,8 @@ Bug Fixes
 
 * SOLR-4164: group.limit=-1 was not supported for grouping in distributed mode.
   (Cao Manh Dat, Lance Norskog, Webster Homer, hossman, yonik)
+
+* SOLR-9692: blockUnknown property makes inter-node communication impossible (noble)
  
 Optimizations
 ----------------------
@@ -396,7 +398,7 @@ Bug Fixes
 
 * SOLR-9389: HDFS Transaction logs stay open for writes which leaks Xceivers. (Tim Owen via Mark Miller)
 
-* SOLR-9692: blockUnknown property makes inter-node communication impossible (noble)
+* SOLR-9188: blockUnknown property makes inter-node communication impossible (noble)
 
 * SOLR-9455: Deleting a sub-shard in recovery state can mark parent shard as inactive. (shalin)