Denis Boulas
Denis Boulas
2 years have passed. only 5 parameters it's possible to override... Great progress!
@dskatz any guidance how you enabled groups? for me Google always returns `groups=[]` Thanks in advance!
All settings are set with ENV variables. ```# export -p | egrep ' PILOSA_' export PILOSA_BIND='10.239.41.59:10101' export PILOSA_CLUSTER_REPLICAS='3' export PILOSA_DATA_DIR='/data/pilosa' export PILOSA_GOSSIP_PORT='11101' export PILOSA_GOSSIP_SEEDS='dev-pilosa-0.dev-pilosa-headless.dev-pilosa.svc.cluster.local:11101,dev-pilosa-1.dev-pilosa-headless.dev-pilosa.svc.cluster.local:11101,dev-pilosa-2.dev-pilosa-headless.dev-pilosa.svc.cluster.local:11101' export PILOSA_VERBOSE='true' ``` Coordinator node additionally...
@jaffee I've tested my configuration with `pilosa/pilosa:v1.2.0` image today. Coordinator just fails to start: ``` + '[' 0 '==' 0 ] + export 'PILOSA_CLUSTER_COORDINATOR=true' + /pilosa server 2019/01/18 16:21:57 Pilosa...
@jaffee then it dies silently... In the log I have only this part: ```/ # tail -f /data/pilosa.log 2019/01/18 17:06:46 [WARN] memberlist: Failed to resolve dev-pilosa-1.dev-pilosa-headless.dev-pilosa.svc.cluster.local:11101: lookup dev-pilosa-1.dev-pilosa-headless.dev-pilosa.svc.cluster.local on 10.239.0.10:53:...
@jaffee now that you've merged it into master, I was able to test. It's definitely better (cannot say how much better yet). At least cluster is able to start from...
All settings are set with ENV variables. ```# export -p | egrep ' PILOSA_' export PILOSA_BIND='10.239.41.59:10101' export PILOSA_CLUSTER_REPLICAS='3' export PILOSA_DATA_DIR='/data/pilosa' export PILOSA_GOSSIP_PORT='11101' export PILOSA_GOSSIP_SEEDS='dev-pilosa-0.dev-pilosa-headless.dev-pilosa.svc.cluster.local:11101,dev-pilosa-1.dev-pilosa-headless.dev-pilosa.svc.cluster.local:11101,dev-pilosa-2.dev-pilosa-headless.dev-pilosa.svc.cluster.local:11101' export PILOSA_VERBOSE='true' ``` Coordinator node additionally...
@bitwiseman Any update on this? or at least any workaround? Plugin version 2.9.2 still have the issue.
@hakman @olemarkus `force_tcp` is questionable solution in general, it makes all requests (even those were done with UDP on client side) initiated in TCP. As per DNS RFC, TCP should...