Document upgrade order for tribe and CCS

Abierto
#30 14 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
30/100
Tipo de issue
Documentación
Claridad
Necesita aclaración
Estado de actividad
Estancado
Área
distributed-systems, documentation

Línea de trabajo

Comienza revisando el resultado de stack-docs issue 17 y el debate de 14 comentarios; después, coordínate con desarrollo sobre el orden de actualización compatible para tribe, CCS y los clústeres posteriores. Se considera terminado cuando las recomendaciones acordadas y cualquier expectativa no compatible sobre actualizaciones progresivas estén documentadas para los clientes.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

This is one area that is not covered today in our docs today.

Even though tribe is deprecated, it is still in the product on 6.x. There will be questions around upgrading tribe node implementations for those who are not ready to switch to CCS yet. Afaik, they need to upgrade the tribe to 6.0 first before the downstream clusters because if the tribe remains on 5.x, it will not be able to join any downstream clusters that have indices created on 6.0. For example, can they upgrade tribe to 6.0 first and then do rolling restarts of downstream 5.6 clusters to 6.0? This is something we will have to sync up with dev on our recommendations. This will probably depend on the outcome of https://github.com/elastic/stack-docs/issues/17, but I do want to make sure that the results are documented :)

Note that some customers may resist switching to CCS right away because, eg.

  • CCS will require that they make changes to their application (not an issue if they use Kibana, but if they don't, then app changes will be needed to use the new CCS syntax).
  • Some customers are more comfortable waiting for a new GA-ed feature to bake in before deploying to production.
  • Or that they need to upgrade to 6.0 to take advantage of some other new features, and prefer to tackle the tribe node piece later

So if we decide that we will not be testing/supporting tribe for rolling upgrades because the tribe node is deprecated, we will just have to document it to set the right expectations upfront.

Even for CCS, there will be questions on upgrade ordering (upgrade CCS first? Downstream clusters?).

Lenguaje dominante
Java
Estrellas
105
Forks
249
Sin PR fusionados en 30 d

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de elastic/stack-docs

Todos los issues de elastic/stack-docs

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.