TLS Self-Signed Certs about monstache HOT 15 CLOSED

The syntax is the same for the connection string in the TOML file or when passed on the command line.

According to

https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-node.html

It seems that all nodes know about one another and can forward requests appropriately. So I'm assuming you can pick any one.

If you are using es5 and gridfs replication it seems it would be best to setup a dedicated node/nodes for ingestion according to that doc.

from monstache.

Can you try supplying the argument elasticsearch-pem-file

flag.StringVar(&configuration.ElasticPemFile, "elasticsearch-pem-file", "", "Path to a PEM file for secure connections to elasticsearch")

You would never know because I failed to document this.

from monstache.

Will give it a go this evening.

from monstache.

@rwynn it worked perfectly, thanks. Now replicating over TLS. 👍

from monstache.

Great. Just FYI you can put this in your TOML file or pass it as a flag on the command line. Simple options work either way. I will close this issue once I've added the docs for the mongo and elasticsearch pem file options.

from monstache.

Thanks. Slightly off-topic, but relating to the config options. Does the syntax for the ES connection string as per the Go client remain the same in the TOML file?

"https://user:[email protected]:9200", "https://user:[email protected]:9200", "..."

Or will the client sniff out the other nodes given one?

from monstache.

Looked into this a bit more and the elastigo go client connection supports a Hosts array in addition to the connection string. Monstache is not surfacing the ability to set the hosts array currently. I will take a look at putting this in. It would be an array of host names in addition to the connection string. Looks like elastigo then chooses a host from the pool based on some heuristics (previously failed?) for each request.

from monstache.

We would be able to test this whenever it's available, have a few clusters running. 👍

from monstache.

@Crispy1975 Are you looking for a copy of each index request to go to N hosts? Or are you looking to configure a pool of hosts and each index request would go to one from the pool?

from monstache.

The best way to do multiple clusters I think would be to run a monstache process for each cluster. For nodes within a cluster a single monstache process can send requests to a pool of nodes using the previously mentioned Hosts setting on the connection. That would be a new config option.

from monstache.

Yeah, we are running different installs of monstache for each cluster to partition data. This works best for us.

from monstache.

Sounds good. If you are using the resume feature make sure to set the resume-name to something unique for each process (cluster) otherwise they will overwrite one another.

I need to fix an issue with using multiple processes combined with the resume feature combined with the multi-worker feature. But that's probably not a combination you are using.

from monstache.

Thanks for the heads-up with that, will be sure to make sure the resume-name is unique.

from monstache.

@Crispy1975,
Just checkin in to see how things are going with monstache. Have you had any pain points using it? Any suggestions for improvements? Thanks.

from monstache.

All good so far, we haven't seen any issues at this point. :)

from monstache.