Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Decide on Message format for ActiveMQ Message to AMI #70

Closed
bari12 opened this issue Nov 8, 2017 · 11 comments
Closed

Decide on Message format for ActiveMQ Message to AMI #70

bari12 opened this issue Nov 8, 2017 · 11 comments

Comments

@bari12
Copy link
Member

bari12 commented Nov 8, 2017

Do we need two different messages? One for Dataset one for Container or is the same one sufficient?

Migrated from JIRA RUCIO-2810

@vingar
Copy link
Contributor

vingar commented Nov 10, 2017

Is it related to the INCOMPLETE message ? Do we have another issue related to it ?

Motivation:
When a dataset starts being deleted, If its state change to INCOMPLETE from a previous state != INCOMPLETE, then a message is produced:

        add_message('INCOMPLETE', {'scope': scope, 'name': name})

@bari12
Copy link
Member Author

bari12 commented Nov 10, 2017

Yes, the epic issue for this is #69. I just noticed though, we added the INCOMPLETE state in the schema.sql, but not in models.py or constants.py yet.

@vingar
Copy link
Contributor

vingar commented Nov 10, 2017

I checked on next and could not find the constants change ? models.py is not necessary.

@bari12
Copy link
Member Author

bari12 commented Nov 10, 2017

Yes, as I said, it's not there 😄

@vingar
Copy link
Contributor

vingar commented Nov 10, 2017

but I did the merge request (100% sure)...

@bari12
Copy link
Member Author

bari12 commented Nov 10, 2017

It doesn't seem to be in there. Only schema.sql and the migrate_repo file.
bf36f63

@bari12
Copy link
Member Author

bari12 commented Nov 10, 2017

But just coming back to the original question. I think one message is enough, no need to have one for DATASET and one for CONTAINER.

@vingar
Copy link
Contributor

vingar commented Nov 10, 2017

did_type in the message ?

@bari12
Copy link
Member Author

bari12 commented Nov 10, 2017

Yes, I think so. To some extent it is redundant, as e.g. AMI would know it anyway, but maybe this is consumed by other services too which do not necessarily know.

@vingar
Copy link
Contributor

vingar commented Nov 10, 2017

issue #68 is about 'Protect storage from too many requests ' ?

@bari12
Copy link
Member Author

bari12 commented Nov 10, 2017

You mean about the epic issue link above? I accidentally linked #68 first, but then corrected to #69; Maybe in your eMail it still says the first version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants