Database: Database not updated after event forwarding - Revision history

Dosproul: 1 revision

2012-08-14T18:57:20Z

1 revision

← Older revision

Revision as of 18:57, 14 August 2012

Rshroyer: Added Categories 8.5 and 9.0.

2012-08-14T01:45:15Z

Added Categories 8.5 and 9.0.

← Older revision		Revision as of 01:45, 14 August 2012
Line 33:		Line 33:
	\| None.		\| None.
	\|}		\|}
		+
		+	[[Category:Cisco_MediaSense,_Release_8.5]] [[Category:Cisco_MediaSense,_Release_9.0]]

Dosproul: 1 revision

2012-08-03T13:04:13Z

1 revision

← Older revision

Revision as of 13:04, 3 August 2012

Rshroyer: Added release 9.0(1)

2012-08-02T03:47:05Z

Added release 9.0(1)

← Older revision		Revision as of 03:47, 2 August 2012
Line 28:		Line 28:
	\|-		\|-
	! '''Release'''		! '''Release'''
-	\| Release 8.5(1), Release 8.5(2), Release 8.5(3), ~~and~~ Release 8.5(4).	+	\| Release 8.5(1), Release 8.5(2), Release 8.5(3), Release 8.5(4), and Release 9.0(1).
	\|-		\|-
	! '''Associated CDETS #'''		! '''Associated CDETS #'''
	\| None.		\| None.
	\|}		\|}
-
-	~~<br>~~
-
-	~~[[Category:Cisco_MediaSense,_Release_8.5]]~~

Dosproul: 1 revision

2012-01-27T17:08:39Z

1 revision

← Older revision

Revision as of 17:08, 27 January 2012

Kemacdon at 20:04, 26 January 2012

2012-01-26T20:04:26Z

← Older revision		Revision as of 20:04, 26 January 2012
Line 5:		Line 5:
	! '''Problem Summary'''		! '''Problem Summary'''
	\|		\|
-	When a client receives an event that was forwarded from the other application server and immediately issues a query to the forwarding ~~serverto~~ get additional data related to the event, it does not see the updates that were reported in the event.	+	When a client receives an event that was forwarded from the other application server and immediately issues a query to the forwarding server to get additional data related to the event, it does not see the updates that were reported in the event.

	\|-		\|-
Line 28:		Line 28:
	\|-		\|-
	! '''Release'''		! '''Release'''
-	\| Release 8.5(1), Release 8.5(2), ~~and~~ Release 8.5(3).	+	\| Release 8.5(1), Release 8.5(2), Release 8.5(3), and Release 8.5(4).
	\|-		\|-
	! '''Associated CDETS #'''		! '''Associated CDETS #'''

Cchetty: 1 revision

2011-10-08T20:19:33Z

1 revision

← Older revision

Revision as of 20:19, 8 October 2011

Cchetty at 18:25, 30 September 2011

2011-09-30T18:25:14Z

← Older revision		Revision as of 18:25, 30 September 2011
Line 4:		Line 4:
	\|-		\|-
	! '''Problem Summary'''		! '''Problem Summary'''
-	\| When an event ~~is sent~~ from the ~~node on which~~ a ~~database change occurred,~~ the forwarding ~~node's database is~~ not ~~updated~~.	+	\|
		+	When a client receives an event that was forwarded from the other application server and immediately issues a query to the forwarding serverto get additional data related to the event, it does not see the updates that were reported in the event.
		+
	\|-		\|-
	! '''Error Message'''		! '''Error Message'''
-	\| None.	+	\|
		+	None.
		+
	\|-		\|-
	! '''Possible Cause'''		! '''Possible Cause'''
	\|		\|
-	~~Event forwarding takes place in parallel with database replication~~. ~~When an~~ event is ~~sent~~ from the ~~node in which a database change occurred~~, ~~the recipient can~~ be ~~sure that~~ the ~~data on~~ that ~~node has already been updated~~. ~~However, there is no guarantee~~ that the forwarding ~~node's database has also been updated~~.	+	The client is querying the wrong server. If the event is forwarded from the other server, there will be a flag in the event that indicates this. Whenever the client receives such a message and it wishes to immediately query for information related to that event, it must issue the query to the other server, not the forwarding server.

-	{{note\| The forwarding node's database will be updated and the data will eventually be replicated.}}	+	Event forwarding takes place in parallel with database replication. When an event is forwarded from the server in which a database change occurred, the recipient can be sure that the data on that server has already been updated. However, there is no guarantee that the forwarding server's database was also updated.
		+
		+	{{note\| The forwarding node's database will be updated and the data will eventually be replicated.}}

	\|-		\|-
	! '''Recommended Action'''		! '''Recommended Action'''
-	\| If ~~there is a reason that~~ the recipient needs to query the metadata immediately after receiving an event, then it should issue that query to the ~~node~~ which originated the event, not to the ~~node~~ which forwarded it. ~~<br>~~	+	\|
		+	If the recipient (client) needs to query the metadata immediately after receiving an event, then the client should issue that query to the server which originated the event--not to the server which forwarded the event.
		+
	\|-		\|-
	! '''Release'''		! '''Release'''
-	\| Release 8.5(2).	+	\| Release 8.5(1), Release 8.5(2), and Release 8.5(3).
	\|-		\|-
	! '''Associated CDETS #'''		! '''Associated CDETS #'''
Line 26:		Line 34:
	\|}		\|}

-	<br>	+	<br>

	[[Category:Cisco_MediaSense,_Release_8.5]]		[[Category:Cisco_MediaSense,_Release_8.5]]

Cchetty: 1 revision

2011-04-21T18:59:37Z

1 revision

← Older revision

Revision as of 18:59, 21 April 2011

Jwolfeld: /* Database not updated after event forwarding */

2011-04-20T23:36:52Z

Database not updated after event forwarding

New page

== Database not updated after event forwarding ==

{| border="1"
|-
! '''Problem Summary'''
| When an event is sent from the node on which a database change occurred, the forwarding node's database is not updated.
|-
! '''Error Message'''
| None.
|-
! '''Possible Cause'''
|
Event forwarding takes place in parallel with database replication. When an event is sent from the node in which a database change occurred, the recipient can be sure that the data on that node has already been updated. However, there is no guarantee that the forwarding node's database has also been updated.

{{note| The forwarding node's database will be updated and the data will eventually be replicated.}}

|-
! '''Recommended Action'''
| If there is a reason that the recipient needs to query the metadata immediately after receiving an event, then it should issue that query to the node which originated the event, not to the node which forwarded it. <br>
|-
! '''Release'''
| Release 8.5(2).
|-
! '''Associated CDETS #'''
| None.
|}

<br>

[[Category:Cisco_MediaSense,_Release_8.5]]