Merge pull request #226727 from spelluru/ehubretention0208

Event Hubs: default retention period is 1

Author: Court72

articles/event-hubs/event-hubs-faq.yml

@@ -23,9 +23,9 @@ sections:
           
           You may want to create a new namespace instead of using an existing one in one of the following scenarios: 
           
-          - You need an Event Hub associated with a new region.
-          - You need an Event Hub associated with a different subscription.
-          - You need an Event Hub with a distinct capacity allocation (that is, the capacity need for the namespace with the added event hub would exceed the 40 TU threshold and you don't want to go for the dedicated cluster)  
+          - You need an Event Hubs associated with a new region.
+          - You need an Event Hubs associated with a different subscription.
+          - You need an Event Hubs with a distinct capacity allocation (that is, the capacity need for the namespace with the added event hub would exceed the 40 TU threshold and you don't want to go for the dedicated cluster)  
           
       - question: |
           What is the difference between Event Hubs Basic and Standard tiers?
@@ -122,7 +122,7 @@ sections:
           
           - Up to 1 MB per second of ingress events (events sent into an event hub), but no more than 1000 ingress events, management operations, or control API calls per second.
           - Up to 2 MB per second of egress events (events consumed from an event hub), but no more than 4096 egress events.
-          - Up to 84 GB of event storage (enough for the default 24-hour retention period).
+          - Up to 84 GB of event storage (enough for the default 1 hour retention period).
           
       - question: |
           How are throughput units billed?
@@ -194,7 +194,7 @@ sections:
       - question: |
           Is there a charge for retaining Event Hubs events for more than 24 hours?
         answer: |
-          The Event Hubs Standard tier does allow message retention periods longer than 24 hours, for a maximum of seven days. If the size of the total number of stored events exceeds the storage allowance for the number of selected throughput units (84 GB per throughput unit), the size that exceeds the allowance is charged at the published Azure Blob storage rate. The storage allowance in each throughput unit covers all storage costs for retention periods of 24 hours (the default) even if the throughput unit is used up to the maximum ingress allowance.
+          The Event Hubs Standard tier does allow message retention periods longer than 24 hours, for a maximum of seven days. If the size of the total number of stored events exceeds the storage allowance for the number of selected throughput units (84 GB per throughput unit), the size that exceeds the allowance is charged at the published Azure Blob storage rate. The storage allowance in each throughput unit covers all storage costs for retention periods of 24 hours even if the throughput unit is used up to the maximum ingress allowance.
 
       - question: |
           How is the Event Hubs storage size calculated and charged?

articles/event-hubs/event-hubs-features.md

@@ -47,14 +47,14 @@ Event Hubs ensures that all events sharing a partition key value are stored toge
 
 Published events are removed from an event hub based on a configurable, timed-based retention policy. Here are a few important points:
 
-- The **default** value and **shortest** possible retention period is **1 day (24 hours)**.
+- The **default** value and **shortest** possible retention period is **1 hour**.
 - For Event Hubs **Standard**, the maximum retention period is **7 days**. 
 - For Event Hubs  **Premium** and **Dedicated**, the maximum retention period is **90 days**.
 - If you change the retention period, it applies to all events including events that are already in the event hub. 
 
 Event Hubs retains events for a configured retention time that applies across
 all partitions. Events are automatically removed when the retention period has
-been reached. If you specify a retention period of one day, the event will
+been reached. If you specify a retention period of one day (24 hours), the event will
 become unavailable exactly 24 hours after it has been accepted. You can't
 explicitly delete events. 
 

articles/event-hubs/event-hubs-messaging-exceptions.md

@@ -64,7 +64,7 @@ The following table lists messaging exception types, and their causes, and notes
 | [UnauthorizedAccessException](/dotnet/api/system.unauthorizedaccessexception?view=netcore-3.1&preserve-view=true) | The [TokenProvider](/dotnet/api/microsoft.servicebus.tokenprovider) object couldn't acquire a token, the token is invalid, or the token doesn't contain the claims required to do the operation. | Make sure the token provider is created with the correct values. Check the configuration of the Access Control Service. | Retry might help in some cases; add retry logic to code. |
 | [ArgumentException](/dotnet/api/system.argumentexception?view=netcore-3.1&preserve-view=true)<br /> [ArgumentNullException](/dotnet/api/system.argumentnullexception?view=netcore-3.1&preserve-view=true)<br />[ArgumentOutOfRangeException](/dotnet/api/system.argumentoutofrangeexception?view=netcore-3.1&preserve-view=true) | One or more arguments supplied to the method are invalid. The URI supplied to [NamespaceManager](/dotnet/api/microsoft.servicebus.namespacemanager) or [Create](/dotnet/api/microsoft.servicebus.messaging.messagingfactory) contains path segment(s). The URI scheme supplied to [NamespaceManager](/dotnet/api/microsoft.servicebus.namespacemanager) or [Create](/dotnet/api/microsoft.servicebus.messaging.messagingfactory) is invalid. The property value is larger than 32 KB. | Check the calling code and make sure the arguments are correct. | Retry will not help. |
 | [Microsoft.ServiceBus.Messaging MessagingEntityNotFoundException](/dotnet/api/microsoft.servicebus.messaging.messagingentitynotfoundexception) <br /><br/> [Microsoft.Azure.EventHubs MessagingEntityNotFoundException](/dotnet/api/microsoft.azure.eventhubs.messagingentitynotfoundexception) | Entity associated with the operation does not exist or it has been deleted. | Make sure the entity exists. | Retry will not help. |
-| [MessagingCommunicationException](/dotnet/api/microsoft.servicebus.messaging.messagingcommunicationexception) | Client is not able to establish a connection to Event Hub. |Make sure the supplied host name is correct and the host is reachable. | Retry might help if there are intermittent connectivity issues. |
+| [MessagingCommunicationException](/dotnet/api/microsoft.servicebus.messaging.messagingcommunicationexception) | Client is not able to establish a connection to Event Hubs. |Make sure the supplied host name is correct and the host is reachable. | Retry might help if there are intermittent connectivity issues. |
 | [Microsoft.ServiceBus.Messaging ServerBusyException](/dotnet/api/microsoft.servicebus.messaging.serverbusyexception) <br /> <br/>[Microsoft.Azure.EventHubs ServerBusyException](/dotnet/api/microsoft.azure.eventhubs.serverbusyexception) | Service is not able to process the request at this time. | Client can wait for a period of time, then retry the operation. <br /> See [ServerBusyException](#serverbusyexception). | Client may retry after certain interval. If a retry results in a different exception, check retry behavior of that exception. |
 | [MessagingException](/dotnet/api/microsoft.servicebus.messaging.messagingexception) | Generic messaging exception that may be thrown in the following cases: An attempt is made to create a [QueueClient](/dotnet/api/microsoft.servicebus.messaging.queueclient) using a name or path that belongs to a different entity type (for example, a topic). An attempt is made to send a message larger than 1 MB. The server or service encountered an error during processing of the request. See the exception message for details. This exception is usually a transient exception. | Check the code and ensure that only serializable objects are used for the message body (or use a custom serializer). Check the documentation for the supported value types of the properties and only use supported types. Check the [IsTransient](/dotnet/api/microsoft.servicebus.messaging.messagingexception) property. If it is **true**, you can retry the operation. | Retry behavior is undefined and might not help. |
 | [MessagingEntityAlreadyExistsException](/dotnet/api/microsoft.servicebus.messaging.messagingentityalreadyexistsexception) | Attempt to create an entity with a name that is already used by another entity in that service namespace. | Delete the existing entity or choose a different name for the entity to be created. | Retry will not help. |
@@ -78,7 +78,7 @@ The following table lists messaging exception types, and their causes, and notes
 This exception can happen if the maximum number of receivers (5) has already been opened on a per-consumer group level.
 
 ### Event Hubs
-Event Hubs has a limit of 20 consumer groups per Event Hub. When you attempt to create more, you receive a [QuotaExceededException](/dotnet/api/microsoft.servicebus.messaging.quotaexceededexception). 
+Event Hubs has a limit of 20 consumer groups per Event Hubs. When you attempt to create more, you receive a [QuotaExceededException](/dotnet/api/microsoft.servicebus.messaging.quotaexceededexception). 
 
 ## TimeoutException
 A [TimeoutException](/dotnet/api/system.timeoutexception?view=netcore-3.1&preserve-view=true) indicates that a user-initiated operation is taking longer than the operation timeout. 
@@ -117,7 +117,7 @@ This error can occur for one of two reasons:
 
     - Up to 1 MB per second of ingress events (events sent into an event hub), but no more than 1000 ingress events, management operations, or control API calls per second.
     - Up to 2 MB per second of egress events (events consumed from an event hub), but no more than 4096 egress events.
-    - Up to 84 GB of event storage (enough for the default 24-hour retention period).
+    - Up to 84 GB of event storage (enough for the default 1 hour retention period).
 
     On the **Overview** page, in the **Show metrics** section, switch to the **Throughput** tab. Select the chart to open it in a larger window with 1-minute intervals on the x-axis. Look at the peak values and divide them by 60 to get incoming bytes/second or outgoing bytes/second. Use similar approach to calculate number of requests per second at peak times on the **Requests** tab. 
 
@@ -140,4 +140,4 @@ You can learn more about Event Hubs by visiting the following links:
 
 * [Event Hubs overview](./event-hubs-about.md)
 * [Create an Event Hub](event-hubs-create.md)
-* [Event Hubs FAQ](event-hubs-faq.yml)
+* [Event Hubs FAQ](event-hubs-faq.yml)