| Title | Replicator needs restarting when you add new users to Perforce or TeamTrack |
| Status | closed |
| Priority | optional |
| Assigned user | Gareth Rees |
| Organization | Ravenbrook |
| Description | When you add a new user to Perforce or TeamTrack or change a user's e-mail address, you have to restart the replicator. |
| Analysis | This is because the replicator caches the users from Perforce and TeamTrack. If the cache were flushed on a regular basis then there would no longer be any need to do this. GDR 2001-07-19: This is Perforce's job 6081. In fact, this job is only true in the TeamTrack integration. The Bugzilla integration re-reads its user cache whenever there's a miss. [NB 2001-07-25: the AG now reflects this]. Once per poll is the natural point to consider reloading the cache on a miss. But that might lead to the USERS table being reloaded every poll, which is a bad idea. |
| How found | customer |
| Evidence | AG, section 10.3. Customer report: < http://info.ravenbrook.com/mail/2001/07/18/19-30-49/0.txt> |
| Observed in | 0.4.2 |
| Created by | Gareth Rees |
| Created on | 2001-01-02 17:15:00 |
| Last modified by | Gareth Rees |
| Last modified on | 2010-10-06 21:36:14 |
| History | 2001-01-02 GDR Created. 2001-07-19 GDR Noted Perforce's job; added customer report. Noted that it only applies to TeamTrack. Upgraded to essential. 2001-07-25 NB Updated AG to say that this is TeamTrack-specific. |
| Change | Effect | Date | User | Description |
|---|---|---|---|---|
| 14772 | closed | 2001-08-07 19:02:38 | Gareth Rees | The replicator doesn't need restarting when the administrator adds a new user to Perforce or TeamTrack. |
| 14469 | open | 2001-07-25 11:28:07 | Nick Barnes | Bugzilla users don't need to restart when adding users. |