[ 
https://issues.apache.org/jira/browse/AMBARI-19033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Olivér Szabó resolved AMBARI-19033.
-----------------------------------
    Resolution: Fixed

committed to trunk:
{code:java}
commit 195b7456c0b4dc15833b502463daba7b29a51bee
Author: oleewere <oleew...@gmail.com>
Date:   Thu Dec 1 11:34:45 2016 +0100

    AMBARI-19033. Log Search: Cannot increase the number of shards per node for 
solr collections (oleewere)
    
    Change-Id: I44fa2c96befa2eff3d6f2acfb608eff8ed45f021
{code}
committed to branch-2.5:
{code:java}
commit 80b5348cac1c54942ca33d92dbc392faa74c9662
Author: oleewere <oleew...@gmail.com>
Date:   Thu Dec 1 11:34:45 2016 +0100

    AMBARI-19033. Log Search: Cannot increase the number of shards per node for 
solr collections (oleewere)
    
    Change-Id: I44fa2c96befa2eff3d6f2acfb608eff8ed45f021
{code}

> 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)

Reply via email to