Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Solr: empty dataverses when content expected #1439

Closed
pdurbin opened this issue Feb 6, 2015 · 2 comments
Closed

Solr: empty dataverses when content expected #1439

pdurbin opened this issue Feb 6, 2015 · 2 comments

Comments

@pdurbin
Copy link
Member

pdurbin commented Feb 6, 2015

In 1eb10af I documented a workaround for a problem I encountered locally wherein I was seeing what looked like empty dataverses when I expected to see content.

This is what I wrote in that commit (which now appears at http://guides.dataverse.org/en/latest/installation/installation-main.html#solr-configuration ):

If WARN org.eclipse.jetty.http.HttpParser – HttpParser Full for /127.0.0.1:8983 appears in the Solr log, adding <Set name="requestHeaderSize">8192</Set> (or a higher number of bytes) to Solr's jetty.xml in the section matching the XPath expression //Call[@name='addConnector']/Arg/New[@class='org.eclipse.jetty.server.bio.SocketConnector'] may resolve the issue. See also https://support.lucidworks.com/hc/en-us/articles/201424796-Error-when-submitting-large-query-strings-

I could also add this is what you see in the Glassfish server.log: "Search Syntax Error: Expected content type application/octet-stream but got ."

As https://support.lucidworks.com/hc/en-us/articles/201424796-Error-when-submitting-large-query-strings- explains, the change to jetty.xml Solr config file is one fix. Another may be switching from GET to POST.

I'm not sure what a user should see when a system error like this happens. Showing the same message as you see for an empty dataverse doesn't seem right. This is sort of status page ( #131 ) or Solr down ( #1042 ) territory.

@pdurbin pdurbin added this to the In Review - Dataverse 4.0 milestone Feb 6, 2015
@scolapasta scolapasta modified the milestones: Beta 15 - Dataverse 4.0, In Review - Dataverse 4.0, Post 4.0 Feb 11, 2015
@scolapasta scolapasta modified the milestones: In Review - Long Term, In Review - Short Term May 8, 2015
@pdurbin
Copy link
Member Author

pdurbin commented Sep 9, 2015

Since the related issue #2311 got assigned to the 4.2 milestone, I'm going to put this one in 4.2 as well and put it in QA. The question is if the explanation about the jetty.xml file at http://guides.dataverse.org/en/4.2/installation/installation-main.html#solr-configuration is good enough. I also added a note to the Google doc linked from #2321.

@pdurbin pdurbin modified the milestones: 4.2, In Review Sep 9, 2015
@pdurbin pdurbin removed their assignment Sep 9, 2015
@kcondon
Copy link
Contributor

kcondon commented Oct 1, 2015

Probably fine. Not sure everyone would immediately be able to parse an xpath expression but at least the accompanying link gives a real life example. The value 8192 is too small for our production config once MyData was added so perhaps this value should be changed to something like Raman suggested in 2311? Anyway, seems ok, closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants