making multi line work? Dead lock recursive locking
See original GitHub issueI have some events on multi line
2019-03-18 06:06:48.859 INFO [manage-xxx-service,,,] [10.2.7.19] 1 --- [-15276-thread-1] o.a.k.clients.consumer.ConsumerConfig : ConsumerConfig values:
auto.commit.interval.ms = 5000
auto.offset.reset = latest
bootstrap.servers = [my-kafka-service:9092]
check.crcs = true
So I added this line:
manage-xxx-service:
<<: *glog
from:
pod: my-xxx-service
multiline:
firstline: /^\d{4}-\d{2}-\d{2} \d{2}:\d{2}:\d{2}/
sourcetype: kube:my-xxx-service
Which produces this config:
<filter tail.containers.var.log.containers.my-xxx-service*my-xxx-service*.log>
@type concat
key log
timeout_label @SPLUNK
stream_identity_key stream
multiline_start_regexp /^\d{4}-\d{2}-\d{2} \d{2}:\d{2}:\d{2}/
flush_interval 5s
</filter>
I’m getting an error “deadlock; recursive locking”
2019-03-18 05:13:54 +0000 [warn]: #0 dump an error event: error_class=ThreadError error="deadlock; recursive locking" location="/usr/local/bundle/gems/fluent-plugin-concat-2.3.0/lib/fluent/plugin/filter_concat.rb:144:in `synchronize'" tag="tail.containers.var.log.containers.my-xxx-service-85855985fc-pgl6g_yyy_my-incident-service-0ee1814dcd3596c96e0bf6c0a2e65a9437cf1b282a95daf41fbd6e8933df1f8f.log" time=
What am I doing wrong?
Issue Analytics
- State:
- Created 5 years ago
- Comments:17 (1 by maintainers)
Top Results From Across the Web
PThread RWLock Deadlocking with Recursive Locks
pthread_rwlock supports recursive read locking, but not recursive write locking. If you write lock the lock while you already hold it, ...
Read more >Recursive (Re-entrant) Locks - Stephen Cleary
The problem with our “multi-lock” is that semaphores don't natively support recursion. If one method acquires the semaphore and calls another ...
Read more >Deadlock with multi-row INSERTs despite ON CONFLICT DO ...
Else, mutually entangled inserts trying to enter identical index tuples in the unique index can lead to the deadlock you observed. The manual:....
Read more >The case of the recursively-acquired non-recursive lock, and ...
A customer encountered a deadlock due to unexpected reentrancy, and they were looking for guidance in fixing it. Here's the code in question ......
Read more >Recursive locks (Linus Torvalds) - Yarchive
The "countingness" means that there can be multiple users inside of it, ... Put another way: a read-write lock is not a "recursive...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I can confirm 1.0.1 removed the errors
I have pushed the settings via configmap, so all containers should be having these settings.