[ 
https://issues.apache.org/jira/browse/SOLR-12814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16638494#comment-16638494
 ] 

ASF subversion and git services commented on SOLR-12814:
--------------------------------------------------------

Commit 5fb384c9898176d34fffe2b310a0a815d8aebecb in lucene-solr's branch 
refs/heads/master from [~janhoy]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=5fb384c ]

SOLR-12814: Metrics history causing "HttpParser URI is too large >8192" when 
many collections
This fixes #461


> Metrics history causing "HttpParser URI is too large >8192" when many 
> collections
> ---------------------------------------------------------------------------------
>
>                 Key: SOLR-12814
>                 URL: https://issues.apache.org/jira/browse/SOLR-12814
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: metrics, SolrCloud
>    Affects Versions: 7.5
>         Environment: 3x zookeeper and 3x solr cloud servers,
> 50 test collections with 0 data in them
>            Reporter: matthew medway
>            Assignee: Jan Høydahl
>            Priority: Major
>              Labels: URI, header, http, httpparser, large, metrics, solr, 
> solrcloud, too, uri
>             Fix For: 7.5.1, 7.6, master (8.0)
>
>         Attachments: longmetricsquery.txt, screencapture-cloud-graph.png, 
> screencapture-nodes-actual-IP.png, screenshot-debug.png
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> If you have a lot of collections, like 50 or more, the new metrics page in 
> version 7.5 can't run its queries because the default 
> solr.jetty.request.header.size and solr.jetty.response.header.size values are 
> too small.
> If I up the header values from 8192 to 65536 the commands will work.
> command to change the defaults:
> {code:java}
> sed -i 's/\"solr.jetty.request.header.size\" 
> default=\"8192\"/\"solr.jetty.request.header.size\" default=\"65536\"/g' 
> /opt/solr/server/etc/jetty.xml 
> sed -i 's/\"solr.jetty.response.header.size\" 
> default=\"8192\"/\"solr.jetty.response.header.size\" default=\"65536\"/g' 
> /opt/solr/server/etc/jetty.xml
> {code}
> before changing the header size log: 
> {code:java}
> 2018-09-27 13:06:45.434 INFO (qtp534906248-14) [ ] o.a.s.s.HttpSolrCall 
> [admin] webapp=null path=/admin/metrics 
> params={wt=javabin&version=2&key=solr.jvm:os.processCpuLoad&key=solr.node:CONTAINER.fs.coreRoot.usableSpace&key=solr.jvm:os.systemLoadAverage&key=solr.jvm:memory.heap.used}
>  status=0 QTime=0
> 2018-09-27 13:07:45.527 WARN (qtp534906248-17) [ ] o.e.j.h.HttpParser URI is 
> too large >8192
> 2018-09-27 13:07:45.530 INFO (qtp534906248-16) [ ] o.a.s.s.HttpSolrCall 
> [admin] webapp=null path=/admin/metrics 
> params={wt=javabin&version=2&key=solr.jvm:os.processCpuLoad&key=solr.node:CONTAINER.fs.coreRoot.usableSpace&key=solr.jvm:os.systemLoadAverage&key=solr.jvm:memory.heap.used}
>  status=0 QTime=0
> 2018-09-27 13:08:45.621 WARN (qtp534906248-20) [ ] o.e.j.h.HttpParser URI is 
> too large >8192
> 2018-09-27 13:08:45.625 INFO (qtp534906248-15) [ ] o.a.s.s.HttpSolrCall 
> [admin] webapp=null path=/admin/metrics 
> params={wt=javabin&version=2&key=solr.jvm:os.processCpuLoad&key=solr.node:CONTAINER.fs.coreRoot.usableSpace&key=solr.jvm:os.systemLoadAverage&key=solr.jvm:memory.heap.used}
>  status=0 QTime=0
> 2018-09-27 13:09:45.725 WARN (qtp534906248-20) [ ] o.e.j.h.HttpParser URI is 
> too large >8192
> {code}
> After changing the header size log:
> {code:java}
> attached as a file because its very long and ugly{code}
> Is it possible to break up this command into batches so that it can run 
> without modifying the header sizes? 
> Thanks!
>  -Matt
>  



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

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to