{"action":"created","issue":{"url":"https://api.github.com/repos/elastic/elasticsearch-ruby/issues/535","repository_url":"https://api.github.com/repos/elastic/elasticsearch-ruby","labels_url":"https://api.github.com/repos/elastic/elasticsearch-ruby/issues/535/labels{/name}","comments_url":"https://api.github.com/repos/elastic/elasticsearch-ruby/issues/535/comments","events_url":"https://api.github.com/repos/elastic/elasticsearch-ruby/issues/535/events","html_url":"https://github.com/elastic/elasticsearch-ruby/issues/535","id":346607402,"node_id":"MDU6SXNzdWUzNDY2MDc0MDI=","number":535,"title":"Cannot get new connection from the pool","user":{"login":"sudhanne","id":12982069,"node_id":"MDQ6VXNlcjEyOTgyMDY5","avatar_url":"https://avatars1.githubusercontent.com/u/12982069?v=4","gravatar_id":"","url":"https://api.github.com/users/sudhanne","html_url":"https://github.com/sudhanne","followers_url":"https://api.github.com/users/sudhanne/followers","following_url":"https://api.github.com/users/sudhanne/following{/other_user}","gists_url":"https://api.github.com/users/sudhanne/gists{/gist_id}","starred_url":"https://api.github.com/users/sudhanne/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sudhanne/subscriptions","organizations_url":"https://api.github.com/users/sudhanne/orgs","repos_url":"https://api.github.com/users/sudhanne/repos","events_url":"https://api.github.com/users/sudhanne/events{/privacy}","received_events_url":"https://api.github.com/users/sudhanne/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":5,"created_at":"2018-08-01T13:46:46Z","updated_at":"2018-08-01T17:06:18Z","closed_at":null,"author_association":"NONE","body":"I am trying to track down the source of the following intermittent error I see on my servers:\r\n\r\n“Cannot get new connection from the pool”\r\n\r\nI am connecting to an Elastic Cloud managed cluster in AWS. Under periods of heavy search load (30 QPS) I occasionally see this error coming from my multisearch queries. "},"comment":{"url":"https://api.github.com/repos/elastic/elasticsearch-ruby/issues/comments/409648649","html_url":"https://github.com/elastic/elasticsearch-ruby/issues/535#issuecomment-409648649","issue_url":"https://api.github.com/repos/elastic/elasticsearch-ruby/issues/535","id":409648649,"node_id":"MDEyOklzc3VlQ29tbWVudDQwOTY0ODY0OQ==","user":{"login":"sudhanne","id":12982069,"node_id":"MDQ6VXNlcjEyOTgyMDY5","avatar_url":"https://avatars1.githubusercontent.com/u/12982069?v=4","gravatar_id":"","url":"https://api.github.com/users/sudhanne","html_url":"https://github.com/sudhanne","followers_url":"https://api.github.com/users/sudhanne/followers","following_url":"https://api.github.com/users/sudhanne/following{/other_user}","gists_url":"https://api.github.com/users/sudhanne/gists{/gist_id}","starred_url":"https://api.github.com/users/sudhanne/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sudhanne/subscriptions","organizations_url":"https://api.github.com/users/sudhanne/orgs","repos_url":"https://api.github.com/users/sudhanne/repos","events_url":"https://api.github.com/users/sudhanne/events{/privacy}","received_events_url":"https://api.github.com/users/sudhanne/received_events","type":"User","site_admin":false},"created_at":"2018-08-01T17:06:18Z","updated_at":"2018-08-01T17:06:18Z","author_association":"NONE","body":"Right now I have one singleton instance of the Elasticsearch client shared across the entire application. This means that our bulk indexing jobs as well as our search query requests are all re-using this client instance. \r\n\r\nIs that OK? Should I be splitting this up?"}}
{"actor":{"display_login":"sudhanne"}}