Deploy D1 to Production

[analogrelay]

Deployment D1

Status: Deployed

Focus: Improve search relevance

Services Deployed:

• Search v3.0.15 - https://nuget-octopus.cloudapp.net/app#/projects/projects-33/releases/3.0.15-r-master/deployments/deployments-122
• Gallery v3.0.6 - https://nuget-octopus.cloudapp.net/app#/projects/projects-98/releases/3.0.6-r-master/deployments/deployments-127
• Work v3.0.7 - https://nuget-octopus.cloudapp.net/app#/projects/projects-97/releases/3.0.7-r-master/deployments/deployments-120

Bugs Fixed: https://github.com/NuGet/NuGetGallery/issues?milestone=49&page=1&state=closed

Deployment Process

• Promote Work Service to target environment using Octopus
• Wait for the Work Service deployment to complete, it will take 30-40mins.
• From nuops, with the target environment selected, run:

nucmd work invoke -j RebuildSearchIndex -p "{'StorageContainerName':'ng-search-secondary'}"

NOTE The index will take a while to build, but this command will return immediately. You can continue with deployment, but the search service will only be searching the portions of the index which have finished building. The NumDocs field at the /search/diag endpoint will tell you how many documents the Search Service is searching. When it reaches about 250,000, the whole index should be ready.

• Also:

nucmd work invoke -j GenerateSearchRankings -p "{'DestinationContainerName':'ng-search-secondary'}"

• And:

nucmd work invoke -j GenerateDownloadCountReport -p "{'DestinationContainerName':'ng-search-secondary'}"

• Schedule the GenerateSearchRankings, GenerateDownloadCountReport and UpdateSearchIndex jobs to run against the new search container:

nucmd azure login
nucmd scheduler newjob -dc 0 -sing -j UpdateSearchIndex -i UpdateSearchIndex_Secondary -f Minute -in  1 -p "{'StorageContainerName':'ng-search-secondary'}"
nucmd scheduler newjob -dc 0 -sing -j GenerateSearchRankings -i GenerateSearchRankings_Secondary -f Day -in  1 -p "{'DestinationContainerName':'ng-search-secondary'}"
nucmd scheduler newjob -dc 0 -sing -j GenerateDownloadCountReport -i GenerateDownloadCountReport_Secondary -f Minute -in  5 -p "{'DestinationContainerName':'ng-search-secondary'}"

• Update Search CSCFG to use "ng-search-secondary" (Make sure to PUSH this change to the deployment repository!)
• Promote Search Service to target environment using Octopus

Pull Requests/Interesting Commits

• Fix NuGet/NuGetGallery#2037 by reading download count report NuGetArchive/NuGet.Services.Search#18
• Fix NuGet/NuGetGallery#2037 by adding a download count report job to the work service NuGet.Services.Work#16
• removed range from ranking score calculation NuGetArchive/NuGet.Services.Search#17
• NuGetArchive/NuGet.Services.Search@de7fa5b

[danliu]

For this issue #2047, what fixes were made exactly?

[analogrelay]

It's a dupe, I closed it and referenced the dupe

[danliu]

How often does the job run? After the fix, shall I expect the download numbers to be the same or diff by a small number? What about the download numbers in the statistic pages.

[analogrelay]

I'll schedule the job to run every 5 minutes for now, we can see how that goes.

[analogrelay]

@danliu Btw, you can go ahead and consider the list of issues resolved complete, I'm basically just doing final testing in dev now.