Hey Minnow, I'm not sure what caused the corruption (if any). You could take a look at the logs and double check if it is indeed a storage plug-in issue.
Storage plugins are persisted in ZooKeeper. If you'd like to take a look, navigate inside your ZooKeeper install location and run the following command: # cd /opt/mapr/zookeeper/zookeeper-3.4.5/bin/ (if you are using MapR) # ./zkCli.sh -server 10.10.103.32:5181 (provide your zookeeper host & port) Connecting to 10.10.103.32:5181 Welcome to ZooKeeper! ... ... [zk: 10.10.103.32:5181(CONNECTED) 0] ls / (do an ls to list) [services, hbase, zookeeper, nodes, servers, ..., *drill*, ...] If you'd like to remove drill storage plug-ins, you can first do an ls /drill and only remove the necessary ones inside it. You could also remove the entire /drill node instead. I'd suggest you be cautious when modifying entries inside the ZooKeeper. Regards, Abhishek On Wed, May 6, 2015 at 3:02 AM, Minnow Noir <[email protected]> wrote: > After upgrading to 0.9 today and then later editing my storage plugins, I > have been unable to start drill. > > I was able to use drill 0.9 for several hours, but then used the web app to > edit the storage plugins to point to a new directory. The update button > did nothing when I clicked it, despite trying several times. Therefore, I > clicked cancel. Instead of showing the plugin list page, I got a 404. My > drill session crashed as well with some error messages about being unable > to access some temporary files. I uninstalled and reinstalled drill, but > can no longer start a drillbit. > > I don't see in the docs where the plugins file is persisted. It apparently > is outside of the drill folder structure since the problem has survived > through uninstalls. Any idea where the file is? > > Thanks, > > Minnow >
