ServerApp.iopub_data_rate_limit

JupyterHub Zero to JupyterHub on Kubernetes
1

Hello. I deployed jupyterhub using helm chart v.2.0.0 and jupyterhub version 3.4.6. I get an error when doing a task. !!! I tried to set the jupyter notebook parameter --NotebookApp.iopub_data_rate_limit=100000000 when building docker, but I get ‘iopub_data_rate_limit’ has moved from NotebookApp to ServerApp. I went to change the file jupyterhub_config.py . I’ve been making c options.ServerApp.iopub_data_rate_limit = 100000000 and c.JupyterHub.iopub_data_rate_limit = 100000000 and the parameter is changed in /usr/local/etc/jupyterhub/config of my hub pod, but I keep getting the error. Can you tell me what I’m doing wrong? Is there a wrong directive or syntax in the configuration?

2

Config parameter iopub_data_rate_limit is on Jupyter Server and not JupyterHub. So, you can set it in your user home ~/.jupyter/jupyter_server_config.py using c.ServerApp.iopub_data_rate_limit = 100000000.

1 Like
3

Can you tell me how to do this for helm chart? I can’t find where to apply this parameter.

4

I dont have a lot of experience on how to do it on Kubernetes context. So, I am not quite sure what is the best way to do it. Seems like extraFiles can be a way to do it?

5

Yup, extraFiles ought to work for this, e.g.

singleuser:
  extraFiles:
    # The file key is just a reference that doesn't influence the
    # actual file name.
    singleUserConfig:
      mountPath: /usr/local/etc/jupyter/jupyter_server_config.json
      data:
        ServerApp:
          iopub_data_rate_limit: 100000000
6

Thank you very much! You’ve made my life better. I hope this will be useful to other people on google))