{"action":"opened","issue":{"url":"https://api.github.com/repos/elastic/elasticsearch/issues/15472","labels_url":"https://api.github.com/repos/elastic/elasticsearch/issues/15472/labels{/name}","comments_url":"https://api.github.com/repos/elastic/elasticsearch/issues/15472/comments","events_url":"https://api.github.com/repos/elastic/elasticsearch/issues/15472/events","html_url":"https://github.com/elastic/elasticsearch/issues/15472","id":122456754,"number":15472,"title":"Evaluate and trim down the thread pools of a TransportClient","user":{"login":"bleskes","id":1006375,"avatar_url":"https://avatars.githubusercontent.com/u/1006375?v=3","gravatar_id":"","url":"https://api.github.com/users/bleskes","html_url":"https://github.com/bleskes","followers_url":"https://api.github.com/users/bleskes/followers","following_url":"https://api.github.com/users/bleskes/following{/other_user}","gists_url":"https://api.github.com/users/bleskes/gists{/gist_id}","starred_url":"https://api.github.com/users/bleskes/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bleskes/subscriptions","organizations_url":"https://api.github.com/users/bleskes/orgs","repos_url":"https://api.github.com/users/bleskes/repos","events_url":"https://api.github.com/users/bleskes/events{/privacy}","received_events_url":"https://api.github.com/users/bleskes/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-12-16T08:58:47Z","updated_at":"2015-12-16T08:58:47Z","closed_at":null,"body":"At the moment, for simplicity, the ThreadPool used by the TransportClient is the same as a full blown node. I.e., we have pools for things like BULK , SEARCH  which are not relevant.  Since we create threads lazily it's typically not a big deal as we will not spawn too many threads. However, it is error prone and conveys the wrong message to people extending functionality around the client like a BulkProcessor.  IMO we should have a trimmed down set."}}