Re: HttpParser URI is too large

2019-01-30 Thread levtannen 
Thank you Eric, 
Actually I have figured this out, but there is a deeper problem: where do
these messages come from? They are internal messages. If I suppress messages
from  "org.apache.solr.servlet.HttpSolrCall" I will suppress all query
reporting and I do not want this. So the question is what is the meaning of
these messages, why I am getting them and how to suppress them if I am
really do not need them?
Regards,
Lev Tannen



--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: HttpParser URI is too large

2019-01-30 Thread Erick Erickson 
Full class name is "org.apache.solr.servlet.HttpSolrCall"
which you should be able to set to WARN level in log4j2.xml.
DEBUG is definitely _not_ what you want as it dumps
more information

BTW, if you want to see the full path in the log file, you can change
the patternlayout in log4j2.xml to something like
%c
rather than
%c{1.}

On Tue, Jan 29, 2019 at 2:09 PM levtannen  wrote:
>
> Thank you Jan. This solution worked. The warning message "URI is too large
> >81920" disappeared. But this fix unleashed an another problem: The INFO
> message that was suppressed by the previous error now is displayed in all
> its length. And it is way too long because it lists all 100 collections. I
> do not need this message in a log and I hope it can be prevented by setting
> an appropriate logger level to DEBUG or to ERROR in solr4j2.xml, but I do
> not know the name of this logger. Could you or somebody in the community to
> figure this out from the following fragment of the log?
> Regards
> Lev Tannen
>
> 32610 2019-01-29 18:07:01.870 INFO  (qtp817348612-19) [   ]
> o.a.s.s.HttpSolrCall [admin] webapp=null path=/admin/metrics
> params={wt=javabin&version=2&key=solr.core.ME-B-cases.shard1.replica_n4:UPDATE./update.requests&key=s
> olr.core.TXS-A-documents.shard1.replica_n1:INDEX.sizeInBytes&key=solr.core.LAW-A-documents.shard1.replica_n4:UPDATE./update.requests&key=solr.core.CA1-A-documents.shard1.replica_n1:INDEX.sizeInBytes&key=solr.core.NYE
> -A-documents.shard1.replica_n4:UPDATE./update.requests&key=solr.core.TXS-B-cases.shard1.replica_n4:QUERY./select.requests&key=solr.core.VI-B-documents.shard1.replica_n4:UPDATE./update.requests&key=solr.core.GU-A-docu
> ments.shard1.replica_n2:QUERY./select.requests&key=solr.core.GAN-B-documents.shard1.replica_n4:QUERY./select.requests&key=solr.core.VT-B-documents.shard1.replica_n1:QUERY./select.requests&key=solr.core.CA7-B-document
> s.shard1.replica_n5:INDEX.sizeInBytes&key=solr.core.MIW-B-cases.shard1.replica_n4:INDEX.sizeInBytes&key=solr.core.MSS-A-documents.shard1.replica_n2:UPDATE./update.requests&key=solr.core.CA2-A-documents.shard1.replica
> _n4:UPDATE./update.requests&key=solr.core.NYS-A-cases.shard1.replica_n4:UPDATE./update.requests&key=solr.core.VAE-B-cases.shard1.replica_n4:INDEX.sizeInBytes&key=solr.core.NYS-B-documents.shard1.replica_n1:INDEX.size
> InBytes&key=solr.core.NCE-B-cases.shard1.replica_n4:QUERY./select.requests&key=solr.core.FLN-B-cases.shard1.replica_n4:INDEX.sizeInBytes&key=solr.core.TNM-A-cases.shard1.replica_n1:UPDATE./update.requests&key=solr.co
> re.OKW-A-cases.shard1.replica_n2:INDEX.sizeInBytes&key=solr.core.PR-B-cases.shard1.replica_n1:UPDATE./update.requests&key=solr.core.INS-B-documents.shard1.replica_n4:INDEX.sizeInBytes&key=solr.core.CA2-B-documents.sh
> ard1.replica_n3:QUERY./select.requests&key=solr.core.GU-A-cases.shard1.replica_n1:QUERY./select.requests&key=solr.core.FLM-B-cases.shard1.replica_n4:UPDATE./update.requests&key=solr.core.ARE-B-documents.shard1.replic
> a_n4:QUERY./select.requests&key=solr.core.NYN-B-documents.shard1.replica_n4:INDEX.sizeInBytes&key=solr.core.GAN-B-documents.shard1.replica_n4:UPDATE./update.requests&key=solr.core.GAN-A-cases.shard1.replica_n1:UPDATE
> ./update.requests&key=solr.core.CAN-B-cases.shard1.replica_n4:INDEX.sizeInBytes&key=solr.core.NCE-B-documents.shard1.replica_n4:UPDATE./update.requests&key=solr.core.WIE-B-cases.shard1.replica_n2:UPDATE./update.reque
> sts&key=solr.core.VAE-B-cases.shard1.replica_n4:QUERY./select.requests&key=solr.core.CAS-A-documents.shard1.replica_n2:UPDATE./update.requests&key=solr.core.PR-A-cases.shard1.replica_n4:UPDATE./update.requests&key=so
> lr.core.CAS-A-documents.shard1.replica_n2:INDEX.sizeInBytes&key=solr.core.ALM-B-documents.shard1.replica_n2:UPDATE./update.requests&key=solr.core.VAW-A-cases.shard1.replica_n4:QUERY./select.requests&key=solr.core.FLM
> 
> ...
>
>
>
> --
> Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: HttpParser URI is too large

2019-01-29 Thread levtannen 
Thank you Jan. This solution worked. The warning message "URI is too large
>81920" disappeared. But this fix unleashed an another problem: The INFO
message that was suppressed by the previous error now is displayed in all
its length. And it is way too long because it lists all 100 collections. I
do not need this message in a log and I hope it can be prevented by setting
an appropriate logger level to DEBUG or to ERROR in solr4j2.xml, but I do
not know the name of this logger. Could you or somebody in the community to
figure this out from the following fragment of the log?
Regards
Lev Tannen

32610 2019-01-29 18:07:01.870 INFO  (qtp817348612-19) [   ]
o.a.s.s.HttpSolrCall [admin] webapp=null path=/admin/metrics
params={wt=javabin&version=2&key=solr.core.ME-B-cases.shard1.replica_n4:UPDATE./update.requests&key=s
 
olr.core.TXS-A-documents.shard1.replica_n1:INDEX.sizeInBytes&key=solr.core.LAW-A-documents.shard1.replica_n4:UPDATE./update.requests&key=solr.core.CA1-A-documents.shard1.replica_n1:INDEX.sizeInBytes&key=solr.core.NYE
 
-A-documents.shard1.replica_n4:UPDATE./update.requests&key=solr.core.TXS-B-cases.shard1.replica_n4:QUERY./select.requests&key=solr.core.VI-B-documents.shard1.replica_n4:UPDATE./update.requests&key=solr.core.GU-A-docu
 
ments.shard1.replica_n2:QUERY./select.requests&key=solr.core.GAN-B-documents.shard1.replica_n4:QUERY./select.requests&key=solr.core.VT-B-documents.shard1.replica_n1:QUERY./select.requests&key=solr.core.CA7-B-document
 
s.shard1.replica_n5:INDEX.sizeInBytes&key=solr.core.MIW-B-cases.shard1.replica_n4:INDEX.sizeInBytes&key=solr.core.MSS-A-documents.shard1.replica_n2:UPDATE./update.requests&key=solr.core.CA2-A-documents.shard1.replica
 
_n4:UPDATE./update.requests&key=solr.core.NYS-A-cases.shard1.replica_n4:UPDATE./update.requests&key=solr.core.VAE-B-cases.shard1.replica_n4:INDEX.sizeInBytes&key=solr.core.NYS-B-documents.shard1.replica_n1:INDEX.size
 
InBytes&key=solr.core.NCE-B-cases.shard1.replica_n4:QUERY./select.requests&key=solr.core.FLN-B-cases.shard1.replica_n4:INDEX.sizeInBytes&key=solr.core.TNM-A-cases.shard1.replica_n1:UPDATE./update.requests&key=solr.co
 
re.OKW-A-cases.shard1.replica_n2:INDEX.sizeInBytes&key=solr.core.PR-B-cases.shard1.replica_n1:UPDATE./update.requests&key=solr.core.INS-B-documents.shard1.replica_n4:INDEX.sizeInBytes&key=solr.core.CA2-B-documents.sh
 
ard1.replica_n3:QUERY./select.requests&key=solr.core.GU-A-cases.shard1.replica_n1:QUERY./select.requests&key=solr.core.FLM-B-cases.shard1.replica_n4:UPDATE./update.requests&key=solr.core.ARE-B-documents.shard1.replic
 
a_n4:QUERY./select.requests&key=solr.core.NYN-B-documents.shard1.replica_n4:INDEX.sizeInBytes&key=solr.core.GAN-B-documents.shard1.replica_n4:UPDATE./update.requests&key=solr.core.GAN-A-cases.shard1.replica_n1:UPDATE
 
./update.requests&key=solr.core.CAN-B-cases.shard1.replica_n4:INDEX.sizeInBytes&key=solr.core.NCE-B-documents.shard1.replica_n4:UPDATE./update.requests&key=solr.core.WIE-B-cases.shard1.replica_n2:UPDATE./update.reque
 
sts&key=solr.core.VAE-B-cases.shard1.replica_n4:QUERY./select.requests&key=solr.core.CAS-A-documents.shard1.replica_n2:UPDATE./update.requests&key=solr.core.PR-A-cases.shard1.replica_n4:UPDATE./update.requests&key=so
 
lr.core.CAS-A-documents.shard1.replica_n2:INDEX.sizeInBytes&key=solr.core.ALM-B-documents.shard1.replica_n2:UPDATE./update.requests&key=solr.core.VAW-A-cases.shard1.replica_n4:QUERY./select.requests&key=solr.core.FLM

...



--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: HttpParser URI is too large

2019-01-03 Thread Jan Høydahl 
Upgrade to v7.6
https://issues.apache.org/jira/browse/SOLR-12814 


--
Jan Høydahl, search solution architect
Cominvent AS - www.cominvent.com

> 21. des. 2018 kl. 21:00 skrev Tannen, Lev (USAEO) [Contractor] 
> :
> 
> Hello Solr community,
> 
> My solrcloud system consists of 3 machines, each running a zookeeper and a 
> solr server. It manages about 200 collections with 1 shard each. It is up and 
> running, but about every minutes it produces  messages in the message log on 
> each computer (messages are at the end). These messages do not relate to any 
> requests. It looks like they are produced by some internal mechanism. Using a 
> suggestion found on the Internet I have already increased the 
> requestHeaderSize and the responseHeaderSize to 81920, but this did not help.
> Do anyone know what do these messages mean and how to get reed of them?
> Thank you.
> Lev Tannen
> 
> Message on Computer1:
> 2018-12-21 19:44:46.552 WARN  (qtp817348612-21) [   ] o.e.j.h.HttpParser URI 
> is too large >81920
> 2018-12-21 19:44:46.560 INFO  (qtp817348612-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=1
> 
> Message on computer 2
> 2018-12-21 19:44:46.530 WARN  (qtp817348612-14) [   ] o.e.j.h.HttpParser URI 
> is too large >81920
> 2018-12-21 19:44:46.537 INFO  (qtp817348612-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=2
> 
> Message on computer3 (a leader)
> 2018-12-21 19:44:46.513 WARN  (qtp817348612-14) [   ] o.e.j.h.HttpParser URI 
> is too large >81920
> 2018-12-21 19:44:46.514 WARN  (MetricsHistoryHandler-12-thread-1) [   ] 
> o.a.s.c.s.i.SolrClientNodeStateProvider could not get tags from node 
> usahubslvcvw121.usa.doj.gov:8983_solr
> org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: Error 
> from server at http://usahubslvcvw121.usa.doj.gov:8983/solr: Expected mime 
> type application/octet-stream but got text/html. Bad Message 
> 414reason: URI Too Long
>at 
> org.apache.solr.client.solrj.impl.HttpSolrClient.executeMethod(HttpSolrClient.java:607)
>  ~[solr-solrj-7.4.0.jar:7.4.0 9060ac689c270b02143f375de0348b7f626adebc - 
> jpountz - 2018-06-18 16:55:14]
>at 
> org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:255)
>  ~[solr-solrj-7.4.0.jar:7.4.0 9060ac689c270b02143f375de0348b7f626adebc - 
> jpountz - 2018-06-18 16:55:14]
>at 
> org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:244)
>  ~[solr-solrj-7.4.0.jar:7.4.0 9060ac689c270b02143f375de0348b7f626adebc - 
> jpountz - 2018-06-18 16:55:14]
>at 
> org.apache.solr.client.solrj.SolrClient.request(SolrClient.java:1219) 
> ~[solr-solrj-7.4.0.jar:7.4.0 9060ac689c270b02143f375de0348b7f626adebc - 
> jpountz - 2018-06-18 16:55:14]
>at 
> org.apache.solr.client.solrj.impl.SolrClientNodeStateProvider$ClientSnitchCtx.invoke(SolrClientNodeStateProvider.java:292)
>  ~[solr-solrj-7.4.0.jar:7.4.0 9060ac689c270b02143f375de0348b7f626adebc - 
> jpountz - 2018-06-18 16:55:14]
>at 
> org.apache.solr.client.solrj.impl.SolrClientNodeStateProvider.fetchMetrics(SolrClientNodeStateProvider.java:150)
>  ~[solr-solrj-7.4.0.jar:7.4.0 9060ac689c270b02143f375de0348b7f626adebc - 
> jpountz - 2018-06-18 16:55:14]
>at 
> org.apache.solr.client.solrj.impl.SolrClientNodeStateProvider.getReplicaInfo(SolrClientNodeStateProvider.java:131)
>  ~[solr-solrj-7.4.0.jar:7.4.0 9060ac689c270b02143f375de0348b7f626adebc - 
> jpountz - 2018-06-18 16:55:14]
>at 
> org.apache.solr.handler.admin.MetricsHistoryHandler.collectGlobalMetrics(MetricsHistoryHandler.java:478)
>  ~[solr-core-7.4.0.jar:7.4.0 9060ac689c270b02143f375de0348b7f626adebc - 
> jpountz - 2018-06-18 16:55:13]
>at 
> org.apache.solr.handler.admin.MetricsHistoryHandler.collectMetrics(MetricsHistoryHandler.java:368)
>  ~[solr-core-7.4.0.jar:7.4.0 9060ac689c270b02143f375de0348b7f626adebc - 
> jpountz - 2018-06-18 16:55:13]
>at 
> org.apache.solr.handler.admin.MetricsHistoryHandler.lambda$new$0(MetricsHistoryHandler.java:230)
>  ~[solr-core-7.4.0.jar:7.4.0 9060ac689c270b02143f375de0348b7f626adebc - 
> jpountz - 2018-06-18 16:55:13]
>at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> [?:1.8.0_181]
>at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) 
> [?:1.8.0_181]
>at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>  [?:1.8.0_181]
>at 
> java.util.concurrent.Sc

HttpParser URI is too large

2018-12-21 Thread Tannen, Lev (USAEO) [Contractor] 
Hello Solr community,

My solrcloud system consists of 3 machines, each running a zookeeper and a solr 
server. It manages about 200 collections with 1 shard each. It is up and 
running, but about every minutes it produces  messages in the message log on 
each computer (messages are at the end). These messages do not relate to any 
requests. It looks like they are produced by some internal mechanism. Using a 
suggestion found on the Internet I have already increased the requestHeaderSize 
and the responseHeaderSize to 81920, but this did not help.
Do anyone know what do these messages mean and how to get reed of them?
Thank you.
Lev Tannen

Message on Computer1:
2018-12-21 19:44:46.552 WARN  (qtp817348612-21) [   ] o.e.j.h.HttpParser URI is 
too large >81920
2018-12-21 19:44:46.560 INFO  (qtp817348612-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=1

Message on computer 2
2018-12-21 19:44:46.530 WARN  (qtp817348612-14) [   ] o.e.j.h.HttpParser URI is 
too large >81920
2018-12-21 19:44:46.537 INFO  (qtp817348612-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=2

Message on computer3 (a leader)
2018-12-21 19:44:46.513 WARN  (qtp817348612-14) [   ] o.e.j.h.HttpParser URI is 
too large >81920
2018-12-21 19:44:46.514 WARN  (MetricsHistoryHandler-12-thread-1) [   ] 
o.a.s.c.s.i.SolrClientNodeStateProvider could not get tags from node 
usahubslvcvw121.usa.doj.gov:8983_solr
org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: Error 
from server at http://usahubslvcvw121.usa.doj.gov:8983/solr: Expected mime type 
application/octet-stream but got text/html. Bad Message 
414reason: URI Too Long
at 
org.apache.solr.client.solrj.impl.HttpSolrClient.executeMethod(HttpSolrClient.java:607)
 ~[solr-solrj-7.4.0.jar:7.4.0 9060ac689c270b02143f375de0348b7f626adebc - 
jpountz - 2018-06-18 16:55:14]
at 
org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:255)
 ~[solr-solrj-7.4.0.jar:7.4.0 9060ac689c270b02143f375de0348b7f626adebc - 
jpountz - 2018-06-18 16:55:14]
at 
org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:244)
 ~[solr-solrj-7.4.0.jar:7.4.0 9060ac689c270b02143f375de0348b7f626adebc - 
jpountz - 2018-06-18 16:55:14]
at 
org.apache.solr.client.solrj.SolrClient.request(SolrClient.java:1219) 
~[solr-solrj-7.4.0.jar:7.4.0 9060ac689c270b02143f375de0348b7f626adebc - jpountz 
- 2018-06-18 16:55:14]
at 
org.apache.solr.client.solrj.impl.SolrClientNodeStateProvider$ClientSnitchCtx.invoke(SolrClientNodeStateProvider.java:292)
 ~[solr-solrj-7.4.0.jar:7.4.0 9060ac689c270b02143f375de0348b7f626adebc - 
jpountz - 2018-06-18 16:55:14]
at 
org.apache.solr.client.solrj.impl.SolrClientNodeStateProvider.fetchMetrics(SolrClientNodeStateProvider.java:150)
 ~[solr-solrj-7.4.0.jar:7.4.0 9060ac689c270b02143f375de0348b7f626adebc - 
jpountz - 2018-06-18 16:55:14]
at 
org.apache.solr.client.solrj.impl.SolrClientNodeStateProvider.getReplicaInfo(SolrClientNodeStateProvider.java:131)
 ~[solr-solrj-7.4.0.jar:7.4.0 9060ac689c270b02143f375de0348b7f626adebc - 
jpountz - 2018-06-18 16:55:14]
at 
org.apache.solr.handler.admin.MetricsHistoryHandler.collectGlobalMetrics(MetricsHistoryHandler.java:478)
 ~[solr-core-7.4.0.jar:7.4.0 9060ac689c270b02143f375de0348b7f626adebc - jpountz 
- 2018-06-18 16:55:13]
at 
org.apache.solr.handler.admin.MetricsHistoryHandler.collectMetrics(MetricsHistoryHandler.java:368)
 ~[solr-core-7.4.0.jar:7.4.0 9060ac689c270b02143f375de0348b7f626adebc - jpountz 
- 2018-06-18 16:55:13]
at 
org.apache.solr.handler.admin.MetricsHistoryHandler.lambda$new$0(MetricsHistoryHandler.java:230)
 ~[solr-core-7.4.0.jar:7.4.0 9060ac689c270b02143f375de0348b7f626adebc - jpountz 
- 2018-06-18 16:55:13]
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
[?:1.8.0_181]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) 
[?:1.8.0_181]
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
 [?:1.8.0_181]
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
 [?:1.8.0_181]
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 
[?:1.8.0_181]
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 
[?:1.8.0_181]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_181]
2018-12-21 19:44:46.518 INFO  (qtp817348612-178) [