In short, I don't know. We have a couple of 4store stores clustered
across a couple of machines, but we managed this via the 4s-cluster-*
method, which involves ssh keys. I've never used the 4s-admin/4s-boss
commands.
That said, looking at the README reminded me of something. My memory is
vague but at one point we had to figure out which port 4store was trying
to use to make sure it was reachable. The README talks about 4s-boss
using port 6733. I suspect you've got that sorted out if 4s-boss can
report the nodes (test1, test2, test3) but I thought I would mention it.
I did note that in this listserv post
https://groups.google.com/forum/#!topic/4store-support/X-Xr1mCsCCg
Manuel suggests the '4s-admin create-store storename' command as a way
to set up the backends on the clustered nodes. (It is followed by
'4s-admin start-stores storename'.) This is not mentioned in the
README. You mentioned using "4s-backend-setup."
On this last point, you specifically said:
> My
> interpretation was that I can just list the node names (i.e.
> 4s-backend-setup 'node name') and it should work.
"node name" is not accurate. It should be the name of the store, not
the node. "node name" - I think - refers to the hostnames or IP
addresses of the machines in the cluster and, if using 4s-boss, would be
set in the /etc/4store.conf file.
So, on each node, 'killall 4s-*' and run 4s-boss. Then, on the master
node, create the appropriate /etc/4store.conf file. Then, still on the
master node, run:
4s-admin create-store viaf
4s-admin start-stores viaf
4s-httpd -p 8080 viaf
HTH,
Kevin
> > > > <mailto:
4store-suppor...@googlegroups.com>.
> > > <mailto:
4store-suppor...@googlegroups.com>.
> > <mailto:
4store-suppor...@googlegroups.com>.
> <mailto:
4store-suppor...@googlegroups.com>.