cannot locate cassandra.yaml when using cfs remotely?
158 views
Skip to first unread message
Jeremy Hanna
unread,
Oct 22, 2011, 10:34:33 AM10/22/11
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Brisk Users
I'm trying to use cfs remotely using oozie and have gotten past a lot of the classpath issues I was having and have gotten oozie to recognize the filesystem scheme, but now I'm running into a problem where it's throwing an error in the logs about it not being able to locate cassandra.yaml - actually in the catalina.out: Cannot locate cassandra.yaml Fatal configuration error; unable to start server. See log for stacktrace. So is it required to have a cassandra.yaml on a remote machine or is there a way around that? Thanks, Jeremy
Jeremy Hanna
unread,
Oct 23, 2011, 2:36:46 PM10/23/11
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Brisk Users
Looks like having the cassandra.yaml is probably going to be standard operating procedure for some reason. I would think it has to do with doing some static initialization that directly or indirectly gets to the database descriptor class, which uses the config. Anyway, I guess I'll just add that to the list of things to configure for getting oozie to work with brisk.