<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Administration on Kinetica Docs</title><link>/7.1/aws/admin/</link><description>Recent content in Administration on Kinetica Docs</description><generator>Hugo -- gohugo.io</generator><language>en</language><atom:link href="/7.1/aws/admin/index.xml" rel="self" type="application/rss+xml"/><item><title>Alerting in AWS</title><link>/7.1/aws/admin/alerting/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/7.1/aws/admin/alerting/</guid><description/></item><item><title>Backing Up &amp; Restoring the Cluster</title><link>/7.1/aws/admin/backup_restore/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/7.1/aws/admin/backup_restore/</guid><description>You can back up Kinetica data through Workbench. Backups can be used to perform a complete data restoration from the point in time the backup was taken. A backup can be requested while the cluster is in a running state; there is no need to suspend it first. Restoring data from a backup, on the other hand, does require the cluster to be suspended first.
Clicking on Snapshots, will display two lists:</description></item><item><title>Changing the Administrator Password</title><link>/7.1/aws/admin/changing_password/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/7.1/aws/admin/changing_password/</guid><description> To change the administration account password, follow these steps:
Log into Workbench as the administrator Click Admin &amp;gt; Password in the top right corner Enter the Current Password Enter a New Password that meets the password strength requirements (up to 1024 characters) Enter the same new password in Confirm Password Click Update to update to the new password</description></item><item><title>Determining the Kinetica Connection URL</title><link>/7.1/aws/admin/hostname/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/7.1/aws/admin/hostname/</guid><description>The URL for connecting to Kinetica can be found within the AWS Console.
Sign into the AWS Console at:
https://aws.amazon.com/console
Search for CloudFormation in the console search bar.
Choose the AWS Region where you originally deployed the stack (e.g., us-west-2).
Select the original stack you created (not the nested stacks), and then click on the Outputs tab.
The value in the workbenchUrl key is the URL for the Workbench application in Kinetica.</description></item><item><title>Event Codes</title><link>/7.1/aws/admin/event_codes/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/7.1/aws/admin/event_codes/</guid><description>When adding an Event Alert, there are many event codes to choose from. You can search through the available events in the event alert creation window using one of the event codes below or using keywords from a description of the desired event, e.g., shutdown, standby, etc. The events are organized by Kinetica component.
Cluster Operations HTTPD High Availability (HA) Host Manager Machine Learning (ML) Monitoring Rank Operations Reveal SQL Query Planner Cluster Operations Event Code Severity Description / Log Message 01.</description></item><item><title>Host Manager</title><link>/7.1/aws/admin/host_manager/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/7.1/aws/admin/host_manager/</guid><description> Host Manager is a supervisor process that manages several processes that are part of each Kinetica install. The following processes are managed by Host Manager and will be restarted if they fail unexpectedly:
Database Services Text Search ODBC Server HTTPD</description></item><item><title>Job Manager</title><link>/7.1/aws/admin/job_manager/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/7.1/aws/admin/job_manager/</guid><description>The Job Manager maintains request ordering across the nodes in your Kinetica cluster at the cost of some performance. All read requests (/show/table, /get/records, etc.) are processed simultaneously. When a write request (/insert/records, /delete/records, etc.) is made, all subsequent read and write requests are blocked until the current write request is finished.
Because read requests are processed simultaneously, read jobs can only be cancelled while a preceding write request is being processed, which is also referred to as a checkpoint.</description></item><item><title>Logging in AWS</title><link>/7.1/aws/admin/logging/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/7.1/aws/admin/logging/</guid><description>Kinetica logs and metrics are sent to AWS CloudWatch so that you can monitor Kinetica's health and performance alongside other components of your analytic pipelines.
Application Logs To view the logs, click on the link in the applicationLogs key in the CloudFormation stack outputs:
In the search box (Filter log streams or try prefix search), type gpudb to search for Kinetica log events:
Logs Insights Alternatively, you can use CloudWatch Logs Insights to craft specific log queries.</description></item><item><title>Removing a Kinetica in AWS Deployment</title><link>/7.1/aws/admin/removing/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/7.1/aws/admin/removing/</guid><description>Kinetica in AWS is deployed as a CloudFormation stack and deleting the stack will remove all associated resources and costs.
To delete the stack through the AWS Console:
Sign into the AWS Console at:
https://aws.amazon.com/console
Search for CloudFormation in the console search bar.
Choose the AWS Region where you originally deployed the stack (e.g., us-west-2).
Select the original stack you created (not the nested stacks), and then click Delete.</description></item><item><title>Upgrade</title><link>/7.1/aws/admin/upgrade/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/7.1/aws/admin/upgrade/</guid><description>If a new version of Kinetica is available, you will see a notification in the upper right hand corner of Workbench.
Clicking on Upgrade, you will see a list of available versions.
Once you choose to initiate the upgrade, the cluster will be suspended until the upgrade process completes.</description></item></channel></rss>