About the failure of using logstash to synchronize mysql data to manticore about manticoresearch

[tomatolog]

could you try to use recent release? As string to timestamp conversion was fixed recently.

[zhangsanhuo]

could you try to use recent release? As string to timestamp conversion was fixed recently.

Thank you for your reply. I deleted old manticore, and reinstall manticore.

Now manticore version is:
Server version: 6.3.0 1811a9efb@24052209 (columnar 2.3.0 88a01c3@24052206) (secondary 2.3.0 88a01c3@24052206) (knn 2.3.0 88a01c3@24052206) git branch HEAD (no branch)

But when i use logstash sycn mysql data to manticore, there is another errors below:
Jun 06 21:02:51 raspberrypi logstash[194455]: [2024-06-06T21:02:51,145][ERROR][logstash.outputs.elasticsearch][main][34fdb55ea05929bf8e49916707c868bf53cef335ed6cce6f91ce5579a973a507] Encountered a retryable error (will retry with exponential backoff) {:code=>400, :url=>"http://localhost:9308/_bulk?filter_path=errors,items.*.error,items.*.status", :content_length=>188, :body=>"{\"error\":\"Something went wrong\"}"}

There is no tables when i use "show tables;" in manticore command.

[Nick-S-2018]

It appears your issue has to do with the Logstash version you use. Unfortunately, it hasn't been reflected in our documentation that Manticore doesn't support the versions >7.15 as of now. We are going to add the support for the newer versions in the near future. Till that time, the solution for you would be to downgrade your Logstash to a version currently supported by Manticore (7.6-7.15), if that doesn't violate other parts of your work.

[zhangsanhuo]

Thanks for your reply. We tried two versions of logstash, 7.15.0 and 7.10.0, but unfortunately, we still could not successfully synchronize MySQL data to the RT table of manticore.

This is the error log of version 7.15.0:

2024-06-14T23:39:52,559][ERROR][logstash.outputs.elasticsearch][main] Could not connect to a compatible version of Elasticsearch {:url=>"http://localhost:9308/"}
[2024-06-14T23:39:52,701][ERROR][logstash.outputs.elasticsearch][main] Unable to retrieve Elasticsearch cluster uuid {:message=>"No Available connections", :exception=>LogStash::Outputs::ElasticSearch::HttpClient::Pool::NoConnectionAvailableError, :backtrace=>["/home/zxf/logstash-7.15.0/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-11.0.2-java/lib/logstash/outputs/elasticsearch/http_client/pool.rb:381:in `with_connection'", "/home/zxf/logstash-7.15.0/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-11.0.2-java/lib/logstash/outputs/elasticsearch/http_client/pool.rb:292:in `perform_request'", "/home/zxf/logstash-7.15.0/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-11.0.2-java/lib/logstash/outputs/elasticsearch/http_client/pool.rb:300:in `block in get'", "/home/zxf/logstash-7.15.0/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-11.0.2-java/lib/logstash/outputs/elasticsearch/http_client.rb:199:in `get'", "/home/zxf/logstash-7.15.0/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-11.0.2-java/lib/logstash/plugin_mixins/elasticsearch/common.rb:152:in `discover_cluster_uuid'", "/home/zxf/logstash-7.15.0/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-11.0.2-java/lib/logstash/outputs/elasticsearch.rb:308:in `finish_register'", "/home/zxf/logstash-7.15.0/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-11.0.2-java/lib/logstash/outputs/elasticsearch.rb:279:in `block in register'", "/home/zxf/logstash-7.15.0/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-11.0.2-java/lib/logstash/plugin_mixins/elasticsearch/common.rb:145:in `block in after_successful_connection'"]}
[2024-06-14T23:40:07,653][ERROR][logstash.outputs.elasticsearch][main][34fdb55ea05929bf8e49916707c868bf53cef335ed6cce6f91ce5579a973a507] Attempted to send a bulk request but there are no living connections in the pool (perhaps Elasticsearch is unreachable or down?) {:message=>"No Available connections", :exception=>LogStash::Outputs::ElasticSearch::HttpClient::Pool::NoConnectionAvailableError, :will_retry_in_seconds=>2}

This is the error log of version 7.10.0:

[2024-06-14T23:52:08,020][ERROR][logstash.outputs.elasticsearch][main][34fdb55ea05929bf8e49916707c868bf53cef335ed6cce6f91ce5579a973a507] Encountered a retryable error. Will Retry with exponential backoff  {:code=>409, :url=>"http://localhost:9308/_bulk"}
[2024-06-14T23:52:10,129][WARN ][logstash.outputs.elasticsearch][main][34fdb55ea05929bf8e49916707c868bf53cef335ed6cce6f91ce5579a973a507] Marking url as dead. Last error: [LogStash::Outputs::ElasticSearch::HttpClient::Pool::HostUnreachableError] Elasticsearch Unreachable: [http://localhost:9308/][Manticore::ClientProtocolException] localhost:9308 failed to respond {:url=>http://localhost:9308/, :error_message=>"Elasticsearch Unreachable: [http://localhost:9308/][Manticore::ClientProtocolException] localhost:9308 failed to respond", :error_class=>"LogStash::Outputs::ElasticSearch::HttpClient::Pool::HostUnreachableError"}
[2024-06-14T23:52:10,146][ERROR][logstash.outputs.elasticsearch][main][34fdb55ea05929bf8e49916707c868bf53cef335ed6cce6f91ce5579a973a507] Attempted to send a bulk request to elasticsearch' but Elasticsearch appears to be unreachable or down! {:error_message=>"Elasticsearch Unreachable: [http://localhost:9308/][Manticore::ClientProtocolException] localhost:9308 failed to respond", :class=>"LogStash::Outputs::ElasticSearch::HttpClient::Pool::HostUnreachableError", :will_retry_in_seconds=>4}

[sanikolaev]

logstash 7.10.0 works with Manticore - https://play.manticoresearch.com/logstash/

[sanikolaev]

@zhangsanhuo try to understand how your case is different from https://play.manticoresearch.com/logstash/

[zhangsanhuo]

I found the reason. It was because of the Raspberry Pi system. When I used the "Linux new5 6.1.0-17-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.69-1 (2023-12-30) x86_64 GNU/Linux" system, there was no problem with logstash synchronization.

[zhangsanhuo]

Hello,

I found that when the mysql field content is NULL instead of Empty String, importing data to manticore through logstash will report an error:
Attempted to send a bulk request but there are no living connections in the pool (perhaps Elasticsearch is unreachable or down?) {:message=>"No Available connections", :exception=>LogStash::Outputs::ElasticSearch::HttpClient::Pool::NoConnectionAvailableError, :will_retry_in_seconds=>2}

and it will cause the data to be unable to synchronize. I would like to ask if this problem will be fixed? Because there are a lot of Null data in our original database.

Thanks in advance for your response.

[sanikolaev]

Thanks @zhangsanhuo

We'll look into it and fix it if we can reproduce.

[zhangsanhuo]

Hello, I would like to ask, does manticore support search chain operation? Just like this: my_search[left_index:right_index].query(q1).query(q2).query(q3). Or can only BoolFilter be used for combined search?

[tomatolog]

you could use multi query only via SphinxQL interface as described Multi-queries. There is no support of multi query for HTTP REST interface.

You could create another ticket at Github with the feature request.

Or can only BoolFilter be used for combined search?

you could use bool JSON search property to combine multiple search conditions but it produces only single result set. Multi query allows to

Multi-queries, or query batches, allow you to send multiple search queries to Manticore in a single network request.

[sanikolaev]

does manticore support search chain operation? Just like this

The PHP client supports it somewhat - https://github.com/manticoresoftware/manticoresearch-php#perform-a-search

[sanikolaev]

@Nick-S-2018 pls try to reproduce it with NULL values.

[Nick-S-2018]

I've reproduced the error and created another issue based on this one: #2363

[Nick-S-2018]

Blocked by #2363

[zhangsanhuo]

I've reproduced the error and created another issue based on this one: #2363

Could you please add support for manticore fields with bigint attributes and timestamp with Null value?