Storlet app goes to 503 ServiceUnavaialble when the app doesn't set metadata
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| storlets |
Confirmed
|
High
|
Unassigned | ||
Bug Description
When a storlet app written in python which doesn't set user metadata in the __call__ method (i.e. it doesn't do like out_files[
The actual response from swift client will be like:
Error downloading object 'storlet/test.py': Object GET failed: http://
And syslog said something like:
Dec 27 04:49:56 - object-server: Storlet execution failed: #012Traceback (most re
cent call last):#012 File "/usr/local/
12 raise StorletRuntimeE
For design specification, we need to decide to set empty dict or original metadata from the object when the app does nothing. I bet set original metadata may be useful.
| description: | updated |
| Eran Rom (eranr) wrote | #1 |
| Kota Tsuyuzaki (tsuyuzaki-kota) wrote | #2 |
| summary: |
- python: storlet app goes to 503 ServiceUnavaialble when the app doesn't - set metadata + Storlet app goes to 503 ServiceUnavaialble when the app doesn't set + metadata |
| Eran Rom (eranr) wrote | #3 |
This is true for both Java and Python written storlets.
The initial thought behind this behaviour was to enforce the storlet writer to set the metadata.
I guess that a better behaviour would be:
1. Add a configuration flag: 'storlet_
2. If the value is True then failing to set the metadata should result in an error.
3. If the value is False then upon timeout the middleware should probably set the original metadata of the storlet, while logging an info entry stating so: This can help for the case where the storlet indeed sets the metadata but failed to do so within the timeout.