Rejected, too many requests? 0.27.1

Hi, i think the max concurent request are not in use any more but i get

2019-12-13T03:33:16.620Z	e[31mERRORe[0m	piecestore	upload rejected, too many requests	{"live requests": 9}

2019-12-13T03:35:06.961Z	e[31mERRORe[0m	piecestore	upload rejected, too many requests	{"live requests": 8}

this are the only rejected in my log.

in my config.yml i put a # in front of it and done a restart. This have i done some updates earlyer.

# how frequently bandwidth usage rollups are calculated
# bandwidth.interval: 1h0m0s

# how frequently expired pieces are collected
# collector.interval: 1h0m0s

# use color in user interface
# color: false

# server address of the api gateway and frontend app
console.address: :14002

# path to static resources
# console.static-dir: ""

# Maximum Database Connection Lifetime, -1ns means the stdlib default
# db.conn_max_lifetime: -1ns

# Maximum Amount of Idle Database connections, -1 means the stdlib default
# db.max_idle_conns: 20

# Maximum Amount of Open Database connections, -1 means the stdlib default
# db.max_open_conns: 25

# address to listen on for debug endpoints
debug.addr: :7777

# If set, a path to write a process trace SVG to
# debug.trace-out: ""

# open config in default editor
# edit-conf: false

# help for setup
# help: false

# path to the certificate chain for this identity
identity.cert-path: identity/identity.cert

# path to the private key for this identity
identity.key-path: identity/identity.key

# alpha is a system wide concurrency parameter
# kademlia.alpha: 5

# the Kademlia node to bootstrap against
# kademlia.bootstrap-addr: bootstrap.storj.io:8888

# the base interval to wait when retrying bootstrap
# kademlia.bootstrap-backoff-base: 1s

# the maximum amount of time to wait when retrying bootstrap
# kademlia.bootstrap-backoff-max: 30s

# size of each Kademlia bucket
# kademlia.bucket-size: 20

# the path for storage node db services to be created on
# kademlia.db-path: config/kademlia

# the public address of the Kademlia node, useful for nodes behind NAT
kademlia.external-address: ""

# operator email address
kademlia.operator.email: ""

# operator wallet address
kademlia.operator.wallet: ""

# size of Kademlia replacement cache
# kademlia.replacement-cache-size: 5

# if true, log function filename and line number
# log.caller: false

# if true, set logging to development mode
# log.development: false

# configures log encoding. can either be 'console' or 'json'
# log.encoding: console

# the minimum log level to log
log.level: debug

# can be stdout, stderr, or a filename
# log.output: stderr
log.output: "/app/config/node.log"

# if true, log stack traces
# log.stack: false

# address to send telemetry to
# metrics.addr: collectora.storj.io:9000

# application name for telemetry identification
# metrics.app: storagenode

# application suffix
# metrics.app-suffix: -release

# instance id prefix
# metrics.instance-prefix: ""

# how frequently to send up telemetry
# metrics.interval: 1m0s

# path to log for oom notices
# monkit.hw.oomlog: /var/log/kern.log

# public address to listen on
server.address: :28967

# log all GRPC traffic to zap logger
server.debug-log-traffic: false

# if true, client leaves may contain the most recent certificate revocation for the current certificate
# server.extensions.revocation: true

# if true, client leaves must contain a valid "signed certificate extension" (NB: verified against certs in the peer ca whitelist; i.e. if true, a whitelist must be provided)
# server.extensions.whitelist-signed-leaf: false

# path to the CA cert whitelist (peer identities must be signed by one these to be verified). this will override the default peer whitelist
# server.peer-ca-whitelist-path: ""

# identity version(s) the server will be allowed to talk to
# server.peer-id-versions: latest

# private address to listen on
server.private-address: 127.0.0.1:7778

# url for revocation database (e.g. bolt://some.db OR redis://127.0.0.1:6378?db=2&password=abc123)
# server.revocation-dburl: bolt://config/revocations.db

# if true, uses peer ca whitelist checking
# server.use-peer-ca-whitelist: true

# total allocated bandwidth in bytes
storage.allocated-bandwidth: 2.0 TB

# total allocated disk space in bytes
storage.allocated-disk-space: 1.0 TB

# how frequently Kademlia bucket should be refreshed with node stats
# storage.k-bucket-refresh-interval: 1h0m0s

# path to store data in
# storage.path: config/storage

# a comma-separated list of approved satellite node urls
# storage.whitelisted-satellites: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S@mars.tardigrade.io:7777,118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW@satellite.stefan-benten.de:7777,121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6@saturn.tardigrade.io:7777,12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs@jupiter.tardigrade.io:7777

# how soon before expiration date should things be considered expired
# storage2.expiration-grace-period: 48h0m0s

# how many concurrent requests are allowed, before uploads are rejected.
# storage2.max-concurrent-requests: 6

# how frequently Kademlia bucket should be refreshed with node stats
# storage2.monitor.interval: 1h0m0s

# how much bandwidth a node at minimum has to advertise
# storage2.monitor.minimum-bandwidth: 500.0 GB

# how much disk space a node at minimum has to advertise
# storage2.monitor.minimum-disk-space: 500.0 GB

# how long after OrderLimit creation date are OrderLimits no longer accepted
# storage2.order-limit-grace-period: 1h0m0s

# allows configuration to enable, disable, or test retain requests from the satellite. Options: (disabled/enabled/debug)
# storage2.retain-status: disabled

# allows for small differences in the satellite and storagenode clocks
# storage2.retain-time-buffer: 1h0m0s

# duration between sending
# storage2.sender.interval: 1h0m0s

# timeout for sending
# storage2.sender.timeout: 1h0m0s

# Interval to check the version
# version.check-interval: 15m0s

# Request timeout for version checks
# version.request-timeout: 1m0s

# server address to check its version against
# version.server-address: https://version.alpha.storj.io

# interval between voucher service iterations
# vouchers.interval: 168h0m0s

#storage2.max-concurrent-requests: 20

startparameter + watchtower:

docker run -d --restart unless-stopped \
-p 28967:28967 \
-p 14002:14002 \
-p 7777:7777 \
-e WALLET="0x120B3d8BC249a2c82D890c228*****" \
-e EMAIL="******" \
-e ADDRESS="******:28967" \
-e BANDWIDTH="10TB" \
-e STORAGE="7TB" \
--mount type=bind,source="/opt/storj/identity",destination=/app/identity \
--mount type=bind,source="/opt/storj/data",destination=/app/config \
--name storagenode storjlabs/storagenode:beta

4vcpu 4GbRam
Debian10
docker
hdd direct connect sata

should i write “storage2.max-concurrent-requests” back to config?
node runs fine! only info about the rejected.

I think a limit is still applied to gRPC connection as those can be problematic. Your node will mostly see dRPC connections now which are unlimited.

I’m not sure what causes gRPC connections to still happen.
@littleskunk could you confirm my suspicion and perhaps explain where the gRPC connections still come from?

You can still limit the amount to whatever you want its still in the config its just set to 0 for unlimited.

# how many concurrent requests are allowed, before uploads are rejected. 0 represents unlimited.
# storage2.max-concurrent-requests: 0

Colleagues, please look into this post.