May be one of your node can not access to AWS API or don't have required credentials???
--
David Pilato
Sent with Airmail
Le 18 septembre 2014 à 23:22:50, rhea ghosh (rhea.ghosh@gmail.com) a écrit:
Ok that was totally it for that first error, I thought I had restarted the service but there were a few nodes taht hadn't been restarted so weren't registering the plugin.
Now I'm getting a different error that I'm still pretty lost on:
curl -XPUT localhost:9200/_snapshot/my_s3_repository/snapshot_20140918?wait_for_completion=true
{"error":"SnapshotCreationException[[my_s3_repository:snapshot_20140918] failed to create snapshot]; nested: IOException[Failed to get [snapshot-snapshot_20140918]]; nested: AmazonClientException[Unable to execute HTTP request: Connection reset]; nested: SocketException[Connection reset]; ","status":500}
On Thursday, September 18, 2014 3:35:20 PM UTC-5, David Pilato wrote:
Not sure my theory is good but my first guess is that you have more than one node running and one of this nodes does not have the plugin installed or has not been restarted.
Can you run: curl
'localhost:9200/_cat/plugins?v'
And post results here
--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet | @elasticsearchfr | @scrutmydocs
Le 18 sept. 2014 à 22:25, rhea ghosh rhea....@gmail.com a écrit :
As a follow up with more information this is the listing for the cloud-aws plugin:
[rhea@server cloud-aws]$ ll
total 14640
-rw-r--r-- 1 root root 12418940 Sep 16 10:43 aws-java-sdk-1.7.13.jar
-rw-r--r-- 1 root root 58160 Sep 16 10:43 commons-codec-1.4.jar
-rw-r--r-- 1 root root 60686 Sep 16 10:43 commons-logging-1.1.1.jar
-rw-r--r-- 1 root root 41853 Sep 16 10:43 elasticsearch-cloud-aws-2.2.0.jar
-rw-r--r-- 1 root root 424648 Sep 16 10:43 httpclient-4.2.jar
-rw-r--r-- 1 root root 223282 Sep 16 10:43 httpcore-4.2.jar
-rw-r--r-- 1 root root 34477 Sep 16 10:43 jackson-annotations-2.1.1.jar
-rw-r--r-- 1 root root 206379 Sep 16 10:43 jackson-core-2.1.1.jar
-rw-r--r-- 1 root root 922643 Sep 16 10:43 jackson-databind-2.1.1.jar
-rw-r--r-- 1 root root 581571 Sep 16 10:43 joda-time-2.3.jar
and when I run s3cmd I get:
[rhea@server cloud-aws]$ s3cmd ls| fgrep elasticsearch-staging
2014-09-15 16:27 s3://elasticsearch-staging
and I get the same error when I try to do a snapshot directly to s3:
[rhea@server cloud-aws]$ curl -XPUT localhost:9200/_snapshot/my_s3_repository/snapshot_20140918?wait_for_completion=true
{"error":"RemoteTransportException[Failed to deserialize exception response from stream]; nested: TransportSerializationException[Failed to deserialize exception response from stream]; nested: InvalidClassException[failed to read class descriptor]; nested: ClassNotFoundException[com.amazonaws.AmazonClientException]; ","status":500}
I'm really confused because it seems like it should work but I keep getting ClassNotFoundExceptions which I find strange since I have the same install on all my nodes.
On Thursday, September 18, 2014 11:56:31 AM UTC-5, rhea ghosh wrote:
Hi
I'm trying to get snapshots up to an AWS S3 bucket from an elasticsearch cluster. I've successfully managed to install cloud-aws 2.2.0 and I believe this should be the right version that I need.
So when I create the repository it seems like everything is fine:
curl -XPOST localhost:9200/_snapshot/my_s3_repository -d '
{
"type": "s3",
"settings" : {
"bucket": "elasticsearch-staging",
"access_key": "XXXXXX",
"secret_key": "XXXXXX"
}
}'
{"acknowledged":true}*
So far so good. But then when I run curator to take a snapshot (or even if I do it directly I get an exception:
curator snapshot --older-than 6 --repository my_s3_repository
...
elasticsearch.exceptions.TransportError: TransportError(500,u'RemoteTransportException[Failed to deserialize exception response from stream]; nested: TransportSerializationException[Failed to deserialize exception response from stream]; nested: InvalidClassException[failed to read class descriptor]; nested: ClassNotFoundException[com.amazonaws.services.s3.model.AmazonS3Exception]; ')
any ideas on how I could fix this?
--
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 toelasticsearc...@googlegroups.com.
To view this discussion on the web visithttps://groups.google.com/d/msgid/elasticsearch/bd120d1e-478c-4674-9fbd-970d1a6580cd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/b1a64dcc-b6e4-4ecc-8296-032f066e81e3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/etPan.541b4e6c.6b8b4567.18d1%40MacBook-Air-de-David.local.
For more options, visit https://groups.google.com/d/optout.