Re: Documents not deleted when using DeleteRequest within BulkProcessor
Thank you for the reply, David.
We are using an alias to delete. Is that a problem? Indexing with the
alias through the bulk processor works fine.
There are no errors reported, it just seems to disappear into the oblivion.
Here's our code for the BulkProcessor:
public static BulkProcessor getBulkProcessor(Client client, int
esConcurrencyLevel, int esBulkSize, int esFlushInterval) {
return BulkProcessor.builder(client, new BulkProcessor.Listener() {
@Override
public void beforeBulk(long executionId, BulkRequest bulkRequest) {
LOG.debug(Processing {} requests in bulk process {},
bulkRequest.numberOfActions(), executionId);
}
@Override
public void afterBulk(long executionId, BulkRequest bulkRequest,
BulkResponse response) {
if (response.hasFailures()) {
for (BulkItemResponse item : response.getItems()) {
LOG.error(Processing to index \{}\ failed for entity id
{} with message {}, item.getIndex(),
item.getId(), item.getFailureMessage());
}
}
}
@Override
public void afterBulk(long executionId, BulkRequest bulkRequest,
Throwable throwable) {
LOG.error(Failed to process {} requests in bulk request {}: {},
bulkRequest.numberOfActions(),
executionId, throwable.getMessage());
throwable.printStackTrace();
}
})
.setBulkActions(esBulkSize)
.setFlushInterval(TimeValue.timeValueSeconds(esFlushInterval))
.setConcurrentRequests(esConcurrencyLevel)
.build();
}
*Code for the delete request:*
bulkProcessor.add(new DeleteRequest(index.getIndexingAlias(), index.getType(),
entityId));
where index.getIndexingAlias() is an alias (same alias used for indexing which
is working), type is the document type company and entityId is the document
ID.
What data would be helpful? An example document, the index metadata, something
else?
On Wednesday, April 29, 2015 at 9:53:41 PM UTC-7, David Pilato wrote:
Do you try to delete a doc using an alias?
Any failure or error reported by the bulk processor?
Hard to tell more without seeing the code / data.
David
Le 30 avr. 2015 à 02:03, Diana Tuck dtu...@gmail.com javascript: a
écrit :
Trying to index/delete documents within one BulkProcessor object in the
Java API. Indexing documents works great! Deleting, however, does not.
bulkProcessor.add(new DeleteRequest(index.getIndexingAlias(),
index.getType(), entityId));
Nothing happens. Any ideas?
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearc...@googlegroups.com javascript:.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/e2774458-8542-4634-bd8d-1ccfd9837409%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/e2774458-8542-4634-bd8d-1ccfd9837409%40googlegroups.com?utm_medium=emailutm_source=footer
.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To unsubscribe from this group and stop receiving emails from it, send an email
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/01b6ab18-78a8-44d0-b574-c649501ec21a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Documents not deleted when using DeleteRequest within BulkProcessor
Trying to index/delete documents within one BulkProcessor object in the Java API. Indexing documents works great! Deleting, however, does not. bulkProcessor.add(new DeleteRequest(index.getIndexingAlias(), index.getType(), entityId)); Nothing happens. Any ideas? -- You received this message because you are subscribed to the Google Groups elasticsearch group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/e2774458-8542-4634-bd8d-1ccfd9837409%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
waited for 30s and no initial state was set by the discovery
I know other people have posted this, but I've tried everything that the
other threads have said to try. We keep getting this at startup of our
java node client:
INFO [2015-02-19 17:57:45,206] org.elasticsearch.node: [localhost]
version[1.4.2], pid[11103], build[927caff/2014-12-16T14:11:12Z]
INFO [2015-02-19 17:57:45,207] org.elasticsearch.node: [localhost]
initializing ...
INFO [2015-02-19 17:57:45,217] org.elasticsearch.plugins: [localhost]
loaded [cloud-aws], sites []
INFO [2015-02-19 17:57:47,625] org.elasticsearch.node: [localhost]
initialized
INFO [2015-02-19 17:57:47,625] org.elasticsearch.node: [localhost]
starting ...
INFO [2015-02-19 17:57:47,716] org.elasticsearch.transport: [localhost]
bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address
{inet[/10.99.157.0:9300]}
INFO [2015-02-19 17:57:49,747] org.elasticsearch.discovery: [localhost]
elasticsearch-dev/EqKAxZm9SCutQGd-0_SonA
WARN [2015-02-19 17:58:19,749] org.elasticsearch.discovery: [localhost]
waited for 30s and no initial state was set by the discovery
INFO [2015-02-19 17:58:19,761] org.elasticsearch.http: [localhost]
bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address
{inet[/10.99.157.0:9200]}
INFO [2015-02-19 17:58:19,761] org.elasticsearch.node: [localhost] started
This is the elasticsearch.yml on our master (and only data node right now):
plugin.mandatory: cloud-aws
cloud:
aws:
region: us-west-2
access_key: ACCESS_KEY
secret_key: SECRET_KEY
discovery:
type: ec2
ec2:
groups: DevAll
And this is our java node client:
Settings settings = ImmutableSettings.settingsBuilder()
.put(node.name, nodeName)
.put(cloud.aws.access_key, awsAccessKey)
.put(cloud.aws.secret_key, awsSecretKey)
.put(cloud.node.auto_attributes, true)
.put(discovery.type, ec2)
.build();
this.node = nodeBuilder()
.clusterName(clusterName)
.settings(settings)
.client(true)
.node();
this.client = node.client();
Any help would be greatly appreciated!!!
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To unsubscribe from this group and stop receiving emails from it, send an email
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/15f03a06-58a8-4ef3-9a73-93fc779dd6e1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: waited for 30s and no initial state was set by the discovery
Additional information - we can telnet into or ES server from our
application server on 9300.
On Thursday, February 19, 2015 at 10:04:51 AM UTC-8, Diana Tuck wrote:
I know other people have posted this, but I've tried everything that the
other threads have said to try. We keep getting this at startup of our
java node client:
INFO [2015-02-19 17:57:45,206] org.elasticsearch.node: [localhost]
version[1.4.2], pid[11103], build[927caff/2014-12-16T14:11:12Z]
INFO [2015-02-19 17:57:45,207] org.elasticsearch.node: [localhost]
initializing ...
INFO [2015-02-19 17:57:45,217] org.elasticsearch.plugins: [localhost]
loaded [cloud-aws], sites []
INFO [2015-02-19 17:57:47,625] org.elasticsearch.node: [localhost]
initialized
INFO [2015-02-19 17:57:47,625] org.elasticsearch.node: [localhost]
starting ...
INFO [2015-02-19 17:57:47,716] org.elasticsearch.transport: [localhost]
bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/
10.99.157.0:9300]}
INFO [2015-02-19 17:57:49,747] org.elasticsearch.discovery: [localhost]
elasticsearch-dev/EqKAxZm9SCutQGd-0_SonA
WARN [2015-02-19 17:58:19,749] org.elasticsearch.discovery: [localhost]
waited for 30s and no initial state was set by the discovery
INFO [2015-02-19 17:58:19,761] org.elasticsearch.http: [localhost]
bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address {inet[/
10.99.157.0:9200]}
INFO [2015-02-19 17:58:19,761] org.elasticsearch.node: [localhost] started
This is the elasticsearch.yml on our master (and only data node right now):
plugin.mandatory: cloud-aws
cloud:
aws:
region: us-west-2
access_key: ACCESS_KEY
secret_key: SECRET_KEY
discovery:
type: ec2
ec2:
groups: DevAll
And this is our java node client:
Settings settings = ImmutableSettings.settingsBuilder()
.put(node.name, nodeName)
.put(cloud.aws.access_key, awsAccessKey)
.put(cloud.aws.secret_key, awsSecretKey)
.put(cloud.node.auto_attributes, true)
.put(discovery.type, ec2)
.build();
this.node = nodeBuilder()
.clusterName(clusterName)
.settings(settings)
.client(true)
.node();
this.client = node.client();
Any help would be greatly appreciated!!!
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To unsubscribe from this group and stop receiving emails from it, send an email
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/f57f1be2-cda0-42c2-9001-33fa29b1a111%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: ClassNotFoundException: org.elasticsearch.discovery.ec2.Ec2DiscoveryModule
Thanks, David. I eventually ended up finding the pom on the github repo. Thanks for adding the documentation!! On Wednesday, February 18, 2015 at 10:39:19 PM UTC-8, David Pilato wrote: Yes. This should be added to the doc: https://github.com/elasticsearch/elasticsearch-cloud-aws/issues/176 You need to add this dependency if you are using a NodeClient: groupIdorg.elasticsearch/groupId artifactIdelasticsearch-cloud-aws/ artifactId version2.4.1/version HTH David Le 19 févr. 2015 à 01:15, Diana Tuck dtu...@gmail.com javascript: a écrit : New to ES - Trying to use the elasticsearch-cloud-aws plugin, but when starting my java client node, I'm getting ClassNotFoundException on org.elasticsearch.discovery.ec2.Ec2DiscoveryModule. Do I need to install this plugin on java client nodes, and if so, how does one do that? Or, rather, is there a maven dependency that can be referenced to load these required classes? For reference, the elasticsearch.yaml is: plugin.mandatory: cloud-aws cloud: aws: access_key: ** secret_key: * discovery: type: ec2 and my java client code is: Settings settings = ImmutableSettings.settingsBuilder() .put(node.name, nodeName) .put(cloud.aws.access_key, awsAccessKey) .put(cloud.aws.secret_key, awsSecretKey) .put(cloud.node.auto_attributes, true) .put(discovery.type, ec2) .build(); this.node = nodeBuilder() .clusterName(clusterName) .settings(settings) .client(true) .node(); this.client = node.client(); -- You received this message because you are subscribed to the Google Groups elasticsearch group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearc...@googlegroups.com javascript:. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/925353fd-b717-417d-986f-570c634e39c1%40googlegroups.com https://groups.google.com/d/msgid/elasticsearch/925353fd-b717-417d-986f-570c634e39c1%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups elasticsearch group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/3fc41382-3521-416d-8052-50f342462816%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Java node client failing to send join request to master
Anyone have any idea where to start with this one? We're running our
singular master/data node in a docker container, trying to connect via a
Java node client on different boxes. Please help!!
INFO [2015-02-20 02:55:11,411] org.elasticsearch.discovery.ec2:
[localhost] failed to send join request to master
[[esNode][jU4Y42dtQfCPJn1-5jFfYw][esHost][inet[/255.255.255.255]]{master=true}],
reason
[RemoteTransportException[[esNode][inet[/255.255.255.255:9300]][internal:discovery/zen/join]];
nested:
NotSerializableTransportException[[org.elasticsearch.transport.ConnectTransportException]
[localhost][inet[/255.255.255.255:9300]] connect_timeout[30s]; connection
timed out: /255.255.255.255:9300; ]; ]
elasticsearch.yml:
cloud:
aws:
access_key: awsAccessKey
secret_key: awsSecretKey
region: us-west-2
discovery:
type: ec2
ec2:
groups: elasticsearch
availability_zones: us-west-2a
tag:
Elasticsearch: tag
network.public_host: 255.255.255.255
network.publish_host: 255.255.255.255
discovery.zen.ping.multicast.enabled: false
Java node client:
Settings settings = ImmutableSettings.settingsBuilder()
.put(node.name, nodeName)
.put(cloud.aws.access_key, awsAccessKey)
.put(cloud.aws.secret_key, awsSecretKey)
.put(cloud.aws.region, us-west-2)
.put(cloud.node.auto_attributes, true)
.put(discovery.type, ec2)
.put(discovery.ec2.groups, elasticsearch)
.put(discovery.ec2.availability_zones, us-west-2a)
.put(discovery.ec2.tag.Elasticsearch, devvpc)
.put(discovery.zen.ping.multicast.enabled, false)
.build();
this.node = nodeBuilder()
.clusterName(clusterName)
.settings(settings)
.client(true)
.node();
this.client = node.client();
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To unsubscribe from this group and stop receiving emails from it, send an email
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/c56baa18-0956-4b88-a063-acd4db82374e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
ClassNotFoundException: org.elasticsearch.discovery.ec2.Ec2DiscoveryModule
New to ES - Trying to use the elasticsearch-cloud-aws plugin, but when starting my java client node, I'm getting ClassNotFoundException on org.elasticsearch.discovery.ec2.Ec2DiscoveryModule. Do I need to install this plugin on java client nodes, and if so, how does one do that? Or, rather, is there a maven dependency that can be referenced to load these required classes? For reference, the elasticsearch.yaml is: plugin.mandatory: cloud-aws cloud: aws: access_key: ** secret_key: * discovery: type: ec2 and my java client code is: Settings settings = ImmutableSettings.settingsBuilder() .put(node.name, nodeName) .put(cloud.aws.access_key, awsAccessKey) .put(cloud.aws.secret_key, awsSecretKey) .put(cloud.node.auto_attributes, true) .put(discovery.type, ec2) .build(); this.node = nodeBuilder() .clusterName(clusterName) .settings(settings) .client(true) .node(); this.client = node.client(); -- You received this message because you are subscribed to the Google Groups elasticsearch group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/925353fd-b717-417d-986f-570c634e39c1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
