log_killcursor(3) [php man page]

LOG_KILLCURSOR(3)							 1							 LOG_KILLCURSOR(3)

log_killcursor - Callback When Executing KILLCURSOR operations

SYNOPSIS

       log_killcursor (array  $server, array  $info)

DESCRIPTION

	A callable function, used by the log_killcursor context option, when reading a killcursor from MongoDB.

       Note

	       This is not a real function, only a prototype of how the function should be.

PARAMETERS

	      o $server
		- An array containing the basic information about the server that was picked.

	      +-----------------+---------------------------------------------------+
	      |      key	|						    |
	      | 		|						    |
	      | 		|			value			    |
	      | 		|						    |
	      +-----------------+---------------------------------------------------+
	      |      hash	|						    |
	      | 		|						    |
	      | 		|  server hash, example: localhost:27017;-;X;56052  |
	      | 		|						    |
	      |      type	|						    |
	      | 		|						    |
	      | 		|  Node type (primary/secondary/mongos/arbiter): 2  |
	      | 		|						    |
	      | max_bson_size	|						    |
	      | 		|						    |
	      | 		| The  maximum	BSON  Size  over the wire this node |
	      | 		| accepts: 16777216				    |
	      | 		|						    |
	      |max_message_size |						    |
	      | 		|						    |
	      | 		| The maximum Message Size over the wire this  node |
	      | 		| accepts: 48000000				    |
	      | 		|						    |
	      |   request_id	|						    |
	      | 		|						    |
	      | 		|    The request identifier for this message: 42    |
	      | 		|						    |
	      +-----------------+---------------------------------------------------+
	      o $info
		-

	      +----------+----------------------------------------+
	      |   key	 |					  |
	      | 	 |					  |
	      | 	 |		   value		  |
	      | 	 |					  |
	      +----------+----------------------------------------+
	      |cursor_id |					  |
	      | 	 |					  |
	      | 	 | integer, the cursor identifier to kill |
	      | 	 |					  |
	      +----------+----------------------------------------+
PHP Documentation Group 													 LOG_KILLCURSOR(3)

LOG_REPLY(3)								 1							      LOG_REPLY(3)

log_reply - Callback When Reading the MongoDB reply

SYNOPSIS

       log_reply (array  $server, array  $messageHeaders, array  $operationHeaders)

DESCRIPTION

	A callable function, used by the log_reply context option, when reading a reply from MongoDB.

       Note

	       This is not a real function, only a prototype of how the function should be.

PARAMETERS

	      o $server
		- An array containing the basic information about the server that was picked.

	      +-----------------+---------------------------------------------------+
	      |      key	|						    |
	      | 		|						    |
	      | 		|			value			    |
	      | 		|						    |
	      +-----------------+---------------------------------------------------+
	      |      hash	|						    |
	      | 		|						    |
	      | 		|  server hash, example: localhost:27017;-;X;56052  |
	      | 		|						    |
	      |      type	|						    |
	      | 		|						    |
	      | 		|  Node type (primary/secondary/mongos/arbiter): 2  |
	      | 		|						    |
	      | max_bson_size	|						    |
	      | 		|						    |
	      | 		| The  maximum	BSON  Size  over the wire this node |
	      | 		| accepts: 16777216				    |
	      | 		|						    |
	      |max_message_size |						    |
	      | 		|						    |
	      | 		| The maximum Message Size over the wire this  node |
	      | 		| accepts: 48000000				    |
	      | 		|						    |
	      |   request_id	|						    |
	      | 		|						    |
	      | 		|    The request identifier for this message: 42    |
	      | 		|						    |
	      +-----------------+---------------------------------------------------+
	      o $messageHeaders
		-

	      +------------+---------------------------------------------------+
	      |    key	   |						       |
	      | 	   |						       |
	      | 	   |			   value		       |
	      | 	   |						       |
	      +------------+---------------------------------------------------+
	      |  length    |						       |
	      | 	   |						       |
	      | 	   |	   integer, bytes, message reply length        |
	      | 	   |						       |
	      |request_id  |						       |
	      | 	   |						       |
	      | 	   |	  integer, the server request identifier       |
	      | 	   |						       |
	      |response_id |						       |
	      | 	   |						       |
	      | 	   | integer,  the driver request identifier this mes- |
	      | 	   | sage is a response of			       |
	      | 	   |						       |
	      |  opcode    |						       |
	      | 	   |						       |
	      | 	   |		  integer, the opcode id	       |
	      | 	   |						       |
	      +------------+---------------------------------------------------+
	      o $operationHeaders
		-

	      +----------+---------------------------------------------------+
	      |   key	 |						     |
	      | 	 |						     |
	      | 	 |			 value			     |
	      | 	 |						     |
	      +----------+---------------------------------------------------+
	      |  flags	 |						     |
	      | 	 |						     |
	      | 	 |	  integer, bitmask of protocol flags	     |
	      | 	 |						     |
	      |cursor_id |						     |
	      | 	 |						     |
	      | 	 | integer, ID of the cursor created on  the  server |
	      | 	 | (0 if none created, or its been exhausted)	     |
	      | 	 |						     |
	      |  start	 |						     |
	      | 	 |						     |
	      | 	 |	  The starting offset of this cursor	     |
	      | 	 |						     |
	      |returned  |						     |
	      | 	 |						     |
	      | 	 | integer,  how many documents are returned in this |
	      | 	 | trip 					     |
	      | 	 |						     |
	      +----------+---------------------------------------------------+
SEE ALSO The OP_REPLY definition in the Wire Protocol.
PHP Documentation Group 													      LOG_REPLY(3)