After upgrading to 5.26 I enabled Bleve and set it to index. After this it seems as though shell commands via mattermost no longer function.
For example, if I execute a simple:
$ /opt/mattermost/bin/mattermost channel list TEAM_NAME
with Bleve enabled, I just get:
{"level":"info","msg":"Server is initializing..."}
2020-08-16T20:30:41.846Z info app/web_hub.go:83 Starting websocket hubs {"number_of_hubs": 2}
2020-08-16T20:30:41.847Z info bleveengine/bleve.go:157 EXPERIMENTAL: Starting Bleve
^C
After I disable Bleve again within the System Console shell commands work again just fine.
I also believe Bleve is not actually indexing when turned on because it stays at 0% indexed on a relatively small Mattermost installation after even two hours of it just sitting there.
1 Like
That’s really interesting @amy.blais - thanks for pointing that out. Hmm. Well, in addition to this, I’m getting the following with the Bleve hang:
Well good news, but such an insanely long time:
Still going:
I suppose it’s just a long waiting game. Clearly this somehow this needs to give better feedback.
Known issue regarding starting such a command:
- Enabling Bleve search engine makes the Command Line Interface (CLI) mutually exclusive with the running server. This issue does not apply when using mmctl Command Line Tool.
You can use the mmctl local mode to run commands locally with Bleve enabled.
As for the indexing progress, is there any information in the server logs related to Bleve or any error log?
The problem when using mmctl is that it appears to be feature incomplete. For example, moving channels between teams seems impossible at present.
It finally finished after 2191 minutes:
Maybe not, it appears to still be going:
Finally finished:
@amy.blais we clearly need some better status updates due to these potentially insanely long run times…
