wouldd commented on issue #7826: URL: https://github.com/apache/incubator-devlake/issues/7826#issuecomment-2615321788
@klesh @caioq I believe I outlined the approach I took to fixing it above. essentially I required all plugins to provide the path to the unique id in any given object being returned so that the persistence layer could use that as the unique key in the database instead of a randomly generated guid. by maintaining a repeatable link between the data retrieved from plugins and that stored in the database I removed the need to empty the databases during a refresh. combined with some improved error handling around deadlock timeouts that I had observed. seemed to fix the issue - I've not had any problems with the setup in the months since I fixed it locally. However obviously this change introduced a significant breaking aspect of requiring that unique id path info for all plugins. easy for me locally to just do that for jira and azd which is all I cared about. There are some fringe issues that crop up since the schema in the db has to support the right keylength etc, and I mentioned needing to update grafana because it had a bug at one point in it's handling of uint64s . We're in the middle of a large migration project at the moment, so I'm not likely to have much time until later in the year when we will be reviewing the setup again etc. but I hope the above make enough sense to base a similar fix off. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@devlake.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
