# ES 0.90.3 with MongoDB river throws NoShardAvailableActionException

**URL:** <https://discuss.elastic.co/t/es-0-90-3-with-mongodb-river-throws-noshardavailableactionexception/13540>\
**Category:** Elasticsearch\
**Created:** [September 10, 2013, 2:37pm UTC](https://discuss.elastic.co/t/es-0-90-3-with-mongodb-river-throws-noshardavailableactionexception/13540 "2013-09-10T14:37:51Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Richard\_Louapre](https://avatars.discourse-cdn.com/v4/letter/r/e19adc/32.png) [@Richard\_Louapre](https://discuss.elastic.co/u/Richard_Louapre)\
**Post date:** [September 10, 2013, 2:37pm UTC](https://discuss.elastic.co/t/es-0-90-3-with-mongodb-river-throws-noshardavailableactionexception/13540/1 "2013-09-10T14:37:51Z")

</div>

With ES 0.90.3 when a MongoDB river setting is added there are a series of  
NoShardAvailableActionException exception thrown (see log file attached).

The same version of MongoDB river with ES 0.90.2 does not thrown any  
exceptions.

Any advice on how about solve this issue?

Thanks,  
Richard.

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [September 10, 2013, 2:40pm UTC](https://discuss.elastic.co/t/es-0-90-3-with-mongodb-river-throws-noshardavailableactionexception/13540/2 "2013-09-10T14:40:15Z")

</div>

I saw some bw compatibility issues while working on other plugins.

Did you try to update your mongodb river project to 0.90.3 and see if everything is compiling fine?

--  
David Pilato | Technical Advocate | [Elasticsearch.com](http://Elasticsearch.com)  
@dadoonet | @elasticsearchfr | @scrutmydocs

Le 10 sept. 2013 à 16:37, Richard Louapre [richard.louapre@gmail.com](mailto:richard.louapre@gmail.com) a écrit :

> With ES 0.90.3 when a MongoDB river setting is added there are a series of NoShardAvailableActionException exception thrown (see log file attached).
> 
> The same version of MongoDB river with ES 0.90.2 does not thrown any exceptions.
> 
> Any advice on how about solve this issue?
> 
> Thanks,  
> Richard.
> 
> --  
> You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).  
> \<elasticsearch.log\>

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Richard\_Louapre](https://avatars.discourse-cdn.com/v4/letter/r/e19adc/32.png) [@Richard\_Louapre](https://discuss.elastic.co/u/Richard_Louapre)\
**Post date:** [September 10, 2013, 3:17pm UTC](https://discuss.elastic.co/t/es-0-90-3-with-mongodb-river-throws-noshardavailableactionexception/13540/3 "2013-09-10T15:17:10Z")

</div>

The plugin compiles and all uni test are successful.

BTW the plugin still works fine with ES 0.90.3 but I'd like to get rid off  
the exceptions.

On Tuesday, September 10, 2013 10:40:15 AM UTC-4, David Pilato wrote:

> I saw some bw compatibility issues while working on other plugins.
> 
> Did you try to update your mongodb river project to 0.90.3 and see if  
> everything is compiling fine?
> 
> --  
> _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com)_  
> @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr[https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr)  
> | @scrutmydocs [https://twitter.com/scrutmydocs](https://twitter.com/scrutmydocs)
> 
> Le 10 sept. 2013 à 16:37, Richard Louapre \<[richard...@gmail.com](mailto:richard...@gmail.com)\<javascript:\>\>  
> a écrit :
> 
> With ES 0.90.3 when a MongoDB river setting is added there are a series of  
> NoShardAvailableActionException exception thrown (see log file attached).
> 
> The same version of MongoDB river with ES 0.90.2 does not thrown any  
> exceptions.
> 
> Any advice on how about solve this issue?
> 
> Thanks,  
> Richard.
> 
> --  
> You received this message because you are subscribed to the Google Groups  
> "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send an  
> email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \<javascript:\>.  
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).  
> \<elasticsearch.log\>

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 2:17am UTC](https://discuss.elastic.co/t/es-0-90-3-with-mongodb-river-throws-noshardavailableactionexception/13540/4 "2017-07-06T02:17:16Z")

</div>

Closed on July 6, 2017, 2:17am UTC


