# Http\_poller time out error

**URL:** <https://discuss.elastic.co/t/http-poller-time-out-error/359099>\
**Category:** Logstash\
**Created:** [May 8, 2024, 7:14pm UTC](https://discuss.elastic.co/t/http-poller-time-out-error/359099 "2024-05-08T19:14:18Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![kishorkumar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kishorkumar/32/132930_2.png) [@kishorkumar](https://discuss.elastic.co/u/kishorkumar)\
**Post date:** [May 8, 2024, 7:14pm UTC](https://discuss.elastic.co/t/http-poller-time-out-error/359099/1 "2024-05-08T19:14:18Z")

</div>

we are recieving the timeout error in http\_poller by connecting it to guardium,

our database is guardium .  
my http pollar settings as follow

```auto

input {
    http_poller {
        urls = > {
            
            "d1" {
                method => post
                url => "https://*:3/restAPI/*"
                headers => {
                }
                body => {
                }   
            }
            "d2" {
                method => post
                url => "https://*:/restAPI/*"
                headers => {
                }
                body => {
                }   
            }

            schedule => {cron => "*/1 * * * *"}
            ssl_verification_mode => none
            request_timeout => 360
            connect_timeout => 60
            socket_timeout => 240
            keepalive => false
            codec => "json"
        }
    }
}

```

and another question how the multiple requests works they get request sequentally one by one and wait for the first to complete, or they runs parallel , if it runs parallel then what if the first request fails will it not wait for the first request to complete and it send the second request , or it will run the second request.

thing is we can increase the schedule time as we have 15000+ logs in every minute so let me know what is the solution to fix this ?

#logstash#Logstash

---

<div class="post-metadata">

**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\
**Post date:** [May 8, 2024, 7:45pm UTC](https://discuss.elastic.co/t/http-poller-time-out-error/359099/2 "2024-05-08T19:45:43Z")

</div>

If you look at the [code](https://github.com/logstash-plugins/logstash-input-http_poller/blob/43b14cdce985910141f1f0e9172c3d0124ad8b80/lib/logstash/inputs/http_poller.rb#L188), there is a single scheduler thread that runs the cron schedule.

When it runs (once a minute for your schedule) it spins off an async request for each URL. As far as I can see, that's it. If you have a 6-minute request timeout for two URLs then I think you could have 12 requests outstanding.

I wouldn't worry about throughput until you can get requests to process _at all_ without timeouts.