Merge pull request #92787 from yegu-ms/master

Renamed troubleshoot files

Author: tiburd

articles/azure-cache-for-redis/TOC.yml

@@ -98,13 +98,13 @@
   - name: Diagnose and troubleshoot
     items:
     - name: Troubleshoot Redis server
-      href: cache-how-to-troubleshoot-server.md
+      href: cache-troubleshoot-server.md
     - name: Troubleshoot Redis client
-      href: cache-how-to-troubleshoot-client.md
+      href: cache-troubleshoot-client.md
     - name: Troubleshoot timeouts
-      href: cache-how-to-troubleshoot-timeouts.md
+      href: cache-troubleshoot-timeouts.md
     - name: Troubleshoot data loss
-      href: cache-how-to-troubleshoot-data-loss.md
+      href: cache-troubleshoot-data-loss.md
   - name: Scale
     items:
     - name: Update to a different size and tier

articles/azure-cache-for-redis/cache-best-practices.md

@@ -29,7 +29,7 @@ By following these best practices, you can help maximize the performance and cos
 
  * **Configure your [maxmemory-reserved setting](cache-configure.md#maxmemory-policy-and-maxmemory-reserved) to improve system responsiveness** under memory pressure conditions.  This setting is especially important for write-heavy workloads or if you're storing larger values (100 KB or more) in Redis. It's recommended that you start with 10% of the size of your cache and then increase the percentage if you have write-heavy loads.
 
- * **Redis works best with smaller values**, so consider chopping up bigger data into multiple keys.  In [this Redis discussion](https://stackoverflow.com/questions/55517224/what-is-the-ideal-value-size-range-for-redis-is-100kb-too-large/), some considerations are listed that you should consider carefully.  Read [this article](cache-how-to-troubleshoot-client.md#large-request-or-response-size) for an example problem that can be caused by large values.
+ * **Redis works best with smaller values**, so consider chopping up bigger data into multiple keys.  In [this Redis discussion](https://stackoverflow.com/questions/55517224/what-is-the-ideal-value-size-range-for-redis-is-100kb-too-large/), some considerations are listed that you should consider carefully.  Read [this article](cache-troubleshoot-client.md#large-request-or-response-size) for an example problem that can be caused by large values.
 
  * **Locate your cache instance and your application in the same region.**  Connecting to a cache in a different region can significantly increase latency and reduce reliability.  While you can connect from outside of Azure, it  not recommended *especially when using Redis as a cache*.  If you're using Redis as just a key/value store, latency may not be the primary concern. 
 
@@ -39,7 +39,7 @@ By following these best practices, you can help maximize the performance and cos
      > [!NOTE]
      > This guidance is specific to the *connection attempt* and not related to the time you're willing to wait for an *operation* like GET or SET to complete.
  
- * **Avoid expensive operations** - Some Redis operations, like the [KEYS](https://redis.io/commands/keys) command, are *very* expensive and should be avoided.  For more information, see some considerations around [long-running commands](cache-how-to-troubleshoot-server.md#long-running-commands)
+ * **Avoid expensive operations** - Some Redis operations, like the [KEYS](https://redis.io/commands/keys) command, are *very* expensive and should be avoided.  For more information, see some considerations around [long-running commands](cache-troubleshoot-server.md#long-running-commands)
 
  * **Use TLS encryption** - Azure Cache for Redis requires TLS encrypted communications by default.  TLS versions 1.0, 1.1 and 1.2 are currently supported.  However, TLS 1.0 and 1.1 are on a path to deprecation industry-wide, so use TLS 1.2 if at all possible.  If your client library or tool doesn't support TLS, then enabling unencrypted connections can be done [through the Azure portal](cache-configure.md#access-ports) or [management APIs](https://docs.microsoft.com/rest/api/redis/redis/update).  In such cases where encrypted connections aren't possible, placing your cache and client application into a virtual network would be recommended.  For details on which ports are used for 
 

articles/azure-cache-for-redis/cache-faq.md

@@ -440,7 +440,7 @@ These tools enable you to monitor the health of your Azure Cache for Redis insta
 <a name="cache-timeouts"></a>
 
 ### Why am I seeing timeouts?
-Timeouts happen in the client that you use to talk to Redis. When a command is sent to the Redis server, the command is queued up and Redis server eventually picks up the command and executes it. However the client can time out during this process and if it does an exception is raised on the calling side. For more information on troubleshooting timeout issues, see [client-side troubleshooting](cache-how-to-troubleshoot-client.md) and [StackExchange.Redis timeout exceptions](cache-how-to-troubleshoot-timeouts.md#stackexchangeredis-timeout-exceptions).
+Timeouts happen in the client that you use to talk to Redis. When a command is sent to the Redis server, the command is queued up and Redis server eventually picks up the command and executes it. However the client can time out during this process and if it does an exception is raised on the calling side. For more information on troubleshooting timeout issues, see [client-side troubleshooting](cache-troubleshoot-client.md) and [StackExchange.Redis timeout exceptions](cache-troubleshoot-timeouts.md#stackexchangeredis-timeout-exceptions).
 
 <a name="cache-disconnect"></a>
 

articles/azure-cache-for-redis/cache-how-to-troubleshoot-client.md renamed to articles/azure-cache-for-redis/cache-troubleshoot-client.md

@@ -108,5 +108,5 @@ Resolutions for large response sizes are varied but include:
 
 ## Additional information
 
-- [Troubleshoot Azure Cache for Redis server-side issues](cache-how-to-troubleshoot-server.md)
+- [Troubleshoot Azure Cache for Redis server-side issues](cache-troubleshoot-server.md)
 - [How can I benchmark and test the performance of my cache?](cache-faq.md#how-can-i-benchmark-and-test-the-performance-of-my-cache)

articles/azure-cache-for-redis/cache-how-to-troubleshoot-data-loss.md renamed to articles/azure-cache-for-redis/cache-troubleshoot-data-loss.md

@@ -124,7 +124,7 @@ You should consider using [Redis data persistence](http://redis.io/topics/persis
 
 ## Additional information
 
-- [Troubleshoot Azure Cache for Redis server-side issues](cache-how-to-troubleshoot-server.md)
+- [Troubleshoot Azure Cache for Redis server-side issues](cache-troubleshoot-server.md)
 - [What Azure Cache for Redis offering and size should I use?](cache-faq.md#what-azure-cache-for-redis-offering-and-size-should-i-use)
 - [How to monitor Azure Cache for Redis](cache-how-to-monitor.md)
 - [How can I run Redis commands?](cache-faq.md#how-can-i-run-redis-commands)

articles/azure-cache-for-redis/cache-how-to-troubleshoot-server.md renamed to articles/azure-cache-for-redis/cache-troubleshoot-server.md

@@ -79,7 +79,7 @@ To mitigate situations where network bandwidth usage is close to maximum capacit
 
 ## Additional information
 
-- [Troubleshoot Azure Cache for Redis client-side issues](cache-how-to-troubleshoot-client.md)
+- [Troubleshoot Azure Cache for Redis client-side issues](cache-troubleshoot-client.md)
 - [What Azure Cache for Redis offering and size should I use?](cache-faq.md#what-azure-cache-for-redis-offering-and-size-should-i-use)
 - [How can I benchmark and test the performance of my cache?](cache-faq.md#how-can-i-benchmark-and-test-the-performance-of-my-cache)
 - [How to monitor Azure Cache for Redis](cache-how-to-monitor.md)

articles/azure-cache-for-redis/cache-how-to-troubleshoot-timeouts.md renamed to articles/azure-cache-for-redis/cache-troubleshoot-timeouts.md

@@ -79,12 +79,12 @@ You can use the following steps to investigate possible root causes.
 
         synctimeout=2000,cachename.redis.cache.windows.net,abortConnect=false,ssl=true,password=...
 1. Ensure you using the latest version of the [StackExchange.Redis NuGet package](https://www.nuget.org/packages/StackExchange.Redis/). There are bugs constantly being fixed in the code to make it more robust to timeouts so having the latest version is important.
-1. If your requests are bound by bandwidth limitations on the server or client, it takes longer for them to complete and can cause timeouts. To see if your timeout is because of network bandwidth on the server, see [Server-side bandwidth limitation](cache-how-to-troubleshoot-server.md#server-side-bandwidth-limitation). To see if your timeout is because of client network bandwidth, see [Client-side bandwidth limitation](cache-how-to-troubleshoot-client.md#client-side-bandwidth-limitation).
+1. If your requests are bound by bandwidth limitations on the server or client, it takes longer for them to complete and can cause timeouts. To see if your timeout is because of network bandwidth on the server, see [Server-side bandwidth limitation](cache-troubleshoot-server.md#server-side-bandwidth-limitation). To see if your timeout is because of client network bandwidth, see [Client-side bandwidth limitation](cache-troubleshoot-client.md#client-side-bandwidth-limitation).
 1. Are you getting CPU bound on the server or on the client?
 
    - Check if you're getting bound by CPU on your client. High CPU could cause the request to not be processed within the `synctimeout` interval and cause a request to time out. Moving to a larger client size or distributing the load can help to control this problem.
-   - Check if you're getting CPU bound on the server by monitoring the CPU [cache performance metric](cache-how-to-monitor.md#available-metrics-and-reporting-intervals). Requests coming in while Redis is CPU bound can cause those requests to time out. To address this condition, you can distribute the load across multiple shards in a premium cache, or upgrade to a larger size or pricing tier. For more information, see [Server-side bandwidth limitation](cache-how-to-troubleshoot-server.md#server-side-bandwidth-limitation).
-1. Are there commands taking long time to process on the server? Long-running commands that are taking long time to process on the redis-server can cause timeouts. For more information about long-running commands, see [Long-running commands](cache-how-to-troubleshoot-server.md#long-running-commands). You can connect to your Azure Cache for Redis instance using the redis-cli client or the [Redis Console](cache-configure.md#redis-console). Then, run the [SLOWLOG](https://redis.io/commands/slowlog) command to see if there are requests slower than expected. Redis Server and StackExchange.Redis are optimized for many small requests rather than fewer large requests. Splitting your data into smaller chunks may improve things here.
+   - Check if you're getting CPU bound on the server by monitoring the CPU [cache performance metric](cache-how-to-monitor.md#available-metrics-and-reporting-intervals). Requests coming in while Redis is CPU bound can cause those requests to time out. To address this condition, you can distribute the load across multiple shards in a premium cache, or upgrade to a larger size or pricing tier. For more information, see [Server-side bandwidth limitation](cache-troubleshoot-server.md#server-side-bandwidth-limitation).
+1. Are there commands taking long time to process on the server? Long-running commands that are taking long time to process on the redis-server can cause timeouts. For more information about long-running commands, see [Long-running commands](cache-troubleshoot-server.md#long-running-commands). You can connect to your Azure Cache for Redis instance using the redis-cli client or the [Redis Console](cache-configure.md#redis-console). Then, run the [SLOWLOG](https://redis.io/commands/slowlog) command to see if there are requests slower than expected. Redis Server and StackExchange.Redis are optimized for many small requests rather than fewer large requests. Splitting your data into smaller chunks may improve things here.
 
     For information on connecting to your cache's SSL endpoint using redis-cli and stunnel, see the blog post [Announcing ASP.NET Session State Provider for Redis Preview Release](https://blogs.msdn.com/b/webdev/archive/2014/05/12/announcing-asp-net-session-state-provider-for-redis-preview-release.aspx).
 1. High Redis server load can cause timeouts. You can monitor the server load by monitoring the `Redis Server Load` [cache performance metric](cache-how-to-monitor.md#available-metrics-and-reporting-intervals). A server load of 100 (maximum value) signifies that the redis server has been busy, with no idle time, processing requests. To see if certain requests are taking up all of the server capability, run the SlowLog command, as described in the previous paragraph. For more information, see High CPU usage / Server Load.
@@ -113,11 +113,11 @@ You can use the following steps to investigate possible root causes.
    - Set expiration times on the keys so that older values are evicted proactively.
    - Monitor the `used_memory_rss` cache metric. When this value approaches the size of their cache, you're likely to start seeing performance issues. Distribute the data across multiple shards if you're using a premium cache, or upgrade to a larger cache size.
 
-   For more information, see [Memory pressure on Redis server](cache-how-to-troubleshoot-server.md#memory-pressure-on-redis-server).
+   For more information, see [Memory pressure on Redis server](cache-troubleshoot-server.md#memory-pressure-on-redis-server).
 
 ## Additional information
 
-- [Troubleshoot Azure Cache for Redis client-side issues](cache-how-to-troubleshoot-client.md)
-- [Troubleshoot Azure Cache for Redis server-side issues](cache-how-to-troubleshoot-server.md)
+- [Troubleshoot Azure Cache for Redis client-side issues](cache-troubleshoot-client.md)
+- [Troubleshoot Azure Cache for Redis server-side issues](cache-troubleshoot-server.md)
 - [How can I benchmark and test the performance of my cache?](cache-faq.md#how-can-i-benchmark-and-test-the-performance-of-my-cache)
 - [How to monitor Azure Cache for Redis](cache-how-to-monitor.md)