-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Can v2.3.3 & v3.0.x use the same hbase environment ? #11133
Comments
It is recommended to use v3.0.0 hbase schema with v3.0.0 collector and web (supports hbase 2.4.10). |
Thank you for your reply. Additionally, I have a question related to the upgrade. If we modify the IP (or load balancer VIP) of the v3.3.0 collector to match that of the v2.3.3 collector while the applications with the v2.3.3 agent deployed are currently running. Will the connection between the v2.3.3 agent and the new collector be normal? Because restarting a lot of production applications requires time and carries a certain risk. If a seamless switch is possible, that would be the best. I encountered errors in the v2.5.x test. |
Changes applied in hbase schema during v2.3.3 -> v3.0.0 is backward compatible so it would be fine to gradually deploy v3.0.0 collector while keeping some v2.3.3 collectors connected to altered hbase. Given that all v2.3.3 collectors and v3.0.0 collectors are connected to the same load balancer, and you gradually update each pinpoint collector versions, your applications with v2.3.3 pinpoint agent will be reconnected to the remaining v3.0.0 collector when all your v2.3.3 collectors are shut down. Will you explain further what errors you have encountered with v2.5.x? |
Thank you for your reply, this answer is helpful. ------------------error logs ------------ |
Hello,
I currently use v2.3.3 and Hbase 2.4.10, hope to smoothly upgrade to v3.0.x, and try to reuse the existing server.
I have seen some differences in hbase-create.hbase between pinpoint v2.3.3 and v3.0.0. Is v2.3.3 compatible with the table structure of v3.0.0? Can I modify the current table structure as v3.0.0 so that both versions can use the same hbase environment?
Thank you.
The text was updated successfully, but these errors were encountered: