{"action":"created","issue":{"url":"https://api.github.com/repos/jprante/elasticsearch-jdbc/issues/752","repository_url":"https://api.github.com/repos/jprante/elasticsearch-jdbc","labels_url":"https://api.github.com/repos/jprante/elasticsearch-jdbc/issues/752/labels{/name}","comments_url":"https://api.github.com/repos/jprante/elasticsearch-jdbc/issues/752/comments","events_url":"https://api.github.com/repos/jprante/elasticsearch-jdbc/issues/752/events","html_url":"https://github.com/jprante/elasticsearch-jdbc/issues/752","id":125956287,"number":752,"title":"CPU usage rising with elasticsearch-jdbc 2.1.0.0","user":{"login":"artholl","id":15691781,"avatar_url":"https://avatars.githubusercontent.com/u/15691781?v=3","gravatar_id":"","url":"https://api.github.com/users/artholl","html_url":"https://github.com/artholl","followers_url":"https://api.github.com/users/artholl/followers","following_url":"https://api.github.com/users/artholl/following{/other_user}","gists_url":"https://api.github.com/users/artholl/gists{/gist_id}","starred_url":"https://api.github.com/users/artholl/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/artholl/subscriptions","organizations_url":"https://api.github.com/users/artholl/orgs","repos_url":"https://api.github.com/users/artholl/repos","events_url":"https://api.github.com/users/artholl/events{/privacy}","received_events_url":"https://api.github.com/users/artholl/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":12,"created_at":"2016-01-11T14:29:54Z","updated_at":"2016-07-07T16:02:52Z","closed_at":null,"body":"Hi!\r\nPreviously working on jdbc importer and elasticsearch with version 1.7.0.1 and 1.7.0, everything was working fine with your elasticsearch-jdbc.\r\n\r\nNevertheless, I'm now using elasticsearch version 2.1.0 and JDBC Importer 2.1.0.0 and I am facing an issue with the CPU usage of the JDBC Importer.\r\n\r\nYou can see the cpu_usage_per_process acquired through topbeat but I can see the same fact (the cpu usage is linearly growing) with other tools.\r\n\r\n![cpu_usage_jdbc_es](https://cloud.githubusercontent.com/assets/15691781/12235836/a1fb1974-b876-11e5-9f7d-50201c7f730b.png)\r\nHere is part of my configuration:\r\n{\r\n  \"type\": \"jdbc\",\r\n  \"jdbc\": {\r\n    \"driver\": \"org.postgresql.Driver\",\r\n    \"strategy\": \"simple\",\r\n    \"schedule\": \"30 0/1 * ? * *\",\r\n    \"url\": \"%DB_URI%\",\r\n    \"user\": \"%DB_USER%\",\r\n    \"password\": \"%DB_PASSWORD%\",\r\n    \"index\": \"test\",\r\n    \"type\": \"test_product\",\r\n    \"sql\": {\r\n      \"statement\": \"/usr/share/elasticsearch/scripts/update.sql\",\r\n      \"parameter\": [\"$metrics.lastexecutionstart\", \"$metrics.lastexecutionstart\"]\r\n    }\r\n  }\r\n}\r\nAnd I know that the sql script don't get any rows. So we can eliminate that from cpu usage.\r\n\r\nIs that a known issue? Am I the only one facing that phenomenon? \r\nI could provide the logging in debug mode but I didn't see anything which seems abnormal. If you want some data don't hesitate!\r\n\r\nPS: Here is some of the INFO of the logger:\r\n[14:16:30,003][INFO ][importer.jdbc            ][pool-2-thread-2] index name = test, concrete index name = test\r\n[14:16:30,008][INFO ][importer.jdbc            ][pool-516-thread-1] strategy simple: settings = \"******\" (my_settings :))\r\n[14:16:30,008][INFO ][importer.jdbc.context.standard][pool-516-thread-1] found sink class org.xbib.elasticsearch.jdbc.strategy.standard.StandardSink@30f223c2\r\n[14:16:30,009][INFO ][importer.jdbc.context.standard][pool-516-thread-1] found source class org.xbib.elasticsearch.jdbc.strategy.standard.StandardSource@a3be548\r\n[14:16:30,009][INFO ][org.xbib.elasticsearch.helper.client.BaseTransportClient][pool-516-thread-1] creating transport client on Linux OpenJDK 64-Bit Server VM Oracle Corporation 1.8.0_66-internal-b17 25.66-b17 with effective settings {autodiscover=false, client.transport.ignore_cluster_name=false, client.transport.nodes_sampler_interval=5s, client.transport.ping_timeout=5s,\r\n[14:16:30,010][INFO ][org.elasticsearch.plugins][pool-516-thread-1] [importer] loaded [helper], sites []\r\n[14:16:30,109][INFO ][org.xbib.elasticsearch.helper.client.BaseTransportClient][pool-516-thread-1] trying to connect to [localhost/127.0.0.1:9300]\r\n[14:16:30,136][INFO ][org.xbib.elasticsearch.helper.client.BaseTransportClient][pool-516-thread-1] connected to [{Outrage}{YOoML0EdQ5aQyEh8FOWm8A}{172.17.4.47}{localhost/127.0.0.1:9300}]\r\n[14:16:30,142][INFO ][importer.jdbc.sink.standard][pool-516-thread-1] creating index test with settings =  and mappings =\r\n[14:16:30,160][WARN ][importer.jdbc.sink.standard][pool-516-thread-1] already exists\r\n\r\nArthur\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/jprante/elasticsearch-jdbc/issues/comments/231125633","html_url":"https://github.com/jprante/elasticsearch-jdbc/issues/752#issuecomment-231125633","issue_url":"https://api.github.com/repos/jprante/elasticsearch-jdbc/issues/752","id":231125633,"user":{"login":"adamlepkowski","id":1699933,"avatar_url":"https://avatars.githubusercontent.com/u/1699933?v=3","gravatar_id":"","url":"https://api.github.com/users/adamlepkowski","html_url":"https://github.com/adamlepkowski","followers_url":"https://api.github.com/users/adamlepkowski/followers","following_url":"https://api.github.com/users/adamlepkowski/following{/other_user}","gists_url":"https://api.github.com/users/adamlepkowski/gists{/gist_id}","starred_url":"https://api.github.com/users/adamlepkowski/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/adamlepkowski/subscriptions","organizations_url":"https://api.github.com/users/adamlepkowski/orgs","repos_url":"https://api.github.com/users/adamlepkowski/repos","events_url":"https://api.github.com/users/adamlepkowski/events{/privacy}","received_events_url":"https://api.github.com/users/adamlepkowski/received_events","type":"User","site_admin":false},"created_at":"2016-07-07T16:02:52Z","updated_at":"2016-07-07T16:02:52Z","body":"It looks familiar I will deploy it tommorow and verify whether it works."}}
{"actor":{"display_login":"adamlepkowski"}}