Thanks for sharing your experiences,Vaclav. That's very valuable. Yes, for (1) bad things can happen if a region server doesn't have the Phoenix jar. This was improved as of HBase 0.98.9 with HBASE-12573 and HBASE-12575. For (3), this was fixed as of Phoenix 3.1/4.1 with PHOENIX-1075. If you have a chance, would you mind filing a JIRA for (2) with as much detail as you have?
Thanks, James On Wed, Jan 7, 2015 at 12:39 PM, Vaclav Loffelmann <[email protected]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > > here's my 2 cents. We've had few serious issues before deploy on > production. > > 1) deploying new server without Phoenix jar - make sure you have > properly configured tool for automatic server maintaining > 2) inserting empty string (byte array) to Phoenix - cause to our use > case this has impact several hours later. > 3) upgrading Phoenix - There was bug with priorities when evaluating > math expressions. > > We are using micro service architecture with node.js. There are few libs > we are participation at[1-4]. > > Our use-case is very simple: aggregate data (sum, avg, ..) on region > server side. We aggregate time series data as client demand timerange. > Phoenix is very use full on this, thanks to parallel querying. > > There are of course easy way, how to add own functionality - creating > build in functions. There [5] is old post, how to do that although > fundamentals are still same. > > So there are one basic advice: Don't underestimate testing. > > [1] > https://github.com/falsecz/byter#support-for-hbase-phoenix-v-300-data-types > [2] https://github.com/falsecz/node-phoenix-proxy > [3] https://github.com/falsecz/phoenix-proxy-server > [4] https://github.com/falsecz/node-hbase > [5] > http://phoenix-hbase.blogspot.cz/2013/04/how-to-add-your-own-built-in-function.html > > - -- > Vaclav Loffelmann > Software Architect > Socialbakers > > > On Thu, Jan 1, 2015 at 11:21 PM, Siddharth Ubale > <[email protected]> wrote: > >> Hi Guys, >> >> >> >> We are seriously thinking of phoenix in Production environment , > however, >> we have no much data of how Phoenix is behaving in production. >> >> Can anyone let us know if anyone is using Phoenix in Production and >> any challenges which they have experienced. >> >> >> >> Thanks, >> >> Siddharth Ubale, >> >> *Synchronized Communications * >> >> *#43, Velankani Tech Park, Block No. II, * >> >> *3rd Floor, Electronic City Phase I,* >> >> *Bangalore – 560 100* >> >> *Tel : +91 80 3202 4060 <%2B91%2080%203202%204060>* >> >> *Web:* *www.syncoms.com* <http://www.syncoms.com/> >> >> *[image: LogoNEWmohLARGE]* >> >> *London*|*Bangalore*|*Orlando* >> >> >> >> *we innovate, plan, execute, and transform the business* >> > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1 > > iQEcBAEBAgAGBQJUrZl/AAoJEG3mD8Wtuk0W1DQH/08aFzMoXosLg+9BMyi9OWH+ > kwbrE5zlnOwb0dnTQSPC220OGt1LmvEcycISUCV/1IcNOlMyd9p0YWQgLYqQ+6Nk > 3YZnvM4BGXblyqFyNgE7Xs2atWVgKjVSwujnfHdcweGrRi9oACxZBNzadV3W4SjZ > 1bnfrSsjfPRAE4lfFdFFciwd+pdKkNgXj/VIWJ5923VMd+ofD+Y9eqyVqyJnUOi/ > KZSjABWoesI4HWdyAbF/XjdiRfpOkXxc8G4OuMtRMeFP923KHXnC78gIz+WrPHHM > KskpSkSU5vCobRa7e3usUt4BEQDje9F64+VuF/Vc96vAKMxe82g7eiErDv2CcgA= > =/quV > -----END PGP SIGNATURE-----
