# What to do with ES?

**URL:** <https://discuss.elastic.co/t/what-to-do-with-es/8607>\
**Category:** Elasticsearch\
**Created:** [August 2, 2012, 1:10pm UTC](https://discuss.elastic.co/t/what-to-do-with-es/8607 "2012-08-02T13:10:35Z")\
**Posts on this page:** 18\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bernd\_Fehling](https://avatars.discourse-cdn.com/v4/letter/b/c2a13f/32.png) [@Bernd\_Fehling](https://discuss.elastic.co/u/Bernd_Fehling)\
**Post date:** [August 2, 2012, 1:10pm UTC](https://discuss.elastic.co/t/what-to-do-with-es/8607/1 "2012-08-02T13:10:35Z")

</div>

Well, after having ES installed and set up 2 nodes on one machine for  
testing I tried to get some content into ES.  
The results are very bad. After 2 days not a single useful doc with an  
acceptable mapping.  
Best I could get was:  
org.elasticsearch.common.netty.handler.codec.frame.TooLongFrameException:  
transport content length received [1.2gb] exceeded [914.1mb]  
at  
org.elasticsearch.transport.netty.MessageChannelHandler.callDecode(MessageChannelHandler.java:143)  
at  
org.elasticsearch.transport.netty.MessageChannelHandler.messageReceived(MessageChannelHandler.java:103)  
at  
org.elasticsearch.common.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:75)  
at  
org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:563)  
...

I don't know how ES comes to 1.2gb or even 914.1mb, because I only tried to  
load about 68mb (112 files) with fsriver.  
My current idea is that ES devides my 68mb by its version number 0.198 but  
this would make 343mb. (You see I havent't lost my humor...)  
Is there ANY useful example somewhere, which really explains step by step  
how to start with index, mapping, loading, ...

Bernd

---

<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:** [August 2, 2012, 1:15pm UTC](https://discuss.elastic.co/t/what-to-do-with-es/8607/2 "2012-08-02T13:15:45Z")

</div>

Hum. As the filesystem river author, I feel guilty... I mean that there is probably something wrong with the river.  
I will track it down. Could you open an issue for that in fsriver project?

David 😉  
Twitter : @dadoonet / @elasticsearchfr

Le 2 août 2012 à 15:10, Bernd Fehling [bernd.fehling@googlemail.com](mailto:bernd.fehling@googlemail.com) a écrit :

> Well, after having ES installed and set up 2 nodes on one machine for testing I tried to get some content into ES.  
> The results are very bad. After 2 days not a single useful doc with an acceptable mapping.  
> Best I could get was:  
> org.elasticsearch.common.netty.handler.codec.frame.TooLongFrameException: transport content length received [1.2gb] exceeded [914.1mb]  
> at org.elasticsearch.transport.netty.MessageChannelHandler.callDecode(MessageChannelHandler.java:143)  
> at org.elasticsearch.transport.netty.MessageChannelHandler.messageReceived(MessageChannelHandler.java:103)  
> at org.elasticsearch.common.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:75)  
> at org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:563)  
> ...
> 
> I don't know how ES comes to 1.2gb or even 914.1mb, because I only tried to load about 68mb (112 files) with fsriver.  
> My current idea is that ES devides my 68mb by its version number 0.198 but this would make 343mb. (You see I havent't lost my humor...)  
> Is there ANY useful example somewhere, which really explains step by step how to start with index, mapping, loading, ...
> 
> Bernd

---

<div class="post-metadata">

**Author:** ![Bernd\_Fehling](https://avatars.discourse-cdn.com/v4/letter/b/c2a13f/32.png) [@Bernd\_Fehling](https://discuss.elastic.co/u/Bernd_Fehling)\
**Post date:** [August 2, 2012, 1:30pm UTC](https://discuss.elastic.co/t/what-to-do-with-es/8607/3 "2012-08-02T13:30:28Z")

</div>

Hi David,

can do that but are you sure it's the fsriver?

Bernd

Am Donnerstag, 2. August 2012 15:15:45 UTC+2 schrieb David Pilato:

> Hum. As the filesystem river author, I feel guilty... I mean that there is  
> probably something wrong with the river.  
> I will track it down. Could you open an issue for that in fsriver project?
> 
> David 😉  
> Twitter : @dadoonet / @elasticsearchfr

---

<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:** [August 2, 2012, 1:37pm UTC](https://discuss.elastic.co/t/what-to-do-with-es/8607/4 "2012-08-02T13:37:55Z")

</div>

Almost. I mean that fsriver is using a bulk to commit changes in ES.  
You can start to modify bulk\_size to 10 to see if it helps.

David 😉  
Twitter : @dadoonet / @elasticsearchfr

Le 2 août 2012 à 15:30, Bernd Fehling [bernd.fehling@googlemail.com](mailto:bernd.fehling@googlemail.com) a écrit :

> Hi David,
> 
> can do that but are you sure it's the fsriver?
> 
> Bernd
> 
> Am Donnerstag, 2. August 2012 15:15:45 UTC+2 schrieb David Pilato:  
> Hum. As the filesystem river author, I feel guilty... I mean that there is probably something wrong with the river.  
> I will track it down. Could you open an issue for that in fsriver project?
> 
> David 😉  
> Twitter : @dadoonet / @elasticsearchfr

---

<div class="post-metadata">

**Author:** ![Bernd\_Fehling](https://avatars.discourse-cdn.com/v4/letter/b/c2a13f/32.png) [@Bernd\_Fehling](https://discuss.elastic.co/u/Bernd_Fehling)\
**Post date:** [August 2, 2012, 1:54pm UTC](https://discuss.elastic.co/t/what-to-do-with-es/8607/5 "2012-08-02T13:54:15Z")

</div>

Just tried with bulk\_size of 10, no changes.  
May be something else with my data.  
Have the JSON records to be serialized instead of pretty printed?

Bernd

Am Donnerstag, 2. August 2012 15:37:55 UTC+2 schrieb David Pilato:

> Almost. I mean that fsriver is using a bulk to commit changes in ES.  
> You can start to modify bulk\_size to 10 to see if it helps.
> 
> David 😉  
> Twitter : @dadoonet / @elasticsearchfr

---

<div class="post-metadata">

**Author:** ![Clinton\_Gormley](https://avatars.discourse-cdn.com/v4/letter/c/50afbb/32.png) [@Clinton\_Gormley](https://discuss.elastic.co/u/Clinton_Gormley)\
**Post date:** [August 2, 2012, 2:00pm UTC](https://discuss.elastic.co/t/what-to-do-with-es/8607/6 "2012-08-02T14:00:39Z")

</div>

On Thu, 2012-08-02 at 06:10 -0700, Bernd Fehling wrote:

> Well, after having ES installed and set up 2 nodes on one machine for  
> testing I tried to get some content into ES.  
> The results are very bad. After 2 days not a single useful doc with an  
> acceptable mapping.  
> Best I could get was:  
> org.elasticsearch.common.netty.handler.codec.frame.TooLongFrameException: transport content length received [1.2gb] exceeded [914.1mb]  
> at  
> org.elasticsearch.transport.netty.MessageChannelHandler.callDecode(MessageChannelHandler.java:143)  
> at  
> org.elasticsearch.transport.netty.MessageChannelHandler.messageReceived(MessageChannelHandler.java:103)  
> at  
> org.elasticsearch.common.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:75)  
> at  
> org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:563)  
> ...
> 
> I don't know how ES comes to 1.2gb or even 914.1mb, because I only  
> tried to load about 68mb (112 files) with fsriver.

You're connecting to port 9300 with http instead of to port 9200.

You'll get the same error message with:

```
curl http://localhost:9300

```

clint

---

<div class="post-metadata">

**Author:** ![Bernd\_Fehling](https://avatars.discourse-cdn.com/v4/letter/b/c2a13f/32.png) [@Bernd\_Fehling](https://discuss.elastic.co/u/Bernd_Fehling)\
**Post date:** [August 2, 2012, 2:07pm UTC](https://discuss.elastic.co/t/what-to-do-with-es/8607/7 "2012-08-02T14:07:26Z")

</div>

Ahhh, thats it. It says:  
[transport] [node\_1] bound\_address  
{inet[/192.168.70.23:9300]  
[http] [node\_1] bound\_address  
{inet[/192.168.70.23:9200]

So I will try with port 9200, thanks.

Bernd

You're connecting to port 9300 with http instead of to port 9200.

> You'll get the same error message with:
> 
> ```
> curl http://localhost:9300 
> 
> ```
> 
> clint

---

<div class="post-metadata">

**Author:** ![Bernd\_Fehling](https://avatars.discourse-cdn.com/v4/letter/b/c2a13f/32.png) [@Bernd\_Fehling](https://discuss.elastic.co/u/Bernd_Fehling)\
**Post date:** [August 2, 2012, 2:18pm UTC](https://discuss.elastic.co/t/what-to-do-with-es/8607/8 "2012-08-02T14:18:06Z")

</div>

OK, one step further.

repsone is  
{"ok":true,"\_index":"\_river","\_type":"base","\_id":"\_meta","\_version":1}  
what ever that means???

But also:  
[2012-08-02 16:09:26,694][INFO][cluster.metadata] [node\_1]  
[\_river] creating index, cause [auto(index api)], shards [5]/[1], mappings  
  
[2012-08-02 16:09:27,028][INFO][cluster.metadata] [node\_1]  
[\_river] update\_mapping [base] (dynamic)  
[2012-08-02 16:09:27,068][WARN][river] [node\_1] failed  
to create river [fs][base]  
org.elasticsearch.common.settings.NoClassSettingsException: Failed to load  
class with value [fs]  
at  
org.elasticsearch.river.RiverModule.loadTypeModule(RiverModule.java:86)  
at  
org.elasticsearch.river.RiverModule.spawnModules(RiverModule.java:57)  
at  
org.elasticsearch.common.inject.ModulesBuilder.add(ModulesBuilder.java:44)  
at  
org.elasticsearch.river.RiversService.createRiver(RiversService.java:135)  
at  
org.elasticsearch.river.RiversService$ApplyRivers$2.onResponse(RiversService.java:270)  
at  
org.elasticsearch.river.RiversService$ApplyRivers$2.onResponse(RiversService.java:264)  
at  
org.elasticsearch.action.support.TransportAction$ThreadedActionListener$1.run(TransportAction.java:86)  
at  
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)  
at  
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)  
at java.lang.Thread.run(Thread.java:662)  
Caused by: java.lang.ClassNotFoundException: fs  
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)  
at java.security.AccessController.doPrivileged(Native Method)  
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)  
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)

What class "fs" is he missing?

curl -XPUT '192.168.12.37:9200/\_river/base/\_meta' -d '{

> "type": "fs",  
> "fs": {  
> "name": "OAI JSON",  
> "url": "/srv/www/solr/DATA/OAI\_JSON",  
> "update\_rate": 36000000,  
> "includes": "\*.json"  
> },  
> "index": {  
> "index": "base",  
> "type": "base",  
> "bulk\_size": 10  
> }  
> }'

It is nearly a cut&paste from the fsriver GitHub example.

Very strange...

Bernd

Am Donnerstag, 2. August 2012 16:07:26 UTC+2 schrieb Bernd Fehling:

> Ahhh, thats it. It says:  
> [transport] [node\_1] bound\_address {inet[/  
> 192.168.70.23:9300]  
> [http] [node\_1] bound\_address {inet[/  
> 192.168.70.23:9200]
> 
> So I will try with port 9200, thanks.
> 
> Bernd
> 
> You're connecting to port 9300 with http instead of to port 9200.
> 
> > You'll get the same error message with:
> > 
> > ```
> > curl http://localhost:9300 
> > 
> > ```
> > 
> > clint

---

<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:** [August 2, 2012, 2:40pm UTC](https://discuss.elastic.co/t/what-to-do-with-es/8607/9 "2012-08-02T14:40:04Z")

</div>

Thanks Clint.  
I don't feel guilty anymore! 😉

fs is missing means that the fs river plugin is not installed.

When you start ES you should see it in the plugins list in logs.  
If not, bin/plugin -install as mentionned in the fsriver doc.

David 😉  
Twitter : @dadoonet / @elasticsearchfr

Le 2 août 2012 à 16:18, Bernd Fehling [bernd.fehling@googlemail.com](mailto:bernd.fehling@googlemail.com) a écrit :

> OK, one step further.
> 
> repsone is {"ok":true,"\_index":"\_river","\_type":"base","\_id":"\_meta","\_version":1}  
> what ever that means???
> 
> But also:  
> [2012-08-02 16:09:26,694][INFO][cluster.metadata] [node\_1] [\_river] creating index, cause [auto(index api)], shards [5]/[1], mappings   
> [2012-08-02 16:09:27,028][INFO][cluster.metadata] [node\_1] [\_river] update\_mapping [base] (dynamic)  
> [2012-08-02 16:09:27,068][WARN][river] [node\_1] failed to create river [fs][base]  
> org.elasticsearch.common.settings.NoClassSettingsException: Failed to load class with value [fs]  
> at org.elasticsearch.river.RiverModule.loadTypeModule(RiverModule.java:86)  
> at org.elasticsearch.river.RiverModule.spawnModules(RiverModule.java:57)  
> at org.elasticsearch.common.inject.ModulesBuilder.add(ModulesBuilder.java:44)  
> at org.elasticsearch.river.RiversService.createRiver(RiversService.java:135)  
> at org.elasticsearch.river.RiversService$ApplyRivers$2.onResponse(RiversService.java:270)  
> at org.elasticsearch.river.RiversService$ApplyRivers$2.onResponse(RiversService.java:264)  
> at org.elasticsearch.action.support.TransportAction$ThreadedActionListener$1.run(TransportAction.java:86)  
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)  
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)  
> at java.lang.Thread.run(Thread.java:662)  
> Caused by: java.lang.ClassNotFoundException: fs  
> at java.net.URLClassLoader$1.run(URLClassLoader.java:202)  
> at java.security.AccessController.doPrivileged(Native Method)  
> at java.net.URLClassLoader.findClass(URLClassLoader.java:190)  
> at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
> 
> What class "fs" is he missing?
> 
> curl -XPUT '192.168.12.37:9200/\_river/base/\_meta' -d '{
> 
> > "type": "fs",  
> > "fs": {  
> > "name": "OAI JSON",  
> > "url": "/srv/www/solr/DATA/OAI\_JSON",  
> > "update\_rate": 36000000,  
> > "includes": "\*.json"  
> > },  
> > "index": {  
> > "index": "base",  
> > "type": "base",  
> > "bulk\_size": 10  
> > }  
> > }'
> 
> It is nearly a cut&paste from the fsriver GitHub example.
> 
> Very strange...
> 
> Bernd
> 
> Am Donnerstag, 2. August 2012 16:07:26 UTC+2 schrieb Bernd Fehling:  
> Ahhh, thats it. It says:  
> [transport] [node\_1] bound\_address {inet[/192.168.70.23:9300]  
> [http] [node\_1] bound\_address {inet[/192.168.70.23:9200]
> 
> So I will try with port 9200, thanks.
> 
> Bernd
> 
> You're connecting to port 9300 with http instead of to port 9200.
> 
> You'll get the same error message with:
> 
> ```
> curl http://localhost:9300 
> 
> ```
> 
> clint

---

<div class="post-metadata">

**Author:** ![Vinicius\_Carvalho](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vinicius_carvalho/32/770_2.png) [@Vinicius\_Carvalho](https://discuss.elastic.co/u/Vinicius_Carvalho)\
**Post date:** [August 2, 2012, 3:36pm UTC](https://discuss.elastic.co/t/what-to-do-with-es/8607/10 "2012-08-02T15:36:54Z")

</div>

Out of curiosity, I had this error other day when I hit the wrong port  
using curl, I've freaked out for a few seconds, and then realized I hit the  
wrong port.

May I ask where does numbers come? 1.2gb exceed 914.1? Cuz I had the same  
doing a simple query on an index in a wrong port 🙂

Regards

On Thursday, August 2, 2012 9:10:35 AM UTC-4, Bernd Fehling wrote:

> Well, after having ES installed and set up 2 nodes on one machine for  
> testing I tried to get some content into ES.  
> The results are very bad. After 2 days not a single useful doc with an  
> acceptable mapping.  
> Best I could get was:  
> org.elasticsearch.common.netty.handler.codec.frame.TooLongFrameException:  
> transport content length received [1.2gb] exceeded [914.1mb]  
> at  
> org.elasticsearch.transport.netty.MessageChannelHandler.callDecode(MessageChannelHandler.java:143)  
> at  
> org.elasticsearch.transport.netty.MessageChannelHandler.messageReceived(MessageChannelHandler.java:103)  
> at  
> org.elasticsearch.common.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:75)  
> at  
> org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:563)  
> ...
> 
> I don't know how ES comes to 1.2gb or even 914.1mb, because I only tried  
> to load about 68mb (112 files) with fsriver.  
> My current idea is that ES devides my 68mb by its version number 0.198 but  
> this would make 343mb. (You see I havent't lost my humor...)  
> Is there ANY useful example somewhere, which really explains step by step  
> how to start with index, mapping, loading, ...
> 
> Bernd

---

<div class="post-metadata">

**Author:** ![Igor\_Motov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/igor_motov/32/45193_2.png) [@Igor\_Motov](https://discuss.elastic.co/u/Igor_Motov)\
**Post date:** [August 2, 2012, 10:12pm UTC](https://discuss.elastic.co/t/what-to-do-with-es/8607/11 "2012-08-02T22:12:23Z")

</div>

When you connect to a port using curl, curl sends HTTP requests that looks  
like this:

POST /my-index/my-type/1 HTTP/1.1  
User-Agent: curl/7.22.0 (x86\_64-apple-darwin1......

When Netty connector of elasticsearch that listens on port 9300 receives a  
request, it expects that the first 4 bytes of the request will contain the  
length of data frame that is about to follow.

So, the first 4 bytes that curl sends are 'P', 'O', 'S', 'T' or 0x50, 0x4F,  
0x53, 0x54. Netty treats these 4 bytes as a big endian  
integer 1,347,375,956 and figures out that it should expect  
approximately 1.2gb of data to follow. It then compares it to 90% of the  
max heap size, which is 914.1m if elasticsearch was started with default  
1GB of memory, figures that there is no way it can handle such a big  
request and bails out by throwing TooLongFrameException.

Igor

On Thursday, August 2, 2012 11:36:54 AM UTC-4, Vinicius Carvalho wrote:

> Out of curiosity, I had this error other day when I hit the wrong port  
> using curl, I've freaked out for a few seconds, and then realized I hit the  
> wrong port.
> 
> May I ask where does numbers come? 1.2gb exceed 914.1? Cuz I had the same  
> doing a simple query on an index in a wrong port 🙂
> 
> Regards
> 
> On Thursday, August 2, 2012 9:10:35 AM UTC-4, Bernd Fehling wrote:
> 
> > Well, after having ES installed and set up 2 nodes on one machine for  
> > testing I tried to get some content into ES.  
> > The results are very bad. After 2 days not a single useful doc with an  
> > acceptable mapping.  
> > Best I could get was:  
> > org.elasticsearch.common.netty.handler.codec.frame.TooLongFrameException:  
> > transport content length received [1.2gb] exceeded [914.1mb]  
> > at  
> > org.elasticsearch.transport.netty.MessageChannelHandler.callDecode(MessageChannelHandler.java:143)  
> > at  
> > org.elasticsearch.transport.netty.MessageChannelHandler.messageReceived(MessageChannelHandler.java:103)  
> > at  
> > org.elasticsearch.common.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:75)  
> > at  
> > org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:563)  
> > ...
> > 
> > I don't know how ES comes to 1.2gb or even 914.1mb, because I only tried  
> > to load about 68mb (112 files) with fsriver.  
> > My current idea is that ES devides my 68mb by its version number 0.198  
> > but this would make 343mb. (You see I havent't lost my humor...)  
> > Is there ANY useful example somewhere, which really explains step by step  
> > how to start with index, mapping, loading, ...
> > 
> > Bernd

---

<div class="post-metadata">

**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\
**Post date:** [August 2, 2012, 10:49pm UTC](https://discuss.elastic.co/t/what-to-do-with-es/8607/12 "2012-08-02T22:49:03Z")

</div>

Thanks, Igor, for tracking this down so thoroughly. I think it's time to  
send Shay a patch for the ES MessageChannelHandler, so the exception will  
no longer look so horrible if a HTTP connection is accidentally made to the  
9300 binary protocol port.

Best regards,

Jörg

On Friday, August 3, 2012 12:12:23 AM UTC+2, Igor Motov wrote:

> When you connect to a port using curl, curl sends HTTP requests that looks  
> like this:
> 
> POST /my-index/my-type/1 HTTP/1.1  
> User-Agent: curl/7.22.0 (x86\_64-apple-darwin1......
> 
> When Netty connector of elasticsearch that listens on port 9300 receives a  
> request, it expects that the first 4 bytes of the request will contain the  
> length of data frame that is about to follow.
> 
> So, the first 4 bytes that curl sends are 'P', 'O', 'S', 'T' or 0x50,  
> 0x4F, 0x53, 0x54. Netty treats these 4 bytes as a big endian  
> integer 1,347,375,956 and figures out that it should expect  
> approximately 1.2gb of data to follow. It then compares it to 90% of the  
> max heap size, which is 914.1m if elasticsearch was started with default  
> 1GB of memory, figures that there is no way it can handle such a big  
> request and bails out by throwing TooLongFrameException.
> 
> Igor
> 
> On Thursday, August 2, 2012 11:36:54 AM UTC-4, Vinicius Carvalho wrote:
> 
> > Out of curiosity, I had this error other day when I hit the wrong port  
> > using curl, I've freaked out for a few seconds, and then realized I hit the  
> > wrong port.
> > 
> > May I ask where does numbers come? 1.2gb exceed 914.1? Cuz I had the same  
> > doing a simple query on an index in a wrong port 🙂
> > 
> > Regards
> > 
> > On Thursday, August 2, 2012 9:10:35 AM UTC-4, Bernd Fehling wrote:
> > 
> > > Well, after having ES installed and set up 2 nodes on one machine for  
> > > testing I tried to get some content into ES.  
> > > The results are very bad. After 2 days not a single useful doc with an  
> > > acceptable mapping.  
> > > Best I could get was:  
> > > org.elasticsearch.common.netty.handler.codec.frame.TooLongFrameException:  
> > > transport content length received [1.2gb] exceeded [914.1mb]  
> > > at  
> > > org.elasticsearch.transport.netty.MessageChannelHandler.callDecode(MessageChannelHandler.java:143)  
> > > at  
> > > org.elasticsearch.transport.netty.MessageChannelHandler.messageReceived(MessageChannelHandler.java:103)  
> > > at  
> > > org.elasticsearch.common.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:75)  
> > > at  
> > > org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:563)  
> > > ...
> > > 
> > > I don't know how ES comes to 1.2gb or even 914.1mb, because I only tried  
> > > to load about 68mb (112 files) with fsriver.  
> > > My current idea is that ES devides my 68mb by its version number 0.198  
> > > but this would make 343mb. (You see I havent't lost my humor...)  
> > > Is there ANY useful example somewhere, which really explains step by  
> > > step how to start with index, mapping, loading, ...
> > > 
> > > Bernd

---

<div class="post-metadata">

**Author:** ![Bernd\_Fehling](https://avatars.discourse-cdn.com/v4/letter/b/c2a13f/32.png) [@Bernd\_Fehling](https://discuss.elastic.co/u/Bernd_Fehling)\
**Post date:** [August 6, 2012, 7:20am UTC](https://discuss.elastic.co/t/what-to-do-with-es/8607/13 "2012-08-06T07:20:06Z")

</div>

OK, having clearified the exception message while using the wrong port I  
still can't get any results.  
The fsriver README says:

bin\plugin -install dadoonet/fsriver

done that.

[INFO][plugins] [node\_1] loaded [], sites [bigdesk,  
fsriver, mapper-attachments, head, paramedic]

So why is it complaining about "fs" when using the example?  
I'm using nearly the same as from the example:

curl -XPUT 'localhost:9200/\_river/mydocs/\_meta' -d '{  
"type": "fs",  
"fs": {  
"name": "My tmp dir",  
"url": "/tmp",  
"update\_rate": 900000,  
"includes": "_.doc,_.pdf",  
"excludes": "resume"  
}  
}'

What does "\_river" mean?  
Where does "mydocs" stand for?  
What is the meaning of "\_meta"?  
What is "type" : "fs" ?  
what does "fs": {... mean?  
Where should I enter my index name?  
Where should I place my mapping?  
Do I have to enter the plugin name "fsriver" somewhere (but it is not in the example)?  
Why do I have a new index "\_river" after using the example?

Very, very strange...

Bernd

---

<div class="post-metadata">

**Author:** ![Bernd\_Fehling](https://avatars.discourse-cdn.com/v4/letter/b/c2a13f/32.png) [@Bernd\_Fehling](https://discuss.elastic.co/u/Bernd_Fehling)\
**Post date:** [August 6, 2012, 8:24am UTC](https://discuss.elastic.co/t/what-to-do-with-es/8607/14 "2012-08-06T08:24:24Z")

</div>

Now this is also very strange, after installing fsriver with:

bin\plugin -install dadoonet/fsriver

and restarting all nodes I get the info:  
[INFO][plugins] [node\_1] loaded [], sites [bigdesk,  
fsriver, mapper-attachments, head, paramedic]

So ES has found the new installed "fsriver" plugin.  
But there is nowhere something like fsriver.jar or fs.jar or any other new  
\*.jar  
Under plugins/fsriver/ directory are only \*.java source files, xml-files,  
pom.xml and other properties and text files located.

Bernd

---

<div class="post-metadata">

**Author:** ![Bernd\_Fehling](https://avatars.discourse-cdn.com/v4/letter/b/c2a13f/32.png) [@Bernd\_Fehling](https://discuss.elastic.co/u/Bernd_Fehling)\
**Post date:** [August 6, 2012, 8:58am UTC](https://discuss.elastic.co/t/what-to-do-with-es/8607/15 "2012-08-06T08:58:52Z")

</div>

Finally "fsriver" is running.  
If installing the plugin you MUST use the version number. If not, you are  
only getting the master sources.  
I thought by omitting the version number it would install the most recent  
version. WRONG!!!

---

<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:** [August 6, 2012, 9:13am UTC](https://discuss.elastic.co/t/what-to-do-with-es/8607/16 "2012-08-06T09:13:04Z")

</div>

Yes. That was in the README :

$ bin\plugin -install dadoonet/fsriver/0.0.2

David 😉  
Twitter : @dadoonet / @elasticsearchfr

Le 6 août 2012 à 10:58, Bernd Fehling [bernd.fehling@googlemail.com](mailto:bernd.fehling@googlemail.com) a écrit :

> Finally "fsriver" is running.  
> If installing the plugin you MUST use the version number. If not, you are only getting the master sources.  
> I thought by omitting the version number it would install the most recent version. WRONG!!!

---

<div class="post-metadata">

**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\
**Post date:** [August 7, 2012, 12:03am UTC](https://discuss.elastic.co/t/what-to-do-with-es/8607/17 "2012-08-07T00:03:16Z")

</div>

Just for the files, the patch is submitted here

> <https://github.com/elastic/elasticsearch/pull/2139>
>
> Hi kimchy,
> 
> I think it is useful to add a special wrong port handling to netty t…ransport, so people who accidentally connect with a HTTP client to port 9300 will receive a small diagnostic message.
> 
> Cheers,
> 
> Jörg

On Friday, August 3, 2012 12:49:03 AM UTC+2, Jörg Prante wrote:

> Thanks, Igor, for tracking this down so thoroughly. I think it's time to  
> send Shay a patch for the ES MessageChannelHandler, so the exception will  
> no longer look so horrible if a HTTP connection is accidentally made to the  
> 9300 binary protocol port.
> 
> > > >

---

<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, 3:17am UTC](https://discuss.elastic.co/t/what-to-do-with-es/8607/18 "2017-07-06T03:17:33Z")

</div>