SCRIPT_IMPORT_FAILED

[Philmod]

Hey,

The driver stopped working 2 weeks ago, and wouldn't restart:

{
_index: _river
_type: storify_stories
_id: _riverstatus
_version: 67536
_score: 1
_source: {
mongodb: {
status: SCRIPT_IMPORT_FAILED
}
}
}

{
_index: _river
_type: storify_stories
_id: storify_production.stories
_version: 875136
_score: 1
_source: {
mongodb: {
_last_ts: { "$ts" : 1395366882 , "$inc" : 287}
}
}
}

1. Any reason the script stopped working at some point and couldn't be reloaded?
2. How to restart it now?
3. Is there a way to monitor it better so I know when something goes wrong?

Best, Philmod

[richardwilly98]

Hi,

SCRIPT_IMPORT_FAILED indicates something went wrong when applying script filter you might found more details about the issue in ES log file.

The best way to restart indexing would be to reindex all data.

[Philmod]

Hey,

I haven't found anything in the logs.

I re-imported the data successfully. So I don't understand why the script failed at some point!?

Thanks, Philmod

On Monday, April 7, 2014, Richard [email protected] wrote:

Hi,

SCRIPT_IMPORT_FAILED indicates something went wrong when applying script filter you might found more details about the issue in ES log file.

The best way to restart indexing would be to reindex all data.

Reply to this email directly or view it on GitHubhttps://github.com/richardwilly98/elasticsearch-river-mongodb/issues/247#issuecomment-39815290 .

Philippe Modard 415-722-1245 [email protected] [email protected] twitter.com/philmod re.vu/philippemodard www.linkedin.com/in/philippemodard IBAN BE70 0639 3284 8025 - BIC: GKCCBEBB

[Philmod]

I have this issue when I restart elasticsearch.

Any way to fix that? (I can't really reimport the data each time, there are > 3 millions elements)

Thanks, Philmod

[Philmod]

@richardwilly98 The way to restart the process is:

1. Delete the _riverstatus curl -XDELETE 'http://localhost:9200/_river/storify_stories/_riverstatus'
2. Restart elasticsearch

I'm not a Java guy, but I think it might be wrong to set the status forever there.

What do you think?

EDIT: The river is working well now after restart, but I'm seeing the status SCRIPT_IMPORT_FAILED back in the _river index. So next time elasticsearch will restart, the river will be blocked again I guess.

[richardwilly98]

You should delete the index and the river then create it.

[Philmod]

@richardwilly98 Each time ES is restarted??

[ivpusic]

I am having the same problems, and I really don't like idea of recreating index each time after river is stopped working. Restarting server each time seems to me like good-enough solution during development, but not in production.

[Philmod]

+1

[nai0om]

still facing this problem in 2.0.1

[wajda]

Have the same issue. Please help.

[wajda]

Ok, found the cause in logs. It would be helpful to also store the last error message besides the "SCRIPT_IMPORT_FAILED" in river status. Thanks