This repository has been archived by the owner on Apr 17, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
ingress: nginx - could not build map_hash #1817
Comments
kayrus
changed the title
ingress: nginx - could not build map_hashcould not build map_hash
ingress: nginx - could not build map_hash
Oct 1, 2016
@aledbf 0.8.3
|
k8s-github-robot
pushed a commit
that referenced
this issue
Nov 3, 2016
Automatic merge from submit-queue Make map_hash_bucket_size configurable I was getting an error while trying to run the nginx controller in minikube. This allows this nginx configuration option to be passed in through a configmap. The default value depends on the processor's cache line size (32 | 64 | 128), however ServerNameHashBucketSize is determined similarly, so I've set it to the same default (64). Fixes #1817 ref kubernetes/minikube#611 cc @bprashanth
aledbf
pushed a commit
to aledbf/contrib
that referenced
this issue
Nov 10, 2016
…size Automatic merge from submit-queue Make map_hash_bucket_size configurable I was getting an error while trying to run the nginx controller in minikube. This allows this nginx configuration option to be passed in through a configmap. The default value depends on the processor's cache line size (32 | 64 | 128), however ServerNameHashBucketSize is determined similarly, so I've set it to the same default (64). Fixes kubernetes-retired#1817 ref kubernetes/minikube#611 cc @bprashanth
Hi,
My config
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Same issue I faced months ago when I provided new nginx config in this PR #1310.
Today I faced it again. But the only difference - I use docker 1.11.2 and HDD instead of 1.12 and SSD. Same Ubuntu Xenial VMs with the same amount of RAM.
I successfully reproduced this error message on pure docker container with this config:
https://gist.github.com/kayrus/dcc092fe2b80b268d01dc591cfcec89a
for some reason increasing
map_hash_bucket_size
didn't help me months ago. But today it helped (map_hash_bucket_size 64;
). Most probably it's worth to makemap_hash_bucket_size
option configurable in ingress.The text was updated successfully, but these errors were encountered: