What Is “HTTP Error 410: Gone” in Jira Service Management?
When transferring data to Jira Service Management, an HTTP Error 410: Gone might occur. This issue happens when Migration Wizard tries to create tickets in your Target platform.
Why Does HTTP Error 410: Gone Happen?
Data Center applications assume that each API request will go to the same node during a data movement. So, whenever requests go to different nodes, HTTP Error 410: Gone appears. This type of system error can also occur if:
- Subsequent API call are sent to the wrong node;
- The Data Center application doesn’t use sticky sessions and has multiple API nodes.
Hence, it is necessary to link a session to the identical node by activating cookie-based "sticky sessions" on the load balancer.
How to Fix HTTP Error 410: Gone?
To correct HTTP Error 410: Gone, you should go to the load balancer in your Data Center application. This type of technology should let you shut down nodes when removing them for maintenance purposes. There you should:
- Remove all of the dedicated API nodes from the cluster except one so all API calls would go to the same code.
- Temporally shut down API nodes to make them inaccessible.
As a result, the load balancer stops sending the nodes new connections but allows existing connections to finish on their own. For more details, refer to the Jira documentation.