Make CloudSQLite daemon begin its port search starting at 22003 instead of 22002 #873
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nick4598
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
pushing a change to start the port for cloudsqlite daemon at 22003 instead of 22002.
IN an attempt to make our daemon deployment go more smoothly, we are having the daemon auto detect an available port instead of always using 22003. This eliminates errors like 'failed to bind to localhost port 22003' which can sometimes occur during daemon rollout in k8s. This caused the cloudsqlite daemon to start picking 22002 which is a problem because the blockcachevfs (pre 3.3.x of itwinjs) daemon uses 22002. Apparently there are still some backends using the blockcache daemon in prod so...
I tried to change the port to the blockcachevfs daemon but it seems that the private registry has pruned that version of @bentley/imodeljs-native, so we can't redeploy it. This was before we started publishing imodeljs-native to the public npm registry, so that version is gone.