On Sun, Jun 11, 2017 at 3:21 AM, Ashish Singhi <ashishsin...@apache.org> wrote:
> I installed the version on a single node cluster with hadoop 2.7.3 version > on server side and default hadoop version at client side in HBase i.e., > 2.7.1 and didn't see any such log warning message. > @Umesh: what hadoop version are you using ? > > > Belated +1 on the RC. > Build the tar ball from the source code, > Exercised some shell commands. > Ran bulk load, import, export job. > Checked audit logs for the operations executed. > > Thanks for the vote Ashish and thanks for taking a look at the log message. Let me tackle Umesh Monday -- I mean, Tuesday... Monday is hbasecon (we sit beside each other). Thanks, St.Ack > Regards, > Ashish > > On Sun, Jun 11, 2017 at 11:48 AM, Ashish Singhi <ashishsin...@apache.org> > wrote: > > > It should not. > > I will try to find some time today and install the alpha release and > check > > this part. > > > > Thanks, > > Ashish > > > > On Sun, Jun 11, 2017 at 12:02 AM, Stack <st...@duboce.net> wrote: > > > >> On Sat, Jun 10, 2017 at 1:35 AM, Ashish Singhi <ashishsin...@apache.org > > > >> wrote: > >> > >> > Its not an issue. The log warnings are coming by HBASE-9393 patch. If > >> user > >> > Hadoop version is not 2.6.4+ or 2.7.0+ then this warn message will be > >> > logged, notifying user about a CLOSE_WAIT connection left behind. As > >> this > >> > log message is in common code flow of read, should we up the log level > >> to > >> > avoid too many same warnings ? > >> > > >> > > >> The alpha has hadoop-2.7.1. Should we be getting the above logs in this > >> case? (Correct me Umesh if you came up on a different hadoop -- I don't > >> think you did). > >> > >> S > >> > >> > >> > >> > Regards, > >> > Ashish > >> > > >> > On Fri, Jun 9, 2017 at 10:45 AM, Stack <st...@duboce.net> wrote: > >> > > >> > > Oh, maybe file issues for what you found boss? > >> > > St.Ack > >> > > > >> > > On Thu, Jun 8, 2017 at 10:15 PM, Stack <st...@duboce.net> wrote: > >> > > > >> > > > Thanks Umesh! > >> > > > > >> > > > On Thu, Jun 8, 2017 at 2:36 PM, Umesh Agashe < > uaga...@cloudera.com> > >> > > wrote: > >> > > > > >> > > >> +1 > >> > > >> > >> > > >> - Downloaded the src tarball. > >> > > >> - Verified the checksums and signature. Looks good. > >> > > >> - Built from source. openjdk version "1.8.0_102" > >> > > >> - mvn apache-rat:check Passed > >> > > >> > >> > > >> - Download the bin tarball. > >> > > >> - Verified the checksums and signature. Looks good. > >> > > >> - Extracted it. Layout looks good. > >> > > >> - Started a local instance. Ran the 'hbase shell' with some > basic > >> > > table > >> > > >> commands. Looks good. > >> > > >> - Ran ltt with 10 million rows and 2 columns/ row > >> > > >> > >> > > >> Note: > >> > > >> - Did not run unit tests. There are a problems with the build. > >> See: > >> > > >> https://builds.apache.org/job/HBase-2.0/jdk=JDK%201.8%20(lat > >> > > >> est),label=Hadoop/10/console > >> > > >> - Noticed a few errors in the log file like: > >> > > >> WARN [MemStoreFlusher.1] io.FSDataInputStreamWrapper: Failed to > >> > invoke > >> > > >> 'unbuffer' method in class class org.apache.hadoop.fs. > >> > FSDataInputStream > >> > > . > >> > > >> So there may be a TCP socket connection left open in CLOSE_WAIT > >> state. > >> > > >> > >> > > >> > >> > > >
