Import Data Azure notification is wrong for Enterprise

Open
#10 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
azure, redis
Domain
cloud, databases

Research direction

No repository file or test is identified; start by reproducing a large import on a Redis Enterprise or EnterpriseFlash cache in the Azure portal and compare its notification with the Activity Log. Done means the notification remains incomplete until the import finishes and the imported data is available.

Written by the indexing model from the issue text.

Description

When importing data into a Redis Enterprise (in this case EnterpriseFlash 345 GB (1 x 345 GB)) cache, the notification in the Azure portal incorrectly says it is complete about 10 seconds after starting the process. Clearly this isn't true, and the data doesn't change.
image

After a few minutes it appears in Activity Log, and shows correctly that it isn't complete:
image

And later it completes
image

Server load shows no activity during this period
image

For reference, Azure Cache for Redis Premium instances behave as expected. While imports are just as unreliable, the notification is correct (stays spinning at the top right of the portal until it is really done), and the graphs show activity during the period.

If we look at an example of importing MUCH less data (in which case it doesn't fail) then the initial Activity Log shows like this, where the process was started at 3:37 PM:
image

It then seemingly doesn't do anything until 3:57 PM (20 minutes), and then over about 5 minutes processes the data. Cursor line indicates 3:37 when it should have started.
image

And for completeness, here is the activity log at the end once it has succeeded
image

Dominant language
PowerShell
Stars
12
Forks
17
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/AzureCacheForRedis

All issues in Azure/AzureCacheForRedis

Similar issues

More Cloud issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.