up to Managing distribution on the server side
We have distTargets that define data and rcDestinations that define destinations. The files that get posted to destination's data store are specified by an rcInterest.
Data gets bundled when there is a destination that has expressed interset in a target.
This table is rather boring to look at alone
mysql> select rcInterest.* from rcInterest join distTarget using(target_id) where dist_group = 'MD01' and stage = 'warp'; +--------+---------+-----------+---------+ | int_id | dest_id | target_id | state | +--------+---------+-----------+---------+ | 1393 | 20 | 742 | enabled | | 1394 | 20 | 744 | enabled | | 1395 | 20 | 743 | enabled | | 1396 | 20 | 746 | enabled | | 1397 | 20 | 745 | enabled | +--------+---------+-----------+---------+
What's going on is more instructive when the table is joined with the targets
mysql> select * from rcInterest join distTarget using(target_id) where dist_group = 'MD01' and stage = 'warp'; +-----------+--------+---------+---------+------------+---------+-------+-------+---------+---------+ | target_id | int_id | dest_id | state | dist_group | filter | stage | clean | state | comment | +-----------+--------+---------+---------+------------+---------+-------+-------+---------+---------+ | 742 | 1393 | 20 | enabled | MD01 | g.00000 | warp | 0 | enabled | NULL | | 744 | 1394 | 20 | enabled | MD01 | i.00000 | warp | 0 | enabled | NULL | | 743 | 1395 | 20 | enabled | MD01 | r.00000 | warp | 0 | enabled | NULL | | 746 | 1396 | 20 | enabled | MD01 | y.00000 | warp | 0 | enabled | NULL | | 745 | 1397 | 20 | enabled | MD01 | z.00000 | warp | 0 | enabled | NULL | +-----------+--------+---------+---------+------------+---------+-------+-------+---------+---------+
The first interest in the table above might have been added by the command
disttool -defineinterest -dest_name ps1-200910-2 -dist_group MD01 -stage warp -filter g.00000
Last modified
17 years ago
Last modified on Oct 15, 2009, 12:54:26 PM
Note:
See TracWiki
for help on using the wiki.
