You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just an idea, but in my case I have static collection of 20 repositories and other 60 repos that are using different branches in different cases. I wonder how tricky it would be to be separate index process from UI and allowing UI to tap to more than one index.
So I would end up with multiple indexers working with their set of repos and UI that can query against content provided by multiple of them.
It would also help with reindexing I guess, as I could run second indexing service to prepare new indexes, and when its done just update UI configuration, while up to now I have to run second application in local mode, then when its ready stop them and swap their configs. this change would introduce no downtime requirement
The text was updated successfully, but these errors were encountered:
This is sitting in master branch now. Need to observe it in test for a long time before this gets marked as done. The main thing I am worried about is the background running tasks suspending and terminating when requested by the index. However you can now reindex everything without causing any downtime.
Just an idea, but in my case I have static collection of 20 repositories and other 60 repos that are using different branches in different cases. I wonder how tricky it would be to be separate index process from UI and allowing UI to tap to more than one index.
So I would end up with multiple indexers working with their set of repos and UI that can query against content provided by multiple of them.
It would also help with reindexing I guess, as I could run second indexing service to prepare new indexes, and when its done just update UI configuration, while up to now I have to run second application in local mode, then when its ready stop them and swap their configs. this change would introduce no downtime requirement
The text was updated successfully, but these errors were encountered: