I got tripped up with this by not setting permissions in S3 properly. I gave individual profiles the read permissions on the bucket, but I didn’t give readers permission ….
The act of being able to hit the file on s3 with a get command was not enough of a sanity check. Highly recommend the aws command line tool for sanity check. SCott > On Nov 17, 2015, at 1:36 AM, Andries Engelbrecht <[email protected]> > wrote: > > For large cluster I normally use clush (cluster shell), edit the config files > on one node and then copy them to all using clush. > > > --Andries > >> On Nov 16, 2015, at 6:41 PM, Mikhailau, Alex <[email protected]> wrote: >> >> Thanks, guys. I had to ssh into each node and update core-site.xml on >> every node. >>
