[{"data":1,"prerenderedAt":421},["ShallowReactive",2],{"docs-nav":3,"docs-page-\u002Fdocs\u002Fconsumer-groups\u002Foverview":133},[4,27,53,68,83,98,117],{"slug":5,"label":6,"pages":7},"get-started","Get Started",[8,12,17,22],{"path":9,"title":10,"order":11},"\u002Fdocs","Welcome",0,{"path":13,"title":14,"navTitle":15,"order":16},"\u002Fdocs\u002Fget-started\u002Fquickstart","Quickstart",null,1,{"path":18,"title":19,"navTitle":20,"order":21},"\u002Fdocs\u002Fget-started\u002Fconnect-to-a-cluster","Connecting to a Kafka Cluster","Clusters",2,{"path":23,"title":24,"navTitle":25,"order":26},"\u002Fdocs\u002Fget-started\u002Flicense","Licensing and Activation","License",3,{"slug":28,"label":29,"pages":30},"console","Console",[31,35,39,43,48],{"path":32,"title":33,"navTitle":34,"order":16},"\u002Fdocs\u002Fconsole\u002Foverview","Produce and Consume Messages in the Kafka Console","Overview",{"path":36,"title":37,"navTitle":38,"order":21},"\u002Fdocs\u002Fconsole\u002Fconsuming-messages","Kafka Consumer: Reading Messages from a Topic","Consuming",{"path":40,"title":41,"navTitle":42,"order":26},"\u002Fdocs\u002Fconsole\u002Fdecoding-messages","Decoding Kafka Avro and Protobuf Messages","Decoding",{"path":44,"title":45,"navTitle":46,"order":47},"\u002Fdocs\u002Fconsole\u002Fproducing-messages","Kafka Producer: Sending Messages to a Topic","Producing",4,{"path":49,"title":50,"navTitle":51,"order":52},"\u002Fdocs\u002Fconsole\u002Freplay-forward-and-export","Replay and Export Kafka Messages","Replay & export",5,{"slug":54,"label":55,"pages":56},"topics","Topics",[57,60,64],{"path":58,"title":59,"navTitle":34,"order":16},"\u002Fdocs\u002Ftopics\u002Foverview","Browse and Inspect Kafka Topics",{"path":61,"title":62,"navTitle":63,"order":21},"\u002Fdocs\u002Ftopics\u002Fcreate-a-topic","Create a Kafka Topic: Partitions, Replication, and Retention","Create a topic",{"path":65,"title":66,"navTitle":67,"order":26},"\u002Fdocs\u002Ftopics\u002Fpartitions-and-records","Adding Kafka Partitions and Deleting Records","Partitions & records",{"slug":69,"label":70,"pages":71},"schema-registry","Schema Registry",[72,75,79],{"path":73,"title":74,"navTitle":34,"order":16},"\u002Fdocs\u002Fschema-registry\u002Foverview","Browse Kafka Schema Registry Subjects and Versions",{"path":76,"title":77,"navTitle":78,"order":21},"\u002Fdocs\u002Fschema-registry\u002Fnew-versions","Register Kafka Schemas and Publish New Versions","New versions",{"path":80,"title":81,"navTitle":82,"order":26},"\u002Fdocs\u002Fschema-registry\u002Fmock-and-lab","Avro Schema Validator and Mock Data Generator","Mock & Lab",{"slug":84,"label":85,"pages":86},"consumer-groups","Consumer Groups",[87,90,94],{"path":88,"title":89,"navTitle":34,"order":16},"\u002Fdocs\u002Fconsumer-groups\u002Foverview","Browse Kafka Consumer Groups and Assignments",{"path":91,"title":92,"navTitle":93,"order":21},"\u002Fdocs\u002Fconsumer-groups\u002Flag","Monitor Kafka Consumer Lag","Lag",{"path":95,"title":96,"navTitle":97,"order":26},"\u002Fdocs\u002Fconsumer-groups\u002Freset-offsets","Reset Kafka Consumer Group Offsets","Reset offsets",{"slug":99,"label":100,"pages":101},"data-clone","Data Clone",[102,105,109,113],{"path":103,"title":104,"navTitle":34,"order":16},"\u002Fdocs\u002Fdata-clone\u002Foverview","Clone Kafka Topics Between Clusters",{"path":106,"title":107,"navTitle":108,"order":21},"\u002Fdocs\u002Fdata-clone\u002Fscope-and-range","Configure Kafka Topic Cloning","Scope & range",{"path":110,"title":111,"navTitle":112,"order":26},"\u002Fdocs\u002Fdata-clone\u002Fmasking","Mask Sensitive Data in Kafka Messages","Masking",{"path":114,"title":115,"navTitle":116,"order":47},"\u002Fdocs\u002Fdata-clone\u002Fpre-flight","Run Pre-flight Checks Before a Kafka Data Clone","Pre-flight",{"slug":118,"label":119,"pages":120},"operate","Operate",[121,125,129],{"path":122,"title":123,"navTitle":124,"order":16},"\u002Fdocs\u002Foperate\u002Fbrokers","Inspect Kafka Brokers and Cluster Configuration","Brokers",{"path":126,"title":127,"navTitle":128,"order":21},"\u002Fdocs\u002Foperate\u002Faccess-control","Inspect Kafka ACLs and Simulate Access","Access Control",{"path":130,"title":131,"navTitle":132,"order":26},"\u002Fdocs\u002Foperate\u002Factivity-logs","Review Kafka Changes in Kafma Activity Logs","Activity Logs",{"id":134,"title":89,"body":135,"description":412,"extension":413,"lastUpdated":414,"meta":415,"navTitle":34,"navigation":416,"order":16,"path":88,"seo":417,"sitemap":418,"stem":419,"__hash__":420},"docs\u002Fdocs\u002Fconsumer-groups\u002Foverview.md",{"type":136,"value":137,"toc":402},"minimark",[138,142,147,150,153,157,160,168,172,191,207,210,219,223,226,233,244,252,256,322,342,351,355,358,377,380,384],[139,140,141],"p",{},"Kafma lists the consumer groups known to the connected cluster. Use the list to\nfind a group, check whether it is active, and inspect its assignments and\nmembers from the same page.",[143,144,146],"h2",{"id":145},"what-is-a-kafka-consumer-group","What is a Kafka consumer group?",[139,148,149],{},"A Kafka consumer group is a set of consumers that share a group ID and divide\ntopic partitions between them. Within the group, each assigned partition is\nread by one member at a time. Adding members can increase parallelism up to the\nnumber of partitions, provided those members subscribe to the topic.",[139,151,152],{},"Different consumer groups read the same topic independently. Each group keeps\nits own committed position for every partition, so one application can be\ncaught up while another is still processing older records.",[143,154,156],{"id":155},"what-is-a-kafka-consumer-offset","What is a Kafka consumer offset?",[139,158,159],{},"An offset identifies a position in one Kafka partition. Because every partition\nhas its own offset sequence, an offset is meaningful only with its topic and\npartition.",[139,161,162,163,167],{},"A consumer group commits offsets to record where it should continue. A\ncommitted offset normally points to the next record the group should read, not\nthe last record it processed. Kafma shows these committed offsets beside each\npartition's end offset, making it possible to inspect assignments and calculate\n",[164,165,166],"a",{"href":91},"consumer lag",".",[143,169,171],{"id":170},"list-and-filter-kafka-consumer-groups","List and filter Kafka consumer groups",[139,173,174,175,179,180,179,183,186,187,190],{},"Search by group ID or filter by ",[176,177,178],"strong",{},"Stable",", ",[176,181,182],{},"Rebalancing",[176,184,185],{},"Empty",", or\n",[176,188,189],{},"Dead",". Each row shows:",[192,193,194,198,201,204],"ul",{},[195,196,197],"li",{},"The group protocol.",[195,199,200],{},"Its state and active member count.",[195,202,203],{},"Its topic and partition assignment.",[195,205,206],{},"Total lag and the number of lagging partitions.",[139,208,209],{},"Refresh the list when membership or assignments change. Pin frequently checked\ngroups to the Watchlist for quicker access from Home.",[139,211,212],{},[213,214],"img",{"alt":215,"height":216,"src":217,"width":218},"Kafka consumer group list with group state, active members, assignments, and total lag",1008,"https:\u002F\u002Fmedia.kafma.app\u002Fdocs\u002Fconsumer-groups\u002Foverview\u002Fconsumer-group-list.png",1556,[143,220,222],{"id":221},"inspect-members-and-topic-assignments","Inspect members and topic assignments",[139,224,225],{},"Select a group to open its details in a drawer without leaving the Consumer\nGroups page. The summary shows its state, member count and assignor, total lag,\nmaximum partition lag, and recent lag trend.",[139,227,228,229,232],{},"Expand a topic to see each partition's committed offset, lag, and current\nassignment. The ",[176,230,231],{},"Members"," section maps member IDs and hosts to their topic and\npartition assignments, which helps locate the process handling a partition.",[139,234,235,236,239,240,243],{},"Use the Console action beside a topic, or hover over an assigned partition and\nselect ",[176,237,238],{},"Inspect",", to open ",[176,241,242],{},"Watch Group"," at the group's committed positions.\nThis connects assignment data to the messages the consumer is approaching.",[139,245,246],{},[213,247],{"alt":248,"height":249,"src":250,"width":251},"Kafka consumer group details showing state, members, topic assignments, committed offsets, and lag",1312,"https:\u002F\u002Fmedia.kafma.app\u002Fdocs\u002Fconsumer-groups\u002Foverview\u002Fconsumer-group-details.png",1560,[143,253,255],{"id":254},"understand-group-state-and-protocol","Understand group state and protocol",[257,258,259,272],"table",{},[260,261,262],"thead",{},[263,264,265,269],"tr",{},[266,267,268],"th",{},"Value",[266,270,271],{},"Meaning",[273,274,275,285,294,303,312],"tbody",{},[263,276,277,282],{},[278,279,280],"td",{},[176,281,178],{},[278,283,284],{},"The group has completed assignment and is not rebalancing",[263,286,287,291],{},[278,288,289],{},[176,290,182],{},[278,292,293],{},"Members or assignments are currently changing",[263,295,296,300],{},[278,297,298],{},[176,299,185],{},[278,301,302],{},"The group has no active members but may still have committed offsets",[263,304,305,309],{},[278,306,307],{},[176,308,189],{},[278,310,311],{},"The coordinator no longer considers the group active",[263,313,314,319],{},[278,315,316],{},[176,317,318],{},"Unknown",[278,320,321],{},"Kafka did not return a recognized state",[139,323,324,325,328,329,333,334,337,338,341],{},"The badge is Kafma's classification of the protocol type returned by Kafka.\n",[176,326,327],{},"CLASSIC"," means Kafka reported the standard ",[330,331,332],"code",{},"consumer"," protocol. ",[176,335,336],{},"SIMPLE","\ncovers other protocol types. These groups can have saved offsets without a\nstandard consumer assignment, so ",[176,339,340],{},"Unassigned"," is not necessarily an error.",[139,343,344,345,347,348,350],{},"State and lag answer different questions. A ",[176,346,178],{}," group can still be\nbehind, while an ",[176,349,185],{}," group can show zero lag if no new records have\narrived.",[143,352,354],{"id":353},"delete-a-kafka-consumer-group","Delete a Kafka consumer group",[139,356,357],{},"Stop all consumers before deleting a group. Kafka rejects deletion while the\ngroup is active.",[139,359,360,361,364,365,368,369,372,373,376],{},"Deleting a group removes the group and its committed offsets. It does not delete\ntopics or messages. If the application later starts with the same group ID,\nKafka has no committed offset to return. The consumer then applies\n",[330,362,363],{},"auto.offset.reset"," for each partition: ",[330,366,367],{},"earliest"," starts at the oldest retained\noffset, ",[330,370,371],{},"latest"," starts at the current end, and ",[330,374,375],{},"none"," fails instead of choosing\na position.",[139,378,379],{},"Write actions are unavailable on read-only connections.",[143,381,383],{"id":382},"next-steps","Next steps",[192,385,386,391,396],{},[195,387,388],{},[164,389,390],{"href":91},"Monitor Kafka consumer lag",[195,392,393],{},[164,394,395],{"href":95},"Reset Kafka consumer group offsets",[195,397,398],{},[164,399,401],{"href":400},"\u002Fdocs\u002Fconsole\u002Fconsuming-messages#live-and-watch-group-modes","Watch a consumer group in the Console",{"title":403,"searchDepth":26,"depth":26,"links":404},"",[405,406,407,408,409,410,411],{"id":145,"depth":21,"text":146},{"id":155,"depth":21,"text":156},{"id":170,"depth":21,"text":171},{"id":221,"depth":21,"text":222},{"id":254,"depth":21,"text":255},{"id":353,"depth":21,"text":354},{"id":382,"depth":21,"text":383},"Browse Kafka consumer groups and assignments in Kafma. Inspect group state, members, protocols, committed offsets, and total consumer lag.","md","2026-08-01",{},true,{"title":89,"description":412},{"loc":88},"docs\u002Fconsumer-groups\u002Foverview","2tBKNThLvs7AFY46_JW5SJN3VJCtsinfCPws-yscBU0",1785561255515]