Is the name of the thread group leader available in /proc? I am looking for the group_leader->comm field for a given task_struct.
Related
could find a precise answer to my question.
I have multiple Threads groups on my Test Plan, in all of them I created a CSV file to read a list of cars, for example:
Thread group 1 cars_thread_1.csv
Thread group 2 cars_thread_2.csv
Thread group 3 cars_thread_3.csv
But the list of cars didn't change inside the CSV files.
What's the recommended approach? Keep it like that or I can create a single CSV cars.csv and all of the threads read it?
Sure you can, just place it at the same level as Thread Groups so all of them would be in the CSV Data Set Config's scope
By default each thread will read next line from the file on each iteration, if this behaviour is not something you're looking for - you can amend Sharing Mode setting of the CSV Data Set Config.
I am looking for a way to create a critical section in Apache NiFi. What I mean by that is to create a group of processors in which a single FlowFile would be processed exclusively - the next FlowFile would be picked up for processing from a queue when the previous FlowFile finishes with the last processor of the group. Please refer to the picture attached below.
Bottom line: At most one FlowFile should be processed within the critical section. Concurrent task parameters applies only to a single processor, not a group of processors.
I want to implement access token management to NiFi API. I would like to keep the token in a cache and also to limit the number of requests to NiFi API.
You can readily do this in NiFi by putting the processors in the "critical section" into a process group (PG) with an input and output port. The PG can then be configured with a flowfile concurrency of "Single flowfile per node" to make it process only one flowfile at a time. If it needs to be single flowfile per cluster, you can use a loadbalancing strategy of "single node" in a connection before entering the PG.
I'm assuming you are making a custom access token flow because the one already present in the NiFi API doesn't do what you want it to, but if not, do check the documents. It leverages the configured identity providers and gives you an access token that lasts for the configured duration (12 hours by default I think).
I want to share all about our case.
We have Hadoop cluster with 2 name nodes, one active name node, and one standby name node.
After some time we notice that the active name node and secondary name node are down for 3 days.
After reviewing the name node log files, we see that the secondary name node was down for 1 month, and the active name node is down for a couple hours.
The other interesting thing that we see on the active name node log is name node heap size problem, as maybe some of you know is the secondary name node actually support the active name node , but secondary name node isn't replace the active name node.
Therefore we guess that the reason that active name node failed is because the active name node did not get data acknowledge from the secondary name node, and maybe it is the reason of high JVM consuming from the active name node.
I will appreciate stack-overflow users help , and your opinion about our case
I need to create an Aggregate report under a thread group with the thread group name. For Ex: If my thread group name is LoginThreadgroup I need to create an Aggregate report file, View Result Tree file name with LoginThreadgroup.jtl LoginThreadgroup_VRT.jtl
I tried to use -${__BeanShell(ctx.getThreadGroup().getName())}.jtl
and
${__threadGroupName}_ViewResultsTree_Failure_report.jtl
ETC but both dint work out well in my case.
I have many thread groups under test tree, for each, I would like to create jtl files with the respective thread group name.
Can anyone help me in this
I don't think you can use JMeter Functions and/or Variables in "Filename" field of a Listener
In general using Listeners is not the best idea as they don't add any value and simply consume CPU, RAM and Disk resources.
I would rather suggest
Adding __threadGroupName() function as a prefix/postfix to your Samplers labels
If you want separate results for different Thread Groups you can use Filter Results Tool to extract Thread-Group-specific entries from the .jtl results file
Aggregate Report can be generated using JMeterPluginsCMD Command Line Tool
I am trying to create a Kafka Streams service where
I am trying to initialize a cache in a processor, that will then be updated by consuming messages with a topic say "nodeStateChanged" for a partition key lets say locationId.
I need to check the node state when I consume another topic lets say "Report" again keyed by the same locationId. Effectively I am joining with the table created by nodeStateChanged.
How do I ensure that all the updates for nodeStateChanged fall on the same instance as the Report topic so that the lookup for a location is possible when a new report is recieved. Do 1 and 2 need to be created by the same topology or it okay to create two seperate topologies that share the same APPLICATION_ID_CONFIG.
You don't need to do anything. Kafka Streams will always co-partition topics. Ie, if you have a sub-topology that reads from multiple topics with N partitions each, you get N tasks and each task is processing corresponding partitions, ie, task 0 processes partitions zero of both input topics, task 1 processes partitions one of both input topics, etc.