Hi Tauseef,
That's really dependent on the environment you're actually running in. But I'm
guessing you're using ingress to route your requests to the JM POD.
If so, I'd suggest you adjust the value of
nginx.ingress.kubernetes.io/proxy-body-size.
Following is an example.
```
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
annotations:
kubernetes.io/ingress.class: nginx
nginx.ingress.kubernetes.io/proxy-body-size: 250m # change this
name: xxx
namespace: xxx
spec:
rules:
- host: flink-nyquist.hvreaning.com
http:
paths:
- backend:
serviceName: xxx
servicePort: 8081
```
Please let me know if there are any other problems.
Best,Yu Chen
> 2023年11月7日 18:40，Tauseef Janvekar <tauseefjanve...@gmail.com> 写道：
>
> Hi Chen,
>
> We are not using nginx anywhere on the server(kubernetes cluster) or on my
> client(my local machine).
> Not sure how to proceed on this.
>
> Thanks,
> Tauseef
>
> On Tue, 7 Nov 2023 at 13:36, Yu Chen <yuchen.e...@gmail.com> wrote:
> Hi Tauseef,
>
> The error was caused by the nginx configuration and was not a flink problem.
>
> You can find many related solutions on the web [1].
>
> Best,
> Yu Chen
>
> [1]
> https://stackoverflow.com/questions/24306335/413-request-entity-too-large-file-upload-issue
>
>> 2023年11月7日 15:14，Tauseef Janvekar <tauseefjanve...@gmail.com> 写道：
>>
>> Hi Chen,
>>
>> Now I get a different error message.
>> root@R914SK4W:~/learn-building-flink-applications-in-java-exercises/exercises#
>> curl -X POST -H "Expect:" -F "jarfile=@./target/travel-i
>> tinerary-0.1.jar" https://flink-nyquist.hvreaning.com/jars/upload
>> <html>
>> <head><title>413 Request Entity Too Large</title></head>
>> <body>
>> <center><h1>413 Request Entity Too Large</h1></center>
>> <hr><center>nginx</center>
>> </body>
>> </html>
>>
>> Thanks
>> Tauseef
>>
>> On Tue, 7 Nov 2023 at 06:19, Chen Yu <yuchen.e...@gmail.com> wrote:
>> Hi Tauseef,
>>
>> Adding an @ sign before the path will resolve your problem.
>> And I verified that both web and postman upload the jar file properly on the
>> master branch code.
>> If you are still having problems then you can provide some more detailed
>> information.
>>
>> Here are some documents of curl by `man curl`.
>>
>> -F, --form <name=content>
>> (HTTP SMTP IMAP) For HTTP protocol family, this lets curl
>> emulate a filled-in form in which a user has
>> pressed the submit button. This causes curl to POST data using
>> the Content-Type multipart/form-data ac‐
>> cording to RFC 2388.
>>
>> For SMTP and IMAP protocols, this is the means to compose a
>> multipart mail message to transmit.
>>
>> This enables uploading of binary files etc. To force the
>> 'content' part to be a file, prefix the file
>> name with an @ sign. To just get the content part from a
>> file, prefix the file name with the symbol <.
>> The difference between @ and < is then that @ makes a file get
>> attached in the post as a file upload,
>> while the < makes a text field and just get the contents for
>> that text field from a file.
>>
>>
>> Best,
>> Yu Chen
>> 发件人: Tauseef Janvekar <tauseefjanve...@gmail.com>
>> 发送时间: 2023年11月6日 22:27
>> 收件人: user@flink.apache.org <user@flink.apache.org>
>> 主题: Error in /jars/upload curl request I am using curl request to upload a
>> jar but it throws the below error
>>
>> <image.png>
>> Received unknown attribute jarfile.
>>
>> Not sure what is wrong here. I am following the standard documentation
>> https://nightlies.apache.org/flink/flink-docs-master/docs/ops/rest_api/
>>
>> Please let me know if I have to use some other command to upload a jar using
>> "/jars/upload" endpoint
>>
>> I also tried to upload using webui but it hangs continuously and only calls
>> GET api with 200 success- https://flink-nyquist.hvreaning.com/jars
>>
>> Thanks,
>> Tauseef
>
