Upgrade App Services
- Capella Operational
Scheduling for Capella App Services
|
From App Services 3.1.8, all configurations previously defined in bucket mode will now be under the _default scope and collection. For example, Access Control functions or Import Filters created in bucket mode prior to App Services 3.1.8 will be listed under the _default scope and collection. |
The underlying framework used by App Services will require periodic upgrading as new versions are rolled out. These upgrades can be scheduled on a per-App Service basis to ensure that they occur at the time best suited to maintain high availability for your services. You can also log incidents and maintenance requests.
App Services Version Support
You can deploy and upgrade clusters to new versions of the App Services framework as they become available.
In general, releases follow this pattern:
| Release | Introduces |
|---|---|
Major |
Major new features and functionality. |
Minor |
Some new features or improvements. |
Patch |
Essential fixes and improvements. |
The App Service framework versions offered in Capella are supported until they reach the end of maintenance. This support typically aligns with the full maintenance lifespan of the major or minor version provided by Couchbase. (See App Service Version Maintenance Support.)
To provide secure and reliable service, the version of the App Service framework deployed will be the latest available patch version. You can expect to be upgraded to the latest patch version shortly after it becomes available on Capella.
When maintenance or an upgrade is scheduled, you can choose to upgrade your App Service framework at any time before the scheduled date. When the scheduled time is reached, the framework is upgraded automatically. The notice that Capella aims to provide varies depending on the nature of the upgrade. See App Services Upgrade Timeframes.
App Services Upgrade Timeframes
Similar to cluster maintenance jobs, App Service upgrades have 2 different kinds of timeframes:
-
Notice period: the interval of time between when the upgrade maintenance job is created (and maintenance notifications are sent) and the scheduled upgrade date (target start time). You receive notification emails when Capella schedules an upgrade maintenance job. For more information, see Manage Upgrade Email Notifications.
-
Upgrade window: the interval of time during which the upgrade can begin. This time is dependent on the upgrade type and begins after the notice periods ends, allowing customers to adjust the upgrade schedule as needed. For more information, see Reschedule a Maintenance Job.
For more details about the different types of App Service maintenance jobs and their respective timeframes, see the following table:
| Upgrade or Maintenance Type | Description | Timeframe |
|---|---|---|
Critical Upgrade |
An upgrade done in response to an urgent bug, vulnerability, or other issue impacting cluster health or performance. |
None. |
Routine Maintenance or App Services Framework Patch |
A new App Services patch version or routine image upgrades. |
A typical App Service maintenance job has a 1 week notice period. It includes an upgrade window of 1 week after the notice period ends, allowing customers to adjust the upgrade schedule as needed. |
App Services Framework Minor Release |
A new App Services minor version release. |
From launch on Capella to end of support on Capella. |
App Services Framework Major Release |
A new App Services major release version. |
From launch on Capella to end of support on Capella. |
| A shorter than best practice period might apply depending on particular circumstances. |
Maintenance Jobs
Maintenance job statuses are pending, running, and completed.
All upgrades and maintenance patches have a target start time. Capella aims to start the maintenance of your App Services at this time. However, maintenance jobs are sometimes delayed when the App Services cannot be upgraded. For example, when an underlying cluster is reconfiguring.
For each individual maintenance job, you can:
-
View its type, status, and scheduled time to upgrade.
-
Review its overview and what’s new.
-
Reschedule it to upgrade at a different time.
-
Set a preferred time to upgrade.
-
Create a support ticket.
When a maintenance job runs, the App Service is moved to a pending state.
Maintenance redeployments are not time-bound, and the time taken varies depending on the size of framework upgrade.
View Individual Maintenance Jobs
You can view scheduled maintenance upgrade jobs for your App Service:
-
From the project page, select the App Services tab.
-
Select the App Service you wish to schedule.
-
Click through to access the App Service maintenance screen:
Set the Day and Time for Future Maintenance Updates
You can specify a preferred day of week and time to carry out future maintenance.
Press Edit Time to set the preferred day and time for future maintenance updates.
From here, you can adjust the day of week and the time of day that you wish future upgrades to occur.
Reschedule a Maintenance Job
You can reschedule any of the jobs in the list that are Pending.
You can reschedule the target start time for an individual maintenance job or choose to run the maintenance job immediately. However, maintenance jobs cannot be deferred indefinitely because each maintenance job has a latest possible upgrade date.
To reschedule your maintenance job:
-
Select a job from the
Maintenance Jobslist. -
This will display a dialog for editing the maintenance schedule for the selected job.
Figure 3. Edit the Maintenance Schedule for Selected Job -
You have a number of choices for altering the schedule for the selected job:
Keep Current Schedule The existing schedule remains unchanged.
Change time Selecting this option will display a dialog box allowing you to change the date and time of the update.
Run Now The job will run within the next ten minutes:
If another job is in progress, then the selected job will be queued to run at a later time.
Manage Upgrade Email Notifications
When a maintenance job is scheduled, email notifications are sent to:
-
Organization Owners where one or more clusters in their organization is scheduled for maintenance.
-
Project Owners and Project managers where at least one cluster on a project they have access to is scheduled for maintenance.
Capella sends these emails when the maintenance job is scheduled and, when applicable, 1 week, 24 hours, and 1 hour prior to the target start time. These notifications include details about the cluster, the upgrade, and the upgrade schedule.
| Those with notifications turned OFF will not receive these emails. For more information about how to turn your email notifications on or off, see Get Alerts through Email. |
Create Support Tickets
You can create a support ticket for any of the service upgrades; typically,
you’d want to do this for an upgrade that failed.
Support tickets are created from the upgrade’s maintenance screen (see Figure 2).
From here, click the Create Support Ticket button.
Fill in as much detail as possible as to the nature of the problem,
including the name of the project the service is attached to, and the cluster the service is using.
If you have any information held in files (service logs, example),
then drop them into the Choose a File box for uploading.
When the ticket is filled in, then press the Create Support Ticket button.
Access App Services Maintenance Activity Logs
Log entries for App Services maintenance are listed in the cluster activity logs for the cluster running your App Services.
Select the cluster running your App Service and navigate to the Activity Log page:
You can select a log entry to see more details, and raise a support ticket if required.
To learn more about activity logs, see Activity Logs