# Amazon Neptune Engine Version 1.0.2.0 (2019-11-08) Release: 1.0.2.0 (2019-11-08)Engine version 1.0.2.0.R1 Amazon Neptune engine version 1.0.2.0.R1 is generally available. For more information, see [Neptune Engine Release 1.0.2.0](https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases-1.0.2.0.html).Engine version 1.0.2.0 is being deprecated Amazon Neptune engine version 1.0.2.0 is now deprecated. Clusters running on this engine version will be upgraded to version 1.0.2.1 automatically during the first maintenance window following June 1, 2020. ## IMPORTANT: THIS ENGINE VERSION IS NOW DEPRECATED Starting from 2020-05-19, no new instances using this engine version will be created. This engine version is now superseded by [version 1.0.2.1](engine-releases-1.0.2.1.md), which contains all the bug fixes in this version as well as additional features such as full-text search integration, OSGP index support, and database snapshot cluster copy across AWS Regions. Starting June 1, 2020, Neptune will automatically upgrade any cluster running this engine version to [the latest patch of version 1.0.2.1](engine-releases-1.0.2.1.R6.md) during the next maintenance window. You can upgrade manually before then, as described [here](engine-releases-1.0.2.1.md). If you have any issues with the upgrade, please contact us through [AWS Support](https://aws.amazon.com/support) or the [AWS Developer Forums](https://forums.aws.amazon.com/forum.jspa?forumID=253). ## Subsequent Patch Releases for This Release Patch Releases + [Release: 1.0.2.0.R3 (2020-05-05)](engine-releases-1.0.2.0.R3.md) + [Release: 1.0.2.0.R2 (2019-11-21)](engine-releases-1.0.2.0.R2.md) ## New Features in This Engine Release New Features In addition to maintenance updates, this release adds new functionality to support more than one engine version at a time (see [Maintaining your Amazon Neptune DB Cluster](cluster-maintenance.md)). As a result, the numbering of engine releases has changed (see [Version numbering before engine release 1.3.0.0](cluster-maintenance.md#older-engine-numbers)). ## Query-Language Versions Supported in This Release Supported Query-Language Versions Before upgrading a DB cluster to version 1.0.2.0, make sure that your project is compatible with these query-language versions: + *Gremlin version:* `3.4.1` + *SPARQL version:* `1.1` ## Upgrade Paths to Engine Release 1.0.2.0 Upgrade Paths You can manually upgrade any previous Neptune engine release to this release. You will not automatically upgrade to this release. ## Upgrading to This Release Upgrading Amazon Neptune 1.0.2.0 is now generally available. If a DB cluster is running an engine version from which there is an upgrade path to this release, it is eligible to be upgraded now. You can upgrade any eligible cluster using the DB cluster operations on the console or by using the SDK. The following CLI command will upgrade an eligible cluster immediately: For Linux, OS X, or Unix: ``` 1. aws neptune modify-db-cluster \ 2. --db-cluster-identifier (your-neptune-cluster) \ 3. --engine-version 1.0.2.0 \ 4. --apply-immediately ``` For Windows: ``` 1. aws neptune modify-db-cluster ^ 2. --db-cluster-identifier (your-neptune-cluster) ^ 3. --engine-version 1.0.2.0 ^ 4. --apply-immediately ``` Updates are applied to all instances in a DB cluster simultaneously. An update requires a database restart on those instances, so you will experience downtime ranging from 20–30 seconds to several minutes, after which you can resume using the DB cluster. ### Always test before you upgrade Test before upgrading When a new major or minor Neptune engine version is released, always test your Neptune applications on it first before upgrading to it. Even a minor upgrade could introduce new features or behavior that would affect your code. Start by comparing the release notes pages from your current version to those of the targeted version to see if there will be changes in query language versions or other breaking changes. The best way to test a new version before upgrading your production DB cluster is to clone your production cluster so that the clone is running the new engine version. You can then run queries on the clone without affecting the production DB cluster. ### Always create a manual snapshot before you upgrade Take a manual snapshot Before performing an upgrade, we strongly recommend that you always create a manual snapshot of your DB cluster. Having an automatic snapshot only offers short-term protection, whereas a manual snapshot remains available until you explicitly delete it. In certain cases Neptune creates a manual snapshot for you as a part of the upgrade process, but you should not rely on this, and should create your own manual snapshot in any case. When you are certain that you won't need to revert your DB cluster to its pre-upgrade state, you can explicitly delete the manual snapshot that you created yourself, as well as the manual snapshot that Neptune might have created. If Neptune creates a manual snapshot, it will have a name that begins with `preupgrade`, followed by the name of your DB cluster, the source engine version, the target engine version, and the date. **Note** If you are trying to upgrade while [a pending action is in process](manage-console-maintaining), you may encounter an error such as the following: ``` We're sorry, your request to modify DB cluster (cluster identifier) has failed. Cannot modify engine version because instance (instance identifier) is running on an old configuration. Apply any pending maintenance actions on the instance before proceeding with the upgrade. ``` If you encounter this error, wait for the pending action to finish, or trigger a maintenance window immediately to let the previous upgrade complete. For more information about upgrading your engine version, see [Maintaining your Amazon Neptune DB Cluster](cluster-maintenance.md). If you have any questions or concerns, the AWS Support team is available on the community forums and through [AWS Premium Support](http://aws.amazon.com/support). # Amazon Neptune Engine Version 1.0.2.0.R3 (2020-05-05) Release: 1.0.2.0.R3 (2020-05-05)Engine version 1.0.2.0.R3 As of 2020-05-05, engine version 1.0.2.0.R3 is being generally deployed. Please note that it takes several days for a new release to become available in every region. For more information about this engine version, see [Neptune Engine Release 1.0.2.0.R3](https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases-1.0.2.0.R3.html). ## IMPORTANT: THIS ENGINE VERSION IS NOW DEPRECATED Starting from 2020-05-19, no new instances using this engine version will be created. This engine version is now superseded by [version 1.0.2.1](engine-releases-1.0.2.1.md), which contains all the bug fixes in this version as well as additional features such as full-text search integration, OSGP index support, and database snapshot cluster copy across AWS Regions. Starting June 1, 2020, Neptune will automatically upgrade any cluster running this engine version to [the latest patch of version 1.0.2.1](engine-releases-1.0.2.1.R6.md) during the next maintenance window. You can upgrade manually before then, as described [here](engine-releases-1.0.2.1.md). If you have any issues with the upgrade, please contact us through [AWS Support](https://aws.amazon.com/support) or the [AWS Developer Forums](https://forums.aws.amazon.com/forum.jspa?forumID=253). ## Defects Fixed in This Engine Release Defects Fixed + Fixed a bug where `ConcurrentModificationConflictException` and `TransactionException` were reported as generic `InternalFailureException`s. + Fixed bugs in health checks that caused frequent restarts of the server during start up. + Fixed a bug where data was not visible on replicas because commits were out of order under certain conditions. + Fixed a bug in load-status serialization where a load failed from a lack of Amazon S3 access permissions. + Fixed a resource leak in Gremlin sessions. + Fixed a bug in health check that hid the unhealthy status on start-up of components managing IAM authentication. + Fixed a bug where Neptune failed to send a WebSocket close frame before closing the channel. ## Query-Language Versions Supported in This Release Supported Query-Language Versions Before upgrading a DB cluster to version 1.0.2.0.R3, make sure that your project is compatible with these query-language versions: + *Gremlin version:* `3.4.1` + *SPARQL version:* `1.1` ## Upgrade Paths to Engine Release 1.0.2.0.R3 Upgrade Paths Your cluster will be upgraded to this patch release automatically during your next maintenance window if you are running engine version `1.0.2.0`. You can manually upgrade any earlier Neptune engine release to this release. ## Upgrading to This Release Upgrading Amazon Neptune 1.0.2.0.R3 is now generally available. If a DB cluster is running an engine version from which there is an upgrade path to this release, it is eligible to be upgraded now. You can upgrade any eligible cluster using the DB cluster operations on the console or by using the SDK. The following CLI command will upgrade an eligible cluster immediately: For Linux, OS X, or Unix: ``` 1. aws neptune modify-db-cluster \ 2. --db-cluster-identifier (your-neptune-cluster) \ 3. --engine-version 1.0.2.0 \ 4. --apply-immediately ``` For Windows: ``` 1. aws neptune modify-db-cluster ^ 2. --db-cluster-identifier (your-neptune-cluster) ^ 3. --engine-version 1.0.2.0 ^ 4. --apply-immediately ``` Updates are applied to all instances in a DB cluster simultaneously. An update requires a database restart on those instances, so you will experience downtime ranging from 20–30 seconds to several minutes, after which you can resume using the DB cluster. ### Always test before you upgrade Test before upgrading When a new major or minor Neptune engine version is released, always test your Neptune applications on it first before upgrading to it. Even a minor upgrade could introduce new features or behavior that would affect your code. Start by comparing the release notes pages from your current version to those of the targeted version to see if there will be changes in query language versions or other breaking changes. The best way to test a new version before upgrading your production DB cluster is to clone your production cluster so that the clone is running the new engine version. You can then run queries on the clone without affecting the production DB cluster. ### Always create a manual snapshot before you upgrade Take a manual snapshot Before performing an upgrade, we strongly recommend that you always create a manual snapshot of your DB cluster. Having an automatic snapshot only offers short-term protection, whereas a manual snapshot remains available until you explicitly delete it. In certain cases Neptune creates a manual snapshot for you as a part of the upgrade process, but you should not rely on this, and should create your own manual snapshot in any case. When you are certain that you won't need to revert your DB cluster to its pre-upgrade state, you can explicitly delete the manual snapshot that you created yourself, as well as the manual snapshot that Neptune might have created. If Neptune creates a manual snapshot, it will have a name that begins with `preupgrade`, followed by the name of your DB cluster, the source engine version, the target engine version, and the date. **Note** If you are trying to upgrade while [a pending action is in process](manage-console-maintaining), you may encounter an error such as the following: ``` We're sorry, your request to modify DB cluster (cluster identifier) has failed. Cannot modify engine version because instance (instance identifier) is running on an old configuration. Apply any pending maintenance actions on the instance before proceeding with the upgrade. ``` If you encounter this error, wait for the pending action to finish, or trigger a maintenance window immediately to let the previous upgrade complete. For more information about upgrading your engine version, see [Maintaining your Amazon Neptune DB Cluster](cluster-maintenance.md). If you have any questions or concerns, the AWS Support team is available on the community forums and through [AWS Premium Support](http://aws.amazon.com/support). # Amazon Neptune Engine Version 1.0.2.0.R2 (2019-11-21) Release: 1.0.2.0.R2 (2019-11-21)Engine version 1.0.2.0.R2 Patch R2 for engine version 1.0.2.0 is generally available. For more information, see [Neptune Engine Release 1.0.2.0.R2](https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases-1.0.2.0.R2.html). ## IMPORTANT: THIS ENGINE VERSION IS NOW DEPRECATED Starting from 2020-05-19, no new instances using this engine version will be created. This engine version is now superseded by [version 1.0.2.1](engine-releases-1.0.2.1.md), which contains all the bug fixes in this version as well as additional features such as full-text search integration, OSGP index support, and database snapshot cluster copy across AWS Regions. Starting June 1, 2020, Neptune will automatically upgrade any cluster running this engine version to [the latest patch of version 1.0.2.1](engine-releases-1.0.2.1.R6.md) during the next maintenance window. You can upgrade manually before then, as described [here](engine-releases-1.0.2.1.md). If you have any issues with the upgrade, please contact us through [AWS Support](https://aws.amazon.com/support) or the [AWS Developer Forums](https://forums.aws.amazon.com/forum.jspa?forumID=253). ## Defects Fixed in This Engine Release Defects Fixed + Improved the caching strategy for dirty pages on the server so that `FreeableMemory` recovers faster when the server enters a low-memory state. + Fixed a bug that could cause a race condition and crash when many concurrent load status and/or start load requests are processed on the server. ## Query-Language Versions Supported in This Release Supported Query-Language Versions Before upgrading a DB cluster to version 1.0.2.0.R2, make sure that your project is compatible with these query-language versions: + *Gremlin version:* `3.4.1` + *SPARQL version:* `1.1` ## Upgrade Paths to Engine Release 1.0.2.0.R2 Upgrade Paths You can manually upgrade any previous Neptune engine release to this release. However, **automatic updating to this release is not supported**. ## Upgrading to This Release Upgrading Amazon Neptune 1.0.2.0.R2 is now generally available. If a DB cluster is running an engine version from which there is an upgrade path to this release, it is eligible to be upgraded now. You can upgrade any eligible cluster using the DB cluster operations on the console or by using the SDK. The following CLI command will upgrade an eligible cluster immediately: For Linux, OS X, or Unix: ``` 1. aws neptune modify-db-cluster \ 2. --db-cluster-identifier (your-neptune-cluster) \ 3. --engine-version 1.0.2.0 \ 4. --apply-immediately ``` For Windows: ``` 1. aws neptune modify-db-cluster ^ 2. --db-cluster-identifier (your-neptune-cluster) ^ 3. --engine-version 1.0.2.0 ^ 4. --apply-immediately ``` Updates are applied to all instances in a DB cluster simultaneously. An update requires a database restart on those instances, so you will experience downtime ranging from 20–30 seconds to several minutes, after which you can resume using the DB cluster. ### Always test before you upgrade Test before upgrading When a new major or minor Neptune engine version is released, always test your Neptune applications on it first before upgrading to it. Even a minor upgrade could introduce new features or behavior that would affect your code. Start by comparing the release notes pages from your current version to those of the targeted version to see if there will be changes in query language versions or other breaking changes. The best way to test a new version before upgrading your production DB cluster is to clone your production cluster so that the clone is running the new engine version. You can then run queries on the clone without affecting the production DB cluster. ### Always create a manual snapshot before you upgrade Take a manual snapshot Before performing an upgrade, we strongly recommend that you always create a manual snapshot of your DB cluster. Having an automatic snapshot only offers short-term protection, whereas a manual snapshot remains available until you explicitly delete it. In certain cases Neptune creates a manual snapshot for you as a part of the upgrade process, but you should not rely on this, and should create your own manual snapshot in any case. When you are certain that you won't need to revert your DB cluster to its pre-upgrade state, you can explicitly delete the manual snapshot that you created yourself, as well as the manual snapshot that Neptune might have created. If Neptune creates a manual snapshot, it will have a name that begins with `preupgrade`, followed by the name of your DB cluster, the source engine version, the target engine version, and the date. **Note** If you are trying to upgrade while [a pending action is in process](manage-console-maintaining), you may encounter an error such as the following: ``` We're sorry, your request to modify DB cluster (cluster identifier) has failed. Cannot modify engine version because instance (instance identifier) is running on an old configuration. Apply any pending maintenance actions on the instance before proceeding with the upgrade. ``` If you encounter this error, wait for the pending action to finish, or trigger a maintenance window immediately to let the previous upgrade complete. For more information about upgrading your engine version, see [Maintaining your Amazon Neptune DB Cluster](cluster-maintenance.md). If you have any questions or concerns, the AWS Support team is available on the community forums and through [AWS Premium Support](http://aws.amazon.com/support).