client.ping returns error, but can access es in browser.

client.ping() returns error ResponseError: parsing_exception.

To Reproduce

'use strict'

const { Client } = require('@elastic/elasticsearch')
const client = new Client({ node: 'http://localhost:9200' })

client.ping({
    requestTimeout: 20000,
}, function (error) {
    if (error) {
        console.error('Elasticsearch cluster is down!, ' + error);
    } else {
        console.log('Everything is ok');
    }
});

Expected behavior

A successful connection. 😃

Notes

I can access the server by going to the url in the browser. Also, I’ve indexed a couple documents from node as well -code which ran after I get the error being discussed.

When running ./bin/elasticsearch, I get

OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release. Version: 7.0.0, Build: default/tar/b7e28a7/2019-04-05T22:55:32.697037Z, JVM: 12

I’ve been trying various things, to no avail- adjusting timeout, ‘use strict’, ‘:9200/’, etc. At least I can still use REST. ^_^

Environment

• node version: 11.12.0
• npm: 6.7.0
• @elastic/elasticsearch version: 7.0.0-rc.1
• os: Mac High Siera 10.13.6

[delvedor]

Hello! In the new JavaScript client every option that is not intended for Elasticsearch lives in a second object, your code should be updated as follows:

'use strict'

const { Client } = require('@elastic/elasticsearch')
const client = new Client({ node: 'http://localhost:9200' })

client.ping({}, { requestTimeout: 20000 }, (err, response) => {
 ...
})

In the response object other than body, statusCode, and headers, you will also find a warnings array and a meta object, which should help you debug issues. In this case, warnings contained the following message: 'Client - Unknown parameter: "requestTimeout", sending it as query parameter'.

[oscar6echo]

@delvedor Just checked and on my Elastic the exact name is monitoring_user.
It worked !

Thx a lot for you quick and precise answer.