hit exception writing heading bytes XXXXX about remoteshuffleservice HOT 8 CLOSED

There is max bytes limit in shuffle server to protect the server, see https://github.com/uber/RemoteShuffleService/blob/master/src/main/java/com/uber/rss/execution/ShuffleExecutor.java#L81

You could change that value if your shuffle data exceeds that limit.

from remoteshuffleservice.

Thanks,I'll try it

from remoteshuffleservice.

Hi, @Lobo2008 Let us know as Bo mentioned, if the max app shuffle data size per server is the issue or not. You should see a RssTooMuchDataException in the stack trace.

If that's not the issue, please check

• are you using the latest master
• what's task time of the failing task and shuffle data written

from remoteshuffleservice.

Hi @mayurdb

• It's the latest version. I cloned and compiled the master branch in April 2022.
• no RssTooMuchDataException ever happened, just RssNetworkException
• I have re-run the app without change the size as Bo mentioned ( i'll try it later) and so far it runs well. I'll post the detail if the application finished or failed
• Wonder if the DEFAULT_APP_MAX_WRITE_BYTES=3TB is one stage shuffle size limitation or the accumulative size of all the shuffle write(?) stages for one application ? Stage-6 has 3TB but still works fine.

from remoteshuffleservice.

I think that DEFAULT_APP_MAX_WRITE_BYTES is actually per server, so if you write 3TB of data but evenly distribute it to multiple servers you would not run into the issue

from remoteshuffleservice.

I think that DEFAULT_APP_MAX_WRITE_BYTES is actually per server, so if you write 3TB of data but evenly distribute it to multiple servers you would not run into the issue

I guess so.

from remoteshuffleservice.

Hi @mayurdb

• It's the latest version. I cloned and compiled the master branch in April 2022.
• no RssTooMuchDataException ever happened, just RssNetworkException
• I have re-run the app without change the size as Bo mentioned ( i'll try it later) and so far it runs well. I'll post the detail if the application finished or failed
• Wonder if the DEFAULT_APP_MAX_WRITE_BYTES=3TB is one stage shuffle size limitation or the accumulative size of all the shuffle write(?) stages for one application ? Stage-6 has 3TB but still works fine.

Finished successfully. But I found that the exception hit exception writing heading bytes is caused by one or some of RSS running out of disk storage space.

from remoteshuffleservice.

Cool, glad you found the cause, and thanks for the update!

from remoteshuffleservice.