Debugging in-cloud distributed code in live load environment

• US 10,114,732 B2
• Filed: 01/29/2016
• Issued: 10/30/2018
• Est. Priority Date: 01/29/2016
• Status: Active Grant

• Current Assignee: CA, Inc. (d/b/a CA Technologies) (Broadcom, Inc.)
• Original Assignee: CA, Inc. (d/b/a CA Technologies) (Broadcom, Inc.)
• Inventors: Mankovskii, Serguei
• Primary Examiner(s): Nahar, Qamrun
• Application Number:
  US15/010,308
• Publication Number:
  US 20170220451A1
• Time in Patent Office: 1,005 Days
• Field of Search: None
• CPC Class Codes: G06F 11/362 Software debugging
• CPC Class Codes: G06F 11/3648 using additional hardware
• CPC Class Codes: G06F 11/3664 Environments for testing or debugging software
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46

Abstract

A multi-device data processing machine system includes a plurality of network-connected cliental servers including first and second production servers coupled to a dynamic load balancer. The machine system also includes an SaaS development server that is configured to pass under-development process requests to the load balancer in combination with a mix command such that the load balancer routes a mix of routine production traffic and the under-development process requests to at least one of the production servers that is instrumented for enabling remote debugging of code executing therein so that the under-development process requests can be debugged under the full or partial stresses of a live production environment.

Claims

1. A remote debugging method comprising:

configuring a transactions traffic distributor in a networked system to distinguish between production traffic and development traffic and to route at least a first portion of production traffic received by the distributor to an associated first production server;

configuring the transactions traffic distributor to route at least a respective portion of development traffic received by the distributor to an associated second production server, the second production server being configured to perform remotely controlled debugging on code of the at least respective portion of development traffic routed thereto;

configuring a development server remote from the first and second production servers and operatively coupled to the networked system to route transaction requests of at least one under-development process to the transactions traffic distributor in the form of development traffic; and

configuring the development server to provide debugging instructions to, and receive debugging results from the second production server.

2. The method of claim 1 and further comprising:

configuring the transactions traffic distributor to route a second portion of the production traffic received by the distributor to the second production server such that the second production server receives and processes at substantially a same time, a mix of transaction requests of the at least one under-development process and of transaction requests of the second portion of the production traffic routed to the second production server.

3. The method of claim 2 and further comprising:

configuring the development server to provide mix control commands to the transactions traffic distributor for controlling the amount of production traffic routed by the distributor to the second production server.

4. The method of claim 3 wherein the transactions traffic distributor is a dynamic load balancer but the mix control commands provided by the development server for determining the mix of traffic to be processed at substantially the same time by the second production server supersede normal dynamic load balancing otherwise performed by the transactions traffic distributor for at least traffic routed to the second production server.

5. The method of claim 1 and further comprising:

configuring the networked system such that the second production server remains allocated to receive traffic routed by the transactions traffic distributor even if it is determined that the resources of the second production server are not currently needed for handling the production traffic currently received by the transactions traffic distributor.

6. The method of claim 2 wherein the first and second production servers are each instrumented to provide performance reporting on respective performance attributes of the first and second production servers in processing production traffic respectively routed to the first and second production servers.

7. The method of claim 6 and further comprising:

configuring the development server to receive performance reporting at least from the second production server so that the development server thereby receives information indicating how the under-development process executing in the second production server affects performance of the second portion of the received production traffic also then processed by the second production server.

8. The method of claim 1 and further comprising:

configuring the transactions traffic distributor to use correlation for automatically determining whether transaction traffic received thereby is development traffic or routine production traffic.

9. The method of claim 8 wherein,

the configuring of the transactions traffic distributor includes configuring the distributor to automatically determine whether development traffic received thereby includes a corresponding correlator token, and if the correlator token is not present, to automatically assign a unique correlator to that received development traffic to thereby distinguish the received development traffic from other development traffic to which other unique correlator tokens have been assigned.

10. A networked system comprising:

a transactions traffic distributor configured to receive plural transaction requests routed thereto by way of a network of the networked system, the plural transaction requests including requests belonging to production type transaction request traffic and requests belonging to development traffic;

first and second production servers operatively coupled to respectively receive first and second portions of the production type transaction request traffic routed to the transactions traffic distributor and then routed by the transactions traffic distributor respectively to at least one of the first and second production servers; and

a development server remote from the first and second production servers and operatively coupled to the network system to route transaction requests of at least one under-development process to the transaction traffic distributor in the form of said development traffic;

wherein the transactions traffic distributor is configured to distinguish between production traffic and development traffic and to route the received development traffic to the second production server, the second production server being configured to perform remotely controlled debugging on code of the development traffic routed thereto; and

wherein the development server is configured to provide debugging instructions to, and receive debugging results from the second production server.

11. The system of claim 10 wherein:

the transactions traffic distributor is configured to route a portion of the received production type traffic to the second production server such that the second production server processes at substantially a same time, a mix of both the transaction requests of the at least one under-development process and the portion of the received production type traffic routed to the second production server.

12. The system of claim 11 wherein:

the development server is configured to provide mix control commands to the transactions traffic distributor for controlling the amount of received production type traffic routed to the second production server.

13. The system of claim 12 wherein the transactions traffic distributor is a dynamic load balancer but the mix control commands provided by the development server for determining the mix of traffic to be processed at substantially the same time by the second production server supersede normal dynamic load balancing otherwise performed by the transaction traffic distributor for at least the first production server.

14. The system of claim 10 wherein:

wherein the first and second production servers are each instrumented to provide performance reporting on respective performance attributes of the first and second production servers in processing production type traffic respectively routed to the first and second production servers.

15. A method of operating a dynamic load balancer configured to receive transaction request traffic routed thereto by way of a network of a networked system, the method comprising:

determining if transaction request traffic routed to and received by the dynamic load balancer includes an operational URL or a development URL, the operational URL indicating that the corresponding transaction request is part of routine production traffic and the development URL that the corresponding transaction request is part of an under-development process;

at least occasionally routing the corresponding transaction request to a first production server associated with the load balancer in response to determining that the corresponding transaction request includes an operational URL; and

routing the corresponding transaction request to a second production server associated with the load balancer in response to determining that the corresponding transaction request includes a development URL;

wherein the second production server is configured to perform remotely controlled debugging on code of the development traffic routed thereto.

16. The method of claim 15 wherein:

prior to at least occasionally routing the corresponding transaction request to the first production server, the dynamic load balancer automatically determines if a mix control of the second production server calls for additional routine production traffic to be routed to the second production server, and if so routing the corresponding transaction request to the second production server.

17. The method of claim 15 and further comprising:

in the case where it is determined that the corresponding transaction request is part of an under-development process, determining if the corresponding transaction request has a transaction correlator that associates the request with a respective under-development process, and if not, automatically assigning a unique correlator to that corresponding transaction request to thereby distinguish development traffic of the respective under-development process from other development traffic to which other unique correlators have been assigned.

18. The method of claim 15 wherein:

the networked system includes a development server remote from the first and second production servers and operatively coupled to the dynamic load balancer and configured for routing transaction requests of at least one under-development process to the dynamic load balancer in the form of development traffic.

19. The method of claim 18 wherein:

the development server is operatively coupled to the second production server for performing remotely controlled debugging of the at least one under-development process when processed by the second production server.

20. The method of claim 19 wherein:

the development server is operatively coupled to the second production server for receiving automatically generated performance reports reporting on performance attributes of the second production server in processing production type traffic while substantially at the same time processing transaction requests of at least one under-development process.