-
Notifications
You must be signed in to change notification settings - Fork 51
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
11c3965
commit c11986e
Showing
1 changed file
with
3 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
c11986e
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hmm in my file the insert is on line 265 and 266 not from 268is that an issue?
Anyhow, I rerun it with the inserted lines.
c11986e
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, don't worry about that small shift with the line number
c11986e
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it took longer, but died again.
c11986e
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, I just saw that you only allocate 512Mo of memory to the solr servlet
I would advice to try at least with 2Go
Thanks anyway for that report, this should slightly lower the needed memory and I will still investigate the issue with some Jpeg and this should fix
c11986e
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i just came to the same idea:
~/solr/solr-6.2.1/bin$ ./solr start -m 2g
but still:
i check your next thing
With the other patch it worked.
The question is because it already went that far as it were, or not:
c11986e
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, it seems that you have some apk (android) file in your trashbin.
When you're deleting a file in NC, you're loosing the mimetype (from the database, fileinfo will return application/octet-stream).
So, nextant will index your file from the trashbin whatever its content. And when Tika (Solr) encounter some Java (or Android, in our case), it will try to read it using an external source highlighter (which is not installed on your box):
http://freecode.com/projects/jhighlight
The other patch will check differently the mimetype if it is a deleted file. Meaning that your apk will not be indexed.
c11986e
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes i am backuping my android devices via titanium backup to my nc.
Thanks for your quick fixes :)