Tag Info

New answers tagged

1

I guess you would need to create an in-between HTTP proxy with all this "business logic", and only allow ElasticSearch access from the localhost. This way direct access to ES is blocked and you get to determine and enforce any policies you'd like (yay! ;) "even if I provide a custom API layer to this someone could easily bypass it": they cannot if ES only ...


0

I've discovered after much suffering that the best way to run elasticsearch on a single server is to change the default setting of: index.number_of_replicas: 1 to index.number_of_replicas: 0 If there are 0 replicas, elasticsearch will never try to assign shards to any other "replica" then itself, thereby removing the issue of unassigned shards and ...


0

The easiest fix for this is to configure elasticsearch so that it doesn't use any replicas: index.number_of_replicas: 0 If elasticsearch isn't trying to distribute shards to other nodes, it won't have unassigned shards. I'm not sure why the default config on elasticsearch is to have index.number_of_replicas: 1 Must people who are tricking around with ...


0

The problem was that somehow I managed to install a ElasticSearch version which required Java 7 (openjdk-7-*) which isn't support for Ubuntu 11.04. The reason I wanted to update is because of a vulnerability which makes your server usable for DDOS attacks. I finally fixed the problem by downgrading Elastic Search to version 1.1.2 and adding firewall rules ...


1

You must use version 0.90.10 of Elasticsearch with Graylog2 0.20. It is using the binary protocol and those are not generally compatible between versions, unfortunately. This line: org.elasticsearch.transport.RemoteTransportException: Failed to deserialize exception response from stream is what gives the problem away, the protocol is different, so the ...



Top 50 recent answers are included