"Deep Exchange 2013"17 queue Part2

Queue Rate

Most novice administrators can understand that a "queue" is a performance metric for a system or component. such as disk I/O queues, CPU queues, and so on. The efficiency of Message Queuing in Exchange 2013 is calculated by the three properties of the queue. The incoming rate (incomingrate) and outgoing rate (Outgoingrate) properties represent the rate at which messages enter and leave messages. Rate (velocity) is the queue consumption rate value that is obtained from the outgoing rate minus the incoming rate. In addition to the above three values, you should also consider the message quantity (Messagecount) attribute, which displays the number of messages in a queue. Administrators should synthesize these attributes to determine whether a queue is normal.

The incoming and outgoing rates are calculated by averaging the number of incoming/outgoing messages per 5 seconds in the last 60 seconds. We can give an example to help understand that the following table is the number of messages that enter and leave the queue every 5 seconds in the last 60 seconds.

Time	5s	10s	15s	20s	25s	30s	35s	40s	45s	50s	55s	60s	Total
Enter queue	12	3	5	7	14	4	1	3	2	7	9	5	72
Leave the queue	4	8	1	2	6	10	5	7	8	3	4	1	59

The value of entering the queue is averaged, that is, 72/12 is 6, the average of leaving the queue is 59/12 4.9, then the queue rate is 4.9-6=-1.1, that is, the queue rate is negative, the amount of incoming queue is greater than the value of the left queue, which causes the queue to never be emptied. It's like a pond where the water is less than the speed of irrigation, so the pool is never empty. This time plus the number of messages in the queue attribute to consider, if the queue has accumulated a certain number of messages, but the queue rate is approaching 0, then the queue is busy, but has been effective in processing the message. And if the velocity of a queue is a large negative value, and the Messagecount is particularly large, it means that there is a problem with the mail flow in this queue.

View queues

In general, messages are handled very quickly in exchange, and if there are more than 10 or even dozens of messages queued in the queue, the current server or network is in a relatively high load. You can use the Queue Viewer or the Get-queue command to view queues on a separate server, or you can use Get-queuedigest rollup to view queues on multiple servers.

Get-queue

The following is an output of the Get-queue command on a full-role Exchange Server, sorted by Messagecount in ascending order. If you do not specify a server with-server after the command, the command returns only the queue information for the server on which the current PowerShell is connected.

650) this.width=650; "title=" image "style=" border-top:0px;border-right:0px;border-bottom:0px;border-left:0px; " Border= "0" alt= "image" Src= "http://s3.51cto.com/wyfs02/M02/70/C0/wKioL1W9Gk6gk24aAADzdCznuG4189.jpg" height= "156" />

The command-sortorder followed by that sort of attribute, the "+" sign in front of the attribute is in ascending order, if the "-" number is in descending order. You can also use the-filiter parameter to match some filtering criteria, such as:

Get-queues-server ex01-filter {messagecount-gt}-sortorder:-messagecount

Notice that Ex2013 's Get-queue command tells you the queue rate (the velocity described above) in detail. This is different from Ex2010, and there are other places where you can wait until the message routing and Delivery Group is referred to later.

Queues in exchange are shut down without mail, so you might see a queue of queues in a business day peak and a bunch of SMTP target domain queues, or you might find other queues disappear late at night, leaving only one submission queue there. Another type of queue cleanup is when the message times out, that is, if the default message is not delivered successfully for more than 2 days, an NDR is sent to the sender, as to why the default is two days, and Microsoft believes that more than two days of mail retry sending is meaningless. Instead, return to the sender to have the sender contact the recipient in a different way.

In order to ensure the uniqueness of the queue, the transport system uses the server name plus an incremented number each time the queue is created to differentiate each queue, which is reset when the transport service restarts.

Get-queuedigest

The front edge of this command has been mentioned, it is a good improvement that you can summarize the queues on multiple servers together. Here, multiple servers can be servers in the same forest, either the same DAG, a member of the same ad site, or multiple servers in the specified list. Use and simple, in the back with some parameters switch on it (-forest,-dag can be separated from multiple DAG names with commas,-server comma-separated multiple servers,-site), all are literal meaning, and there are-filter switches, you can filter filtering.

Using the Exchange Queue Viewer

Although the control center for Exchange 2013 is no longer the same style as the previous MMC-based management console, it is the EAC for the Web page, but there are things that the EAC cannot do, such as viewing the queue contents, Ex2013 retains the previous queue viewer, mostly from the ease of use, Although performance is not very good, the contents of the Queue Viewer are refreshed every 5 seconds. But often you see the bottom of the page that says "X missions are in progress ..."

650) this.width=650; "title=" image "style=" border-top:0px;border-right:0px;border-bottom:0px;border-left:0px; " Border= "0" alt= "image" Src= "http://s3.51cto.com/wyfs02/M00/70/C0/wKioL1W9Gk-hshBjAAFb4q2eHfw675.jpg" height= "392" />

Queue Status:

Each queue presents the following states:

Activity: message is being transferred

Connect: Connecting Next hop

Ready: All messages representing the queue are successfully transferred, and the queue is currently empty.

Retry: Indicates that the queue is waiting to retry the connection

Pending: The administrator suspends the queue manually, but the new message still goes into the queue, but the message does not leave the queue.

It is important to note that in a complex DAG environment, messages are submitted to other mailbox servers for queuing instead of on the local server, because Exchange can deliver messages to any server in the primary delivery Group (based on minimum cost, of course). So it's possible that you can't find the queue information about the message on the current server, or you might want to use Get-queuedigest to see the queues in the entire DAG.

In the next chapter, we'll talk about how to maintain queues, how to prioritize operations, and how to take advantage of the pickup directory.

This article is from the "Castamere Rainy season" blog, be sure to keep this source http://sodaxu.blog.51cto.com/8850288/1680919

"Deep Exchange 2013"17 queue Part2