These are chat archives for azukiapp/azk

19th
Aug 2015
Gullit Miranda
@gullitmiranda
Aug 19 2015 00:38
Well, I believe that in future versions of azk it may be simpler to implement.
Slobodan Mišković
@slobo
Aug 19 2015 19:54
Is it possible to give each scalable instance a host name? I'm thinking about what gets passed to docker -h
or actually looking for any way to identify an instance number from inside the container.
Any persistent and unique per instance thing will do.
(i'm building a solrcloud cluster, and when doing azk restart, i need to tell each instance who they are, otherwise they just join as a whole new node and don't know which shard they should be responsible for)
Slobodan Mišković
@slobo
Aug 19 2015 20:02
(hm, I'll try to solve it by using multiple systems instead, that should be more reliable)
(but then I lose out on having azk be the load balancer)
Gullit Miranda
@gullitmiranda
Aug 19 2015 22:22
@slobo, sorry for the delay.
There are two environment variables that are unique: $HOSTNAME and $AZK_UID. I believe that with them you can separate instances.
to get all envs, run:
$ azk shell -- env
Slobodan Mišković
@slobo
Aug 19 2015 23:52
my understanding is that $HOSTNAME is going to change every time system is started.
I need something that i can trace back to a particular instance.
Well, I needed something.
Turns out I had an error in another configuration, so I no longer need to identify an instance...
thanks
Gullit Miranda
@gullitmiranda
Aug 19 2015 23:58
That's good.
I will note this problem you had to discuss it with the rest of the team, we may be able to resolve this in a relatively simple manner.