at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:282)
at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:324)
at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:176)
at java.io.InputStreamReader.read(InputStreamReader.java:184)
at java.io.BufferedReader.fill(BufferedReader.java:153)
at java.io.BufferedReader.readLine(BufferedReader.java:316)
at java.io.BufferedReader.readLine(BufferedReader.java:379)
at
at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:282)****
at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:324)****
at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:176)****
at java.io.InputStreamReader.read(InputStreamReader.java:184)****
at java.io.BufferedReader.fill(BufferedReader.java:153)****
at java.io.BufferedReader.readLine(BufferedReader.java:316)****
at java.io.BufferedReader.readLine(BufferedReader.java:379)****
at
at sun.nio.ch.FileDispatcher.read0(Native Method)
at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:251)
at sun.nio.ch.IOUtil.read(IOUtil.java:218)
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:254)
at
at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:282)
at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:324)
at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:176)
at java.io.InputStreamReader.read(InputStreamReader.java:184)
at java.io.BufferedReader.fill(BufferedReader.java:153)
at java.io.BufferedReader.readLine(BufferedReader.java:316)
at java.io.BufferedReader.readLine(BufferedReader.java:379)
at
at sun.nio.ch.FileDispatcher.read0(Native Method)
at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:251)
at sun.nio.ch.IOUtil.read(IOUtil.java:218)
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:254)
at
at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:282)
at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:324)
at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:176)
at java.io.InputStreamReader.read(InputStreamReader.java:184)
at java.io.BufferedReader.fill(BufferedReader.java:153)
at java.io.BufferedReader.readLine(BufferedReader.java:316)
at java.io.BufferedReader.readLine(BufferedReader.java:379)
at
I don't see anything interesting there, strange... . Based on teh code, it
seems like the twitter4j library is being properly restarted and we try to
reconnet properly, I will try and recreate it...
On Thu, Apr 5, 2012 at 1:12 AM, David Pilato david@pilato.fr wrote:
Hi Shay,****
Sorry to nag. Could you give a look at this log file ?****
I have to restart my instance (or delete the river and recreate it) about
every two or three days.****
at sun.nio.ch.FileDispatcher.read0(Native Method)****
at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39)****
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:251)****
at sun.nio.ch.IOUtil.read(IOUtil.java:218)****
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:254)*
at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:282)****
at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:324)****
at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:176)****
at java.io.InputStreamReader.read(InputStreamReader.java:184)****
at java.io.BufferedReader.fill(BufferedReader.java:153)****
at java.io.BufferedReader.readLine(BufferedReader.java:316)****
at java.io.BufferedReader.readLine(BufferedReader.java:379)****
at
I have the same trouble with twitter river.
You can easy to repeat this bug if temporary disconnect your network.
After error in log:
... stream failure, restarting stream...
You can switch your network on, but twitter river can't turn back.
Could I restart the river without shutting down cluster?
I did not find any way to fix it.
So, I created a crontab script that look at logs and restart the node each time I see the error. The other node (2 nodes cluster) recreate the river and continue to fetch Twitter content.
I have the same trouble with twitter river.
You can easy to repeat this bug if temporary disconnect your network.
After error in log:
... stream failure, restarting stream...
You can switch your network on, but twitter river can't turn back.
Could I restart the river without shutting down cluster?
First to mention, I am not much into core elasticsearch code, but I do
quite a bit of custom modification on the plugins part to support my
business cases. My statement here might sound too novice. My apologies.
I had faced the same problem stated here in this thread while I built the
plugin directly using command as stated in link
I needed to modify the code of twitter river several times for custom
requirements, and have faced two compilation problems. Resolving those
problems and building the jar on my end has incidentally resolved
this re-connection problem. (I am using elasticsearch 0.19.9)
Following are the changes I made in the code. I am really not very sure
whether I made the correct changes or not, the experts can really help
better here, but those just worked for me.
// TODO, we can update the status of the river to RECONNECT
logger.warn("failed to connect after failure, throttling", e);
threadPool.schedule(TimeValue.timeValueSeconds(10),
ThreadPool.Names.CACHED, new Runnable() { @Override
public void run() {
reconnect();
}
});
changed to
// TODO, we can update the status of the river to RECONNECT
logger.warn("failed to connect after failure, throttling", e);
threadPool.schedule(TimeValue.timeValueSeconds(10),
ThreadPool.Names.CACHE, new Runnable() { @Override
public void run() {
reconnect();
}
});
And to emphasize, these were creating compilation problem at my end, I
didn't just do a random code change. Also when using behind corporate
firewall, the following open issue described at https://github.com/elasticsearch/elasticsearch-river-twitter/issues/15 needs
to be addressed.
Regards,
-- Sujoy
On Tuesday, November 6, 2012 12:37:15 PM UTC+5:30, Mikola Senyk wrote:
Thank you David!
Your crontab script is nice temporary solution.
Sorry, that I copied from a wrong development location.
Sujoy
On Thursday, November 8, 2012 11:31:59 AM UTC+5:30, Sujoy Sett wrote:
Hi,
First to mention, I am not much into core elasticsearch code, but I do
quite a bit of custom modification on the plugins part to support my
business cases. My statement here might sound too novice. My apologies.
I needed to modify the code of twitter river several times for custom
requirements, and have faced two compilation problems. Resolving those
problems and building the jar on my end has incidentally resolved
this re-connection problem. (I am using elasticsearch 0.19.9)
Following are the changes I made in the code. I am really not very sure
whether I made the correct changes or not, the experts can really help
better here, but those just worked for me.
// TODO, we can update the status of the river to RECONNECT
logger.warn("failed to connect after failure, throttling", e);
threadPool.schedule(TimeValue.timeValueSeconds(10),
ThreadPool.Names.CACHED, new Runnable() { @Override
public void run() {
reconnect();
}
});
changed to
// TODO, we can update the status of the river to RECONNECT
logger.warn("failed to connect after failure, throttling", e);
threadPool.schedule(TimeValue.timeValueSeconds(10),
ThreadPool.Names.CACHE, new Runnable() { @Override
public void run() {
reconnect();
}
});
And to emphasize, these were creating compilation problem at my end, I
didn't just do a random code change. Also when using behind corporate
firewall, the following open issue described at https://github.com/elasticsearch/elasticsearch-river-twitter/issues/15 needs
to be addressed.
Regards,
-- Sujoy
On Tuesday, November 6, 2012 12:37:15 PM UTC+5:30, Mikola Senyk wrote:
Thank you David!
Your crontab script is nice temporary solution.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.
