1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
Does it happen on each invocation or only after a few of them? the /tmp remains between invocations in the same sandbox. If it happens in each invocation, need to further investigate. If it only happens after a few invocations, make sure to delete the files that were created in the previous invocations.
BTW, I tried df
and it worked just fine:
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/vdd 4130944 17736 4096824 1% /tmp
Maybe there is something wrong in the way you configured it?
Contenus pertinents
- demandé il y a 2 mois
- demandé il y a 6 mois
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 2 ans
it happens each and every time. The invocation of a DF in the originating lambda shows exactly as you have described, yet when the code is invoked inside of the handler it shows a different space size for /tmp. That is what is throwing me off. Like its a new boto instance created within the lambda handler. Again forgive me if my technical language is a challenge.
What is your function doing? Can you share the code?
What do you mean by "originating lambda"? How many functions do you have?
I have a few functions but when I modify the original lamda code with the following:
def register(cfn): response = cfn.register_type( Type='RESOURCE', TypeName='AWSQS:MYCUSTOM::Manager', SchemaHandlerPackage="s3://xxx/yyy/awsqs-mycustom-manager.zip", LoggingConfig={"LogRoleArn": "xxx", "LogGroupName": "awsqs-mycustom-manager-logs"}, ExecutionRoleArn="xxx" ) dfout = os.popen('df') print( dfout.read())
I can view the cloudwatch logs and see the output for the lambda:
/mnt/root-rw/opt/amazon/asc/worker/tasks/rtfs/python3.7-amzn-201803 8351792 6720731 1626965 81% / /dev/vdd 4229728 18152 4195192 1% /tmp
Which is 4GB and good.
However, when the awsqs-mycustom-manager.zip is updated with the exact same debug:
Filesystem 1K-blocks Used Available Use% Mounted on /mnt/root-rw/opt/amazon/asc/worker/tasks/rtfs/python3.7-amzn-201803 8351792 6720731 1626965 81% / /dev/vdb 1490800 14092 1460324 1% /dev /dev/vdd 538424 876 525712 1% /tmp /dev/root 10190100 552464 9621252 6% /var/rapid /dev/vdc 37120 37120 0 100% /var/task
returns 512MB ...
If I understand correctly, awsqs-mycustom-manager is a new function. As a new function you need to change its configuration as well. It does not inherit the configuration from this function.