I'm a little unsure what you mean. If you're running a local mode cluster (using LocalCluster) I'm wondering what storm.yaml you're editing? Are you using LocalCluster or do you mean that you've installed a Storm release to your local machine?
If you're running Storm in local mode using LocalCluster, I don't believe you can set the log directory in 1.0.3 (I'm not a hundred percent on this). I think local clusters currently just save files to the temporary files directory. Local mode is more configurable in 2.0.0. 2017-10-06 22:06 GMT+02:00 Mahak Goel <[email protected]>: > Here are the steps I took: > 1. In storm.yaml set storm.log.dir to a directory with write permissions > 2. Put storm.yaml into a directory called conf > 3. Set the STORM_CONF_DIR to the conf directory > > I then got these errors > Exception in thread "main" java.lang.ExceptionInInitializerError > at org.apache.storm.config$read_storm_config.invoke(config.clj:78) > at org.apache.storm.config$fn__908.invoke(config.clj:100) > at org.apache.storm.config__init.load(Unknown Source) > at org.apache.storm.config__init.<clinit>(Unknown Source) > > Is this expected to work in local mode? > > On Fri, Oct 6, 2017 at 1:50 PM, Stig Rohde Døssing <[email protected]> > wrote: > >> Hi Mahak, >> >> You should be able to set paths in your conf/storm.yaml. I'm guessing you >> need to set storm.workers.artifacts.dir. See >> https://github.com/apache/storm/blob/v1.0.3/conf/defaults.yaml for >> reference. >> >> 2017-10-06 17:39 GMT+02:00 Mahak Goel <[email protected]>: >> >>> apache-storm-1.0.3/storm-1.0.3/logs/workers-artifacts/ >>> >>> Hi, I'm getting this unable to create directory error while trying to >>> run storm. Is this because it doesn't have write permissions to create its >>> log directory? Is there a way for me to configure where the logs should go >>> so I can specify a directory where there are write permissions? >>> >> >> >
