the level of configurability in this thing is one of the best I've seen

pgrep -af trains shows that there is nothing running with that name

I'll try to put it again

and I'm using the same credentials

It's working! 😄

And yes, it makes perfect sense, thanks for the answer

I'll try it

Do you have any idea as to why does that happen SuccessfulKoala55

I have a single IAM, my question is what kind of permissions I should associate with the IAM so that the autoscaler task will work

?

yep

SuccessfulKoala55 AppetizingMouse58

[ec2-user@ip-10-0-0-95 ~]$ df -h Filesystem Size Used Avail Use% Mounted on devtmpfs 3.9G 0 3.9G 0% /dev tmpfs 3.9G 0 3.9G 0% /dev/shm tmpfs 3.9G 880K 3.9G 1% /run tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup /dev/nvme0n1p1 8.0G 6.5G 1.5G 82% / tmpfs 790M 0 790M 0% /run/user/1000

that is because my own machine has 10.2 (not the docker, the machine the agent is on)

e.g. docker-compose restart

Let's try

But does it disable the agent? or will the tasks still wait for the agent to dequeue?

Okay, I'll try that

Actually I removed the key pair, as you said it wasn't a must in the newer versions

So prior to doing any work on the trains autoscaler servcice, I should first create a auto scaling group in AWS?

😅

doesn't contain the number 4

Hi FriendlySquid61 I did all the changes you said

What about permissions to the machines that are being spun up? For exampel if I want the instances to have specific permissions to read/write to S3 for example, how do I mange those?

same result

Gotcha

AgitatedDove14 I really don't know how is this possible... I tried upgrading the server, tried whatever I could

About small toy code to reproduce I just don't have the time for that, but I will paste the callback I am using to this explanation. This is the overall logic so you can replicate and use my callback

From the pipeline task, launch some sub tasks, and put in their post_execute_callback the .collect_description_tables method from my callback class (attached below) Run t...

this is the full one TimelyPenguin76

Maybe something similar to dockers, that I could name each one of my trains agents and then refer to them by name something like

trains-agent daemon --name agent_1 ...

Then
trains-agent stop/start

I've dealt with this earlier today because I set up 2 agents, one for each GPU on a machine, and after editing configurations I wanted to restart only one of them (because the other was working) and then I noticed I don't know which one to kill

I can try something with $(pwd)

But I'm naive enough to believe that 10.2 is compatible with 10.1 as it is a minor upgrade