It looks like you can't just install, say, the tserver RPM to get the tserver. It depends on server-base, core, start, etc. So this means I either need to figure out the dependencies and put them all on the rpm -i command, or configure a directory as a local yum repo. Does anyone know a convenient way to do that? It seems like this could use some documentation, since it's seems like a pretty nonstandard way to distribute RPMs.
Independent of all that, having just installed all the packages, I'm not sure how to get it to actually work. It looks like the accumulo jars are installed in /usr/share/java/accumulo rather than $ACCUMULO_HOME/lib, and all services are failing to start, missing the class org.apache.accumulo.start.Main. After I've installed the RPMs, am I supposed to edit accumulo-env.sh to stick all the jar locations on the classpath or something? It's not obvious to me where a good place to do that would be, or if there are other paths I need. What was the reasoning behind having the rpm create such a different installation tree from other deployments? Thanks again, Michael On Mon, Jan 27, 2014 at 5:40 PM, Josh Elser <[email protected]> wrote: > I believe the point of breaking them up the way they are is that you can > run just what you need on each host. Installing them all would certainly > give you the runtime flexibility while you can just chkconfig on the > processes you actually want to start. > > > On 1/27/14, 5:04 PM, Michael Berman wrote: > >> Ok, so I've successfully build my RPMs, and I have a whole pile of them. >> Is there one that will install all the services? Or should I install >> the >> tserver, master, gc, etc from their own poms just on the machines I want >> to >> run those on? Or do I need to install them all? >> >> >> On Mon, Jan 27, 2014 at 11:53 AM, Josh Elser <[email protected]> >> wrote: >> >> You probably want/need 'thrift,rpm,docs'. >>> >>> And, afaik, no, these are not documented anywhere. You can get a list >>> using `mvn help:all-profiles`, but, without descriptions, they're pretty >>> useless. >>> >>> >>> On 1/27/14, 11:43 AM, Michael Berman wrote: >>> >>> I'm trying to do some testing on the 1.6 RPM. What maven switches are >>>> our >>>> official builds built with? Is just -Prpm enough, or do I need >>>> assemble, >>>> apache-release, etc., too? Is this stuff documented anywhere? >>>> >>>> Thanks, >>>> Michael >>>> >>>> >>>> >>
