Import Data Azure notification is wrong for Enterprise

未关闭
#10 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
停滞
技术栈
azure, redis
领域
cloud, databases

调研方向

未识别出任何仓库文件或测试；首先在 Azure portal 中的 Redis Enterprise 或 EnterpriseFlash 缓存上重现一次大型导入，并将其通知与 Activity Log 进行比较。完成标准是：在导入完成且导入的数据可用之前，通知始终保持不完整。

由索引模型根据 Issue 内容生成。

描述

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

主要语言
PowerShell
星标
12
派生
17
30 天内没有已合并 PR

贡献指南

这个仓库没有索引到贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

Azure/AzureCacheForRedis 的其他 Issue

查看 Azure/AzureCacheForRedis 的全部 Issue

相似的 Issue

更多 Cloud Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。