=== REDIS BUG REPORT START: Cut & paste starting from here ===
[018876] 23 Aug 20:51:25.017 # --- EXCEPTION_ACCESS_VIOLATION
[018876] 23 Aug 20:51:25.017 # --- STACK TRACE
redis-server.exe!((null):0)(0x1401E3C90, 0x0014FF60, 0x00000001, 0x0014E980)
redis-server.exe!((null):0)(0x0014E980, 0x00000001, 0x00000000, 0x0014F398)
KERNELBASE.dll!UnhandledExceptionFilter((null):0)(0x0005AA89, 0x7FFB0BB31690, 0x00000000, 0x7FFB0B9F0B4A)
ntdll.dll!RtlMoveMemory((null):0)(0x0014EA50, 0x00000000, 0x0014EA08, 0x0014EFF0)
ntdll.dll!_C_specific_handler((null):0)(0x00000000, 0x0014EF50, 0x0014F630, 0x0014F630)
ntdll.dll!_chkstk((null):0)(0x0014F630, 0x7FFB0B9D0000, 0x7FFB0BA2AA68, 0x7FFB0BB5CBF8)
ntdll.dll!RtlFindCharInUnicodeString((null):0)(0x02960000, 0x0014F101, 0x7FCEE2003F00, 0x0014F3C0)
ntdll.dll!KiUserExceptionDispatcher((null):0)(0x14005C975, 0x7FCECBC03BC0, 0x14000A3A5, 0x7FCECBC00E60)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x7FCECBC03BC0, 0x14000A3A5, 0x7FCECBC00E60, 0x14000A5B6)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x7FCEE2003F00, 0x00000000, 0x7FCEE2003F00, 0x14000A437)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x7FCECAC03DC0, 0x0000000F, 0x140235D60, 0x0000000F)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x0000000F, 0x7FCEE2003F00, 0x6039691B850BE, 0x1400646DC)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x00000000, 0x7FCEE2003F00, 0x00000000, 0x140098B80)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x7FCEE2003F00, 0x7FCE00000000, 0x7FCE00000000, 0x7FFB00000000)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x7FCEE2003F00, 0x7FCEE2003F00, 0x7FCEE2003F00, 0x00000000)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x00000083, 0x7FCEE2003F00, 0x00000083, 0x7FCEE2003F00)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x7FCECE400A40, 0x7FCECE400A70, 0x00000000, 0x00000002)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x7FCECFC002A0, 0x00000000, 0x00000001, 0x00000001)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x00000000, 0x0000001B, 0x00000005, 0x00000005)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x000049BC, 0x1401DD580, 0x14025F180, 0x7FCECD800F90)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x00000002, 0x00000002, 0x00000002, 0x004D35F0)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x00000000, 0x00000000, 0x004C1C30, 0x00000000)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x00000000, 0x00000000, 0x00000000, 0x00000000)
KERNEL32.DLL!BaseThreadInitThunk((null):0)(0x00000000, 0x00000000, 0x00000000, 0x00000000)
ntdll.dll!RtlUserThreadStart((null):0)(0x00000000, 0x00000000, 0x00000000, 0x00000000)
ntdll.dll!RtlUserThreadStart((null):0)(0x00000000, 0x00000000, 0x00000000, 0x00000000)
[018876] 23 Aug 20:51:25.021 #
=== REDIS BUG REPORT END. Make sure to include from START to END. ===
Please report this bug by following the instructions at:
https://github.com/zkteco-home/redis-windows/wiki/Submitting-an-Issue
Suspect RAM error? Use redis-server --test-memory to verify it.
起因 向redis 插入大量数据 10s 左右大概10十几万数据
插入时可能会报错,报错时间点不定,大概都是运行一段时间后报错
网上能找到很多解决方法(具体执行baidu),一种主流的方法是redis配置stop-writes-on-bgsave-error设为false,但这种方法只是让出错不停止,错误还是存在的,所以不想用这种方法
另外原因大概也清楚:就是redis写入数据会先写到内存,然后每隔一段时间会把内存数据写入rdb(一个文件数据库),以实现不会因为关机内存数据丢失就没了数据。问题是在写入rdb时出错
但不知道写入rdb出错原因在哪,网上很多说是内存不够,所以先改配置提高内存 先看看情况
(之前不知道什么原因只给了redis 256mb)
maxmemory 1gb