wsk activation poll when invoked without any explicit time parameters performs a query like

/api/v1/namespaces/_/activations?docs=true&limit=0&since=1542422386538&skip=0

Where it fetches full docs without any explicit limit and since set to epoch time at the start of poll. At times we have seen queries where the difference between current time and since is in days

[2018-12-04T15:15:10.467Z] [INFO] [#tid_1rrQBHlr8f8Xomky3qi3fsELzTIpH7CB] GET /api/v1/namespaces/_/activations docs=true&limit=0&since=1543338217244&skip=0

Here 1543338217244 is ~ Nov-27. This happens because some developers tend to leave poll command running in some forgotten console tab. Due to this each such poll command tries to fetch same set of 200 records (due to limit=0) over and over again putting load on db