Hi Daniel,
thanks for the update. I have a strange situation with the included elasticsearch server after the update to 7.0.8:
Here are my observations:
1) elasticsearch started with seafile = slow and no search
if I start seafile via systemctl there are the following errors in the elasticsearch.log:
[2019-08-26T11:43:37,326][INFO ][o.e.n.Node ] initializing …
[2019-08-26T11:43:38,331][ERROR][o.e.b.Bootstrap ] Exception
java.lang.IllegalStateException: failed to obtain node locks, tried [[/home/seafile/pro-data/search/data/elasticsearch]] with lock id [0]; maybe these locations are not writable or multiple nodes were started without increasing [node.max_local_storage_nodes] (was [1])?
at org.elasticsearch.env.NodeEnvironment.(NodeEnvironment.java:265) ~[elasticsearch-5.6.13.jar:5.6.13]
at org.elasticsearch.node.Node.(Node.java:265) ~[elasticsearch-5.6.13.jar:5.6.13]
Also the cpu and memory usage is near 100% and seafile is responding very slowly.
2) seafile without file indexing = fast but no search
If I disable INDEX FILE in the seafevents.conf seafile is running like it should. Except that the search field is still visible but does not delivery and results.
In 6.x the search field disappered if I dissabled the file indexing. It seems this is not the case in 7.0.x., right?
3) elasticsearch started manually = search but no seafile
if I stop seafile and seahub and start the elasticsearch server manually I can update the search index without problems. Seafile is not running.
seafile@…:~/seafile-pro-server-7.0.8/pro/elasticsearch/bin$ ./elasticsearch
[2019-08-26T11:41:17,316][INFO ][o.e.n.Node ] [lCLpIG3] starting …
[2019-08-26T11:41:18,631][INFO ][o.e.t.TransportService ] [lCLpIG3] publish_address {127.0.0.1:9300}, bound_addresses {[::1]:9300}, {127.0.0.1:9300}seafile@…:~/seafile-pro-server-7.0.8/pro$ ./pro.py search --update
Index updated, statistic report:08/26/2019 11:42:30 [INFO] seafes:165 start_index_local: [commit read] 11
08/26/2019 11:42:30 [INFO] seafes:166 start_index_local: [dir read] 11
08/26/2019 11:42:30 [INFO] seafes:167 start_index_local: [file read] 11
08/26/2019 11:42:30 [INFO] seafes:168 start_index_local: [block read] 11
here is the relevant part of my seafevents.conf
[INDEX FILES]
enabled = true
interval = 10m
highlight = fvh
index_office_pdf = true
Can anybody confirm this behaviour?
Best regards
Christoph