Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Traun Leyden
    @tleyden
    Yes, admin/password are the defaults
    Sebastien Arbogast
    @sarbogast
    then it should not have worked with a custom password for admin, should it?
    Sebastien Arbogast
    @sarbogast
    also, at the end of the procedure, if I run 'docker ps- -a' I see 8 containers, including 5 that have exited. I'm guessing those 5 are from all the commands that I ran to initialize the cluster, but won't they incur additional charges if I don't remove them?
    Traun Leyden
    @tleyden
    Great catch!
    Yup, you will be charged
    I need to update to add -rm flag
    Btw did you hear that joyent will present at Cb Connect?
    Sebastien Arbogast
    @sarbogast
    no I didn't know
    too bad I can't join
    Traun Leyden
    @tleyden
    Bryan Cantrill is slated to give a keynote, and a couple other Joyet folks will be coming to Connect. You can watch the videos after the conference.
    Sebastien Arbogast
    @sarbogast
    awesome
    I mean it's good if they make it easier to deploy couchbase to the cloud but hopefully this will make it worth the effort for Couchbase to tackle other kinds of customers ;)
    Traun Leyden
    @tleyden
    Joyent is on prem too. (A lot of enterprise customers require on prem)
    I'm also working on getting couchbase working on kubernetes: https://github.com/tleyden/couchbase-kubernetes
    Theoretically that could also run on Joyent, but I dont think they support Kubernetes out of the box yet. I've been testing on Google Container Engine (GKE)
    Sebastien Arbogast
    @sarbogast
    I know, but startups are rarely on prem, startups don't want to have to deal with all that infrastructure stuff, for us, infrastructure is a commodity, and spending thousands of dollars on our own data centers, and paying consultants 2500 bucks a day to help us set that all up is just overkill
    Traun Leyden
    @tleyden
    You are talking to a prev startup cofounder who ran everything on heroku ;)
    Sebastien Arbogast
    @sarbogast
    Heroku for couchbase sync si sooooo the future!
    manyan.chen
    @manyan
    @tleyden can you provide a command to start/restart a couchbase node using docker? one of the node went down last night, as you can see the docker ps return me empty list, would like to restart it, but can no find the command, cheers
    Traun Leyden
    @tleyden
    @manyan sorry, just now seeing your message.
    @manyan can you give me a little more background on how you are running it? Is this under coreos? let me know the blog post or instructions you are working off of
    Traun Leyden
    @tleyden
    @PaulCapestany the coreos/fleet stuff is broken for me too: couchbaselabs/couchbase-server-coreos#17. I'm pretty sure I broke things when I made some changes to make things work with Kubernetes.
    Traun Leyden
    @tleyden
    ok, fixed and I the instructions have been consolidated into this README
    Paul Capestany
    @PaulCapestany
    @tleyden just now seeing your message, I seemed to still run into issues even with updated code + README → couchbaselabs/couchbase-server-coreos#18
    Traun Leyden
    @tleyden
    can you paste the output of "docker log afd91d66eab3"?
    (the container id of the sync gw container that seems to have failed)
    or fleetctl journal --lines 1000 sync_gw_node@1.service
    Paul Capestany
    @PaulCapestany
    sure
    oh, hmm, already killed off that cluster, starting up a new one
    Paul Capestany
    @PaulCapestany
    @tleyden — I just edited couchbaselabs/couchbase-server-coreos#18 and updated all the log files with info from a brand new cluster (and added extra stuff you'd asked for)
    I'm surprised that the config emitted had "server":"http://127.0.0.1:8091", rather than {{ .COUCHBASE_IP }}, though I don't know if that's the root problem
    Traun Leyden
    @tleyden
    that whole approach of rewriting the file from a template feels super hacky.
    I guess the thing writing the file is probably writing it one place, and thing reading the file is looking for it in a different place... what those places are is not immediately apparent.
    I guess confd would probably be a cleaner approach. any thoughts?
    Paul Capestany
    @PaulCapestany
    @tleyden your README (and the issue I opened) uses --config-url=http://git.io/b9PK which sets "server":"http://127.0.0.1:8091"
    Traun Leyden
    @tleyden
    egads
    good catch, I need to fix that
    Paul Capestany
    @PaulCapestany
    though I'd also used my own config file with {{ .COUCHBASE_IP }} and still had same issues I think
    retrying now though to triple check
    Paul Capestany
    @PaulCapestany
    yeah, same issue even when using {{ .COUCHBASE_SERVER_IP }} https://gist.github.com/PaulCapestany/b58b26d44b4cb6fd1f34
    Paul Capestany
    @PaulCapestany
    @tleyden I think I may have tracked things down a bit further → https://github.com/couchbaselabs/couchbase-server-coreos/issues/18#issuecomment-106026386
    Traun Leyden
    @tleyden
    just posted to the ticket
    Traun Leyden
    @tleyden
    @PaulCapestany merged. glad you remembered to run go generate!
    to use that change, you'll need to follow the instructions here: https://github.com/tleyden/couchbase-cluster-go#running-on-the-latest-code
    Paul Capestany
    @PaulCapestany
    yeah
    Traun Leyden
    @tleyden
    (so that it pulls the latest couchbase-cluster-go rather than using the version baked into the docker image)
    Paul Capestany
    @PaulCapestany
    one thing I noticed though is that go generate output seems to differ a bit (not just in generated bytes), for example removing a ~ ... does that matter?
    couchbase-cluster-go (Git) 2015-05-27 14-11-19.png