[
https://issues.apache.org/jira/browse/TS-4102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Fang updated TS-4102:
---------------------------
Description:
Requiring sha1 from https://luarocks.org/modules/kikito/sha1
in global hook mode would cause traffic server to dead-loop and 100% cpu util,
then killed by TM & restarted.
This creates a "start -> high cpu dead-loop -> killed" dead end.
By chaning "local PRELOAD_CACHE = true" in sha1.lua to "local PRELOAD_CACHE =
false", ts_lua will started successfully.
i am not sure if this is a bug of luajit/sha1/ts_lua, but requires sha1 from
bare luajit command-line without disable PRELOAD_CACHE works fine.
was:
require sha1 from https://luarocks.org/modules/kikito/sha1
would cause traffic server to dead-loop and 100% cpu util,
then killed by TM & restarted.
entering a start, high cpu dead-loop, killed dead end.
by chaning "local PRELOAD_CACHE = true" in sha1.lua to
"local PRELOAD_CACHE = false", ts_lua will started successfully.
i am not sure if this is a bug of luajit/sha1/ts_lua, but
requires sha1 from luajit command line without disable PRELOAD_CACHE orks
fine.
> sha1.lua cause traffic server dead loop
> ---------------------------------------
>
> Key: TS-4102
> URL: https://issues.apache.org/jira/browse/TS-4102
> Project: Traffic Server
> Issue Type: Bug
> Components: Lua
> Reporter: James Fang
>
> Requiring sha1 from https://luarocks.org/modules/kikito/sha1
> in global hook mode would cause traffic server to dead-loop and 100% cpu
> util, then killed by TM & restarted.
> This creates a "start -> high cpu dead-loop -> killed" dead end.
> By chaning "local PRELOAD_CACHE = true" in sha1.lua to "local PRELOAD_CACHE =
> false", ts_lua will started successfully.
> i am not sure if this is a bug of luajit/sha1/ts_lua, but requires sha1 from
> bare luajit command-line without disable PRELOAD_CACHE works fine.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
