About J-D

J-D · ‎09-11-2018

Hi, This was missed in the docs, I opened an internal ticket to have it added to that page. We did the 6.0 certification on RHEL-compatible 7.5 OSes back in June. Sorry about this! J-D

J-D · ‎04-19-2018

It's hard to tell from just this log snippet if anything really bad is happening, but for sure you have a tablet server that seems to be gone (192.168.1.XX:7050: connect: Connection refused) during that time. Is ksck returning all ok? Do you have a range partition that covers the time range you are writing into?

J-D · ‎03-16-2018

Hi, This looks like a different flavor of something we encountered while testing Sentry in 5.13 (that we didn't resolve). I pinged a few folks internally. FWIW I tried just spinning up a secure CM5.14.1 + CDH5.12.2 cluster with all the services and my HMS came up just fine without that config. Can you describe more how you upgraded CM, if any other configs were changed before/after the upgrade, and if you added any services before or after? As an aside, the Impala forum is probably not the best place to get help for this issue. Thanks, J-D

J-D · ‎02-15-2018

Hi Rajesh, Yes that's what it means. J-D

J-D · ‎08-28-2017

" PARTITIONS 1" means that you are trying to create a table with 1 hash bucket, you need at least 2 (like the error you're getting says). This is a way to force you to think about how you want to distribute your data. Only 2 tservers won't work with the default replication factor of 3, as per http://kudu.apache.org/docs/known_issues.html#_tables

J-D · ‎08-28-2017

@hindog wrote: " Nor the browser column" -- What if the "browser" column WAS the primary key? Would increment be possible in similar fashion to upsert, the difference being that internally Kudu would read the existing value and add it to the increment value before saving? The other Kudu limitation that this runs into is that row key columns cannot be modified. It would be somewhat easier to implement atomic increments on non-key columns, but then that means doing a lot of updates and it's not something Kudu excels at e.g. it supports modifying data but the higher the rate the slower the reads are.

J-D · ‎07-31-2017

Kudu doesn't do anything special to resolve hostnames, so it should use the hosts file by way of doing the resolving. You can also see a 5s delay when trying to resolve the address, I would recommend googling "dns 5 seconds delay" and debug your network situation from there.

J-D · ‎07-21-2017

Deletes like this should be fine, even more ideal when you need to delete huge batches of rows is to hopefully have range partitions setup so that you can just drop them (see this doc), but for millions of rows it shouldn't timeout unless there's something misconfigured.

J-D · ‎07-21-2017

Dropping the table and recreating it would be a lot more efficient than deleting every row one by one after reading them (which is what "delete from" does). All the logs that pertain to tablet 871c8123905c4e529a233c18751f8154 for that tablet server could be useful. The full INFO file would be perfect if you can zip it and host it on a server somewhere.

J-D · ‎07-21-2017

You need to run ksck as the Kudu superuser in order to get the full functionality, this is defined by "--superuser_acl" and it defaults to the user that runs Kudu which is normally "kudu".

J-D · ‎07-21-2017

In Kudu, doing a delete like this is basically like inserting as many rows as you are deleting, so this might not be what you want to do. In any case, we'd need a lot more logs from nod7.exp to understand what's going on. My guess is that Kudu doesn't have enough memory, sometimes CM can configure it to use 1GB which is below the safe minimum.

J-D · ‎06-30-2017

Any chance some of you are running on Azure? It has known issues with ntp: https://social.msdn.microsoft.com/Forums/azure/en-US/8c0a1026-0b02-405a-848e-628e68229eaf/i-have-a-lot-of-time-has-been-changed-in-the-journal-of-my-linux-boxes?forum=WAVirtualMachinesforWindows

J-D · ‎06-23-2017

Ok so it seems the things you previously pasted were resolved when your Kudu cluster finished booting up. When you say "same error", you mean on the client side you're still getting timeouts? I'm asking because what you're showing after that are warnings, not errors, and it's perfectly normal to get memory pushback when servers are too busy. Now this can either mean two things: you're trying to insert faster than Kudu can ingest it based on the resources (disks/ram/cpu) it's given, or there's something wrong with flushing and it's too slow. Having a much bigger log snippet from wewcw0hd3dn01 or wewcw0hd3dn04 would help.

J-D · ‎06-23-2017

Ok, with 1 disk you wouldn't want more than 1 maintenance manager threads. The log lines you showed can mean that the tablet server is still starting up. Depending on the amount of data and the number of tablets, it can take minutes. You can also run "kudu cluster ksck <master_addresses" to see what's up the all the tablets.

J-D · ‎06-23-2017

Hi, 2GB is still on the small side, especially if you have a lot of tablets. Here's the recommendation: http://kudu.apache.org/docs/known_issues.html#_server_management Also, which version of Kudu? How many data dirs? How many maintenance manager threads? Thanks, J-D

J-D · ‎06-17-2017

This question has been posted in many different places and it seems to be related to the fact that this is run from a Windows host which has never been tested. It's not clear it's really a TLS issue. @mbigelow wrote: I would try loading the CA cert that signed the certs for the Kudu master and worker nodes into the JSSE truststore. Do this on the host you are running the Kudu app on. Then any Java applications will use it when negotiating TLS handshakes. You could also create a truststore and use that when launching the Kudu app. https://www.cloudera.com/documentation/enterprise/5-8-x/topics/cm_sg_create_key_trust.html That's not how it works in Kudu though, the CA cert is stored in the Kudu master, no messing with JSSE, see http://kudu.apache.org/docs/security.html

J-D · ‎05-08-2017

Hi, This is likely to be slow, as described in this section of the documentation: http://kudu.apache.org/docs/kudu_impala_integration.html#kudu_impala_insert_bulk There isn't much you can do about this, except going the " Batch Insert" route as described in the link above. J-D

J-D · ‎04-27-2017

Hi, Kudu currently doesn't support atomic increments or any kind of operation that reads a value and makes a decision based on that value with the guarantee that it won't change. Thx, J-D

J-D · ‎04-03-2017

Hi Amit, Your understanding is correct, we can't share dates. For Kudu we work hard to pickup new upstream as fast as we can but in general our internal timelines cannot match every single open source project that Cloudera supports so there's always going to be a delay. Hope this helps, J-D

J-D · ‎03-21-2017

Hi, This is a current limitation in Kudu (see the second bullet point): http://kudu.apache.org/docs/known_issues.html#_schema_and_usage_limitations Putting ent_ts first in the schema will solve this. Arguably the error message could be better. Regards, J-D

J-D · ‎01-30-2014

* Is this available in CDH4.5.0 running with hbase 0.94.6? It is available in 0.94.6-cdh4.5.0 yes. * Do i set this in the safety valvle for the regionserver settings? Yes. * Can I verify this is the current policy running on major compactions? Major compactions compact all the files, so there isn't a policy in use here. Best I can tell you can't really see if the policy is in effect when file selection is done for minor compactions. One thing you can do is look at the list of configurations on a running region server, go to one of your region server's web UI and put /conf after the port then look for hbase.hstore.useExploringCompation. It won't be listed in 4.0.0 but in 4.5.0 it should be there and set to true if you set useExploringCompation correctly.

Online	Offline
Last Visited	‎04-26-2019 04:13 PM

Date Registered	‎07-08-2013 03:33 PM
Last Visited	‎04-26-2019 04:13 PM
Total Messages Posted	60
Total Kudos Received	4

Re: CDH 6 Supported OS

Re: What does "Multi-datacenter is not supported" ...

Re: Error during CREATE KUDU table using IMPALA

Re: Errors gathering consensus info for Tablet Ser...

Re: kudu soft memory error

Re: CDH 6 Supported OS

Re: KUDU: RPC Error from Vote Request

Re: Hive Metastore fails to start after upgrading ...

Re: What does "Multi-datacenter is not supported" ...

Re: Error during CREATE KUDU table using IMPALA

Re: Kudu increment update support

Re: DNS Error when trying to insert data in Kudu t...

Re: Error in delete from kudu table -WARNINGS:..Ti...

Re: Error in delete from kudu table -WARNINGS:..Ti...

Re: Errors gathering consensus info for Tablet Ser...

Re: Error in delete from kudu table -WARNINGS:..Ti...

Re: kudu service are getting down frequently

Re: kudu soft memory error

Re: kudu soft memory error

Re: kudu soft memory error

Re: Kudu TLS Error

Re: batch insert into kudu table via using impala ...

Re: Kudu increment update support

Re: When will Kudu 1.3.0 parcel be available?

Re: Received ImpalaRuntimeException: Error creatin...

Re: CDH4.5 enable ExploringCompaction