[ https://issues.apache.org/jira/browse/KUDU-2342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16397618#comment-16397618 ]
Todd Lipcon commented on KUDU-2342: ----------------------------------- {code} if (s.ok() && peer_pb && peer_pb->member_type() == RaftPeerPB::NON_VOTER && peer_pb->attrs().promote()) { // This peer is ready to promote. // // TODO(mpercy): Should we introduce a function SafeToPromote() that // does the same calculation as SafeToEvict() but for adding a VOTER? NotifyObserversOfPeerToPromote(peer->uuid()); {code} I think Mike's TODO here is relevant. Basically we ended up proposing an uncommittable config change here. > Insert into Lineitem table with 1340 tablets on 129 node cluster failed with > "Failed to write batch " > ----------------------------------------------------------------------------------------------------- > > Key: KUDU-2342 > URL: https://issues.apache.org/jira/browse/KUDU-2342 > Project: Kudu > Issue Type: Bug > Components: tablet > Affects Versions: 1.7.0 > Reporter: Mostafa Mokhtar > Assignee: Alexey Serbin > Priority: Blocker > Labels: scalability > Attachments: Impala query profile.txt, tablet-info.html > > > While loading TPCH 30TB on 129 node cluster via Impala, write operation > failed with : > Query Status: Kudu error(s) reported, first error: Timed out: Failed to > write batch of 38590 ops to tablet b8431200388d486995a4426c88bc06a2 after 1 > attempt(s): Failed to write to server: a260dca5a9c846e99cb621881a7b86b8 > (vc1515.halxg.cloudera.com:7050): Write RPC to X.X.X.X:7050 timed out after > 180.000s (SENT) -- This message was sent by Atlassian JIRA (v7.6.3#76005)