You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@infra.apache.org by "Gavin (JIRA)" <ji...@apache.org> on 2014/11/22 17:56:33 UTC
[jira] [Assigned] (INFRA-8681) delayed/undelivered mail for
jamestaylor@apache.org
[ https://issues.apache.org/jira/browse/INFRA-8681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gavin reassigned INFRA-8681:
----------------------------
Assignee: Gavin
> delayed/undelivered mail for jamestaylor@apache.org
> ---------------------------------------------------
>
> Key: INFRA-8681
> URL: https://issues.apache.org/jira/browse/INFRA-8681
> Project: Infrastructure
> Issue Type: Bug
> Reporter: James Taylor
> Assignee: Gavin
> Priority: Critical
>
> My mail to/from my apache account (jamestaylor@apache.org) seems to be having problems. I'm not sure if it's an INFRA issue or something else. Please advise (see below for an example of the bounces I'm getting back).
> {code}
>
> Delivered-To: giacomotaylor@gmail.com
> Received: by 10.170.113.71 with SMTP id f68csp113691ykb;
> Fri, 21 Nov 2014 10:45:33 -0800 (PST)
> Received-SPF: pass (google.com: domain of designates 10.170.40.199 as permitted sender) client-ip=10.170.40.199
> Authentication-Results: mr.google.com;
> spf=pass (google.com: domain of designates 10.170.40.199 as permitted sender) smtp.mail=;
> dkim=pass header.i=@googlemail.com
> X-Received: from mr.google.com ([10.170.40.199])
> by 10.170.40.199 with SMTP id 190mr4937849yki.14.1416595533147 (num_hops = 1);
> Fri, 21 Nov 2014 10:45:33 -0800 (PST)
> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
> d=googlemail.com; s=20120113;
> h=mime-version:from:to:subject:message-id:date:content-type
> :content-transfer-encoding;
> bh=jIXq6AjnL5JCaDooN7nO1AmAFAw+qZIL45/9hw/8LkE=;
> b=KGci5Hp3mSKKXdFwgRNfHZKiLNqE3iLvI6jgwnO+tdQ7h906gFcckudGHueqzODdWC
> cDFf1TKLTyZewu3XMG7k9sTYXXY/DywCWC9wtadBnYg/gKtyxjqfPw0+cSEzfTcso3Ty
> L4tRrKkUaBjaSRU2uExILjPJqthxQiCJ0+u05i8gCIYsO1oeTiHToFxaUSNV83S7OBh1
> uDsyIPhPl0KC4g1H3wt1+Kuf2LxTij6om+aRYKvkQJpn3K6hikTWaoQPSRCfjTYjhG/Q
> Po8U0MSkQgOWJsX9woXWvp+2VTv8s4WlvNe8PV7FPA9yQgRdYTcgYWGYF/CZIMud74In
> 1rDA==
> X-Received: by 10.170.40.199 with SMTP id 190mr4937849yki.14.1416595533143;
> Fri, 21 Nov 2014 10:45:33 -0800 (PST)
> MIME-Version: 1.0
> Return-Path: <>
> Received: by 10.170.40.199 with SMTP id 190mr4376877yki.14; Fri, 21 Nov 2014
> 10:45:33 -0800 (PST)
> From: Mail Delivery Subsystem <ma...@googlemail.com>
> To: giacomotaylor@gmail.com
> Subject: Delivery Status Notification (Delay)
> Message-ID: <00...@google.com>
> Date: Fri, 21 Nov 2014 18:45:33 +0000
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: quoted-printable
> This is an automatically generated Delivery Status Notification
> THIS IS A WARNING MESSAGE ONLY.
> YOU DO NOT NEED TO RESEND YOUR MESSAGE.
> Delivery to the following recipient has been delayed:
> jamestaylor@apache.org
> Message will be retried for 2 more day(s)
> Technical details of temporary failure:=20
> The recipient server did not accept our requests to connect. Learn more at =
> http://support.google.com/mail/bin/answer.py?answer=3D7720=20
> [(0) people.apache.org. [140.211.11.9]:465: socket error]
> ----- Original message -----
> MIME-Version: 1.0
> X-Received: by 10.170.82.66 with SMTP id y63mr203809yky.68.1416514560796; T=
> hu,
> 20 Nov 2014 12:16:00 -0800 (PST)
> Received: by 10.170.52.151 with HTTP; Thu, 20 Nov 2014 12:16:00 -0800 (PST)
> In-Reply-To: <D0...@pnnl.gov>
> References: <D0...@pnnl.gov>
> Date: Thu, 20 Nov 2014 12:16:00 -0800
> Message-ID: <CAAF1JdiJpfWNo6pWQMkhVOEEwDgi-kUxNAhCGxbZBVXP51M-Cw@mail.gmail=
> .com>
> Subject: Re: Phoenix
> From: James Taylor <ja...@apache.org>
> To: "Perko, Ralph J" <Ra...@pnnl.gov>
> Cc: "mujtaba@apache.org" <mu...@apache.org>, James Taylor <jamestaylor@ap=
> ache.org>
> Content-Type: text/plain; charset=3DUTF-8
> Content-Transfer-Encoding: quoted-printable
> Hi Ralph,
> Thanks for the encouraging words - glad to hear it's helped.
> What version of Phoenix are you using and when did you start seeing
> these issues? Those numbers you mention are within the bounds of what
> Phoenix is intended to handle. We might need to work with you to tune
> things appropriately.
> Regards,
> James
> On Thu, Nov 20, 2014 at 12:10 PM, Perko, Ralph J <Ra...@pnnl.gov> wro=
> te:
> > James and Mujtaba,
> >
> > I am a big fan of the Phoenix project. I have found it very helpful and =
> it
> > has significantly reduced my development time. Having implemented salted
> > buckets, secondary indexes and DAO layers on top of Hbase myself in the p=
> ast
> > I can appreciate the effort required in a project such as this - it has b=
> een
> > a huge time saver. I also really like your co=E2=80=93processor approach=
> . We have
> > a very tight schedule and it would be tough to hit our goal if I had to
> > write all my queries manually in hbase.
> >
> > I have recently run into significant issues while trying to query the
> > system. Simple queries such as =E2=80=9Cselect * from SOMETABLE limit 10=
> ;=E2=80=9D throws
> > errors. I am wrestling with a lot of timeouts of various sorts (rpc,
> > expired leases and seemingly random unknown errors). Adjustments to what
> > seem to be relevant settings just cause different errors to show. Anyth=
> ing
> > other an indexed query fails.
> >
> > My current environment is a 30 node cluster with over 7B records. The da=
> ta
> > was loaded with the CsvBulkLoadTool. Once live this will increase by a r=
> ate
> > of 2 =E2=80=93 3 B records/day. I need to support queries that will retu=
> rn tens of
> > thousands of results.
> >
> > Am I exceeding the capability of Phoenix beyond its original intent? Hav=
> e
> > you seen the issues I am talking about? Are these issues largely Phoenix=
> ,
> > HBase (or user) issues? I am wondering if I should be considering a
> > different approach. I am happy to post this on the user=E2=80=99s forum =
> if you like
> > but wanted to run this by you first.
> >
> > Thank you and best regards,
> > Ralph Perko
> ----- Message truncated -----
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)