Hi Elias,
thanks for reporting back -- glad to hear you got there in the end!
It might be useful to note that in your particular case, just
running index-discovery without any additional flags might have
helped. When run without any flags, it finds items that "need" a
reindex (ie, those that are eligible for indexing but don't exist in
the index at all, or where the last modified date in the db is more
recent than the last indexed field in the Solr index) and reindexes
only those. That's assuming your tomcat memory problems came from
the number of items to be processed in a full index (so every
partial index might have gotten a bit further through the indexing
before running out of memory).
cheers,
Andrea
On 18/03/16 08:34, Elias Tzoc wrote:
Thanks a lot Andrea,
The curl lines were useful for troubleshooting ... at the
end, it was a tomcat memory problem, which prevented the
index-discovery process to complete.
Elias
On Wednesday, March 16, 2016 at 4:53:29 PM UTC-4, Andrea Schweer
wrote:
Hi Elias,
On 17/03/16 04:40, Elias Tzoc wrote:
Thanks for the reply ... I just tried that
query and the missing items are set to "t" or true and
every other field in the item table looks normal. I've
also run index-discovery with -b -c -f -o then restarted
tomcat and nothing has worked so far ... it must be a
discovery solr problem somewhere, any suggestions will
be appreciated!
You could check whether these items are indexed in Solr, by
querying Solr directly. Solr is locked down to localhost, so
you'll have to do this on the machine that DSpace is running
on. If 123456789/123 is the handle of one of your affected
items, run eg
curl
' http://localhost:8080/solr/search/select?q=handle:123456789/123&rows=0&indent=true'
the result should include
<result name="response" numFound=" 1" start="0">
to indicate that the item is indexed. If you get
numFound="0", the item isn't indexed.
You could also run
curl
' http://localhost:8080/solr/search/select?q=handle:123456789/123&rows=1&fl=read,discoverable&indent=true'
to check what user/s can find this item via Discovery
(assuming you have access rights awareness turned on for
Discovery -- that's the default). You're looking for a
response like this:
<arr name="read">
<str>g0</str>
</arr>
<str name="discoverable">true</str> </doc>
g0 means the group with id 0 (= anyone) can
read/find this item. It's ok if there are additional values
listed besides g0. If g0 isn't included in the "read"
values, double-check the item's authorisation policies and
make sure the Anonymous group has READ permission on the
item. (Edit item -> Authorisation policies in XMLUI).
The "discoverable" value should match what's in the
database.
If your items are indexed in Discovery, with read for g0,
but are still not showing up when you search -- I'd
personally try clearing the cocoon cache (assuming you're
using XMLUI), then try another search.
If your items aren't indexed in Discovery, look for error
messages in dspace.log while you're running index-discovery
-- it could be that there are non-valid-for-XML characters
in the metadata (or extracted fulltext) for those items.
That would stop them from being indexed, but this should
also be logged.
cheers,
Andrea
--
Dr Andrea Schweer
Lead Software Developer, ITS Information Systems
The University of Waikato, Hamilton, New Zealand
+64-7-837 9120
--
You received this message because you are subscribed to the Google
Groups "DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.
--
Dr Andrea Schweer
Lead Software Developer, ITS Information Systems
The University of Waikato, Hamilton, New Zealand
+64-7-837 9120
--
You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.
|
