You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
2015/01/01 05:32:01.548419 <autogenerated>:50: [WARN] Unexpected error updating node key: 100: Key not found (/workflows/nodes/XYZ) [1682348]
2015/01/01 05:32:01.549067 <autogenerated>:50: [ERROR] Error deleting handled command /workflows/nodes/XYZ: 100: Key not found (/workflows/nodes/XYZ) [1682349]
2015/01/01 05:32:01.549135 <autogenerated>:50: [ERROR] Invalid command /workflows/nodes/XYZ: unexpected end of JSON input
Due to network issues metafora wasn't able to update its node key before the node key's 20s TTL expired. This is expected behavior during network partitions.
However, the coordinator incorrectly tried to interpret the key expiration event as a command (second line) and obviously couldn't (third line).
So luckily this is a noop, but it's pretty scary that the command watcher can even interpret node keys as commands. The command watcher deletes handled commands, so having it touch the node key at all is scary.
This method should be improved to insure we never try to treat node keys as commands:
From an internal metafora app:
Due to network issues metafora wasn't able to update its node key before the node key's 20s TTL expired. This is expected behavior during network partitions.
However, the coordinator incorrectly tried to interpret the key expiration event as a command (second line) and obviously couldn't (third line).
So luckily this is a noop, but it's pretty scary that the command watcher can even interpret node keys as commands. The command watcher deletes handled commands, so having it touch the node key at all is scary.
This method should be improved to insure we never try to treat node keys as commands:
metafora/m_etcd/coordinator.go
Lines 385 to 402 in 4862f92
The text was updated successfully, but these errors were encountered: