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

Olivér Szabó updated AMBARI-24067:
----------------------------------
    Affects Version/s:     (was: 2.7.0)
                       2.6.0

> Log Search: indexed string field can be too large for audit_logs
> ----------------------------------------------------------------
>
>                 Key: AMBARI-24067
>                 URL: https://issues.apache.org/jira/browse/AMBARI-24067
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-infra, ambari-logsearch
>    Affects Versions: 2.6.0
>            Reporter: Olivér Szabó
>            Assignee: Olivér Szabó
>            Priority: Critical
>             Fix For: 2.7.0
>
>
> {code:java}
> error en audit_logs
> 2018-05-29 19:33:18,434 [qtp225493257-718281] ERROR [c:audit_logs s:shard4 
> r:core_node6 x:audit_logs_shard4_replica1] 
> org.apache.solr.common.SolrException (SolrException.java:148) - 
> org.apache.solr.common.SolrException: Exception writing document id 
> 8c5deae9-c1b7-4ebf-9981-1ac92f1d2f84 to the index; possible analysis error: 
> Document contains at least one immense term in field="action" (whose UTF8 
> encoding is longer than the max length 32766), all of which were skipped.  
> Please correct the analyzer to not produce such terms.  The prefix of the 
> first immense term is: '[105, 110, 115, 116, 97, 108, 108, 101, 100, 58, 32, 
> 97, 108, 108, 32, 115, 101, 114, 118, 105, 99, 101, 115, 32, 111, 110, 32, 
> 97, 108, 108]...', original message: bytes can be at most 32766 in length; 
> got 106331. Perhaps the document has an indexed string field (solr.StrField) 
> which is too large
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to