-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PB-82: prepare migration to k8s #597
Conversation
775f470
to
3993ee1
Compare
3993ee1
to
c7e0142
Compare
needed during the parallel operations of service-search-sphinx on infra-vhost and k8s. on k8s we are forced to mount the efs indexes with the full path: so this will be the folder with the efs index files: * /var/local/geodata/service-sphinxsearch/${DBSTAGING}/index this is due to a limitation of the aws efs csi driver which is not supporting subpaths as volumemount config. we would have to create new peristant volumes with terraform which is unreasonable for this special use-case.
c7e0142
to
a99846d
Compare
9592ac0
to
29d35e1
Compare
I don't have the full picture here, but I'm wondering if it would not be better to have a dedicated EFS Access Point for sphinx index sharing instead of reusing the /prod and /dev of our geodata EFS ? We could reuse the geodata EFS but use another access point to better separate the search index from the geodata. This would not add more cost and would be clearer in the configuration. If sphinx needs also the geodata for indexing it can still mount both the geodata /prod|/dev and the new access point /service-search-sphinx-index-dev|int|prod |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As far as I can tell, looks good.
@ltshb |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
i will merge this now so that we can observe sphinx on k8s on dev under real-life conditions. |
a few changes in the dockerfile and in the efs sync script are needed during the parallel operations of service-search-sphinx on infra-vhost and k8s.
on k8s we are forced to mount the efs indexes with the full path: so this will be the folder with the efs index files:
/var/local/geodata/service-sphinxsearch/${DBSTAGING}/index
this is due to a limitation of the aws efs csi driver which is not supporting subpaths as volumemount config. we would have to create new peristant volumes with terraform which is unreasonable for this special use-case.