tags

LSF data management tag query and cleanup options

Options

Tag query:

bdata tags list [-w] [-u all | -u user_name] [-dmd cluster_name]

Tag cleanup:

bdata tags clean [-u user_name] [-dmd cluster_name] tag_name

Description

The list command displays the names of the known tags.

When the CACHE_ACCESS_CONTROL=Y parameter is configured in lsf.datamanager, the list command displays the user group that the file belongs to. All users (not just the administsrator) can specify the –u option to see tags that are owned by other users.
bdata tags list
NAME      USER    GROUP     LAST_UPLOAD          LAST_DOWNLOAD
code      user1   pcl       06/12/2015 15:50:10  -
tag1      user1   <error>   03/12/2015 13:51:59  -
tag2      user2   test      03/12/2015 13:52:06  -
tag3      user2   test      03/12/2015 13:52:09  -

If a bdata chgrp command did not successfully change the user group of the file, the GROUP column shows <error>.

A dash (-) in the GROUP column of a tag query indicates that CACHE_ACCESS_CONTROL=Y is not configured.

The clean command deletes the tag and all its containing files. Data manager administrators can clean any tags. Ordinary users can clean only their own tags. Each LSF data manager manages its own cache area. You can query and manage tags through -dmd cluster_name option, which redirects the request to the dmd that serves the specified cluster.

Examples

Query known local tags:

bdata tags list -u all
NAME       USER   LAST_UPLOAD           LAST_DOWNLOAD
tag_name1  user1  06/27/2015 16:37:52   06/28/2015 16:37:52
tag_name2  user2  06/23/2015 16:37:52   06/28/2015 16:37:52
tag_name3  user3  06/25/2015 16:37:52   06/30/2015 16:37:52
...

A dash (-) in the LAST_UPLOAD column of a tag query indicates tags that were created, but not finished their first upload:

bdata tags list -u all
NAME       USER   LAST_UPLOAD       LAST_DOWNLOAD
tag_name1  user1  -                 -
tag_name2  user2  -                 -
tag_name3  user3  -                 -
...

In this state, the scheduler does not schedule the job to use the tags until the first upload to the staging area is finished and the LAST_UPLOAD time is set. If the upload fails, the tag stays this way. Use bdata tags clean to clean up the tags for failed uploads.