ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Olivér Szabó (JIRA) <j...@apache.org>
Subject [jira] [Resolved] (AMBARI-16288) Separate number of shards and replication factor configurations for audit logs and service logs
Date Tue, 10 May 2016 13:12:12 GMT

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

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

committed to trunk:
{code:java}
commit 3332dad4d6da83defc61dba6db3a147db63deecb
Author: oleewere <oleewere@gmail.com>
Date:   Tue May 10 13:39:51 2016 +0200

    AMBARI-16288. Separate number of shards and replication factor configurations for audit
logs and service logs (oleewere)
{code}

> Separate number of shards and replication factor configurations for audit logs and service
logs
> -----------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-16288
>                 URL: https://issues.apache.org/jira/browse/AMBARI-16288
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-logsearch, ambari-server
>    Affects Versions: 2.4.0
>            Reporter: Olivér Szabó
>            Assignee: Olivér Szabó
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-16288.patch
>
>
> Currently "logsearch.collection.numshards" and "logsearch.collection.replication.factor"
configuration is responsible to set the number of shards and replication factor for both service
log and audit log collections. These configurations needs to be separated (based on collection
names)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message