[
https://issues.apache.org/jira/browse/AMBARI-19033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15711701#comment-15711701
]
Hudson commented on AMBARI-19033:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6125 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6125/])
AMBARI-19033. Log Search: Cannot increase the number of shards per node
(oleewere:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=195b7456c0b4dc15833b502463daba7b29a51bee])
* (edit)
ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/dao/SolrCollectionDao.java
> Log Search: Cannot increase the number of shards per node for solr collections
> ------------------------------------------------------------------------------
>
> Key: AMBARI-19033
> URL: https://issues.apache.org/jira/browse/AMBARI-19033
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
> Affects Versions: 2.4.0
> Reporter: Olivér Szabó
> Assignee: Olivér Szabó
> Fix For: 2.5.0
>
> Attachments: AMBARI-19033.patch
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> If the user changes the number of shards for collections, logsearch cannot
> create the new shards if there is not enough solr cores for that
> (same for hadoop_logs and audit_logs collection)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
